Methods and apparatus for using control values to control communications processing

(54) Title: METHODS AND EQUIPMENT FOR USING CONTROL VALUES TO CONTROL COMMUNICATION PROCESSING (30) Unionist Priority: 07/06/2006 us 60/812053 (73) Holder (s): Qualcomm Incorporated (72) Inventor (s) : Faith Ulupinar, Gavin Bernard Horn, Paul E. Bender, Rajat Prakash (74) Attorney (s): Montaury Pimenta, Machado & Lioce (86) International Request: pct us2007070624de

06/07/2007 (57) Summary: methods and equipment to use CONTROL VALUES TO CONTROL COMMUNICATION PROCESSING. Methods and equipment for tunneling packets between server and remote Access Points for delivery to an access terminal (AT) are described. Methods and equipment for communicating control values ​​and / or information in addition to information to be delivered to an AT via an aerial link are also described. An AT uses the received control information to retrieve communicated packets. Some features support the use of multiple headers and / or indicators in the headers, for example, Packet Correlation Protocol (PCP) and / or RLP headers, which can be used to control routing of payloads communicated to an RLP processing module corresponding to an AP that was the source of the reported payload.

(87) International Publication: wo 2007/143721 de

13/12/2007

<img file="BRPI0712412A2_D0001.tif" />

METHODS AND EQUIPMENT FOR USING CONTROL VALUES FOR

CONTROL COMMUNICATION PROCESSING

RELATED APPLICATIONS

The present application claims the benefit of Provisional Patent Application USSN 60 / 812,053 filed on June 7, 2006, entitled A METHOD AND APPARATUS FOR USING REPROCESS BIT TO DELIVER DATA which is expressly incorporated herein by reference.

FIELD

The various modalities are directed at methods and equipment for communications, and more methods and equipment related to control and processing of communications particularly using control values.

FUNDAMENTALS

Wireless communications systems often include a plurality of access points (APs) and / or other network elements in addition to access terminals, for example, mobile devices or other end-devices. In many cases, access terminals normally communicate with access points via wireless links while other elements on the network, for example,

APs, usually communicate with each other through non-air links, for example, fiber, cable or wired links.

While an access terminal (AT) moves in a system, and / or while overhead link conditions change, the access terminal may lose or terminate a connection to an AP and can establish and / or maintain a connection with another

AP. As a result, an AP that has an air link connection to an

AT can end up in a situation where it has undelivered packages that are about to be communicated to an AT with which it no longer has a connection.

2/52

APs often subject IP packets and / or other higher-level packets to fragmentation prior to transmission over an aerial link. RLP (Radio Link Protocol) processing can be used to perform this function and / or to generate header that can be used to reconstruct higher level packets, for example, smaller MAC packets, communicated over an aerial link. Different access nodes can perform, for example, the fragmentation function, slightly differently. Consequently, in many modalities, it may be important that ATs receiving an RLP packet should be able to identify the AP that was responsible for generating the RLP packets to begin with so that the packets can be processed by a corresponding RLP module and the packet plus high level, in the case of fragmentation, reconstructed from there.

It should be appreciated that there is a need for methods and / or equipment that support packet communications between an AP that is remote to an AT and an AP that is serving the AT and has an active over-the-air connection to the AT can be used to deliver packages. There is also a need for methods and / or equipment that can be used to communicate sufficient control information to enable an AT to apply appropriate processing, for example, RLP processing, to packets received over an overhead link.

SUMMARY

Some features are directed to methods and equipment that can be used to tunnel packets between a server and remote Access Point for delivery to an access terminal (AT). Other characteristics are directed to values ​​and / or communication control information in addition to information

3/52 to be delivered to an AT via an aerial link. Some features support the use of multiple headers, for example, Packet Correlation Protocol (PCP) and / or RLP headers, which can be used to control the routing of payloads communicated to an RLP processing module that corresponds to a AP that was the source of the reported payload.

An exemplary method of operating an access terminal according to several modalities, comprises:

examining an RLP header from an RLP packet to determine whether a reprocess indicator value in the RLP header has been adjusted; and if it is determined that the reprocess indicator has been adjusted: i) by passing a payload that corresponds to the indicator value to an address layer module;

and ii) operate the addressing layer module to deliver the payload corresponding to the indicator value to an RLP module corresponding to an address value included in the RLP packet with the reprocess indicator. An exemplary access terminal, according to several modalities, comprises: a first RLP payload processing module corresponding to a first access point; a second RLP payload processing module corresponding to a second access point; an addressing module for forwarding packet payloads to one of the RLP payload processing modules based on the address information communicated to the address module;

a header processing module to determine, based on an indicator value included in a header, whether the header includes an address used to route an RLP packet payload and forward the packet payload to the addressing module when the indicator value indicate that an address used to route packet payloads

RLP is included.

4/52

An exemplary method of operating a first access point, according to several modalities, comprises: receiving a radio link protocol packet, through an inter-access tunnel, the radio link protocol packet received including the targeted information an access terminal; determine whether the received radio link packet fits into a MAC packet; if it is determined that the received radio link packet fits into a MAC packet: generate a MAC packet including the received radio link packet; and transmitting the generated MAC packet to the access terminal over an aerial link between the first access point and the access terminal. An exemplary access point, according to some modalities comprises: a tunnel interface module for receiving tunneled packets from another access point; a packet fragmentation determination module to determine whether packet fragmentation should be performed on the contents of a tunneled packet; an RLP header generation module coupled to the packet fragmentation module to generate an RLP header that includes a value indicating the presence of an address to be used to route an RLP packet payload to an RLP module; and a wireless transmitter for transmitting a packet over an air link that includes an RLP header generated by the RLP header generation module and at least part of a tunneled packet.

An exemplary method of operating a first access point, according to some modalities, comprises: receiving a package to be communicated to an access terminal; determine whether the first access point is remote to the access terminal to which the received packet must be communicated; if it is determined that the first access point is remote to the access terminal to which the received packet must be communicated: i) generate an RLP header; ii) generate

5/52 a tunnel header that includes a return address corresponding to the first access point;

and iii) transmit the received packet with the header

RLP and the tunnel header to a second access point through an exemplary tunnel, from which second point communicates. One is coupled to a first access point, the access point having an aerial link connection with an access terminal, in some modalities, comprises:

remote means of determining access point does not have an access terminal to which one to determine link link packet must be remote device packet processing processing packet

i) means header packets received from a remote device point processing of RLP header generation

RLP which includes an address to which is not included means of generating access to generate be in the one used if the first air with a statement; o means for remote access, o means including:

to generate a value set to indicate to route a payload header header to tunnel an RLP packet that is communicated to the second point at the access terminal.

Packet tunnel packet RLP includes access

While the various modalities

Generated RLP;

inter-point of tunnel used package to be for transmission were discussed in the summary above, it must be appreciated that not all modalities necessarily include the same characteristics and some of the necessary modalities.

characteristics described above are not but can

Numerous additional benefits are desirable in some characteristics, modalities and discussed in the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

6/52

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

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

Figure 3 illustrates an exemplary network that includes a distributed access network (AN) architecture and an access terminal (AT).

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

Figure 5 is a drawing illustrating an exemplary communications system, different flows of exemplary packets, and the drawing is used to describe reprocess and remote bit settings used in different flows.

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

Figure 7 is a flow chart of an exemplary method of operating a server access point, for example, local, according to various modalities.

<td>Figure</td><td> 8</td><td>what</td><td>understands</td><td>The</td><td>combination</td><td>of the figure</td><td>8A</td>

<td>and figure 8B</td><td>is</td><td>one</td><td>flowchart</td><td>in</td><td>a method</td><td>exemplary</td><td>in</td>

<td colspan="2">operate a terminal</td><td>in</td><td colspan="2">access, by</td><td>example,</td><td>mobile node</td><td>without</td>

various modalities.

yarn, according to an exemplary example

Figure 9 in agreement is a drawing of a terminal with

Figure 10 is according to

Figure 11 is according to various access modes.

a drawing of a point several modalities.

a drawing of a point several modalities.

access access

DETAILED DESCRIPTION

Wireless communication systems are widely developed to provide various types of communication content such as voice, data, and so on. These systems can be multiple-access systems capable of

7/52 support communication with multiple users by sharing available system resources (for example, bandwidth and transmission power). Examples of such multiple-access systems include Worldwide Interoperability for Microwave Access (WiMAX), infrared protocols such as the Infrared Data Association (IrDA), short-range wireless protocols / technologies, Bluetooth® technology, ZigBee® protocol, protocol ultra-broadband (UWB), native radio frequency (HomeRF), shared wireless access protocol (SWAP), broadband technology such as a wireless Ethernet compatibility alliance (WECA), wireless fidelity alliance (Wi-Fi Alliance), 802.11 network technology, public switched telephone network technology, heterogeneous public communications network technology such as the Internet, private wireless communications network, terrestrial mobile radio network, code division multiple access (CDMA), broadband code division multiple access (WCDMA), universal mobile telecommunications system (UMTS), advanced mobile phone service (AMPS), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), global system for mobile communications (GSM), carrier radio transmission technology (RTT) single (IX), evolution data only technology (EV-DO), general packet radio service (GPRS), improved GSM data environment (EDGE), high speed downlink data packet access (HSPDA), analogue and digital satellite systems, and some other technologies / protocols that can be used on at least one wireless communications network and one data communications network.

8/52

Generally, a multi-access wireless communication system can simultaneously support communication to multiple wireless terminals. Each terminal communicates with one or more base stations through transmissions on the forward and reverse links. The direct link (or 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-entry and single-exit, multiple-entry and single-exit or multiple-entry and multiple-exit (MIMO) system.

Referring to Fig. 1, a 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, others including 108 and 110, and one including 112 and 114. In Fig. 1, only two antennas are shown for each antenna group, however, more or fewer antennas can be used for each antenna group. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over direct link 120 and receive information from access terminal 116 over 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 on direct link 126 and receive information from access terminal 122 on reverse link 124. In In an FDD system, communication links 118, 120, 124 and 126 can use different frequencies for communication. For example, direct link 120 may use a different frequency then that used by reverse link 118.

9/52

Each group of antennas and / or the area in which they are designed to communicate is often referred to as an access point sector. In the modality, each antenna group is designed to communicate with access terminals in a sector of the areas covered by access point 100.

In a communication over direct links 120 and 126, the transmitting antennas of the access point 100 use beam formation in order to improve the signal / noise ratio of direct links to the different access terminals 116 and 122. Also, an access point using beamforming to transmit to randomly scattered access terminals through its cover makes less interference to access terminals in neighboring cells than an access point transmitting through a single antenna to all of its terminals access.

An access point can be a fixed station used to communicate with the terminals and can also be referred to as an access node, a B node, a base station or some other terminology. An access terminal can also be called an access device, user equipment (UE), a wireless communication device, a terminal, a wireless terminal, a mobile terminal, a mobile node, a termination node or some other terminology.

FIG. 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 to a transmission (TX) data processor 214.

In one embodiment, each data stream is transmitted over a respective transmission antenna. The TX 214 data processor formats, encodes, and merges traffic data for each data stream based on a

10/52 particular encoding scheme selected for that data stream to provide encoded data.

The encoded data for each data stream can be multiplexed with pilot data using OFDM techniques. Pilot data is typically a known pattern of data that is processed in a known manner and can be used in the receiving system to estimate the channel response. The multiplexed pilot and encoded data for each data stream is then modulated (that is, mapped to symbol) based on a particular modulation scheme (for example, BPSK, QSPK, M-PSK, or M-QAM) selected for that stream data 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 supplied to a MIMO TX 220 processor, which can further process the modulation symbols (for example, for OFDM). The MIMO TX 220 processor then supplies N_T modulation symbol streams at N_T transmitters (TMTR)

222a with

222t.

In certain embodiments, the MIMO processor

TX 220 applies beamforming weights to the symbols in the data streams and the antenna from which the symbol is being transmitted.

Each transmitter (222a, 222t) receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (for example, amplifies, filters, and upwards converts) the analog signals to provide an appropriate modulated signal for transmission about the MIMO channel. The N_T Modulated signals from transmitters 222a to 222t are then transmitted from N_T antennas 224a to 224t, respectively.

11/52

At the access terminal 250, the transmitted modulated signals are received by the N_R antennas 252a to 252r and the signal received from each antenna 252 is supplied to a respective receiver (RCVR) 254a at 254r. Each receiver (254a, ..., 254r) conditions (for example, filters, amplifies, and downwards converts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding received symbol stream .

An RX 260 data processor then receives and processes the N_R symbol streams received from the N_Rreceivers (254a, ..., 254r) based on a particular receiver processing technique to provide N_Tdetected symbol streams. The RX 260 data processor then demodulates, de-scales, 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 MIMO TX 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 part and a classification value part.

The reverse link message can comprise various types of information regarding the communication link and / or the data flow received. The reverse link message is then processed by a TX 238 data processor, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a to

12/52

254r, and transmitted, via the antennas (252a, 252r), respectively, back to access point 210.

At access point 210, the modulated signals 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 reverse link message transmitted by the system receiver 250. 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 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 methods.

In one respect, SimpleRAN is designed to significantly simplify communications protocols between access network elements of the return transport channel in a wireless radio access network, while providing fast 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 both centralized and distributed distribution. The network architectures for centralized and distributed distributions are shown in Fig. 3 and Fig. 4 respectively.

13/52

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

In a distributed architecture shown in Fig.

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 native agent 310. In addition, AN 302 includes an IP 312 cloud. APs (304, 306, 308) are coupled to the IP cloud via of the links (314, 316, 318), respectively. IP cloud 312 is coupled to HA 310 through link 320.

An AP includes one:

Network function (NC):

• one per AP, and multiple NFs can serve a single TA.

• A single NF is the IP layer attachment point (IAP) for each AT, that is, the NF to which the HA forwards 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 Fig. 4.

• The IAP can change (L3 handoff) to optimize packet routing over the transport channel returning to the AT.

• The IAP also performs the role of the session master for the TA. (In some modalities, only the session master can perform session configuration, or change the session state.) • 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:

• Multiple per AP, and multiple TFs can serve a single TA.

• Provides attachment of overhead interface to the AT.

14/52 • May be different for forward and reverse links.

• Changes (L2 handoff) based on radio conditions.

In AN 302, APa 304 includes NF 324, TF 326 and TF 328. In AN 302 APb 306 includes NF 330, TF 332 and TF 334. In AN 302 APc 308 includes NF 336, TF 338 and TF 340.

An AT includes:

I_x interface presented to the mobile node (MN) for each NF in the active set.

Mobile node (MN) to support mobility of the IP layer at the access terminal.

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

The exemplary AT 303 includes a plurality of interfaces (I_a 342, I_b 344, I_c 346) and MN 348. The AT 303 can be, and is sometimes, coupled to the AP_a 304 via the wireless link 350. AT 303 can be, and is sometimes coupled to AP_b 306 via wireless link 352. AT 303 can be, and is sometimes coupled to AP_c 308 via wireless link 354.

Figure 4 illustrates an exemplary network 400 including a distributed AN 402 and an AT 403.

In a centralized architecture shown in Fig.

4, the NF is no longer logically associated with a single TF, so the NA comprises network functions, access points 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 IP cloud 418. NF 404 is coupled to the IP cloud 418 via the link 420. NF 406 is attached to the IP cloud 418 through link 422. NF 408 is attached to the IP cloud 418 through link 424. IP cloud 418 is attached to HA 416 through link 426. NF 404 is coupled (AP_a 410, AP_b 412, AP_c 414) through the links (428, 430,

432), respectively. The NF 406 is coupled (AP_a 410, AP_b

15/52

412, AP_c 414) through the links (434, 436, 438), respectively. The NF 4 08 is coupled (AP_a 410, AP_b 412, AP_c 414) through the links (440, 442, 444), respectively.

<td></td><td colspan="2">The AP at 410 includes</td><td>TF 462 and TF 464. 0</td><td>AP_b</td><td> 412</td>

<td>includes</td><td>TF</td><td>466 and TF 468. 0 AP_</td><td>c 414 includes TF 470 and</td><td colspan="2">TF 472.</td>

<td></td><td></td><td colspan="2">As long as an NC acts as the controller</td><td>for</td><td>an</td>

<td>TF, and</td><td colspan="2">many NFs can be</td><td>logically associated</td><td>with</td><td>an</td>

<td>only</td><td>TF,</td><td>the controller</td><td>NC for an AT, this</td><td>and the</td><td>NF</td>

communicating with a TA as part of the active set, it performs the functions of allocating, managing and disconnecting 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 logical functions performed are the same as for distributed architecture.

The exemplary AT 403 includes a plurality of interfaces (I_a 446, I_b 448, I_c 450) and MN 452. AT 403 can be, and is sometimes, coupled to the AP_a 410 via wireless link 454. AT 403 can be, and is sometimes coupled to AP_b 412 via wireless link 456. AT 403 can be, and is sometimes coupled to AP_c 414 via wireless link 458.

In DO and 802.20 systems, an AT obtains service from an AP by attempting to access an access channel in a particular sector (TF). The NF associated with the TF that receives the access attempt contacts the IAP that is the session master for AT and retrieves a copy of the AT session. (The TA indicates the identity of the IAP 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 search for the IAP address.)

16/52 After successful access, the AT is assigned aerial interface resources such as a MAC ID and data channels to communicate with that sector.

In addition, the TA can send a report indicating the other sectors it can hear and their signal strengths. The TF receives the report and forwards it as a network-based controller instead of the AT with implemented in the NF that provides for an active set.

For DO and

802.20 like today, there is exactly one

NC that the TA can communicate with (except during an NC handoff when there are two temporarily). Each of the TFs in communication with the TA will forward the received data and signaling to this single NF. This NF also acts as a network-based controller for the TA and is responsible for negotiating and managing the allocation and disconnecting of resources for the TA to use with the sectors in the active set.

The active set is therefore the set of sectors in which the TA is assigned air interface resources. The AT will continue to send periodic reports and the network-based controller can add or remove sectors from the active set as AT moves around the network.

NFs in the active pool will also seek 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 a CDMA aerial 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.

17/52

<td></td><td>For a system</td><td>OFDMA, or</td><td>one</td><td>system</td><td colspan="2">without soft</td>

<td>handoff,</td><td colspan="3">a function of the active set is</td><td>to allow</td><td>that the</td><td>AT</td>

<td>commute</td><td>quickly between</td><td>sectors</td><td>at the</td><td>set</td><td>active</td><td>and</td>

<td>Keep</td><td>service without having</td><td>to do</td><td>an</td><td colspan="2">new try</td><td>in</td>

<td>access.</td><td>An attempt to</td><td>access is</td><td colspan="4">usually much more</td>

slower than switching between active pool members, provided the active pool member already has the session and air interface resources assigned to the TA. Therefore, an active set is useful to handoff without affecting the QoS service of active applications.

When, an AT and the session master at

IAPs negotiate attributes, or alternatively the status of the connection changes, the new values ​​for the attributes or the new state requirement to be distributed to each of the sectors in the active set in a timely manner to ensure the optimal service of each sector. In some cases, for example, if the type of headers changes, or security keys change, an AT may not be able to communicate with a sector at all until these changes are propagated to that sector. So each member of the active set must be updated when the session changes. Some changes may be less critical to synchronize than others.

There are three main types of state or context found on the network for an AT that has an active connection:

Data state is the state on the network in the data path between the AT and the IAP or an NC during a connection. The data state includes such things as header compressor status or RLP flow states that are very dynamic and difficult to transfer.

Session state is the state on the network in the control path between the AT and the IAP that is preserved when a connection is closed. The session state includes the value of

18/52 attributes that are negotiated between the TA and the

IAP. These attributes affect the characteristics of the connection and server received by the TA.

For example, an AT can negotiate the QoS configuration for a new application to provide new filter and flow specifications to the network that indicates the QoS service requirements for the application. As another example, the

AT can negotiate the size and type of headers used in communication with the AN. The negotiation of a new set of attributes defined as a session change.

connection status is the status on the network in the control path between the

Until the

IAP or an NC that is not preserved when a connection closes and the

AT is idle. The connection state can include information such as power control loop values, soft handoff timing, and active set information.

On a

IAP or L3 handoff the three status types may need to be transferred between the old and new IAP. If only an idle TA can handoff the IAP

L3, then only the session state needs to be transferred.

To support L3 handoff for an active AT, data and connection status may also need to be transferred.

The DO and 802.20 type systems, L3 handoff the simple data state by defining multiple routes (or data stacks), where the data state for each route is local to that route, that is, the routes each have the status of independent data. By associating each IAP with a different route, the data state does not need to be transferred in a handoff. An even better step is to associate each NF with a different route. In this case, the L3 handoff is completely transparent to the data state, except for possible packet reordering.

19/52

Since the data state has multiple routes, the next logical step to support L3 handoff for an active AT is to move the IAP connection state control and make it local to 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 to each NC. This may require that any one of you negotiate and manage the allocation and disconnect resources from the connection state is transferred to the TA since there is no longer a single NF to manage all members of the active set. You can also make some additional requirements in the air interface design to avoid tight coupling between TFs - since different TFs cannot share the same NF - in the active set. For example, to operate in an optimal manner, it is preferable to eliminate all tight synchronization between TFs that do not have the same NC, such as power control loops, soft handoff, etc.

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

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

Fundamentally, some session state (QoS profile, security keys, attribute values, etc.) cannot be done locally to an NF (or to the IAP) because it is very expensive to trade every time there is an NF handoff (or an L3). Session status is also relatively static and easy

20/52 to transfer. What is needed are mechanisms to manage and update the session state while changing and during the IAP handoff where the session master moves.

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

A separate but related issue is the AT control of the L3 handoff. Today, in DO and 802.20 systems, AT is aware of the L3 handoff as long as it allocates and disconnects local batteries, but has no control over when the L3 handoff occurs. This is called network-based mobility management. The question is whether to make AT the handoff controller, that is, to use AT-based mobility management?

To support fault tolerance and load balancing, the network needs to either be able to 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 occur.

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 additionally by not requiring network elements to determine when to handoff.

The primary reason systems type DO and 802.20 use network-based mobility is that AT-based mobility is not optimized to work fast enough to support voice. A secondary reason is the tunneling overhead introduced by terminating the mobile IP tunnels

21/52 (for MIPv6) in the OT. The mobility latency can be resolved by forwarding 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:

The L2 or layer 2 handoff refers to changing the direct link or reverse link (TF) server sector.

The L3 handoff refers to the IAP change,

Handoff L2 should be as fast as possible in response to changing radio conditions. DO and 802.20 systems use the PHY layer signaling to do a quick L2 handoff.

The L2 handoff is transfer from the TF server sector to direct (FL) or reverse (RL) links. A handoff occurs when the TA selects a new server sector in the active set based on the RF conditions seen in the TA for that sector. The TA performs filtered measurements on RF conditions for direct and reverse links 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 in the pilots in the shared signaling channel, to select their desired FL server sector. For the reverse link, the TA estimates the CQI erasure rate for each sector in the active set based on the power control commands up / down to the sector TA.

The L2 handoff is initiated when the AT requests a server sector other than FL or RL through a reverse link control channel. Dedicated resources are allocated in a TF when it is included in the active pool for an TA. TF is already configured to support AT before the handoff request. The target server sector detects the request for

22/52 handoff and complete the handoff with the allocation of traffic resources to the TA. The direct link TF handoff requires a round trip message exchange between the source TF or IAP and the target TF in order to receive data for the target TF to transmit. For the reverse link TF handoff, the target TF can immediately allocate resources to the TA.

L3 handoff is the transfer from the IAP. The L3 handoff involves a linked update of HA with the new IAP and requires a transfer of session from the new IAP to the control plan. The L3 handoff is asynchronous to the L2 handoff in the system so that the L2 handoff is not limited by the MIPv6 handoff signaling speed.

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

The route indicates that NF has processed the packet. For example, a

NF can be associated in TF and over the air like Route A, while another NF can be associated with Route

B.

An

TF server can simultaneously send packets to a

AT of both Route A and

Route B, that is, from both NFs, using a separate and independent sequence space for each one.

There are two key ideas in the design of ensuring the QoS treatment for a mobile and system for its traffic is retained over each handoff mode:

Decoupling the handoff L2 and L3

Reserving air interface resources and seeking the session at the target NF or TF before the handoff occurs to minimize data flow interruption during handoff.

This is done by adding the TF and

Target NC to the active set.

system is designed to separate L2 handoff

L3 in order to allow the system to support traffic

EF

23/52 during high L2 handoff rates. The L3 handoff requires a linked update, which is limited to a rate of 2 to 3 per second. In order to allow a faster rate of the L2 handoff of 20 to 30 hertz, L2 and L3 handoffs are designed to be independent and asynchronous.

For the L2 handoff, active set management allows all TFs in the active set to be configured and dedicated resources to be assigned in order to be ready to serve in the event 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 pool, which is a pool of APs that have resources assigned to the TA. At a given point in time, an AT may be within the radiocommunication range with one of the APs, or for the purpose of optimizing battery power and reducing radio interference, it may communicate only with a carefully selected AP (server AP) . The problem considered here is the delivery of data packets or signaling messages from a non-server AP via a server AP.

Radio link protocol (RLP): Each AP has an RLP, which fragments upper layer packets, and if necessary retransmits the fragments. The RLP also adds its own header to each transmitted fragment. The TA has multiple cases of RLP, one for each AP that is in the active pool.

Tunneling: A server AP receives packets from a non-server AP through an inter-AP tunnel called the L2TP tunnel (layer 2 tunneling protocol). The server AP can deliver packets received in the tunnel by two alternating methods that use the following two bits.

24/52

Remote bit: The remote bit is part of the Packet Correlation Protocol (PCP) header. The PCP header is sometimes also called a MAC consolidation header. The remote bit is set by the sending PCP and processed by the receiving PCP. If the remote bit has the value 1 (the bit is set) then the bit is followed by an AP address, and the receiving PCP passes the payload to the addressing layer. The addressing layer examines the address and forwards it to the addressed RLP. If the remote bit has value

0, the bit is not followed by an address and the receiving PCP passes the payload to the RLP of the

Server AP.

Reprocess bit:

reprocess bit is part of each payload

RLP. If set), the bit is followed by an AP address. If the reprocess bit is set, the receiving RLP passes the packet back to the addressing layer.

The addressing layer examines the address and forwards it to the

Addressed RLP. If the reprocess bit is not set (bit = 0), the receiving RLP passes the packet back to the application (for example, header decompressor or IP layer).

The decision to adjust these bits is made by the AP service (APb). For a packet that is received by APb from APa, there are the following two choices

1. Remote = 1, Reprocess = 0: In this case, the server AP does not use its RLP and does not fragment the packet. This case can be used if the packet received in APb from APa is small enough to fit into a MAC payload. The AP server also introduces an address in the packet, and this is the address known to the AP server because it received the packet through the L2TP tunnel.

2. Remote = 0, Reprocess = 1: In this case, the server AP uses its RLP and can fragment the packet. This case can be used if the packet received in APb from APa does not fit in a

25/52 MAC payload. The AP server also introduces an address in the packet, and this address is known to the AP server because it received the packet through the L2TP tunnel.

Figure 5 includes an exemplary communications system 500 and a corresponding legend 502. The exemplary communications system 500 includes a first access point APa 504, a second access point APb 506 and an access terminal AT 508. From the perspective of the AT 508 , currently, APb 506 is your server, for example, access point, local. There is a wireless air link 552 between APb 506 and AT 508. From the perspective of the AT 508, APa 504 is currently a remote access point. There is a Layer 2 Tunneling Protocol tunnel 550 between APa 504 and APb 506.

access point to (APa) 504 includes a header compressor module_a 510, an RLP_a module 512, a PCP module — a 514 and a MAC / PHY module 516. Access point b (APb) 506 includes a compressor module header 518, an RLP_b 520 module, a PCP_b 522 module and a MAC / PHY 524 module. The access terminal (AT) 508 includes a header compressor module_b 526, an RLP_b module 528, a PCP_b module 530, a first MAC / PHY 532 module, a header compressor module_a 536, an RLP_a module 538, a module PCP_a 540, and a second MAC / PHY 542 module. It should be noted that PCP_b 530 routes based on the remote bit value included in the PCP header.

Legend 502 includes dashed line 544, dotted line 546 and continuous line 548 used to illustrate the packet flow for three different examples. The dashed line 544 represents the flow for an example of: no packet fragmentation; the remote bit is set; the reprocess bit is not set; and the APa address is contained in the PCP header. The dotted line 546 represents

26/52 the flow for an example of: packet fragmentation in the RLP 520 of AP_b 506; the remote bit is not set, the reprocess bit is set, and the APa address is contained in the RLP header. Continuous line 548 indicates that an example of local delivery and APa 504 is not involved.

Figure 5 explains the fragment flow from a non-server AP (APa 504) that is delivered through a server AP (APb 506) and describes the flow of packets depending on the setting of the two bits above. Each of the packages in this example is exchanged between APa 504 and AT 508 via MAC / PHY 524 from APb 506 and through PCP 522 from APb

506.

Some characteristics of several modalities are:

1. It allows different versions of RLP to run on different APs. In this case, effectively, an RLP is allowed to tunnel data to another RLP. For example, RLP_a 512 of APa 504 can tunnel data to RLP_b 520 of APb 506 through the L2TP 550 tunnel.

2. Facilitates partial pack progress during handoff. Consider the case when part of an IP packet (or other) was served by APa 504 when the handoff occurred. Then, APa 504 wishes to deliver the remaining part of the package to AT 508. In this invention, APa 504 can send this remaining part to APb 506, and APb 506 can deliver it to AT 508. In the AT 508, this remaining part of the packet flows after addressing layer 534 to RLPa 538, where it is combined with the part previously sent.

The invention allows APb 506 to send only the unsent portion of the packet, and the entire packet does not have to be sent from APb 506. This allows for more efficient use of bandwidth because no part of the

27/52 package is sent twice. Such partial packet progress is important when the handoff is frequent and IP packets can be divided into several MAC layer fragments.

3. Facilitates signaling messages to go from non-server APs to AT. The signaling messages generated in APa 504 can be delivered by APb 506, and this allows efficient management of resources in the AP and AT 508.

4. It allows two possible routes for tunneled packets: The packages received by a server AP through the L2TP tunnel can be sent, for example, by the addressing module 513, through two separate routes, one using the RLP of the server AP, and the other that does not use the RLP of the server AP. For example, the path that corresponds to the dotted line 546 uses the RLP_b 520 of the APb server 50 6, when the path that corresponds to the dotted line 544 does not use the RLP_b 520 of the APb server 506.

Figure 6 is a flow chart 600 of an exemplary method of operating an access point (AP). The AP that performs the flowchart 600 steps is sometimes referred to as the current AP. The operation starts at step 602, where the access point is powered up and initialized. The operation proceeds from the beginning of step 602 to step 604. In step 604 the access point receives a packet, for example, an IP packet, to be communicated to an access terminal (AT). Then, in step 606, the access point determines whether it is remote with respect to the destination access terminal for the received packet. If the AP is remote with respect to the target AT, then the operation proceeds from step 606 to step 608; if not, the operation proceeds from step 606 to step 620.

28/52 RLP header. Stage

608 includes sub-step 610, in which the

AP set a reprocess bit

0. The operation proceeds from step 608 to step

612, in which the AP adds the generated RLP header to the received packet.

The operation proceeds from step 612 to step 614.

In step 614, the access point generates an inter-AP tunnel header, for example, a tunnel tunnel header.

Layer Tunneling Protocol (L2TP), with the sender address equal to the AP address of the

Current AP. The operation proceeds from step 614 to step 616.

In step 616, the access point appends the generated tunnel header to the header

Generated RLP and received packet combination.

Then, at the access terminal, the generated tunnel header transmits, the generated RLP header and the packet received through an inter-AP tunnel, for example, through an L2TP tunnel. In some modalities, the destination at the opposite end of the tunnel is another AP, for example, the server AP for the AT to which the packet corresponds.

Returning to step 620, in step 620 the access point performs normal transmission processing. Step 620 includes sub-step 622 in which the access point generates the MAC packet or packets, and then in step 624 transmits the generated MAC packet or packets, for example, over an aerial link to the access terminal.

The operation proceeds from either step 618 or 624 to final step 626. The exemplary method of flowchart 600 is repeated for additional received radio link protocol packets that must be communicated to an access terminal.

The access point that performs the flowchart 600 steps can be a remote access point or a service, for example, local, perspective access point

29/52 of the access terminal to which the package must be communicated. In one example, the access terminal is the AT 508 in figure 5.

Steps 606, 612, 614, 616, and 618 apply to the case where the access point that performs the flowchart method 600 is a remote access point from the perspective of the access terminal, and the remote access point communicates information to be communicated to the AT through a return transport channel network using an interAP tunnel, for example, an L2TP tunnel, for example, communicating the packet to the AT 's, for example, local AP. In such a case, the remote access point performing the flowchart method 600 is remote APa 504 of figure 5. Steps 620 and 624 apply to the case where the access point performing the flowchart method 600 is a server access point , for example, local, from the perspective of the access terminal, and the server access point communicates information to the AT over a wireless link and the server AP, for example, local, does not use an inter-AP tunnel for such communication . In such a case, the remote access point carrying out the flowchart method 600 is the APb, for example, location 506 of figure 5.

7 is a flow chart 700 of an exemplary method of operating a server, e.g., local access point. In the initial step 702, the server access point is powered up and initialized. The access point is a server access point from the perspective of the access terminals that are using it as a current network attachment point. The operation proceeds from the initial step 702 to step 704. In step 704, the server access point receives a radio link protocol (RLP) packet through an inter-AP tunnel, for example, a Layer 2 Tunneling Protocol (L2TP) tunnel with a sender address. The operation proceeds from step 704 to step 706.

30/52

In step 706, the server AP determines whether or not the received RLP packet fits into an available MAC size packet. If the received RLP packet fits into a single MAC packet then operation proceeds from step 706 to step 708. However, if the received RLP packet needs to be fragmented and parts communicated in different MAC packets, then operation proceeds from step 706 to step 722 .

Returning to step 708, in step 708, the server access point generates a MAC packet. Step 708 includes sub-steps 710 and 718. In sub-step 710, the server access point generates a PCP header. Sub-step 710 includes sub-steps 712, 714 and 716. In sub-step 712, the server access point sets a remote bit = 1. Then, in substep 714, the server AP sets a PCP address = the address of the remote sender's AP, and in substep 716, the server access point introduces the remote bit and the PCP address in the PCP header. The operation proceeds from sub-step 710 to sub-step 718. In sub-step 718, the server access point forms a MAC packet that includes the generated PCP header and received RLP packet.

In step 720, the server access point transmits the generated MAC packet, for example, over a wireless air link to an AT for which the packet is intended. The operation proceeds from step 720 to final step 744.

Returning to step 722, in step 722, the server access point generates a MAC packet. Step 722 includes sub-steps 724, 732, 734 and 738. In sub-step 724, the server access point generates an RLP header. Sub-step 724 includes sub-steps 726, 728 and 730. In sub-step 726, the server access point sets a reprocess bit = 1. Then in sub-step 728, the server access point sets an address RLP = the address of the sender's remote AP. In sub-step 730, the server access point introduces the

31/52 reprocessing of sub-step 726 and RPL address of sub-step 728 in an RLP header. The operation proceeds from substep 724 to substep 732, where the server access point fragments the remaining received RLP payload if necessary.

The operation proceeds from sub-step 732 to sub-step 734, in which the server access point generates a PCP header. Sub-step 734 includes sub-step 736, in which the server access points set a remote bit = 0. The operation proceeds from sub-step 734 to sub-step 738.

In sub-step 738, the access point forms a MAC packet that includes the generated PCP header from sub-step 734, the generated RLP header from sub-step 724, and an RLP payload. The RLP payload is, for example, a fragment of the RLP payload from the RLP packet received from step 704. The operation proceeds from step 722 to step 740. In step 740, the server access point transmits the MAC packet generated from step 722, for example, over a wireless air link, to the access terminal for which the packet is intended. The operation proceeds from the stage

740 step 742.

In step 742, the server access point determines whether or not there is any remaining RLP payload fragment to be transmitted corresponding to the RLP packet received from step 704. If there are no more fragments, operation proceeds from step

742 the final step 744. If there are still fragments of RLP payload to be reported, follow the operation and proceed from step

722 for generating another package

MAC.

In step 744, the operation ends with respect to the method since the received radio link packet was transmitted. The exemplary method of flowchart 700 is repeated for additional radio link protocol packets received over an inter-AP tunnel, for which the access point is a server access point.

32/52

Figure Ί corresponds to a TA server AP that receives and processes information communicated about an inter-AP tunnel, for example, an L2TP tunnel, generating one or more MAC packets, generating one or more MAC packets and transmitting one or more MAC packets over a wireless communications link between the server AP and the AT. For example, AT is the AT 508 of figure 5, and the server AP performing the steps of flowchart 700 is APb 506 of figure 5 with respect to tunneling cases.

Figure 8 comprising the combination of figure 8A and figure 8B is a flow chart 800 of an exemplary method of operating an access terminal (AT), for example, a wireless mobile node. The operation starts at step 802, where the access terminal is powered and initialized. In the initial 802 step, the access terminal establishes a wireless connection to an access point, for example, your current server access point. The operation proceeds from the initial 802 step to step 804.

In step 804, the access terminal receives a MAC packet. Then, in step 806 an access terminal PCP module processes a PCP header that corresponds to the received MAC packet and determines a remote bit value carried in the PCP header. The operation proceeds from step 806 to step 808, where the access terminal proceeds along different operational flows depending on the remote bit value determined from the PCP header. If the PCP module of the AT determines that the remote bit is not set (remote bit = 0) then the operation proceeds from step 808 to step 814. However, if the PCP module of the AT determines that the remote bit is set (remote bit = 1), then the operation proceeds from step 808 to step 812.

Returning to step 814, in step 814, the PCP module of the AT delivers the payload of the MAC packet to the

33/52 radio link protocol (RLP) server, for example, local, AT. The operation proceeds from step 814 to step 816. In step 816 the server RLP module, for example, local, performs RLP processing. Step 816 includes sub-steps 818, 820, 822, 824, 826, 827 and 828. In sub-step 818, the server RLP module, for example, local, processes the RLP header and determines the reprocess bit value. Then, in sub-step 820, the server RLP processing module proceeds along different operating paths depending on the determined reprocess bit value. In sub-step 820, if the reprocess bit is not set (reprocess bit = 0), then operation proceeds from sub-step 820 to sub-step 822. However, if in sub-step 820 the reprocess bit is set (reprocess bit = 1), then operation proceeds from sub-step 820 to sub-step 827.

Returning to sub-step 822, in sub-step 822 the RLP server module performs a package reassembly operation, and then in sub-step 824, the RLP server module passes the reassembled package to an application module, for example, a header decompression module or IP layer module. The operation proceeds from sub-step 824 final to step 826.

Returning to sub-step 827, in sub-step 827 the RLP module of the AT server performs a packet reassembly operation. The operation proceeds from sub-step 827 to sub-step 828. In sub-step 828, the AT server RLP module passes the payload or processed payload to an AT address layer module.

Returning to step 812, in step 812, the AT's PCP module delivers the payload of the MAC packet to the AT's address layer module. The operation proceeds from step 812 to step 830. In step 830 the layer module

34/52 addressing examines the address, which followed the remote bit, and delivers the payload to the RLP module specified by the address. The operation proceeds from step 830 to step 832. In step 832 the specified RLP module performs the processing

RLP. Stage

832 includes sub-steps 834,

836, 838, 839,

840, 842 and

844. In the sub-step

834, the specified RLP module processes the RLP header and determines the reprocess bit value.

Then, in sub-step 836, the specified RLP processing module proceeds along the different operation paths depending on the determined reprocess value. In sub-step 836, if the reprocess bit is not set (reprocess bit = 0), then the operation proceeds from sub-step 836 to sub-step 838. However, if in sub-step 836 the reprocess is set (reprocess bit = 1), then operation proceeds from sub-step 836 to sub-step 839.

Returning to sub-step 838, in sub-step 838 the specified RLP module performs a package reassembly operation, and then in sub-step 842, the specified RLP module passes the reassembled package to an application module, for example, an header decompression module or IP layer module. The operation proceeds from sub-step 842 to final step 844.

Returning to sub-step 839, in sub-step 839, the RLP server of the AT performs a packet reassembly operation. The operation proceeds from sub-step 839 to sub-step 840. In sub-step 840, in the AT server RLP module, the payload or the processed payload passes to an AT address layer module.

If the operation proceeded to substep 828 or substep 840, then the operation proceeds to step 846. In step 84 6, the AT's address layer module examines the address, which followed the reprocess bit,

35/52 delivers the payload or the processed payload to the RLP module specified by the address. The operation proceeds from step 846 through connection node A 848 to step 850. In step 850, the specified RLP module identified in step 846, performs a packet reassembly operation, for example, it combines a recovered packet fragment with all other fragments previously recovered from the packet transported by other MAC packets. Then, in step 852 the specified RLP module identified in step 846 determines whether the set of a top level package has been completed. The operation proceeds from step 852 to step 854.

In step 854, if the specified RLP module completed reassembly of a top level packet, for example, an IP packet, then the operation proceeds to step 856 where the specified RLP module passes the reassembled packet from the top level to an application module , for example, a header decompression module or an IP layer module. The operation proceeds from step 856 to final step 866.

Returning to step 854, in step 854 if the specified RLP module did not complete the reassembly of a top level packet, for example, an IP packet, then operation proceeds to step 858, where the specified RLP module stores the packet fragment. upper level recovered. The operation proceeds from step 858 to step 860, where the specified RLP module waits for additional corresponding packet fragments to arrive and to be retrieved. Then, at step 8 62, the specified RLP module reassembles the additional corresponding top-level packet fragment or fragments with the fragment from step 858 which obtains a top-level packet. The operation proceeds from step 862 to step 864 in which the module

36/52

Specified RLP passes the top-level package reassembled to an application module, for example, a header decompression module or an IP layer module. The operation proceeds from step 864 to final step 866.

Figure 8 corresponds to access terminal operations including MAC packet reception, PCP processing, address layer module operations, RLP processing, and top level packet reassembly operations. 0 Exemplary AT, for example AT 508 of Figure 5, includes a plurality of RLP modules, and uses one or more control bits, for example, a remote bit and / or a reprocess bit and / or associated address in header fields , to determine which RLP module is to perform a package reassembly operation. If a reprocess or remote bit is set to one, it is followed by an address field.

A reprocess bit = 1 indicates that a higher level packet, for example, an IP packet has been fragmented by an RLP module in an AP. Different fragments are communicated via different MAC packets. The address associated with the reprocess bit does not identify which RLP module actually cut the top-level packet, but rather identifies the original source of the top-level packet. In some embodiments, a number of fragments = 1 is also allowed. In this mode, the reprocess bit can be set = 1 with only one MAC packet communicated.

For an RLP packet sent and received through an L2TP tunnel, the reprocess bit will be set to zero since fragmentation has not yet occurred. If the RLP of the server AP then needs to perform fragmentation, the reprocess bit will be set to one for each new RLP packet header field within a MAC packet to be

37/52 transmitted. Note that the reprocess bit corresponding to the RLP packet sent through the L2TP tunnel is different from the reprocess bit that the server AP inserts.

A remote bit = 1 and a reprocess bit = 0 indicate that a higher level packet from a remote AP fits into a single MAC packet and is being communicated through a server AP to the AT. With respect to the TA, the flow including steps 804, 806, 808, 812, 830, and 832 including sub-steps 834, 836, 838 and 842 corresponds to such a case.

A remote bit = 0 and a reprocess bit = 0 indicate that a higher level packet from the server AP, for example, local, fits into a single MAC packet and is being communicated to the AT. With respect to TA, the flow including steps 804, 806, 808, 814, and 816 including sub-steps 818, 820, 822 and 824 corresponds to such a case.

The path that includes steps 804, 806, 808, 814, 816 including sub-steps 818, 820, 827 and 828, 846, 848 and 850 can represent either IP packet fragment retrieval in remote AP or fragment recovery IP packet originating locally, where the address following the reprocess bit identifies the source of the IP packet that has been fragmented and is being reassembled.

Figure 9 is a drawing of an exemplary access terminal 900 according to various modalities. The exemplary access terminal 900 is, for example, the access terminal 508 of figure 5. Exemplary access terminal 900 includes a wireless receiver module 902, a wireless transmitter module 904, a processor 906, I / O devices of user 908 and memory 910 coupled together via a 912 bus over which the various elements can exchange data and information. Memory 910 includes routines 918 and

38/52 data / information 920. Processor 906, for example, a

40/52 processed by the first MAC / PHY module 942, if you forward the received RLP packet payload to its corresponding RLP payload processing module 926 or forward the received RLP packet payload to addressing module 950. Then the first PCP 938 header processing module performs routing. For example, if the remote bit = 1, an address follows the remote bit in the PCP header and the RLP packet payload is forwarded to address module 950 along with the address. Alternatively, if the remote bit = 0, the RLP packet payload is sent to the first RLP 926 payload processing module.

The second PCP header processing module 940 determines, based on the value of an indicator value, for example, a remote bit value, in a PCP header of a packet, for example, a received MAC packet that was received over a aerial link and processed by the second MAC / PHY 944 module, if the received RLP packet payload is forwarded to its corresponding RLP 930 payload processing module or forward the received RLP packet payload to addressing module 950. Then the second PCP 932 header processing module performs the routing. For example, if the remote bit = 1, an address follows the remote bit in the PCP header and the RLP packet payload is forwarded to address module 950 along with the address. Alternatively, if the remote bit = 0, the RLP packet payload is sent to the second RLP 930 payload processing module.

first RLP header processing module 928 determines, based on the value of an indicator value, for example, a reprocess bit value, in an RLP header of a packet, for example, an RLP packet that was forwarded to the first RLP module 922 if

<img file="BRPI0712412A2_D0002.tif" />

forward the received RLP packet payload to your 926 payload processing module or forward the received RLP packet payload to the 950 addressing module.

So the first RLP header processing module

928 performs the routing. For example, if the reprocess bit

1, an address follows the reprocess bit in the RLP header and the RLP packet payload is forwarded to the addressing module 950 along with the address. Alternatively, if the reprocess bit = 0, the RLP packet payload is sent to the first RLP 926 payload processing module to perform a packet reassembly operation, for example, to obtain a higher level packet, for example. example, an IP packet that is passed to the first 946 application module.

The second RLP header processing module 932 determines, based on the value of an indicator value, for example, a reprocess bit value, in an RLP header of a packet, for example, an RLP packet that was forwarded the second RLP 924 module, if you forward the received RLP packet payload to your payload processing module

930 or forward the received RLP packet payload to the addressing module

950.

So the second header processing module

RLP

932 performs the routing. For example, if the reprocess bit

1, an address follows the reprocess bit in the RLP header and the RLP packet payload is forwarded to the addressing module 950 along with the address. Alternatively, if the reprocess bit = 0, the RLP packet payload is sent to the second RLP 932 payload processing module to perform a packet reassembly operation, for example, to obtain a higher level packet, for example. example, an IP packet that is passed to the second 948 application module.

42/52

The first RLP 922 module can be associated with a first access point, for example, a current server access point for the access terminal to which the access terminal 900 has an active connection, while the second RLP 924 module can be associated with an access point with which the access terminal previously had an active connection.

addressing module 950 forwards a packet payload to one of the RLP payload processing modules (926, 930) based on the address information communicated to the 950 addressing module.

received MAC packet 952 is a packet that has been received by the wireless receiver module 902 and processed through one or first and second MAC / PHY modules (942, 944). If the packet is processed through the first MAC / PHY 942 module, the packet is an entry to the first PCP 934 module, while if the packet is processed through the second MAC / PHY 944 module, the packet is an entry to the second PCP 936 module.

The determined bit value of the remote bit value in the PCP header 954 is obtained and used by a PCP header routing module (938, 940) to determine the packet payload routing. The determined bit value of the reprocess bit value in the RLP header 956 is obtained and used by an RLP header routing module (928, 932) to determine the packet payload routing. The forwarded RLP packet payload 958 is an RLP packet payload forwarded by one of a PCP header module (938, 940), an RLP header processing module (928, 930), or addressing module 950. O highest level reconstructed packet 960 is, for example, an IP packet, which has been reconstructed by processing from one of the load processing modules

43/52 useful RLP (926, 930), for example, by reassembling higher level packet fragments carried in one or more RLP packet payloads. The reconstructed top-level package 960 is sent to an application module (946, 948).

Figure is a drawing of an exemplary access point 1000 according to various modalities.

The exemplary access point

1000 is, for example, server access point, for example, local, 506 in figure 5. Exemplary access point

1000 includes a wireless receiver module

1002, a wireless transmitter module 1004, a processor

1006, a network interface module 1008 and memory 1010 coupled together through a bus 1012 over which the various elements can exchange data and information.

The memory

1010 includes 1017 routines and data / information

1018. The processor

1006, for example, a CPU, performs routines 1017 and uses data / information 1018 in memory

1010 to control the operation of access point 1000 and implement methods, for example, flowchart methods

700 of figure 7.

The wireless receiver module 1002, for example, an OFDM or CDMA receiver, is coupled to the receiving antenna

1014 through which the access point receives uplink signals from the access terminals. The wireless transmitter module 1004, for example, a transmitter

OFDM or CDMA, a 1016 transmission antenna is coupled, through which the access point transmits downlink signals to the access terminals.

The wireless transmitter module

1004 transmits a packet over an aerial link that includes a header

RLP generated by the RLP header generation module

1024 and at least by a part of a tunneled packet, for example, one of the packets being transmitted over the air link being generated by MAC 1 1034 packet.

44/52

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 for transmission and reception. In some modalities, the access point uses MIMO techniques.

network interface module 1008 is coupled to other network nodes, for example, other access points, AAA node, native agent node, etc., and / or the Internet via network link 1009. The network interface module network 1008 includes a transmission module 1011 and a receiver module 1013.

Routines 1017 include a tunnel interface module 1020, a packet fragmentation determination module 1022, a packet fragmentation module 1023, an RLP header generation module 1024, a PCP header generation module 102 6 and a MAC packet assembly module 1031. The PCP header generation module 1026 includes a non-fragmented packet header generation module 1028 and a fragmented packet header generation module 1030. The data / information 1018 includes a tunneled packet received from a remote access point 1032 and one or more generated MAC packets (generated MAC packet 1 1034, ..., generated MAC packet N 1036). The generated MAC packets (1034, ..., 1036) carry payload information from the received tunneled packet 1032. The generated MAC packet 1 1034 includes a generated PCP header 1 1038, a generated RLP header 1 1040, and a load portion useful 1 1042. The generated MAC packet N 1036 includes a generated PCP header N 1044, a generated RLP header N 1046, and a payload portion N 1048.

45/52

The tunnel interface module 1020 receives tunneled packets from another access point. The tunneled packet is transported over network link 1009 through receiver module 1013 from network interface module 1008 to tunnel interface module 1020. The exemplary received tunnel packet from remote access terminal 1032 is a packet received by the tunnel interface 1020.

The packet fragmentation determination module 1022 determines whether packet fragmentation should be performed on the contents of a tunneled packet. The 1023 packet fragmentation module fragments the packets that the 1022 packet fragmentation determination module determines to be too large to fit into a single MAC packet.

The RLP header generation module 1024, which is coupled to the 1023 packet fragmentation module, generates an RLP header that includes a value indicating the presence of an address to be used to route an RLP packet payload to an RLP module. For example, the generated RLP header includes a reprocess bit that is set to one and also includes an address following the reprocess bit.

The non-fragmented packet header generation module 1028 generates PCP headers that correspond to packets that were not subject to fragmentation, the non-fragmented packet generation module 1028 generates a PCP header that includes a value indicating the presence of an address to be used for routing payloads to an RLP processing module and ii) an address value when a portion of a tunneled packet that has not been fragmented must be transmitted. For example, the non-fragmented header generation module 1028 generates a PCP header that includes a remote bit = 1 followed by an address. In several modalities, the address included in the PCP header when the included value indicates the presence of an address, for

46/52 example, remote bit = 1, corresponds to a second access point, for example, a remote access point, which was the source of a tunneled packet that provided the information being transmitted with the generated PCP header.

The 1030 fragmented packet header generation module generates PCP headers corresponding to parts of packets that resulted from fragmentation, the 1030 fragmented packet header generation module generating PCP headers that include a value indicating the absence of a PCP header from a address used to route a payload to an RLP processing module. For example, the fragmented header generation module 1030 generates a PCP header including a remote bit = 0.

The MAC packet assembly module 1031 assembles generated elements, for example, a generated RLP header, a generated PCP header, and payload portion, for example, a fragmented payload portion, in a MAC package. The generated MAC packet 1 1034 and the generated MAC packet N 1036 represent the exemplary assembled MAC packets that are transmitted by the wireless transmitter module 1004.

Figure 11 is a drawing of an exemplary access point 1100 according to various modalities. Exemplary access point 1100 is, for example, remote access point 504 in figure 5. Access point 1100 is, for example, coupled to a second access point, the second access point having an overhead link with an access terminal. The second access point is, for example, access point 506 of figure 5, and the access terminal is, for example, access terminal 508 of figure 5.

Exemplary access point 1100 includes a wireless receiver module 1102, a wireless transmitter module 1104, a processor 1106, a network interface module 1108, and

47/52 the memory 1110 coupled together through a bus 1112 on which the various elements can exchange data and information. Memory 1110 includes routines 1118 and data / information 1120. Processor 1106, for example, a CPU, executes routines 1118 and uses the data / information

1120 in memory 1110 to control the operation of the access point

1100 and to implement methods, for example, the flowchart 600 methods of figure 6.

wireless receiver module 1102, for example, an OFDM or CDMA receiver, is coupled to the receiving antenna 1114 through which the access point receives uplink signals from the access terminals, for example, the access terminals which are local. The wireless transmitter module 110 4, for example, an OFDM transmitter or

CDMA, the 1116 transmission antenna is coupled, through which the access point transmits downlink signals to access terminals, for example, access terminal which is local and with which the access point is acting as an access point server. The wireless transmitter module 1104 transmits a packet, for example, the packet

Generated MAC 1140, which was generated by the packet generation module

MAC 112 6, to an access terminal using the access point

1100 over a wireless air link connection.

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 for transmission and reception. In some modalities, the access point uses MIMO techniques.

48/52

The network interface module 1108 is coupled to other network nodes, for example, other access points, AAA node, native agent node, etc., and / or the Internet via the 1109 network link. The interface module The network module 1108 includes a transmission module 1111 and a receiver module 1113. The transmission module 1111 transmits a generated tunneled packet, for example, packet 1138, to a second access point.

Routines 1118 include a remote determination module 1122, a remote device package processing module 1124, and a package generation module

MAC 1126.

The remote device packet processing module

1124 includes an RLP 1128 header generation module, an 1130 inter-access tunnel header generation module, an RLP header to the 1132 packet attachment module, and an 1134 tunnel header attachment module. / information

1120 include information indicating access terminals with an 1136 overhead link, a generated packet to be transported through a tunnel to another AP 1138, and a generated 1140 MAC packet.

remote determination module 1122 determines whether access point 1100 has an over-the-air connection to an access terminal to which a packet must be communicated. The remote device packet processing module

1124 generates a tunneled packet to communicate information to an access terminal with which the access point 1100 does not have an over-the-air connection. The MAC packet generation module 1126 generates a MAC packet to communicate information to an access terminal with which the access point 1100 has an over-the-air connection. Information 1136, indicating the access terminals with which the access point 1000 has an active connection, for example, a list

49/52 maintained from active connections, is used by remote determination module 1122.

The RLP header generation module 1128 generates an RLP header that includes a value set to indicate that an address to be used to route an RLP payload is not included in the generated RLP packet header, for example, a reprocess bit is adjusted = 0 in a generated RLP header. The inter-access tunnel header generation module 1130 generates a tunnel packet header used to tunnel an RLP packet that includes a packet to be communicated to a second access point for transmission to an access terminal. The generated inter-access tunnel header includes address information identifying access point 1100 as the source of the information to be transported to the access terminal. 0 tunnel is, for example, a layer 2 tunneling protocol (L2TP) tunnel.

The RLP header to the 1132 packet attachment module attaches a generated RLP header to a packet to be communicated to generate a combined RLP header and packet. The tunnel header attachment module 1134 attaches an inter-access point generated tunnel header generated by the 1130 inter-access tunnel header generation module to the combined RLP header and packet to generate a tunneled packet, for example , generated package 1138 to be transported through a tunnel to another access point.

The MAC packet generation module 1126 generates MAC packets that correspond to packets to be communicated to the access terminal with which the access point 1100 has an active wireless connection.

In several modalities, the nodes described here are implemented using one or more modules to carry out the

50/52 steps corresponding to one or more methods of the aspect, for example, signal processing, steps of generation and / or message transmission. Thus, in some modalities the various characteristics are implemented using modules. Such modules can be implemented using software, hardware or a combination of software and hardware. Many of the methods or method steps described above 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, compact disk,

DVD, etc.

to control a machine, for example, general purpose computer with or without additional hardware, to implement all or parts of the methods described above, for example, on one or more nodes.

Consequently, among other things, the aspect is directed at a machine-readable medium that includes instructions executable by machine to make a machine, for example, processor and associated hardware, perform one or more of the steps of the methods described above.

In various modalities, nodes described here are implemented using one or more modules to perform the steps that correspond to one or more methods, for example, signal processing, steps of generation and / or message transmission. 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, forwarding a connection request, forwarding a connection response, determining resource assignment, requesting resources, updating resources, etc. In some modalities, several features are implemented using modules. Such

51/52 modules can be implemented using software, hardware or a combination of software and hardware. Many of the methods or method steps described above 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, general purpose computer with or without additional hardware, to implement all or parts 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 methods described above.

In some embodiments, the processor or processors, for example, CPUs, of one or more devices, for example, communications devices such as access terminals and / or access points, are configured to perform the steps of the methods described as being performed communications device. Processor configuration can be achieved using one or more modules, for example, software modules, to control processor configuration and / or including hardware on the processor, for example, hardware modules, to perform the steps and / or configuration of control processor reported. Consequently, some but not all modalities are directed to a device, for example, a communications device, with a processor that includes a module that corresponds to each of the steps of the various described methods performed by the device in which the processor is included. In some, but not all

52/52 modalities, a device, for example, communications device, includes a module that corresponds 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.

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

OFDM and / or CDMA.

In various modalities, mobile nodes are implemented as notebook computers, personal data assistants (PDAs), or other portable devices including receiver / transmitter circuits and logic and / or routines, to implement the methods of various modalities.