BR112012000354B1 - method for execution by a mobile station in a mobile communications network, mobile station and method for execution by a base station in a mobile communications network - Google Patents

Abstract

MEDIA ACCESS CONTROL FOR WIRELESS SYSTEM. A METHOD FOR RUNNING BY A MOBILE STATION (MS) IN A MOBILE COMMUNICATIONS NETWORK, THE METHOD COMPRISING: RECEIVING A FIRST MS IDENTIFIER FROM THE NETWORK DURING A RANGE CALCULATION OPERATION INVOLVING MS; THE USE OF THE FIRST MS IDENTIFIER FOR THE EXTRACTION OF THE CONTENT OF AT LEAST ONE MESSAGE RECEIVED FROM THE NETWORK DURING SUCH RANGE CALCULATION OPERATION; THE USE OF A SECOND MS IDENTIFIER, DIFFERENT FROM THE FIRST MS IDENTIFIER, TO EXTRACT THE CONTENT OF AT LEAST ONE MESSAGE RECEIVED FROM THE NETWORK AFTER SUCH RANGE CALCULATION OPERATION IS COMPLETED. ALSO, A METHOD FOR EXECUTION BY THE BASE STATION, COMPRISING: THE EXTRACTION OF A FIRST MESSAGE INTENDED FOR MS, THE FIRST MESSAGE INCLUDING A FIRST IDENTIFIER FOR USE BY MS DURING A RANGE CALCULATION OPERATION; THE DETERMINATION THAT SUCH REACH CALCULATION OPERATION IS COMPLETED; THE EXTRACTION OF A SECOND MESSAGE INTENDED FOR MS, THE SECOND MESSAGE INCLUDING A SECOND IDENTIFIER FOR USE BY MS IN A SUBSEQUENT COMMUNICATION WITH THE NETWORK.

Description

CROSS REFERENCE ON RELATED REQUEST

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 61/223,134, filed July 6, 2009, which is hereby incorporated by reference in its entirety.

[0002] This order is a continuation in part of the non-provisional order (serial number to be determined) resulting from a conversion under 37 C.F.R. § 1.53(c)(3) of US Provisional Patent Application No. 61/223,134, filed July 6, 2009, which claims the benefit of US Provisional Patent Application No. 61/078,570, filed July 7 of 2008.

TECHNICAL FIELD

[0003] This application relates to wireless communication techniques.

BACKGROUND OF THE INVENTION

[0004] Draft System Description Document, IEEE 802.16m-08/003r1, dated 15 April 2008, states that: “This standard [802.16m] amends the IEEE WirelessMAN-OFDMA 802.16 specification to the provision of an advanced air interface for operation in licensed bands. It fits the cellular layer requirements of advanced IMT next-generation mobile networks. This amendment provides ongoing support for legacy WirelessMAN-OFDMA equipment... The purpose of this standard is to provide necessary performance improvements to support future advanced services and applications, such as those described in the ITU in the ITU-RM Report .2072."

[0005] Also, the IEEE 802.16m System Requirements Document (IEEE 802.16m-07/002r4) states that: “The processing time, including the processing time for control signaling, as well as the related processing time a carrier data transfer, for all applications, should be reduced as much as practicable without compromising overall performance and ensuring proper support of system resources.”

SUMMARY OF THE INVENTION

[0006] According to a first broad aspect, the present invention seeks to provide a method for execution by a mobile station in a mobile communications network, the method comprising: receiving a first mobile station identifier from the network during a range calculation operation involving the mobile station; using the first mobile station identifier for extracting the content of at least one message received from the network during said range calculation operation; using a second mobile station identifier, different from the first mobile station identifier, for extracting content from at least one message received from the network after said range calculation operation is completed.

[0007] According to a second broad aspect, the present invention seeks to provide a mobile station comprising: a receiving circuit configured to receive messages from a network, at least one of the messages received during a range calculation operation and comprising a first mobile station identifier; a processing entity configured to extract the content of at least one message received from the network during said range calculation operation, based on the first mobile station identifier, and to extract the content of at least one message received to from the network, after said range calculation operation is completed, based on a second mobile station identifier different from the first mobile station identifier.

[0008] According to a third broad aspect, the present invention seeks to provide a computer readable storage medium comprising computer readable instructions which, when executed by a computing entity in a mobile station causes the mobile station to: extract the content of at least one message received from a network during a range calculation operation based on the use of a first mobile station identifier; and extracts the content of at least one message received from the network, after said range calculation operation is completed, based on the use of a second mobile station identifier different from the first mobile station identifier.

[0009] According to a fourth broad aspect, the present invention seeks to provide a mobile station comprising: a means for receiving messages from a network, at least one of the messages received during a range calculation operation and comprising a first mobile station identifier; means for extracting the content of at least one message received from the network during said range calculation operation, based on the first mobile station identifier; and means for extracting the content of at least one message received from the network after said range calculation operation is completed, based on a second mobile station identifier different from the first mobile station identifier.

[00010] According to a fifth broad aspect, the present invention aims to provide a method for execution by a base station in a mobile communications network, comprising: extracting a first message destined for a mobile station, the first message including a first mobile station identifier for use by the mobile station during a range calculation operation; determining that said range calculation operation is complete; extracting a second message to the mobile station, the second message including a second mobile station identifier for use by the mobile station in subsequent communication with the network.

[00011] According to a broad sixth aspect, the present invention aims to provide a base station comprising: a transmission circuit configured to extract messages destined for the mobile station; a processing entity configured to determine when a range calculation operation involving a mobile station is completed, for inserting into a first of the messages transmitted during the range calculation operation a first mobile station identifier for use by the mobile station during the said range calculation operation, and for inserting in a second of the messages a second mobile station identifier for use by the mobile station, after said range calculation operation is completed.

[00012] According to a broad seventh aspect, the present invention aims to provide a computer readable storage medium comprising computer readable instructions which, when executed by a computing entity at a base station, make causing the base station to: insert in a first message to a mobile station involved in a range calculation operation a first mobile station identifier for use by the mobile station during said range calculation operation; and inserting into a second message destined for the mobile station a second mobile station identifier for use by the mobile station, after said range calculation operation is completed.

[00013] According to an eighth broad aspect, the present invention aims to provide a base station comprising: means for extracting messages destined for a mobile station; means for determining when a range calculation operation involving a mobile station is completed; means for inputting into a first of the messages transmitted during the range calculation operation a first mobile station identifier for use by the mobile station during said range calculation operation; and means for inserting into a second of the messages a second mobile station identifier for use by the mobile station after said range calculation operation is completed.

[00014] According to a ninth aspect, the present invention seeks to provide a method for data transmission, comprising: accessing a memory to obtain an amount of data associated with a service flow established with a recipient and to be transmitted to him; memory access to obtain control information characterizing the service flow; formulating a datagram by placing at least some of the data in a datagram payload and placing in a datagram header the control information characterizing the service flow, where the control information characterizing the service flow occupies less than sixteen bits of header; modulating a radio frequency signal with the datagram and releasing the radio frequency signal wirelessly.

[00015] Aspects and features of the present application will become apparent to those of ordinary skill in the art upon a review of the following description of specific modalities of an exhibit in conjunction with associated drawing figures and appendices.

BRIEF DESCRIPTION OF THE DRAWINGS

[00016] The embodiments of the present application will now be described, by way of example only, with reference to the associated drawing figures, in which like reference numerals are used in different figures to denote similar elements.

[00017] Figure 1 is a block diagram of a cellular communication system.

[00018] Figure 2 is a block diagram of an example base station that could be used to implement some modalities of the present application.

[00019] Figure 3 is a block diagram of an example wireless terminal that could be used to implement some of the embodiments of the present application.

[00020] Figure 4 is a block diagram of an example relay station that could be used for implementing some modalities of the present application.

[00021] Figure 5 is a block diagram of a logical decomposition of an example OFDM transmitter architecture that could be used for implementing some modalities of the present application.

[00022] Figure 6 is a block diagram of a logical decomposition of an example OFDM receiver architecture that could be used for implementing some modalities of the present application.

[00023] Figure 7 is Figure 1 of IEEE 802.16m-08/003r1, an example of a general network architecture.

[00024] Figure 8 is figure 2 of IEEE 802.16m-08/003rl, a relay station in a general network architecture.

[00025] Figure 9 is figure 3 of IEEE 802.16m-08/003rl, a system reference model.

[00026] Figure 10 is figure 4 of IEEE 802.16m-08/003rl, a protocol structure of IEEE 802.16m.

[00027] Figure 11 is Figure 5 of IEEE 802.16m-08/003rl, an IEEE 802.16m MS/BS data plane processing flow.

[00028] Figure 12 is figure 6 of IEEE 802.16m-08/003rl, an IEEE 802.16m MS/BS control plane processing flow.

[00029] Figure 13 is figure 7 of IEEE 802.16m-08/003rl, generic protocol architecture for multi-carrier system support.

[00030] Figure 14 is a flowchart showing a message flow between a base station and a mobile station involved in a range calculation operation with it, in the case of an initial network entry, according to a non-limiting modality specific of the present invention.

[00031] Figure 15 conceptually illustrates a header of a media access control protocol data unit (MAC PDU).

[00032] Figure 16 shows a variant of the flowchart in Figure 14.

[00033] Figure 17 shows another variant of the flowchart in Figure 14.

[00034] Figure 18 is a flowchart showing a message flow between a base station and a mobile station involved in a range calculation operation with it, in the case where the mobile station re-enters the network from a inactive state, according to a specific non-limiting embodiment of the present invention.

[00035] Figure 19 is a flowchart showing a message flow between a base station and a mobile station involved in a range calculation operation with it, in the case of a location update, according to a specific non-limiting modality of the present invention.

[00036] Figure 20 shows a state diagram of a mobile station, illustrating a number of possible states, including an initialization state, an access state, a connected state and an idle state.

[00037] Figure 21 shows in more detail how the mobile station transitions into and out of the initialization state.

[00038] Figure 22 shows in more detail how the mobile station transitions into and out of the access state.

[00039] Figure 23 shows in more detail how the mobile station transitions into and out of the connected state.

[00040] Figure 24 shows in more detail how the mobile station transitions into and out of the idle state.

[00041] It is to be expressly understood that the description and drawings are only for the purpose of illustrating certain embodiments of the invention and are an aid to understanding. They are not intended to be a definition of the limits of the invention.

DETAILED DESCRIPTION OF THE INVENTION

[00042] In the present exhibition, reference has been made to IEEE 802.16 and IEEE 802.16m. Below, the term “IEEE 802.16” is meant to involve versions of the IEEE Standard 802.16-, including but not limited to the IEEE Standards 802.16-2004 and -2009, while the term “IEEE 802.16m” is meant to involve versions of IEEE 802.16m-08, including, but not limited to, 802.16m-08/003r3, and /003r1 and /003r9a. All of the foregoing documents, which are hereby incorporated by reference herein, are available from IEEE, 3 Park Avenue, New York, Nyquist 10016-5997, USA, and may be consulted for additional background information. as to the context in which certain embodiments of the present invention may find application.

[00043] Referring to the drawings, figure 1 shows a base station controller (BSC) 10, which controls wireless communications in multiple cells 12, which cells are served by corresponding base stations (BSs) 14. In some configurations, each cell is further divided into multiple sectors 13 or zones (not shown). In general, each BS 14 facilitates communications with mobile stations (MSs)16, which are in cell 12 associated with the corresponding BS 14. MSs 16 may alternatively be referred to as mobile terminals, wireless stations, wireless terminals, subscriber stations , subscriber terminals, etc.

[00044] The movement of MSs 16 relative to BSs 14 results in a significant fluctuation in channel conditions. As illustrated, the BSs 14 and MSs 16 may include multiple antennas for the provision of spatial diversity for communications. In some configurations, relays (or relay stations-RSs) 15 can aid in communications between BSs 14 and MSs 16. MSs 16 can be transferred 18 from any cell 12, sector 13, zone (not shown), BS 14 or RS 15 to another cell 12, sector 13, zone (not shown), BS 14 or RS 15. In some configurations, the BSs 14 communicate with each other and with another network (such as a core network or the internet, both not shown) over a backhaul network 11. In some configurations, a BSC 10 is not required.

[00045] Referring to figure 2, an example of a BS 14 is illustrated. The BS 14 generally includes a control system 20, a baseband processor 22, a transmit circuit 24, a receive circuit 26, multiple antennas 28, and a network interface 30. The receive circuit 26 receives frequency signals from radio carrying information from one or more remote transmitters provided by MSs 16 (shown in figure 3) and RSs 15 (shown in figure 4). A low-noise amplifier and filter (not shown) can cooperate for amplifying and removing wideband interference from the signal for processing. A downconverting and digitizing circuit (not shown) will then convert the filtered received signal to an intermediate frequency or baseband signal, which is then digitized into one or more digital streams.

[00046] Baseband processor 22 processes the digitized received signal to extract the information or data bits carried in the received signal. This processing typically comprises demodulation, decoding and error correction operations. As such, baseband processor 22 is generally implemented in one or more digital signal processors (DSPs) or application-specific integrated circuits (ASICs). The received information is then sent over a wireless network via the network interface 30 or transmitted to another MS 16 served by the BS 14, directly or with the assistance of an RS 15.

[00047] On the transmit side, the baseband processor 22 receives the digitized data, which may represent voice, data or control information, from the network interface 30 under the control of the control system 20, and encodes the data for transmission. The encoded data is extracted to transmission circuit 24, where it is modulated by one or more carrier signals having a desired transmission frequency or frequencies. A power amplifier (not shown) will amplify the modulated carrier signals to a level suitable for transmission, and deliver the modulated carrier signals to antennas 28 through a combination network (not shown). Modulation and processing details are described in more detail below.

[00048] Referring to Fig. 3, an example of an MS 16 is illustrated. Similar to BS 14, MS 16 will include a control system 32, a baseband processor 34, a transmit circuit 36, a receive circuit 38, antennas 40, and a user interface circuit 42. reception 38 receives radio frequency signals carrying information from one or more BSs 14 and RSs 15. A low-noise amplifier and filter (not shown) can cooperate for the application and removal of a wideband interference from the signal for processing. A downconverting and digitizing circuit (not shown) will then downconvert the filtered received signal to an intermediate frequency or baseband signal, which is then digitized to one or more digital streams.

[00049] The baseband processor 34 processes the digitized received signal to extract the information or data bits carried in the received signal. This processing typically comprises demodulation, decoding and error correction operations. Baseband processor 34 is generally implemented in one or more digital signal processors (DSPs) and application-specific integrated circuits (ASICs).

[00050] As for the transmission, the baseband processor 34 receives the digitized data, which may represent voice, videos, data or control information, from the control system 32, which it encodes for transmission. The encoded data is extracted to transmission circuit 36, where it is used by a modulator to modulate one or more carrier signals that are at a desired transmission frequency or frequencies. A power amplifier (not shown) will amplify the modulated carrier signals to a level suitable for transmission, and deliver the modulated carrier signal to antennas 40 through a combination network (not shown). Various modulation and processing techniques available to those skilled in the art are used for a signal transmission between the mobile terminal and the base station, directly or through the relay station.

[00051] In an orthogonal frequency division multiple modulation (OFDM), the transmission band is divided into multiple orthogonal carrier waves. Each carrier wave is modulated according to the digital data to be transmitted. Due to the fact that OFDM divides the transmission bandwidth into multiple carriers, the bandwidth per carrier decreases and the modulation time per carrier increases. Since multiple carriers are transmitted in parallel, the transmission rate for digital data or symbols on any given carrier is lower than when a single carrier is used.

[00052] An OFDM modulation uses the execution of an inverse fast Fourier transform (IFFT) on the information to be transmitted. For a demodulation, performing a fast Fourier transform (FFT) on the received signal retrieves the transmitted information. In practice, the IFFT and the FFT are provided by a digital signal processing performing an Inverse Discrete Fourier Transform (IDFT) and a Discrete Fourier Transform (DFT), respectively. Therefore, the feature of OFDM modulation characterization is that orthogonal carrier waves are generated for multiple bands in a transmission channel. Modulated signals are digital signals having a relatively low transmission rate and capable of being in their respective bands. Individual carrier waves are not directly modulated by digital signals. Instead, all carrier waves are modulated at once by IFFT processing.

[00053] Orthogonal Frequency Division Multiple Access (OFDMA) is a multiple user version of the OFDM digital modulation scheme. Multiple access is achieved in OFDMA by assigning subsets of subcarriers to individual users. This allows simultaneous low data rate transmission from multiple users. Like OFDM, OFDMA employs multiple closely spaced subcarriers, but the subcarriers are divided into groups of subcarriers. Each group is called a subchannel. Subcarriers that form a subchannel need not be adjacent. In downlink, a subchannel may be intended for different receivers. In the uplink, a transmitter can be assigned one or more subchannels. A subchannel defines subchannels that can be allocated to MSs depending on their channel conditions and data requirements. Using a subchannel, in the same time frame, a BS can allocate more transmit power to user devices (MSs) with a lower SNR (Signal to Noise Ratio) and less power to user devices with a higher SNR. A subchannel also allows the BS to allocate higher power to subchannels assigned to indoor MSs resulting in better coverage in buildings. An uplink subchannel can save user device transmit power because it can concentrate power only on certain subchannels allocated to it. This power saving feature is particularly useful for battery powered user devices.

[00054] In one operation, OFDM can be used for at least one downlink (DL) transmission from BSs 14 to MSs 16. Each BS 14 is equipped with “n” transmit antennas 28 (n > 1 ), and each MS 16 is equipped with “m” 40 receiving antennas (m > 1). Notably, the respective antennas can be used for reception and transmission using duplexers or switches and are also labeled so just for clarity. (When RSs 15 are used, OFDM can be used for a downlink transmission from BSs 14 to RSs 15 and from RSs 15 to MSs 16.)

[00055] In the uplink direction, MS 16 can use OFDMA digital modulation scheme. (When RSs 15 are used, OFDMA can be used for an uplink transmission from BSs 14 to RSs 15 and from RSs 15 to MSs 16.)

[00056] It should be appreciated that the choice of OFDM on the downlink and OFDMA on the uplink is not limiting in any way, and that other modulation schemes could be used.

[00057] With reference to figure 4, an example of an RS 15 is illustrated. Similar to BS 14 and MS 16, RS 15 will include a control system 132, a baseband processor 134, a transmit circuit 136, a receive circuit 138, antennas 130 and a relay circuit 142. relay circuit 142 allows RS 15 to assist in communications between a BS 14 and MSs 16. Receive circuit 138 receives radio frequency signals carrying information from one or more BSs 14 and MSs 16. low noise and a filter (not shown) can cooperate to apply and remove a wideband interference from the signal for processing. A downconverting and digitizing circuit (not shown) will then downconvert the filtered received signal to an intermediate frequency or baseband signal, which is then digitized to one or more digital streams.

[00058] The baseband processor 134 processes the digitized received signal to extract the information or data bits carried in the received signal. This processing typically comprises demodulation, decoding and error correction operations. Baseband processor 134 is generally implemented in one or more digital signal processors (DSPs) or application-specific integrated circuits (ASICs).

[00059] As for transmission, the baseband processor 134 receives the digitized data, which may represent voice, video, data or control information, from the control system 132, which it encodes for transmission. The encoded data is extracted to transmission circuit 136, where it is used by a modulator for modulating one or more carrier signals that are at a desired transmission frequency or frequencies. A power amplifier (not shown) will amplify the modulated carrier signals to a level suitable for transmission, and deliver the modulated carrier signal to antennas 130 through a combination network (not shown). Various modulation and processing techniques available to those skilled in the art are used for a signal transmission between the mobile terminal and the base station, directly or indirectly through a relay station, as described above.

[00060] With reference to Fig. 5, a logical OFDM transmission architecture will be described. Initially, the BSC 10 will send data to be transmitted for several MSs 16 to the BS 14, either directly or with the assistance of an RS 15. The BS 14 can use the channel quality indicators (CQIs) associated with the mobile terminal for the programming the data for transmission, as well as selecting an appropriate encoding and modulation for transmitting the programmed data. The CQIs can be directly from the MSs 16 or determined in the BS 14 based on information provided by the MSs 16. In any case, the CQI for each MS 16 is a function of the degree to which the amplitude (or response) of channel varies across the OFDM frequency band.

[00061] The programmed data 44, which is a bit stream, is scrambled in a way that reduces the peak to average power ratio associated with the data using data scrambling logic 46. A cyclic redundancy check (CRC) for the scrambled data is determined and appended to the scrambled data using CRC add logic 48. Then a channel coding is performed using channel encoder logic 50 to effectively add redundancy to the data to facilitate recovery and an error correction on the MS 16. Again, the channel coding for a particular MS 16 is based on the CQI. In some implementations, channel encoder logic 50 uses known turbocoding techniques. The encoded data is then processed by rate combining logic 52 to compensate for the data expansion associated with an encoding.

[00062] Bit interleaver logic 54 systematically reorders the bits in the encoded data to minimize the loss of consecutive data bits. The resulting data bits are systematically mapped into corresponding symbols depending on the baseband modulation chosen by the mapping logic 56. A quadrature amplitude modulation (QAM) or a quadrature phase shift key modulation (QPSK) can be used, by way of example. The degree of modulation can be chosen based on the CQI of the particular mobile terminal. Symbols can be systematically reordered to further enhance the immunity of the transmitted signal to periodic data loss caused by frequency selective fading using symbol interleaver logic 58.

[00063] At this point, groups of bits have been mapped into symbols representing locations in an amplitude and phase constellation. When spatial diversity is desired, blocks of symbols are then processed by a space-time block code (STC) coder logic 60, which modifies the symbols in a way making the transmitted symbols more resistant to interference and more readily decoded into an MS 16. The STC encoder logic 60 will process the input symbols and provide "n" outputs corresponding to the number of transmit antennas 28 to the BS 14. The control system 20 and/or the baseband processor 22, as described herein with respect to Fig. 5, will provide a control signal mapping for control of an STC encoding. At this point, assume that the symbols for the “n” outputs are representative of the data to be transmitted and capable of being retrieved by the MS 16.

[00064] For the present example, assume that the BS 14 has two antennas 28 (n = 2) and the STC encoder logic 60 provides the symbol output streams. Therefore, each of the symbol streams extracted by the STC encoder logic 60 is sent to a corresponding IFFT processor 62, illustrated separately for ease of understanding. Those skilled in the art will recognize that one or more processors can be used to provide such digital signal processing, alone or in combination with other processing described herein. The IFFT processors 62 will preferably operate on the respective symbols for the provision of an inverse Fourier transform. The output of IFFT processors provides symbols in the time domain. The time domain symbols are grouped into frames, which are associated with prefix-by-prefix insertion logic 64. Each of the resulting signals is upconverted in the digital domain to an intermediate frequency and converted to an analog signal via of the digital up-conversion (DUC) and digital-to-analog (D/A) conversion circuit 66. The resulting (analog) signals are then simultaneously modulated to the desired RF frequency, amplified and transmitted via the RF circuit 68 and the antennas 28. Notably, the pilot signals known by the intended MS 16 are scattered among the subcarriers. The MS 16, which is discussed in detail below, can use the pilot signals for channel estimation.

[00065] A reference is now made to figure 6, to illustrate the reception of signals transmitted by an MS 16, directly from the BS 14 or with the assistance of RS 15. Upon the arrival of the signals transmitted in each of the antennas 40 of the MS 16, the respective signals are demodulated and amplified by a corresponding RF circuit 70. For the sake of brevity and clarity, only one of the two reception paths is described and illustrated in detail. An analog-to-digital (A/D) and downconverter circuit 72 digitizes and downconverts the analog signal for digital processing. The resulting digitized signal can be used by an automatic gain control (AGC) circuit 74 to control the gain of the amplifiers in the RF circuit 70 based on the received signal level.

[00066] Initially, the digitized signal is provided to a synchronization logic 76, which includes a coarse synchronization logic 78, which buffers several OFDM symbols and calculates an autocorrelation between two successive OFDM symbols. A resulting time index corresponding to the maximum of the correlation result determines a fine sync search window, which is used by the fine sync logic 80 for determining an accurate framing start position based on the headers. The output of fine sync logic 80 facilitates a frame acquisition by frame alignment logic 84. Proper framing alignment is important so that subsequent FFT processing provides an accurate conversion from time domain to domain frequency. The fine synchronization algorithm is based on the correlation between the received pilot signals carried by the headers and a local copy of the known pilot data. Once a frame alignment acquisition occurs, the OFDM symbol prefix is removed with the prefix removal logic 86, and the resulting samples are sent to a frequency offset correction logic 88, which compensates for the offset. frequency fluctuations caused by unmatched local oscillators in the transmitter and receiver. Synchronization logic 76 may include frequency shift and clock estimation logic 82, which is based on the headers, to aid in estimating these effects on the transmitted signal and providing these estimates to correlation logic 88 for the proper processing of OFDM symbols.

[00067] At this point, the OFDM symbols in the time domain are ready for a conversion to the frequency domain using an FFT 90 processing logic. The results are frequency domain symbols, which are sent to a frequency domain logic. processing 92. Processing logic 92 extracts the scattered pilot signal using scattered pilot extraction logic 94, determines a channel estimate based on the extracted pilot signal using channel estimate logic 96, and provides the channel responses for all subcarriers using channel reconstruction logic 98. In order to determine a channel response for each of the subcarriers, the pilot signal is essentially multiple pilot symbols which are scattered among the data symbols by all of the OFDM subcarriers in a known pattern in time and frequency. Continuing with Fig. 6, the processing logic compares the received pilot symbols with the pilot symbols that are expected on certain subcarriers at certain times to determine a channel response for the subcarriers on which the pilot symbols were transmitted. The results are interpolated to an estimate of a channel response for most if not all remaining subcarriers for which pilot symbols were not provided. The real and interpolated channel responses are used for estimating an overall channel response, which includes the channel responses for most if not all subcarriers in the OFDM channel.

[00068] Frequency domain symbols and channel reconstruction information, which are derived from the channel responses for each receive path, are provided to an STC decoder 100, which provides an STC decoding in both received paths for the recovery of transmitted symbols. The channel reconstruction information provides an equalization information to the STC decoder 100 sufficient to remove the effects of the transmission channel when processing the respective frequency domain symbols.

[00069] The retrieved symbols are put back in order using symbol interleaver logic 102 which corresponds to symbol interleaver logic 58 of the transmitter. The deinterlaced symbols are then demodulated or demapped to a corresponding bit stream using demapping logic 104. The bits are then deinterlaced using bit deinterlacing logic 106, which corresponds to bit interlacing logic 54 of transmitter architecture. The de-interlaced bits are then processed by a rate mismatch logic 108 and presented to channel decoder logic 110 for recovering the initially scrambled data and CRC checksum. Therefore, CRC logic 112 removes the CRC checksum, checks the scrambled data in the traditional way, and provides it to descramble logic 114 for descramble, using the known base station descramble code for data recovery originally broadcast 116.

[00070] In parallel with the retrieval of data 116, a CQI signal, or at least a sufficient information for creating a CQI in the BS 14 is determined and transmitted to the BS 14. As mentioned above, the CQI can be a a function of the carrier-to-noise (CR) ratio, as well as the degree to which the channel response varies across the various sub-carriers in the OFDM frequency band. For this modality, the channel gain for each subcarrier in the OFDM frequency band being used for transmitting an information is compared against one another to determine the degree to which the signal gain varies across the band. frequency of OFDM. Although numerous techniques are available for measuring the degree of variation, one technique is to calculate the standard deviation of the channel gain for each subcarrier over the entire OFDM frequency band being used for data transmission.

[00071] In some embodiments, a broadcast station may operate in a time-divided manner using only one relation or alternatively include multiple relations.

[00072] Turning now to figure 7, an example reference model is shown, which is a logical representation of a network that supports wireless communications among the mentioned BSs 14, MSs 16 and RSs 15 above, in accordance with a non-limiting embodiment of the present invention. The network reference model identifies functional entities and reference points by which interoperability is achieved between these functional entities. Specifically, the network reference model may include an MS 16, an access service network (ASN) and a connectivity service network (CSN).

[00073] ASN can be defined as a complete set of network functions necessary for the provision of radio access to a subscriber (for example, an IEEE 802.16e or an 802.16m subscriber). The ASN may comprise network elements such as one or more BSs 14 and one or more ASN gateways. An ASN can be shared by more than one CSN. ASN can provide the following functions: • Layer 1 and Layer 2 connectivity with MS 16; • The transfer of AAA messages to the subscriber's home network service provider (H-NSP) for authentication, authorization and session accounting for subscriber sessions; • Network discovery and selection of subscriber's preferred NSP; • A relay functionality for establishing a Layer 3 (L3) connectivity to the MS 16 (eg an IP address allocation); • Radio resource management.

[00074] In addition to the above functions, for a portable and mobile environment, an ASN can still support the following functions: • ASN anchored mobility; • CSN anchored mobility; • Sending a radio call; • ASN-CSN tunneling.

[00075] For its part, CSN can be defined as a set of network functions that provide IP connectivity services to the subscriber. A CSN can provide the following functions: • MS IP address and endpoint parameter allocation for user sessions; • Proxy or AAA server; • Policy and admission control based on user subscription profiles; • ASN-CSN tunneling support; • Subscriber taxation and settlement between operators; • Tunneling between CSNs for roaming; • Mobility between ASN.

[00076] CSN may provide services such as location-based services, peer-to-peer connectivity services, provisioning, authorization and/or connectivity to IP multimedia services. The CSN may further comprise network elements such as routers, proxy/AAA servers, user databases and internetwork gateway MSs. In the context of IEEE 802.16m, the CSN can be employed as part of an IEEE 802.16m NSP or as part of an incumbent IEEE 802.16e NSP.

[00077] In addition, SRs 15 can be employed for the provision of improved coverage and/or capacity. Referring to Figure 8, a BS 14 that is capable of supporting a legacy RS communicates with the legacy RS in the "legacy zone". The BS 14 is not required to provide legacy protocol support in the “16m zone”. The relay protocol design could be based on the IEEE 802-16j design, although it may be different from the IEEE 802-16j protocols used in the “legacy zone”.

[00078] Referring now to figure 9, a system reference model is shown, which applies to the MS 16 and the BS 14, and includes several building blocks, including a sub-layer of the access control common part. medium (MAC), a convergence sublayer, a security sublayer, and a physical layer (PHY).

[00079] The convergence sublayer performs a mapping of external network data received through CS SAP into MAC SDUs received by MAC CPS through MAC SAP, a classification of external network SDUs and associating them with SFID MAC and CID, payload header suppression/compression (PHS).

[00080] The security sublayer performs authentication and secure key exchange and encryption.

[00081] The physical layer performs physical layer protocols and functions.

[00082] The MAC common part sublayer is now described in greater detail. First, it will be appreciated that media access control (MAC) is connection oriented. That is, for purposes of mapping to services on MS 16 and associating varying levels of QoS, data communications are carried out in the context of “connections”. In particular, “service streams” can be provisioned when the MS 16 is installed in the system. Shortly after a MS 16 registration, connections are associated with these service flows (one connection per service flow) to provide a reference against which bandwidth is requested. Additionally, new connections can be established when a customer's service needs change. A connection defines the mapping between peer convergence processes using MAC and a service flow. The service flow defines the QoS parameters for the MAC protocol data units (PDUs) that are exchanged on the connection. Thus, service flows are integral to the bandwidth allocation process. Specifically, the MS 16 requests an uplink bandwidth on a per connection basis (implicitly identifying the service flow). Bandwidth may be granted by the BS to an MS as an aggregate of grants in response to peer connection requests from the MS.

[00083] With further reference to Fig. 10, the MAC Common Part Sublayer (CPS) is classified into Radio Resource Management and Control (RRCM) functions and Media Access Control (MAC) functions.

[00084] The RRCM functions include several function blocks that are related to radio resource functions such as: • Radio resource management • Mobility management • Network entry management • Location management • Idle mode management • System Configuration Security Management • MBS (Broadcast and Multicast service) • Connection and service flow management • Relay functions • Self-organizing •Multi-carrier

Radio Resource Management

[00085] The radio resource management block adjusts radio network parameters based on traffic load, and also includes a load control (load balancing), admission control and interference control function.

Mobility Management

[00086] The mobility management block supports functions related to an intra-RAT/inter-RAT point-to-point transfer. The mobility management block handles an intra-RAT/inter-RAT network topology acquisition, which includes advertising and metering, manages candidate neighbor target BSs/RSs and also decides whether the MS performs a point-to-point transfer operation. intra-RAT/inter-RAT point.

Network Entry Management

[00087] The network entry management block is in charge of initialization and access procedures. The network input management block can generate management messages which are needed during access procedures, ie, range calculation, basic capacity negotiation, registration, and so on.

Location Management

[00088] The location management block is in charge of supporting a location-based service (LBS). The location management block can generate messages including LBS information.

Idle Mode Management

[00089] Idle mode management block manages a location update operation during an idle mode. The idle mode management block controls an idle mode operation, and generates a radio call sending announcement message based on a radio call sending message from a radio call sending controller on the core network side.

Security Management

[00090] The security management block is in charge of authentication/authorization and key management for security communication.

System Configuration Management

[00091] The system configuration management block manages system configuration parameters, and system parameters and system configuration information for transmission to the MS.

MBS (Multicast and Wide Broadcast Service)

[00092] The MBS (Multicast and Widecast Service) block controls the management messages and data associated with a widecast and/or multicast service.

Workflow and Connection Management

[00093] The connection and service flow management block allocates "mobile station identifiers" (or station identifiers - STIDs) and "flow identifiers" (FIDs) during point-to-point access/transfer/creation procedures flow of service. Mobile station identifiers and FIDs will be discussed further below.

Relay Functions

[00094] The Relay Function Block includes functions to support multiple-hop relay mechanisms. Functions include procedures for maintaining retransmission paths between the BS and an access RS.

self-organization

[00095] The self-organizing block performs functions to support self-configuration and self-optimization mechanisms. Functions include procedures for requesting RSs/MSs to report measurements for self-configuration and self-optimization and receiving measurements from RSs/MSs.

Multiple Carrier

[00096] Multi-carrier block (MC) allows a common MAC entity to control a PHY covering multiple frequency channels. Channels can be of different bandwidths (eg 5, 10 and 20 MHz), be in contiguous or non-contiguous frequency bands. The channels can be of the same or different duplexing modes, for example frequency division duplexing (FDD), time division duplexing (TDD) or a mixture of bidirectional and wide-spread carriers only. For contiguous frequency channels, the overlapping guard subcarriers are aligned in the frequency domain so as to be used for a data transmission.

[00097] Medium Access Control (MAC) includes function blocks which are related to physical layer and link controls, such as: • PHY control • Control signaling • Sleep mode management • QoS • Resource Programming and Multiplexing • ARQ • Fragmentation/Packaging • MAC PDU Formation • Multiple Radio Coexistence • Data Forwarding • Interference Management • Coordination between BS

PHY control

[00098] The PHY control block handles a PHY signaling such as range calculation, measure/return (CQI) and HARQ ACK/NACK. Based on the CQI and the HARQ ACK/NACK, the PHY control block estimates a channel quality, as seen by the MS, and performs a link adaptation by adjusting the modulation and coding scheme (MCS), and/ or power level. In the range calculation procedure, the control block does an uplink sync with power adjustment, frequency offset estimate and sync offset.

Control Signaling

[00099] Control signaling block generates resource allocation messages. The sleep mode management block handles a sleep mode operation.

Sleep Mode Management

[000100] The sleep mode management block also generates a MAC signaling related to a sleep operation, and can communicate with the resource multiplexing and scheduling block, so as to operate properly according to the sleep period .

QoS

[000101] The QoS block handles a QoS management based on QoS parameters introduced from the connection and service flow management block for each connection. Programming and

Resource Multiplexing

[000102] Resource programming and multiplexing block schedules and multiplexes packets based on connection properties. In order to reflect the connection properties, the resource multiplexing and programming block receives a QoS information from the QoS block for each connection.

ARCH

[000103] The ARQ block handles a MAC ARQ function. For ARQ-enabled connections, the ARQ block logically divides the MAC SDU into ARQ blocks, and numbers each logical ARQ block. The ARQ block can also generate ARQ management messages, such as a return message (ACK/NACK information).

Fragmentation/Packaging

[000104] Block fragmentation/packaging performs a fragmentation or a packaging of MSDUs based on scheduling results from the scheduling block and resource multiplexing.

MAC PDU Formation

[000105] MAC PDU building block builds a MAC PDU so that a BS/MS can transmit user or management traffic messages to a PHY channel. MAC PDU building block adds a MAC header and can add sub-headers.

Multiple Radio Coexistence

[000106] The multiple radio coexistence block works to support concurrent operations of IEEE 802.16m and non-IEEE 802.16m radios co-located in the same mobile station. Data Forwarding

[000107] The data forwarding block performs data forwarding functions when RSs are present in the path between a BS and an MS. The data forwarding block can cooperate with other blocks, such as the resource multiplexing and scheduling block and the MAC PDU forming block.

Interference Management

[000108] The interference management block performs functions for managing an interference between cells/sectors. Operations can include: • MAC layer operation • Interference measurement/assessment report sent via MAC signaling • Interference mitigation by programming and flexible frequency reuse • PHY layer operation • Transmission power control • Cancellation interference • Interference measurement • Beam forming/transmission precoding (Tx)

Coordination between BS

[000109] The coordination block between BSs performs functions for coordinating the actions of multiple BSs by exchanging information, for example, interference management. Functions include procedures for exchanging information, eg for managing interference between BSs by frame signaling and by sending MAC message from MS. The information may include interference characteristics, eg interference measurement results, etc.

[000110] Reference is now made to figure 11, which shows the user traffic data flow and a processing in the BS 14 and MS 16. The dashed arrows show the user traffic data flow from from the network layer to the physical layer and vice versa. On the transmission side, a network layer packet is processed by the convergence sublayer, the ARQ function (if present), the fragmentation/packaging function and the MAC PDU formation function, to form PDU(s). ) MAC to be sent to the physical layer. On the receive side, a physical layer SDU is processed by a MAC PDU formation function, the fragmentation/packaging function, the ARQ function (if present) and the convergence sublayer function, for packet formation. of network layer. The solid arrows show the primitive control parts among the CPS functions and between the CPS and the PHY that are related to user traffic data processing.

[000111] Reference is now made to figure 12, which shows the CPS control plane signaling flow and the processing in the BS 16 and MS 14. On the transmission side, the dashed arrows show the flow of control plane signaling from the control plane functions to the data plane functions and the processing of control plane signaling by the data plane functions to the formation of the corresponding MAC signaling (e.g., management messages MAC header/sub-header) to be transmitted over the air. On the receiving side, the dashed arrows show the processing of over-the-air MAC signaling received by the data plane functions and the reception of the corresponding control plane signaling by the control plane functions. The solid arrows show the control primitives among the CPS functions and between CPS and PHY that are related to the processing of a control plane signaling. Solid arrows between M_SAP/C_SAP and MAC function blocks show the primitive control and management parts to/from the network management and control system (NCMS). The primitive parts to/from M_SAP/C_SAP define the functionalities involved in the network, such as interference management between BS, inter/intra-RAT mobility management, etc., and management-related functionalities such as location management, system configuration, etc.

[000112] Non-limiting examples of MAC management messages include DL-MAP, UL-MAP, DCD and UCD. Although nomenclature from IEEE 802.16 and/or 802.16m has been adopted, it should be appreciated that explicit compliance with any standard is not a requirement, and that those skilled in the art will recognize the use of a common nomenclature as an aid in understanding, rather than a limitation of the present invention.

[000113] DL-MAP and UL-MAP can be used for defining access to downlink and uplink information, respectively. DL-MAP is a MAC management message that defines downlink burst start times. Equivalently, UL-MAP is a set of information that defines the entire access (uplink) for all MSs during a scheduling interval. Basically, DL-MAP and UL-MAP can be seen as directories, broadcast by the BS, of downlink and uplink frames.

[000114] The DCD (downlink channel descriptor) message is a broadcast MAC management message transmitted by the BS 14 at a periodic time interval, so as to provide the burst profiles (physical parameter sets) that can be used by a physical downlink channel during a burst, in addition to other useful downlink parameters. The UCD (uplink channel descriptor) message is a broadcast MAC management message transmitted by the BS at a periodic time interval, so as to provide the burst profile description (physical parameter sets) that can be used by a physical uplink channel, in addition to other useful uplink parameters.

[000115] Reference is now made to Figure 13, which shows a generic protocol architecture for supporting a multi-carrier system. A common MAC entity can control a PHY passing through multiple frequency channels. Some MAC messages sent on one carrier may also apply to other carriers. Channels can be of different bandwidths (eg 5, 10 and 20 MHz) and be in contiguous or non-contiguous frequency bands. Channels can be in different multiplexing modes, for example FDD, TDD or a mixture of bidirectional carriers or just wide broadcast.

[000116] The common MAC entity can simultaneously support the presence of MSs 16 with different capabilities, such as operation with more than one channel at a time or aggregation by contiguous or non-contiguous channel.

[000117] Figure 20 illustrates a possible state transition diagram for an MS 16. As a non-limiting example, the diagram shows four (4) states, the initialization state, the access state, the connected state and the inactive state.

Initialization State

[000118] In the boot state (see figure 21), the MS 16 performs a cell selection by scanning, synchronizing and acquiring system configuration information prior to entering the access state. If the MS 16 cannot properly perform system configuration information decoding and cell selection, it will return to perform downlink scanning and synchronization. If the MS 16 successfully decodes the information and selects a target BS 14, it will transition to the access state.

Access Status

[000119] In the access state (see figure 22), the MS 16 performs a network entry with the target BS 14. The network entry is a multi-step process consisting of range calculation, pre-capacity negotiation. authentication, authentication and authorization, capacity exchange and registration.

[000120] The decomposition of the input system procedure leading from downlink scanning and synchronization to the point at which a connection is established can be established as follows, by way of non-limiting example: • Downlink scanning and synchronization and acquisition of grant message (which grants an uplink resource) and acquisition of downlink channel and uplink channel description; • Initial range calculation; • Ability to negotiate; • Authorization and authentication/key exchange; • Registration with BS 14; • Establishment of connection.

[000121] Upon failure to complete network entry, MS 16 may transition to boot state.

Connected State

[000122] When in the connected state, the MS 16 can operate in one of 3 modes (see figure 23): sleep mode, active mode and scan mode. During the connected state, the MS 16 can maintain one or more key connections established during the access state. Additionally, the MS 16 and BS 14 can establish additional transport connections. The MS 16 can remain in the connected state during a peer-to-peer transfer. The MS 16 can transition from connected to idle state on a command from the BS 14. A failure to hold the fundamental connection(s) can also prompt the MS 16 to transition to the initialization state .

[000123] With reference now to the modes of operation in the connected state, when the MS 16 is in active mode, the BS 14 can program the MS 16 to transmit and receive at the first available opportunity provided by the protocol being implemented, i.e., the MS is assumed to be 'available' for the BS 14. The MS 16 may request a transition to sleep mode or scan mode from active mode. A transition to sleep or scan mode can happen by a command from the BS 14. The MS 16 can transition to the idle state from the connected state's active mode.

[000124] When in sleep mode, the MS 16 and the BS 14 agree on a division of resources in time into sleep windows and listen windows. It is only expected that the MS 16 will be able to receive transmissions from the BS 14 during the listen windows, and any protocol exchange has to be initiated during that time. The transition of MS 16 to active mode is alerted by control messages received from BS 14. MS 16 can transition to idle state from sleep mode of connected state during listen intervals.

[000125] When in scan mode, MS 16 performs measurements as instructed by BS 14. MS 16 is unavailable to BS 14 while in scan mode. The MS 16 returns to active mode once the duration negotiated with the BS 14 for scanning expires. inactive state

[000126] The idle state (see figure 24) may include, by way of non-limiting example, 2 separate modes, specifically, radio call mode available and radio call mode unavailable, based on their operation and a MAC message generation. During the idle state, the MS 16 can perform a power saving by switching between radio call available and radio call unavailable mode.

[000127] In idle mode, the MS 16 can belong to one or more radio call groups of different sizes and shapes, based on user mobility. The MS 16 monitors the radio call message during the MS radio call listen interval. The start of the MS radio call listen interval is derived based on the radio call cycle and the radio call offset. The radio call offset and radio call cycle can be defined in terms of the number of superframes.

[000128] The MS 16 can thus be radio called by the BS 14 (using a radio call send message) while in the available radio call mode. If the MS 16 is called by radio with an indication to return to the connected state, the MS 16 will transition to the access state for its re-entry into the network.

[000129] MS 16 can also perform location update procedure during idle state.

[000130] During radio call unavailable mode, the MS 16 does not need to monitor the downlink channel in order to reduce its power consumption.

[000131] The MS has a global address (or a global identifier) and logical addresses (or logical identifiers) that identify the MS during an operation. Specifically, the global address can be a globally unique 48-bit IEEE extended unique identifier (EUI-48™) based on the 24-bit organizationally unique identifier (OUI) value administered by the IEEE Registration Authority. However, this is not a limitation or restriction of the present invention.

[000132] As logical identifiers are concerned, these may include one or more "flow identifiers" (FIDs) and one or more "mobile station identifiers". FIDs can uniquely identify the management connections and transport connections that the MS 16 has established with the network. Some specific FIDs can be pre-assigned. For their part, the mobile station identifiers uniquely identify the MS 16 in the domain of the BS 14. Various types of STID could be as follows:

[000133] Access ID: a temporary identifier assigned to the MS 16 when performing a range calculation operation (i.e., upon a network entry while in the access state or upon a network re-entry or during an update while in the idle state). This ID can be assigned to the MS 16 by the BS 14 when the BS 14 first detects a range calculation code transmission from the MS 16.

[000134] MS ID: An identifier assigned to MS 16 for use in the connected state. The MS ID replaces the Access ID and can be sent to the MS 16 during the range calculation operation. A downlink control information dedicated to a particular MS (e.g., downlink PHY burst/resource allocation) can be addressed using the MS ID. The MS ID can be, but need not be, the same length as the Access ID identifier.

[000135] Inactive ID: An identifier assigned to an MS for use in the inactive state. In order to reduce signaling processing time and provide location privacy, the idle ID can be assigned to uniquely identify those MSs in the idle ID who are in a particular radio call group. The idle ID remains valid for MS 16 as long as MS 16 is in the same radio paging group. Idle ID can be assigned during idle ID entry or during a location update due to a radio call group change. The idle ID may be included in a message sent by the MS 16 in the idle ID for purposes of radio call response or location update.

[000136] By way of example, the mobile station identifiers mentioned above could be 8 bits, 10 bits or 12 bits in length, although longer or shorter STIDs are possible, without deviating from the present invention. Different mobile station identifiers can be of different lengths. For example, access ID could be the same length as MS ID, both could be shorter than idle ID. However, this is just an example, and is not to be considered limiting. Other mobile station identifiers may exist and could be reserved, for example, for broadcast and multicast services.

[000137] As will be appreciated by those skilled in the art, a MAC PDU is a data packet (group of data bits, or datagram) that contains header, connection address, and data protocol information, which is used for control and transferring information over a type of medium (such as a radio channel). Referring now to Fig. 15, the MAC PDU created in association with a given connection contains a header which holds a corresponding FID along with control information (e.g. a length field which indicates the length of the MAC PDU payload and an extended header bit (EH) which, if set, indicates that additional information appears in an extended (not shown) portion of the header). The MAC PDU can also have a payload of data and error checking bits (CRC) after the header (eg user data). The payload can be used to carry management messages and data associated with various traffic connections.

[000138] Being local to the MS, each FID is shorter than the 16-bit CID defined in the IEEE 802.16-2004 standard or the IEEE 802.16-2009 standard. In a non-limiting modality, the FID can be 4 bits long. In another non-limiting modality, the FID can be 3 bits long. Other possibilities exist within the scope of the present invention. The use of FID in the MAC header also results in a shorter overall MAC header than those proposed in IEEE 802.16-2004 or IEEE 802.16-2009, where a 16-bit CID is used.

[000139] The following now describes a range calculation operation that can be performed by the MS 16 and the BS 14 in order to establish a connectivity. The range calculation operation is performed by the appropriate function blocks described above and in particular by the function blocks belonging to the medium access control (MAC) common part (CPS) sublayer. These function blocks can include, for example, and without limitation, the network input management block and the idle mode management block (part of the radio resource management and control functions - RRCM) as well as the block of PHY control (part of the media access control functions - MAC) described earlier in relation to figure 10.

[000140] Three non-limiting range calculation operation scenarios will be described, specifically Scenario A, in which MS 16 is seeking to establish an initial connectivity to the network (i.e. MS 16 is activated, passes through state and performs a range calculation from the access state), Scenario B, in which the MS 16 performs a range calculation when re-entering the network (for example, after having been in idle state, after leaving the network to use a different one, then returned (ie roaming), etc.), and Scenario C, in which the MS 16, after being in the idle state, performs a range calculation in the context of a location update . Scenario A

[000141] In Scenario A, MS 16 is seeking to establish an initial connectivity to the network. First, the MS 16 is activated and goes through the initialization state. During the boot state, the MS 16 performs a scan and a synchronization. In other words, when the MS 16 wants to join the network, it first scans the downlink frequencies to look for a suitable channel. The search is completed as soon as it detects a downlink frame. The next step is to establish a synchronization with the BS 14. Once the MS 16 receives a DL-MAP message and a DCD message, the downlink synchronization phase is completed and the MS 16 remains synchronized as long as it continues receiving DL-MAP and DCD messages. After synchronization is established, the MS 16 waits for a UCD message to acquire the uplink channel parameters.

[000142] A range calculation operation now takes place while the MS 16 is in the access state. Referring to Fig. 14, the BS 14 issues an uplink grant message 1410 (e.g., an UL-MAP message) which defines an initial range calculation interval to be used by the MS 16 in the uplink frame. . The content of the uplink grant message could be formulated by an uplink scheduler in the BS 14. The uplink scheduler manages the uplink bandwidth and schedule MSs that will have uplink grants allocated, based on requirements of your service flow(s) and bandwidth requests. An uplink grant allocated by the uplink scheduler is directed to a reserved FID (eg, broadcast) and may use a predefined robust profile with modulation of BPSK % / FEC, for example. After the transmission of the grant message 1410, the BS 14 continues to operate normally (1412). This includes periodically issuing other grant messages, such as grant message 1422.

[000143] Meanwhile, as shown in 1412, MS 16 was waiting to receive a grant message, and is assumed to finally receive grant message 1410. Upon receipt of grant message 1410, MS 16 formulates a range calculation message 1416 characterized by a set of range calculation features. For example, the MS 16 can randomly select a code from a set of pseudo noise range calculation codes, modulate it into a range calculation subchannel, and subsequently transmit it in a range of range calculation randomly selected from a set of range calculation ranges available in the uplink frame. The MS 16 can use a random selection or a random return for selecting a range calculation interval. When a random selection is used, the MS 16 can select a range calculation range from all available ranges in a single frame using a uniform random process, although other possibilities exist. When a random return is used, the MS 16 can select a range calculation interval from all available range calculation intervals in a corresponding return window using a uniform random process, for example.

[000144] If the BS 14 properly detects the presence of the range calculation code in the range calculation message range calculation interval 1416, then the BS 14 will issue a range calculation response message to the MS 16. For example, the range calculation response message could take a form similar to an RNG-RSP message as defined in IEEE 802.16 or 802.16m. In anticipation of this event, in step 1426, the MS 16 determines whether an RNG-RSP message has been received from the BS 14. If a certain amount of time has elapsed, and an RNG-RSP message has not been received, then, this will mean that the BS 14 has not properly detected the presence of the range calculation code in the range calculation range of the range calculation message 1416. This could be for a variety of reasons, including issues of power, interference, etc. . By the way, MS 16 is also watching for additional grant messages (step 1420). In fact, if the aforementioned grant message 1422 is received without having received an intervening RNG-RSP message from the BS 14, then the MS 16 will be granted a new range calculation interval in a link frame ascending.

[000145] In response and similarly to what was described above, the MS 16 formulates a range calculation message 1424 which is characterized by a set of range calculation features. Specifically, the MS 16 randomly selects a code from a set of pseudo noise range calculation codes, modulates it into a range calculation subchannel, and subsequently transmits it in a range calculation interval. range selected randomly from a set of range calculation intervals available in the uplink frame, and returns to step 1426. If the BS 14 properly detects the presence of the range calculation code in the range calculation range of range calculation message 1424, then the BS 14 will issue a range calculation response message to the MS 16. In anticipation of this event, in step 1426, the MS 16 determines whether a range calculation response message has been received from the BS 14. If a certain amount of time has elapsed, and a range calculation response message has not yet been received, then the MS 16 will receive yet another grant message in the step 1420 and so on. However, if the BS 14 does not properly detect the presence of the range calculation code in the range calculation range of the range calculation message 1424 (step 1428), then the BS 14 will determine whether the range calculation operation is okay. successful (step 1430). In other words, just because the BS 14 can listen to the MS 16 does not mean that the MS 16 is using proper power, timing, and frequency parameters.

[000146] Thus, the result of step 1430 may be that the BS 14 has determined that the range calculation operation was a success, in which case the BS 14 proceeds to issue a range calculation response message 1450 indicative of this determination. On the other hand, the result of step 1430 may be that the BS 14 determined that the range calculation operation was not a success. In this case, BS 14 proceeds to step 1432, where a parameter setting is calculated. This can affect one or more of the frequency, timing and power that characterize the signaling used by the MS 16. Various algorithms can be used to determine a fit of the power, timing and/or frequency characteristics of the uplink signal. Also, in step 1432, the BS 14 calculates a new range calculation code and/or a new range calculation interval to be used by the MS 16. Also, in step 1432, the BS 14 determines an access ID for the MS 16. The access ID can be used by the BS 14 as an address, an encryption key or a scrambling code for a content destined for the MS 16, during the range calculation operation.

[000147] The BS 14 then proceeds to formulate a range calculation response message 1434, which is sent to the MS 16. The range calculation response message 1434 specifies that a range calculation is to continue, and provides any necessary adjustments in the timing/frequency/power characteristics of the uplink signal. In addition, the range calculation response message 1434 specifies the range calculation code and/or the range calculation interval that were used by the MS 16 for the transmission of the range calculation message 1424. This allows the MS to 16 recognize that the range calculation response message 1434 is actually intended for it. In addition, the range calculation response message 1434 identifies the assigned range calculation code and/or the assigned range calculation interval to be used by the MS 16 next time. In addition, the range calculation response message 1434 includes the access ID mentioned above.

[000148] The range calculation response message 1434 is then received at the MS 16. The MS 16 performs step 1426 and determines that the range calculation response message 1434 is indeed a destined range calculation response message. for MS. In particular, this can be determined based on the fact that the range calculation code and/or the range calculation interval that the MS 16 previously used is represented in the range calculation response message 1434. Therefore, the MS 16 takes the “S” branch out of step 1426. Also, the MS 16 stores the access ID in memory for future use. Also, the MS 16 makes the required adjustments for the power/time/frequency characteristics it uses in the uplink direction. The MS 16 then proceeds to formulate another range calculation message 1436 characterized by a set of range calculation features (and also the time/frequency/power characteristics). This time, the MS 16 uses the assigned range calculation code and the assigned range calculation interval received from the BS 14 in the range calculation response message 1434.

[000149] The BS 14 receives the range calculation message 1436 and determines if the range calculation operation is successful (step 1438). The result of step 1438 may be that the BS 14 has determined that the range calculation operation was a success, in which case the BS 14 proceeds to issue a range calculation response message 1448 indicative of this determination. However, it is possible, at this stage, that the previous power/time/frequency settings were not sufficient. The result of step 1438, therefore, may be that the BS 14 has determined that the range calculation operation was not a success. In this case, BS 14 proceeds to step 1440, where an additional parameter setting is calculated. This can again affect one or more of the frequency, timing and power that characterize the signaling used by the MS 16. Various algorithms can be used to determine a set of power, timing and/or frequency characteristics of the link signal ascending. Also, in step 1440, the BS 14 can, but need not, calculate a new range calculation code and/or a new range calculation interval to be used by the MS 16.

[000150] The BS 14 then proceeds to formulate a range calculation response message 1442, which is sent to the MS 16. The range calculation response message 1442 specifies that the range calculation is to continue, as well as providing any additional adjustments needed for the uplink signal timing/frequency/power characteristics. In addition, the range calculation response message 1442 specifies the access ID that had previously been sent to the MS 16 in the range calculation response message 1434. The access ID allows the MS 16 to recognize that the range message 1442 range calculation answer is intended for it. Therefore, it is not necessary to transmit in the range calculation response message 1442 the range calculation code and/or the range calculation interval which were used by the MS 16 for the transmission of the range calculation message 1436. the range calculation response message 1442 identifies the assigned range calculation code and/or the assigned range calculation interval, if computed in step 1440, to be used by the MS 16 in the future.

[000151] In step 1444, the MS 16 makes the required adjustments for the power/time/frequency characteristics it uses in the uplink direction. The MS 16 then proceeds to formulate another range calculation message 1446 characterized by a set of range calculation features (and also the adjusted time/frequency/power characteristics). The MS 16 uses the range calculation code and range calculation interval it had used in the past, or uses the assigned range calculation code and/or the assigned range calculation range specified by the MS 16 in the response message. range calculation message 1442. The BS 14 receives range calculation message 1446 from the MS 16 and determines whether the range calculation operation is successful (step 1438). If the result of step 1438 is that the BS 14 determined that the range calculation operation was not a success, then the BS 14 will return to step 1440. However, at some point, the range calculation operation will be considered as having been successful, and the BS 14 will proceed to issue a range calculation response message 1448 indicative of this determination. The range calculation response message 1448 also includes the access ID identifying the MS 16. However, an extended MAC address is not required.

[000152] The BS 14 then issues a grant message 1452, which schedules the next uplink transmission from the MS 16. In this case, the next uplink transmission from the MS 16 is a Calculation Request message range 1454 containing the global address (for example, the 48-bit MAC address) of the MS 16. For example, the range calculation request message 1454 could take a form similar to an RNG-REQ message as defined in IEEE 802.16 or 802.16m. Receipt of the global address by the BS 14 allows the BS 14 to determine the true identity of the MS 16 with which the range calculation operation was successfully completed. Thus, in step 1456, the BS 14 determines the MS ID based on the global address. This can be done by looking up the MS ID in a table in memory, based on the global address. Alternatively, the MS ID can be assigned from a group of addresses or identifiers, and stored in association with the global address.

[000153] The BS 14 then sends a range calculation response message 1458 to the MS 16, containing the MS ID as well as the access ID identifying the MS. The MS 16 receives the range calculation response message 1458, and determines who is the recipient of this message (based on the access ID). The MS 16 proceeds to extract the MS ID and store it in memory. With the range calculation operation now completed, the MS 16 enters the connected state. MS 16 uses the MS ID in future communication with the network during the connected state. Future communication may include transmission and/or reception of data in association with management connections and traffic connections.

[000154] It should be appreciated that due to the fact that the access ID is designed for use specifically during the range calculation operation, and due to the fact that only a limited number of mobile stations perform a range calculation at any given time , the login ID can be limited to a small number of bits and in particular less than 16 bits. As an example, the range of 8 to 10 bits might be suitable as an access ID length. Also, the fact that the same access ID could conceivably be recycled by different mobile stations performing a range calculation at different non-overlapping times, the access ID does not have a one-to-one mapping with a given global address of MS. This preserves anonymity and improves security.

[000155] Also, due to the fact that, during the connected state, the MS 16 can be identified by the MS ID, rather than its global address, and because the MS ID is local to the BS domain of service, a similarly small number of bits can be used and in particular less than 16 bits. Again, the 8-10 bit range may be suitable, by way of example. However, this does not imply that the login ID and MS ID need to be the same length.

[000156] It will also be appreciated that a comparatively short length of Access ID and MS ID will cause a shortening of the grant message (eg UL-MAP), range calculation response message (eg RNG- RSP) and the range calculation request message (eg RNG-REQ). DL-MAP, DCD and UCD messages would similarly benefit from reduced length.

[000157] A first alternative modality is now described with reference to the flowchart in Figure 16. Specifically, consider that the result of step 1438 is that the BS 14 determined that the range calculation operation was not a success. In this case, BS 14 proceeds to step 1640, where an additional parameter setting is calculated. This again may affect one or more of the frequency, timing and power that characterize the signaling used by the MS 16. Various algorithms can be used to determine a fit of the power, timing and/or frequency characteristics of the uplink signal. Also, in step 1640, the BS 14 calculates a new range calculation code and a new range calculation interval to be used by the MS 16. As the range calculation continues, the assigned range calculation resources correspond to channels of range calculation with progressively smaller modality offsets. For example, initial range calculation attempts can be sent in a range calculation region that covers 6 symbols, which is intended to accommodate larger range calculation timing offsets. As the range calculation progresses, the BS 14 can assign range calculation resources to the MS 16 that cover progressively shorter durations, such as 3 and then 2 symbols. The assigned end-range calculation facility can only accommodate a sync on a cyclic prefix length of OFDM. (The final assigned range calculation feature can also be retained by the MS 16 for a periodic range calculation).

[000158] The BS 14 then proceeds to formulate a range calculation response message 1642, which is sent to the MS 16. The range calculation response message 1642 specifies that a range calculation is to continue as well as provides any additional adjustments needed for the sync/frequency/power characteristics of the uplink signal. In addition, the range calculation response message 1642 identifies the assigned range calculation code and the assigned range calculation interval to be used by the MS 16 in the future. In fact, in step 1444, the MS 16 makes the required adjustments for the operatively/time/frequency characteristics it uses in the uplink direction. The MS 16 then proceeds to formulate another range calculation message 1646 characterized by a set of range calculation features (and also the adjusted time/frequency/power characteristics). The MS 16 uses the assigned range calculation code and the assigned range calculation interval specified by the MS 16 in the range calculation response message 1642.

[000159] A second alternative embodiment is now described with reference to the flowchart in Figure 17. Specifically, in this alternative embodiment, since the range calculation code and range calculation range used in a range calculation message are received ("heard") by the BS 14, the MS 16 continues to use the same range calculation code and range calculation interval, until the BS 14 generates a range calculation response message indicative of a calculation successful range.

[000160] Alternatively or additionally, the MS 16 and BS 14 use sequences (or "scrambling codes") to scramble the communications between the two entities. A first of these sequences is an "initial range calculation sequence" and a second of these sequences is a "continued range calculation sequence". As shown in Figure 17, the initial range calculation sequence is used by the MS 16 to scramble the range calculation messages it sends before receiving the first range calculation response message from the BS 14. Also, as shown in Fig. 17, the initial range calculation sequence is also used by the BS 14 for scrambling messages sent to the MS 16, before the MS 16 has received the access ID. Also, as shown in Figure 17, the continued range calculation sequence (or, optionally, the initial range calculation sequence) can be used by the MS 16 to scramble the range calculation messages it sends between receiving the first range calculation response message from BS 14 and receipt of MS ID. Thus, it is assumed that the initial range calculation sequence (and, if used, the continued range calculation sequence) is known by the BS 14 and the MS 16. Also, as shown in Figure 17, after the MS 16 has received the access ID, the BS 14 scrambles messages destined for the MS 16 using the access ID. Clearly, proper unscrambling needs to be performed by the recipient and therefore before a knowledge of the proper scrambling code is required. For this reason, it is only after the MS 16 has been informed of the access ID that messages destined for the MS 16 can be scrambled using the access ID. Scenario B

[000161] In Scenario B, MS 16 becomes involved in a range calculation operation upon re-entry into the network (for example, after having been in the idle state, after leaving the network to use a different one, then returned ( i.e. in roaming), etc.). Thus, in this scenario, a sync is assumed to have been maintained. Reference is now made to the flowchart of Fig. 18 which shows the actions of the BS 14 and MS 16 while the MS 16 is in the access state. It should be appreciated that a range calculation may take place autonomously (i.e. MS initiated) or in response to a radio call message 1809 from the BS 14 while the MS 16 is in the available radio call sending mode. from the inactive state. In the case of a received radio call message 1809, the radio call message 1809 may specify the set of dedicated range calculation resources to be used by the MS 16, such as a dedicated range calculation code and a range of Dedicated range calculation.

[000162] The BS 14 issues an uplink grant message 1810 (e.g., an UL-MAP message), which defines an initial range calculation interval to be used by the MS 16 in the uplink frame. The content of the uplink grant message could be formulated by an uplink scheduler in the BS 14. The uplink scheduler manages an uplink bandwidth, and schedules the MSs that will be allocated uplink grants based on the QoS requirements of your service flow(s) and bandwidth requests. An uplink grant allocated by the uplink progressively is directed to a reserved FID (eg, broadcast), and may use a predefined robust profile with BPSK %/FEC modulation, for example. After the transmission of the grant message 1810, the BS 14 continues to operate normally (1812). This includes periodically issuing other grant messages, such as grant message 1822.

[000163] Meanwhile, as shown in 1812, MS 16 was waiting to receive a grant message, and is assumed to finally receive grant message 1810. Upon receipt of grant message 1810, MS 16 formulates a range calculation message 1816 characterized by a set of dedicated range calculation facilities specified in radio call message 1809. This includes a dedicated range calculation code and/or a dedicated range calculation interval.

[000164] If the BS 14 properly detects the presence of the range calculation code in the range calculation range of the range calculation message 1816, then the BS 14 will issue a range calculation response message to the MS 16. For example, the range calculation response message could take a form similar to an RNG-RSP message as defined in IEEE 802.16 or 802.16m. In anticipation of this event, in step 1826, the MS 16 determines whether an RNG-RSP message has been received from the BS 14. If a certain amount of time has elapsed, and an RNG-RSP message has not been received, then, this will mean that the BS 14 has not properly detected the presence of the range calculation code in the range calculation range of the range calculation message 1816. This could be for a variety of reasons, including issues of power, interference, etc. . By the way, MS 16 is also aware of the receipt of additional grant messages (step 1820). In fact, if the aforementioned grant message 1822 is received without receiving an intervening RNG-RSP message from the BS 14, then the MS 16 will be granted a new range calculation interval in a link frame ascending.

[000165] In response and similarly to what has been described above, the MS 16 formulates a range calculation message 1824 which is characterized by a set of dedicated range calculation resources. If the BS 14 properly detects the presence of the range calculation code in the range calculation message range calculation interval 1824, then the BS 14 will issue a range calculation response message to the MS 16. In an anticipation of this event, in step 1826, the MS 16 determines whether a range calculation response message has been received from the BS 14. If a certain amount of time has elapsed, and a range calculation response message has not yet been received, then MS 16 will receive yet another grant message at step 1820, and so on. However, if the BS 14 does not properly detect the presence of the range calculation code in the range calculation range of the range calculation message 1824 (step 1828), then the BS 14 will determine whether the range calculation operation is okay. successful (step 1830). In other words, just because the BS 14 can listen to the MS 16 does not mean that the MS 16 is using proper power, timing, and frequency parameters.

[000166] Thus, the result of step 1830 may be that the BS 14 has determined that the range calculation operation was a success, in which case the BS 14 proceeds to issue a range calculation response message 1850 indicative of this determination. On the other hand, the result of step 1830 may be that the BS 14 determined that the range calculation operation was not a success. In this case, BS 14 proceeds to step 1832, where a parameter setting is calculated. This can affect one or more of the frequency, timing and power that characterize the signaling used by the MS 16. Various algorithms can be used to determine a fit of the power, timing and/or frequency characteristics of the uplink signal. Also, in step 1832, the BS 14 calculates a new range calculation code and/or a new range calculation interval to be used by the MS 16. Also, in step 1832, the BS 14 determines an access ID for the MS 16. The access ID can be used by the BS 14 as an address, an encryption key or a scrambling code for a content destined for the MS 16, during the range calculation operation.

[000167] The BS 14 then proceeds to formulate a range calculation response message 1834, which is sent to the MS 16. Range calculation response message 1834 specifies that a range calculation is to continue, and provides any necessary adjustments in the timing/frequency/power characteristics of the uplink signal. In addition, the range calculation response message 1834 specifies the range calculation code and/or the range calculation interval that were used by the MS 16 for the transmission of the range calculation message 1824. This enables the MS 16 recognize that the 1834 range calculation response message is actually intended for it. In addition, the range calculation response message 1834 identifies the assigned range calculation code and/or the assigned range calculation interval to be used by the MS 16 next time. In addition, the 1834 range calculation response message includes the access ID mentioned above.

[000168] The range calculation response message 1834 is then received at the MS 16. The MS 16 performs step 1826 and determines that the range calculation response message 1834 is in fact a target range calculation response message. for MS. In particular, this can be determined based on the fact that the range calculation code and/or the range calculation interval that the MS 16 previously used is represented in the range calculation response message 1834. Therefore, the MS 16 takes the “S” branch out of step 1826. Also, the MS 16 stores the access ID in memory for future use. Also, the MS 16 makes the required adjustments for the power/time/frequency characteristics it uses in the uplink direction. The MS 16 then proceeds to formulate another range calculation message 1836 characterized by a set of range calculation features (and also the time/frequency/power characteristics). The MS 16 uses the dedicated range calculation code and the range calculation interval, or the new range calculation code and the new range calculation interval received from the BS 14 in the range calculation response message 1834 .

[000169] BS 14 receives range calculation message 1836 and determines if range calculation operation is successful (step 1838). The result of step 1838 may be that the BS 14 has determined that the range calculation operation was a success, in which case the BS 14 proceeds to issue a range calculation response message 1848 indicative of this determination. However, it is possible, at this stage, that the previous power/time/frequency settings were not sufficient. The result of step 1838, therefore, may be that BS 14 has determined that the range calculation operation was not a success. In this case, BS 14 proceeds to step 1840, where an additional parameter setting is calculated. This can again affect one or more of the frequency, timing and power that characterize the signaling used by the MS 16. Various algorithms can be used to determine a set of power, timing and/or frequency characteristics of the link signal ascending. Also, at step 1840, BS 14 can, but need not, calculate a new range calculation code ("newest") and/or a new range calculation interval ("newest") to be used by MS 16.

[000170] The BS 14 then proceeds to formulate a range calculation response message 1842, which is sent to the MS 16. Range calculation response message 1842 specifies that range calculation is to continue, as well as providing any additional adjustments needed for the uplink signal timing/frequency/power characteristics. In addition, the range calculation response message 1842 specifies the access ID that had previously been sent to the MS 16 in the range calculation response message 1834. The access ID allows the MS 16 to recognize that the range message 1842 range calculation answer is intended for it. Therefore, it is not necessary to transmit in the range calculation response message 1842 the range calculation code and/or the range calculation interval which were used by the MS 16 for the transmission of the range calculation message 1836. the range calculation response message 1842 identifies the assigned range calculation code and/or the assigned range calculation interval, if computed in step 1840, to be used by the MS 16 in the future.

[000171] In step 1844, the MS 16 makes the required adjustments for the power/time/frequency characteristics it uses in the uplink direction. The MS 16 then proceeds to formulate another range calculation message 1846 characterized by a set of range calculation features (and also the adjusted time/frequency/power characteristics). The MS 16 uses the dedicated range calculation code and the dedicated range calculation interval it had used in the past, or uses the newest range calculation code and the newest range calculation range specified by the MS 16 in the message. range calculation reply message 1842. The BS 14 receives range calculation message 1846 from the MS 16 and determines whether the range calculation operation is successful (step 1838). If the result of step 1838 is that the BS 14 determined that the range calculation operation was not a success, then the BS 14 will return to step 1840. However, at some point, the range calculation operation will be considered as having been successful, and the BS 14 will proceed to issue a range calculation response message 1848 indicative of this determination. The range calculation response message 1848 also includes the access ID identifying the MS 16. However, an extended MAC address is not required.

[000172] The BS 14 then issues a grant message 1852, which schedules the next uplink transmission from the MS 16. In this case, the next uplink transmission from the MS 16 is a Calculation Request message range 1854 containing the global address (eg, the 48-bit MAC address) of the MS 16. For example, the range calculation request message 1854 could take a form similar to an RNG-REQ message as defined in IEEE 802.16 or 802.16m. Receipt of the global address by the BS 14 allows the BS 14 to determine the true identity of the MS 16 with which the range calculation operation was successfully completed. In step 1856, the BS 14 determines the MS ID based on the global address. This can be done by looking up the MS ID in a table in memory, based on the global address. Alternatively, the MS ID can be assigned from a group of addresses or identifiers, and stored in association with the Idle ID.

[000173] The BS 14 then sends a range calculation response message 1858 to the MS 16, containing the MS ID as well as the access ID identifying the MS. The MS 16 receives the range calculation response message 1858, and determines who is the recipient of this message (based on the access ID). The MS 16 proceeds to extract the MS ID and store it in memory. With the range calculation operation now completed, the MS 16 enters the connected state. MS 16 uses the MS ID in future communication with the network during the connected state. Future communication may include transmission and/or reception of data in association with management connections and traffic connections.

[000174] A first alternative modality can incorporate the changes in figure 18 similarly to those modified in the flowchart in figure 16.

[000175] A second alternative modality can incorporate the changes in figure 18 similarly to those modified in the flowchart in figure 17.

Scenario C

[000176] In Scenario C, the MS 16 becomes involved in a range calculation operation in order to perform a location update while in the idle state. The location update can take place autonomously (i.e. MS initiated) or in response to a radio call sending message from the BS 14 while the MS 16 is in the radio call sending mode available from the idle state. Specifically, the MS in idle mode can perform a location update process operation if one of the following location update trigger conditions is met: • Radio call send group location update: MS 16 performs the process of location update when the MS 14 detects the paging group change by monitoring the paging group IDs which are transmitted by the BS 14; • Timer-based location update: the MS 16 periodically performs a location update process, before the timer expires inactively; • Deactivation Location Update: MS 14 attempts to complete a location update once as part of its deactivation procedure in an orderly fashion; • Multicast/Broadcast (MBS) location update: when receiving MBS data in idle state, during an MBS zone transition, the MS 16 can perform an MBS location update process for acquiring the zone information from MBS for continuous reception of MBS data.

[000177] Reference is now made to the flowchart in Figure 19, which shows the actions of the BS 14 and MS 16, while the MS 16 performs a location update while in the idle state. Specifically, the description from the reference number 1809 to the point where the MS 16 issues the range calculation request message 1854 containing the idle ID of the MS 16 is identical to that given above with reference to Fig. 18. Scope calculation request 1854 can also be formulated to indicate that it is a location update and not taking place in the context of a network entry. At step 1956, the BS 14, which is on receipt of the range calculation request message 1854, acknowledges the location update. This can be done by issuing a 1958 range calculation response message to the MS 16, containing a location update acknowledgment as well as the access ID identifying the MS. The MS 16 receives the range calculation response message 1958, and determines who is the recipient of this message (based on the access ID). With the range calculation operation now completed, the MS 16 returns to the idle state, until an additional location update is required, or until it is commanded to enter the connected state. The MS 16 uses the idle ID in future communication with the network during the idle state.

[000178] A first alternative modality can incorporate the changes in figure 19 similarly to those modified in the flowchart in figure 16.

[000179] A second alternative modality can incorporate the changes in figure 19 similarly to those modified in the flowchart in figure 17.

[000180] It should be appreciated that many variants of the above arrangements are possible. Specifically, messages can be scrambled, encoded or encrypted in any way desired. In particular, the scrambling techniques described with reference to Fig. 17 could be applied in any of the other message flowcharts in order to improve security, reduce peak power or for other reasons.

[000181] Furthermore, although the above messages have been described in the context of IEEE 802.16 and IEEE 802.16m mobile communication standards, it should be appreciated that the present invention can be more widely applied to other communication systems, including those being implemented or designed in accordance with other mobile communication standards, such as the long-term evolution (LTE) standard being promulgated by the Third Generation Partnership Project (3GPP).

[000182] Furthermore, although the above description has focused on an initial range calculation using an Access ID and an MS ID, it should be appreciated that the MS 16 can perform a periodic range calculation using one or both of these identifiers. .

[000183] Furthermore, although the above description has focused on a point-to-multipoint (PMP) implementation using an orthogonal frequency division multiple access (OFDMA) PHY layer, it should be appreciated that embodiments of the present invention can apply to other PHY implementations and layers, including a mesh implementation, as well as a single-layer (SC) PHY, a single-carrier access (SCa) PHY, and orthogonal frequency division multiplexing (OFDM) PHY. For example, in the PHY layers of SC, SCa and OFDM, instead of sending a range calculation code, MS can send an RNG-REQ message at an initial range calculation interval. Also, the MAC protocol used can support time division duplex (TDD) and/or frequency division duplex (FDD).

[000184] Furthermore, it should be appreciated that embodiments of the present invention can be applied to relay stations (RSs). More specifically, an RS can behave in such a way as to allow the MS to interact as if it were interacting with an MS. By the way, RS may implement one or more of the above features with respect to the initial scope calculation.

[000185] The preceding figures and description provide a specific example of a communication system that could be used to implement order modalities. It should be understood that the order modalities can be implemented with communications systems having architectures that are different from the specific example, but that operate in a manner consistent with the modalities implementation as described here.

[000186] Those of skill in the art will appreciate that, in some embodiments, the MS 16 and/or the BS 14 may comprise one or more computing apparatus that have access to a code memory (not shown) which stores a program code which is computer readable (instructions) for operating one or more computing devices, thereby allowing one or more of the functions described above to be performed. Computer-readable program code could be stored on a medium which would be fixed, tangible, and readable directly by one or more computing devices (eg, a removable floppy disk, a CD-ROM, a ROM, a disk computer-readable program code could be stored remotely, but be transferable to one or more computing devices via a modem or other interface device (eg, a communications adapter ) connected to a network (including, without limitation, the Internet) by a transmission medium, which may be a non-wireless medium (eg, optical or analog communications lines) or a wireless medium (eg, schematics microwave, infrared or others) or a combination thereof. In other embodiments, the MS 16 and/or BS 14 may comprise pre-programmed hardware or firmware elements (e.g., application-specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), flash memory , etc.), or other related components that allow one or more of the functions described above to be performed.

Claims (13)

1. Method for execution by a mobile station (16) in a mobile communications network characterized in that it comprises the steps of: receiving (1426) a temporary mobile station identifier from the network during a range calculation operation involving the mobile station; using the temporary mobile station identifier to extract the contents of at least one message received from the network during the range calculation operation; replacing the temporary mobile station identifier with an additional mobile station identifier, the additional mobile station identifier based on a global mobile station address; and using (1460) the additional mobile station identifier to extract the contents of at least one message received from the network after the range calculation operation is completed. 2. Method according to claim 1, characterized in that the temporary mobile station identifier is included in a first message received from the network during the range calculation operation, and further comprising, before receiving the first message: sending (1424) a range calculation message to the network, the range calculation message defined by a range calculation resource set, wherein the range calculation facility set includes a range calculation code and a range calculation time interval, wherein at least one of the range calculation code and the range calculation time interval is selected by the mobile station. 3. Method according to claim 1, characterized in that it further comprises, after receiving the temporary mobile station identifier: sending (1436) a range calculation message to the network, the range calculation message defined by a range calculation feature set, where the range calculation feature set includes a range calculation code and a range calculation time interval. 4. Method according to claim 1, wherein the additional mobile station identifier is included in a specific message received during the range calculation operation, and characterized in that it further comprises the step of: determining that the message specific is intended for the mobile station based on a presence of the temporary mobile station identifier in the specific message. 5. Method according to claim 1, characterized in that at least one of the at least one message received during the range calculation operation comprises an indication of completion of the range calculation operation. 6. Method according to claim 1, characterized in that the additional mobile station identifier is included in a particular message received during the range calculation operation. 7. Method according to claim 1, characterized in that the message including the unique identifier is sent according to uplink parameters, the method further comprising, after the step of receiving the additional mobile station identifier and before sending the message including the unique identifier: receiving a grant message from the network, the grant message indicating the uplink parameters for transmitting the message including the unique identifier. 8. Method according to claim 7, characterized in that the grant message includes the first mobile station identifier. 9. Mobile station characterized in that it comprises: a receiving circuit configured to receive messages from a network, at least one of the messages received during a range calculation operation and comprising a temporary mobile station identifier; a processing entity configured to extract the contents of at least one message received from the network during the range calculation operation based on the first mobile station identifier and to extract the contents of at least one message received from the network after the range calculation operation is completed based on a second mobile station identifier different from the temporary mobile station identifier. 10. Method for execution by a base station (14) in a mobile communications network characterized in that it comprises the steps of: issuing (1434) a first message intended for a mobile station (16), the first message including an identifier a temporary mobile station for use by the mobile station during a range calculation operation; determining (1438) that the range calculation operation is complete; issuing (1448) a second message intended for the mobile station, the second message including an additional mobile station identifier to replace the temporary mobile station identifier and for use by the mobile station in subsequent communication with the network. 11. Method according to claim 10, characterized in that the step of issuing the first message is performed after the step of receiving (1436) a range calculation message from the temporary mobile station, the calculation message range defined by a set of range calculation features. 12. Method according to claim 10, characterized in that it further comprises the steps of: receiving (1454) a globally unique identifier from the mobile station; consulting (1456) a memory based on the globally unique identifier to obtain the additional mobile station identifier. 13. Method according to claim 10, characterized in that it further comprises, before completion of the range calculation operation, the step of sending (1458) at least one message to the mobile station using the station identifier temporary mobile.

Images