Methods, computer-readable media and apparatus used for airlink communications

(54) Title: METHODS, MEANS LEGIBLE BY

COMPUTER AND EQUIPMENT USED FOR AIR LINK COMMUNICATIONS (30) Unionist Priority: 07/06/2006 us 60 / 812,011 (73) Owner (s): Qualcomm Incorporated (72) Inventor (s): Fatih Ulupinar, Gavin Bernard Horn, Paul E. Bender, Rajat Prakash (74) Attorney (s): Montaury Pimenta, Machado & Lioce (86) International Request: pct us2007070645 de

06/06/2007 (87) International Publication: wo 2007/143731 of

12/13/2007 (57) Summary: methods, computer-readable medium AND EQUIPMENT used for AEREO link communications. Methods and equipment for communication between an access terminal (AT) and a device serving the AT through an Access Point (AP) are described. According to a characteristic, server devices can be assigned specific addresses which are interpreted based on the source of the communication, for example, MAC packet, in which the address is used. Such addresses can be interpreted as being of a different type than other addresses which can be interpreted and / or used without regard to the sender's identity. In some modalities, Session Controllers and / or Internet Connection Points (lAPs) are identified with such addresses. The address value is identical for one or more ATs, but it is interpreted in an AP receiving such an IAP address based on the information corresponding to the AT which sent the packet including the address of the Session Controller or IAP.

<img file="BRPI0712410A2_D0001.tif" />

METHODS, MEDIA LEGIBLE BY COMPUTER AND EQUIPMENT USED FOR AIR LINK COMMUNICATIONS.

RELATED REQUESTS

This application claims the benefit of the

United States Provisional Patent Application

60 / 812,011 filed on June 7, 2006, entitled A METHOD AND APPARATUS FOR L2TP TUNNELING and the benefit of United States Provisional Patent Application 60 / 812,012 filed on June 7, 2006, entitled A METHOD AND APPARATUS FOR ADDRESSING MULTIPLE ACCESS POINTS each of which is expressly incorporated herein by reference.

FIELD

The present invention relates to methods and equipment for communications, and more specifically, methods and equipment related to packet routing.

BACKGROUND

Wireless communication systems often include several network access points in addition to mobile terminals and other endpoints. In many cases they normally communicate with (APs) and / or other access elements, for example, node devices from the terminals access the access points via wireless communication links while other elements in the network, for example , APs generally communicate via non-air links, for example, fiber, cable or wire links. In the case of an aerial link, bandwidth is a valuable limited resource. Consequently, it is desirable that communication via the aerial link be carried out efficiently without excessive overhead.

2/49

3/49 overhead link IAP address. This value is identical for one or more ATs, but it is interpreted in an AP receiving such an IAP address based on information corresponding to the AT that sent the packet including the IAP address.

Thus, the address

IAP can be implemented as a special address type

AT to identify an AP which Internet address IAP.

short, by modalities, an indicator that for the TA sending

In various embodiments, for example, bits can be used by a packet point including the IAP address is much less. In some, the IAP address is implemented as an address type where the address type indicator indicates that if no bit is the address, it is necessary to indicate the type of address.

Using an IAP-type address. In such of those used for

IAP of the type described, the relatively short address can be sent via air link when one communicates with its IAP air address.

package, maps the used links links

IP

In the case of the complete example, the mobile device is trying to unlike the modalities where if one of the IAP is sent via the uplink signals link, the AP receiving a MAC packet, with an IAP address, long address for the IAP address that for communications through links, through aerial channels.

corresponding set should be an example of transport

This can be information, of return, which to the sending AT are not done through access to a current IAP address serving short IAP address can be long, for example, address to the AT that sent the packet.

set AP package, which to the AT. Of this asset, includes mode, mapped to the address

Full IP, of the IAP serving

The determined address of the

4/49

5/49 predefined aerial corresponding to the network device, the network device having an IP address which is longer than the predetermined aerial link address; and determining an IP address corresponding to the predefined air link address from mapping information between the predefined air link addresses and the IP addresses. Another exemplary method of operating an access point comprises: receiving from a communication link with a network device, a first packet including information that must be communicated to an access terminal and a network device IP address indicating the source of information; and determining a predefined air link address corresponding to the network device address from mapping information between the predefined air link addresses and the IP addresses, the predefined air link address being shorter than the IP address. An exemplary access point includes: a wireless receiver to receive from an overhead link, a first packet communicated from an access terminal, the first packet including information that must be communicated to a network device and an address predefined air link corresponding to the network device, the network device having an IP address which is longer than the predetermined air link address; and an IP address determination module for determining an IP address corresponding to the predefined air link address from mapping information between the predefined air link addresses and the IP addresses.

An exemplary method of operating an access terminal for communicating information comprises: generating a packet, the packet including a predetermined overhead link address corresponding to a network device, the network device having an IP address which is more

6/49 longer than the predetermined aerial link address and information that must be communicated to the network device; and transmit the generated packet via an aerial link to an access point. Another exemplary method of operating an access terminal comprises: receiving a packet, the packet including a predetermined aerial link address corresponding to a network device, the network device having an IP address that is longer than the aerial link address predetermined and information that must be communicated to the access terminal; and determining from the stored address information and the predetermined air link address included in the received packet, the network device which is the source of information included in the received packet. An exemplary access terminal comprises: a packet generation module for generating packets, the packets including information that must be communicated to a network device and a predetermined overhead link address corresponding to the network device, the network device having an address IP which is longer than the predetermined overhead link address; and a wireless transmitter to transmit the packets generated over an aerial link to an access point.

Although several modalities have been discussed in the above summary, it must be considered that not all modalities necessarily include the same characteristics and some of the characteristics described above are not necessary, but may be desirable in some modalities. Several additional features, modalities and advantages are discussed in the detailed description below.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates a multiple access wireless communication system according to a modality.

7/49

Figure 2 is a block diagram of an exemplary communication system.

Figure 3 illustrates an exemplary network including an access network (AN) architecture distributed over an access terminal (AT).

Figure 4 illustrates an exemplary network including a centralized AN architecture and an AT.

Figure 5 is a flow chart of an exemplary method of operating an access point according to several modalities.

Figure 6 is a flow chart of an exemplary method of operating an access point according to several modalities.

Figure 7 is a drawing of an exemplary access point according to several modalities.

Figure 8 is a flow chart of an exemplary method of operating an access terminal to communicate information.

Figure 9 is a flow chart of an exemplary method of operating an access terminal according to various modalities.

Figure 10 is a drawing of an exemplary access terminal according to various modalities.

DETAILED DESCRIPTION

Wireless communication systems are widely used to provide various types of communication content such as voice, data, and so on. These systems can be multiple access systems capable of supporting communication with multiple users by sharing available system resources (for example, bandwidth and transmission power).

Examples of such multiple access systems include

Interoperability

World for Microwave Access (WiMAX), infrared protocols such as

8/49

Infrared Data (IrDA), short range wireless protocols / technologies, Bluetooth® technology, ZigBee® protocol, ultra-broadband protocol (UWB), native radio frequency (HomeRF), shared wireless access protocol (SWAP), broadband technology such as a wireless Ethernet compatibility association (WECA), wireless fidelity association (WiFi association), 802.11 network technology, public switched telephone network technology, public heterogeneous communication network technology such as the Internet, private wireless communication network, terrestrial mobile radio network, code division multiple access (CDMA), broadband code division multiple access (WCDMA) systems , universal mobile telecommunication system (UMTS), advanced mobile phone service system (AMPS), time division multiple access system (TDMA), frequency division multiple access system (FDMA), orthogonal frequency division multiple access system (OFDMA), global system for mobile communications (GSM), single carrier technology (IX) radio transmission (RTT), data-only evolution technology (EV-DO), service general radio package (GPRS), GSM optimized data environment (EDGE), high-speed downlink data access system (HSPDA), analog and digital satellite systems, and any other technologies / protocols that may be used on at least one of a wireless communication network and a data communication network.

Generally, a wireless multiple access communication system can simultaneously support communication to multiple wireless terminals. Each terminal communicates with only one or more base stations through transmissions on the forward and reverse links. Direct link (or

9/49 downlink) refers to the communication link from the base stations to the terminals, and the reverse link (or uplink) refers to the communication link from the terminals to the base stations. This communication link can be established through a single input, single output, multiple input, single output or multiple input, multiple output (MIMO) system.

With reference to Figure 1, the multiple access wireless communication system according to a modality is illustrated. An access point 100 (AP) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional group including 112 and 114. In Figure 1, only two antennas are shown for each antenna group. however, a greater or lesser number of antennas can be used for each group of antennas. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via direct link 120 and receive information from access terminal 116 via link reverse 118. Access terminal 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal 122 via direct link 126 and receive information from access terminal 122 via reverse link 124. In an FDD system, communication links 118, 120, 124 and 126 can use different frequencies for communication. For example, the direct link

120 you can use a different frequency than the one used by the reverse link 118.

Each group of antennas and / or the area in which they are designated for communication is often referred to as an access point sector. In the modality, groups of antennas are designated for communication with the

10/49 access in a sector of the areas covered

100.

In communication through the access points 120 direct links and

126, the transmission antennas of the access point 100 use beam formation to improve the signal-to-noise ratio of the direct links to the different access terminals 116 and 122. In addition, an access point using beamforming to transmit to access terminals scattered randomly across its coverage area causes less interference to access terminals in neighboring cells than an access point transmitting through its access terminals. access.

An access point used to communicate with those referred to as an access node, a single antenna for all can be a fixed terminal station and can also be a Node B, a base station or some other terminology. An access terminal can also be called an access device, user equipment (UE), wireless communication device, terminal, wireless terminal, mobile terminal, mobile node, endpoint or some other terminology.

Figure 2 is a block diagram of an exemplary access point 210 and an exemplary access terminal 250 in a MIMO 200 system. At access point 210, traffic data for a number of data streams is provided from a data source

212 for a transmission data processor (TX) 214.

In one embodiment, each data stream is transmitted through a respective transmission antenna. The TX 214 data processor formats, encodes, and merges data traffic for each data stream based on a specific coding scheme selected for that data stream to provide data

11/49 coded.

The encoded data for each data stream can be multiplexed with pilot data using OFDM techniques. Pilot data is typically from a known data pattern that is processed in a known manner and that can be used in the receiving system to estimate the channel response. The multiplexed pilot and the encoded data for each data stream are then modulated (ie mapped into symbols) based on a specific modulation scheme (for example, BPSK, QSPK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, encoding, and modulation for each data stream can be determined by the instructions performed by the processor 230.

The modulation symbols for each of the data streams are then provided to a TX MIMO 220 processor, which can additionally process the modulation symbols (for example, for OFDM). The TX MIMO 220 processor then provides N_T modulation symbol streams for N_Ttransmitters (TMTR) 222a to 222t. In certain embodiments, the TX MIMO 220 processor applies beamforming weights to the data stream symbols and the antenna from which the symbol is being transmitted.

Each transmitter (222a, ..., 222t) receives and processes a stream of symbols, respective to provide one or more analog signals, and additionally conditions (for example, enlarges, filters and upwards converts) the analog signals to provide a modulated signal suitable for transmission through the MIMO channel. The N_T signals modulated from transmitters 222a to 222t are then transmitted from N_T antennas 224a to 224t, respectively.

12/49

At the access terminal

250, the modulated signals transmitted are received by the

N_r antennas 252a to 252r and the signal received from each antenna 252 is provided to a respective receiver (RCVR) 254a to 254r. Each receiver

254r) conditions (for example, filters, amplifies, received, digitizes the conditioned signal to provide samples, additionally processes the samples to provide a flow of corresponding received symbols.

An RX 2 60 data processor then receives and processes the N_r symbol streams received from the

N_r receivers (254a, ...,

254r) based on a specific receiver processing technique to provide N_T detected symbol streams. The RX 260 data processor then demodulates, deinterleaves, and decodes each detected symbol stream to retrieve traffic data for the data stream. Processing by the RX 260 data processor is complementary to that performed by the TX MIMO 220 processor and TX 214 data processor in the transmitting system 210.

A processor 270 periodically determines which pre-coding matrix to use (discussed below).

Processor 270 formulates a reverse link message comprising a matrix index portion and a rating value portion.

The reverse link message can comprise various types of information regarding the communication link and / or the flow of data received. The reverse link message is then processed by a data processor

TX 2 38, which also receives the data number of data streams from

236, modulated by a modulator 280, of traffic to a data source conditioned by transmitters 254a to 254r, and transmitted, through

13/49 antennas (252a, 252r), respectively, back to access point 210.

At access point 210, signals modulated from access terminal 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by an RX data processor 242 to extract the transmitted reverse link message by the receiving system 250. The processor 230 then determines which pre-coding matrix to use to determine the beam formation weights, then processes the extracted message.

Memory 232 includes routines and data / information. Processors 230, 220 and / or 242 execute the routines and use the data / information in memory 232 to control the operation of the access point 210 and implement the methods. Memory 272 includes routines and data / information. Processors 270, 260, and / or 238 execute the routines and use the data / information in memory 272 to control the operation of the access terminal 250 and implement the methods.

In one respect, SimpleRAN is designed to significantly simplify communication protocols between the elements of the return transport channel access network in a wireless radio access network, while providing rapid handoff to accommodate the demands of low latency applications. , such as VOIP, in rapidly changing radio conditions.

In one aspect, the network comprises access terminals (AT) and an access network (AN).

AN supports not only a centralized deployment but also a distributed deployment. The network architectures for centralized and distributed deployments are shown in Figure 3 and Figure 4, respectively.

14/49

Figure 3 illustrates an exemplary network 300 including a distributed AN 302 and an AT 303.

In the distributed architecture shown in Figure 3, AN 302 comprises access points (AP) and native agents (HA). AN 302 includes a plurality of access points (APa 304, APb 306, APc 308) and the native agent 310, In addition, AN 302 includes a large amount of IP 312. The APs (304, 306, 308) are coupled to the large amount of IP through links (314, 316, 318), respectively. The large amount of IP 312 is coupled to HA 310 via link 320.

An AP includes one:

Network Function (NC):

o One per AP, and multiple NFs can be serving a single TA.

o A single NF is the IP layer connection point (IAP) for each AT, that is, the NF to which the HA sends packets sent to the AT. In the example in Figure 4, NF 336 is the current IAP for AT 303, as shown by line 322 in Figure 4.

o The IAP can change (L3 handoff) to optimize the routing of packets through the return transport channel to the AT.

o The IAP also performs the role of the session master for the TA. (In some modalities, only the session master can perform the session configuration, or change the session state.) O The NF acts as the controller for each of the TFs in the AP and performs functions such as allocation, management and disconnection of resources for an AT in TF.

Transceiver (TF) or sector functions:

o Multiple per AP, and multiple TFs can serve one

15/49 single AT.

o Provides the air interface connection to the AT.

It can be different for the links, direct and reverse.

<td></td><td>o Muda</td><td>(L2 handoff) with</td><td colspan="2">based on</td><td>conditions</td><td>in</td>

<td></td><td>radio.</td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>In AN</td><td colspan="2">302 APa 304 includes</td><td>NF 324</td><td>, TF 326 and</td><td>TF</td>

<td> 328 .</td><td>On AN 302</td><td>the APb 306 includes the</td><td>NF</td><td>330, a</td><td>TF 332 and the</td><td>TF</td>

<td> 334 .</td><td>On AN 302</td><td>the APc 308 includes the</td><td>NF</td><td>336, the</td><td>TF 338 and the</td><td>TF</td>

<td> 340.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>A T</td><td>includes:</td><td></td><td></td><td></td><td></td>

<img file="BRPI0712410A2_D0002.tif" />

each NF in the active set.

Mobile node (MN) to support layer mobility

IP at the access terminal.

APs communicate using a tunneling protocol defined via IP. The tunnel is an IPem-IP tunnel for the data plane and an L2TP tunnel for the control plane.

Exemplary TA 30 3 includes a plurality of

<td>Interfaces</td><td>(I_a 342, I_b 344,</td><td>I_c 34 6) and MN</td><td> 348 .</td><td>The TA</td><td> 303</td>

<td colspan="4">can be coupled, and sometimes is coupled to the</td><td>AP a</td><td> 304</td>

<td colspan="2">can through the link without</td><td>wire 350. 0 AT</td><td> 303</td><td>can</td><td>to be</td>

<td>coupled,</td><td>and sometimes it is</td><td>coupled to</td><td>AP_b</td><td> 306</td><td>per</td>

<td>intermediate</td><td>wireless link</td><td colspan="2">352. 0 AT 303,</td><td>can</td><td>to be</td>

<td>coupled,</td><td>and sometimes it is</td><td>coupled to</td><td>AP c</td><td> 308</td><td>per</td>

<td>intermediate</td><td>wireless link 354</td><td> •</td><td></td><td></td><td></td>

<td>THE</td><td colspan="2">Figure 4 illustrates a network</td><td colspan="2">exemplary</td><td> 400</td>

including a distributed AN 402 and an AT 403.

Centralized Network Architecture

In a centralized architecture shown in

Figure 4, the NF is no longer logically associated with a single TF, so that the AN comprises network functions, points

16/49 access and native agents. Exemplary AN 402 includes a plurality of NFs (404, 406, 408), a plurality of APs (AP_a 410, AP_b 412, AP_c 414), HA 416 and a large amount of IP 418. NF 404 is coupled with the large amount of IP 418 via link 420. NF 406 is attached to the large amount of IP 418 via link 422. NF 408 is attached to the large amount of IP 418 via link 424. The large amount of IP 418 is

<td>coupled to</td><td>HA 416</td><td>per</td><td colspan="2">intermediate</td><td>from link 426. 2</td><td>X NF</td><td>404 is</td>

<td>coupled to</td><td>(AP_a</td><td> 410,</td><td>AP_b</td><td> 412,</td><td>AP c 414) by</td><td colspan="2">intermediate</td>

<td>of links</td><td> (428,</td><td> 430,</td><td> 432) ,</td><td colspan="2">respectively. THE</td><td>NF</td><td>406 is</td>

<td>coupled to</td><td>(AP_a</td><td> 410,</td><td>AP_b</td><td> 412,</td><td>AP c 414) by</td><td colspan="2">intermediate</td>

<td>of links</td><td> (434,</td><td> 436,</td><td> 438) ,</td><td colspan="2">respectively, A</td><td>NF</td><td>408 is</td>

<td>coupled to</td><td>(AP_a</td><td> 410,</td><td>AP_b</td><td> 412,</td><td>AP c 414) by</td><td colspan="2">intermediate</td>

of the links (440, 442, 444), respectively.

AP_a 410 includes TF 462 and TF 464. AP_b 412 includes TF 466 and TF 468. AP_c 414 includes TF 470 and TF 472.

As an NF acts as the controller for a TF, and any NFs can be logically associated with a single TF, the NF controller for an AT, that is, the NF communicating with an AT as a part of the active set, performs the allocate, manage and disconnect resources for TF in that TA. Therefore, multiple NFs can control resources in a single TF, although these resources are managed independently. In the example in Figure 4, NF 408 is acting as an IAP for AT 403, as shown by line 460.

The rest of the logic functions performed are identical as for the distributed architecture.

Exemplary AT 403 includes several interfaces (I_a 446, I_b 448, I_c 450) and MN 452. AT 403 can be, and is sometimes coupled to the AP at 410 via the link

17/49 wireless 454. The AT 403 can be attached, and sometimes it is attached to the AP_b 412 via the wireless link 456. The AT 403 can be attached, and sometimes it is attached to the AP_c 414 via the wireless link 458 thread.

In systems such as DO and 802.20, an AT obtains service from an AP by attempting to access an access channel in a specific sector (TF). The NF associated with the TF receiving the access attempt contacts the IAP that is the session master for the TA and retrieves a copy of the TA session. (The TA indicates the identity of the IAP by including a UATI in the access payload. UATI can be used as an IP address to directly address the IAP, or it can be used to query the IAP address.) In a successful access attempt, the TA is assigned air interface resources such as a MAC ID and channel data to communicate with that sector.

Additionally, the TA can send a report indicating the other sectors that it can hear and their signal strengths. TF receives the report and sends it to a network-based controller in the NF, which in turn provides the TA with an active set. For DO and 802.20 in the way they are currently implemented, there is exactly one NF with which the AT can communicate (except during an NF handoff when there are two temporarily). Each of the TFs in communication with the TA will send the received data and signal to that single NF. This NF also acts as a network-based controller for the TA and is responsible for negotiating and managing the allocation and disconnection of resources for the TA for use with the sectors in the active set.

active set, therefore, is the set of sectors in which the TA is allocated

18/49 overhead interface. The AT will continue to send periodic reports and the network-based controller can add or remove sectors from the active set as the AT moves around the network.

NFs in the active pool will also fetch a local copy of the session for the TA when they join the active pool. The session is necessary to properly communicate with the TA.

For an aerial CDMA link with soft handoff, in the uplink each of the sectors in the active set can try to decode an AT transmission. In the downlink, each of the sectors in the active set can transmit to the AT simultaneously, and the AT combines the transmissions received to decode the packet.

For an OFDMA system, or a system without a soft handoff, a function of the active set is to allow the TA to change quickly between sectors in the active set and maintain the service without having to make a new access attempt. An access attempt is generally much slower than switching between members of the active set, since members of the active set already have the session and air interface resources assigned to the TA. Therefore, an active set is useful to perform a handoff without affecting the QoS service of active applications.

When an AT and the session master in the IAP negotiate the attributes, or alternatively the state of the connection changes, the new values ​​for the attributes or the new state needed to be distributed to each of the sectors in the active set in a timely manner for ensure optimum service from each sector. In some cases, for example, if you change the header type, or if you change the security keys, an AT may not be able to communicate with a sector at all until these

19/49 changes are propagated to that sector. Therefore, each member of the active set must be updated when the session changes.

Some changes may be less crucial to synchronize than others.

There are three main types of found on the network for an AT that has

Data state between the AT's compactor state and data state or an active context connection:

data is the state the IAP in an NF includes header things or states are very dynamic and difficult session state is control between the AT and the IAP connection is attributes attributes received closed.

that are affect those by the OT.

on the network during a RLP flow state such as which to transfer.

the network status in the route that is retained when a session state includes the value of those negotiated between the TA and the IAP. These connection and service characteristics

For example, an AT can negotiate the QoS configuration for a filter and specification requirements. Example QoS service headers

AT can be used in a new session set.

The state control path of the new application and providing a new filter to negotiate the communication attributes is the connection between the AT and the network indicating the application.

Like another size and the type of with AN. The negotiation defined as a preserved change when a connection closes the connection state can include such a power control loop, the state

IAP or one on the network at

NF that is not and the TA is inactive. 0 information such as soft handoff timing values, and active set information.

In an IAP or L3 handoff, the three types of states may need to be transferred between the old and the new IAP

IAP. If only an inactive TA can make an L3 handoff,

20/49 then only the session state needs to be transferred. To support L3 handoff for an active AT, data and connection status must also be transferred.

Systems such as DO and 802.20, make the L3 data state handoff simple by defining multiple routes (or data stacks), where the data state for each route is local to that route, that is, each of the routes has been data independent. By associating each IAP with a different route, the data state does not need to be transferred in a handoff. An even better additional step is to increase each NF with a different route, in which case L3 handoff is completely transparent to the data state, except for possible reordering of packets.

As the data state has multiple routes, the next logical step to support L3 handoff for an active AT is to move control of the connection state from the IAP and make the same location for each NF in the active set. This is done by defining multiple control routes (or control cells) and defining the air interface so that the control cells are independent and local in relation to each NC. This may require that part of the negotiation and management of resource allocation and disconnection in the connection state be transferred to the AT since there is no longer a single NF to manage all members of the active set. This may also make some additional requirements in relation to your air interface model to avoid a fair coupling between TFs - since different TFs may not share the same NF - in the active set. For example, to operate optimally, it is preferable to eliminate all fair synchronization between TFs that do not have the same NC, such as power control loops, soft handoff, etc.

21/49

Pushing the connection state and data to the NFs eliminates the need to transfer that state into an L3 handoff, and should also make the NF to NF interface simpler.

The system therefore defines multiple, independent control and data stacks (called interfaces in Figure 3 and Figure 4) in the TA to communicate with different NFs as needed, as well as addressing mechanisms for the TA and TFs to distinguish logically between these stacks.

Fundamentally, some session state (QoS profile, security keys, attribute values, etc.) cannot be done locally for an NF (or IAP) because it is very expensive to deny each time there is an NF handoff (or an L3). In addition, the session state is relatively static and easy to transfer. What is needed are mechanisms to manage and update the session state as it changes and during the IAP handoff where the session master moves.

Optimizing the transfer of session state to L3 handoff is a useful feature for each system regardless of the network architecture as it simplifies network interfaces and should also improve the handoff continuity property.

A more related separate problem is the L3 handoff AT control. Currently, in systems like DO and 802.20, the AT is aware of the L3 handoff since it allocates and disconnects the local batteries, but has no control over when the L3 handoff occurs. This is called network-based mobility management. The question is: make the TA the handoff controller, that is, use mobility management based on TA?

To support fault tolerance and balance of

22/49 load, the network needs to either be able to make the handoff or have a mechanism to signal to the TA to make a handoff. So if AT-based mobility management is used, the network still needs a mechanism to indicate when this should happen.

AT-based mobility management has some obvious advantages, such as allowing a single mechanism for inter- and intra-technology, or global and local mobility. It also simplifies network interfaces further by not requiring network elements to determine when to handoff.

The main reason that systems like DO and 802.20 use network-based mobility is that AT-based mobility is not optimized to work quickly enough to support voice. A secondary reason is the tunneling overhead introduced by determining the mobile IP tunnels (for MIPv6) in the AT. The mobility latency can be solved by sending the data using tunnels between the current and previous direct link server sector, as well as possibly using bicasting, where the data is sent to multiple NFs in the active set, simultaneously.

In SimpleRAN, there are two types of handoff. For example, Layer 2 or L2 handoff refers to the change of the direct link or reverse link (TF) server sector and L3 handoff refers to the change of the IAP. L2 handoff should be as fast as possible in response to changing radio conditions. Systems like DO and 802.20 use PHY layer signaling to make the L2 handoff fast.

L2 handoff is the transfer from the TF server sector to the links, direct (FL) or reverse (RL). A handoff occurs when the TA selects a new server sector in the active pool based on the RF conditions seen in the TA

23/49 for that sector. The AT performs filtered measurements on the RF conditions for the links, direct and reverse, for all sectors in the active set. For example, in 802.20 for the direct link the AT can measure the SINR in the acquisition pilots, in the common pilot channel (if present), and the pilots in the shared signaling channel, to select their desired FL server sector. For the reverse link, the TA estimates the CQI erase rate for each sector in the active set based on the up / down power control commands in the TA from the sector.

L2 handoff is initiated when the AT requests a different FL or RL server sector through a reverse link control channel. Dedicated resources are allocated to a TF when it is included in the active pool for an AT. TF is already configured to support AT before the handoff request. The target server sector detects the handoff request and completes the handoff with the allocation of traffic resources to the TA. The direct link TF handoff requires a round-trip message exchange between the originating TF or IAP and the target TF to receive data for the target TF to transmit. For reverse link TF handoff, the target TF can immediately allocate resources to the TA.

L3 handoff is the transfer from IAP. L3 handoff involves updating the HA link with a new IAP and requires a session transfer to the new IAP for the control plan. L3 handoff is asynchronous in relation to L2 handoff in the system so that L2 handoff is not limited by the MIPv6 handoff signaling speed.

L3 handoff is supported by the air in the system by defining an independent route for each NF. Each stream provides multiple routes for transmitting and receiving upper layer packets. The route indicates which

24/49

NF processed the package. For example, an NF can be associated with TF and over the air as Route A, while another NF can be associated with Route B. A TF server can simultaneously send packets to an AT from not only Route A but also Route B, that is, from both NFs, using a separate and different sequence space for each one.

There are two fundamental ideas in the system model to guarantee the QoS treatment for a mobile device and its traffic is retained through each handoff mode: L2 decoupling and L3 handoff.

Reserve air interface resources and fetch the session from the target NF or TF before the handoff occurs to minimize data flow interruption during the handoff. This is done by adding the target TF and NF to the active set.

The system is designed for separate L2 and L3 handoffs to allow the system to support EF traffic during high L2 handoff rates. L3 handoff requires a link update, which is limited to a rate of 2 to 3 per second. To allow a faster rate of L2 handoff from 20 to 30 Hz, L2 and L3 handoff are designed to be independent and asynchronous.

For L2 handoff, active set management allows all TFs in the active set to be configured and dedicated resources to be allocated so that they are ready to serve the TA in the case of an L2 handoff.

Consider a Mobile Wireless Communication System with multiple access points (AP) that provide service to the access terminals (AT). Many systems have an active set, which is a set of APs that have resources assigned to the TA. At any given time, an TA

25/49 can be within the radio communication range with one of the APs, or for the purpose of optimizing battery power and reducing radio interference, it can only communicate with a carefully selected AP (server AP). The problem considered here is the delivery of messages and data between the various APs in the system, detailing how the server AP can deliver messages to and from the TA. APs can exchange data through an L2TP tunnel (layer two tunneling protocol). If ο AP1 has to send a message or data to the AT, while AP2 is the server AP, then AP1 first uses the L2TP tunnel to deliver the packet to AP2, and ο AP2 delivers that packet to the AT using a mechanism including use of an identifier bit, for example, a reprocessing bit. Similarly, if the AT has to send a message or data to ο AP1, while ο AP2 is serving, it sends the message to AP2 with a set of remote bits, and ο AP2 sends that packet to ο AP1 through the L2TP tunnel.

The L2TP header includes the following fields

1. UserlD: This is the address of the user to which the L2TP packet is addressed.

2. ForwardOrReverse: This field identifies whether the AT is the destination or the source of the packet.

3. FlowID: In a model, this field can only be present in direct link packets (packets destined for the AT), and it identifies the flow that the server AP must use to deliver the packet to the AT.

4. SecurityField: In a model, this field can be present only in reverse link packets (packets originated in the AT). SecurityField can include an IsSecure bit,

26/49 a Keylndex field (to identify the keys used for security operation) and a CryptoSync field.

In one aspect, L2TP direct link packets are communicated. We describe here the process used by an AP to send and receive a direct link L2TP packet.

An AP sends a direct link L2TP packet when it has the data or a message to send to the AT. The AP forms the appropriate header and sends the L2TP packet to the server AP (or it does not know the identity of the server AP, possibly by forwarding the packet through a central node - the IAP).

When an AP receives a direct link L2TP packet, it performs the following steps

1. If the AP is not serving the specified UserlD (in the L2TP header), it sends the packet to the current server AP (possibly by forwarding the packet through a central node - the IAP)

2. If the AP is serving the determined UserlD, it delivers the packet to the AP using the RLP flow and the associated QoS attributes for the determined FlowID (in the L2TP header).

In one respect, L2TP reverse link packets are communicated. Here we describe the process used by an AP to send and receive a reverse link L2TP packet.

An AP sends an L2TP reverse link packet when it receives a packet from the AP, and the remote bit is set for that packet. The first step for the AP sending the L2TP packet is address determination.

Address Determination: If the remote bit for the packet is set, the packet also includes a field for

<img file="BRPI0712410A2_D0003.tif" />

<img file="BRPI0712410A2_D0004.tif" />

<img file="BRPI0712410A2_D0005.tif" />

<img file="BRPI0712410A2_D0006.tif" />

<img file="BRPI0712410A2_D0007.tif" />

<td>Address</td><td>for</td><td>identifies</td><td>which AP this package should</td><td>to be</td>

<td>delivered</td><td>(AP</td><td>target). 0</td><td>Receiving AP maps champion</td><td>is from</td>

<td>Address</td><td>for</td><td>the address</td><td>AP's IP. This mapping can</td><td>to be</td>

<td colspan="3">established by</td><td></td><td></td>

<td></td><td> 1.</td><td>One method</td><td>assisted by AT in which</td><td>at</td>

<td></td><td></td><td>posts</td><td>describing a mapping</td><td>are</td>

<td></td><td></td><td>sent to</td><td>from the TA to the AP,</td><td>and the</td>

<td></td><td></td><td>information</td><td>mapping is then used</td><td>fur</td>

<td></td><td></td><td colspan="3">AP for mapping between the address used</td>

through the aerial link and the IP address.

2. A network-assisted method by which the mapping information provided by a central entity or the target AP is used.

3. PilotPN-based method. In this case, the address field can simply be the same as the PilotPN (or some higher bits of PilotPN) of the AP corresponding to the address. The receiving AP knows the PilotPN and the IP addresses of all contiguous APs as part of the network configuration (which itself can be assisted by the network) and uses this information to map between the PN-based address and the corresponding IP address.

. An IAP address method where a special address type is used by the AT to identify the AP which is the internet coupling point for the AT. Each AP in an active set of APs corresponding to an AT knows the IP address of the IAP for the specific AT and can map between the IAP address and the IP address of the IAP of the AT.

After determining the address, the AP sending the L2TP packet can also insert fields related to the

28/49 security if necessary, and as determined by the security model.

When an AP receives an L2TP reverse link packet, it performs the following steps

1. If the AP is not serving the given User ID specified in a received packet (in the L2TP tunnel), it ignores the packet.

2. If the AP is serving the UserlD determined from the received packet, it processes the packet as if the packet was received from its own MAC layer. The processing of the packet may depend on the SecurityField received in the L2TP tunnel.

Figure 5 is a flow chart 500 of an exemplary method of operating an access point according to various modalities. The operation starts at step 502 where the access point is powered on and initialized and proceeds to step 504.

In step 504, the access point receives a first packet communicated from an access terminal from an aerial link. The first packet including information that must be communicated to a network device and a predefined air link address corresponding to the network device, the network device having an IP address which is longer than the predetermined air link address. The operation proceeds from step 504 to step 506.

In step 506, the access terminal determines an IP address corresponding to the predetermined air link address from mapping information between the predetermined air link addresses and the IP addresses. In several ways, determining an IP address corresponding to the predefined air link address includes

29/49 access a database including information by mapping predefined aerial link addresses to IP addresses of network devices. In some embodiments, the step of determining an IP address corresponding to the predefined air link address is performed as an information function identifying the access terminal from which the first packet was received, the information mapping the predefined air link addresses to IP addresses including information mapping a predefined air link address to different IP addresses depending on the source of the packet that included the predefined mapping.

In many ways, the default address is an Internet Docking Point (IAP) address. In some embodiments, the default address is a session controller address. In some embodiments, the predefined aerial link addresses are reserved addresses and at least one of the predefined aerial link addresses in the database is short or shorter than any other address used by the access terminal via an aerial link. In an exemplary mode, at least one of the predefined addresses includes a maximum of two bits. The operation proceeds from step 506 to step 508.

In step 508, the access terminal transmits a second packet addressed to the network device, the second packet transmitted including the determined IP address and the information that must be communicated to the network device.

Figure 6 is a flow chart 60 0 of an exemplary method of operating an access point according to various modalities. The operation starts at step 602, where the access terminal is powered on and initialized and proceeds to step 604. In step 604, the access point receives a first packet including information from a communication link with a network device. that should be

30/49 communicated to an access terminal and a network device IP address indicating the source of the information.

operation proceeds from step 604 to step 606.

In the step

606, the access terminal determines a predefined air link address corresponding to the network device address from the information mapping between predefined air link addresses and addresses

IP, the predefined air link addresses being shorter than the IP addresses. In several embodiments, the step of determining an IP address corresponding to the predefined air link address includes accessing the stored information including information by mapping the IP addresses of network devices to predetermined air link addresses. In such modalities, the information stored indicates a mapping of multiple network devices of the same type because it has different IP addresses for the same predetermined aerial link address. In some embodiments, the default address is an Internet Docking Point address. In some embodiments, the default address is a session controller address. In various modalities, the predefined aerial link addresses are reserved addresses, at least one of the predefined addresses being as short or shorter than any other address used by the access terminal via an aerial link. In an exemplary mode, at least one of the predefined addresses includes a maximum of two bits. The operation proceeds from step 606 to step 608.

In step 608, the access point transmits, via an aerial link, a second packet to the access terminal, the second transmitted packet including the predefined predefined air link address and the information that must be communicated to the access terminal.

31/49

Figure 7 is a drawing of an exemplary access point 700 according to various modalities. Exemplary access point 700 includes a wireless receiver module 702, a wireless transmitter module 704, a processor 706, a network interface module 708, and memory 710, which are coupled together via a 712 bus through which the various elements can exchange data and information. Memory 710 includes routines 718 and data / information 720. 0 706 processor for example a

CPU, performs routines 718 and uses data / information 720 in memory 710 to control the operation of the access point and implement methods, for example, a method according to flowchart 500 in Figure 5 and / or flowchart 600 in Figure 6.

The wireless receiver module 72, for example, an OFDM and / or CDMA receiver, is coupled to the receiving antenna 714 through which the access point receives uplink signals from the access terminals. The wireless receiver module 702 receives a packet from an access terminal, the received packet including information that must be communicated to a network device and a predefined air link address corresponding to the network device, the network device having a IP address which is longer than the predefined air link address. The packet received from AT 734 is an example of a packet received via wireless receiver module 702.

The wireless transmitter module 704, for example, an OFDM and / or CDMA transmitter, is coupled to the transmission antenna 716 through which the access point transmits downlink signals to the access terminals. The wireless transmitter module 704 transmits downlink packets to the ATs via a wireless communication link.

32/49

Exemplary generated packet addressed to an AT 740 is a packet transmitted by the wireless transmitter module 704.

In some embodiments, multiple antennas and / or multiple antenna elements are used for reception. In some embodiments, multiple antennas and / or multiple antenna elements are used for transmission. In some embodiments, at least some of the same antennas or antenna elements are used not only for transmission but also for reception. In some modalities, the access point uses MIMO techniques.

The network interface module 708 couples the access point 700 to other network nodes, for example, other access points, nós nodes, native agent nodes, etc., and / or the Internet can through the network link 709 The network interface module 708 includes a transmitter module 711 and a receiver module 713. 0 transmitter module 711, for example, a return transport channel network transmitter, transmits a packet directed to a network device, the packet transmitted including a given IP address and information that must be communicated to the network device. For example, transmitter module 711 transmits the generated packet addressed to network device 736. The receiver module 713, for example, a return transport channel network receiver, receives from a communication link with a network device, a packet including information that must be communicated to an access terminal and an IP address network device indicating the source of the information. The packet received from the network device 738 is such an exemplary packet received via the receiver module 713.

Routines 718 include an IP address determination module 722, an access terminal identification module 724 and a network packet generation module 726,

33/49 an aerial link address determination module 727, and an aerial link packet generation module 728. Data / information 720 includes an address information database 730, access terminal status information 732, a packet received from an access terminal 734, a generated packet directed to a network device 736, a packet received from a network device 738 and a generated packet directed to an access terminal 740.

The address information database 730 includes address information corresponding to a plurality of different types of network devices (network device information 1 742, ..., network device information 744). The address information database 73 0, which is coupled to the IP address determination module 722, includes information mapping between the predefined air link addresses and the IP addresses of the network devices. The address information database 730 is also coupled to the overhead link determination module 727. Network device information 1 742, for example, Internet Coupling Point (IAP) information, includes an address of predefined aerial link 746, access terminal identification information (AT ID information 748,..., AT ID number information 7 52) and IP address information (IP address 750,..., IP address 754). Corresponding to network device 1, for example, an IAP, each of the ATs identified by (AT ID 1 748, ..., AT ID N 752) uses the same predefined air link address 746. However, the address predefined overhead link 746 can match, and sometimes does, different IP addresses. For the AT identified by AT ID 748, the default air link address 746 corresponds to the

34/49 IP address 750, while for the AT identified by the ID N of AT 752, the predefined air link address 746 corresponds to the IP address 754. IP addresses 750 and 754 can be and sometimes are different. Device number 744, for example, Session Controller information, includes a predefined overhead link address 756, access terminal identification information (AT 758 ID 1 information, ..., ID information AT No. 7 62) and IP address information (IP address 760, ..., IP address 764). Corresponding to network device n, for example, a Session Controller, each of the ATs identified by (ID 1 of AT 758, ..., ID N of AT 762) uses the same predefined overhead link address 756. However, the predefined overhead link address 756 can match, and sometimes matches different IP addresses. For the AT identified by the ID 1 of AT 758, the default air link address 756 corresponds to the IP address 7 60, while for the AT identified by the ID N of AT 762, the default air link address 756 corresponds to the IP address 764 IP addresses 760 and 764 can be and are sometimes different.

In some embodiments, the predefined air link addresses are reserved addresses. In some such modalities, at least one of the predefined aerial link addresses in the 730 database is short or shorter than any other address used by the access terminal via an aerial link.

Access terminal status information 732 includes status information corresponding to a plurality of different access terminals (access terminal 1 status information 766, ..., access N terminal status information 768).

The package received from a terminal

35/49 access 734 includes a predefined overhead link address 770 and information that must be communicated to a network device 772. The generated packet addressed to a network device 736 includes an IP address 774 and information for the network device 776.

packet received from a network device 738 includes an IP address 778 and information for an access terminal 780. The generated packet addressed to an access terminal 740 includes a predefined overhead link address 782 and information directed to an access terminal 784.

The IP address determination module 722 determines an IP address corresponding to a predefined air link address from information mapping between predefined air link addresses and IP addresses. For example, the IP address determination module 722 determines the address

IP

774 from the predefined air link address 770 to the address information database 730.

An access terminal identification module 724 provides information identifying the access terminal from which a packet was received, for the IP address determination module 722, the IP address determination module determining an IP address corresponding to the IP address. predefined aerial link as a function of the information identifying the access terminal. Ά information mapping predefined air link addresses to IP addresses includes information mapping a predefined air link address to different IP addresses depending on the source of the packet that included the predefined address and information. For example, if the source of the packet received from the AT 734 was the access terminal identified by ID 1 of the AT 748 and the default air link address was the

36/49 predefined overhead link address 746, so the IP address is the IP address 750; however, if the source of the packet received from the AT 734 was the access terminal identified by the ID N of AT 752 and the default air link address was the default air link address 746, then the IP address is the IP address 754 .

The air link address determination module 727 determines a predefined air link address corresponding to a network device from information mapping between predefined air link addresses and IP addresses, the predefined air link address being shorter than the IP address. For example, the air link address determination module 727, determines the predefined air link address 782 that should be used in the generated packet addressed to the AT 740 from the IP address 778 of the packet received from the network device 738 and mapping the information in the address information database 730 corresponding to the AT to which the packet is addressed.

aerial link packet generation module 728 generates packets to be transmitted over an air link, the generated packets including a predetermined aerial link address corresponding to a network device, for example, the network device which is the source of the information being carried by the packet. The generated package addressed to the AT 740 is an exemplary package generated by the 728 overhead link generation module. The network packet generation module 726 generates packets directed to a network device, for example, an access terminal serving as an IAP for an access terminal or a session controller for an AT. The generated packet directed to the network device 736 is an exemplary packet generated by the network packet generation module 726. The

37/49 network packet generation 726 uses an IP address determined by the address determination module 722 when generating a packet, for example, packet 736.

Figure 8 is a flow chart 800 of an exemplary method of operating an access terminal to communicate information. The operation starts at step 802, where the access terminal is connected and initialized and proceeds to step 804. In step 804, the access terminal generates a packet, the packet including a predefined air link address corresponding to a network device, the network device having an IP address which is no longer than the predetermined air link address and information that must be communicated to the network device. In some embodiments, the generated package is a MAC package. Step 804 includes sub-steps 806 and 808. In sub-step 806, the access terminal selects from a set of pre-defined, stored aerial link addresses, the address corresponding to the network device to which the information is to be communicated. Then, in sub-step 808, the access terminal places the selected predefined air link address in a destination field of a packet header.

In some embodiments, the predefined aerial link addresses are reserved addresses and at least one of the predefined aerial link addresses in the stored set is shorter than any other addresses used by the access terminal via an aerial link. In some embodiments, the network device can, and is sometimes, an Internet Docking Point used by the access terminal to gain access to the network. In some embodiments, the network device is a session controller used to control the communication session in which the access terminal is a participant.

38/49

In some embodiments, the predetermined air link address used by the access terminal to communicate with the network device is identical to the predefined air link address used by other access terminals to communicate with other network devices, and the generated packet includes an access terminal identifier used by a receiving device in combination with the predefined air link address to determine the IP address of the network device to which the information in the packet is being communicated. In some embodiments, the network device is a session controller used to control the communication session in which the access terminal is a participant. In various embodiments, the network devices which are accessed by different access terminals using the same predefined address are the same type of network device.

The operation proceeds from step 804 to step 810. In step 810 the access terminal transmits the generated packet via an aerial link to an access point.

In one embodiment, the network device is an Internet Connection Point (IAP) and when you change the IAP to the access terminal, due to a change in position or a network consideration, the reserved address used by the access terminal for access the current Internet Connection Point of the AT remains the same, but the mapping between the reserved address and the IP of the current IAP to the AT changes when the access terminal changes the Internet Connection Points. Thus, in some modalities, a reserved aerial link address, for example, a reserved aerial link address for IAP functionality, used by an AT can be viewed from the AT's perspective as a virtual address which can be associated, and

39/49 is sometimes associated with different physical devices at different times, for example, different physical devices serving the same function for the TA. In

<td>some</td><td colspan="2">modalities,</td><td>O</td><td>AT</td><td>it doesn't have to be,</td><td colspan="2">and it is not</td>

<td>aware &lt;</td><td>of</td><td>Address</td><td>IP</td><td>of</td><td>Current IAP for</td><td>AT in</td><td>one</td>

<td colspan="2">determined</td><td>time.</td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>THE</td><td>Figure 9</td><td>is</td><td>one</td><td colspan="2">flowchart 900 of a method</td><td>in</td>

<td>operation</td><td>ex</td><td>emplar of</td><td>one</td><td colspan="2">access terminal</td><td>wake up</td><td>with</td>

various modalities. The operation starts at step 902 where the access terminal is powered on and initialized and proceeds to step 904. In step 904, the access terminal receives a packet, for example, a MAC packet, the packet including a predetermined overhead link address corresponding to a network device, the network device having an IP address which is longer than the predetermined over-the-air link address and information that must be communicated to the access terminal. The operation proceeds from step 904 to step 906. In step 906 the access terminal determines from the stored address information the predetermined air link address included in the received packet. The network device with the source of the information included in the received packet.

The operation proceeds from step 906 to step 908. In step 908, the access terminal processes the received packet in a way that depends on which network device is determined to be the source of the information included in the received packet, processing including driving the information for a software module inside the access terminal that processes messages received from the given network device.

In some embodiments, the received packet includes the predetermined air link address in a source field of a packet header included in the packet

40/49 received. In several embodiments, the predetermined aerial link address is a reserved address, the predetermined aerial link address being as short or shorter than any other addresses used by the access terminal via an aerial link. In this mode, the default address includes a maximum of two bits.

In some embodiments, the network address is an Internet Docking Point used by the access terminal to gain access to the network. In various embodiments, the predetermined aerial link address used by the access terminal to communicate with the network device is the same as the predefined aerial link address used by other access terminals to access other network devices. In some of these modalities, the network device and the other network devices are Internet Connection Points.

In various embodiments, the network device is a session controller used to control communication sessions in which the access terminal is a participant.

Figure 10 is a drawing of an exemplary access terminal 1000 according to various modalities. The exemplary access terminal 1000 can communicate, and sometimes communicates the information to a remote device via an access point. 0 exemplary access terminal 1000 includes a wireless receiver module 1002, a wireless transmitter module 1004, a processor 1006, user I / O devices 1008 and memory 1010 coupled together via a bus 1012 through which the various elements can exchange data and information. Memory 1010 includes routines 1018 and data / information 1020. Processor 1006, for example, a CPU, executes routines 1018 and uses data / information 1020 in memory 1010

41/49 to control the operation of the access terminal and implements the methods, for example, the flowchart 800 methods in Figure 8 and flowchart 900 in Figure 9.

The wireless receiver module 1002, for example, a CDMA or OFDM receiver, is coupled to the receiving antenna 1014 through which the access terminal 1000 receives downlink signals from the access points. The receiving module 1002 receives a packet including a predetermined overhead link address received corresponding to a communication network device, for example, received packet 1050.

The wireless transmitter module 1004, for example, a CDMA or OFDM transmitter, is coupled to the transmitting antenna 1016 through which the access terminal 1000 transmits the uplink signals to the access points. The wireless transmitter module 1004 transmits the generated packets, for example, the generated packet 1034, over an aerial link to an access point.

In some embodiments, the same antenna is used for transmission and reception. In some embodiments, multiple antennas and / or multiple antenna elements are used for reception. In some embodiments, multiple antennas and / or multiple antenna elements are used for transmission. In some embodiments, at least some of the same antennas or antenna elements are used not only for transmission but also for reception. In some modalities, the access terminal uses MIMO techniques.

User I / OU devices 1008 include, for example, microphone, keyboard, compact keyboard, switches, camera, speaker, video, etc. User I / O devices 1008 allow a user of access terminal 1000 to enter data / information, access data / information from

42/49 output, and control at least some functions of the access terminal

1000, for example, start a communication session with a non-hierarchical node, for example, another access terminal.

Routines 1018 include a packet generation module

1022, an address determination module 1024, a device identification module 1026, a plurality of software modules corresponding to different network devices (software module for network device 1 1028, for example,

AT IAP, ..

software module for network device N 1030 (eg, AT session controller) and a packet processing module 1032. Data / information 1020 includes a generated packet addressed to a network device 1034, a set of predefined air link addresses corresponding to the 1040 network devices, and a received packet including information from a 1050 network device. The generated packet directed to a network device 1034 includes a predetermined overhead link address corresponding to network device 1036 and information that must be communicated to network device 1030. The set of predefined air link addresses corresponding to the 1040 network devices includes several different predefined air link addresses associated with different network devices (network device 1, for example, AT IAP, information 1042, ... , network node device, e.g., AT session controller, information 1046). The network device 1, for example, IAP information of the AT 1042 includes predefined air link address 1 1044, while the network device, for example, AT session controller, information 1046 includes the predefined air link address n 1048.

In some modalities the aerial link addresses

Predefined 43/49 are reserved addresses, and at least one of the predefined aerial link addresses in the stored set of aerial link addresses 1040 is as short or shorter than any other addresses used by the access terminal via the same link access address. others an aerial link. In various modalities, pre-defined aerial used by terminal one of

1000 for communication with a network device is what the terminal address of network devices.

generated access packet is used with the IP address of the predefined overhead link used by access to communicate with others

In some of these embodiments, one including a terminal identifier by a receiving device in combination of a predefined aerial link to the network device to which it will be communicated. In several embodiments, determine the packet must the other network devices are of the same type as the network device as that of the terminal device network access device to which the packet from

1000 is directed.

For example, the network to which the access 1000 is, while the corresponding corresponds to the access;

can packet from the directed terminal, for example, it is the IAP of the AT 1000, other network devices can be different IAPs in the system.

same type, however match them

IAPs can therefore

Example IAPs, IAPs corresponding to a few different physical devices.

In several modalities, the

Internet coupling point, changes due to access, and different points are sometimes the network device is one and the IAP, for the AT 1000, a change in the location of the access terminal to map the reserved address used by the communicate with the IAP remains the same terminal, but the between the reserved address and the IP addresses, for example, at an access point in the system, changes when

44/49 the access terminal changes the Internet Docking Point. In several ways, the network device is an Internet Docking Point, and the IAP, for the AT 1000, changes due to a change in network considerations, for example, loading problems, device failure problems, routing, reserved address used by the access terminal to communicate with the

TA IAP remains the same, but mapping between the reserved address and the addresses

IP, for example, on an access point in the system, changes when the internet connection point of the access terminal is changed. In some modalities, the access terminal 1000 is unaware of the IP address corresponding to your IAP and / or is unaware of the network-based changes in the IAP, for example, the access terminal 1000 uses the same predefined overhead link address for communicate with your currently assigned IAP, with whatever physical device in the system may match.

received packet including information from the network device 1050 includes a source header field 1052 and information to be communicated to the AT 1054. In some embodiments the received packet 1050 is a MAC packet. The packet header source field 1052 includes a predetermined air link address corresponding to a 1056 network device, for example, one of the set of predefined air link addresses (predefined air link address 1 1044, ..., address predefined aerial link number 1048).

The packet generation module 1022 generates packets including information that must be communicated to a network device and a predetermined overhead link address corresponding to the network device, the network device having an IP address which is more

45/49 longer than the predetermined overhead link address. The generated packet addressed to the 1034 network device is an exemplary packet generated by the 1022 packet generation module. In some embodiments, the generated packets are MAC packets.

address determination module 1024 selects the predetermined aerial link address corresponding to the network device with which the access terminal seeks to communicate information from the set of predefined, stored aerial link addresses included in the 1040 information and provides the selected address to the 1022 package generation module. For example, if the TA wants to communicate information to the TA's IAP, the address determination module selects address 1 from the predefined overhead link 1044 and sends that selected address to the 1022 packet generation module, where the packet includes the address in a generated packet, for example, defines the predetermined overhead link address corresponding to the network device 1036 to the predefined overhead link address 1044 for the generated packet 1034.

The device identification module 1026 determines from the set of predetermined aerial link addresses (1044, ..., 1048) and the predetermined aerial link address includes in a received packet, for example, the predetermined aerial link address 1056 in the received packet 1050, the network device which is the source of the information included in the received packet. For example, device identification module 1026 determines that the source of information 1054 in packet 1050 is the network device that is the current IAP of the AT or is the network device that is the current session controller of the AT.

The software module 1028 processes messages to

46/49 from network device 1, for example, messages to

TA IAP. The software module 1030 processes messages from network device n, for example, messages from the session controller of the AT.

packet processing module 1032 processes a received packet in a way that depends on which network device is determined to be the source of information included in the received packet, processing including directing the information to one of the access terminal 1000 modules that processes messages received from the specified network device.

In various modalities, the nodes described here are implemented using one or more modules to perform the steps corresponding to one or more methods of the aspect, for example, signal processing, message generation and / or transmission steps.

Thus, in some modalities, several characteristics are implemented using modules.

Such modules can be implemented using software, hardware or a combination of software and hardware.

Many of the methods described above or steps in the method can be implemented using machine-executable instructions, such as software, included in a machine-readable medium such as a memory device, for example, RAM, floppy, compact disc, DVD, etc. , to control a machine, for example, a computer in common use with or without additional hardware, to implement all or portions of the methods described above, for example, on one or more nodes. Consequently, among other things, the aspect is directed to a machine-readable medium including instructions executable by machine to make a machine, for example, processor and associated hardware, perform one or more of the steps of the

47/49 method (s) described above.

In various modalities, the nodes described here are implemented using one or more modules to perform the steps corresponding to one or more methods, for example, signal processing, message generation and / or transmission steps. Some exemplary steps include transmitting a connection request, receiving a connection response, updating a set of information indicating an access point with which an access terminal has an active connection, sending a connection request, sending a connection response, determining resource allocation, requesting resources, updating resources, etc. In some modalities, several features are implemented using the modules. Such modules can be implemented using software, hardware or a combination of software and hardware. Many of the methods described above or method steps can be implemented using machine-executable instructions, such as software, included in a machine-readable medium such as a memory device, for example, RAM, floppy disk, laser disk, DVD, etc. . to control a machine, for example, a computer in common use with or without additional hardware, to implement all or portions of the methods described above, for example, on one or more nodes. Consequently, among other things, several modalities are directed at a machine-readable medium including instructions executable by machine to make a machine, for example, processor and associated hardware, perform one or more of the steps of the method (s) described above.

In some embodiments, the processor or processors, for example, CPUs, of one or more devices, for example, communication devices such as access terminals and / or access points, are

48/49 configured to perform the steps of the methods described as being performed by the communication device. The processor configuration can be performed using one or more modules, for example, software modules, to control the processor configuration and / or by including hardware in the processor, for example, hardware modules, to perform the mentioned steps and / or control processor configuration. Consequently, some, but not all modalities are directed to a device, for example, a communication device, with a processor which includes a module corresponding to each of the steps of the various methods described performed by the device in which the processor is included. In some, but not all modalities, a device, for example, a communication device, includes a module corresponding to each of the steps of the various methods described performed by the device in which the processor is included. The modules can be implemented using software and / or hardware.

Several additional variations in the methods and equipment described above will be evident to those skilled in the art in light of the above descriptions. Such variations must be considered within the scope. The methods and equipment of the various modalities can be, and in various modalities, they are used with CDMA, orthogonal frequency division multiplexing (OFDM), and / or several other types of communication techniques that can be used to provide wireless communication links between access nodes and mobile nodes. In some modalities, access nodes are implemented as base stations that establish communication links with mobile nodes using OFDM and / or CDMA. In several modalities, mobile nodes are implemented as notebook computers,

49/49 personal data assistants (PDAs), or portable devices including receiver / transmitter circuits, and logic and / or routines, other than to implement the methods of the various modalities.