Method and apparatus for updating locations of dormant mobile stations

Abstract

In code division multiple access communication systems, there are three levels for updating locations of dormant mobile stations (MSs) and setting up fast call. In sector and are levels, the dormant MS send a layer 2 message containing a message type and MS identifier to a base transceiver station (BTS). Since the message is associated with the sector where the MS is located, the network is aware of the MS's location from the updated location. The dormant MS sends to the BTS a reconnect message containing a message type and an MS identifier. The MS's dormant to active state transition is initiated by the MS. In the communication network, sub-packet zone ID is broadcasted in the overhead message. The MS reports its location change on R-CSCH and the network with the BSC level control can page the MS within the zone where the MS sends the report.

Description

TECHNICAL FIELD

[0002] The present invention relates to a method and an apparatus for updating locations of dormant mobile stations and in particular to a method and an apparatus for updating the locations of mobile stations to support fast call setup and reduce paging resource utilization in wireless access networks.

BACKGROUND INFORMATION

[0003] Code division multiple access (CDMA) communication systems provide communication services of wireless radio transmissions. In wireless access networks in accordance with CDMA systems, mobile stations (MSs) connected thereto may be in different states, e.g., active and dormant states. Moreover, a power-on MS may be operating in different states (e.g., active state, control-hold state or dormant state in a cdma2000 system). When an MS is in the dormant state, usually, the wireless access network has no knowledge on the location of the dormant MS. It is ideal in the wireless access network to have knowledge of an MS's location at sector level when the MS is in the dormant state, so as to support fast call setup as well as efficient paging.

[0004] Currently, the typical manner in which the network will determine the location of the MS will be to broadcast to the entire network. This presents a significant drain on the network resources. Further, in order for the wireless access network to know an MS's location as it moves through the network, an MS in the dormant state has to report on its location over the reverse link random channel whenever the MS performs an idle handoff. However, such a mechanism to update an MS's location significantly increases the reverse link overhead. It is therefore necessary to reduce the overhead caused by the location update and, at the same time, still enable efficient paging.

[0005] In some situations, whenever the network wants to bring the MS in the dormant state back to the active state, the network has to page the MS across the entire network to know the location of the MS. After the MS responds to the paging and the network becomes aware of the location of the MS, the network can allocate dedicated resources to the MS and move it to the active state. Usually, this procedure takes about 1-2 seconds. It has been shown that the system capacity and the MS's end-to-end performance are quite sensitive to the dormant to active state transition delay, especially in a network where packet-data applications dominate the traffic load.

[0006] In other situations, the network has data to send to an MS that is in a dormant state, but without bringing the MS back to the active state (e.g., short data burst application). In such instances, the network has to send the data across the whole network as it has no information on the location of the MS. This usually consumes significant forward link resources, especially when the short data burst application is widely supported. If the wireless access network is aware of the location of the MSs in the dormant state, the network will send a short data burst to the MS through the right sector and the consumption of the forward link resource will be reduced. However, due to the consideration of the reverse link overhead, the frequency of sending “location update” messages should be configurable based on different scenarios.

[0007] Still other situations address the problem associated with locating the dormant MS through the use of current layer 3 messaging for the purpose of location update.

[0008] Attached with each such layer 3 message is a list of pilot strengths that is redundant and increases the reverse link overhead.

[0009] SUMMARY OF THE INVENTION

[0010] It is an object of the present invention to provide an improved method and apparatus for updating locations of dormant MSs. The method and apparatus in accordance with the present invention achieve reduction of the overhead caused by the location update and to enable efficient paging.

[0011] In accordance with one aspect of the present invention, there is provided a method for determining when a location update message is sent from a mobile station (MS) to a base transceiver station (BTS) when the MS is in a dormant state. The method includes the steps of: starting a first timer when the MS enters a dormant state; starting a second timer when the first timer reaches a predefined value T1; while the first timer is counting and prior to its reaching the predefined value T1, sending a layer 2 location update message whenever the MS performs an idle handoff indicating that the strongest pilot signal strength has changed from one sector to another sector; while the second timer is counting and prior to its reaching a predefined value T2, sending a layer 2 location update message whenever a further criterion is met; and after the second timer has reached the predefined value T2, sending no further layer 2 location update messages.

[0012] For example, the further criterion is a time period, an MS's travel distance, a predefined number of idle handoffs.

[0013] Advantageously, the values T1 and T2 of the first and second timers are defined based on the condition of the network (e.g., QoS). The values T1 and T2 are provided by the network to the MSs.

[0014] In accordance with another aspect of the present invention, there is provided a method for defining the region of a wireless network in which to page a dormant mobile station (MS) when the network determines that data is to be sent to that dormant MS.

[0015] The method includes the steps of: starting a first timer when the MS enters a dormant state; starting a second timer when the first timer reaches a predefined value T1; while the first timer is counting and prior to its reaching the predefined value T1, sending an MS page to the sector indicated by the most recent layer 2 location update message received from the MS; while the second timer is counting and prior to its reaching a predefined value T2, sending an MS page to the sectors surrounding the sector indicated in the most recently received layer 2 location update message consistent with the further criterion being used to trigger a location update messages being sent from the MS; and after the second timer has reached the predefined value T2, sending an MS page to all network sectors.

[0016] In accordance with yet another aspect, there is provided a method for determining when a location update message needs to be sent from an MS to a base transceiver station (BTS) when the MS is in a dormant state. The method includes the steps of: determining if the MS has moved physically from one geographic region to another region served by a cell sector; and sending a location update message to the network servicing the MS indicating that the two strongest pilot signals are received by the MS.

[0017] For example, the step of determining includes the step of determining if the MS has moved physically outside the geographic region served by a plurality of cell sectors defined in a sub-packet zone received previously from the network servicing the MS. Similarly, the step of determining may include the step of: determining if the MS has moved physically into the geographic region served by a cell sector not identified in a list of cell sectors in a sub-packet zone received previously from the network servicing the MS.

[0018] Advantageously, the location update message is transmitted as a Level 2 message. The layer 2 location update message contains a message type and an MS identifier, thereby the network updating the location of the MS.

[0019] The method may further include the step of: sending by the BTS to the MS a location update acknowledgement message containing a message type and an MS identifier, in response to the layer 2 location update message from the MS. Accordingly, the location update is initiated by the MS.

[0020] The methods may further include the steps of sending by the MS in the dormant state to the BTS a reconnect message containing a message type and an MS identifier; and sending by the BTS to the MS a channel assignment message. The MS's dormant to active state transition is initiated by the MS.

[0021] The method may further include the steps of: sending by the MS to the BTS a layer 2 location update message containing a message type and an MS identifier; sending by the BTS to the MS a location update acknowledgement message containing a message type and an MS identifier; and sending by the BTS to the MS a message informing MS's active set The BTS initiates an MS's dormant to active state transition.

[0022] The method may further include the steps of: sending by the MS to the BTS a layer 2 location update message containing a message type and an MS identifier; sending by the BTS to the MS a location update acknowledgement message containing a message type and an MS identifier, sending by the BTS to the MS a message informing MS's active set; sending by the BTS to the MS a data burst message; and sending by the MS to the BTS a data burst acknowledgement message containing a message type and an MS identifier. The data burst is initiated by the BTS.

[0023] In communication services, zones may be registered to track MSs. BTSs need to track MSs to a smaller tracking zone to achieve efficient dormant to active transition. In accordance with the present invention, there is provided a method for tracking zone update to enable the network to page a mobile station (MS) in a smaller area, zones relating to base station controllers (BSCs) that control communications among the BTSs and the MSs, the zones being further defined as smaller zones that are registered for zone tracking. The method includes the steps of: defining the size of the tracking zones; defining the zones of the BTSs; broadcasting tracking zone identifiers; and paging MSs in the tracking zones.

[0024] In accordance with one aspect of the present invention, sub-packet zone ID is broadcasted in the overhead message. The MS reports its location on R-CSCH when it detects a tracking zone change. Based on the report from the MSs, the network with the BSC level control can page the MS within the zone where the MS sends the report

[0025] Advantageously, the MS reports on its change of location in the tracking zone. The reporting of the location change is made on R-CSCH. For example, the same value is assigned to the BTSs in the same tracking zone and the size of the zone is determined. The values are defined for the tracking zone identifier; the number of tracking zone identifiers to be maintained in the tracking zone list; the maximum number of Radio Environment Report Messages that the MS is permitted to transmit before disabling tracking zone reporting the BTS's support of tracking zone reporting indicator; and the tracking zone list which is a list of most recent tracking zone identifier received by the MS.

[0026] In accordance with yet another aspect, there is provided a mobile station (MS) for communicating with a base transceiver station (BTS) and a base station controller (BSC) in a wireless communication system, the MS in a dormant state sending a location update message, the MS starting a first timer when the MS enters a dormant state; starting a second timer when the first timer reaches a predefined value T1; while the first timer is counting and prior to its reaching the predefined value T1, sending a layer 2 location update message whenever the MS performs an idle handoff indicating that the strongest pilot signal strength has changed from one sector to another sector; while the second timer is counting and prior to its reaching a predefined value T2, sending a layer 2 location update message whenever a further criterion is met; and after the second timer has reached the predefined value T2, sending no further layer 2 location update messages.

[0027] Also, a communication network including the MS and a base transceiver stations (BTSs) may be provided according to an embodiment of the present invention. The network pages a dormant MS when the network determines that data is to be sent to that dormant MS. In the network, the BTS receives the layer 2 location update message and sends a location update acknowledgement message to the MS.

[0028] In accordance with yet another aspect of the present invention, there is provided a system for tracking zone update to enable the network to page a mobile station (MS) in a smaller area, zones relating to base station controllers (BSCs) that control communications among the BTSs and the MSs, the zones being further defined as smaller zones that are registered for zone tracking.

[0029] In accordance with the present invention, the network is able to know the location of dormant MSs. The overhead caused by the location update can be reduced and still efficient paging is enabled.

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIG. 1 illustrates a wireless access network based on the CDMA system that can operate in accordance with an embodiment of the present invention.

[0031] FIG. 2 illustrates a method for updating the location of an MS to facilitate fast paging in accordance with an embodiment of the present invention.

[0032] FIGS. 3A and 3B illustrate a method for initiating the MS's dormant to active state transition by the MS in accordance with an embodiment of the present invention.

[0033] FIGS. 4A and 4B illustrate a method for initiating the MS's dormant to active state transition by the BTS in accordance with an embodiment of the present invention.

[0034] FIG. 5 illustrates a method for initiating the data burst transmission by the MS in accordance with an embodiment of the present invention.

[0035] FIG. 6 illustrates a method for initiating the data burst transmission by the BTS in accordance with an embodiment of the present invention.

[0036] FIG. 7 illustrates service zones defined by areas wherein MSs communicate with the relevant BTSs wherein a method for tracking zone update according to an embodiment of the present invention can operate.

DETAILED DESCRIPTION

[0037] The present invention uses short layer 2 signalling to facilitate location determination of the MS within a network. The usage of shorter messages (layer 2 message) significantly over-performs the use of longer messages (e.g., layer 3). In accordance with an embodiment of the present invention, a method of three-level location update by MSs in dormant state is provided. The three-level location update in accordance with the present invention may be applied to a cdma2000 system, for example.

[0038] In an example of the present invention, a three-level location update mechanism is defined that is a “sector level” location update, an “area level” location update, and a completion of location update (i.e., a “network level”).

[0039] In the sector level location update, after an MS enters a dormant state, it reports its location whenever it performs an idle handoff. This operation is called a “sector level” location update and operates only for a certain period of time. The purpose of the “sector level” location update is to speed up the packet data state transition from dormant to active.

[0040] In the area level location update, after the “sector level” location update period, the MS reduces the frequency of location update. The MS performs location update once every specified number of idle handoffs. This operation is called “area level” location update and is performed for a certain period of time. The purpose of the “area level” location update is to significantly reduce the location update overhead (compared to the case of “sector level” location update) and still provide information on an MS's ‘rough location’ for the network to estimate the paging area.

[0041] In the completion of location update, after the operation of the “area level” location update, an MS stops updating its location completely. At this level, the existing operation procedure for an MS in a dormant state is performed. Regarding the location update, the network operates at three levels: i.e., a sector level, an area level (page control mechanism), and a network level.

[0042] Whenever the network requires an MS to go to dormant through a “release” message, two timer values are defined, T1 and T2. Here, T1 specifies the time period when operating on the “sector level” location update and T2 specifies the time period when operating on the “area level” location update. The values of T1 and T2 are defined based on the parameters such as the traffic type, the system load, the MS's type and so on. When an MS enters the dormant state, the timer starts counting and when it reaches T1, it stops. Then, the timer restarts counting and when it reaches T2, it stops.

[0043] Due to the “location update” messages being sent over the random channel by the MSs, the “location update” message should be as short as possible in order to increase the throughput and reduce the interference. In this message, only the absolutely necessary information is carried, which is an MS_ID, to uniquely identify the MS.

[0044] This MS_ID is sent over a layer 2 message. The MS_ID is assigned either during call setup or whenever the MS enters dormant state. The MS sends the location update layer 2 message on the reverse link random access channel associated with the sector selected by the MSs. Therefore, when the network receives the layer 2 message, both the MS and the sector are uniquely identified.

[0045] Any radio environment related information (such as pilot strength measurements) will not be attached with each “location update” message and can be sent on the dedicated channel if needed when an MS is brought back to the active state.

[0046] For the sake of reliability of the location update operation, an acknowledgement to the “location update” message is implemented. However, this is an optional operation and the network can decide whether such an acknowledgement is required or not through a control bit along with the “release” message which brings the MS to the dormant state.

[0047] The sector level location update is performed. When the MS goes to a dormant state, the timer is set to count and it continues up to T1. In today's system, when the MS is in the dormant state, it continuously monitors the pilot strength of the surrounding sectors. The MS typically selects a sector with the highest pilot strength to monitor any paging information from the network. When a new sector with the highest pilot strength is detected, the MS performs an idle handoff and puts this new sector into its active set (1 member). In accordance with an embodiment of the present invention, the location update is performed after the occurrence of every idle handoff. The location update procedure is performed until the timer reaches T1. Therefore, before the timer counts T1, the network is able to assign resources to the MS immediately on the reported sector and bring the MS back to its active state when needed. This feature is called fast call setup. When the timer reaches T1, the MS starts the “area level” location update procedure, and the timer restarts counting until T2.

[0048] When an MS starts the “area level” location update procedure, the timer restarts counting and the MS reports its location through the “location update” message. The trigger for sending the “location update” message is a further criterion such as a timer based, distance based, or count of idle handoff based criteria. The frequency of sending the “location update” message in this period should be much lower than that during the “sector level” operation. If the network needs to page an MS, the network can perform the paging in a larger area than one sector but much smaller area than the entire network and the specifics of this page is implementation specific. For example, if the further criterion is time based (such as every 15 minutes where the period of T2 is perhaps 3 hours), the paging should be in sectors consistent with the distance an MS could travel during that 15 minute interval. If the further criterion is distance based, then the network page need only cover the area in which the MS could travel without causing a location update message being sent. If the further criterion is based on counting idle handoffs, a predefined number of idle handoffs can be counted or a predetermined number of idle handoffs indicating a move of the MS into a new sector can be counted. When the timer reaches T2, the MS starts the “network level” location update procedure.

[0049] The network location update is performed. An MS stops sending any location update message and the network has to do the general paging when needed. After an MS stops sending the “location update” message, the existing procedure is resumed.

[0050] The network can configure the MS to bypass the “sector level” and/or the “area level” update. By setting T1 as 0, the “sector level” update is bypassed. By setting T2 as 0, the “area level” update is bypassed.

[0051] In order to support the three-level location update operation, the existing layer 3 message (resource release message (RRM)/resource release mini-message (RRMM) can be modified to include the values of T1 and T2 and the “location update acknowledge required” flag. The value of T1 and/or T2 could be zero, which means that there is no corresponding location update period. The “location update acknowledge required” flag (one bit) can be set or reset to show whether the acknowledgement to the “location update” message is supported.

[0052] In order to support a short message (5 ms layer 2 message), two options are disclosed. 1) Option 1 is to modify the header part in the existing reservation mode of the reverse link enhanced access channel (R-EACH). Such modified header format is shown in Tables hereinafter. Option 2 is to define a new 5 ms frame (9.6 kb/s) for basic mode operation of R-EACH. The layer 2 information carried on this frame is same as Option 1. As the long code mask includes the identification of sector used, R-EACH channel, the relationship between the MS and the selected R-EACH channel of the selected sector is unique.

[0053] A new MS_ID is defined and sent in the “location update” message. This MS_ID length can be, e.g., 24 bit, to uniquely identify an MS in the dormant state that supports location update operation. The MS_ID is sent through the reverse link channels associated with the sector which the MS selected as the member of its active set (the long code mask used for the transmission of the “location update” message) includes the sector ID. Therefore, the one-to-one relationship between the MS and the sector is clearly identified. The MS_ID can be assigned either at the registration of the MS or whenever an MS goes to the dormant state through the existing RRM/RRMM.

[0054] If the network supports the feature of acknowledging the “location update” message, the ACK can be sent on the forward link channel assignment channel (F-CACH) or on the forward link common control channel (F-CCCH).

[0055] If the network wants to bring an MS in the dormant state back to active state before the expiration of T1, the network can send the Enhanced Channel Assignment message (ECAM) on F_CCCH channel and bring the MS back to the active state. If multi-legs operation (multiple members in an active set of MSs in a soft handoff) is required, the network can require the MS to report its radio environment through the pilot strength measurement message (PSMM)/pilot strength measurement mini-message (PSMMM) or the MS can autonomously sends PSMM/PSMMM once it acquires the traffic channel.

[0056] When the network wants to either bring an MS back or has short data to send to an MS when the MS is operating in the “area level” location update period, the network decides the paging range based on the parameters which control the rule of location update operation.

[0057] In another example of the present invention, the overhead caused by the location update is to define a MAC layer message for the purpose of location update is reduced. When the network brings an MS to the dormant state, the network assigns a specific length (e.g., 24-bit) mobile station identifier, LOC_UP_MS_ID, to the MS in a L3 signalling message.

[0058] Whenever an MS in the dormant state reports its location, instead of sending a L3 message with radio environment report, the MS sends its LOC_UP_MS_ID contained in a MAC layer “location update” message over a random channel associated with the sector the MS is monitoring. In this way, the network obtains the information on the MS's location. The additional radio environment report can be sent on the dedicated channel if needed, once a dedicated channel is acquired.

[0059] Since the MAC layer “location update” message contains much fewer information bits than a L3 layer message, the MAC layer message can be sent, for example, in a frame with the length of 5 ms at rate of 9.6 kbps. The shorter message length sent over the random channel reduces the interference and increases the throughput by reducing the possibility of collisions. The network can acknowledge each “location update” message by using the existing MAC layer ACK mechanism.

[0060] FIG. 1 shows a wireless access network that can operate in accordance with an embodiment of the present invention. In FIG. 1, the network includes a plurality of Base Transceiver Stations (BTSs) (here only two BTSs 111 and 113 are shown for simplicity). Each of the BTSs provides communication links among a plurality of MSs (MSs) (here only three MSs 121, 123 and 125 are shown for simplicity) and between the MSs. The BTSs are connected to a Base Station Controller (BSC) 141 which is connected to a wireline network such as the Public Switching Telephone Network (PSTN) 131. The BSC 141 controls communication operations in the system, the operation being in relation to a back haul between the PSTN 131 and the BTSs. The BSC 141 and BTSs 111 and 113 each have central processing units (CPU) and related data store means (not shown) to perform the communication and other functions. Also, each of the MSs 121-125 has a CPU and related data store means (not shown) to perform the communication and the other functions. Each of the MSs 121-125 provides a timer function to enable the location update operation. The timer's function may be achieved by the CPU of the MS. The timer starts when the MS enters its dormant state. The timer stops when it reaches a specified value T1. Thereafter, the timer restarts and it stops when it reaches another specified value T2.

[0061] The network shown in FIG. 1 operates at three levels: i.e., a sector level, an area level (page control mechanism), and a network level. The network and the MSs communicate with the R_EACH messages and the F_CACH messages. Table I shows the format of the release C R_EACH header (32 bits).

TABLE I
Field       Length (bits)
HASH_ID     16
RATE_WORD   3
MODE_ID     1
HO_REQ_ID   0 or 1
NEIGHBOR_PN 0 or 9
RESERVED    As required

[0062] In Table I,

[0063] HASH_ID: Hash Idenfifier.

[0064] The MS shall set this field to HASH_IDS. HASH_ID is for identification by F_CASH.

[0065] RATE_WORD: Rate and frame size indicator.

[0066] The MS shall set this field according to Table II to indicate the requested transmission rate and frame size of the data to be transmitted on R-CCCH. RATE_WORD indicates one of six configurations.

[0067] MODE_ID: Mode Identifier.

[0068] The MS shall set this field to ‘0’. Other values for this field are reserved.

[0069] HO_REQ_ID: Handoff Request Identifier.

[0070] The MS shall include this field if MODE_ID is set to ‘0’.

[0071] Otherwise, the MS shall omit this field.

[0072] NEIGHBOR_PN: Neighbor Pilot PN Offset.

[0073] The MS shall include this field only if HO_REQ_ID is included and set to ‘1’. If included, the MS shall set this field to the neighbor pilot PN offset.

[0074] RESERVED: Reserved bits.

[0075] The MS shall set this field so that the total number of bits in this message is 32. The MS shall set all the reserved bits to ‘0’.

[0076] Table II shows the RATE_WORD Encoding.

TABLE II
	Data Rate	Frame Length	No. of Information
RATE_WORD	(kbps)	(ms)	(bits)
‘000’	9.6	20	172
‘001’	19.2	20	360
‘010’	19.2	10	172
‘011’	38.4	20	744
‘100’	38.4	10	360
‘101’	38.4	5	172
‘110’-‘111’	RESERVED

[0077] Table III shows the format of a location update message (LUM).

TABLE III
Field    Length (bits)
RESERVED As required
MS_ID    24
MSG_TYPE 2 (10)

[0078] In Table III,

[0079] RESERVED: Reserved bits.

[0080] The MS shall set this field so that the total number of bits in this message is 32. The MS shall set all the reserved bits to ‘0’.

[0081] MS_ID: Mobile station identifier.

[0082] The MS shall set this field to LOC_UP_MS_IDs.

[0083] MSG_TYPE: Message Type.

[0084] The MS shall set this field to ‘10’.

[0085] Table IV shows the format of a reconnect message.

TABLE IV
Field    Length (bits)
RESERVED As required
MS_ID    24
MSG_TYPE 2 (01)

[0086] In Table IV,

[0087] RESERVED: Reserved bits.

[0088] The MS shall set this field so that the total number of bits in this message is 32. The MS shall set all the reserved bits to ‘0’.

[0089] MS_ID: Mobile station identifier.

[0090] The MS shall set this field to LOC_UP_MS_IDs.

[0091] MSG_TYPE: Message Type.

[0092] The MS shall set this field to ‘01’.

[0093] Table V shows the format of a reservation request message.

TABLE V
Field       Length (bits)
Reserved    As required
HASH_ID     16
MODE_ID     1
RATE_WORD   3
HO_REQ_ID   0 or 1
NEIGHBOR_PN 0 or 9
MSG_TYPE    2 (00)

[0094] In Table V,

[0095] RESERVED: Reserved bits.

[0096] The MS shall set this field so that the total number of bits in this message is 32. The MS shall set all the reserved bits to ‘0’.

[0097] HASH_ID: Hash Identifier.

[0098] The MS shall set this field to HASH_IDS. HASH_ID is for identification by F_CASH.

[0099] MODE_ID: Mode Identifier.

[0100] The MS shall set this field to ‘0’. Other values for this field are reserved.

[0101] RATE_WORD: Rate and frame size indicator.

[0102] The MS shall set this field according to Table II to indicate the requested transmission rate and frame size of the data to be transmitted on R-CCCH.

[0103] HO_REQ_ID: Handoff Request Identifier.

[0104] The MS shall include this field if MODE_ID is set to ‘0’.

[0105] Otherwise, the MS shall omit this field.

[0106] NEIGHBOR_PN: Neighbor Pilot PN Offset.

[0107] The MS shall include this field only if HO_REQ_ID is included and set to ‘1’. If included, the MS shall set this field to the neighbor pilot PN offset.

[0108] MSG_TYPE: Message Type.

[0109] The MS shall set this field to ‘00’.

[0110] Table VI shows the format of an Early Acknowledgement Channel Assignment Message (EACAM).

TABLE VI
Field     Length (bits)
MSG_TYPE  3
HASH_ID   16
RATE_WORD 3
RCCCH_ID  5
CPCCH_ID  2
HO_FLAG   1
RESERVED  2

[0111] In Table VI,

[0112] MSG_TYPE: Message Type.

[0113] The BTS shall set this field to ‘000’.

[0114] HASH_ID: Hash Identifier.

[0115] The BTS shall set this field to the HASH_ID field of the corresponding Enhanced Access Channel header received from the MS.

[0116] RATE_WORD: Rate and frame duration indicator.

[0117] The BTS shall set this field according to above-mentioned Table II to indicate the transmission rate and frame duration of the R-CCCH that the BTS grants to the MS. The BTS should determine the rate and frame duration based on the RATE_WORD field of the corresponding Enhanced Access Channel header received from the MS.

[0118] RCCCH_ID: Reverse Common Channel Identifier.

[0119] The BTS shall set this field to the R-CCCH index that the BTS grants to the MS.

[0120] CPCCH_ID: Common Power Control Channel Identifier.

[0121] The BTS shall set this field to the index of the Common Power Control Channel.

[0122] HO_FLAG: Handoff Flag.

[0123] The BTS shall set this field to ‘1’ if the HO_REQ_ID field of the corresponding Enhanced Access Channel header received from the MS is equal to ‘1’ and the BTS grants the request for Power Control Subchannel being in soft-handoff. Otherwise, the BTS shall set this field to ‘0’.

[0124] RESERVED: Reserved bits.

[0125] The BTS shall set all the bits in this field to ‘0’.

[0126] Table VII shows the format of a power control channel assignment message (PCCAM).

TABLE VII
Field          Length (bits)
MSG_TYPE       3
HASH_ID        16
CPCCH_ID_2     2
CPCSCH_2       7
POWER_COMB_IND 1
RESERVED       3

[0127] In Table VII,

[0128] MSG_TYPE: Message Type.

[0129] The BTS shall set this field to ‘001’.

[0130] HASH_ID: Hash Identifier.

[0131] The BTS shall set this field to the HASH_ID field of the corresponding Enhanced Access Channel header received from the MS.

[0132] CPCCH_ID—2: Common Power Control Channel Identifier.

[0133] The BTS shall set this field to the Common PC Channel corresponding to the neighbor BTS.

[0134] CPCSCH—2: Common Power Control Subchannel Identifier.

[0135] The BTS shall set this field to the Common PC Sub-channel corresponding to the neighbor BTS.

[0136] POWER_COMB_IND: PC bits combine Indicator.

[0137] If the BTS instructs the MS to combine the PC bits received from the neighbor BTS, the BTS shall set this field to ‘1’. Otherwise, the BTS shall set this field to ‘0’.

[0138] RESERVED: Reserved bits.

[0139] The BTS shall set this field to ‘000’.

[0140] Table VIII shows the format of a location update acknowledgment message (LUAM).

TABLE VIII
Field    Length (bits)
MSG_TYPE 3 (010)
MS_ID    24
RESERVED As required

[0141] In Table VIII,

[0142] MSG_TYPE: Message Type.

[0143] The BTS shall set this field to ‘010’.

[0144] MS_ID: Mobile station identifier.

[0145] The BTS shall set this field to the LOC_UP_MS_ID field of the corresponding Location Update Message received from the MS.

[0146] RESERVED: Reserved bits.

[0147] The BTS shall set this field to ‘00000’.

[0148] Table IX shows the format of a modified message format of a data burst acknowledgement message (DBAM).

TABLE IX
Field    Length (bits)
MSG_TYPE 3 (011)
MS_ID    24
RESERVED As required

[0149] In Table IX,

[0150] MSG_TYPE: Message Type.

[0151] The BTS shall set this field to ‘011’.

[0152] MS_ID: Mobile station identifier.

[0153] The BTS shall set this field to the LOC_UP_MS_ID field of the corresponding Location Update Message received from the MS.

[0154] RESERVED: Reserved bits.

[0155] The BTS shall set this field to ‘00000’.

[0156] FIG. 2 shows a method of location update by an MS. The BTS and the MS communicate with the R_EACH messages and the F_CACH messages. Referring to FIGS. 1 and 2, the location update initiated by an MS will be described.

[0157] The values of T1 and T2 are defined based on the parameters such as the traffic type, the system load, the MS's type and so on. The values of T1 and T2 are determined by the BSC 141 and sent by the BSC 141 (of the sector) to the MSs 121-125.

[0158] The MS initiates the location update. When the MS (e.g., the MS 121) enters its dormant state, the timer of the MS starts counting. The MS sends a message consisting of a preamble and header (MSG_Type=00) to the BTS1 (e.g., the BTS 111) through the reverse link. The location update header is shown in Table III (MSG_TYPE of two bits). The BTS1 sends back a location update acknowledgement message (MSG_Type=010) through the forward link to the MS. The location update acknowledgement message of three bits is shown in Table VIII (MSG_TYPE of three bits). Before sending the location update acknowledgement message to the MS, the BTS1 notifies the BSC 141 to identify the update of the active set of the MS (Active_set info (MS_ID)). This is repeated in a case where the timer does not reach T1. The location of the dormant MS is updated.

[0159] If the MS 121 moves physically outside the geographic area served by the BTS 111 to another area served by the BTS2 (e.g., the BTS 113), the MS 121 sends a message consisting of a preamble and header (MSG_Type=00) only to the BTS2 through the reverse link. The BTS2 sends back a location update acknowledgement message (MSG_Type=010) through the forward link to the MS. Before responding to the MS, the BTS2 sends the BSC 141 a message identifying the MS (Active_set info (MS_ID)). The location of the dormant MS is updated.

[0160] The “location update” message is short in order to increase the throughput and reduce the interference. In this message, only the absolutely necessary information is carried, which is an MS_ID, to uniquely identify the MS. This MS_ID is sent over a layer 2 message. The MS sends the location update layer 2 message on the reverse link random access channel associated with the sector selected by the MSs. Therefore, when the network receives the layer 2 message, both the MS and the sector are uniquely identified.

[0161] Any radio environment related information (such as pilot strength measurements) will not be attached with each “location update” message and can be sent on a dedicated channel if needed when an MS is brought back to active state.

[0162] In the embodiment, the BTS sends back the acknowledgement message to the MS that initiated the location update. For the sake of reliability of location update operation, an acknowledgement to the “location update” message is implemented. However this is optional operation and the network can decide whether such an acknowledgement is required or not through a control bit along with the “release” message which brings the MS to the dormant state.

[0163] The timer is set to count when the MS goes to dormant state and continues counting up to T1. In today's systems, when the MS is in the dormant state, it continuously monitors the pilot strength of the surrounding sectors. The MS typically selects a sector with the highest pilot strength to monitor any paging information from the network. When a new sector with the highest pilot strength is detected, the MS performs an idle handoff and put this new sector into its active set (1 member).

[0164] In accordance with an embodiment of the present invention, the location update is performed after the occurrence of every idle handoff. The location update procedure is performed as long as the timer does not reach T1. Therefore, before the timer counts T1, the network is able to assign resources to the MS immediately on the reported sector and bring the MS back to its active state when needed. This feature is called fast call setup. When the timer reaches T1, the MS starts the “area level” location update procedure, and the timer starts counting until T2.

[0165] When an MS starts the “area level” location update procedure, the timer starts counting and the MS reports its location through the “location update” message. The trigger for sending the “location update” message is a further criterion such as a timer based, distance based or count of idle handoff based criteria. The frequency of sending the “location update” message in this period should be much lower than that during the “sector level” operation. When the timer reaches T2, the MS starts the “network level” location update procedure. An MS stops sending any location update message and the network has to do the general paging when needed.

[0166] If the network needs to page an MS, it can do the paging in a larger area than one sector but much smaller area than the entire network and the specifics of this page is implementation specific. For example, if the further criterion is time based (such as every 15 minutes where the period of T2 is perhaps 3 hours), the paging should be in sectors consistent with the distance an MS could travel during that 15 minute interval. If the further criterion is distance based, then the network page need only cover the area in which the MS could travel without causing a location update message being sent. If the further criterion is based on counting idle handoffs, a predefined number of idle handoffs can be counted or a predetermined number of idle handoffs indicating a move of the MS into a new sector can be counted.

[0167] The network can bring an MS in the dormant state back to active state before the expiration of T1. FIGS. 3A and 3B show the procedure of the dormant to active state transition initiated by the MS. Referring to FIGS. 1 and 3A and 3B, the dormant to active state transition by an MS will be described.

[0168] The MS (e.g., the MS 121) sends a message consisting of a preamble and header (MSG_Type=01) to the BTS (e.g., the BTS 111) through the reverse link. The reconnect header is shown in Table IV (MSG_TYPE of two bits). The BTS sends back the enhanced channel assignment message (ECAM). The MS returns to its active state and operates on one leg mode (i.e., one member in an active set). Later, the MS sends a pilot report message to the BTS over R_FCH/DCCH. This achieves higher throughput than R_REACH. Where multi-legs operation is required, the BTS sends ECAM (multiple members of active set) message to the MS over F_FCH/PDCH, because the network requires that the MS to report its radio environment through PSMM/PSMMM or the MS can autonomously sends PSMM/PSMMM once it acquires the traffic channel.

[0169] There are two options to send the ECAM via the BTS to the MS. Option 1 is to send the ECAM over F_CCCH as shown in FIG. 3A. Option 2 is to send the ECAM over F_CACH as shown in FIG. 3B. Option 2 is more efficient than option 1, but the length of message in over F_CACH is restricted.

[0170] When the network wants to either bring an MS back or has short data to send to an MS when the MS is operation in the “area level” location update period, the network decides the paging range based on the parameters which control the rule of location update operation.

[0171] The network can bring an MS in the dormant state back to active state initiated by the BTS. FIGS. 4A and 4B show the procedure of the dormant to active state transition initiated by the BTS. Referring to FIGS. 1 and 4A and 4B, the dormant to active state transition initiated by the BTS will be described.

[0172] The BTS initiates the location update in response to the MS's location update. The MS (e.g., the MS 121) sends a message consisting of a preamble and header (MSG_Type=00) to the BTS (e.g., the BTS 111) through the reverse link (R_EACH). The location update header is shown in Table III (MSG_TYPE of two bits). The BTS sends back a location update acknowledgement message (MSG_Type=010) through the forward link (F_CACH) to the MS. The location update acknowledgement message of three bits is shown in Table VIII (MSG_TYPE of three bits). In this case, the network is now aware of the location of the MS and the BTS sends the enhanced channel assignment message (ECAM) over F_CCCH. The MS backs to its active state and operates on one leg mode (i.e., one member in an active set). Then, the MS sends a pilot report message to the BTS over R_DCCH/FCH, because the network requires that the MS to report its radio environment through PSMM once it acquires the traffic channel. This achieves higher throughput than R_REACH.

[0173] Where multi-legs operation is required, there are two options of sending ECAM by the BTS to the MS. Option 1 is that the BTS sends ECAM of multiple members in active set as shown in FIG. 4A. Option 2 is that the BTS sends ECAM of the MS's active set that is necessary to be updated as shown in FIG. 4B. In Option 2, during the active state, the active set can be gradually updated.

[0174] The network can transmit the data burst to an MS in the dormant state. FIG. 5 shows the procedure of the data burst transmission initiated by a dormant MS. Referring to FIGS. 1 and 5, the data burst transition initiated by the MS will be described.

[0175] The MS (e.g., the MS 121) sends a message consisting of a preamble and header (MSG_Type=10) to the BTS (e.g., the BTS 111) through the reverse link (R_EACH). The reservation request header is shown in Table V (MSG_TYPE of two bits). The BTS sends back the early acknowledgement message (MSG_Type=01) to the MS over F_CACH. In the embodiment, the format of the Early Acknowledgement Channel Assignment Message (EACAM) shown in Table VI is modified by the location update acknowledgment message shown in Table VIII. The MS sends the preamble and data to the BTS over R_CCCH and the BTS sends data burst acknowledgement message (MSG_Type=11) to the MS over F_CACH. The format of the data burst acknowledgement message is shown in Table IX.

[0176] The network can transmit the data burst to an MS in the dormant state. FIG. 6 shows the procedure of the data burst transmission initiated by the BTS. Referring to FIGS. 1 and 6, the data burst transition initiated by the BTS will be described.

[0177] The MS (e.g., the MS 121) sends a message consisting of a preamble and header (MSG_Type=00) to the BTS (e.g., the BTS 111) through the reverse link (R_EACH). The location update message is shown in Table III (MSG_TYPE of two bits). The BTS sends back the location update acknowledgement message (MSG_Type=010) to the MS over F_CACH. In this case, the network is aware of the location of the MS, the network sends a short data burst message to the MS over F_CCCH of the sectors in the “sub-packet data zone” where the MS is. The MS sends the data burst acknowledgment message (MSG_Type=11) to the BTS over R_EACH. The format of the data burst acknowledgment message is shown in Table IX.

[0178] In communication services, zones may be registered to track MSs. Such registration zones are efficient to voice services, but not to packet data services. BTSs need to track MS to a smaller tracking zone to achieve more efficient dormant to active transitions. The present invention may provide a method for tracking zone update to enable a base transceiver station (BTS) to page a mobile station (MS) in a smaller area.

[0179] In order to improve the paging within smaller tracking zones, in accordance with an embodiment of the present invention, sub-packet zone ID is broadcasted in the overhead message. The MS that support the feature reports its location on R-CSCH when it detects a tracking zone change. The service provider configures the size of the tracking zone and all BTSs in the same tracking zone have same zone value. Based on the report from the MSs, the network with the BSC level control can page the MS within the zone where the MS sends the report.

[0180] FIG. 7 shows an example of zones containing user MSs. Referring to FIG. 7, zones Z11, Z12 and Z13 belong to the area of one Base Station Controller BSC1. Zones Z21, Z22 and Z23 belong to an adjacent area of another Base Station Controller BSC2. Each zone is divided to a plurality of smaller areas: e.g., B1, B2, B3, B4 and B5. Zone Z13 is adjacent to zone Z23 and B1, B2 and B3 belong to zone Z13 and B4 and B5 belong to zone 23, respectively.

[0181] To perform the tracking zone and the paging shown in FIG. 7, the following is necessary as CDMA Numeric Information.

[0182] TKZ_IDs—Tracking zone identifier.

[0183] TKZ_LIST_LENs—Number of tracking zone identifier to be maintained in the tracking zone list.

[0184] MAX_NUM_TKZs—The maximum number of Radio Environment Report

[0185] Messages that the MS is permitted to transit before disabling tracking zone reporting.

[0186] TKZ_SUPs—BTS support of tracking zone reporting indicator.

[0187] TKZ_LISTs—Tracking zone list. It is a list of most recent TKZ_IDs MS have received.

[0188] In the MS in the dormant state, the MS monitors the Paging Channel or the Quick Paging Channel or Forward Common Control Channel/Primary Broadcast Control Channel. The MS can receive messages, receive an incoming call (MS terminated call), initiate a call (MS originated call), cancel a priority access and channel assignment (PACA) call, initiate a registration, or initiate a message transmission.

[0189] The MS may monitor the Quick Paging Channel to determine if it should receive messages from the Paging Channel or Forward Common Control Channel.

[0190] Upon entering the Mobile Station Dormant State from the Mobile Station Initialization State, the MS shall perform the following:

[0191] If SR1_BCCH_NON_TD_INCLS is equal to ‘1’, or if SR1_TD_INCLs is equal to ‘1’ and the MS supports the transmit diversity mode specified by SR1_TD_MODEs, or if the MS supports Spreading Rate 3 on the common channel and SR3_INCLs is equal to ‘1’, the MS shall perform the following:

[0192] Set its Primary Broadcast Control Channel code channel to BCCHs,

[0193] Set the Primary Broadcast Control Channel data rate as determined by BRATs,

[0194] Set the Primary Broadcast Control Channel code rate as determined by BCCH_CODE_RATEs,

[0195] Set SLOTTEDs to YES if T_SLOTTEDs is equal to ‘00000000’ or if the MS does not support the slotted timer; otherwise, enable the TMS—Slotted timer with the duration specified by T_SLOTTEDs and set SLOTTEDs to NO, and

[0196] Perform common channel supervision. The initial parameter is set up when the MS enters the dormant state from the MS initialization state.

[0197] Otherwise, the MS shall perform the following:

[0198] Set its code channel to PAGECHs,

[0199] Set the Paging Channel data rate as determined by PRATs,

[0200] Set SLOTTEDs to YES if T_SLOTTEDs is equal to ‘00000000’ or if the MS does not support the slotted timer; otherwise, enable the TMS—Slotted timer with the duration specified by T_SLOTTEDs and set SLOTTEDs to NO, and

[0201] Perform Paging Channel supervision.

[0202] Upon entering the Mobile Station Dormant State from the Mobile Station Control on the Traffic Channel State, the MS shall perform all of the following:

[0203] Set SLOTTEDs to YES if T_SLOTTEDs is equal to ‘00000000’ or if the MS does not support the slotted timer, otherwise, enable the TMS—Slotted timer with the duration specified by T_SLOTTEDs and set SLOTTEDs to NO.

[0204] Perform common channel supervision.

[0205] If TKZ_ENABLED is YES and the tracking zone update timer is not enabled, the MS shall perform the following:

[0206] Initialize the tracking zone list TKZ_LISTs with the length of TKZ_LIST_LENs and add TKZ_IDs to the TKZ_LISTs,

[0207] Set the tracking zone update timer to infinity if TKZ_UPDATE_PRDs is equal to ‘1111’; otherwise, the MS shall set the tracking zone update timer to 2 TKZ—UPDATE—PRDS+6 seconds, then

[0208] Enable the tracking zone update timer.

[0209] If REDIRECTIONs, PACAs, and NDSS_ORIGs are equal to disabled, the MS may exit the Mobile Station Dormant State at any time and enter the System Determination Substate of the Mobile Station Initialization State with a reselection indication.

[0210] While in the Mobile Station Dormant State, the MS shall perform the following procedures:

[0211] The MS shall perform Paging Channel or Forward Common Control Channel monitoring procedures.

[0212] The MS shall perform message acknowledgment procedures with the received forward message from the BTS.

[0213] If the key set-up timer expires or has expired, the MS shall set REG_SECURITY_RESYNC (formerly called REG_ENCRYPT_RESYNC) to YES and the MS shall go to the System Determination Substate with an encryption/message integrity failure indication.

[0214] If TKZ_ENABLED is set to YES, the MS shall perform the following:

[0215] If TKZ_IDs is not equal to any entry in TKZ_LISTs, the MS shall send a Radio Environment Report Message by performing the Mobile Station Message Transmission Operation.

[0216] If TKZ timer of any entry in TKZ_LISTs has expired, the MS shall delete that entry.

[0217] If the tracking zone update timer expires, the MS shall disable the tracking zone update timer and set TKZ_ENABLED to NO.

[0218] Upon expiration of the radio environment report timer, the MS shall disable the timer and set RER_ENABLED (the radio environment report) to NO. If TKZ_INFO_INCLs is equal to ‘1’, then the MS shall perform the following:

[0219] Set TKZ_ENABLED to YES.

[0220] Initialize the tracking zone list TKZ_LISTs with the length of TKZ_LIST_LENs and add TKZ_IDs to the TKZ_LISTs,

[0221] Set the tracking zone update timer to infinity if TKZ_UPDATE_PRDs is equal to ‘1111’; otherwise, the MS shall set the tracking zone update timer to 2 TKZ—UPDATE—PRDS+6 seconds, then

[0222] Enable the tracking zone update timer.

[0223] Whenever an Extended System Parameters Message is received on the Paging Channel, the configuration message sequence number, CONFIG_MSG_SEQr, shall be compared to that stored in EXT_SYS_PAR_MSG_SEQs. If the comparison results in a match, the MS may ignore the message. If the comparison results in a mismatch, then the MS shall process the remaining fields in the message as follows.

[0224] The MS shall store MS initiated position location determination supported indicator (MS_INIT_POS_LOC_SUP_INDs=MS_INIT_POS_LOC_SUP_INDr).

[0225] If the MS supports tracking zone, the MS shall store tracking zone supported indicator (TKZ_SUPs=TKZ_SUPr).

[0226] If TKZ_SUPs is equal to ‘1’, the MS shall store the tracking zone identifier (TKZ_IDs=TKZ_IDr).

[0227] If TKZ_ENABLED is YES and the tracking zone update timer is not enabled, the MS shall perform the following:

[0228] Initialize the tracldng zone list TKZ_LISTs with the length of TKZ_LIST_LENs and add TKZ_IDs to the TKZ_LISTs,

[0229] Set the tracking zone update timer to infinity if TKZ_UPDATE_PRDs is equal to ‘1111’; otherwise, the MS shall set the tracking zone update timer to 2 TKZ—UPDATE—PRDS+6 seconds, then

[0230] Enable the tracking zone update timer.

[0231] Whenever an ANSI-41 System Parameters Message is received, the configuration message sequence number, CONFIG_MSG_SEQr, shall be compared to that stored in A41_SYS_PAR_MSG_SEQs. If the comparison results in a match, the MS may ignore the message. If the comparison results in a mismatch, then the MS shall process the remaining fields in the message to store parameters.

[0232] The MS shall store the following parameters:

[0233] Configuration message sequence number (CONFIG_MSG_SEQs=CONFIG_MSG_SEQr, A41_SYS_PAR_MSG_SEQs=CONFIG_MSG_SEQr)

[0234] Home registration indicator (HOME_REGs=HOME_REGr)

[0235] If MSG_INTEGRITY_SUPr is equal to ‘1’ and SIG_INTEGRITY_SUP_INCLr is equal to ‘1’, the MS shall store the message integrity algorithms that the BTS supports (SIG_INTEGRITY_SUPs=SIG_INTEGRITY_SUPr); otherwise, the MS shall set SIG_INTEGRITY_SUPs to ‘00000000’.

[0236] The MS shall also store the following parameters if the MS is not in the Origination Attempt Substate or Page Response Substate:

[0237] System identification (SIDs=SIDr)

[0238] Network identification (NIDs=NIDr)

[0239] Registration zone (REG_ZONEs=REG_ZONEr)

[0240] If DIST_REG_INCL is equal to ‘0’, then the MS shall set REG_DIST equal to ‘00000000000’.

[0241] If the MS supports tracking zone, the MS shall store tracking zone supported indicator (TKZ_SUPs=TKZ_SUPr). If TKZ_SUPs is equal to ‘1’, the MS shall store the tracking zone identifier (TKZ_IDs=TKZ_IDr).

[0242] If TKZ_ENABLED is set to YES and the tracking zone update timer is not enabled, the MS shall perform the following:

[0243] Initialize the tracking zone list TKZ_LISTs with the length of TKZ_LIST_LENs and add TKZ_IDs to the TKZ_LISTs,

[0244] Set the tracking zone update timer to infinity if TKZ_UPDATE_PRDs is equal to ‘1111’; otherwise, the MS shall set the tracking zone update timer to 2 TKZ—UPDATE—PRDS+6 seconds, then

[0245] Enable the tracking zone update timer.

[0246] If the MS supports the Mobile Station Message Transmission Operation, the operation will be performed when the user directs the MS to transmit a Data Burst Message, or when the MS detects a change in the hook status since the last time when the MS sent hook status information and the MS supports the Device Information Message on the R-CSCH, or when the MS detects that a Radio Environment Report Message is required to be transmitted on the R-CSCH.

[0247] If the MS supports the Mobile Station Message Transmission Operation, the MS shall set CURR_ACC_MSG_SEQ to NULL.

[0248] If the MS supports the Mobile Station Message Transmission Operation and the operation is performed when the user directs the MS to transmit a Data Burst Message, the MS shall enter the Update Overhead Information Substate of the System Access State with a message transmission indication within T33m seconds.

[0249] If the MS supports the Mobile Station Message Transmission Operation and the operation is performed when the MS detects a change in the hook status since the last time when the MS sent hook status information, the MS shall enter the Update Overhead Information Substate of the System Access State with a hook status indication within T33m seconds.

[0250] If the MS supports the Mobile Station Message Transmission Operation and the operation is performed when the MS detects that a Radio Environment Report Message is required to be transmitted on the R-CSCH, the MS shall perform the following:

[0251] If RER_ENABLED is set to YES, the MS shall enter the Update Overhead Information Substate of the System Access State with a radio environment report indication within T33m seconds.

[0252] Otherwise, if TKZ_ENABLED is set to YES, the MS shall enter the Update Overhead Information Substate of the System Access State with a tracking zone report indication within T33m seconds.

[0253] The MS enters different substates dependent upon the entry of the Update Overhead Information Substate as follows:

[0254] If this substate was entered with a message transmission indication, the MS shall enter the Mobile Station Message Transmission Substate with a message transmission indication.

[0255] If this substate was entered with a hook status indication, the MS shall enter the Mobile Station Message Transmission Substate with a hook status indication.

[0256] If this substate was entered with a PACA cancel indication, the MS shall enter the PACA Cancel Substate.

[0257] If this substate was entered with a radio environment report indication, the MS shall enter the Mobile Station Message Transmission Substate with a radio environment report indication.

[0258] If this substate was entered with a tracking zone report indication, the MS shall enter the Mobile Station Message Transmission Substate with a tracking zone report indication.

[0259] In the Mobile Station Message Transmission Substate, the MS sends a Data Burst Message, a Device Information Message, or a Radio Environment Report Message. If the BTS responds with an authentication request, the MS responds in this substate.

[0260] Upon entering the Mobile Station Message Transmission Substate, the MS shall transmit the message as follows:

[0261] If the MS entered this substate with a message transmission indication, the MS shall transmit the Data Burst Message to the BTS.

[0262] If the MS entered this substate with a hook status indication, the MS shall set the autonomous message timer equal to AUTO_MSG_INTERVALs and shall start the timer. The MS shall transmit the Device Information Message to the BTS, with the RECORD_TYPE field of the message set to 00100000 and the Hook Indicator field set to the current hook status.

[0263] If the MS entered this substate with a radio environment report indication, the MS shall transmit the Radio Environment Report Message to the BTS in assured mode, and increment RER_COUNT (the radio environment report count) upon receiving confirmation of delivery. If, after incrementing, RER_COUNT is equal to MAX_NUM_RERs, the MS shall set RER_ENABLED to NO. If RER_ENABLED is set to NO and TKZ_INFO_INCLs is equal to ‘1’, the MS shall perform the following:

[0264] Set TKZ_ENABLED to YES.

[0265] Initialize the tracking zone list TKZ_LISTs with the length of TKZ_LIST_LENs and add TKZ_EDs to the TKZ_LISTs,

[0266] Set the tracking zone update timer to infinity if TKZ_UPDATE_PRDs is equal to ‘1111’; otherwise, the MS shall set the tracking zone update timer to 2 TKZ—UPDATE—PRDS+6 seconds, then

[0267] Enabled the tracking zone update timer.

[0268] If the MS entered this substate with a tracking zone report indication, the MS shall perform the following:

[0269] The MS shall transmit the Radio Environment Report Message to the BTS.

[0270] If the MS receives confirmation of delivery of Radio Environment Report Message, the MS shall add TKZ_IDs to TKZ_LISTs and start the TKZ timer for this TKZ_IDs. If TKZ_LISTs is full, the entry with active TKZ timer with smallest remaining TKZ timer value shall be removed from the list before adding the new entry.

[0271] The MS shall increment TKZ_COUNT upon receiving confirmation of delivery. If, after incrementing, TKZ_COUNT is equal to MAX_NUM_TKZs, the MS shall disable the tracking zone update timer and set TKZ_ENABLED to NO.

[0272] While in the Mobile Station Message Transmission Substate, the MS shall monitor the Paging Channel or the Forward Common Control Channel. The MS determines and declares in a case of a loss of the Paging Channel or the Forward Common Control Channel.

[0273] In the Traffic Channel Substate, the MS may exchange Traffic Channel frames with the BTS in accordance with the current service configuration. The MS may perform the gating operation of Reverse Pilot Channel.

[0274] While in the Traffic Channel Substate, the MS shall perform the following:

[0275] The MS shall perform Forward Traffic Channel supervision. If a loss of the Forward Traffic Channel is declared, the layer 3 shall terminate all Call Control instances, and shall enter the System Determination Substate of the Mobile Station Initialization State with a system lost indication.

[0276] The MS may send a Pilot Strength Measurement Mini Message to report pilot strength order change information, periodic pilot strength information, or threshold based pilot strength information, as specified in the Mobile Assisted Burst Operation Parameters Message.

[0277] The MS shall set TKZ_ENABLED to NO, set TKZ_LISTs to NULL, and disable the tracking zone update timer.

[0278] The MS shall adjust its transmit power.

[0279] In the Release Substate, the MS confirms the disconnect of all calls and physical channels. Upon entering the Release Substate, the MS shall perform the following:

[0280] The MS shall set the substate timer for T55m seconds.

[0281] The MS shall set RER_ENABLED to its default value of NO.

[0282] In response to an Extended Release Message, procedures for exiting the Release Substate are made. If the MS received an Extended Release Message with the RER_INFO_INCL (the radio environment report information included indicator) field set to ‘1’, then the MS shall set RER_ENABLED to YES, RER_COUNT to 0, and shall perform the following:

[0283] The MS shall store the following:

[0284] maximum allowed number of radio environment reports (MAX_NUM_RERs=infinity, if MAX_NUM_RER_IDXr is equal to ‘111’; otherwise, MAX_NUM_RERs=2MAX—NUM—RER—IDXr).

[0285] maximum number of pilots to maintain in RER_PILOT_LIST (MAX_RER_PILOT-LIST_SIZEs=MAX_RER_PILOT_LIST_SIZEr).

[0286] system identification for radio environment reporting (RER_SIDs=SIDs).

[0287] network identification for radio environment reporting (RER_NIDs=NIDs).

[0288] The MS shall initialize the radio environment report pilot list (RER_PILOT_LIST). The initial RER_PILOT_LIST is defined as the set of pilots that made up the Active Set on the Traffic Channel.

[0289] The MS shall enable the radio environment report timer with an initial value of infinity if RER_TIMEr is equal to ‘111’; otherwise, the MS shall enable the radio environment report timer with an initial value of 2RER—TIMEr seconds if RER_TIME_UNITr is equal to ‘00’, or 2RER—TIMEr minutes if RER_TIME_UNITr is equal to ‘01’, or 2RER—TIMEr hours if RER_TIME_UNITr is equal to ‘10’.

[0290] If the MS received an Extended Release Message with the field of the tracking zone reporting information included indicator set to ‘1’ and the BTS support of tracking zone reporting indicator is equal to ‘1’, then the MS shall set TKZ_COUNT to 0, and shall perform the following:

[0291] The MS shall store the following:

[0292] Tracking zone list length (TKZ_LIST_LENs=TKZ_LIST_LENr).

[0293] TKZ timer (TKZ_TIMERs=TKZ_TIMERr).

[0294] Maximum allowed number of tracking zone reports (MAX_NUM_TKZs==infinity, if MAX_NUM_TKZ_IDXr is equal to ‘111’; otherwise, MAX_NUM_TKZs=2MAX—NUM—TKZ—IDXr)

[0295] Tracking zone update period (TKZ_UPDATE_PRDs=TKZ_UPDATE_PRDr).

[0296] If RER_INFO_INCL is equal to ‘0’, the MS shall set TKZ_ENABLED to YES.

[0297] If RER_INFO_INCL is equal to ‘1’, the MS shall set (TKZ_INFO_INCLs=TKZ_INFOINCLr).

[0298] The MS shall perform the procedures to determine whether to enter the Mobile Station Dormant State or System Determination Substate of the Mobile Station Initialization State.

[0299] If the MS received a Release Order with ORDQ equal to ‘00000011’ (Enhanced Release Order), the MS shall perform the procedures to exit the Release Substate.

[0300] The followings describe the messages and their PDU formats sent by the MS on the R-CSCH. The messages sent on the R-CSCH are summarized in Table X.

TABLE X
Message Name	MSG_TAG	P_REV_IN_USE*
Registration Message	RGM	All
Order Message	ORDM	All
Data Burst Message	DBM	All
Authentication Response	AURSPM	≧10
Message
Authentication	AURSYNM	≧10
Resynchronization Message
Reconnect Message	RCNM	≧9
Radio Environment Report	RERM	≧11
Message

[0301] In Table X, P_REV_IN_USE (*) equal to “All” implies all values applicable to the Band Class.

[0302] MSG_TAG: RERM—The RERM is shown in Table XI.

TABLE XI
Field       Length (bits)
LAST_REPORT 1
TKZ_REPORT  1

[0303] In Table XI,

[0304] LAST_REPORT—Last radio environment report indicator.

[0305] The MS shall set this field to ‘1’ if RER_COUNT is equal to (MAX_NUM_RERs-1) or TKZ_COUNT is equal to ((MAX_NUM_TKZs-1); otherwise, the MS shall set this field to ‘0’.

[0306] TKZ_REPORT—Tracking zone report indicator.

[0307] The MS shall set this field to ‘1’ if the Radio Environment Report Message is sent for tracking zone report; otherwise, the MS shall set this field to ‘0’.

[0308] The Capability Information record identifies whether the following optional or MOB_P_REV dependent features are supported by the MS. The format of the indicator message is shown in Table XII.

TABLE XII
Type-Specific Field Length (bits)
PDCH_CHM_SUPPORTED  1
RER_SUPPORTED       1
TKZ_SUPPORTED       1
RESERVED            0-7 (as needed)

[0309] In Table XII,

[0310] RER_SUPPORTED—Radio environment reporting supported indicator.

[0311] The MS shall set this field to ‘1’ if it supports radio environment reporting on the R-CSCH; otherwise, the MS shall set this field to ‘0’.

[0312] TKZ_SUPPORTED—Tracking zone supported indicator.

[0313] The MS shall set this field to ‘1’ if it supports tracking zone reporting on the R-CSCH; otherwise, the MS shall set this field to ‘0’.

[0314] MSG_TAG: ESPM—The format of the Extended System Parameters Message (ESPM)is shown in Table XIII.

TABLE XIII
Field           Length (bits)
NUM_PDCCH       0 or 3
NUM_PDCCH+1 occurrences of the following record:
{(NUM_PDCCH+1)
FOR_PDCCH_WALSH 0 or 6
}(NUM_PDCCH+1)
TKZ_SUPPORTED   1
TKZ_ID          0 or 8

[0315] In Table XIII,

[0316] TKZ_SUPPORTED—Tracking zone supported indicator.

[0317] The BTS shall set this field to ‘1’ if the tracking zone is supported; otherwise, the BTS shall set this field to ‘0’.

[0318] TKZ_ID—Tracking zone identifier.

[0319] If TKZ_SUP is set to ‘1’, the BTS shall set this field to its tracking zone identifier, otherwise, the BTS shall omit this field.

[0320] MSG_TAG:A41SPM—The format of the ANSI-41 System Parameters Message (A41SPM) is shown in Table XIV.

TABLE XIV
Field             Length (bits)
PILOT_PN          9
CONFIG_MSG_SEQ    6
SID               15
NID               16
PACKET_ZONE_ID    8
REG_ZONE          12
SIG_INTEGRITY_SUP 0 or 8
TKZ_SUPPORTED     1
TKZ_ID            0 or 8

[0321] In Table XIV,

[0322] SIG_INTEGRITY_SUP—Signaling integrity algorithm supported by the BTS.

[0323] If MSG_INTEGRITY_SUP is set to ‘1’, the BTS shall set this field as follows; otherwise, the BTS shall omit this field.

[0324] The BTS shall set this field to indicate the supported message integrity algorithms in addition to the default integrity algorithm.

[0325] The BTS shall set each subfield to ‘1’ if the corresponding message integrity algorithm is supported by the BTS; otherwise, the BTS shall set the subfield to ‘0’.

[0326] The BTS shall set the RESERVED subfield to ‘00000000’.

[0327] TKZ_SUPPORTED—Tracking zone supported indicator.

[0328] The BTS shall set this field to ‘1’ if the tracking zone is supported; otherwise, the BTS shall set this field to ‘0’.

[0329] TKZ_ID—Tracking zone identifier.

[0330] If TKZ_SUP is set to ‘1’, the BTS shall set this field to its tracking zone identifier; otherwise, the BTS shall omit this field.

[0331] MSG_TAG: ERM—The format of the Extended Release Message (ERM) is shown in Table XV.

TABLE XV
Field                   Length (bits)
RER_INFO_INCL           1
MAX_NUM_RER_IDX         0 or 3
RER_TIME                0 or 3
RER_TIME_UNIT           0 or 2
MAX_RER_PILOT_LIST_SIZE 0 or 3
TKZ_INFO_INCL           1
MAX_NUM_TKZ_IDX         0 or 3
TKZ_UPDATE_PRD          0 or 4
TKZ_LIST_LEN            0 or 4
TKZ_TIMER               0 or 8

[0332] In Table XV,

[0333] MAX_RER_LIST_SIZE—Maximum number of pilots to maintain in RER_PILOT_LIST.

[0334] If RER_INFO_INCL is set to ‘0’, the BTS shall omit this field; otherwise, the BTS shall include this field and set it as follows:

[0335] The BTS shall set this field to the maximum number of pilots other than the Active Set pilot that the MS is to maintain in RER_PILOT_LIST. The BTS shall set this field to a value in the range 0 to 5 inclusive.

[0336] TKZ_INFO_INCL—Tracking zone reporting information included indicator.

[0337] If USE_EXT_CH_IND is equal to ‘0’ and CH_IND is equal to ‘111’, or the physical channels indicated by the two least significant bits of CH_IND includes all the physical channels (FCH, DCCH, or both) currently being processed by the MS, the BTS shall set this field as follows:

[0338] If the tracking zone reporting related fields are included in this message, the BTS shall set this field to ‘1’; otherwise, the BTS shall set this field to ‘0’.

[0339] Otherwise, the BTS shall set this field to ‘0.

[0340] MAX_NUM_TKZ_IDX—Maximum number of tracking zone reporting index.

[0341] If the tracking zone reporting information included indicator is set to ‘0’, the BTS shall omit this field;

[0342] otherwise, the BTS shall include this field and set it as follows:

[0343] The BTS shall set this field to the maximum number of tracking zone reports that the MS is allowed to transmit, expressed as 2MAX—NUM—TKZ—IDX where 0≦MAX_NUM_TKZ_IDX≦6. If the MS is allowed to transmit an unlimited number of tracking zone reports, then the BTS shall set this field to ‘111’.

[0344] TKZ_UPDATE_PRD—Tracking zone update period.

[0345] If the tracking zone reporting information included indicator is set to ‘0’, the BTS shall omit this field;

[0346] otherwise, the BTS shall include this field and set it as follows:

[0347] The BTS shall set this field such that the desired tracking zone update timer value is 2TKZ—UPDATE—PRD+6 seconds. If the value of the timer is infinite, then the BTS shall set this field to ‘1111’.

[0348] TKZ_LIST_LEN—Tracking zone list length.

[0349] If the tracking zone reporting information included indicator is set to ‘0’, the BTS shall omit this field; otherwise, the BTS shall include this field and set it as follows:

[0350] The BTS shall set this field to the length of the tracking zone list minus one.

[0351] TKZ_TIMER—tracking zone timer.

[0352] If the tracking zone reporting information included indicator is set to ‘0’, the BTS shall omit this field; otherwise, the BTS shall include this field and set it as follows:

[0353] The BTS shall set this field to the value of the tracking zone timer (in units of seconds) minus one.

[0354] The radio environment report fields are required for being set to support tracking zone reporting by the MS while in the dormant state. If P_REV_IN_USEs is greater than or equal to four, the MS shall include the radio environment report fields; otherwise, the MS shall omit the radio environment report fields. When the MS includes time-sensitive radio environment report fields in the PDU being transmitted, the MS shall set the time-sensitive radio environment report fields.

[0355] The MS shall select the NUM_ADD_PILOTS and NUM_AUX_PILOTS pilots to be reported from among the pilots monitored in the ACCESS_HO_LIST and OTHER_REPORTED_LIST, and shall include the respective records in the PDU, as a list with NUM_ADD_PILOTS and NUM_AUX_PILOTS entries, according to the following procedure (or equivalent):

[0356] The list shall be empty initially and new records shall be added consecutively from the start of the list, without duplicates, until the list contains NUM_ADD_PILOTS plus NUM_AUX_PILOTS records.

[0357] No record corresponding to the pilot in the Active Set shall be part of the list.

[0358] If FIRST_IS_ACTIVE is equal to ‘0’, a record corresponding to the common pilot shall be added to the list.

[0359] If PREVIOUS_ACTIVE_PILOTs is not NULL, a record corresponding to the pilot identified by PREVIOUS_ACTIVE_PILOTs shall be added to the list, unless already present in the list.

[0360] Records corresponding to pilots in the ACCESS_HO_LIST shall be added to the list without the encapsulated PDU exceeding max_msg_size for the channel on which the PDU will be sent.

[0361] After including records corresponding to the pilots in the ACCESS_HO_LIST, records corresponding to the pilots having the highest pilot strength relative to other pilots in the OTHER_REPORTED_LIST shall be added to the list. As many pilots as possible from the OTHER_REPORTED_LIST shall be included in the list without the encapsulated PDU exceeding max_msg_size for the channel on which the PDU will be sent.

[0362] If the PDU corresponds to a Radio Environment Report Message, and RER_ENABLED is set to YES, the MS shall generate a new RER_PILOT_LIST, which is the set of pilots that includes the Active Set pilot and the min(MAX_RER_PILOT_LIST_SIZEs, NUM_ADD_PILOTS+NUM_AUX_PILOTS) additional pilots with records included in the PDU that have the strongest pilot strength.

[0363] It should be understood that the present invention is applicable to significantly enhance third generation wireless systems such as, but not limited to, 1xEV-DO, 1xEV-DV, MC-DV and UMTS/HSDPA. 1xEV-DO has been standardized by the Telecommunication Industry Association as TIA/EIA/IS-856, “CDMA2000, High Rate Packet Data Air Interface Specification”. 1xEV-DV provides integrated voice and simultaneous high-speed packet data multimedia services within CDMA2000 at speeds of up to 3.09 Mbps. Relatedly, MC-DV provides integrated multi-carrier voice and simultaneous high-speed packet data multimedia services within CDMA2000. UMTS/HSDPA is High Speed Downlink Packet Access (HSDPA) within the Universal Mobile Telephone System (UMTS). The present invention can easily update the location of a dormant MS and setup fast call, while reduce paging resource utilization in wireless access networks.

[0364] Although particular embodiments of the present invention have been described in detail, it should be appreciated that numerous variations, modifications, and adaptations may be made without departing from the scope of the present invention as defined in the claims.

Claims

1. A method for determining when a location update message is sent from a mobile station (MS) to a base transceiver station (BTS) when the MS is in a dormant state, the method comprising the steps of: starting a first timer when the MS enters a dormant state; starting a second timer when the first timer reaches a predefined value T1; while the first timer is counting and prior to its reaching said predefined value T1, sending a layer 2 location update message whenever the MS performs an idle handoff indicating that the strongest pilot signal strength has changed from one sector to another sector, while the second timer is counting and prior to its reaching a predefined value T2, sending a layer 2 location update message whenever a further criterion is met; and after the second timer has reached said predefined value T2, sending no further layer 2 location update messages.

2. The method of claim 1, wherein said further criterion includes a time period.

3 The method of claim 1, wherein said further criterion includes the MS having traveled a predetermined distance since the previous location update message was sent.

4 The method of claim 1, wherein said further criterion includes counting a predefined number of idle handoffs.

5 The method of claim 1, further comprising predefining the starting value for the first timer to said predefined value T1.

6. The method of claim 1, further comprising predefining the starting value of the second timer to said predefined value T2.

7. The method of claim 4, further comprising predefining the starting value of the second timer to said predefined value T2.

8. A method for defining the region of a wireless network in which to page a dormant mobile station (MS) when the network determines that data is to be sent to that dormant MS, the method comprising the steps of: starting a first timer when the MS enters a dormant state; starting a second timer when the first timer reaches a predefined value T1; while the first timer is counting and prior to its reaching said predefined value T1, sending an MS page to the sector indicated by the most recent layer 2 location update message received from the MS; while the second timer is counting and prior to its reaching a predefined value T2, sending an MS page to the sectors surrounding the sector indicated in the most recently received layer 2 location update message consistent with the further criterion being used to trigger a location update messages being sent from the MS; and after the second timer has reached said predefined value T2, sending an MS page to all network sectors.

9. The method of claim 8, wherein said further criterion includes a time period.

10 The method of claim 8, wherein said further criterion includes the MS having traveled a predetermined distance since the previous location update message was sent.

11 The method of claim 8, further comprising predefining the starting value for the first timer to said predefined value T1.

12. The method of claim 8, further comprising predefining the starting value of the second timer to said predefined value T2.

13. The method of claim 11, further comprising predefining the starting value of the second timer to said predefined value T2.

14 The method of claim 8, wherein said further criterion includes counting a predefined number of idle handoffs

15. The method of claim 1, wherein said layer 2 location update message includes identification of the two strongest pilot signals being received by the MS.

16. A method for determining when a location update message needs to be sent from an MS to a base transceiver station (BTS) when the MS is in a dormant state, the method comprising the steps of: determining if the MS has moved physically from one geographic region to another region served by a cell sector; and sending a location update message to the network servicing the MS indicating that the two strongest pilot signals are received by the MS.

17. The method of claim 16, wherein the step of determining includes the step of: determining if the MS has moved physically outside the geographic region served by a plurality of cell sectors defined in a sub-packet zone received previously from the network servicing the MS.

18. The method of claim 16, wherein the step of determining includes the step of: determining if the MS has moved physically into the geographic region served by a cell sector not identified in a list of cell sectors in a sub-packet zone received previously from the network servicing the MS.

19. The method of claim 16, further comprising providing a delay between the determining step and the sending step whereby ping-ponging between sub-packet zones in prevented.

20. The method of claim 16, wherein the location update message is transmitted as a layer 2 message.

21. The method of claim 1, wherein the step of sending a layer 2 location update message while the first timer is counting includes the step of: sending by the MS to the BTS a layer 2 location update message containing a message type and an MS identifier, whereby the network updating the location of the MS.

22. The method of claim 21, further comprising the step of: in response to the layer 2 location update message from the MS, sending by the BTS to the MS a location update acknowledgement message containing a message type and an MS identifier.

23. The method of claim 1, further comprising the steps of: sending by the MS in the dormant state to the BTS a reconnect message containing a message type and an MS identifier; and sending by the BTS to the MS a channel assignment message, whereby the MS initiates an MS's dormant to active state transition.

24. The method of claim 1, further comprising the steps of: sending by the MS to the BTS a layer 2 location update message containing a message type and an MS identifier; sending by the BTS to the MS a location update acknowledgement message containing a message type and an MS identifier; and sending by the BTS to the MS a message informing MS's active set, wherein the BTS initiates an MS's dormant to active state transition.

25. The method of claim 1, further comprising the steps of: sending by the MS to the BTS a layer 2 location update message containing a message type and an MS identifier; sending by the BTS to the MS a location update acknowledgement message containing a message type and an MS identifier, sending by the BTS to the MS a message informing MS's active set; sending by the BTS to the MS a data burst message; and sending by the MS to the BTS a data burst acknowledgement message containing a message type and an MS identifier.

26. A method for tracking zone update to enable a communication network to page a mobile station (MS) in a smaller area, zones relating to base station controllers (BSCs) that control communications among the BTSs and the MSs, the zones being further defined as smaller zones that are registered for zone tracking, the method comprising the steps of: defining the size of the tracking zones; defining the zones of the BTSs; broadcasting tracking zone identifiers; and paging MSs in the tracking zones.

27. The method of claim 26, wherein the step of defining the zones of the BTSs includes the step of assigning the same value to the BTSs in the same tracking zone;

28. The method of claim 26, further comprising the step of reporting by the MS on change of location in the tracking zone.

29. The method of claim 28, wherein the step of reporting includes the step of reporting the location change on R-CSCH.

30. The method of claim 26, wherein the information on the performing of the tracking zone update are defined by values.

31. The method of claim 30, wherein the values are defined for: the tracking zone identifier; the tracking zone list which is a list of most recent tracking zone identifier received by the MS; the number of tracking zone identifier to be maintained in the tracking zone list; the maximum number of Radio Environment Report Messages that the MS is permitted to transmit before disabling tracking zone reporting; and the BTS's support of tracking zone reporting indicator.

32. The method of claim 26, wherein the tracking zone update is performed in the MS's dormant state, the method further comprising the step of: performing paging channel supervision when the MS enters the dormant state from the MS initialization state.

33. The method of claim 26, further comprising the steps of: upon entering the MS dormant state from the MS control on the Traffic Channel state, performing by the MS, if the tracking zone update is enabled and the tracking zone timer is not enabled, initializing the tracking zone list with the length of the number of the tracking zone identifier and adding the tracking zone identifier to the tracking zone list; setting the tracking zone update timer at a certain value; and enabling the tracking zone update timer.

34. The method of claim 26, further comprising the steps of performing by the MS, if the tracking zone update is enabled, if the tracking identifier is not equal to any entry in the tracking zone list, sending a Radio Environment Report Message by performing the Mobile Station Message Transmission Operation in an update overhead information substate; if the tracking zone update timer of any entry in the tracking zone list has expired, deleting that entry; and if the tracking zone update timer expires, disabling the tracking zone update timer to disable the tracking zone update.

35. The method of claim 26, further comprising the step of: enabling the tracking zone update at a different time than the radio environment report.

36. The method of claim 35, wherein the step of enabling includes the steps of performing by the MS, upon expiration of the radio environment report timer, if the tracking zone reporting information included indicator is equal to “1”: enabling the tracking zone update; initializing the tracking zone list with the length of the number of tracking zone identifier and adding the tracking zone identifier to the tracking zone list; setting the tracking zone update timer at a certain value; and enabling the tracking zone update timer.

37. The method of claim 32, further comprising the steps of performing by the MS, in response to an Extended System Parameters Message received on the Paging Channel, storing the MS initiated position location determination supported indicator; if the MS supports tracking zone, storing the tracking zone supported indicator; if the tracking zone update is enabled and the tracking zone update timer is not enabled, initializing the tracking zone list with the length of the number of tracking zone identifier and adding the tracking zone identifier to the tracking zone list; setting the tracking zone update timer to a certain value; and enabling the tracking zone update timer.

38. The method of claim 26, further comprising the steps of performing by the MS: if the MS supports tracking zone, storing the tracking zone supported indicator, if the indicator is equal to ‘1’, storing the tracking zone identifier; if the tracking zone update is enabled and the tracking zone update timer is not enabled, performing: initializing the tracking zone list with the length of the number of the tracking zone identifier and adding the tracking zone identifier to the tracking zone list; setting the tracking zone update timer to a certain value; and enabling the tracking zone update timer.

39. The method of claim 26, wherein: the MS supports the Mobile Station Message Transmission Operation, the operation being performed when the user directs the MS to transmit a Data Burst Message, or when the MS detects a change in the hook status since the last time when the MS sent hook status information; and the MS supports the Device Information Message on the R-CSCH, or when the MS detects that a Radio Environment Report Message is required to be transmitted on the R-CSCH, wherein when the MS detects that a Radio Environment Report Message is required to be transmitted on the R-CSCH, the method includes the steps of performing by the MS: if RER_ENABLED is set to YES, entering the Update Overhead Information Substate of the System Access State with a radio environment report indication within a certain period of time; otherwise, if the tracking zone update is enabled, entering the Update Overhead Information Substate of the System Access State with a tracking zone report indication within a certain period of time.

40. The method of claim 26, further comprising the step of updating the information wherein if the Updated Overhead Information Substate is entered with a tracking zone report indication, the MS enters the Mobile Station Message Transmission Substate with a tracking zone report indication.

41. The method of claim 26, wherein in the Mobile Station Message Transmission Substate, the MS sends a Data Burst Message, a Device Information Message, or a Radio Environment Report Message, wherein the method includes the steps of performing by the MS; upon entering the Mobile Station Message Transmission Substate with a radio environment report indication, transmitting the Radio Environment Report Message to the BTS; if RER_ENABLED is set to NO and the tracking zone reporting information included indicator is equal to ‘1’, enabling the tracking zone update; initializing the tracking zone list with the length of the number of tracking zone identifier and adding the tracking zone identifier to the tracking zone list; setting the tracking zone update timer to a certain value; and enabling the tracking zone update timer, if the MS enters the Mobile Station Message Transmission Substate with a tracking zone report indication, transmitting the Radio Environment Report Message to the BTS; if the MS receives confirmation of delivery of Radio Environment Report Message, adding the tracking zone update identifier to the tracking zone list and starting the tracking zone update timer for the tracking zone update identifier, wherein the tracking zone list is full, the entry with active tracking zone update timer with smallest remaining tracking zone update timer value is removed from the list before adding the new entry; incrementing the tracking zone update count upon receiving confirmation of delivery, wherein if, after incrementing, the count is equal to the maximum number of Radio Environment Report Messages, the MS disables the tracking zone update timer.

42. The method of claim 26, wherein in the Traffic Channel Substate, the MS exchanges Traffic Channel frames with the BTS, the method includes the steps of performing by the MS: while in the Traffic Channel Substate, disabling the tracking zone update, setting the tracking zone list to null, and disabling the tracking zone update timer.

43. The method of claim 26, wherein in the procedure for the exiting the Release Substate, if the MS receives an Extended Release Message with the field of the tracking zone reporting information included indicator set to ‘1’ and the BTS support of tracking zone reporting indicator is equal to ‘1’, the method includes the steps of performing by the MS: setting the tracking zone count to 0; and storing the values of: the number of the tracking zone identifier to be maintained in the tracking zone list; the tracking zone update timer; the maximum allowed number of tracking zone reports; and the tracking zone update period; if RER_INFO_INCL is equal to ‘0’, enabling the tracking zone update; if RER_INFO_INCL is equal to ‘1’, setting the tracking zone reporting information included indicator.

44. The method of claim 39, wherein the Mobile Station Message Transmission Operation supported by the MS, the method further comprising the step of: providing on the R-CSCH messages containing the Radio Environment Report Message.

45. The method of claim 44, wherein the step of providing includes the step of: providing the Radio Environment Report Message containing the field of the tracking zone report indicator and its length.

46. The method of claim 45, wherein the step of providing includes the step of: providing the Radio Environment Report Message containing the field of the tracking zone report indicator of one bit.

47. The method of claim 46, further comprising the steps of: setting the field to ‘1’ if the Radio Environment Report Message is sent for tracking zone report; and otherwise, setting the field to ‘0’.

48. The method of claim 44, further comprising the step of: providing a message field containing: a radio environment reporting supported indicator; and a tracking zone supported indicator.

49. The method of claim 48, wherein the step of providing includes the step of: setting the field of the tracking zone supported indicator to ‘1’ if it supports tracking zone reporting on the R-CSCH; and otherwise, setting the filed to ‘0’.

50. The method of claim 44, further comprising the step of: providing an Extended System Parameters Message containing fields of a tracking zone supported indicator and a tracking zone identifier.

51. The method of claim 50, wherein the step of providing includes the step of: providing an Extended System Parameters Message containing fields of a tracking zone supported indicator of one bit and a tracking zone identifier of zero or eight bits

52. The method of claim 51, wherein the BTS sets the field of the tacking zone supported indicator to ‘1’ if the tracking zone is supported and otherwise to ‘0’.

53. The method of claim 50, wherein the BTS sets the field of the tacking zone identifier to ‘1’ if the field of the tacking zone supported indicator is set to ‘1’ and otherwise, the BTS omits the field of the tracking zone identifier.

54. The method of claim 44, further comprising the step of: providing an ANSI-41 System Parameters Message containing fields of a tracking zone supported indicator and a tracking zone identifier.

55. The method of claim 54, wherein the step of providing includes the step of: providing an ANSI-41 System Parameter Message containing fields of a tracking zone supported indicator of one bit and a tracldng zone identifier of zero or eight bits.

56. The method of claim 54, wherein the BTS sets the field of the tracking zone supported indicator to ‘1’ if the tracking zone is supported and otherwise, the BTS sets the field of the tracking zone supported indicator to ‘0’.

57. The method of claim 54, wherein if the field of the tracking zone supported indicator is set to ‘1’ the BTS sets the field of the tracking zone identifier to its tracking zone identifier and otherwise, the BTS omits the field of the tracking zone identifier.

58. The method of claim 44, further comprising the step of: providing an Extended Release-Message containing fields of a tracking zone reporting information included indicator, a maximum number of tracking zone reporting index, a tracking zone update period, a tracking zone list length and a tracking zone timer.

59. The method of claim 58, wherein the step of providing includes the step of: providing an Extended Release Message containing fields of a tracking zone reporting information included indicator of one bit, a maximum number of tracking zone reporting index of zero or three bits, a tracking zone update period of zero or four bits, a tracking zone list length of zero or four bits and a tracking zone timer of zero or eight bits.

60. The method of claim 58, further comprising the steps of performing by the BTS based on the channel indication bits of channels processed by the MS: setting the field of the racking zone reporting information included indicator to ‘1’ if the tracking zone reporting related fields are included in the extended release message and otherwise to ‘0’.

61. The method of claim 58, wherein if the tracking zone reporting information included indicator is set to ‘0’, the BTS omits the field of the maximum number of tracking zone reporting index and otherwise, the BTS includes the field of the maximum number of tracking zone reporting index and set it as follows: the BTS sets the field of the maximum number of tracking zone reporting index to the maximum number of tracking zone reports that the MS is allowed to transmit, expressed as 2MAX—NUM—TKZ—IDX where 0≦MAX_NUM_TKZ_IDX≦6, wherein if the MS is allowed to transmit an unlimited number of tracking zone reports, then the BTS sets the field of the maximum number of tracking zone reporting index to ‘111’.

62. The method of claim 58, wherein if the tracking zone reporting information included indicator is set to ‘0’, the BTS omits the field of the racking zone update period; and otherwise, the BTS includes the field of the racking zone update period and set it as follows: the BTS sets the field of the racking zone update period such that the desired tracking zone update timer value is 2TKZ—UPDATE—PRD+6 seconds, wherein the value of the timer is infinite, then the BTS sets the field of the racking zone update period to ‘1111’.

63. The method of claim 58, wherein if the tracking zone reporting information included indicator is set to ‘0’, the BTS omits the filed of the tracking zone list length; and otherwise, the BTS includes the filed of the tracking zone list length and set it as follows: the BTS sets the filed of the tracking zone list length to the length of the tracking zone list minus one.

64. The method of claim 58, wherein if the tracking zone reporting information included indicator is set to ‘0’, the BTS omits the filed of the tracking zone timer; and otherwise, the BTS includes the filed of the tracking zone timer and sets it as follows: the BTS sets the filed of the tracking zone timer to the value of the tracking zone timer (in units of seconds) minus one.

65. The method of claim 44, wherein if the PDU on the R-CSCH corresponds to a Radio Environment Report Message and RER_ENABLED is set to YES, the MS generates a new set of pilots that includes the Active Set pilot and additional pilots with records included in the PDU that have the strongest pilot strength.

66. A system for tracking zone updates to a communication network to page a mobile station (MS) in a smaller area including zones relating to base station controllers (BSCs) that control communications among the BTSs and the MSs, the zones being further defined as smaller zones that are registered for zone tracking, the system comprising: means for defining the size of the tracking zones; means for defining the zones of the BTSs; means for broadcasting tracking zone identifiers; and means for paging MSs in the tracking zones.

67. The system of claim 66, wherein the means for defining the zones of the BTSs includes means for assigning the same value to the BTSs in the same tracking zone.

68. The system of claim 66, further including means for reporting by the MS on change of location in the tracking zone.

69. The system of claim 66, wherein the information on the performing of the tracking zone update are defined by values, said values being defined for: the tracking zone identifier; the tracking zone list which is a list of most recent tracking zone identifier received by the MS; the number of tracking zone identifier to be maintained in the tracking zone list; the maximum number of Radio Environment Report Messages that the MS is permitted to transmit before disabling tracking zone reporting; and the BTS's support of tracking zone reporting indicator.

70. A mobile station (MS) for communicating with a base transceiver station (BTS) and a base station controller (BSC) in wireless communication system, the MS in a dormant state sending a location update message, the MS comprising: means for starting a first timer when the MS enters a dormant state; means for starting a second timer when the first timer reaches a predefined value T1; means for sending, while the first timer is counting and prior to its reaching said predefined value T1, a layer 2 location update message whenever the MS performs an idle handoff indicating that the strongest pilot signal strength has changed from one sector to another sector; means for sending, while the second timer is counting and prior to its reaching a predefined value T2, a layer 2 location update message whenever a further criterion is met; and means for sending, after the second timer has reached said predefined value T2, no further layer 2 location update messages.

71. The MS of claim 70, further including means for predefining the starting value for the first timer to said predefined value T1.

72. The method of claim 70, further including means for predefining the starting value of the second timer to said predefined value T2.

73. The MS of claim 70, further including means for sending the BTS a layer 2 location update message containing a message type and an MS identifier, whereby the network updating the location of the MS.

74. A communication network comprising base station controllers (BSCs) and base transceiver stations (BTSs) that communicate with mobile stations (MSs) in wireless communication system, the network paging a dormant MS when the network determines that data is to be sent to that dormant MS, the MS comprising: means for starting a first timer when the MS enters a dormant state; means for starting a second timer when the first timer reaches a predefined value T1; means for sending, while the first timer is counting and prior to its reaching said predefined value T1, a layer 2 location update message whenever the MS performs an idle handoff indicating that the strongest pilot signal strength has changed from one sector to another sector; means for sending, while the second timer is counting and prior to its reaching a predefined value T2, a layer 2 location update message whenever a further criterion is met; and means for sending, after the second timer has reached said predefined value T2, no further layer 2 location update messages, wherein the BTS includes: means for receiving the layer 2 location update message; means for sending a location update acknowledgement message to the MS.

75. The communication network of claim 74, wherein: the MS further includes means for sending the BTS a layer 2 location update message containing a message type and an MS identifier, whereby the network updating the location of the MS; and the BTS further include means for sending the MS a location update acknowledgment message containing a message type and an MS identifier.

76. The communication network of claim 74, wherein: the MS in the dormant state includes means for sending the BTS a reconnect message containing a message type and an MS identifier; and the BTS includes the MS a channel assignment message, whereby the MS initiates an MS's dormant to active state transition.

77. The communication network of claim 74, wherein: the MS includes means for sending the BTS a layer 2 location update message containing a message type and an MS identifier; and the BTS includes: means for sending the MS a location update acknowledgement message containing a message type and an MS identifier; and means for sending the MS a message informing MS's active set, wherein the BTS initiates an MS's dormant to active state transition.

78. The communication network of claim 74, wherein: the MS includes means for sending the BTS a layer 2 location update message containing a message type and an MS identifier; and the BTS includes: means for sending the MS a location update acknowledgement message containing a message type and an MS identifier; and means for sending the MS a message informing MS's active set; and means for sending the MS a data burst message, wherein the MS further includes means for sending the BTS a data burst acknowledgement message containing a message type and an MS identifier.

79. A method for updating locations of mobile stations (MSs) in a dormant state in a wireless communication network wherein a Base Station Controller controls various operating aspects of the network and a Base Transceiver Station provides communication links between MSs and between the MSs and a wireline telephone network, the method comprising the steps of: starting a timer when the MS enters a dormant state; while the timer is counting and prior to its reaching a predefined value T1, sending by the MS to the BTS, whenever the MS performs an idle handoff, a message containing information on the location of the MS, the information being associated with the sector of the MS, thereby the network updating the location of the dormant MS at the sector level; when the timer's count reaches the value T1, restarting the timer to count until it reaches a predetermined value T2; while the timer is counting and prior to its reaching the predefined value T2, sending by the MS to the BTS a message containing information on the location of the MS, the information being associated with the area of the MS, the area being greater than the sector, thereby the network updating the location of the dormant MS at the area level; when the timer's count reaches the value T2, sending no further message of location to the BTS.

80. The method of claim 79, further including the step of: after the timer's count reaches the value T2, sending an MS page to all network sectors.

81. The method of claim 79, wherein: the step of sending a message prior to T1 includes the step of sending a layer 2 message containing a message type and an MS identifier; and the step of sending a message prior to T2 includes the step of sending a layer 2 message containing a message type and an MS identifier.