Methods and apparatus for using control values to control communications processing

Methods and apparatus for tunneling packets between remote and serving Access points for delivery to an access terminal (AT) are described. Methods and apparatus for communicating control values and/or information in addition to information to be delivered to an AT over an airlink are also described. An AT uses the received control information to recover communicated packets. Some features support the use of various headers and/or indicators in the headers, e.g., RLP and/or Packet Correlation Protocol (PCP) headers, which may be used to control routing of communicated payloads to an RLP processing module corresponding to an AP which was the source of the communicated payload.

FIELD

Various embodiments are directed to methods and apparatus for communications, and more particularly to methods and apparatus related to using control values to control communications processing.

BACKGROUND

Wireless communications systems often include a plurality of access points (APs) and/or other network elements in addition to access terminals, e.g., mobile or other end node devices. In many cases access terminals normally communicate with access points via wireless communications links while other elements in the network, e.g., APs, generally communicate with one another via non-air links, e.g., fiber, cable or wire links.

As an Access Terminal (AT) moves in a system, and/or as airlink conditions change, the access terminal may loose or terminate a connection with an AP and may establish and/or maintain a connection with another AP. As a result, an AP which had an airlink connection with an AT may end up in a situation where it has undelivered packets which are to be communicated to an AT with which it no longer has a connection.

APs often subject IP packets and/or other higher level packets to fragmentation prior to transmission over an airlink. RLP (Radio Link Protocol) processing may be used to perform this function and/or to generate header which can be used in reconstructing the higher level packets from, e.g., smaller MAC packets, communicated over an airlink. Different access nodes may implement, e.g., the fragmentation function, slightly differently. Accordingly, in many embodiments, it may important that ATs receiving an RLP packet be able to identify the AP which was responsible for generating the RLP packets to begin with so that the packets can be processed by a corresponding RLP module and the higher level packet, in the case of fragmentation, reconstructed therefrom.

It should be appreciated that there is a need for methods and/or apparatus which support the communications of packets between an AP which is remote to an AT and an AP which is serving the AT and has an active airlink connection with the AT that can be used to deliver packets. There is also a need for methods and/or apparatus which can be used to communicate sufficient control information to allow an AT to apply the proper processing, e.g., RLP processing, to packets received over an airlink.

SUMMARY

Some features are directed to methods and apparatus which can be used to tunnel packets between a remote and serving Access Point for delivery to an access terminal (AT). Other features are directed to communicating control values and/or information in addition to information to be delivered to an AT over an airlink. Some features support the use of various headers, e.g., RLP and/or Packet Correlation Protocol (PCP) headers, which may be used to control routing of communicated payloads to an RLP processing module corresponding to an AP which was the source of the communicated payload.

An exemplary method of operating an access terminal in accordance with various embodiments, comprises: examining an RLP header of an RLP packet to determine if a reprocess indicator value in said RLP header has been set; and if it is determined that said reprocess indicator has been set: i) passing a payload corresponding to said indicator value to an addressing layer module; and ii) operate addressing layer module to deliver the payload corresponding to said indicator value to an RLP module corresponding to an address value included in said RLP packet with said reprocess indicator. An exemplary access terminal, in accordance with various embodiments, 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 said RLP payload processing modules based on address information communicated to said addressing module; a header processing module for determining, based on an indicator value included in a header, whether the header includes an address used for routing an RLP packet payload and forwarding the packet payload to said addressing module when the indicator value indicates that an address used for routing RLP packet payloads is included.

An exemplary method of operating a first access point, in accordance with various embodiments, comprises: receiving a radio link protocol packet, via an inter-access point tunnel, the received radio link protocol packet including information directed to an access terminal; determining if the received radio link packet fits in a MAC packet; if it is determined that the received radio link packet fits in a MAC packet: generating a MAC packet including the received radio link packet; and transmitting the generated MAC packet to the access terminal over an air link between said first access point and said access terminal. An exemplary access point, in accordance with some embodiments comprises: a tunnel interface module for receiving tunneled packets from another access point; a packet fragmentation determination module for determining if packet fragmentation is to be performed on the content of a tunneled packet; an RLP header generation module coupled to said packet fragmentation module for generating an RLP header including a value indicating the presence of an address to be used for routing an RLP packet payload to an RLP module; and a wireless transmitter for transmitting a packet over an airlink including an RLP header generated by said RLP header generation module and at least a portion of a tunneled packet.

An exemplary method of operating a first access point, in accordance with some embodiments, comprises: receiving a packet to be communicated to an access terminal; determining if the first access point is remote to the access terminal to which said received packet is to be communicated; if it is determined that the first access point is remote to the access terminal to which said received packet is to be communicated: i) generating an RLP header; ii) generating a tunnel header including a sender address corresponding to said first access point; and iii) transmitting the received packet with the RLP header and tunnel header to a second access point via a communications tunnel. An exemplary first access point, which is coupled to a second access point, said second access point having an airlink connection with an access terminal, in some embodiments, comprises: a remote determination means for determining if the first access point does not have an airlink connection with an access terminal to which a packet is to be communicated; remote device packet processing means for processing packets received from a remote access point, said remote device packet processing means including: i) RLP header generation means for generating an RLP header including a value set to indicate that an address to be used for routing an RLP payload is not included in the generated RLP packet header; ii) inter-access point tunnel header generation means for generating a tunnel packet header used for tunneling an RLP packet including said packet to be communicated to said second access point for transmission to said access terminal.

While various embodiments have been discussed in the summary above, it should be appreciated that not necessarily all embodiments include the same features and some of the features described above are not necessary but can be desirable in some embodiments. Numerous additional features, embodiments and benefits are discussed in the detailed description which follows.

DETAILED DESCRIPTION

Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include World Interoperability for Microwave Access (WiMAX), infrared protocols such as Infrared Data Association (IrDA), short-range wireless protocols/technologies, Bluetooth® technology, ZigBee® protocol, ultra wide band (UWB) protocol, home radio frequency (HomeRF), shared wireless access protocol (SWAP), wideband technology such as a wireless Ethernet compatibility alliance (WECA), wireless fidelity alliance (Wi-Fi Alliance), 802.11 network technology, public switched telephone network technology, public heterogeneous communications network technology such as the Internet, private wireless communications network, land mobile radio network, code division multiple access (CDMA), wideband 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), single carrier (1X) radio transmission technology (RTT), evolution data only (EV-DO) technology, general packet radio service (GPRS), enhanced data GSM environment (EDGE), high speed downlink data packet access (HSPDA), analog and digital satellite systems, and any other technologies/protocols that may be used in at least one of a wireless communications network and a data communications network.

Referring toFIG. 1, a multiple access wireless communication system according to one embodiment is illustrated. An access point100(AP) includes multiple antenna groups, one including104and106, another including108and110, and an additional including112and114. InFIG. 1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal116(AT) is in communication with antennas112and114, where antennas112and114transmit information to access terminal116over forward link120and receive information from access terminal116over reverse link118. Access terminal122is in communication with antennas106and108, where antennas106and108transmit information to access terminal122over forward link126and receive information from access terminal122over reverse link124. In a FDD system, communication links118,120,124and126may use different frequencies for communication. For example, forward link120may use a different frequency then that used by reverse link118.

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

In communication over forward links120and126, the transmitting antennas of access point100utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals116and122. Also, an access point using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access point transmitting through a single antenna to all its access terminals.

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

FIG. 2is a block diagram of an embodiment of an exemplary access point210and an exemplary access terminal250in a MIMO system200. At the access point210, traffic data for a number of data streams is provided from a data source212to a transmit (TX) data processor214.

Each transmitter (222a, . . . ,222t) receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. NTmodulated signals from transmitters222athrough222tare then transmitted from NTantennas224athrough224t, respectively.

At access terminal250, the transmitted modulated signals are received by NRantennas252athrough252rand the received signal from each antenna252is provided to a respective receiver (RCVR)254athrough254r. Each receiver (254a, . . . ,254r) conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

At access point210, the modulated signals from access terminal250are received by antennas224, conditioned by receivers222, demodulated by a demodulator240, and processed by a RX data processor242to extract the reverse link message transmitted by the receiver system250. Processor230then determines which pre-coding matrix to use for determining the beamforming weights, then processes the extracted message.

Memory232includes routines and data/information. Processors230,220and/or242execute the routines and uses the data/information in memory232to control the operation of the access point210and implement methods. Memory272includes routines and data/information. Processors270,260, and/or238execute the routines and uses the data/information in memory272to control the operation of the access terminal250and implement methods.

In an aspect, SimpleRAN is designed to significantly simplify the communications protocols between the backhaul access network elements in a wireless radio access network, while providing fast handoff to accommodate the demands of low latency applications, such as VOIP, in fast changing radio conditions.

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

The AN supports both a centralized and distributed deployment. The network architectures for the centralized and distributed deployments are shown inFIG. 3andFIG. 4respectively.

In a distributed architecture shown inFIG. 3, the AN302comprises access points (AP) and home agents (HA). AN302includes a plurality of access points (APa304, APb306, APc308) and home agent310. In addition, AN302includes an IP cloud312. The APs (304,306,308) are coupled to the IP cloud via links (314,316,318), respectively. The IP cloud312is coupled to the HA310via link320.

An AP includes a:

Network function (NF):One per AP, and multiple NFs can serve a single AT.A single NF is the IP layer attachment point (IAP) for each AT, i.e., the NF to which the HA forwards packets sent to the AT. In the example ofFIG. 4, NF336is the current IAP for AT303, as shown by the line322inFIG. 4.The IAP may change (L3 handoff) to optimize routing of packets over the backhaul to the AT.The IAP also performs the function of the session master for the AT. (In some embodiments, 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 like allocating, managing and tearing down resources for an AT at the TF.

Transceiver functions (TF) or sector:Multiple per AP, and multiple TFs can serve a single AT.Provides the air interface attachment for the AT.Can be different for the forward and reverse links.Changes (L2 handoff) based on radio conditions.

An AT includes a:Interface I_x presented to the mobile node (MN) for each NF in the active set.Mobile node (MN) to support IP layer mobility 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.

Exemplary AT303includes a plurality of Interfaces (I_a342, I_b344, I_c346) and MN348. AT303can be, and sometimes is, coupled to AP_a304via wireless link350. AT303can be, and sometimes is, coupled to AP_b306via wireless link352. AT303, can be, and sometimes is, coupled to AP_c308via wireless link354.

In a centralized architecture shown inFIG. 4, the NF is no longer logically associated with a single TF, so the AN comprises network functions, access points and home agents. Exemplary AN402includes a plurality of NFs (404,406,408), a plurality of APs (AP_a410, AP_b412, AP_c414), HA416and IP cloud418. NF404is coupled to IP cloud418via link420. NF406is coupled to IP cloud418via link422. NF408is coupled to IP cloud418via link424. IP cloud418is coupled to HA416via link426. NF404is coupled to (AP_a410, AP_b412, AP_c414) via links (428,430,432), respectively. NF406is coupled to (AP_a410, AP_b412, AP_c414) via links (434,436,438), respectively. NF408is coupled to (AP_a410, AP_b412, AP_c414) via links (440,442,444), respectively.

Since an NF acts as the controller for a TF, and many NFs can be logically associated with a single TF, the NF controller for an AT, i.e., the NF communicating with an AT as a part of the active set, performs the functions of allocating, managing and tearing down resources for the TF at that AT. Therefore, multiple NFs may control resources at a single TF, although these resources are managed independently. In the example ofFIG. 4, NF408is acting as an IAP for AT403, as shown by the line460.

The rest of the logical functions performed are the same as for the distributed architecture.

In systems like DO and 802.20, an AT obtains service from an AP by making an access attempt on an access channel of a particular sector (TF). The NF associated with the TF receiving the access attempt contacts the IAP that is the session master for the AT and retrieves a copy of the AT's session. (The AT indicates the identity of the IAP by including an UATI in the access payload. The UATI may be used as an IP address to directly address the IAP, or may be used to look up the address of the IAP.) On a successful access attempt, the AT is assigned air interface resources such as a MAC ID and data channels to communicate with that sector.

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

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

NFs in the active set will also fetch a local copy of the session for the AT when they join the active set. The session is needed to communicate properly with the AT.

For a CDMA air link with soft handoff, on the uplink each of the sectors in the active set may try to decode an AT's transmission. On the downlink, each of the sectors in the active set may transmit to the AT simultaneously, and the AT combines the received transmissions to decode the packet.

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

When, an AT and the session master in the IAP negotiate attributes, or alternatively the state of the connection changes, the new values for the attributes or the new state need to be distributed to each of the sectors in the active set in a timely manner to ensure optimal service from 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 at all with a sector until these changes are propagated to that sector. Thus every member of the active set should 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 in the network for an AT that has an active connection:

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

Session state is the state in the network on the control path between the AT and the IAP that is preserved when a connection is closed. Session state includes the value of the attributes that are negotiated between the AT and the IAP. These attributes affect the characteristics of the connection and the service received by the AT. For example, an AT may negotiate the QoS configuration for a new application and supply new filter and flow specifications to the network indicating the QoS service requirements for the application. As another example the AT may negotiate the size and type of the headers used in communication with the AN. The negotiation of a new set of attributes is defined as a session change.

Connection state is the state in the network on the control path between the AT and the IAP or an NF that is not preserved when a connection closes and the AT is idle. Connection state may include such information as power control loop values, soft handoff timing, and active set information.

In an IAP or L3 handoff the three types of state may need to be transferred between the old IAP and the new IAP. If only an idle AT can make an L3 handoff, then only the session state needs to be transferred. To support L3 handoff for an active AT, the data and connection state may also need to be transferred.

Systems like DO and 802.20, make L3 handoff of the data state simple by defining multiple routes (or data stacks), where the data state for each route is local to that route, i.e., the routes each have independent data state. By associating each IAP with a different route, the data state does not need to be transferred in a handoff. A further, even better step, is to associate each NF with a different route in which case L3 handoff is completely transparent to the data state, except for possible packet reordering.

Since the data state has multiple routes, the next logical step to support L3 handoff for an active AT is to move the control of the connection state from the IAP and make it local to each NF in the active set. This is done by defining multiple control routes (or control stacks) and defining the air interface so that the control stacks are independent and local to each NF. This may require that some of the negotiating and managing the allocation and tear down of resources of the connection state is transferred to the AT since there is no longer a single NF to manage all the members of the active set. It may also make some additional requirements on the air interface design to avoid a tight coupling between TFs—since different TFs may not share the same NF—in the active set. For instance, to operate in an optimal way, it is preferable to eliminate all tight synchronization between TFs that do not have the same NF, such as power control loops, soft handoff, etc.

Pushing the data and connection state down to the NFs eliminates the need to transfer this state on a L3 handoff, and also should make the NF-to-NF interface simpler.

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

Fundamentally, some session state (QoS profile, security keys, attribute values, etc.) cannot be made local to an NF (or IAP) because it is too expensive to negotiate every time there is a NF (or a L3) handoff. Also 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 IAP handoff where the session master moves.

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

A separate but related issue is the AT control of L3 handoff. Today, in systems like DO and 802.20, the AT is aware of the L3 handoff since it allocates and tears down local stacks, but it has no control of when L3 handoff occurs. This is called network-based mobility management. The question is whether to make AT the handoff controller, i.e., to use AT based mobility management?

To support fault tolerance and load balancing, the network needs either to be able to make the handoff or have a mechanism to signal to the AT to do a handoff. Thus if AT based mobility management is used, the network still needs a mechanism to indicate when it should occur.

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

The primary reason systems like 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 (for MIPv6) in the AT. The mobility latency can be solved by forwarding data using tunnels between the current and previous forward link serving 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:

Layer 2 or L2 handoff refers to changing of the forward link or reverse link serving sector (TF).

L3 handoff refers to changing 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 L2 handoff fast.

L2 handoff is transfer of the serving sector TF for the forward (FL) or reverse (RL) links. A handoff occurs when the AT selects a new serving sector in the active set based on the RF conditions seen at the AT for that sector. The AT performs filtered measurements on the RF conditions for the forward and reverse links for all sectors in the active set. For instance, in 802.20 for the forward link the AT can measure the SINR on the acquisition pilots, the common pilot channel (if present), and the pilots on the shared signaling channel, to select its desired FL serving sector. For the reverse link, the AT estimates the CQI erasure rate for each sector in the active set based on the up/down power control commands to the AT from the sector.

L2 handoff is initiated when the AT requests a different FL or RL serving sector via a reverse link control channel. Dedicated resources are assigned at a TF when it is included in the active set for an AT. The TF is already configured to support the AT before the handoff request. The target serving sector detects the handoff request and completes the handoff with the assignment of traffic resources to the AT. The forward link TF handoff requires a round trip of messaging between the source TF or IAP and target TF in order to receive data for the target TF to transmit. For reverse link TF handoff, the target TF may immediately assign resources to the AT.

L3 handoff is the transfer of the IAP. L3 handoff involves a HA binding update with the new IAP and requires a session transfer to the new IAP for the control-plane. L3 handoff is asynchronous to L2 handoff in the system so that L2 handoff is not limited by MIPv6 handoff signaling speed.

L3 handoff is supported over the air in the system by defining an independent route to each NF. Each flow provides multiple routes for transmission and reception of higher layer packets. The route indicates which NF processed the packet. For example, one NF may be associated at the TF and over the air as Route A, while another NF may be associated with Route B. A serving TF can simultaneously send packets to an AT from both Route A and Route B. i.e., from both NFs, using a separate and independent sequence space for each.

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

Decoupling of L2 and L3 handoff

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

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

For L2 handoff, the active set management allows all the TFs in the active set to be configured and dedicated resources assigned in order to be ready to serve the AT in the event of an L2 handoff.

Consider a Mobile Wireless Communication System with multiple access points (AP) that provide service to access terminals (AT). Many systems have an active set, which is a set of APs that have assigned resources to the AT. At a given point in time, an AT may be within range of radio communication with one of the APs, or for the purpose of battery power optimization and radio interference reduction, may communicate only with one carefully selected AP (serving AP). The problem considered here is the delivery of signaling messages or data packets from a non-serving AP through a serving AP.

Radio Link Protocol (RLP): Each AP has an RLP, that fragments upper layer packets, and if needed retransmits the fragments. The RLP also adds its own header to each transmitted fragment. The AT has multiple instances of RLP, one for each AP that is in the active set.

Tunneling: A serving-AP receives packets from a non-serving AP via an inter-AP tunnel called the L2TP (layer 2 tunneling protocol) tunnel. The serving AP may deliver packets received on the tunnel by two alternate methods that use the following two bits.

Remote bit: The remote bit is part of the Packet Correlation Protocol (PCP) header. The PCP header is also sometimes called a MAC consolidation header. The remote bit is set by the transmitting PCP and processed by the receiving PCP. If the remote bit has 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 serving AP.

Reprocess bit: The reprocess bit is part of each RLP payload. If the reprocess bit=1 (is set), the bit is followed by an AP address. If the reprocess bit is set the receiving RLP passes the reassembled packet 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 reassembled packet to the application (e.g. header decompressor or IP layer).

The decision for setting these bits is made by the serving AP (APb). For a packet that is received by APb from APa, there are the following two choices1. Remote=1, Reprocess=0: In this case, the serving AP does not use it's RLP and does not fragment the packet. This case may be used if the packet received at APb from APa is small enough to fit in one MAC payload. The serving AP also inserts an address in the packet, and this is the address known to the serving AP because it received the packet through the L2TP tunnel.2. Remote=0, Reprocess=1: In this case, the serving AP uses it's RLP and may fragment the packet. This case may be used if the packet received at APb from APa does not fit in one MAC payload. The serving AP also inserts an address in the packet, and this address is known to the serving AP because it received the packet through the L2TP tunnel.

FIG. 5includes an exemplary communications system500and a corresponding legend502. Exemplary communications system500includes a first access point APa504, a second access point APb506and an access terminal AT508. From the perspective of AT508, currently, APb506is its serving, e.g., local, access point. There is a wireless air link552between APb506and AT508. From the perspective of AT508, currently, APa504is a remote access point. There is a Layer 2 Tunneling Protocol tunnel550between APa504and APb506.

Access point a (APa)504includes a header a compressor module510, a RLP_a module512, a PCP_a module514and a MAC/PHY module516. Access point b (APb)506includes a header_b compressor module518, a RLP_b module520, a PCP_b module522and a MAC/PHY module524. Access Terminal (AT)508includes a header_b compressor module526, a RLP_b module528, a PCP_b module530, a first MAC/PHY module532, a header_a compressor module536, a RLP_a module538, a PCP_a module540, and a second MAC/PHY module542. It should be noted that PCP_b530routes based on the remote bit value included in the PCP header.

Legend502includes dashed line544, dotted line546and solid line548used to illustrate packet flow for three different examples. Dashed line544represents flow for a case of: no packet fragmentation; the remote bit is set; the reprocess bit is not set; and APa address is contained in the PCP header. Dotted line546represents flow for a case of: packet fragmentation at the RLP520of AP_b506; the remote bit is not set, the reprocess bit is set, and APa address is contained in the RLP header. Solid line548indicates a case of local delivery and APa504is not involved.

FIG. 5explains the flow of fragments from a non-serving AP (APa504) that are delivered through a serving AP (APb506) and describes the flow of the packets depending on the setting of the above two bits. Each of the packets in this example are exchanged between APa504and the AT508through MAC/PHY524of APb506and through PCP522of APb506.

Some features of various embodiments are:1. Allows different versions of RLP to execute on different APs. In this case, effectively, one RLP is allowed to tunnel data to another RLP. For example, RLP_a512of APa504can tunnel data to RLP_b520of APb506via L2TP tunnel550.2. Facilitates partial packet progress during handoff. Consider the case when part of an IP (or other) packet has been served by APa504when handoff happened. Then, APa504wishes to deliver the remaining part of the packet to the AT508. In this disclosure, APa504may send this remaining part to APb506, and APb506may deliver it to the AT508. At the AT508, this remaining part of the packet flows after the addressing layer534to RLPa538, where it is combined with the previously sent part.The disclosure allows APb506to send only the unsent part of the packet, and the entire packet does not have to be sent from APb506. This allows for more efficient use of bandwidth because no part of the packet is sent twice. Such partial packet progress is important when handoff is frequent and IP packets may be split into several MAC layer fragments.3. Facilitates signaling messages to go from non-serving APs to the AT. Signaling messages generated at APa504can be delivered through APb506, and this allows for efficient management of resources at the AP and AT508.4. Allows for two possible paths for tunneled packets: Packets received by a serving AP through the L2TP tunnel may be sent, e.g., by addressing module513, through two separate paths, one using the RLP of the serving AP, and the other not using the RLP of the serving AP. For example the path corresponding to dotted line546uses the RLP_b520of serving APb506, while the path corresponding to dashed line544does not use the RLP_b520of the serving APb506.

FIG. 6is a flowchart600of an exemplary method of operating an access point (AP). The AP performing the steps of flowchart600is sometimes referred to as the current AP. Operation starts in step602, where the access point is powered on and initialized. Operation proceeds from start step602to step604. In step604the access point receives a packet, e.g., an IP packet, to be communicated to an access terminal (AT). Then, in step606, 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 destination AT, then operation proceeds from step606to step608; otherwise, operation proceeds from step606to step620.

In step608, the AP generates an RLP header. Step608includes sub-step610, in which the AP set a reprocess bit=0. Operation proceeds from step608to step612, in which the AP adds the generated RLP header to the received packet. Operation proceeds from step612to step614.

In step614, the access point generates an inter-AP tunnel header, e.g., a Layer 2 Tunneling Protocol (L2TP) tunnel header, with the sender address equal to the AP address of the current AP. Operation proceeds from step614to step616. In step616the access point attaches the generated tunnel header to the generated RLP header and received packet combination. Then, in step618, the access terminal transmits the generated tunnel header, generated RLP header and received packet via an inter-AP tunnel, e.g., via a L2TP tunnel. In some embodiments, the destination at the other end of the tunnel is another AP, e.g., the serving AP for the AT to which the packet corresponds.

Returning to step620, in step620the access point performs normal transmission processing. Step620includes sub-step622in which the access point generates the MAC packet or packets, and then in step624transmits the generated MAC packet or packets, e.g., via an airlink to the access terminal.

Operation proceeds from either step618or624to end step626. The exemplary method of flowchart600is repeated for additional received radio link protocol packets which are to be communicated to an access terminal.

The access point performing the steps of flowchart600can be a remote access point or a serving, e.g., local, access point from the perspective of the access terminal to which the packet is to be communicated. In one example, the access terminal is AT508ofFIG. 5.

Steps606,612,614,616, and618apply to the case where the access point performing the method of flowchart600is a remote access point from the perspective of the access terminal, and the remote access point communicates information to be communicated to the AT via a backhaul network using an inter-AP tunnel, e.g., a L2TP tunnel, e.g., communicating the packet to the AT's serving, e.g., local AP. In one such case the remote access point performing the method of flowchart600is remote APa504ofFIG. 5. Steps620and624apply to the case where the access point performing the method of flowchart600is a serving, e.g., local, access point from the perspective of the access terminal, and the serving access point communicates information to the AT over a wireless link and the serving, e.g., local, AP does not use an inter-AP tunnel for such communication. In one such case the remote access point performing the method of flowchart600is serving, e.g., local APb506ofFIG. 5.

FIG. 7is a flowchart700of an exemplary method of operating a serving, e.g., local, access point. In start step702, the serving access point is powered on and initialized. The access point is a serving access point from the perspective of access terminals which are using it as a current point of network attachment. Operation proceeds from start step702to step704. In step704, the serving access point receives a radio link protocol (RLP) packet via an inter-AP tunnel, e.g., a Layer 2 Tunneling Protocol (L2TP) tunnel with sender address. Operation proceeds from step704to step706.

In step706, the serving AP determines whether or not the received RLP packet fits in an available MAC size packet. If the received RLP packet fits in a single MAC packet then operation proceeds from step706to step708. However, if the received RLP packet needs to be fragmented and portions communicated in different MAC packets, then operation proceeds from step706to step722.

Returning to step708, in step708, the serving access point generates a MAC packet. Step708includes sub-steps710and718. In sub-step710, the serving access point generates a PCP header. Sub-step710includes sub-steps712,714and716. In sub-step712, the serving access point sets a remote bit=1. Then, in sub-step714, the serving AP sets a PCP address=address of the remote AP of the sender, and in sub-step716, the serving access point inserts the remote bit and PCP address into the PCP header. Operation proceeds from sub-step710to sub-step718. In sub-step718, the serving access point forms a MAC packet including the generated PCP header and received RLP packet.

In step720, the serving access point transmits the generated MAC packet, e.g., over a wireless airlink to an AT for which the packet is intended. Operation proceeds from step720to end step744.

Returning to step722, in step722, the serving access point generates a MAC packet. Step722includes sub-steps724,732,734and738. In sub-step724, the serving access point generates an RLP header. Sub-step724includes sub-steps726,728and730. In sub-step726, the serving access point sets a reprocess bit=1. Then in sub-step728, the serving access point sets an RLP address=address of the remote AP of the sender. In sub-step730, the serving access point inserts the reprocess bit of sub-step726and the RPL address of sub-step728into an RLP header. Operation proceeds from sub-step724to sub-step732, in which the serving access point fragments the remaining received RLP payload if needed. Operation proceeds from sub-step732to sub-step734, in which the serving access point generates a PCP header. Sub-step734includes sub-step736, in which the serving access points sets a remote bit=0. Operation proceeds from sub-step734to sub-step738.

In sub-step738, the access point forms a MAC packet including the generated PCP header of sub-step734, the generated RLP header of sub-step724, and an RLP payload. The RLP payload is, e.g., a fragment of the RLP payload from the received RLP packet of step704. Operation proceeds from step722to step740. In step740the serving access point transmits the generated MAC packet of step722, e.g., via a wireless airlink, to the access terminal for which the packet is intended. Operation proceeds from step740to step742.

In step742, the serving access point determines whether or not there are any remaining RLP payload fragments to be transmitted corresponding to the received RLP packet of step704. If there are not more fragments, operation proceeds from step742to end step744. If there are still RLP payload fragments to be communicated, then operation proceeds to step722for the generation of another MAC packet.

In step744, operation terminates with regard to the method since the received radio link packet has been transmitted. The exemplary method of flowchart700is repeated for additional radio link protocol packets received over an inter AP tunnel, for which the access point is a serving access point.

FIG. 7corresponds to an AT's serving AP receiving and processing information communicated over an inter-AP tunnel, e.g., a L2TP tunnel, generating one or more MAC packets, and transmitting the generated one or more MAC packets over a wireless communications link between the serving AP and the AT. For example, the AT is AT508ofFIG. 5, and the serving AP performing the steps of flowchart700is APb506ofFIG. 5with respect to the tunneling cases.

FIG. 8comprising the combination ofFIG. 8AandFIG. 8Bis a flowchart800of an exemplary method of operating an access terminal (AT), e.g., a wireless mobile node. Operation starts in step802, where the access terminal is powered on and initialized. In start step802, the access terminal establishes a wireless connection with an access point, e.g., its current serving access point. Operation proceeds from start step802to step804.

In step804, the access terminal receives a MAC packet. Then, in step806a PCP module of the access terminal processes a PCP header corresponding to the received MAC packet and determines a remote bit value conveyed in the PCP header. Operation proceeds from step806to step808, where the access terminal proceeds along different operational flows as a function of the determined remote bit value from the PCP header. If the PCP module of the AT determines that the remote bit is not set (remote bit=0) then operation proceeds from step808to step814. However, if the PCP module of the AT determines that the remote bit is set (remote bit=1), then operation proceeds from step808to step812.

Returning to step814, in step814, the PCP module of the AT delivers the payload of the MAC packet to the serving, e.g. local, radio link protocol (RLP) module of the AT. Operation proceeds from step814to step816. In step816the serving, e.g., local, RLP module performs RLP processing. Step816includes sub-steps818,820,822,824,826,827and828. In sub-step818, the serving, e.g., local, RLP module processes the RLP header and determines the reprocess bit value. Next, in sub-step820the serving RLP processing module proceeds along different operation paths as a function of the determined reprocess bit value. In sub-step820, if the reprocess bit is not set (reprocess bit=0), then operation proceeds from sub-step820to sub-step822. However, if in sub-step820the reprocess bit is set (reprocess bit=1), then operation proceeds from sub-step820to sub-step827.

Returning to sub-step822, in sub-step822the serving RLP module performs a packet reassembly operation, and then in sub-step824, the serving RLP module passes the reassembled packet to an application module, e.g., a header decompression module or IP layer module. Operation proceeds from sub-step824to end step826.

Returning to sub-step827, in sub-step827the serving RLP module of the AT performs a packet reassembly operation. Operation proceeds from sub-step827to sub-step828. In sub-step828the serving RLP module of the AT passes the payload or processed payload to an addressing layer module of the AT.

Returning to step812, in step812, the PCP module of the AT delivers the payload of the MAC packet to the addressing layer module of the AT. Operation proceeds from step812to step830. In step830the addressing layer module examines the address, which followed the remote bit, and delivers the payload to the RLP module specified by the address. Operation proceeds from step830to step832. In step832the specified RLP module performs RLP processing. Step832includes sub-steps834,836,838,839,840,842and844. In sub-step834the specified RLP module processes the RLP header and determines the reprocess bit value. Next, in sub-step836the specified RLP processing module proceeds along different operation paths as a function of the determined reprocess bit value. In sub-step836, if the reprocess bit is not set (reprocess bit=0), then operation proceeds from sub-step836to sub-step838. However, if in sub-step836the reprocess bit is set (reprocess bit=1), then operation proceeds from sub-step836to sub-step839.

Returning to sub-step838, in sub-step838the specified RLP module performs a packet reassembly operation, and then in sub-step842, the specified RLP module passes the reassembled packet to an application module, e.g., a header decompression module or IP layer module. Operation proceeds from sub-step842to end step844.

Returning to sub-step839, in sub-step839, the serving RLP of the AT performs a packet reassembly operation. Operation proceeds from sub-step839to sub-step840. In sub-step840, the serving RLP module of the AT passes the payload or processed payload to an addressing layer module of the AT.

If operation had proceeded to sub-step828or sub-step840, then operation proceeds to step846. In step846, the addressing layer module of the AT examines the address, which followed the reprocess bit, and delivers the payload or processed payload to the RLP module specified by the address. Operation proceeds from step846via connecting node A848to step850. In step850, the specified RLP module identified in step846, performs a packet reassembly operation, e.g., combines a recovered packet fragment with any other previously recovered packet fragments conveyed by other MAC packets. Then, in step852the specified RLP module identified in step846determines if assembly of an upper level packet has been completed. Operation proceeds from step852to step854.

In step854, if the specified RLP module has completed reassembly of an upper level packet, e.g., an IP packet, then operation proceeds to step856where the specified RLP module passes the reassembled upper level packet to an application module, e.g., a header decompression module or an IP layer module. Operation proceeds from step856to end step866.

Returning to step854, in step854if the specified RLP module has not completed reassembly of an upper level packet, e.g., an IP packet, then operation proceeds to step858, where the specified RLP module stores the recovered upper level packet fragment. Operation proceeds from step858to step860, where the specified RLP module waits for additional corresponding packet fragments to arrive and be recovered. Then, in step862, the specified RLP module reassembles the additional corresponding upper level packet fragment or fragments with the fragment of step858obtaining an upper level packet. Operation proceeds from step862to step864in which the specified RLP module passes the reassembled upper level packet to an application module, e.g., a header decompression module or an IP layer module. Operation proceeds from step864to end step866.

FIG. 8corresponds to access terminal operations including MAC packet reception, PCP processing, addressing layer module operations, RLP processing, and upper level packet reassembly operations. The exemplary AT, e.g., AT508ofFIG. 5, includes a plurality of RLP modules, and utilizes one or more control bits, e.g., a remote bit and/or a reprocess bit and/or associated address in header fields, to determine which RLP module is to perform a packet reassembly operation. If a remote or reprocess bit is set to one, it is followed by an address field.

A reprocess bit=1 indicates that a higher level packet, e.g., an IP packet was 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 chopped up the higher level packet, but rather identifies the original source of the higher level packet. In some embodiments, a number of fragments=1 is also allowed. In such an embodiment, the reprocess bit can be set=1 with only one MAC packet communicated.

For an RLP packet sent and received via an L2TP tunnel, the reprocess bit will be set to zero since fragmentation has not yet occurred. If the serving AP's RLP 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 transmitted. Note that the reprocess bit corresponding to the RLP packet sent via the L2TP tunnel is different from the reprocess bit that the serving AP inserts.

A remote bit=1 and a reprocess bit=0 indicates that a higher level packet from a remote AP fit into a single MAC packet and is being communicated via a serving AP to the AT. With regard to the AT, the flow including steps804,806,808,812,830, and832including sub-steps834,836,838and842corresponds to such a case.

A remote bit=0 and a reprocess bit=0 indicates that a higher level packet from the serving, e.g., local, AP, fit into a single MAC packet and is being communicated to the AT. With regard to the AT, the flow including steps804,806,808,814, and816including sub-steps818,820,822and824corresponds to such a case.

The path including steps804,806,808,814,816including sub-steps818,820,827and828,846,848and850can represent either remote AP sourced IP packet fragment recovery or local sourced IP packet fragment recovery, where the address following the reprocess bit identifies the source of the IP packet which was fragmented and is being reassembled.

FIG. 9is a drawing of an exemplary access terminal900in accordance with various embodiments. Exemplary access terminal900is, e.g., access terminal508ofFIG. 5. Exemplary access terminal900includes a wireless receiver module902, a wireless transmitter module904, a processor906, user I/O devices908and memory910coupled together via a bus912over which the various elements may interchange data and information. Memory910includes routines918and data/information920. The processor906, e.g., a CPU, executes the routines918and uses the data/information920in memory910to control the operation of the access terminal and implement methods, e.g., the methods of flowchart800ofFIG. 8.

Wireless receiver module902, e.g., a CDMA or OFDM receiver, is coupled to receive antenna914via which the access terminal900receives downlink signals from access points. Wireless receiver module902receives packets, e.g., obtaining received MAC packet952. Wireless transmitter module904, e.g., a CDMA or OFDM transmitter, is coupled to transmit antenna916via which the access terminal900transmits uplink signals to access points. Wireless transmitter module904transmits generated packets, e.g., generated MAC packets, over an airlink 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 for both transmission and reception. In some embodiments, the access terminal uses MIMO techniques.

User I/O devices908include, e.g., microphone, keyboard, keypad, switches, camera, speaker, display, etc. User I/O devices908allow a user of access terminal900to input data/information, access output data/information, and control at least some functions of the access terminal900, e.g., initiate a communications session with a peer node, e.g., another access terminal.

Routines918include a first RLP module922, a second RLP module924, a first PCP module934, a second PCP module936, a first MAC/PHY module942, a second MAC/PHY module944, a first application module946, a second application module948and an addressing module950. The first RLP module922includes a first RLP payload processing module926and a first RLP header processing module928. The second RLP module924includes a second RLP payload processing module930and a second RLP header processing module932. The first PCP module934includes a first PCP header processing module938, and the second PCP module936includes a second PCP header processing module940. Data/information920includes a received MAC packet952, a determined bit value of remote bit in PCP header954, a determined bit value of reprocess bit in RLP header956, a forwarded RLP packet payload958, and a reconstructed higher level packet960.

The first RLP processing module922corresponds to a first access point, while the second RLP processing module924corresponds to a second access point. Addressing module950forwards packet payloads to one of the RLP payload processing modules (926,930) based on the information communicated to said addressing module950.

First PCP header processing module938determines, based on the value of an indicator value, e.g. a remote bit value, in a PCP header of a packet, e.g., a received MAC packet which was received over an airlink and processed by first MAC/PHY module942, whether to forward the received RLP packet payload to its corresponding RLP payload processing module926or to forward the received RLP packet payload to the addressing module950. Then the first PCP header processing module938executes the forwarding. 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 the addressing module950along with the address. Alternatively, if the remote bit=0, the RLP packet payload is sent to the first RLP payload processing module926.

Second PCP header processing module940determines, based on the value of an indicator value, e.g. a remote bit value, in a PCP header of a packet, e.g., a received MAC packet which was received over an airlink and processed by second MAC/PHY module944, whether to forward the received RLP packet payload to its corresponding RLP payload processing module930or to forward the received RLP packet payload to the addressing module950. Then the second PCP header processing module932executes the forwarding. 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 the addressing module950along with the address. Alternatively, if the remote bit=0, the RLP packet payload is sent to the second RLP payload processing module930.

First RLP header processing module928determines, based on the value of an indicator value, e.g. a reprocess bit value, in a RLP header of a packet, e.g., a RLP packet which was forwarded to first RLP module922, whether to forward the received RLP packet payload to its payload processing module926or to forward the received RLP packet payload to the addressing module950. Then the first RLP header processing module928executes the forwarding. 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 module950along with the address. Alternatively, if the reprocess bit=0, the RLP packet payload is sent to the first RLP payload processing module926to perform a packet reassembly operation, e.g., to obtain a higher level packet, e.g., an IP packet which is passed to the first application module946.

Second RLP header processing module932determines, based on the value of an indicator value, e.g. a reprocess bit value, in a RLP header of a packet, e.g., a RLP packet which was forwarded to second RLP module924, whether to forward the received RLP packet payload to its payload processing module930or to forward the received RLP packet payload to the addressing module950. Then the second RLP header processing module932executes the forwarding. 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 module950along with the address. Alternatively, if the reprocess bit=0, the RLP packet payload is sent to the second RLP payload processing module932to perform a packet reassembly operation, e.g., to obtain a higher level packet, e.g., an IP packet which is passed to the second application module948.

The first RLP module922may be associated with a first access point, e.g., a current serving access point for the access terminal with which the access terminal900has an active connection, while the second RLP module924may be associated with an access point with which the access terminal previously had an active connection.

Addressing module950forwards a packet payload to one of the RLP payload processing modules (926,930) based on address information communicated to said addressing module950.

Received MAC packet952is a packet which has been received by wireless receiver module902and processed through one or first and second MAC/PHY modules (942,944). If the packet is processed through first MAC/PHY module942the packet is an input to first PCP module934, while if the packet is processed through second MAC/PHY module944, the packet is an input to second PCP module936.

Determined bit value of remote bit value in PCP header954is obtained and used by a PCP header routing module (938,940) to determine packet payload routing. Determined bit value of reprocess bit value in RLP header956is obtained and used by a RLP header routing module (928,932) to determine packet payload routing. Forwarded RLP packet payload958is a RLP packet payload forwarded by one of a PCP header module (938,940), a RLP header processing module (928,930), or addressing module950. Reconstructed higher level packet960is, e.g., an IP packet, which had been reconstructed by processing of one of the RLP payload processing modules (926,930), e.g., by reassembly higher level packet fragments conveyed in one or more RLP packet payloads. The reconstructed higher level packet960is forwarded to an application module (946,948).

FIG. 10is a drawing of an exemplary access point1000in accordance with various embodiments. Exemplary access point1000is, e.g., serving, e.g., local, access point506ofFIG. 5. Exemplary access point1000includes a wireless receiver module1002, a wireless transmitter module1004, a processor1006, a network interface module1008and memory1010coupled together via a bus1012over which the various elements may interchange data and information. Memory1010includes routines1017and data/information1018. The processor1006, e.g., a CPU, executes the routines1017and uses the data/information1018in memory1010to control the operation of the access point1000and implement methods, e.g., the methods of flowchart700ofFIG. 7.

Wireless receiver module1002, e.g., an OFDM or CDMA receiver, is coupled to receive antenna1014via which the access point receives uplink signals from access terminals. Wireless transmitter module1004, e.g., an OFDM or CDMA transmitter, is coupled to transmit antenna1016, via which the access point transmits downlink signals to access terminals. Wireless transmitter module1004transmits a packet over an airlink including an RLP header generated by RLP header generation module1024and at least a portion of a tunneled packet, e.g., one of the packets being transmitted over the airlink being generated MAC packet11034.

In some embodiments, the same antenna is used for transmission and reception. In some embodiments multiple antennas and/or multiple antenna elements are uses for reception. In some embodiments multiple antennas and/or multiple antenna elements are uses for transmission. In some embodiments at least some of the same antennas or antenna elements are used for both transmission and reception. In some embodiments, the access point uses MIMO techniques.

Network interface module1008is coupled to other network nodes, e.g., other access points, AAA node, home agent node, etc, and/or the Internet via network link1009. Network interface module1008includes a transmission module1011and a receiver module1013.

Routines1017include a tunnel interface module1020, a packet fragmentation determination module1022, a packet fragmentation module1023, an RLP header generation module1024, a PCP header generation module1026and a MAC packet assembly module1031. PCP header generation module1026includes an unfragmented packet header generation module1028and a fragmented packet header generation module1030. Data/information1018includes a received tunneled packet from a remote access point1032and one or more generated MAC packets (generated MAC packet11034, . . . , generated MAC packet N1036). The generated MAC packets (1034, . . . ,1036) carry payload information from the received tunneled packet1032. Generated MAC packet11034includes a generated PCP header11038, a generated RLP header11040, and a payload portion11042. Generated MAC packet N1036includes a generated PCP header N1044, a generated RLP header N1046, and a payload portion N1048.

Tunnel interface module1020receives tunneled packets from another access point. The tunneled packet is conveyed via network link1009through receiver module1013of network interface module1008to tunnel interface module1020. Exemplary received tunnel packet from remote access terminal1032is a packet received by tunnel interface module1020.

Packet fragmentation determination module1022determines if packet fragmentation is to be performed on the content of a tunneled packet. Packet fragmentation module1023fragments packets which the packet fragmentation determination module1022determine to be too large to fit into a single MAC packet.

RLP header generation module1024, which is coupled to the packet fragmentation module1023, generates an RLP header including a value indicating the presence of an address to be used for routing an RLP packet payload to an RLP module. For example, the generated RLP header includes a reprocess bit which is set to one and also includes an address following the reprocess bit.

Unfragmented packet header generation module1028generates PCP headers corresponding to packets which were not subject to fragmentation, said PCP unfragmented packet generation module1028generating a PCP header including 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 which has not been fragmented is to be transmitted. For example, the unfragmented header generation module1028generates a PCP header including a remote bit=1 followed by an address. In various embodiments, the address included in the PCP header when the included value indicates the presence of an address, e.g., remote bit=1, corresponds to a second access point, e.g., a remote access point, which was the source of a tunneled packet which provided information being transmitted with said generated PCP header.

Fragmented packet header generation module1030generates PCP headers corresponding to portions of packets which resulted from fragmentation, said PCP fragmented packet header generation module1030generating PCP headers including a value indicating the absence, from the PCP header of an address used for routing a payload to an RLP processing module. For example, the fragmented header generation module1030generates a PCP header including a remote bit=0.

MAC packet assembly module1031assembles generated elements, e.g., a generated RLP header, a generated PCP header and payload portion, e.g., a fragmented payload portion, into a MAC packet. Generated MAC packet11034and generated MAC packet N1036represent exemplary assembled MAC packets which are transmitted by wireless transmitter module1004.

FIG. 11is a drawing of an exemplary access point1100in accordance with various embodiments. Exemplary access point1100is, e.g., remote access point504ofFIG. 5. Access point1100is, e.g., coupled to a second access point, the second access point having an airlink connection with an access terminal. The second access point is, e.g., access point506ofFIG. 5, and the access terminal is, e.g., access terminal508ofFIG. 5.

Exemplary access point1100includes a wireless receiver module1102, a wireless transmitter module1104, a processor1106, a network interface module1108and memory1110coupled together via a bus1112over which the various elements may interchange data and information. Memory1110includes routines1118and data/information1120. The processor1106, e.g., a CPU, executes the routines1118and uses the data/information1120in memory1110to control the operation of the access point1100and implement methods, e.g., the methods of flowchart600ofFIG. 6.

Wireless receiver module1102, e.g., an OFDM or CDMA receiver, is coupled to receive antenna1114via which the access point receives uplink signals from access terminals, e.g. access terminals which are local. Wireless transmitter module1104, e.g., an OFDM or CDMA transmitter, is coupled to transmit antenna1116, via which the access point transmits downlink signals to access terminals, e.g., access terminal which are local and with which the access point is acting as a serving access point. Wireless transmitter module1104transmits a packet, e.g., generated MAC packet1140, which has been generated by MAC packet generation module1126, to an access terminal using access point1100via a wireless airlink connection.

In some embodiments, the same antenna is used for transmission and reception. In some embodiments multiple antennas and/or multiple antenna elements are uses for reception. In some embodiments multiple antennas and/or multiple antenna elements are uses for transmission. In some embodiments at least some of the same antennas or antenna elements are used for both transmission and reception. In some embodiments, the access point uses MIMO techniques.

Network interface module1108is coupled to other network nodes, e.g., other access points, AAA node, home agent node, etc, and/or the Internet via network link1109. Network interface module1108includes a transmission module1111and a receiver module1113. Transmission module1111transmits a generated tunneled packet, e.g., packet1138, to a second access point.

Routines1118include a remote determination module1122, a remote device packet processing module1124and a MAC packet generation module1126. Remote device packet processing module1124includes an RLP header generation module1128, an inter-access point tunnel header generation module1130, a RLP header to packet attachment module1134, and a tunnel header attachment module1134. Data/information1120includes information indicating access terminals with an airlink connection1136, a generated packet to be conveyed via a tunnel to another AP1138, and a generated MAC packet1140.

Remote determination module1122determines if the access point1100has an airlink connection with an access terminal to which a packet is to be communicated. Remote device packet processing module1124generates a tunneled packet to be communicate information to an access terminal with which access point1100does not have an airlink connection. MAC packet generation module1126generates a MAC packet to communicate information to an access terminal with which the access point1100has an airlink connection. Information1136, indicating access terminals with which access point1000has an active connection, e.g., a maintained list of active connections, is used by remote determination module1122.

RLP header generation module1128generates an RLP header including a value set to indicate that an address to be used for routing an RLP payload is not included in the generated RLP packet header, e.g., a reprocess bit is set=0 in a generated RLP header. Inter-access point tunnel header generation module1130generates a tunnel packet header used for tunneling an RLP packet including a packet to be communicated to a second access point for transmission to an access terminal. The generated inter-access point tunnel header includes address information identifying access point1100as the source of the information to be conveyed to the access terminal. The tunnel is, e.g., a layer 2 tunneling protocol (L2TP) tunnel.

RLP header to packet attachment module1132attaches a generated RLP header to a packet to be communicated to generate a combined RLP header and packet. Tunnel header attachment module1134attaches a generated inter-access point tunnel header generated by the inter-access point tunnel header generation module1130to the combined RLP header and packet to generate a tunneled packet, e.g., generated packet1138to be conveyed via a tunnel to another access point.

MAC packet generation module1126generates MAC packets corresponding to packets to be communicated to access terminal with which said access point1100has an active wireless connection.

In various embodiments, nodes described herein 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 embodiments various features are implemented using modules. Such modules may be implemented using software, hardware or a combination of software and hardware. Many of the above described methods or method steps can be implemented using machine executable instructions, such as software, included in a machine readable medium such as a memory device, e.g., RAM, floppy disk, compact disc, DVD, etc. to control a machine, e.g., general purpose computer with or without additional hardware, to implement all or portions of the above described methods, e.g., in one or more nodes. Accordingly, among other things, the aspect is directed to a machine-readable medium including machine executable instructions for causing a machine, e.g., processor and associated hardware, to perform one or more of the steps of the above-described method(s).

In various embodiments nodes described herein 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, forwarding a connection request, forwarding a connection response, determining resource assignment, requesting resources, updating resources, etc. In some embodiments various features are implemented using modules. Such modules may be implemented using software, hardware or a combination of software and hardware. Many of the above described methods or method steps can be implemented using machine executable instructions, such as software, included in a machine readable medium such as a memory device, e.g., RAM, floppy disk, compact disc, DVD, etc. to control a machine, e.g., general purpose computer with or without additional hardware, to implement all or portions of the above described methods, e.g., in one or more nodes. Accordingly, among other things, various embodiments are directed to a machine-readable medium including machine executable instructions for causing a machine, e.g., processor and associated hardware, to perform one or more of the steps of the above-described method(s).

In some embodiments, the processor or processors, e.g., CPUs, of one or more devices, e.g., communications devices such as access terminals and/or access points, are configured to perform the steps of the methods described as being performed by the communications device. The configuration of the processor may be achieved by using one or more modules, e.g., software modules, to control processor configuration and/or by including hardware in the processor, e.g., hardware modules, to perform the recited steps and/or control processor configuration. Accordingly, some but not all embodiments are directed to a device, e.g., communications device, with a processor which includes a module corresponding 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 embodiments a device, e.g., communications device, includes a module corresponding to each of the steps of the various described methods performed by the device in which the processor is included. The modules may be implemented using software and/or hardware.

Numerous additional variations on the methods and apparatus described above will be apparent to those skilled in the art in view of the above descriptions. Such variations are to be considered within scope. The methods and apparatus of various embodiments may be, and in various embodiments are, used with CDMA, orthogonal frequency division multiplexing (OFDM), and/or various other types of communications techniques which may be used to provide wireless communications links between access nodes and mobile nodes. In some embodiments the access nodes are implemented as base stations which establish communications links with mobile nodes using OFDM and/or CDMA. In various embodiments the mobile nodes are implemented as notebook computers, personal data assistants (PDAs), or other portable devices including receiver/transmitter circuits and logic and/or routines, for implementing the methods of various embodiments.