Methods and devices of addressing based on pn code for wireless communication

Related Applications

This application claims priority to US Provisional Application №60 / 812,011, filed June 7, 2006, entitled "A METHOD AND APPARATUS FOR L2TP TUNNELING", and US Provisional Application №60 / 812,012, filed June 7, 2006, under the name "A METHOD AND APPARATUS FOR ADDRESSING MULTIPLE ACCESS POINTS", each of which are hereby specifically incorporated by reference.

TECHNICAL FIELD

The present invention relates to methods and apparatus for communications, and more particularly, to methods and apparatus related to the routing of packets.

BACKGROUND

Wireless communication systems often include a plurality of access points (AP) and / or other network elements in addition to access terminals, such as mobile or other end node devices. In many cases access terminals normally communicate with access points via wireless links while other elements in the network, such as AP, typically communicate with each other on stationary communications lines, for example fiber, cable or wire links. In the case of a wireless link band is a valuable scarce resource. Accordingly, it is desirable that transmission over the wireless link are operated efficiently without excessive overhead.

The communications links between access points and / or other network devices often have lower limits on bandwidth than wireless links between access terminals and access points. Accordingly, the relay link allows large overhead in relation to the length of the address and / or other information than the wireless link.

While the IP address is successfully used in the networks over the years, they tend to include an excessive number of bits. For communicating over wireless links it is desirable to use shorter addresses. However, it would be desirable that no changes in the addresses used on the wireless link, not prevented the use of IP addresses on the other communication lines, such as the relay links.

SUMMARY OF THE INVENTION

Describes methods and apparatus for communicating between an access terminal (AT) and an access point (AP). For communication over a wireless link between the AP and AT address based on a pilot PN code signal is used as an identifier, such as addresses AP. PN code for the pilot signal - an identifier of the pilot signal used for distinguishing pilot signal or pilot signals transmitted by different access points or sectors. When the pilot channel uses generation circuit based on a pseudorandom noise (PN), this identifier is usually called the PilotPN. In this application, the term "PN code" means an identifier pilot general type, and the PN code address is the address on the basis of the PN code.

Other examples of generating a pilot signal includes the Gold sequence, the pilots based on the beacon, etc., and in these cases address based on a PN code address is based on an identifier transmitted pilot signals used type.

Location based on the PN code may be based on the signals based on a pilot PN code signal received from the AP. Thus, based on address AP PN can be determined from pilot signals received from the AP. Address AP through PN can be shortened version of the PN code corresponding to the AP, the full PN code corresponding to the AP, or a value which can be derived in known manner from the PN code corresponding AP. Using the value based on the PN code as the address for the AP, AT can identify the AP in a wireless communication system without having to use the IP address corresponding to the AP. Moreover, addressing based on the PN code has the advantage that the information used is easily accessible to AT, since this information can be received from or output signals which are normally transmitted to the AT for other purposes. Thus, AT may identify a local or remote serving AP as the AP, which the AT has an active connection, without the need to carry out the process of identifying an IP address or another address update process. Furthermore, since the identifier based on the PN code used for communication over the wireless link may be shorter than the full IP address AP, can make effective use of the wireless link.

Location based on the PN code used to identify the AP, the serving AP can be used for transmission on the downlink and / or AT to transmit on the uplink. In the case of transmissions on the downlink, the serving AP indicates the source of the transmitted payload such as a remote or local AP Serving AP, including the address on the basis of the PN code corresponding to the transmitting device. For example, when a packet payload corresponding to a remote AP, the serving AP is transmitted via the Layer 2 tunnel, determines the address of the serving AP based on the PN code used to identify the remote AP, the IP address of the remote AP. You can use the lookup table maintained by the serving AP, which includes information and IP addresses corresponding to the device identifier information by the PN code. Search table allows the serving AP to establish a correspondence between an IP address and address on the basis of the PN code device, thus allowing to determine the IP address of an identifier on the basis of the PN code, or to determine the identity on the basis of the PN code of an IP address. In some embodiments, the actual address based on the PN code used in the wireless link are stored in the lookup table. However, the stored PN code information may be a value, such as a PN code AP, from which address on the basis of the PN code for wireless communication can be derived, for example, in a known manner, for example by clipping and / or by using a predetermined formula. In some embodiments, the lookup table may be maintained on the basis of the address information and the PN code transmitted by the relay communication lines connecting the network devices, such information may be transmitted as part of the routing update information, initial configuration information of the AP and / or other methods. For example, in some embodiments, AP initially supplied with information about the PN codes used in neighboring example physically proximate, AP, and their corresponding IP addresses.

In the case of uplink signals AT uses the address on the basis of the PN code for identifying the destination device for which the payload is transmitted, for example packet payload MAC (Media Access Control). The destination device identified location based on the PN code may be remote AP or current serving AP, to which the packet is transmitted over a wireless link. Receiving a packet from the AT, the serving AP determines whether the packet remote AP, and, if so, in some embodiments, determines an appropriate length, for example, IP (Internet Protocol) address of the AP assignment of the identifier PN code received over a wireless link connection. The received packet payload is forwarded to the destination AP by using the determined IP address as the destination address of the transmitted packet. Packet can be transmitted, and in various embodiments are sent, the destination AP is identified by a specific IP address, Layer 2 through a tunnel used for transmitting packets between the remote AP and the serving AP.

Thus, AT may transmit over a wireless link using a smaller number of bits for identifying the destination device than would be required if a long address, e.g. original IP address of the destination device, used for communication over the wireless link between the serving AP and AT.

An exemplary method for transmitting information to the access terminal comprises the steps of: generating a packet, said packet includes an address based on the PN code that identifies the access point, and information to be communicated to an access terminal; and transmitting the generated packet over a wireless link to the access terminal. An exemplary method of operating the access point to transmit information to the remote access point comprises the steps of: receiving a packet from the access terminal, wherein the packet includes an address based on the PN code and information to be transmitted to the remote device; determine the long address corresponding to the address on the basis of the PN code to be used for packet transmission to a remote device, wherein the long address includes more bits than the address based on the PN code; and transmitting the information to be transmitted with a long address to a remote device. Exemplary access point to transmit information to access terminal comprising: a network interface for receiving a packet from a remote device over a network connection, wherein the packet includes a long address and information to be transmitted; mapping module address length address based on the PN code to determine the address based on a PN code corresponding to the length of the address, the address on the basis of the PN code used in a wireless communication system, the address based on a PN code includes fewer bits than the longest address; generating module downlink burst for generating a packet including the address on the basis of the PN code and information to be transmitted; and a wireless transmitter for transmission over a wireless communication downlink burst.

An exemplary method of operating an access terminal for transmission of information comprising the steps of: receiving a signal from the device; generating an address based on the PN code from the received signal; and generating a packet including the address on the basis of the PN code, the packet is sent to the device. An exemplary method of operating an access terminal for receiving information from the remote device via an access point comprises the steps of: receiving a packet from the access point, including the address on the basis of the PN code corresponding to the remote unit and the information from the remote device; and identifying the remote device that transmits information from the addresses on the basis of the PN code and the stored information associated with the received address based on PN code to the access point. Exemplary access terminal to transmit information to a remote device via an access point comprises: a packet generation unit for generating a packet including the address on the basis of the PN code corresponding to the remote device, and the information to be transmitted to the remote device; and a wireless transmitter for transmitting the generated packet over a wireless link to the access point.

Although in the above Summary of the Invention The various embodiments, it should be understood that not necessarily all embodiments include the same features and some features described above are not necessary but can be desirable in some embodiments. Numerous additional features, embodiments and benefits are discussed in the following detailed description.

BRIEF DESCRIPTION OF DRAWINGS

1 - a wireless multiple-access communication according to one embodiment.

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

3 - an illustrative network includes an access network (AN) architecture and distributed access terminal (AT).

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

5 - is a flowchart of an exemplary method of operating the access point to transmit information to access terminal in accordance with various embodiments.

6 - is a flowchart of an exemplary method of operating an access point for communication with the remote access point.

7 - an exemplary access terminal in accordance with various embodiments.

8 - is a flowchart of an exemplary method of operating an access terminal for transmission of information in accordance with various embodiments.

9 - is a flowchart of an exemplary method of operating an access terminal for receiving information from the remote device through the access point.

10 - diagram of an exemplary access terminal in accordance with various embodiments.

Detailed description

Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (eg, 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), protocols / technologies wireless short-range communication, Bluetooth® technology, ZigBee® protocol, ultra wide band protocol [ultra wide band] (UWB), home radio frequency (HomeRF), Wireless Application Protocol public [shared wireless access] (SWAP), wideband technology, such as wireless Ethernet compatibility alliance (WECA), wireless fidelity alliance (Wi-Fi Alliance), networking technology 802.11 technology public switched telephone network technology, public heterogeneous communications network, such as the Internet, private wireless communications network, land mobile radio network, a system of code division multiple access (CDMA), broadband code division multiple access (WCDMA), a universal system for mobile telecommunications (UMTS), advanced mobile phone service (AMPS), multiple access with time division (TDMA), multiple access, frequency division (FDMA), multiple access orthogonal frequency division multiplexing (OFDMA), global system for mobile communications (GSM), radio transmission technology (RTT) on a single carrier (1X), the technology evolution data only (EV-DO), total radiocommunication packet (GPRS), enhanced data GSM environment (EDGE), a system of high-speed data transmission on the downlink connection (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 network.

Generally, a wireless multiple-access communication system can concurrently support communication with multiple wireless terminals. Each terminal communicates with one or more base stations via transmissions on forward and reverse links. The forward link (or downlink) - link from base stations to the terminals, and the reverse link (or uplink) - the communication link from the terminals to the base stations. This communication link may be established in a single-input single-output, multiple-input single-output or a multiple-input multiple-output (MIMO).

Figure 1 shows a wireless multiple-access communication according to one embodiment. The access point 100 (AP) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and another including 112 and 114. In Figure 1, only two antennas are shown for each antenna group, however, for each antenna group can be used more or fewer antennas. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118. Access terminal 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal 122 over forward link 126 and receive information from access terminal 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for connection. For example, forward link 120 may use a different frequency than that used by reverse link 118 line.

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

In communication over forward links 120 and 126, the transmitting antennas of access point 100 use beamforming to improve signal-noise ratio of forward links for the different access terminals 116 and 122. 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.

The access point may be a fixed station used for communicating with the terminals and may also be called an access point, Node B, 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.

2 shows a block diagram of an embodiment of an exemplary access point 210 and an exemplary access terminal 250 in a MIMO system 200. At access point 210, traffic data for a number of data streams from a data source 212 to transmit data processor (TX) 214.

In an embodiment, each data stream is transmitted over a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The result of multiplexing pilot and coded data for each data stream is then modulated (i.e., symbol mapped to) based on a particular modulation scheme (e.g., BPSK, QSPK, M-PSK or M-QAM), selected for that data stream to provide symbols modulation. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.

The modulation symbols for each of the data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). Then a TX MIMO processor 220 provides NT modulation symbol streams to NT transmitters (TMTR) 222a-222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is transmitted.

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. Then, NT modulated signals from transmitters 222a-222t are transmitted from NT antennas 224a-224t, respectively.

At access terminal 250, the transmitted modulated signals are received by NR antennas 252a-252r, and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a-254r.

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.

Then, RX data processor 260 receives and processes the NR received symbol streams from NR receivers (254a, ..., 254r) based on a particular receiver processing technique to provide NT "detected" symbol streams. Then, RX data processor 260 demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data from a data stream. The processing by RX data processor 260 further treatments carried TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and / or the received data stream. Then the reverse link message is processed by TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, transmitters 254a-254r, and transmitted via 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 a RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. Processor 230 then determines which pre-coding matrix to use for determining the beam-forming weights then processes the extracted message.

Memory 232 includes routines and data / information. Processors 230, 220 and / or 242 perform the routines and uses 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 perform the routines and uses the data / information in memory 272 to control the operation of the access terminal 250 and implement methods.

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

According to an aspect of the network comprises access terminals (AT) and an access network (AN).

AN supports both centralized and distributed configuration. Network architecture for centralized and distributed configurations shown in Figures 3 and 4 respectively.

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

In a distributed architecture shown in Figure 3, AN 302 comprises access points (AP) and home agents (HA). AN 302 includes a plurality of access points (AP_a 304, AP_b 306 AP_c 308) and home agent 310. In addition, AN 302 includes an IP cloud 312. AP (304, 306, 308) connected to the IP cloud via communication lines (314, 316, 318), respectively. IP cloud 312 is connected to the HA 310 through the communication line 320.

AP includes:

Network functions (NF):

- One per AP, and multiple NF can serve a single AT.

- NF unit is the connection point level IP (IAP) for each AT, i.e. NF, which the HA forwards the packets destined for AT. In the example shown in Figure 4, NF 336 is the current IAP for AT 303, as shown by line 322 in Figure 4.

- IAP may change (L3 handoff) to optimize routing of packets to the relay network AT.

- 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 status of the session).

- NF acts as the controller for each of the TF on the AP and performs functions such as the selection, administration and blocking resources for AT on TF.

Transceiver functions (TF) or sector:

- Several in the AP, and multiple TF can serve a single AT.

- Radio interface provides connectivity to AT.

- May be different for the forward and reverse links.

- Change (handover L2) based on radio conditions.

The AN 302 AP_a 304 includes NF 324, TF 326 and TF 328. In AN 302 AP_b 306 includes NF 330, TF 332 and TF 334. In AN 302 AP_c 308 includes NF 336, TF 338 and TF 340 .

AT includes:

- Interface I_x, represented by the mobile node (MN) for each NF in the active set.

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

AP communicate using a tunneling protocol defined at the level of IP. The tunnel is an IP-tunnel in-IP in terms of data and the L2TP tunnel management plan.

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

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

In a centralized architecture shown in Figure 4, NF already logically associated with a single TF, so the AN comprises network functions, access points and home agents. Exemplary AN 402 includes a plurality NF (404, 406, 408), the collection AP (AP_a 410, 412 AP_b, AP_c 414), HA 416 and IP cloud 418. NF 404 is connected to the IP Cloud 418 by link 420. NF 406 connected to the IP Cloud 418 by link 422. NF 408 is connected to IP cloud 418 via the communication cloud 424. The IP 418 is connected to the HA 416 by link 426. NF 404 is connected to (AP_a 410, 412 AP_b, AP_c 414) along lines connection (428, 430, 432), respectively. NF 406 is connected to (AP_a 410, 412 AP_b, AP_c 414) via communication lines (434, 436, 438), respectively. NF 408 is connected to (AP_a 410, 412 AP_b, AP_c 414) via communication lines (440, 442, 444), respectively.

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

Since NF acts as the controller for a TF, and many NF can be logically associated with a single TF, NF-AT to the controller, i.e. NF, communicates with AT as a part of the active set, performs the functions of allocating, managing and resources to TF block this AT. Therefore, multiple NF can manage resources on a single TF, although these resources are managed independently. In the example shown in Figure 4, NF 408 is acting as an IAP for AT 403, as shown by line 460.

Other logical functions performed are the same as for the distributed architecture.

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

In systems like DO and 802.20 AT receives a service from the AP, making the access attempt on an access channel of a particular sector (TF). NF, associated with TF, receiving the access attempt contacts the IAP, which is the session master for the AT, and retrieves a copy of the session AT (AT indicates the identity of the IAP by the fact that includes the UATI in the access payload. UATI may be used as the IP address to go directly to the IAP or an can be used to search for addresses IAP). In the case of successful access attempts AT are assigned air interface resources such as MAC ID and data channels to communicate with that sector.

In addition, AT may send a report indicating the other sectors that he can hear, and the intensity of their signals. TF receives the report and forwards it to the network controller in the NF, which in turn provides the AT active set. For DO and 802.20 as they are implemented today, there is exactly one NF, from which the AT may communicate (except-NF handoff when there are temporarily two them). Each of the TF, in communication with the AT, will forward the received data and signaling to this single NF. This NF also acts as a network controller for the AT and is responsible for coordination and management and allocation of resources for blocking the AT to use with the sectors in the active set.

Thus, the active set is a set of sectors in which the AT are assigned air interface resources. AT will continue to send periodic reports and the network controller may add or remove sectors from the active set as it is moved over the network AT.

NF in the active set will also retrieve the local copy of the session for the AT, when they become members of the active set. The session is required for proper communication with the AT.

For wireless link CDMA soft handover on the uplink each of the sectors in the active set may try to decode the transmission AT. On the downlink, each sector 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 feature of the active set is to allow the AT to switch quickly between sectors in the active set and maintain service without the need for new access attempts. An access attempt is usually carried out 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 AT. Therefore, an active set is useful for handoff without affecting the QoS active applications.

When the 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 promptly distribute to each of the sectors in the active set, in order to ensure optimal service from each sector. In some cases, for example, if you change the type of titles, or change security keys, AT may be completely unable to communicate with the sector, as long as these changes do not extend to this sector. Thus, each member of the active set should be updated when you change the session. Some changes may be less critical to synchronize than others.

There are three main types of state or context found in the network AT, which has an active connection:

Data state - a state of the network on the data path between the AT and the IAP or an NF during a connection. Condition data includes, e.g., header compression block state or RLP flow states, which are very dynamic and difficult to transfer.

Session state - a state in the network on the control path between the AT and the IAP, which is saved when you close the connection. 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, AT may negotiate the QoS configuration for a new application and submit to the new network filter specification and the flow indicating QoS requirements for the application. In another example, AT may negotiate the size and type of the headers used in communication with the AN. Approval of a new set of attributes is defined as the change in session.

Connection state - a state in the network on the control path between the AT and the IAP or an NF, which is not saved when you close the connection, and when the AT is in standby mode. Connection state may include such information as power control loop values, soft handoff timing, and active set information.

The IAP or L3 handoff the three types of state may need to be transferred between the old IAP and the new IAP. If the L3 handover may be performed only by the AT standby mode, it is necessary to carry only the state of the session. To support L3 handoff for an active AT, it may also be necessary to transfer the data state, and connections.

Systems like DO and 802.20, L3 performs handover condition data simply by asking multiple routes (or stacks of data), where the data state for each route locally for this route, that is, each route has an independent state of the data. Due to the binding of each IAP with a separate route, the state is not required to transfer data at handover. Further, even the best, step is to associate each NF with a separate route in which case L3 handoff is completely transparent with regard to the state of the data, except for the possible re-ordering packets.

Since the data state has multiple routes, the next logical step to support L3 handoff for an active AT is to move the control status of the connection from the IAP and the localization for each NF in the active set. To do this, set multiple control routes (or control stacks) and is given by radio, allowing control stacks are independent and local to each NF. This may require that some part of the agreement and the administration and allocation of resources to block the connection status transferred to the AT, as there is no longer a single NF to administer all the members of the active set. This may also create some additional requirements on the air interface design to avoid a close connection between TF - since different TF may not jointly use the same NF - in the active set. For example, for optimal operation, preferably to eliminate any tight synchronization between TF, which do not have the same NF, such as power control loops, soft handoff, etc.

Pushing the data and connection state down to the NF eliminates the need to transfer this state on the handover L3, and also simplifies the interface between the NF.

Therefore, the system defines multiple independent data and control stacks (called interfaces 3 and 4), to the AT to communicate with different NF, if necessary, and addressing mechanisms for the AT and the TF logical distinction between the stacks.

In principle, some session state (QoS profile, security keys, attribute values, etc.) can be done locally with respect to NF (or IAP), because it is too expensive to produce alignment each time in the presence of a handover NF (or a L3). In addition, the session state is relatively static and easy to carry. Only needed mechanisms of administration and update the session state as it changes and during IAP handoff when moving the session master.

Optimizing the session state transfer for L3 handoff is a useful feature for each system independently of the network architecture since it simplifies network interfaces and improves the smoothness of the handoff.

Management awareness against handover

A separate but related issue is the management handover L3 to AT. Currently, systems like DO and 802.20, AT knows handover L3, since it allocates and local stacks blocks, but does not control the time of the handover L3. This is called network mobility management. The question is whether to make AT the handoff controller, ie, whether to use mobility management on the part of AT.

To support fault tolerance and load balancing network should be able to make a handoff or have a mechanism for signaling to the AT for the handover. Thus, if a mobility management by the AT, the network still needs a mechanism indicate when it should occur.

Mobility management by the AT has some obvious advantages, such as allowing the use of a single mechanism for inter-and intra technology, or global and local mobility. It also simplifies network interfaces because it does not require the network elements to determine when to carry out the handover.

The main reason why systems like DO and 802.20 use network mobility, is that mobility from the AT is not optimized to work fast enough to support voice communications. An additional reason is the tunneling overhead due to end mobile IP tunnels (for MIPv6) in the AT. Q mobility latency can be solved by forwarding data using tunnels between the current and previous forward link serving sectors communication, and possibly also using a double addressing, when data is transmitted on multiple NF in the active set simultaneously.

L2 and L3 Handover

In SimpleRAN there are two types of handover. For example, handoff or L2 level 2 is replaced by the serving sector (TF) of the forward link or reverse link, and L3 handover is replaced IAP. L2 handoff should occur as quickly as possible in response to changing radio conditions. Systems like DO and 802.20 physical layer signaling is used for quick handover of the L2.

Handover L2 - is the transfer of the serving sector TF for the forward (FL) or reverse (RL) links. Handoff occurs when the AT selects a new serving sector in the active set based on RF conditions observed at the AT for that sector. AT performs filtered measurements of RF conditions for the forward and reverse links for all sectors in the active set. For example, 802.20 for the forward link the AT can measure the SINR of the captured pilots, general pilot channel (if available), and pilots on the signaling channel common use, to select the desired serving sector FL. For the reverse link, AT estimates the CQI erasure rate for each sector in the active set on the basis of commands up / down power supplied to the AT from the sector.

L2 handoff begins when the AT requests a different FL serving sector and RL control channel for the reverse link. Dedicated resources are assigned to the TF, when it is included in the active set for the AT. TF is already capable of supporting the AT to the handover request. The target serving sector detects the handoff request and completes the handoff resource assignment for traffic AT. TF handoff of the forward link requires two-way messaging between the source TF or IAP and target TF to receive data for the target TF to transmit. Handover TF uplink target TF may immediately assign resources AT.

Handover L3 - is the transfer of IAP. L3 handoff HA binding update provides a new IAP and requires a session transfer to the new IAP for the management plan. 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 radio link 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 a radio link as a Route A, while another NF may be associated with Route B. A serving TF can simultaneously send packets to an AT from Route A and Route B, i.e. from both NF, using a separate and independent sequence space for each.

The design of the system, there are two basic ideas of how to ensure that the processing of QoS for the mobile device and its traffic is stored in each handoff mode: Disconnect handover L2 and L3.

Reserve air interface resources for the session, and retrieve the target NF or TF before the handoff implementation to minimize the data flow interruption during the handoff. To this was added the target TF and NF to the active set.

The system is designed to share handovers L2 and L3, the system can support EF traffic during high-frequency handover L2. L3 handoff requires a binding update, which is limited to a frequency of 2-3 per second. To provide faster L2 handoff from 20 to 30 Hz handovers L2 and L3 should be performed independently and asynchronously.

For L2 handover active set management allows you to configure all of TF in the active set, and assign them to dedicated resources so that they are ready to serve the AT case handover L2.

Consider a mobile wireless communication system with multiple access points (AP), which provide service to access terminals (AT). Many systems have an active set, which is a collection AP, AT to assign resources. At this point, the AT may be within radio range of one or AP, in order to save battery power and reducing interference, may communicate only with one carefully selected AP (serving AP). Problem considered here is the delivery of messages and data between different AP in the system so that the serving AP may deliver messages to and from the AT.

AP can communicate through the tunnel L2TP (the tunneling protocol of the second level). If AP1 has to transmit a message or data to the AT, while as AP2 is the serving AP, the AP1 first uses L2TP tunnel for packet delivery to AP2, and AP2 delivers this packet to the AT using a mechanism involving the use of bit identifier such reprocess bit. Similarly, if the AT should transmit a message or data to AP1, while as a serving AP2, AP2 transmits a message to a predetermined bit of distance and AP2 transmits the packet to AP1 via the L2TP tunnel.

The L2TP header includes the following fields:

1. UserID: is the address of the user to which the packet is addressed L2T P

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

3. FlowID: in one design, this field may be present only in the forward link packets (packets destined for the AT), and it identifies the stream, which the serving AP should be used to deliver the packet to the AT

4. SecurityField: in one construction, this field may be present only in the reverse-link packets (packets originating from AT). SecurityField may include bits IsSecure, field KeyIndex (identification keys used for safe operation) and field CryptoSync.

In one embodiment, the packets are sent downlink L2TP. Here we describe the process used by the AP to send and receive L2TP packet downlink.

L2TP packet AP transmits downlink, when it has data or a message for transmission to the AT. AP forms the appropriate header and transmits the L2TP packet to the serving AP (or if she does not know the identity of the serving AP, possibly by routing the packet through a central node - IAP).

When an AP receives the L2TP packet downlink, it performs the following steps:

1. If the AP is not serving for the given UserID (title L2TP), it forwards the packet to the current serving AP (possibly by routing the packet through a central node - IAP)

2. If the AP is serving for the given UserID, it delivers the packet to the AT using the RLP flow and associated QoS attributes for this FlowID (title L2TP).

According to one aspect of the transmitted packets L2TP uplink. Here we describe the process used by the AP to transmit and receive L2TP packet uplink. L2TP packet AP transmits a reverse link when it receives a packet from the AT, and for that packet is set bit distance. The first step for the AP transmitted packets L2TP, is to determine the address.

Determination addresses: if the remote bit is set for a packet, the packet also includes an address field to identify, on which the AP is necessary to deliver the packet (target AR). Host AP compares the address field with the IP address of the AP. This comparison can be set:

1. The method relying on AT, wherein the messages describing the comparison is transmitted with AT to the AP, then the AP uses mapping information for mapping between the address used on the wireless link, and the IP addresses.

2. The method of network-based, according to which the information is used comparison, provides a central entity or target AP.

3. The method based on the PilotPN. In this case, the address field may be simply equal PilotPN (or some significant bits PilotPN) AR corresponding address. Host PilotPN and AP knows the IP address of the neighboring AP that is part of network configuration (which itself may be based on a network), and uses this information for comparison between the location based on the PN code and the corresponding IP addresses.

4. The method based on the address IAP, according to which the AT uses a special type of addresses to identify the AR, which is the point of connection to the Internet for the AT. Each AP in the active set of the AP, the corresponding AT, knows the IP address of the IAP for AT specific and can establish the correspondence between the IP address and location IAP IAP for AT.

After determining the address AP, transmits packets L2TP, may also, if necessary, to insert a field related to security, which are determined by the design protection.

When the AP receives the L2TP packet uplink, it performs the following steps:

1. If the AP is not serving for the UserID, of the received packet (L2TP tunnel), it ignores the packet.

2. If the AP is the serving UserID for the received packet, it processes the packet as if the packet is received from its own level MAC. Processing package may depend on SecurityField, adopted in the tunnel L2TP.

5 shows a flowchart 500 of an exemplary method of operating the access point to transmit information to access terminal in accordance with various embodiments. Operation begins at step 502 where the AP is switched on and initialized. The access point, carry out the method presented flowchart 500 represents, for example, the serving access point, which has an active wireless link with an access terminal. Thus, the access point is a serving access point from the perspective of an access terminal. Steps 504 and / or 506 are performed in some embodiments, but omitted in other embodiments. The sequence of operations will be described as if the steps 504 and 506 are enabled; but it is obvious that the sequence of operations may bypass step omitted.

Operation proceeds from start step 502 to step 504. In step 504 an access point, for example, the serving access point receives a packet from a remote access point, the received packet includes the IP address corresponding to the remote access point, and information to be transmitted to the terminal access. Then, in step 506, the access point, for example, the serving access point retrieves information from the database with an IP address matching location based on the PN code, address information on the basis of the PN code corresponding to the IP address of the remote access point. Operation proceeds from step 506 to step 508.

In step 508 an access point, for example, the serving access point generates a packet wherein the packet includes an address based on the PN code that identifies the access point, such as a remote access point, and information to be transmitted. Step 508 includes sub-step 510 at which an access point carries out a process represented by a flowchart 500 such as the serving access point specifies an address based on the PN code from the other addresses, such as IP address corresponding to the access point, such as a remote access point , the other address includes more bits than the address on the basis of the PN code. In some embodiments, sub-step 510 includes sub-step 512. In sub-step 512 the access point, carry out the method presented flowchart 500, for example, the serving access point specifies the address on the basis of the PN code corresponding to a remote access point from the extracted address information to based on the PN code corresponding to the IP address of the remote access point. Then, in step 514, the access point, for example, the serving access point transmits the generated packet over a wireless link.

In some embodiments, the address information on the basis of the PN code includes an address based on a PN code corresponding to a remote access point, and the step of the determination operation addresses use the extracted address based on a PN code as an address on the basis of the PN code included in the transmitted packet . In certain other embodiments, the extracted address information on the basis of the PN code includes a value from which an address based on a PN code corresponding to a remote access point can be derived by a predetermined function, and the step of determining the address on the basis of PN code corresponding to a remote Devices using a predetermined function to generate an address on the basis of the PN code value included in the extracted address information on the basis of the PN code. In some embodiments, a specific address on the basis of the PN code is a part of the pilot PN code signal used remote access point, and when generating the package include the generated packet information included in the received packet.

6 shows a flowchart 600 of an exemplary method of operating an access point for communication with the remote access point. Operation begins at step 602 where the AP is switched on and initialized and proceeds to step 604. In step 604, the access point receives the information indicating the PN codes used by other access points in the system. Then, in step 606, the access point saves the PN code information corresponding to other nodes in the system, with the corresponding address length corresponding to the other nodes. Operation proceeds from step 606 to step 608.

In step 608 an access point, for example a serving access point from the perspective of an access terminal receives a packet from the access terminal, wherein the packet includes an address based on the PN code and information to be transmitted to the remote device. Operation proceeds from step 608 to step 610. In step 610, the access terminal determines the long address corresponding to the address on the basis of the PN code to be used for packet transmission to a remote device, wherein the long address includes more bits than the address on the basis of the PN code. Step 610 includes sub-step 612, at which the access point retrieves from the database information matching the IP address from the address on the basis of the PN code, IP address corresponding to the address on the basis of the PN code. Operation proceeds from step 610 to step 614. In step 614, the access point transmits information to be transmitted with a long address to a remote device. In some embodiments, the step of transmitting information to be transmitted with a long address, the remote device transmits the received information to the remote access point using the specific IP address as a destination identifier in the header used to route the packet to the remote access point through the tunnel Level 2.

In some embodiments, the stored PN code information includes a value that can be determined in a predetermined manner based on the address of the PN code. In some embodiments, the stored PN code information includes an address based on a PN code corresponding to the IP address of the remote access point.

7 illustrates an exemplary access point 700 in accordance with various embodiments. Access point 700 transmits information over a wireless link to the access terminal for which it is serving access point. The exemplary access point 700 includes a wireless receiver module 702, wireless transmitter module 704, a processor 706, network interface module 708 and memory 710 coupled together via a bus 712 over which the various elements may interchange data and information. Memory 710 includes routines 718 and data / information 720. The processor 706, such as a CPU, executes the routines 718 and uses the data / information 720 in memory 710 to control the operation of the access point and implement methods such as the method shown in flowchart 500 shown in Figure 5, and / or the flowchart 600 shown in Figure 6.

Wireless receiver module 702, for example OFDM or CDMA receiver, is connected to receive antenna 714 via which the access point receives uplink signals from access terminals. Wireless receiver module 702 receives the packet from the access terminal, wherein the received packet includes the address based on a PN code and the information to be transmitted to a remote device, such as remote access point.

Wireless transmitter module 704, for example OFDM or CDMA transmitter, is connected to transmit antenna 716 via which the access point transmits downlink signals to access terminals. Module wireless transmitter 704 transmits, through a wireless communication downlink packets, for example a generated downlink packet, the module 724 includes an address based on a PN code as a header portion and a part of the packet payload comprising information to be transmission.

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

Network interface unit 708 connects the AP 700 to other network nodes, such as other access points, AAA node, home agent node, etc., and / or the Internet via network link 709. In various embodiments, a tunnel between AP, e.g. tunnels Layer 2 Tunneling Protocol, established at the relay network via the network interface unit 708, and the path of the tunnel includes a network link 709. Network interface module 708 receives a packet from a remote device, such as remote access point, via a network connection, such as communication link 709, the package includes a long address and information to be transmitted.

Procedure 718 includes a module 722 comparison with the length of the address location, based on a PN code generation unit 724 downlink burst, the module 726 updates the database, the address comparing module 728 on the basis of a long PN code and location module 730 generating the tunneled packets. Data / information 720 includes address information database 732 and state information 742 of the access terminal. Information database 732 address, which is available module 722 comparison with the length of the address location, based on a PN code includes stored information associating with long addresses corresponding address information based on the PN code. Address Information database 732 includes a plurality of sets of information corresponding to different access points in a communication system (information of the access point 1 733, ..., access point information 735 n). About 733 of the access point 1 comprises a long address 1 734 736 and the corresponding address information based on the PN code 1. The information of the access point 735 n includes n long address 738 and the corresponding address information 740 based on the PN code n. In some embodiments, the long address (734, 738) are IP addresses. In various embodiments, the address on the basis of the PN code PN code based on the pilot signal used by the access point having the longest address corresponding to the address on the basis of the PN code. In various embodiments, the long address - this is the address used for routing packets between access points, such as between the remote access point and the serving access point through the tunnel layer 2, such as a tunnel Layer 2 Tunneling Protocol and the information PN code includes a PN code, used for packet transmission over a wireless link. The status information of the access terminal includes state information corresponding set of access terminals, such as access terminals having an active wireless link with the access point 700 (state information 744 of the access terminal 1, ..., status information of the access terminal 746 N).

Module 722 Mapping long address with the address on the basis of the PN code determines the address based on a PN code corresponding to the length of the address, the address on the basis of the PN code used in a wireless communication system, the address based on a PN code includes fewer bits than the long address. Generation module downlink burst 724 generates a packet including the address on the basis of the PN code and information to be transmitted.

Module 728 matching addresses based on the PN code from long location determines the long address corresponding to the address on the basis of the PN code to be used for transmission of information to a remote device, such as remote access point, the long address includes more bits than the address based on PN code. Module 730 generating tunneled packets generates a packet to be transmitted to a remote device, such as remote access point, the module 730 generating tunneled packet generating package includes: i) the long address determined from the address on the basis of the PN code included in the received packet and ii) the information to be transmitted, which has been included in the received packet that included a shorter address used to determine the long address.

8 shows a flowchart 800 of an exemplary method of operating an access terminal for transmission of information in accordance with various embodiments. Operation begins at step 802 where the access terminal is powered on and initialized and proceeds to step 804. In step 804, the access terminal receives a signal from a device, such as a pilot signal from a remote access point. Then, in step 806, the access terminal generates an address based on the PN code from the received signal. In various embodiments, step 806 includes sub-step 808 where the access terminal uses a predetermined function to generate the address based on the PN code from the PN code of the pilot signal detected from the received pilot signal. In some such embodiments, the predetermined function uses the full pilot PN code signal as an address on the basis of the PN code of the remote device. In certain other embodiments, the predetermined function uses a part of the PN code of the pilot signal as an address on the basis of the PN code of the remote device, wherein a portion less than a full PN code for the pilot signal.

Operation proceeds from step 806 to step 810. In step 810, the access terminal maintains a database of information corresponding to a wireless link, and the IP address information identifying a correspondence between the IP address corresponding to a device, such as a remote access point and location-based PN code, generated in step 806.

Operation proceeds from step 810 to step 812, where the access terminal determines whether the address of the access terminal is not a wireless link based on a PN code for a device such as the remote access point. In various embodiments, step 812 includes sub-step 814 at which the access terminal checks to determine whether the access terminal is one of i) a predetermined reserved addresses; ii) the address outputted from the access terminal to the first access point to be used for transmission over the wireless link to the first access point, packets destined for the remote access point; and iii) the address issued by the network to be used for packet transmission over a wireless link to the remote access point.

Operation proceeds from step 812 to step 816. In step 816 a sequence of operations further determined depending on whether the found addresses one or more wireless links not on the basis of the PN code for a device such as the remote access point. If the address is not on the basis of the PN code was not found at step 812, then operation proceeds from step 816 to step 818; otherwise operation proceeds from step 816 to step 820.

Returning to step 818, in step 818, the access terminal generates a packet including the address on the basis of the PN code, the packet is sent to a device such as a remote access point. Operation proceeds from step 818 to step 822.

Returning to step 820, in step 820, the access terminal generates a packet including the address of the wireless link is not based on the PN code, the packet is sent to a device such as a remote access point. Operation proceeds from step 820 to step 822.

In step 822, the access terminal transmits the generated packet to the first communication device, for example a first access point over a wireless link. The transmitted packet is destined for a remote device such as a remote access point. The first access point is connected to a device such as a remote access point via a relay network providing communication line.

9 shows a flowchart 900 of an exemplary method of operating an access terminal for receiving information from the remote device through the access point. Operation begins at step 902 where the access terminal is powered on and initialized and proceeds to step 904. In step 904, the access terminal receives the pilot signal from the remote device. Then, in step 906, the access terminal generates an address based on a pilot signal from the received pilot signal. Step 906 includes sub-step 908 at which the access terminal uses a predetermined function to generate the address based on a pilot signal PN code from the pilot signal detected from the received pilot signal. In some embodiments, the predetermined function uses the full pilot PN code signal as an address on the basis of the PN code of the remote device. In certain other embodiments, the predetermined function uses a part of the PN code of the pilot signal as an address on the basis of the PN code of the remote device, wherein a portion less than a full PN code for the pilot signal. Operation proceeds from step 906 to step 910.

In step 910, the access terminal stores the address of the pilot signal generated from a received pilot signal in the information database that is used to establish the correspondence between the addresses on the basis of the PN code and long addresses. In various embodiments, the step of storing the address of the pilot signal generated from a received pilot signal in the information database based on the address stored pilot code with a long address corresponding to the remote device. In some such embodiments, the long address is an IP address corresponding to the remote device.

Operation proceeds from step 910 to step 912. In step 912, the access terminal receives the packet from the access point, including the address on the basis of the PN code corresponding to the remote unit and the information from the remote device. Then, in step 914, the access terminal identifies the remote unit which transmitted the address information on the basis of the PN code and the stored information associated with the received location-based PN code to the access point.

In one exemplary embodiment, the remote device is a remote access point and the remote unit previously acted as the active network connection point of the access terminal and the access point acts as a current active network connection point of the access terminal.

10 illustrates an exemplary access terminal 1000 according to various embodiments. Exemplary access terminal 1000 can transmit and sometimes conveys information to the remote device through the access point. Exemplary access terminal 1000 includes a wireless receiver module 1002, a wireless transmitter module 1004, a processor 1006, user I / O devices 1008 and memory 1010 coupled together via a bus 1012 over which the various elements may interchange data and information. Memory 1010 includes routines 1018 and data / information 1020. The processor 1006, such as a CPU, executes the routines 1018 and uses the data / information 1020 in memory 1010 to control the operation of the access terminal and implement methods such as the method shown in flowchart 800 shown in Figure 8, and the flowchart 900 shown in Figure 9.

Wireless receiver module 1002, e.g. OFDM or CDMA receiver, is connected to receive antenna 1014 via which the access terminal 1000 receives downlink signals from access points. Wireless receiver module 1002 receives a packet transmitted over a wireless link to the access terminal, which includes an address based on a PN code identifying the source of information included in the received packet, such as received packet 1058.

Wireless transmitter module 1004, e.g. OFDM or CDMA transmitter, is connected to a transmit antenna 1016 via which the access terminal 1000 transmits uplink signals to an access point. Wireless transmitter module 1004 transmits the generated packets, for example generated packet 1052 over a wireless link to the access point.

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

User I / O devices 1008 include, e.g., microphone, keyboard, keypad, switches, camera, speaker, display, etc. User I / O devices 1008 allow a user of access terminal 1000 to input data / information, access the output data / information and control at least some functions of the access terminal 1000, for example, initiate a communications session with a peer node, such as another access terminal.

Procedure 1018 includes a module 1022 to determine the address based on a PN code generation unit 1024 packet module 1026 identifying the source of the received packet and a module 1031 updates the address database. In some embodiments, procedure 1018 includes a module 1027 to determine whether the address is not based on a PN code and a module 1029 making a decision about the type of address. Data / information 1020 includes the adoption of a pilot in 1028, corresponding to a PN code 1030 received pilot signal and the corresponding particular address in 1032 on the basis of the PN code. Data / information 1020 also includes information address database 1034, which includes the address mapping information corresponding to a plurality of points of access (access point information 1036 1, ..., information 1038 of the access point n). Information database of addresses 1034 is, for example, a database of information matching a wireless link, and IP addresses. Information 1036 of the access point 1 comprises a long address 1 corresponding to the address 1040 and 1042 based on the PN code 1. The information of the access point 1 038 n includes a long address n 1044 and 1046 corresponding to the address on the basis of the PN code n. The database 1034 stores an address on the basis of the PN code determined from the received pilot signal. In some embodiments, the stored address on the basis of the PN code (1042, ..., 1046) are PN codes of pilot signal of which was determined address based on the PN code. For example, in some embodiments, pilot PN code signal 1030 - this is the same as the specific address on the basis of the PN code 1032. In some embodiments, the stored address on the basis of the PN code output from the PN code of the pilot signal from which to address based on a PN code determined according to a predetermined function. For example, a specific address on the basis of the PN code 1032 is output from the PN code of the pilot signal 1030 and two values ​​can be different and are sometimes.

In some embodiments, the address information database 1034 may, and sometimes does, include one or more alternate addresses not on the basis of the PN code corresponding to the long address. For example, the information 1038 of the access point n, in certain embodiments, includes an alternate address 1047 is not based on the PN code n, which also corresponds to the length of the address n 1044. Address based on the PN code, for example alternate address 1047 is not based on the PN code n represents, for example, one of predetermined reserved addresses, outputted from the access terminal 1000 on the first access point to be used for transmission over the wireless link to the first access point, packets destined for the remote access point, and addresses outputted from the network, to be used for packet transmission over a wireless link to the remote access point.

Data / information 1020 also includes information to access terminal state 1048, for example, information including a list of access points with which the access terminal is currently active link. Data / information 1020 also include a destination address 1050, and a generated corresponding packet 1052. The destination address is, for example, a long address, particularly IP address corresponding to the AP. The generated packet 1052 includes an address 1054 on the basis of the PN code, for example address based on a PN code corresponding to the destination address 1050, and payload information 1056. Data / information 1020 also includes received packet 1058 and the corresponding source address identified 1064. Adopted Package 1058 includes an address 1060 on the basis of the PN code and payload information 1062. An identified source address 1064 - this is a long address matches the address 1060 on the basis of the PN code.

Packet generation module 1024 generates a packet for example generated packet 1052 includes an address based on the PN code and information to be transmitted to the remote device. In some embodiments, the packet generation module 1024, at times, generates a packet including the address is not on the basis of the PN code and information to be transmitted to the remote device. In some such embodiments, the packet generation module 1024 includes a sub-module generating packets based on a PN code and generating submodule packages are based on the PN code.

Address determining module 1022 based on the PN code determines, for example generates address based on the PN code from the pilot signal, the address on the basis of the PN code corresponds to the access point from which was passed the pilot signal. For example, in accordance with one access point, address determination unit 1022 based on the PN code address 1032 determines based on the PN code from the received pilot signal 1028. In some embodiments, in determining, for example, address generation based on the PN code used previously specific function for generating addresses based on the PN code from the PN code of the pilot signal detected from the received pilot signal. In some such embodiments, the predetermined function uses the full pilot PN code signal as an address on the basis of the PN code of the remote device, which was received pilot signal. In certain other embodiments, the predetermined function uses a part of the PN code of the pilot signal as an address on the basis of the PN code of the remote device, wherein a portion less than a full PN code for the pilot signal.

The module 1026 identifying the source of the received packet identifies the source of the received packet with the address information database 1034. For example, the module 1026 identifying the source of the received packet processes the received packet 1058, checks the address on the basis of the PN code and determines from the information database of addresses 1034 source, such as a long address associated with the address 1060 on the basis of the PN code. An identified source address 1064 is output module 1026 identifying the source of the received packet is a long address (1040 ... 1044) in the database 1034.

The module 1031 updates the address database updates and maintains a database of information address 1034, for example, stored in a database in 1034 addresses the information matches the IP address corresponding to the remote device, and address on the basis of the PN code. For example, a specific address in 1032 on the basis of the PN code is stored in the information database of addresses 1034 and is associated with its access point and the corresponding length of the address.

Unit 1027 determining whether the address is not on the basis of the PN code determines whether the address of the access terminal 1000 is not a wireless link based on the PN code for the remote access point. In some embodiments, the packet generation module 1024 uses the address on the basis of the PN code to generate the packet, when determining whether a module 1027 determines that no address is not on the basis of the PN code for the remote access point; otherwise the packet generation module 1024 uses one of the available addresses not on the basis of the PN code. Module 1029 decision about the type of address determines what type of address to use. In some embodiments, module 1029 making a decision about the type of address decides whether to use the address on the basis of the PN code or address is not on the basis of the PN code. In some embodiments, module 1029 making a decision about the type of address decides which type of address is not on the basis of the PN code used in the presence of the aggregate does not alternate addresses based on the PN code. In some embodiments, different types of alternate addresses are associated with different parts of communication systems, various devices and / or different levels of priority.

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 steps of generation and / or transmission. 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, eg, RAM, floppy disk, CD-ROM, DVD, etc. to control a machine, e.g., general purpose computer with or without additional hardware has to implement some or all of the above described methods, e.g., in one or more nodes. Accordingly, one aspect provides a machine-readable medium including machine executable instructions cause the machine, for example a processor and associated equipment, to carry out one or more of the above steps (s) 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, such as signal processing steps of generation and / or transmission. Some exemplary steps include transmitting a connection request, receiving a connection response, the update information indicating the access point with which the access terminal has an active connection, forwarding the connection request, sending a connection response, determining resource assignment, requesting resources, update resources and m. d. 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, eg, RAM, floppy disk, CD-ROM, DVD, etc. to control a machine, e.g., general purpose computer with or without additional hardware has to implement some or all of the above described methods, e.g., in one or more nodes. Accordingly, various embodiments also provide a machine-readable medium including machine executable instructions cause the machine, for example a processor and associated equipment, to carry out one or more of the above steps (s) method (s).

In some embodiments, the processor or processors such as a CPU, one or more devices, such as communication devices such as access terminals and / or access points are capable of steps of the methods described as being carried by the communication device. Can configure the processor using one or more modules, such as program modules to control processor configuration and / or by including hardware in the processor, e.g., hardware modules, to perform above mentioned steps and / or control processor configuration. Accordingly, some but not all embodiments provide a device, such as a communication device having a processor which includes a module corresponding to each of the steps of the various described methods performed by a 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 a device in which the processor is included. The modules may be implemented using software and / or hardware.

Those skilled in the art that many additional variations on the methods and apparatus described above on the basis of the foregoing description. Such variations should be considered as within the scope of the invention. The methods and apparatus of various embodiments may be used, and, in various embodiments, 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 digital assistants (PDAs), or other portable devices including circuitry and logic and / or routines receiver / transmitter, for implementing the methods according to various embodiments.