CN101422009A - Automatic selection of home agent - Google Patents

Abstract

The claimed subject matter relates to assigning a home agent to a wireless terminal during authentication, authorization, and/or accounting with respect to the wireless terminal. The wireless terminal may provide an identification that may be relayed to the AAA server through the base station. The AAA server may then determine one or more home agents that may be associated with the wireless terminal. If more than one home agent can be assigned to the wireless terminal, the base station can resolve which home agent to use during registration of the wireless terminal. This determination may be important for MVNOs.

Description

Automatic selection of home agent

Cross References to Related Applications

This application claims the benefit of U.S. Provisional Patent Application No. 60/792,017, filed April 14, 2006, entitled "METHODS AND APPARATUS FOR SUPPORTING MOBILE VIRTUAL NETWORK." The entirety of said application is incorporated herein by reference.

technical field

The following description relates generally to communication systems and, more specifically, to selecting a home agent for use in connection with wireless terminal registration.

Background technique

Wireless networking systems have become a common way to communicate with other people around the world. Wireless communication devices such as cellular telephones, personal digital assistants, and the like are becoming smaller and more powerful to meet consumer needs and improve portability and convenience. Consumers have become dependent on the devices, demanding reliable service, extended coverage areas, additional services (eg, web browsing capabilities), and the ever-decreasing size and cost of the devices.

A typical wireless communication network (eg, using frequency, time, and code division techniques) includes one or more base stations that provide coverage areas to subscribers and mobile (eg, wireless) devices that can transmit and receive data within the coverage areas. A typical base station can simultaneously transmit multiple data streams to multiple devices for broadcast, multicast, and/or unicast services, where a data stream is a data stream that can be of independent reception interest to a user device. User devices within the coverage area of the base station may be interested in receiving one, more than one or all data streams carried by the composite stream. Likewise, a user device may transmit data to a base station or another user device.

In order for a wireless device to communicate in a wireless network, the device, or a host associated therewith, must be configured, including registering the wireless device with an entity that facilitates mobility management. In conventional cellular systems, a Public Switched Data Network (PSDN) is used to determine which entity is to be associated with the wireless device. This situation may be important when one or more mobile virtual network operators (MVNOs) have leased network infrastructure, since each MVNO may desirably be associated with a mobility management server. Thus, the wireless terminal will be associated with the leased mobility management server or with the MVNO that "owns" the subscriber using the wireless device. Also, conventionally, this is done at the PSDN, which is the first connection point for IP in conventional networks. However, as networks adapt over time to enable IP connections to occur at the periphery of the network, new ways of determining which mobility management server is associated with a wireless terminal will be necessary.

Contents of the invention

The following presents a simplified summary in order to provide a basic understanding of some aspects of claimed subject matter. This summary is not an extensive overview and is not intended to identify key/critical elements or to delineate the scope of the claimed subject matter. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

Claimed subject matter relates to assigning a home agent to a wireless terminal during authentication, authorization, and/or billing with respect to the wireless terminal. The wireless terminal may provide an identification that may be relayed to an AAA server through a base station. The AAA server can then determine one or more home agents that can be associated with the wireless terminal. If more than one home agent can be assigned to the wireless terminal, the base station can resolve which home agent to use during registration of the wireless terminal. This determination may be important to the MVNO.

In an aspect, a method for registering a wireless terminal with a home agent is described herein, wherein the method comprises: receiving an identification token from the wireless terminal when the wireless terminal requests access to a network, and The signature is provided to the AAA server. The method may further comprise receiving an identity of at least one home agent from the AAA server, and routing registration information from the wireless terminal to the identified home agent.

Also disclosed hereinafter is a base station, wherein the base station includes a memory holding instructions for receiving an identification from a wireless terminal and providing the identification to an AAA server when the wireless terminal requests access to a network . The memory may further include instructions for receiving an identification code of at least one home agent from the AAA server and routing registration information from the wireless terminal to the identified home agent. The base station may additionally include a processor that executes the instructions.

In yet another aspect, a communication device may comprise means for receiving from an AAA server a profile associated with a subscriber, the profile including an identification of a home agent assigned to an MVNO associated with the subscriber code; and means for establishing a Mobile IP tunnel with said identified home agent. Additionally, the machine-readable medium may have stored thereon machine-executable instructions for: receiving an identification token associated with a subscriber; providing the identification token to the AAA server; A profile of the subscriber, the profile including one or more home agents assigned to the MVNO associated with the subscriber. The machine-readable medium may additionally retain instructions for selecting a home agent from the one or more home agents and routing registration information from the subscriber to the selected home agent.

In yet another aspect, a processor may be configured to execute instructions for receiving from an AAA server a profile associated with a subscriber, wherein the profile includes an attribution assigned to an MVNO associated with the subscriber The proxy's identification code. The processor may also be configured to execute instructions for establishing a Mobile IP tunnel with the identified home agent.

Additionally, a method for determining one or more home agents associated with a wireless terminal is described hereinafter, wherein the method comprises: receiving an identification token associated with the wireless terminal; based at least in part on the identification identifying at least one home agent that may be associated with the wireless terminal; and providing an identification code of the at least one home agent to a base station communicatively coupled to the wireless terminal. Additionally, an AAA server is described herein, wherein the server includes memory including instructions for: receiving an identification associated with a wireless terminal; at least one home agent associated with the wireless terminal; and providing an identification code of the at least one home agent to a base station communicatively coupled to the wireless terminal. The AAA server may also include a processor to execute the instructions.

According to another aspect, an AAA server may comprise: means for receiving an identification associated with a subscriber from a base station communicatively coupled to the subscriber; A device of the network to which the subscriber is associated. Additionally, the AAA server may comprise: means for determining at least one home agent assigned to the network; and wireless means for assigning the at least one home agent to the subscriber for use by the subscriber The registered device of the terminal.

According to yet another aspect, a machine-readable medium is described herein, wherein the machine-readable medium has stored thereon instructions for: receiving, from a base station communicatively coupled to the subscriber, information related to the subscriber; and identifying an MVNO associated with the subscriber based at least in part on the signature. The instructions within the machine-readable medium may also include determining at least one home agent assigned to the MVNO and assigning the at least one home agent to the subscriber for registration of wireless terminals used by the subscriber. Furthermore, a processor is contemplated, wherein the processor is configured to execute instructions for: receiving a NAI of a subscriber requesting access to an IP-based wireless network; a network associated with the subscriber; determining at least one home agent assigned to the network, associating the subscriber with the at least one home agent; and relaying the association to a base station.

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in conjunction with the following description and accompanying drawings. The described aspects are indicative, however, of but a few of the various ways in which the principles of the claimed subject matter may be employed, and the claimed subject matter is intended to include all such aspects and their equivalents. Other advantages and novel features will become apparent from the following embodiments considered in conjunction with the drawings.

Description of drawings

1 is a high-level block diagram provided to illustrate a system for determining a home agent associated with a wireless terminal.

2 is a high-level block diagram provided to illustrate a system for determining a home agent associated with a wireless terminal.

3 is a representative flowchart illustrating a method for identifying a home agent associated with a wireless terminal.

4 is a representative flowchart illustrating a method for performing registration of a wireless terminal with an identified home agent.

Figure 5 is an example configuration diagram.

Figure 6 is an example configuration diagram.

7 is a block diagram of a system for identifying a home agent associated with a wireless terminal.

8 is a block diagram of a system for performing registration of a wireless terminal with an identified home agent.

9 illustrates an example wireless communication device.

10 illustrates an example communication system.

Figure 11 illustrates an example end node.

Figure 12 illustrates an example access node.

Figure 13 illustrates an example AAA server.

Detailed ways

The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of claimed subject matter. It may be evident, however, that the subject matter may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing claimed subject matter.

Additionally, various aspects are described herein with respect to terminals. A terminal can also be called a system, user device, secure digital card (SD card), subscriber unit, subscriber station, mobile station, mobile device, remote station, remote terminal, access terminal, user terminal, user agent, or user equipment. The user device can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a PDA, a palm-sized device with wireless connection capability, a module within a terminal, or other processing device connected to a wireless modem device.

Furthermore, aspects of claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques of making software, firmware, hardware, or any combination thereof to control a computer or computing component to implement the aspects of claimed subject matter various aspects. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes, etc.), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards and flash memory devices (eg, cards, sticks, key drives, etc.). Additionally, it should be appreciated that a carrier wave may be used to carry computer readable electronic data such as described for transmitting and receiving voice mail or for accessing a network such as a cellular network. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit described herein.

Referring now to FIG. 1 , a system 100 is shown to illustrate selecting one of several home agents to associate with a wireless terminal in conjunction with registering the wireless terminal with the home agent. In an example, system 100 can be a cellular IP system, such as a cellular IP system that can be used in conjunction with flash OFDM. System 100 includes a wireless terminal 102, which may be a mobile phone, PCMCIA card, memory card, personal digital assistant, and/or the like. The wireless terminal 102 can be associated with a base station 104 such that data can be transferred between the wireless terminal 102 and the base station 104 via radio. To enable such communication, one or more links between the wireless terminal 102 and the base station 104 need to be established and configured, wherein the configuration includes providing an IP address to a host device (not shown), which can be achieved by having the wireless terminal 102 communicate to the home agent Sign up to get the IP address.

In some cases, services may be provided to subscribers (e.g., owners/users of wireless terminal 102) over a particular network, such as a mobile virtual network operator (MVNO), a virtual private network (VPN), or other suitable network, and thus The subscriber should register with the Home Agent assigned to the particular network. For example, an MVNO typically leases network infrastructure and uses that infrastructure to provide services to subscribers associated with the MVNO. When a wireless terminal 102 is powered on or initially enters a network (eg, within range of a base station 104), authentication/authorization/billing procedures are undertaken prior to enabling the wireless terminal 102 to access services associated with the network. To this end, wireless terminal 102 may provide an identification to base station 104 , which in turn may relay this identification to AAA server 106 . In another example, the base station 104 may resolve the subscriber's specific identification code based on the identification provided by the wireless terminal 102 and transmit the identification code to the AAA server 106 . It should be understood that any suitable means for resolving the subscriber's identification code is contemplated by the inventors and intended to be within the scope of the claims appended hereto. The identification provided by the wireless terminal may be, for example, a Network Access Identifier (NAI), International Mobile Subscriber Identity (IMSI), or any other suitable identification.

Based on the identification, the AAA server 106 may determine, from a plurality of home agents, the home agent with which the wireless terminal 102 is associated during registration. In one example, AAA server 106 may return a home agent address (eg, IP address) specific to the "realm" (eg, usernumber@realm.com) of the user's NAI. In another example, the AAA server 106 can be communicatively coupled to an indexed database and can determine a home agent address based on inspection of this index given the signature. In yet another example, the base station 104 can include sufficient intelligence to determine a home agent (and an address associated with the home agent) to be assigned to the wireless terminal.

Furthermore, a profile associated with the wireless terminal 102 can reside in the AAA server 106, and the profile can include the address or hostname of the appropriate home agent. For example, AAA server 106 may return the AAA-Home Agent hostname, and base station 104 may resolve this hostname in domain name server (DNS) 108 . Additionally, the profile may include a network (e.g., MVNO)-home agent hostname identifier that may be provided to the base station 104, and the base station 104 may be locally configured to resolve this hostname via DNS 108 or other suitable database to One or more IP addresses.

The system 100 may include N home agents 110-114, wherein one or more of the home agents 110-114 may be associated with a network from a plurality of networks 116-120, wherein the networks 116-120 may be or may be MVNOs, VPNs, and other suitable networks are included so that each network can operate independently of the other (eg, different administrative domains, reuse of address space, etc.). Accordingly, multiple home agents can be associated with and/or can be assigned to a single network. For example, home agent 110 may be associated with network 116, home agent 112 may be associated with network 118, home agent 114 may be associated with network 120, and so on. For example, an association between a home agent and a network may mean that the home agent is directly connected to the network through a communication link (eg, T1, ATM, Ethernet, etc.). Additionally or alternatively, the home agent may connect directly to the network through use of a tunnel (eg, MPLS, IPinIP, GRE, etc.) established between the home agent and the network.

A home agent can be used to perform mobility management with respect to one or more wireless terminals. More specifically, a home agent may be a router that tunnels packets to and from wireless terminal 102 through a current point of attachment (eg, base station 104). Based on the identification provided by wireless terminal 102 during authentication, authorization, and/or billing, for example, a home agent address or hostname of one of home agents 110-114 may be identified by AAA server 106 and provided to base station 104. During registration of the wireless terminal 102, the base station 104 may indicate that the wireless terminal 102 (or a host associated therewith) should request IP configuration information from the identified home agent. Accordingly, base station 104 can establish a tunnel (eg, a Mobile IP tunnel) with the correct home agent.

AAA server 106 and/or base station 104 can determine an appropriate home agent associated with wireless terminal 102 via various methods/mechanisms. For example, a subscriber using wireless terminal 102 may be associated with an MVNO that is accessible through several home agents, and AAA server 106 may select one of the home agents. For example, the selection may be made based on geographic location (eg, the home agent that is geographically closest to the wireless terminal 102). In another example, the selection may be made based on an ordered list such that if the AAA server 106 associates the first wireless terminal with the first home agent associated with the MVNO, the AAA server will associate the second wireless terminal with the first home agent associated with the MVNO. associated with the second home agent associated with the MVNO. Additionally or alternatively, the AAA server 106 may use the weighted list to select a home agent for the wireless terminal 106 . For example, if a first Home Agent is associated with a larger resource than a second Home Agent, it is more likely that the wireless terminal will be assigned to the Home Agent associated with a larger amount of resources.

Specific examples are described next to better describe the selection of a particular home agent. The wireless terminal 102 may be associated with a user subscribing to services provided by the network 116 . When wireless terminal 102 connects to the network, it undergoes authentication by AAA server 106 . AAA server 106 may receive the identification token associated with wireless terminal 102 and may communicate back to base station 104 the address or hostname of home agent 110 (which is assigned to network 116). The base station 104 thus knows with which home agent it should tunnel (eg, using Mobile IP) to connect the wireless terminal 102 to the network 116 . For example, the base station 104 can resolve the hostname to the IP address of the home agent 110 through the use of the DNS 108.

Referring now to FIG. 2, there is shown a system 200 for illustrating the use of a proxy server (proxy) in connection with determining a home agent for use in connection with registering a wireless terminal. System 200 includes a wireless terminal 202 that accesses a network through a base station 204 . During authentication, wireless terminal 202 may provide an identification, such as a NAI, to base station 204 . The NAI can be relayed to an AAA server 206 , which determines a network (eg, MVNO) 208 associated with the subscriber using the wireless terminal 202 . For example, this determination can be made via analysis of domains within the NAI. The access request may then be provided to network AAA server 210 (eg, AAA server 210 specific to network 208). The network AAA server 210 can then authenticate the wireless terminal 202 and can provide the base station 204 with a specific address or hostname of at least one home agent 212 associated with the network 208 . The home agent address and/or hostname may be provided to base station 204 either directly or through AAA server 206 . For example, if base station 204 receives a hostname, it can resolve this hostname to an IP address through the use of DNS (not shown). Other mechanisms and means for resolving hostnames to IP addresses are contemplated by the inventors and are intended to be within the scope of the claims appended hereto. Base station 204 may establish a Mobile IP tunnel with home agent 212 , where home agent 212 may have a preconfigured tunnel with a gateway of network 208 . In another embodiment, base station 204 may assign a network home agent by resolving the domain of network 208 to a set of home agents (eg, via DNS, local configuration, and/or other suitable database).

AAA server 206 can communicate the address of home agent 212 back to base station 204 in a number of different ways. For example, base station 204 may be provided with an IP address that can be used as is. In another example, this address may be in the form of a hostname resolvable by base station 204 to one or more IP addresses (for load balancing). Additionally, the domain of network 208 can be provided to base station 204, and base station 204 can automatically construct a hostname (eg, homeagent.mvno) that is resolvable through use of DNS.

Referring to Figures 3 and 4, methods related to configuring wireless terminals and/or hosts are illustrated. Although, for purposes of simplicity of explanation, methods are shown and described as a series of acts, it is to be understood and appreciated that the methods are not limited by the order of acts, as some acts may occur in a different order and/or in accordance with one or more embodiments. Or concurrently with other actions from those shown and described herein. For example, those of skill in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events (eg, in a state diagram). Furthermore, not all illustrated acts may be utilized to implement methodologies in accordance with claimed subject matter.

Referring in particular to FIG. 3, there is illustrated a method 300 for providing a home agent identity/address to a base station associated with a wireless terminal. Method 300 begins at 302 and at 304 receives an identification associated with a wireless terminal. More specifically, this identification may be received in conjunction with authentication/authorization/accounting procedures undertaken when said wireless terminal attempts to access a wireless network. Furthermore, the signature can be a NAI, and can be received, for example, at an AAA server. At 306, a home agent desired to be assigned to the wireless terminal is determined, wherein this determination may be based at least in part on the identification. For example, a database may be accessed to determine the home agent. In another example, a domain within the NAI can be analyzed to determine a particular network, such as an MVNO, and based on this determination, a home agent associated with that network can be determined. At 308, a home agent address/identification code is provided to a base station communicatively coupled to the wireless terminal. Thereafter, the base station can resolve the home agent address (if necessary) and can establish a Mobile IP tunnel with the correct home agent. For example, method 300 may be implemented within an AAA server and may be undertaken in an IP-based cellular system. Method 300 then completes at 310 .

Referring now to FIG. 4, a method 400 for registering a wireless terminal with a home agent is illustrated. For example, method 400 can be undertaken in a base station. Method 400 begins at 402 and at 404 a network access request is received from a wireless terminal. For example, a wireless terminal can enter a geographic area associated with a network, can power on, and so on. The access request may include providing the base station with an identity associated with the wireless terminal (such that the wireless terminal can be authenticated/authorized). At 406, the identifier in the access request is provided to an AAA server, where the server may be an MVNO-specific AAA server, a wholesale AAA server, or the like. As noted above, the identifier may be a NAI, an IMSI value, a telephone number, or any other suitable data that may be used to identify a wireless terminal or a subscriber associated therewith.

At 408, identifications of one or more home agents assignable to the wireless terminal are received. For example, this identification, which may be an IP address, hostname, etc., may be determined at the AAA server and provided to the base station. For example, if one or more hostnames are received, the hostnames can be resolved to IP addresses through the use of DNS. At 410, a registration with one of the identified home agents is performed. For example, the AAA server can provide the base station with a domain or list of home agents, and the base station can resolve the appropriate home agent based on this list. In another example, the AAA server can provide the base station with a weighted list of home agents, where home agents can be weighted based on location, capacity, and/or the like. The base station can then resolve which home agent should be associated with the wireless terminal during registration of the terminal. In detail, the base station can establish a Mobile IP (MIP) tunnel with the selected home agent. Method 400 then completes at 412 .

Referring to FIG. 5 , a configuration diagram 500 is illustrated. Diagram 500 involves host 502 wireless terminal 504, base station 506, AAA server 508, home agent 510, and (as appropriate) DNS 512. Host 502 may be a computer or a portable device, and may include an IP stack. Wireless terminals 504 may be used to handle physical layer connections and communications with the network (eg, establish wireless communications with base stations 506). Base station 506 acts as an access point to network services and home agent 508 may be used in connection with mobility management. For example, the AAA server 508 may be used in connection with authentication, authorization, and/or accounting for the wireless terminal 504, and the DNS 512 may be used in connection with resolving IP addresses when given the hostname of the home agent.

The wireless terminal 504 and the base station 506 can take an air interface access at 514 , where this action 514 involves establishing a physical layer connection between the wireless terminal 504 and the base station 506 . At 516 , the wireless terminal 504 provides a network access request to the base station 506 , where the request may include an identification associated with the wireless terminal 504 . This designation may include, for example, NAI (or other suitable identifier). At 518, an AAA access request can be formed at base station 506 and provided to AAA server 508, where this request can include the NAI or other suitable identifier. At 519 , network access can be performed between wireless terminal 504 , base station 506 and AAA server 508 . For example, network access may involve mutual authentication between wireless terminal 504 and an AAA server. At 520, the AAA server 508 may accept the access request and provide a message to the base station 506 indicating acceptance of the access request. Additionally, the access accept message may include the home agent IP address, hostname (eg, MVNO-home agent hostname), or other suitable identifier of the particular home agent (eg, home agent 510).

If the AAA server 508 provided the hostname to the base station 506, at 522 the base station 506 can provide a DNS resolution request for this hostname to the DNS 512. At 524, DNS 512 provides a resolution response to base station 506, wherein the resolution response may include the IP address of home agent 510 (which is associated with the hostname).

At 526, a connection response message is provided from the base station 506 to the wireless terminal 504, where this message may be used in connection with configuring the wireless terminal 504. For example, the connection response message may include information identifying base station 506 at the network layer (eg, a unique identifier at the network layer). In an example, the information may be or may include an IP address associated with base station 506, an indication of the IP address that host 502 is ready, an IP address of home agent 510, and the like.

Thereafter, at 528, the wireless terminal 504 can provide a registration request message to the base station 506, wherein the registration request message can be compliant with MMP (a protocol based on Mobile IP but using fewer messages). The action at 528 establishes a link as the primary link between the wireless terminal 504 and the base station 506 (if multiple links are enabled). In this example configuration diagram 500 , MMP can run in wireless terminals 504 and base stations 506 . However, it should be understood that host 502 and/or home agent 510 may be configured to run a MMP. In addition, MIP can be performed between the wireless terminal 502 and the base station 506, where this configuration request message includes a home agent identity or access, as is conventional. Base station 506 is configured to receive the registration request message and analyze a profile associated with wireless terminal 504 (or a subscriber associated therewith). The profile can be received at 520, eg, in access information and can include a home agent address. The content of the profile may indicate whether the wireless terminal 504 is statically addressed or dynamically addressed. At 530 , the base station 506 may form and relay a MIP registration request message to the home agent 510 identified during act 520 . Additionally, if initial registration, an indication that there is no IP address assigned to the wireless terminal 504 can be provided at 530 (eg, by setting a flag or including a specific value within the request).

For example, at 532, home agent 510 may respond to base station 506 with an appropriate reply in MIP (MIP Registration Response message). This reply may include the IP address expected to be assigned to host 502, the address of home agent 510, and/or the amount of time the registration will be valid before expiring. Upon receiving the MIP Registration Response message, base station 506 can form a MMP Registration Response message and provide this message to wireless terminal 504 at 534 . This message may include a Lifetime field corresponding to the amount of time within the MIP Registration Response message. For example, the lifetime field may include a time that is equal to or less than a time indicated in the MIP Registration Response message. Alternatively, MIP may be run between home agent 510 and host 502 in conjunction with configuring host 502 and/or wireless terminal 504 .

Upon receipt of the MMP Registration Response message, the wireless terminal 504 may have established its link with the base station 506 as the primary link. Since this may be the first time the wireless terminal 504 has established a primary link, at 536 the wireless terminal 504 may indicate to the host 502 via the wireless terminal interface that the network is available. This trigger may initiate an auto-configuration process in the host 502, where the configuration is valid until the wireless terminal 504 instructs the network to go down via the wireless terminal interface. Usually, the host 502 only needs to be notified once that the primary link has been established. In parallel, the base station 506 can learn that the link with the wireless terminal 504 is the primary link with respect to the wireless terminal 504 .

At 538 , host 502 can generate a DHCP discover message, which can be communicated to wireless terminal 504 and/or base station 506 . If the base station 506 receives the DHCP discover message, then at 540 the base station 506 can respond to the host 502 with an appropriate DHCP offer message. This message may include various parameters (depending on the parameters in the DHCP discover message). For example, the DHCP offer message may include an IP address, a lease time, a gateway address for the assigned IP address, a netwrok mast for the assigned IP address, and the like. At 542, the host 502 may respond with a DHCP request message, and at 544, the base station 506 may respond again with an acknowledgment message. In other words, base station 506 can be configured as a DHCP server. Thus, host 502 is a connected and configured network layer.

In another example, wireless terminal 504 can be configured as a DHCP server. For example, the wireless terminal 504 can receive the DHCP discover message, and the wireless terminal 504 can learn configuration information associated with the host 502 . Thereafter, wireless terminal 504 can form and provide a DHCP offer message to host 502, and can receive a response from host 502 (eg, in the form of a DHCP request message). Thereafter, the wireless terminal 504 may provide a DHCP acknowledgment to the host 502 . Additionally, the host 502 can be configured to run MMP such that the host 502 (but not the wireless terminal 504) can generate and receive MMP messages. If the host 502 is configured in this way, it may not be necessary to configure the wireless terminal 504 or the base station 506 as a DHCP server, since the host 502 can be configured directly via MMP.

Referring now to FIG. 6 , a configuration diagram 600 is illustrated. Configuration diagram 600 involves terminal device 602, base station 604, AAA server 606, home agent 608, and (as the case may be) DNS 610. For example, terminal device 602 may be a wireless terminal. In another case, the terminal device 602 may be a wireless terminal (eg, computer, personal digital assistant (PDA), game console, camera, etc.) integrated with a host. The terminal device 602 and the base station 604 can take an air interface access at 612 , where this action 612 involves establishing a physical layer connection between the terminal device 602 and the base station 604 . At 614 , terminal device 602 may form and relay a network access request to base station 604 , wherein the request may include a NAI or other suitable identification associated with terminal device 602 .

At 616, the base station 604 can provide the AAA server 606 with the AAA access request. The request provided at 616 may include, for example, an identification flag. At 617 , a network access procedure may be performed between the terminal device 602 and the AAA server 606 . For example, the AAA server may determine a profile associated with terminal device 602 during the network access procedure. At 618, the AAA server 606 may generate an access accept message and provide this message to the base station 604, wherein the access request message may include the address and/or hostname of the home agent 608 (selected from several available home agents), For example, MVNO Home Agent hostname. For example, it may be desirable to assign to the end device 602 a particular home agent associated with the MVNO providing the service to the end device 602 .

At 620, if the access accept message includes a hostname, base station 604 can provide a DNS resolution request for this hostname to DNS 610. At 622, DNS 610 generates and transmits a resolution response message to base station 604, wherein the response message may include the IP address of home agent 608. Next, at 624 the base station 604 can provide a configuration message to the terminal device 602 , where this message can include the address of the home agent 608 . At 626, the terminal device may form a registration request in Mobile IP (MIP). For example, the registration request may involve requesting the IP address of a host (not shown) associated with end device 602 . At 628, the base station 604 can transmit the MIP registration request to the home agent 608, and at 630, the home agent 608 can respond with a MIP registration response message. At 632, the MIP Registration Response message is relayed from the base station 604 to the terminal device 602. In this case, the MIP Registration Response message may include additional configuration, such as home agent address, netmask, default router, DNS server, and other information typically included in DHCP messages (e.g., as in FIG. 5 ) .

Referring now to Figures 7 and 8 together, a system related to configuring a host is provided. The system can be represented as a series of interrelated functional blocks, which can represent functions implemented by a processor, software, hardware, firmware, or any suitable combination thereof. With particular reference to Figure 7, there is illustrated a system that facilitates association of a mobile terminal with a home agent. System 700 includes a logical module 702 for receiving a profile from an AAA server. For example, the profile may be received in response to the AAA server receiving an identification associated with the mobile terminal. Logic module 702 may include antennas, receiver chains, network ports, and/or any suitable hardware, software, firmware, and the like that may facilitate receiving profiles from an AAA server. System 700 additionally includes a logical module 704 for establishing a MIP tunnel with the identified home agent. For example, the home agent can be identified within the received profile. Logic modules 704 may include antennas, transmitter chains, processors, memory, hardware, software, firmware, and the like.

Referring to Fig. 8, illustrated is a system 800 for use in connection with registering a wireless terminal with a selected home agent. System 800 includes a logical module 802 for receiving an identification associated with a subscriber from a base station. For example, the identification mark can be NAI or other suitable identification data. Module 802 may include an antenna, receiver chain, processor, memory, and/or any suitable hardware, software, and/or firmware that may be used in connection with receiving the signature. System 800 also includes a logic module 804 for identifying a network associated with a subscriber. For example, the distinguishing can be made based at least in part on the signature. The modules 804 may include processors, databases, and the like. System 800 can further include a logical module 806 for determining at least one home agent assigned to the network, where module 806 can include a processor, memory, database, DNS, and the like. System 800 can further include a logical module 808 for assigning at least one home agent to a describer, where module 808 can include antennas, transmitters, transmitter chains, network ports, processors, memory, and the like.

Referring now to FIG. 9, a wireless communication device 900 is illustrated. A wireless communication device can be, for example, a wireless terminal, a base station, and/or an AAA server. Apparatus 900 may include memory 902, which may include instructions related to, for example, generating, packaging, and/or receiving an identification token associated with a subscriber. Additionally, memory 902 can include instructions for selecting a home agent based at least in part on the received subscriber identification code. Additionally, memory 902 can include instructions for establishing a MIP tunnel, etc., between the base station and the selected home agent. Device 900 may also include a processor 904 that may execute instructions held in memory 902 .

To provide additional context for one or more embodiments described herein, Figure 10 is provided to illustrate an example communication system 1000 comprising multiple nodes interconnected by communication links. System 1000 may use Orthogonal Frequency Division Multiplexing (OFDM) signals to communicate information over wireless links. However, other types of signals are also contemplated, such as Code Division Multiple Access (CDMA) signals or Time Division Multiple Access (TDMA) signals (along with signals used in terrestrial networks). Nodes in communication system 1000 exchange information based on a communication protocol (eg, Internet Protocol (IP)) using signals (eg, messages). The communication links of system 1000 may be implemented, for example, using wires, fiber optic cables, and/or wireless communication techniques. System 1000 includes a plurality of end nodes 1002-1012, which access communication system 1000 through a plurality of access nodes 1014-1018. End nodes 1002-1012 may be, for example, wireless communication devices or terminals, and access nodes 1014-1018 may be, for example, wireless access routers or base stations. The communication system 1000 also includes a number of other nodes 1020-1030 for providing interconnectivity or providing specific services or functions.

The communication system 1000 depicts a network 1060 comprising an access control node 1020 (which may be an AAA server), a first mobility support node 1022, a second mobility support node 1024, and an application server node 1026 (which may be a DNS server, for example), All nodes are connected to intermediate network node 1028 by corresponding network links 1032-1038, respectively. In some embodiments, the access control node (e.g., Remote Authentication Dial-In User Service (RADIUS) or Diameter server) supports authentication, authorization, and/or accounting of end nodes and/or services associated with end nodes . In some embodiments, mobility support nodes 1022 and 1024 (e.g., Mobile IP Home Agents and/or Context Transfer Servers) (e.g., by redirecting traffic to and from end nodes and/or transferring communication with access nodes) The state associated with the end node is used to support the mobility of the end node between access nodes (eg, handover). In some embodiments, an application server node 1026 (e.g., a session initiation protocol server, streaming media server, or other application layer server) supports session signaling for services available to end nodes and/or provides services or content available to end nodes . In an example, different end nodes may be associated with different mobility support nodes according to the network to which they belong. For example, a first mobility support node 1022 may be associated with a first network, while a second mobility support node 1024 may be connected to a second network. The network can be, for example, an MVNO, a VPN, and/or combinations thereof. As an example, mobility support nodes 1022 and 1024 may be coupled to a network gateway module (not shown) that enables the nodes to couple to first and second networks, respectively.

Intermediate network nodes 1028 in network 1060 provide interconnectivity to network nodes external to network 1060 through network links 1034 . Network link 1034 connects to intermediate network node 1030, which provides further connectivity to access nodes 1014, 1016, and 1018 through network links 1036-1040, respectively. Each access node 1014-1018 is depicted as providing connectivity to end nodes 1002-1012, respectively, through corresponding access links 1042-1052, respectively. In communication system 1000, each access node 1014-1018 is depicted as providing access using a wireless technology (eg, a wireless access link). However, wired technology may also be used in conjunction with providing access. The radio coverage area (eg, the communication cell 1054-1058 of each access node 1014-1018) is illustrated as a circle surrounding the corresponding access node.

The communication system 1000 may be used as a basis for the description of the various embodiments described herein. Alternative embodiments include various network topologies in which the number and types of nodes (including network nodes, access nodes, end nodes, and various control, support, and server nodes), the number and types of links, and the number and types of links between the various nodes The interconnectivity of the communication system 1000 may be different from that of the communication system 1000. Additionally, some of the functional entities depicted in the communication system 1000 may be omitted or combined. The location or placement of said functional entities may also be changed.

11 provides an illustration of an example end node 1100 (eg, a wireless terminal, a host device, or a combination thereof). End node 1100 is a representation of a device that may function as any of end nodes 1002-1012 (FIG. 10). The end node 1100 includes a processor 1102 , a wireless communication interface module 1104 , a user input/output interface 1106 and a memory 1108 coupled together by a bus 1110 . Thus, through the bus 1110, the various components of the end node 1100 can exchange information, signals and data. Components 1102 - 1108 of end node 1100 may be located inside housing 1112 .

The wireless communication interface module 1104 provides a mechanism by which the internal components of the end node 1100 can send and receive signals to and from external devices and network nodes (eg, access nodes). The wireless communication interface module 1104 includes, for example, a receiver module 1114 with a corresponding receive antenna 1116 and a transmitter module 1118 with a corresponding transmit antenna 1120 for coupling the end node 1100 to other network nodes, e.g., via a wireless communication channel .

End node 1100 also includes a user input device 1122 (eg, a keypad) and a user output device 1124 (eg, a display) coupled to bus 1110 via user input/output interface 1106 . Therefore, the user input/output devices 1122 and 1124 can exchange information, signals and data with other components of the end node 1100 through the user input/output interface 1106 and the bus 1110 . User input/output interface 1106 and associated devices 1122 and 1124 provide a mechanism by which a user may operate end node 1100 to accomplish various tasks. Specifically, user input device 1122 and user output device 1124 provide functionality that allows a user to control end node 1100 and applications (e.g., modules, programs, routines, and/or functions) executing in memory 1108 of end node 1100 .

The processor 1102 controls the operation of the end node 1100 under the control of various modules (eg, routines) included in the memory 1108 to perform various signaling and processing. Modules included in memory 1108 are executed at startup or when called by other modules. Modules may exchange data, information, and signals when executed. Modules may also share data and information while executing. The memory 1108 of the end node 1100 includes a control signaling module 1126, an application module 1128, and a service control module 1130, and the service control module 1130 further includes configuration information 1132 and various additional modules.

Control signaling module 1126 controls processing related to receiving and sending signals (e.g., messages) for controlling various functions of end node 1100 including, for example, traffic control module 1130 and configuration information 1132 and various additional modules. Aspects of operation and/or configuration. In some embodiments, the control signaling module 1126 may include state information (e.g., parameters, status, and/or other information) related to the operation of the end node 1100 and/or one or more signaling protocol. Specifically, the control signaling module 1126 may include configuration information (eg, end node identification information and/or parameter settings) and operational information (eg, information about current processing status, status of pending message transactions, etc.).

Application module 1128 controls processing and communications related to one or more applications supported by end node 1100 . In some embodiments, application module 1128 processing may include input/output of information through user input/output interface 1106, manipulation of information associated with an application, and/or receiving or sending signals associated with an application (for example, message) related tasks. In some embodiments, the application module 1128 includes state information (eg, parameters, status, and/or other information) related to the operation of one or more applications supported by the application module 1128 . Specifically, the application module 1128 may include configuration information (eg, user identification information and/or parameter settings) and operational information (eg, information about current processing status, status of pending responses, etc.). Applications supported by the applications module 1128 include, for example, voice over IP (VoIP), web browsing, streaming audio/video, instant messaging, file sharing, gaming, and the like.

Traffic control module 1130 controls processes related to receiving and sending data information (eg, messages, packets and/or frames) via wireless communication interface module 1104 . The example traffic control module 1130 includes configuration information 1132 and various additional modules that enable a home agent to select from a plurality of home agents. In some embodiments, various additional modules are included to perform specific functions and operations as needed to support specific aspects of business control. Modules may be omitted and/or combined depending on the functional requirements of the service control when necessary. Each additional module included in the traffic control module 1130 is described next.

Air interface module 1134 facilitates establishing a physical layer connection between end node 1100 and an access node (not shown), such as a base station. Air interface module 1134 may be initiated, for example, when end node 1100 receives power and/or enters a network (eg, enters a geographic area associated with the network). Configuration information 1132 may include configuration information (eg, parameter settings) that affects the operation of air interface module 1134 .

A network access module 1136 may facilitate receipt of requests for network access to, eg, an AAA server and responses related to network access. For example, network access module 1136 may be used in connection with providing an identifier (eg, NAI) associated with end node 1100 to an AAA server. The identification flag may be maintained in module data 1146 which may be read and/or written by the module through network access. The network access module 1136 is also operable to receive an address of a home agent to be associated with the end node 1100 (eg, a home agent associated with an MVNO providing services to the end node 1100).

The WTI module 1138 may be used to communicate data between the wireless terminal and the host. This information may be configuration information, such as the IP address assigned to the host (and other suitable configuration information). MMP module 1140 enables end node 1100 to receive and interpret messages (eg, from base stations) corresponding to the MMP protocol. The MMP module additionally allows the end node 1100 to form and transmit MMP messages (eg, configuration request messages) to the base station. The MIP module 1142 provides a way for the end node 1100 to receive, interpret, form and transmit configuration messages in Mobile IP (eg, Mobile IPv4 and/or Mobile IPv6). DHCP module 1144 provides end node 1100 with the ability to act as a DHCP server. For example, DHCP module 1144 may be configured to provide configuration information, etc., to a host device in response to a DHCP discover message. Module data 1146 may include data that may be extracted by one or more modules 1132-1144 or data that may be input by one or more modules 1132-1144. For example, module data 1146 may include network access data, may hold specific addresses (eg, base station addresses, home agent addresses, etc.), MMP or Mobile IP data, and the like.

FIG. 12 provides a detailed illustration of an example access node 1200 . Access node 1200 is a detailed representation of an apparatus that may function as any of access nodes 1014-1018 depicted in FIG. 10 . In the embodiment of FIG. 12 , the access node 1200 includes a processor 1202 , a memory 1204 , a network/internetwork interface module 1206 and a wireless communication interface module 1208 coupled together through a bus 1210 . Thus, via the bus 1210, various components of the access node 1200 may exchange information, signals and data. Components 1202 - 1210 of access node 1200 are located inside housing 1212 .

The network/internetwork interface module 1206 provides a mechanism by which the internal components of the access node 1200 can send signals to or receive signals from external devices and network nodes. Network/internetwork interface modules 1206 include receiver modules 1214 and transmitter modules 1216 that couple node 1200 to other network nodes, eg, via copper or fiber optic lines. The wireless communication interface module 1208 also provides a mechanism by which the internal components of the access node 1200 can send and receive signals to and from external devices and network nodes (eg, end nodes). The wireless communication interface module 1208 includes, for example, a receiver module 1218 with a corresponding receive antenna 1220 and a transmitter module 1222 with a corresponding transmit antenna 1224 . A wireless communication interface module 1208 is used to couple the access node 1200 to other nodes, eg, through a wireless communication channel.

Processor 1202 controls the operation of access node 1200 under the control of various modules (eg, routines) included in memory 1204 to perform various signaling and processing. Modules included in memory 1204 are executed at startup or when called by other modules. Modules may exchange data, information, and signals when executed. Modules may also share data and information while executing. In the embodiment of FIG. 12, the memory 1204 of the access node 1200 includes a control signaling module 1226 and a service control module 1228, and the service control module 1228 further includes configuration information 1230 and various additional modules 1232-1242.

Control signaling module 1226 controls processing related to receiving and sending signals (e.g., messages) for controlling various additional modules 1232-1242 including, for example, traffic control module 1228 and configuration information 1230 and included therein The operation and/or configuration of various aspects of the access node 1200. For example, the control signaling module 1226 includes state information (eg, parameters, status, and/or other information) related to the operation of the access node 1200 and/or one or more signaling protocols supported by the control signaling module 1226 . Specifically, the control signaling module 1226 may include configuration information (e.g., access node identification information and/or parameter settings) and operational information (e.g., information about current processing status, status of pending message transactions, etc.) .

The traffic control module 1228 controls processes related to receiving and sending data information (eg, messages, packets, and/or frames) through the wireless communication interface module 1208 . For example, the traffic control module may include configuration information 1230 and various additional modules 1232-1242 for use in connection with determining a home agent associated with an end node (eg, end node 1600). In some embodiments, the traffic control module 1228 includes state information related to the operation of the access node 1200, the traffic control module 1228, and/or one or more of the various additional modules 1232-1242 included therein ( For example, parameters, status and/or other information). Configuration information 1230 (eg, parameter settings) determines, affects, and/or specifies the operation of the traffic control module 1228 and/or the various additional modules 1232-1242 included therein. In some embodiments, various additional modules are included to perform specific functions and operations as needed to support specific aspects of business control. In various embodiments, modules may be omitted and/or combined as desired depending on the functional requirements of the home agent's choice. Each additional module included in the traffic control module 1228 is described next.

The air interface module 1232 facilitates establishing a physical layer connection between the end nodes and the access node 1200 . For example, air interface module 1232 may be initiated when access node 1200 receives an indication that a wireless terminal is within range of access node 1200 and desires to access a network. The network access module 1234 may be used in connection with authenticating and authorizing an end node (eg, authenticating an identity code of an end node and determining the type and quality of service that should be provided to the end node). For example, the access node 1200 can act as a conduit between the end nodes and the AAA server, and the network access module 1234 can facilitate the encapsulation and relay of messages related to network access.

DNS resolution module 1236 may be used in connection with receiving a hostname and resolving an IP address based at least in part on the hostname. In a particular example, the access node 1200 can receive the MVNO-home agent hostname from the AAA server. The DNS resolution module 1236 can provide a DNS resolution request to a DNS server and can receive an IP address from the server. Thereafter, DNS resolution module 1236 may store the IP address in, for example, module data 1244 .

The MMP module 1238 enables the access node 1200 to receive and interpret messages (eg, from wireless terminals) corresponding to the MMP protocol. The MMP module additionally allows the access node 1200 to form and transmit MMP messages (eg, configuration request messages) to end nodes. The MIP module 1240 provides a means for the access node 1200 to receive, interpret, form and transmit configuration messages in Mobile IP (eg, Mobile IPv4 and/or Mobile IPv6). DHCP module 1242 provides access node 1200 with the ability to act as a DHCP server. For example, DHCP module 1242 may be configured to provide configuration information, etc., to a host device in response to a DHCP discover message. Module data 1244 may include data that may be extracted by one or more modules 1232-1242 or data that may be input by one or more modules 1232-1242. For example, module data 1242 may include network access data, may hold specific addresses (eg, base station addresses, home agent addresses, etc.), MMP or Mobile IP data, and the like. In addition, module data 1242 may hold identification flags, profiles, MVNO-home agent identifiers, home agent addresses, DHCP data, and the like associated with end nodes.

FIG. 13 illustrates an example AAA server 1300 associated with various aspects. AAA server 1300 may be, for example, access control node 1020 depicted in FIG. 10 . As depicted, AAA server 1300 includes processor 1302 , communication interface 1304 , and memory 1308 coupled together by bus 1310 . Thus, through the bus 1310, various components of the AAA server 1300 can exchange information, signals and data. Components 1302 - 1310 of end node 1300 may be located inside housing 1312 .

Communication interface 1304 provides a mechanism by which the internal components of AAA server 1300 can send signals to and receive signals from external devices and network nodes (eg, access nodes). Communication interface 1304 includes, for example, a receiver module 1314 with a corresponding receive antenna 1316 and a transmitter module 1318 with a corresponding transmit antenna 1320 for coupling AAA server 1300 to other network nodes (e.g., over any suitable communication channel) .

Processor 1302 may be under the control of various modules (eg, routines) included in memory 1308 and may control AAA server 1300 to operate to perform the various signaling and processes described herein. Modules included in memory 1308 may execute at startup or when invoked by other modules. Modules may exchange data, information, and signals when executed. Modules may also share data and information while executing. Memory 1308 of AAA server 1300 may include signaling/control module 1326 and signaling/control data 1328 .

The signaling/control module 1326 controls processes related to receiving and sending signals (eg, messages) to manage state information storage, retrieval and processing. Signaling/control data 1328 includes status information related to the operation of the AAA server, eg, parameters, status and/or other information. In particular, signaling/control data 1328 may include configuration information 1330 (eg, AAA server identification information) and operational information 1332 (eg, information about current processing status, status of pending responses, etc.). Signaling/control module 1326 can access and/or modify signaling/control data 1328 (eg, update configuration information 1330 and/or operational information 1332).

Memory 1308 may also include a correlator module 1334 for correlating a home agent with a wireless terminal based on an identification (eg, NAI) associated with the wireless terminal. For example, the correlator module 1334 can access a database that indexes home agents with a particular MVNO, and the correlator module 1334 can determine the particular MVNO based on the identification. Thereafter, the correlator module 1334 may determine at least one home agent assigned to the particular MVNO. Memory 1308 may also include a network access module 1336, which may be used to perform authentication (and authorization and accounting) with respect to a particular wireless terminal.

What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the foregoing embodiments, but one of ordinary skill in the art can recognize that many other combinations and permutations of various embodiments are possible. Accordingly, the described embodiments are intended to embrace all alterations, modifications and variations that come within the spirit and scope of the appended claims. Furthermore, to the extent that the term "include" is used in the description or the claims, this term is intended to include in a manner similar to the term "comprising", such as "comprising" in the claims as explained when used as a transitional term in .

Claims (33)

CLAIMS 1. A method for registering a wireless terminal with a home agent, comprising: receiving an identification mark from the wireless terminal when the wireless terminal requests to access the network; providing said signature to an AAA server; receiving an identification code of at least one home agent from said AAA server; and Registration information from the wireless terminal is routed to the identified home agent. 2. A base station configured to perform the method of claim 1. 3. The method of claim 1, further comprising establishing a MIP tunnel with the identified home agent. 4. The method of claim 1, wherein the identified home agent is determined by identifying a network associated with the identification provided to the AAA server. 5. The method of claim 1, wherein the identified home agent is determined by identifying one of a MVNO and a VPN associated with the identification provided to the AAA server. 6. The method of claim 1, wherein the received identification code is a hostname, and the method further comprises resolving the hostname to one or more IP addresses. 7. The method of claim 6, wherein resolving the hostname is performed in conjunction with DNS. 8. The method of claim 6, wherein resolving the hostname is done locally. 9. The method of claim 1, further comprising: receiving a list of multiple home agents; and A home agent is selected from the list of home agents and registration information is routed to the selected home agent. 10. The method of claim 9, wherein the list is an ordered list. 11. The method of claim 1, further comprising registering the wireless terminal with the home agent by using MMP. 12. A base station comprising: memory that holds instructions for: receiving an identification mark from the wireless terminal when the wireless terminal requests to access the network; providing said signature to an AAA server; receiving an identification code of at least one home agent from said AAA server; and routing registration information from the wireless terminal to the identified home agent; and A processor executes the instructions. 13. The base station of claim 12, wherein the AAA server is an MVNO specific AAA server. 14. A communications device comprising: receiving means for receiving from an AAA server a profile associated with a subscriber, the profile including an identification code assigned to a home agent of an MVNO associated with the subscriber; and establishing means for establishing a Mobile IP tunnel with said identified home agent. 15. The communications device of claim 14, which is a base station. 16. The communication device of claim 14 configured to operate in an IP-based cellular system. 17. The communications apparatus of claim 14, further comprising routing means for routing the subscriber's registration request to the identified home agent. 18. A machine-readable medium having stored thereon machine-executable instructions for: receive an identification token associated with the subscriber; providing said signature to an AAA server; receiving a profile assigned to the subscriber, the profile including one or more home agents assigned to the MVNO associated with the subscriber; selecting a home agent from the one or more home agents; and Registration information from the subscriber is routed to the selected home agent. 19. A base station comprising the machine-readable medium of claim 18. 20. A processor that executes the following instructions: receiving from the AAA server a profile associated with the subscriber, the profile including an identification code assigned to a home agent of the MVNO associated with the subscriber; and A Mobile IP tunnel is established with the identified Home Agent. 21. The processor of claim 20, further configured to execute the following instructions: A registration request is routed to the identified home agent. 22. A method for determining one or more home agents to be associated with a wireless terminal, comprising: receiving an identification token associated with the wireless terminal; determining at least one home agent associated with the wireless terminal based at least in part on the signature; and The identification code of the at least one home agent is provided to a base station communicatively coupled to the wireless terminal. 23. An AAA server configured to perform the method of claim 22. 24. The method of claim 22, further comprising: determining an MVNO associated with the wireless terminal based at least in part on the signature; determining at least one home agent assigned to the MVNO; and The identity code of the at least one home agent is provided to the base station. 25. The method of claim 22, further comprising: establishing a profile associated with the wireless terminal; encapsulating the identification code of the home agent in the profile; and The profile is provided to the base station. 26. The method of claim 22, wherein the identification code provided to the base station is a hostname. 27. An AAA server comprising: memory, which includes instructions for: receiving an identification tag associated with the wireless terminal; determining at least one home agent associated with the wireless terminal based at least in part on the signature; and providing an identification code of the at least one home agent to a base station communicatively coupled to the wireless terminal; and A processor executes the instructions. 28. An AAA server comprising: receiving means for receiving an identification associated with a subscriber from a base station communicatively coupled to the subscriber; identifying means for identifying a network associated with said subscriber based at least in part on said identification; determining means for determining at least one home agent assigned to said network; and Assigning means for assigning said at least one home agent to said subscriber for registration of wireless terminals used by said subscriber. 29. The AAA server according to claim 28, wherein said identification mark is NAI. 30. The AAA server of claim 28, wherein the network is one of an MVNO and a VPN. 31. A machine-readable medium having stored thereon machine-executable instructions for: receiving an identification associated with a subscriber from a base station communicatively coupled to the subscriber; identifying an MVNO associated with the subscriber based at least in part on the signature; determining at least one home agent assigned to the MVNO; and The at least one home agent is assigned to the subscriber for registration of wireless terminals used by the subscriber. 32. A processor that executes the following instructions: receiving NAIs of subscribers requesting access to IP-based wireless networks; determining a network associated with the subscriber based at least in part on the received NAI; determining at least one home agent assigned to the network; associating the subscriber with the at least one home agent; and The association is relayed to the base station. 33. The processor of claim 32, wherein the network is one of an MVNO and a VPN.

Images