# Patent

## Title
Mobile IP accounting

## Abstract

In one embodiment, accounting information for a mobile node operating according to Mobile IP Protocol is updated. A network device that supports Mobile IP composes a request packet for the mobile node. The request packet identifies the mobile node and includes at least one counter associated with accounting information pertaining to the mobile node. The request packet is then sent to a server adapted for performing accounting. The server then logs the accounting information for the mobile node. The server may then send a reply packet to the network device acknowledging logging of the accounting information pertaining to the mobile node. A bill for Mobile IP services may then be generated from the accounting information.

## Background
RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 09/227,398, entitled “Mobile IP Accounting,” filed on Jan. 8, 1999, by Kent Leung, which is incorporated herein by reference for all purposes.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The disclosed embodiments relate to Mobile IP network technology. More particularly, the disclosed embodiments relate to Mobile IP accounting.
2. Description of the Related Art
Mobile IP is a protocol which allows laptop computers or other mobile computer units (referred to as “Mobile Nodes” herein) to roam between various sub-networks at various locations—while maintaining internet and/or WAN connectivity. Without Mobile IP or related protocol, a Mobile Node would be unable to stay connected while roaming through various sub-networks. This is because the IP address required for any node to communicate over the internet is location specific. Each IP address has a field that specifies the particular sub-network on which the node resides. If a user desires to take a computer which is normally attached to one node and roam with it so that it passes through different sub-networks, it cannot use its home base IP address. As a result, a business person traveling across the country cannot merely roam with his or her computer across geographically disparate network segments or wireless nodes while remaining connected over the internet. This is not an acceptable state-of-affairs in the age of portable computational devices.
To address this problem, the Mobile IP protocol has been developed and implemented. An implementation of Mobile IP is described in RFC 2002 of the Network Working Group, C. Perkins, Ed., Oct. 1996. Mobile IP is also described in the text “Mobile IP Unplugged” by J. Solomon, Prentice Hall. Both of these references are incorporated herein by reference in their entireties and for all purposes.
The Mobile IP process and environment are illustrated in FIG. 1. As shown there, a Mobile IP environment 2 includes the internet (or a WAN) 4 over which a Mobile Node 6 can communicate remotely via mediation by a Home Agent 8 and a Foreign Agent 10. Typically, the Home Agent and Foreign Agent are routers or other network connection devices performing appropriate Mobile IP functions as implemented by software, hardware, and/or firmware. A particular Mobile Node (e.g., a laptop computer) plugged into its home network segment connects with the internet through its designated Home Agent. When the Mobile Node roams, it communicates via the internet through an available Foreign Agent. Presumably, there are many Foreign Agents available at geographically disparate locations to allow wide spread internet connection via the Mobile IP protocol. Note that it is also possible for the Mobile Node to register directly with its Home Agent.
As shown in FIG. 1, Mobile Node 6 normally resides on (or is “based at”) a network segment 12 which allows its network entities to communicate over the internet 4 through Home Agent 8 (an appropriately configured router denoted R2). Note that Home Agent 8 need not directly connect to the internet. For example, as shown in FIG. 1, it may be connected through another router (a router R1 in this case). Router R1 may, in turn, connect one or more other routers (e.g., a router R3) with the internet.
Now, suppose that Mobile Node 6 is removed from its home base network segment 12 and roams to a remote network segment 14. Network segment 14 may include various other nodes such as a PC 16. The nodes on network segment 14 communicate with the internet through a router which doubles as Foreign Agent 10. Mobile Node 6 may identify Foreign Agent 10 through various solicitations and advertisements which form part of the Mobile IP protocol. When Mobile Node 6 engages with network segment 14, Foreign Agent 10 relays a registration request to Home Agent 8 (as indicated by the dotted line “Registration”). The Home and Foreign Agents may then negotiate the conditions of the Mobile Node's attachment to Foreign Agent 10. For example, the attachment may be limited to a period of time, such as two hours. When the negotiation is successfully completed, Home Agent 8 updates an internal “mobility binding table” which specifies the care-of address (e.g., a collocated care-of address or the Foreign Agent's IP address) in association with the identity of Mobile Node 6. Further, the Foreign Agent 10 updates an internal “visitor table” which specifies the Mobile Node address, Home Agent address, etc. In effect, the Mobile Node's home base IP address (associated with segment 12) has been shifted to the Foreign Agent's IP address (associated with segment 14).
Now, suppose that Mobile Node 6 wishes to send a message to a corresponding node 18 from its new location. An output message from the Mobile Node is then packetized and forwarded through Foreign Agent 10 over the internet 4 and to corresponding node 18 (as indicated by the dotted line “packet from MN”) according to a standard internet protocol. If corresponding node 18 wishes to send a message to Mobile Node—whether in reply to a message from the Mobile Node or for any other reason—it addresses that message to the IP address of Mobile Node 6 on sub-network 12. The packets of that message are then forwarded over the internet 4 and to router R1 and ultimately to Home Agent 8 as indicated by the dotted line (“packet to MN(1)”). From its mobility binding table, Home Agent 8 recognizes that Mobile Node 6 is no longer attached to network segment 12. It then encapsulates the packets from corresponding node 18 (which are addressed to Mobile Node 6 on network segment 12) according to a Mobile IP protocol and forwards these encapsulated packets to a “care of” address for Mobile Node 6 as shown by the dotted line (“packet to MN(2)”). The care of address may be, for example, the IP address of Foreign Agent 10. Foreign Agent 10 then strips the encapsulation and forwards the message to Mobile Node 6 on sub-network 14. The packet forwarding mechanism implemented by the Home and Foreign Agents is often referred to as “tunneling.”
The Mobile IP Management Information Base (MIB) [RFC 2006] may be used by network administrators in managing mobile nodes, foreign agents, and home agents on a particular network. By way of example, the Mobile IP MIB defines a set of variables that can be examined or configured by a manager station using version 2 of the Simple Network Management Protocol (SNMPv2) [RFC 1905]. More particularly, variables are provided which permit accounting, or recording, of the actions of a particular mobile node. By way of example, an overall service time for the mobile node and the total number of registration requests accepted or denied by a Home Agent may be updated. This accounting information is typically stored on the corresponding network device (e.g., Home Agent or Foreign Agent) and therefore each network device may be periodically examined by the manager station.
As shown in FIG. 2, storage and updating of accounting information is typically dispersed among the network devices (e.g., routers) in a typical Mobile IP network segment. Mobile IP environment 202 includes the internet (or a WAN) 204 over which various mobile nodes can communicate remotely via mediation by a corresponding Home Agent (via an appropriately configured router denoted R1). An entity such as a corporation, business, or government may provide multiple Home Agents. Here, a first Home Agent 206, a second Home Agent 208, a third Home Agent 210, a fourth Home Agent 212, and a fifth Home Agent 214 are shown. As shown, such an environment lacks a centralized database for accounting information. Therefore, each Home Agent must be separately configured for mobile nodes supported by that Home Agent and accounting information for these mobile nodes is stored with that Home Agent. Moreover, redundant Home Agents may be provided to permit a Home Agent to serve as a backup to protect against failure by a primary Home Agent. By way of example, the fourth Home Agent 212 and the fifth Home Agent 214 may store identical accounting information in the event that one of the Home Agents fails. Thus, when accounting information is updated, the information must be updated on all of the redundant Home Agents. Accordingly, such a system requires considerable administrative overhead.
Although information associated with the activity of mobile nodes may be recorded, the information typically maintained has limited uses in a billing environment. More particularly, a mechanism for tracking the amount of information sent and/or received by selected mobile nodes has not been established. By way of example, the number of packets or bytes sent and/or received by mobile nodes operating under Mobile IP Protocol has not been monitored. Moreover, although variables may be used to update the number of registrations accepted or denied by a Home Agent as well as update the overall service time for a mobile node, these variables have not been implemented for the purposes of billing users associated with these mobile nodes. In addition, although these variables may be polled by the manager station periodically as requested, this process is not dynamic.
While billing may be performed for nodes which are not mobile, such methods may not easily be applied to mobile nodes operating under the Mobile IP Protocol. By way of example, billing is often performed through the use of time stamps. For a node which is not mobile, this method is acceptable since only two time stamps, a START time stamp and a STOP time stamp for a given session, are required to determine a total service time. However, in a Mobile IP environment, each mobile node may roam to numerous Foreign Agents while communicating with a given corresponding node. The Home Agent, which would presumably log START and STOP time stamps, sees only some of the packets associated with a session between the mobile node and the corresponding node. Thus, it may not know exactly when a session starts ands stops. Accordingly, this method of accounting and billing cannot easily be applied to mobile nodes operating under a Mobile IP Protocol.
In view of the above, a need exists for monitoring the quantity of information sent and received by mobile nodes for billing purposes. Moreover, it would beneficial if a system having centralized database management were provided to dynamically store and process this billing information for mobile nodes supported by multiple network devices.
OVERVIEW
In accordance with one embodiment, an apparatus includes a memory and a processor coupled to the memory. At least one of the processor or the memory are adapted for updating a counter associated with a mobile node's activity and sending an accounting request identifying the mobile node and including the counter to a AAA server supporting a AAA protocol, where the AAA server is adapted for recording accounting information associated with the mobile node using the counter, and where the accounting request indicates a request to update accounting information associated with the mobile node using the counter. The apparatus supports Mobile IP and the AAA protocol, and the accounting request is sent in accordance with the AAA protocol.
In accordance with another embodiment, an apparatus includes a memory and a processor coupled to the memory. At least one of the processor or the memory are adapted for storing accounting information for a plurality of mobile nodes and logging accounting information associated with a mobile node in response to an accounting request received from a network device supporting Mobile IP. The accounting request indicates a request to update the accounting information associated with the mobile node using the at least one counter, where the accounting request identifies the mobile node and includes at least one counter associated with the accounting information. The apparatus is a AAA server supporting a AAA protocol. The network device further supports the AAA protocol and the accounting request is sent in accordance with the AAA protocol.
In accordance with yet another embodiment, a request packet for a mobile node is composed by a network device supporting Mobile IP, the request packet identifying the mobile node and including at least one counter associated with accounting information pertaining to the mobile node, wherein the request packet indicates a request to update accounting information associated with the mobile node using the at least one counter. The network device sends the request packet to a AAA server adapted for performing accounting, thereby enabling the AAA server to update accounting information for the mobile node, the AAA server supporting a AAA protocol, wherein the request packet is composed in accordance with the AAA protocol.
In accordance with yet another embodiment, a AAA server receives a request packet from a network device operating under Mobile IP Protocol, the request packet identifying a mobile node and including at least one counter associated with accounting information pertaining to the mobile node, the AAA server supporting a AAA protocol, wherein the request packet indicates a request to update accounting information associated with the mobile node using the at least one counter. The AAA server logs the accounting information for the mobile node identified in the request packet using the counter of the request packet.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram illustrating a Mobile IP network segment and associated environment.
FIG. 2 is a block diagram illustrating a mobile IP network segment and associated environment without a centralized source of accounting information.
FIG. 3 is a block diagram illustrating a mobile IP network segment and associated environment having a centralized database as a source for accounting information according to one embodiment of the invention.
FIG. 4 is a process flow diagram illustrating the steps performed during the update of accounting information pertaining to a mobile node according to one embodiment of the invention.
FIG. 5 is a block diagram of a network device that may be configured to implement aspects of the present invention.



DESCRIPTION OF EXAMPLE EMBODIMENTS
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the disclosed embodiments. It will be obvious, however, to one skilled in the art, that the disclosed embodiments may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order not to unnecessarily obscure the disclosed embodiments.
The disclosed embodiments provide methods and apparatus for logging accounting information for a mobile node. This is accomplished through the use of a centralized server which provides accounting services. The server may store and update accounting information for multiple network devices. In addition, the centralized server may have access to billing software which generates bills from the accounting information. In this manner, accounting information may be dynamically updated and processed for billing purposes.
According to one embodiment of the invention, a method of updating accounting information for a mobile node operating according to Mobile IP Protocol is provided. A network device that supports Mobile IP composes a request packet for the mobile node. The request packet identifies the mobile node and includes at least one “counter” associated with accounting information pertaining to the mobile node. The request packet is then sent to a server adapted for performing accounting.
Various counters may be provided in the request packet. By way of example, a counter may indicate the number of packets or bytes that have been sent to or from the mobile node. As yet another example, a counter may be used to indicate the total service time for the mobile node. Thus, the quantity of information that is sent and received by mobile nodes may be monitored for billing purposes.
According to yet another embodiment of the invention, the server receives the request packet from the network device and logs the accounting information for the mobile node. A reply packet may then be sent to the network device acknowledging logging of the accounting information pertaining to the mobile node. In addition, a bill for Mobile IP services may be generated from the accounting information.
As described above with reference to FIG. 2, due to the lack of a centralized database, the amount of accounting information that may be stored by each network device is limited. Moreover, since each Home Agent must be separately configured, such a system requires a considerable amount of administrative support and increases the probability that errors may be introduced by a user configuring the system. Accordingly, it would be desirable if a single system having a centralized repository were implemented to store some or all of the accounting information for the mobile nodes supported by one or more Home Agents or Foreign Agents.
An invention is described herein that provides such a centralized repository (e.g., a database). FIG. 3 is a block diagram illustrating a mobile IP network segment and associated environment having a centralized database as a source for accounting information according to one embodiment of the invention. Unlike the system of FIG. 2, an environment in which a centralized database, or server 302, is provided. As shown, the server may be coupled to multiple routers or other network devices operating under the Mobile IP Protocol (e.g., Home Agents or Foreign Agents) via a network. In addition, this centralized server 302 may be adapted for performing certain Mobile IP functions as implemented by software, hardware, and/or firmware. In one example, server 302 is configured to authenticate or assist in authenticating a Mobile IP registration request from a mobile node. In addition to updating accounting information, the server may have access to billing software 303, which resides on the server or is easily accessible to the server. The billing software may then be used to generate a bill 304 using the accounting information stored on the server 302. In this manner, accounting may be used to account for services used by a particular mobile node in a billing environment.
In addition to providing a centralized server that is capable of storing and updating accounting information for multiple mobile nodes as well as multiple network devices, the centralized server may provide further services. By way of example, the centralized server may provide authentication services and/or authorization services. While authentication determines “who” an entity is, authorization determines what services a user is allowed to perform, or access. A class of servers known as “AAA” or triple-A servers may be employed. The AAA represents authentication, authorization, and accounting. Various protocols such as the Remote Authentication Dial In User Service (RADIUS) and TACACS+ may be implemented to provide such a server. Note that the Home Agent or Foreign Agent providing accounting information to the server must provide communications in formats required by the AAA server protocol.
FIG. 4 is a process flow diagram illustrating the steps performed during a method of updating accounting information pertaining to a mobile node and billing in Mobile IP according to one embodiment of the invention. As shown in FIG. 4, vertical line 402 represents steps performed by the mobile node, vertical line 404 represents steps performed by the network device (e.g., Home Agent or Foreign Agent) and vertical line 406 represents steps performed by the server. At step 408, the mobile node sends a packet to the network device. By way of example, the packet may be a data packet sent during a Mobile IP session or a registration request packet. At step 410, the network device monitors the activity of the mobile node. By way of example, the network device may update one or more variables (e.g., counters) indicating the number of packets that have been sent to/from the mobile node, the total service time (e.g., cumulative registration lifetimes), the number of bytes that have been sent to/from the mobile node, or the total service time for the mobile node. As yet another example, where the network device is a Home Agent, a counter may be updated to indicate the number of registrations accepted or denied by the Home Agent. Depending upon the type of information being monitored, the counters may be updated at various intervals. By way of example, if the monitored information is service time, the counters may be updated periodically after a predetermined time period. As yet another example, the counters may be updated after each registration or after one or more packets are received or sent by the mobile node.
Once the counters have been updated, the counters may be used to update the accounting information stored on the server. At step 412, a request packet for the mobile node is composed and sent to a server adapted for logging accounting information. By way of example, the request packet may identify the mobile node and include at least one counter associated with accounting information pertaining to the mobile node. By way of example, in accordance with the TACACS+ Protocol, the request packet may be an accounting REQUEST packet. Step 412 may be triggered by various trigger events. Thus, not every update of a counter in the network device necessarily results in sending a request packet to the server. For example, only certain accounting relevant events may trigger sending the information to the server. Examples of such trigger events include initiating a new registration, terminating a registration, passing a threshold number packets or bytes, etc.
The server receives the request packet from the network device and logs the accounting information provided in the accounting request at step 414. As described above, the accounting request identifies the mobile node and may include at least one variable (e.g., counter) associated with the accounting information. The server may then store and/or manipulate the counter to generate appropriate accounting information. It may even generate a bill for Mobile IP services from the accounting information. The bill may then be sent to the user through a variety of mechanisms. In addition, the server may send a reply packet to the network device acknowledging logging of the accounting information pertaining to the mobile node at step 416. By way of example, in accordance with the TACACS+ Protocol, the request packet may be an accounting REPLY packet. Such a reply packet may indicate a status of PASS or FAIL in relation to the logging of the accounting information.
As described above, the server may log accounting information for multiple network devices. The network devices may be Foreign Agents as well as Home Agents. However, it is important to recognize that traffic may be unidirectional and therefore may be not be received by both the Home Agent and the Foreign Agent. By way of example, registration of mobile nodes may be performed at the Home Agent without direct participation by a Foreign Agent. As yet another example, a packet sent from a mobile node visiting a Foreign Agent may be sent directly to a corresponding node without communicating with its Home Agent. In order to ensure that all relevant Mobile IP usage is captured, accounting information may be sent between a Foreign Agent and the visiting mobile node's Home Agent. By way of example, when a mobile node sends a packet (e.g., a data packet) to a corresponding node, the packet may be reverse tunneled from the Foreign Agent to the Home Agent. In this manner, reverse tunneling may be used to ensure that accounting information stored on a server associated with one or more Home Agents is accurate. Alternatively, the Foreign Agent may generate its own counters (e.g., number of bytes sent from the mobile node to the corresponding node) and transmit those counters to the Home Agent. In another alternative embodiment, it may be preferable to provide a server on a network for use by one or more Foreign Agents rather than a Home Agent.
The disclosed embodiments provide methods and apparatus for logging accounting information for mobile nodes and generating bills for Mobile IP services associated with this accounting information. Although the servers of this invention are described with reference to TACACS+ and RADIUS, any suitable protocol may be implemented. In this manner, a mobile node may be billed for information that is sent as well as received by the mobile node. Such servers may run on a PC or workstation such as a UNIX workstation.
The disclosed embodiments can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, magnetic tape, and optical data storage devices.
The apparatus (Home Agent, Foreign Agent, and/or mobile node) of this invention may be specially constructed for the required purposes, or may be a general purpose programmable machine selectively activated or reconfigured by a computer program stored in memory. The processes presented herein are not inherently related to any particular router or other apparatus. In a preferred embodiment, any of the Home and Foreign Agents and mobile nodes of this invention may be specially configured routers such as specially configured router models 2500, 2600, 3600, 4000, 4500, 4700, 7200, and 7500 available from Cisco Systems, Inc. of San Jose, Calif. A mobile node that is a router is known as a “mobile router.” A general structure for some of these machines will appear from the description given below.
Referring now to FIG. 5, a router/agent 502 of the present invention includes a master central processing unit (CPU) 504, low and medium speed interfaces 506, and high speed interfaces 508. When acting under the control of appropriate software or firmware, the CPU 504 is responsible for such router tasks as routing table computations and network management. It is also responsible for registration, packet tunneling and other Mobile IP functions of a Home Agent or a Foreign Agent. It may include one or more microprocessor chips 510 selected from complex instruction set computer (CISC) chips (such as the Motorola MPC860 microprocessor or the Motorola 68030 microprocessor, reduced instruction set computer (RISC) chips, or other available chips. In a preferred embodiment, a memory 512 (such as non-volatile RAM and/or ROM) also forms part of CPU 504. However, there are many different ways in which memory could be coupled to the system.
The interfaces 508 and 506 are typically provided as interface cards. Generally, they control the sending and receipt of data packets over the network and sometimes support other peripherals used with the router 502. The low and medium speed interfaces 506 include a multiport communications interface 514, a serial communications interface 516, and a token ring interface 518. The high speed interfaces 508 include an FDDI interface 520 and a multiport ethernet interface 522. Preferably, each of these interfaces (low/medium and high speed) includes (1) a plurality of ports appropriate for communication with the appropriate media, and (2) an independent processor such as the 2901 bit slice processor (available from Advanced Micro Devices corporation of Santa Clara Calif.), and in some instances (3) volatile RAM. The independent processors control such communications intensive tasks as packet switching and filtering, and media control and management. By providing separate processors for the communications intensive tasks, this architecture permits the master microprocessor 504 to efficiently perform routing computations, network diagnostics, security functions, etc.
The low and medium speed interfaces are coupled to the master CPU 504 through a data, control, and address bus 524. High speed interfaces 508 are connected to the bus 524 through a fast data, control, and address bus 526 which is in turn connected to a bus controller 528. The bus controller functions are provided by a processor such as a 2901 bit slice processor.
Although the system shown in FIG. 5 is a preferred router of the present invention, it is by no means the only router architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc. would also be acceptable. Further, other types of interfaces and media could also be used with the router. Still further, in some cases, the invention can be implemented on network devices other than routers.
Although illustrative embodiments and applications of this invention are shown and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those of ordinary skill in the art after perusal of this application. For instance, although the specification has described routers, other entities used to tunnel packets to mobile nodes on remote network segments can be used as well. For example, bridges or other less intelligent packet switches may also employ the standby protocol of this invention. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

## Claims

1. An apparatus, comprising:
a memory; and
a processor coupled to the memory, at least one of the processor or the memory being configured for:
updating a counter associated with a mobile node's activity; and
sending an accounting request identifying the mobile node and including the counter to a AAA server supporting a AAA protocol, the AAA server being adapted for recording accounting information associated with the mobile node using the counter, wherein the accounting request indicates a request to update accounting information associated with the mobile node using the counter, wherein the counter is associated with the mobile node's activity during a Mobile IP session, thereby enabling accounting information associated with the mobile node to be updated as the mobile node roams to one or more locations during the Mobile IP session;
wherein the apparatus supports Mobile IP and the AAA protocol, and wherein the accounting request is sent in accordance with the AAA protocol.

2. The apparatus as recited in claim 1, wherein the AAA server does not support Mobile IP.

3. The apparatus as recited in claim 1, at least one of the processor or the memory being configured for sending an accounting request in response to a trigger event, the trigger event being a lapse of a predetermined period of time, initiation or termination of a registration of the mobile node, or when a number of packets are received or sent by the mobile node.

4. The apparatus as recited in claim 1, wherein the counter indicates at least one of a number of packets received by the mobile node, a number of packets sent from the mobile node, a total service time for the mobile node, a number of bytes that have been sent to the mobile node, a number of bytes that have been sent from the mobile node, or a number of registrations that have been accepted.

5. The apparatus as recited in claim 1, wherein the apparatus is a Home Agent supporting the mobile node or a Foreign Agent to which the mobile node has roamed.

6. The apparatus as recited in claim 5, wherein the apparatus is a Foreign Agent.

7. The apparatus as recited in claim 5, wherein the apparatus is a Home Agent, wherein the Home Agent receives accounting information from a Foreign Agent to which the mobile node has roamed, thereby enabling the Home Agent to provide the counter in the accounting request.

8. The apparatus as recited in claim 5, wherein the apparatus is a Home Agent, and wherein reverse tunneling is performed such that the Home Agent can receive and track data packets that are transmitted at least one of to the mobile node or from the mobile node.

9. The apparatus as recited in claim 1, wherein the AAA server maintains accounting information for a plurality of mobile nodes supported by a plurality of Home Agents.

10. The apparatus as recited in claim 9, the accounting information being received from a plurality of network devices, each of the plurality of network devices being a Home Agent or a Foreign Agent adapted for sending an accounting request to the server to update accounting information associated with a mobile node.

11. The apparatus as recited in claim 10, wherein each of the plurality of network devices supports Mobile IP and the AAA protocol, wherein each of the plurality of network devices is configured for sending the accounting request to the server in the AAA protocol.

12. The apparatus as recited in claim 10, wherein each of the plurality of network devices is configured for sending an accounting request in response to a trigger event, the trigger event being a lapse of a predetermined period of time, initiation or termination of a registration of the mobile node, or when a number of packets are received or sent by the mobile node.

13. The apparatus as recited in claim 1, wherein the server maintains accounting information for a plurality of mobile nodes, the plurality of mobile nodes being supported by a plurality of network devices, each of the plurality of network devices being a Home Agent or a Foreign Agent.

14. An apparatus, comprising:
a memory; and
a processor coupled to the memory, at least one of the processor or the memory being configured for:
storing accounting information for a plurality of mobile nodes and logging accounting information associated with a mobile node in response to an accounting request received from a network device supporting Mobile IP, the accounting request identifying the mobile node and including at least one counter associated with the accounting information, wherein the accounting request indicates a request to update the accounting information associated with the mobile node using the at least one counter, wherein the counter is associated with the mobile node's activity during a Mobile IP session, thereby enabling accounting information associated with the mobile node to be updated as the mobile node roams to one or more locations during the Mobile IP session;
wherein the apparatus is a AAA server supporting a AAA protocol;
wherein the network device further supports the AAA protocol and the accounting request is sent in accordance with the AAA protocol.

15. The apparatus as recited in claim 14, wherein the AAA server does not support Mobile IP.

16. The apparatus as recited in claim 14, wherein the apparatus is in communication with a plurality of network devices supporting Mobile IP.

17. The apparatus as recited in claim 16, wherein each of the plurality of network devices supporting Mobile IP is a Home Agent or a Foreign Agent.

18. The apparatus as recited in claim 14, wherein the network device is a Home Agent or a Foreign Agent.

19. The apparatus as recited in claim 14, the plurality of mobile nodes being supported by a plurality of network devices, each of the plurality of network devices being a Home Agent or a Foreign Agent.

20. The apparatus as recited in claim 14, the plurality of mobile nodes being supported by a plurality of Home Agents.

21. The apparatus as recited in claim 14, the at least one counter indicating at least one of a number of packets that have been sent to the mobile node, a number of packets that have been sent from the mobile node, a total service time for the mobile node, a number of bytes that have been sent to the mobile node, a number of bytes that have been sent from the mobile node, or a number of registrations that have been accepted.

22. The apparatus as recited in claim 14, wherein the AAA server is configured for sending an accounting reply to the network device in response to the accounting request, the accounting reply acknowledging logging of the accounting information pertaining to the mobile node.

23. The apparatus as recited in claim 14, wherein the server is a TACACS+ or a RADIUS server.

24. The apparatus as recited in claim 14, wherein the AAA server maintains accounting information for a plurality of mobile nodes supported by a plurality of Home Agents, wherein the accounting information for each of the plurality of mobile nodes is received from at least one of a Home Agent or a Foreign Agent.

25. A method, comprising:
composing a request packet by a network device supporting Mobile IP, the request packet identifying a mobile node and including at least one counter associated with accounting information pertaining to the mobile node, wherein the request packet indicates a request to update accounting information associated with the mobile node using the at least one counter, wherein the counter is associated with the mobile node's activity during a Mobile IP session; and
sending the request packet to a AAA server adapted for performing accounting, thereby enabling the AAA server to update accounting information for the mobile node, the AAA server supporting a AAA protocol, wherein the request packet is composed in accordance with the AAA protocol.

26. The method as recited in claim 25, wherein the AAA server does not support Mobile IP.

27. The method as recited in claim 25, wherein the network device is a Home Agent supporting the mobile node or a Foreign Agent to which the mobile node has roamed.

28. The method as recited in claim 25, wherein composing is performed in response to a trigger event, the trigger event being a lapse of a predetermined period of time, initiation or termination of a registration of the mobile node, or when a number of packets are received or sent by the mobile node.

29. The method as recited in claim 25, the at least one counter indicating at least one of a number of packets that have been sent to the mobile node, a number of packets that have been sent from the mobile node, a total service time for the mobile node, a number of bytes that have been sent to the mobile node, a number of bytes that have been sent from the mobile node, or a number of registrations that have been accepted.

30. The method as recited in claim 25, further comprising:
receiving a reply packet for the mobile node identified in the request packet, the reply packet acknowledging logging of the accounting information pertaining to the mobile node.

31. The method as recited in claim 25, wherein the server is a TACACS+ or a RADIUS server.

32. The method as recited in claim 25, further including:
receiving a data packet from the mobile node or receiving a data packet that has been sent by the mobile node, wherein composing the request packet is performed in response to receiving the data packet.

33. The method as recited in claim 32, further including:
forwarding the data packet to another network device.

34. The method of claim 25, wherein composing a request packet for the mobile node is triggered by an accounting event.

35. The method of claim 34, wherein composing a request packet is performed in response to receiving accounting information for the mobile node from another network device supporting Mobile IP.

36. A method, comprising:
receiving at a AAA server a request packet from a network device operating under Mobile IP Protocol, the request packet identifying a mobile node and including at least one counter associated with accounting information pertaining to the mobile node, the AAA server supporting a AAA protocol, wherein the request packet indicates a request to log accounting information associated with the mobile node using the at least one counter, wherein the counter is associated with the mobile node's activity during a Mobile IP session; and
logging the accounting information for the mobile node identified in the request packet using the counter of the request packet.

37. The method as recited in claim 36, wherein the network device further supports the AAA protocol and the request packet is sent in accordance with the AAA protocol.

38. The method as recited in claim 36, wherein the AAA server does not support Mobile IP.

39. The method as recited in claim 36, the at least one counter indicating at least one of a number of packets that have been sent to the mobile node, a number of packets that have been sent from the mobile node, a total service time for the mobile node, a number of bytes that have been sent to the mobile node, a number of bytes that have been sent from the mobile node, or a number of registrations that have been accepted.

40. The method as recited in claim 36, wherein the network device is a Home Agent supporting the mobile node or a Foreign Agent to which the mobile node has roamed.

41. The method as recited in claim 36, further including:
sending a reply packet for the mobile node identified in the request packet, the reply packet acknowledging logging of the accounting information pertaining to the mobile node.

42. The method as recited in claim 36, further including:
generating a bill for Mobile IP services from the accounting information.

43. The method as recited in claim 36, wherein the AAA server is a TACACS+ or a RADIUS server.

44. The apparatus as recited in claim 14, at least one of the processor or the memory being further configured for:
updating the accounting information associated with the mobile node as the mobile node roams to one or more locations during the Mobile IP session.

45. The method as recited in claim 36, further comprising:
receiving at the AAA server a second request packet from a second network device operating under Mobile IP Protocol, the second request packet identifying the mobile node and including at least one counter associated with accounting information pertaining to the mobile node, wherein the second request packet indicates a request to log accounting information associated with the mobile node using the at least one counter provided in the second request packet, wherein the counter in the second request packet is associated with the mobile node's activity during the Mobile IP session; and
logging the accounting information for the mobile node identified in the second request packet using the counter of the second request packet.

46. The method as recited in claim 45, wherein the network device and the second network device are geographically separated.