MX2008004841A - Wireless terminal methods and apparatus for establishing connections - Google Patents

Abstract

Methods and apparatus for establishing communication links, used to support communications sessions with one or more end nodes, e.g., mobile devices, are described. Various features are directed to a mobile node controlling the establishment of initial links to a first access node and the establishment of new links from a first access node to a second access node during a handoff operation using highly efficient messages and signal.

Description

METHODS AND APPLIANCES OF WIRELESS TERMINAL TO ESTABLISH CONNECTIONS FIELD OF THE INVENTION The present invention relates to communication systems and, more particularly, to methods and apparatus for establishing connections in wireless communications networks, for example, cellular.

BACKGROUND OF THE INVENTION Communication systems often include a plurality of network nodes which are coupled to access nodes through which the end nodes, for example, mobile devices, are coupled to the network. Network nodes can be accommodated in a hierarchy. The Access, Authentication and Authorization (AAA) servers are nodes which are usually placed in a relatively high position in the network hierarchy. These typically provide information used for access control and security purposes. Access nodes often have a secure link to an AAA server in cases where such servers are used. The secure link can be through one or more nodes in the hierarchy. Operators usually administer access sessions on IP networks using the RADIUS protocol and the associated AAA RADIUS servers. In the future, AAA systems can be based on new protocols, such as DIAMETER. In a system that uses an AAA RADIUS server, when a user tries to access an operator network, for the duration of an access session, the local access router usually issues one or more RADIUS Access Requests to an Authentication Server to authenticate that user based on their identity such as a Network Access Identifier (NAI). The AAA database usually holds the identities of those users who are allowed access to their system along with the characteristics of the services they can use. When the user is successfully authenticated, their access port on the access device is configured with commensurate status of the policy with the user's service authorization. The service authorization is normally delivered through RADIUS to the Access Router by the Authorization Server. While authorized, the use of the service during an access session is recorded by the Access Router, and sent as Accounting Records to an Accounting Server using accounting request messages in the RADIUS protocol. The Accounting Server can be part of the AAA server or it can be a stand-alone server using the same protocol with the authorization server. If the user is connected to multiple Access Routers during a single session, then multiple sessions need to be added to the Accounting Servers. AAA systems are usually used with Mobile IP to manage the IP address assignments (HoA), to dynamically assign HA, to distribute MN profiles to the Access Router and also to distribute security keys in order to authenticate MIP messages and to secure the air link. The Mobile Node, an end node which has the ability to change its network junction point, usually sends a MIP message to access the system, which triggers an AAA request to authenticate and authorize the Mobile Node. The MN AAA profile and the security state are then passed from the AAA system to the Access Router to control the services consumed by the MN. MNs can change their network junction point, for example, as they move from one cell to another cell. This involves changing the point of attachment of the MNs from a first access node, for example, a first router, to a second access node, for example, a second router. This process is usually referred to as a transfer. As part of a transfer, the MN CoA / CCoA needs to be updated and then transferred to the HA using MIP signaling so that the packets are redirected to the MN through the new Access Router. As part of the transfer process, it is necessary to transfer at least some status information of the first access router corresponding to the MN involved in the transfer to the new access router so that the MN service is not interrupted. This process is known as State Transfer. The State Transfer may include, for example, the transfer of AAA profile status information that was previously delivered through RADIUS to the AR, at which the MN access session began. It may also include, for example, the transfer of air link security vectors, MN-NAI, MN IP address, MN-EUI-64, remaining MIP registration duration, MN multicast group membership, control status of admission, resource reservation status, dif-serv status, SIP session state, compressor status, MN schedule history and / or many other potential items of the MN-specific AR status information. At least in a known system, the transfer of status information during a transfer is achieved through the new access node to which a mobile node that sends a status transfer message through the communications network is connecting. to the previous access node to which the mobile node was connected. In response, the previous access node forwards the status information to the new access node. Alternatively, a core node is used to store the state associated with a particular mobile node. When said mobile node attempts to move to another target access node, said target access node may recover the state associated with said mobile node from said core node. Mobile IP, (versions 4 and 6) also known as MIPv4 [MIPv4] and MlPvß [MlPvß], allows a mobile node (MN) to register its temporary location indicated by a care direction (CoA) to its Local Agent (HA) ). The HA then maintains a mapping (also called a union) between the permanent address of the MN, otherwise called Local Address (HoA), and the registered CoA so that the packets for that MN can be redirected to their current location using techniques IP encapsulation (tunneling). The CoA used by an MN can be an address that belongs to an Agent Outside (FA) on an Access Router when used MIPv4 or it can be an address temporarily assigned to the MN itself, from the prefix of the Access Router, in which case it is called a care address placed (CCoA). This last model also applies to MIPv4 while it is the only mode of operation in MlPvß. It can be seen that for the purpose of this document, the terms CCoA and CoA as well as Registration and Union Update (BU) may be interchangeable because they are corresponding terms for MIPv4 and MlPvß. The Registration Request message that complies with the smallest possible MIPv4 includes at least the following headings and fields. IP Header (at least 160 bits long) UDP Header (at least 64 bits long) The UDP header is followed by the Mobile IP fields shown below: (at least 192 bits long) 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - < - + - + - + - + - + - + - + - + - + - + - + - + - + | TiP ° | s | B | D | M |? | R | t | x | Duration , i Local Address i + _ .- + _ + _ + _ +. + -. + _ + _ + _ + _ + _ + - + - + _ +. + _ + _ + _ + _ + _ + -. + _ + - + - + - + - + - + - + - + - + - + I Local Agent | | Care address | I I Identification! I I Type 1 (Registration Application) S Simultaneous unions. If the 'S' bit is set, the mobile node is asked to retain its previous mobility unions by the local agent. B Diffusion datagrams. If bit 'B' is set, the mobile node is requested that the local agent tunnel to it any broadcast datagrams it receives in the local network. D De-encapsulation by mobile node. If the bit 'D1 is set, the mobile node will de-encapsulate the datagrams which are sent to the care address. That is, the mobile node is using a placed care address.

M Minimum encapsulation. If the 'M' bit is set, the mobile node is requested to use its local agent using minimal encapsulation [34] for datagrams tunneled to the mobile node. G GRE encapsulation. If the 'G1 bit is set, the mobile node is requested to use its GRE localization [16] for datagrams tunneled to the mobile node by its local agent. r Sent as zero; ignored at reception. T Reverse tunneling requested; x Sent as zero; ignored at reception. Duration The number of seconds remaining before the record is considered expired. A value of zero indicates a request to delete the record. An Oxffff value indicates infinity. Local Address The IP address of the mobile node. Local Agent The IP address of the local agent of the mobile node. Care Address The IP address for the end of the tunnel. Identification A 64-bit number built by the mobile node, used to compare Registry Requests with Registry Responses, and for protection against replay attacks of Registry Messages. Extensions (at least 176 bits long) The fixed portion of the Registration Request is followed by one or more of the Extensions. An extension that enables authorization MUST be included in all Registration Requests. 0 1 2 '3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | Type | Length | SPI ....

.... SPI (cont.) | Authenticator .... + - + - 4.-H.-4.- - + - + - + - + - + - + - + - 4 .- + - + - + - + -4 .- + - + -4.- + - I (- + - + - + - + - + - + - + - + Type 32 Length 4 plus the number of bytes in the Authenticator. SPI Security Parameter Index (4 bytes). An opaque identifier. Authenticator The default authentication algorithm uses HMAC-MD5 to calculate a 128-bit "message digest" of the registration message.

Authenticator Extension 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1 Type I Length I SPI ....

.... SPI (cont.) I Authenticator ....

Type 32 Length 4 plus the number of bytes in the Authenticator. SPI Security Parameter Index (4 bytes). An opaque identifier. Authenticator The default authentication algorithm uses HMAC-MD5 to calculate a 128-bit "message digest" of the registration message. The smallest possible MIPv4 Registration Request message shown above is 592 bits long, which can result in inefficient use of resources when it has to be transmitted over a wireless link for the purpose of registration and transfer. It can be seen that in practice, typical MIPv4-compliant Registration Request messages are significantly larger than the calculated minimum value but that minimum value is used for illustration purposes. The smallest possible MIPv4-compliant record response message includes at least the following headers and fields. IP Header (at least 160 bits long) UDP Header (at least 64 bits long) The UDP header is followed by the fields of Mobile IP shown below: (at least 160 bits long) 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + - + -4-- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + 'Type' Code 'Duration' + - + -4 - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + | Local address I I Local Agent I + - + -4-- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + I I + Identification + II 4- + -4-- + - + - + - + - + - + - + - + - + - + - + - + -4 - + - + - + -4 - + - 4- + - + - + - + - + - + - + - + - + - + - + 'Extensions .... -4 + _4 .. + - ._4- - + _ + - Type 3 (Registration Response) Code A value that indicates the result of the Registration Request.

Duration If the Code field indicates that the record was accepted, the duration field is set to the number of seconds remaining before the record is considered expired. A value of zero indicates that the mobile node has been deregistered. An Oxffff value indicates infinity. Local Address The IP address of the mobile node. Local Agent The IP address of the local agent of the mobile node. Identification A 64-bit number used for comparing Registry Requests with Registry Responses, and for protection against attacks from reproducing registration messages. Extensions (at least 176 bits long) The fixed portion of the Registration Response is followed by one or more of the Extensions. An extension that enables authorization MUST be included in all Registry Responses. Authenticator Extension 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + • - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + 'Type I Longitu' SPI + - + - + - + - + - + - + - 4 - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - 4 - + - + - 4 - + - + - + - + - + .... SPI (cont.) I Authenticator .... 4 - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + Type 32 Length 4 plus the number of bytes in the Authenticator. SPI Security Parameter index (4 bytes). An opaque identifier. Authenticator The default authentication algorithm uses HMAC-MD5 to calculate a 128-bit "message digest" of the registration message. The smallest possible MIPv4-compliant Record Reply message shown above is 560 bits long which can result in inefficient use of resources when it has to be transmitted over a wireless link for the purpose of registration and transfer. It can be seen that in practice, the typical MIPv4 Registration Response messages are significantly larger than the calculated minimum value, but said minimum value is used for illustration purposes. It can also be seen that, as well known to those skilled in the art, the junction update (equivalent to a MIPv4 registration request) that complies with the smallest possible Mobile IPv6 (MlPvβ) is larger than the request message from Record that meets the smallest possible MIPv4. Finally, it can be appreciated that as those skilled in the art are aware, the smallest possible IPv6 Mobile (MlPvβ) union recognition (equivalent to a MIPv4 Registry Response) is greater than the Registration Response message that complies with the smallest MIPv4 possible. By virtue of the previous analysis, it should be appreciated that there is a need for new and more efficient methods to execute the establishment of network links with access nodes in the case of an initial registration of a mobile node with a network, a transfer to a new one access node or in other cases where a mobile node enters a new cell.

SUMMARY OF THE INVENTION The present invention focuses on methods and apparatus for establishing connections between wireless terminals and access nodes. Various methods and apparatus of the invention can be used to establish communication links with one or more mobile nodes. The established links can be used to support communications versions with one or more end nodes, for example, mobile devices. Various novel features focus on the methods of the mobile node to control the establishment of initial links with a first access node. Other features focus on the establishment of a new link as part of a mobile node transfer from a first access node to a second access node during a transfer operation using highly efficient messages and signal. Highly efficient messages, often shorter than IPv4 or IPvd mobile messages that could be used to perform similar tasks, are generated, used and stored in accordance with the various embodiments of the invention. Although some features focus on wireless terminal methods and apparatus, as well as novel messages of the invention stored in a wireless terminal, other features focus on novel access node methods and apparatus. The invention also focuses on data storage devices, for example, memory devices, which store one or more of the novel messages of the present invention. Additional features and benefits of the present invention are discussed in the following detailed description.

BRIEF DESCRIPTION OF THE FIGURES Figure 1 illustrates a network diagram of an exemplary communications system executed in accordance with the present invention. Figure 2 illustrates an exemplary end node executed in accordance with the present invention. Figure 3 illustrates an exemplary access node executed in accordance with the present invention. Figure 4 illustrates an exemplary Server Node executed in accordance with the present invention. Figure 5 illustrates a Local Agent node executed in accordance with the present invention. Figure 6 illustrates an exemplary reduced size IP registration message executed in accordance with the present invention.

Figure 7 illustrates an exemplary reduced size IP registration response message executed in accordance with the present invention. Figure 8 illustrates exemplary signaling executed in accordance with the present invention when an end node changes from one access node to another access node.

DETAILED DESCRIPTION OF THE INVENTION The methods and apparatus of the present invention for establishing links and network connections with access nodes used to support communication sessions with one or more end nodes, eg mobile devices, can be used with a wide range of communication systems . For example, the invention can be used with systems that support mobile communication devices such as laptops equipped with modems, PDAs, and a wide variety of other devices, which support wireless interfaces in the interest of device mobility. Figure 1 illustrates an exemplary communication system 100 executed in accordance with the present invention, for example, a cellular communication network, which comprises a plurality of nodes interconnected by communications links. The nodes in the exemplary communication system 100 exchange information using signals, for example, messages based on communication protocols, for example, Internet Protocol (IP). The communication links of the system 100 can be executed, for example, using cables, fiber optic cables, and / or wireless communication techniques. The exemplary communication system 100 includes a plurality of end nodes 144, 146, 144 ', 146', 144", 146", which have access to the communication system through a plurality of access nodes 140, 140 ' 140. The end nodes 144, 146, 144 ', 146', 144", 146" may be, for example, wireless communication devices or terminals, and the access nodes 140, 140 ', 140"may be , for example, wireless access routers base stations. The exemplary communication system 100 also includes a number of other nodes 104, 106, 109, 110 and 112, used to provide interconnectivity or to provide specific services or functions. Specifically, the exemplary communication system 100 includes a Server 104, used to support state transfer and storage pertaining to end nodes. The Server node 104 may be an AAA server, or it may be a Context Transfer Server, or it may be a server that includes both AAA server functionality and Context Transfer server functionality. The exemplary system 100 of Figure 1 shows a network 102 including the Server 104, the Local Agent node 109 and the node 106, all of which are connected to an intermediate network node 110 via a corresponding network link 105, 108 and 107 , respectively. The intermediate network node 110 in the network 102 also provides interconnectivity to network nodes that are external from the perspective of the network 102 through the network link 111. The network link 111 is connected to another intermediate network node 112, which provides additional connectivity to a plurality of access nodes 140, 140 ', 140"through the network links 141, 141', 141", respectively. Each access node 140140 ', 140"is shown as providing connectivity to a plurality of N endpoints (144, 146), (144', 146 '), (144", 146"), respectively, through the access links corresponding (145, 147), (145 *, 147 '), (145", 147"), respectively In the exemplary communication system 100, each access node 140, 140', 140"is displayed as using wireless technology , for example, wireless access links, to provide access. A radio coverage area, e.g., the communications cell, 148, 148 ', 148"of each access node 140, 140', 140", respectively, is illustrated as a circle surrounding the access node. The exemplary communication system 100 is subsequently used as a basis for the description of various embodiments of the invention. Alternative embodiments of the invention include various network topologies, wherein the number and type of network nodes, the number and type of access nodes, the number and type of end nodes, the number and type of Servers and Local Agents or other agents, the number and type of links, and the interconnectivity between nodes may differ from that of the exemplary communication system 100 shown in Figure I. In various embodiments of the present invention, some of the functional entities shown in Figure 1 may be omitted or combined. The location or placement of these functional entities in the network can also be modified. Figure 2 provides a detailed illustration of an exemplary executed end node 200, for example, a mobile node, executed in accordance with the present invention. The exemplary end node 200, which is shown in Figure 2, is a detailed representation of an apparatus that can be used as any of the end nodes 144, 146, 144 ', 146', 144", 146", which are shown in Figure 1. In the embodiment of Figure 2, the end node 200 includes a processor 204, a wireless communication interface 230, an input / output user interface 240 and memory 210 coupled together by a link 206. Accordingly, through link 206, the various components of end node 200 can exchange information, signals and data. The components 204, 206, 210, 230, 240 of the end node 200 are located within a housing 202. The wireless communication interface 230 provides a mechanism through which the internal components of the end node 200 can send and receive signals to / from external devices and network nodes, for example, access nodes. The wireless communication interface 230 includes, for example, a receiver circuit 232 with a corresponding receive antenna 236 and a transmitter circuit 234 with a corresponding transmit antenna 238 used to couple the end node 200 with other network nodes, for example , through wireless communication channels. The exemplary end node 200 also includes a user input device 242, e.g., a keyboard, and a user output device 244, e.g., a screen, which are coupled to link 206 through the user interface. user input / output 240. Therefore, the input / output user devices 242, 244 can exchange information, signals and data with other components of the end node 200 through the input / output user interface 240 and the link 206. The input / output user interface 240 and the associated devices 242, 244 provide a mechanism through which a user can operate the end node 200 to accomplish various tasks. In particular, the user input device 242 and the user output device 244 provide the functionality that allows a user to control the end node 200 and applications, eg, modules, routine programs and / or functions, which are executed in the memory 210 of the end node 200. The processor 204 under control of several modules, for example, routines, included in memory 210, controls the operation of end node 200 to execute various signaling and processing as discussed below. The modules included in the memory 210 are executed at the time of commissioning or as required by other modules. Modules can exchange data, information, and signals when they are executed. The modules can also share data and information when they are executed. In the embodiment of Figure 2, the memory 210 of the end node 200 of the present invention includes a signaling / control module 212 and signaling / control data 214. The signaling / control module 212 controls the generation of signals and the processing related to receiving and sending signals, for example, messages for storage management, recovery and processing of status information. The messages stored in memory 210 include a connection request message 610, a connection response message 660, an IP registration message 800 and an IP registration response message 900. Messages 800 and 900 may be messages reduced, for example, of small size, of the invention, which are smaller than the IP v4 and / or v6 convention Mobile messages. The messages stored in the memory can be messages which are generated and / or received. The will be discussed in more detail below. The signaling / control data 214 includes status information, eg, parameters, status and / or other information related to the operation of the end node. In particular, the signaling / control data 214 may include configuration information 216, for example, end node identification information, and operational information 218, for example, information regarding the current processing status, status of pending responses, etc. . The module 212 can access and / or modify the data 214, for example, update the configuration information 216 and / or the operational information 218. Figure 3 provides a detailed illustration of an exemplary access node 300 executed in accordance with the present invention. The exemplary access node 300, which is shown in Figure 3, is a detailed representation of an apparatus that can be used as any of the access nodes 140, 140 ', 140"shown in Figure 1. In the 3, the access node 300 includes a processor 304, memory 310, a network / inter-network interface 320 and a wireless communication interface 330, coupled together by the link 306. Therefore, through the link 306, the various components of the access node 300 can exchange information, signals and data The components 304, 306, 310, 320, 330 of the access node 300 are located within a housing 302.

The network / inter-network interface 320 provides a mechanism through which the internal components of the access node 300 can send and receive signals to / from external devices and network nodes. The network / inter-network interface 320 includes a receiver circuit 322 and a transmitter circuit 324 used to couple the node 300 to other network nodes, for example, through copper cables or fiber optic lines. The wireless communication interface 330 also provides a mechanism through which the internal components of the access node 300 can send and receive signals to / from external devices and network nodes, for example, end nodes. The wireless communication interface 330 includes, for example, a receiver circuit 332 with a corresponding receiving antenna 336 and a transmitting circuit 334 with a corresponding transmission antenna 338. The interface 330 is used for coupling the access node 300 to other nodes. network, for example, through wireless communication channels. The processor 304 under the control of various modules, for example, routines, included in the memory 310 controls the operation of the access node 300 to execute various signaling and processing. The modules included in the memory 310 are executed at the time of commissioning or as required by other modules that may be present in the memory 310. The modules can exchange data, information and signals when they are executed. The modules can also share data and information when they are executed. In the embodiment of Figure 3, the memory 310 of the access node 300 of the present invention includes a State Management Module 312 and a Signaling / Control Module 314. In correspondence with each of these modules, the memory 310 also includes State Management data 313 and Signaling / Control data 315. Messages stored in memory 310 include a connection request message 610, a connection response message 660, an IP 800 registration message and a response message registration IP 900. The messages 800 and 900 may be small messages, for example, of small size, of the invention, which are smaller than the IP v4 and / or v6 convention Mobile messages. The memory 310 also includes a Mobile IPv4 and / or IPvd Mobile 680 registration message. The messages stored in the memory can be messages which are generated and / or received. The messages will be discussed in more detail below. The State Management Module 312 controls the processing of signals received from the end nodes or other network nodes relating to state storage and retrieval. The State Management data 313 includes, for example, information related to the end node, such as the state or part of the state, or the location of the current end node state if it is stored in some other network node. The State Management Module 312 may access and / or modify the State Management data 313. The Signaling / Control Module 314 controls the processing of the signals to / from the end nodes on the wireless communication interface 330, and to / from other network nodes on the network / inter-network interface 320, as necessary for other operations, such as a basic wireless function, network management, etc. The Signaling / Control data 315 includes, for example, data related to the end node relating to the wireless channel assignment for basic operation, and other data related to the network, such as the address of the support / administration servers, Configuration information for basic network communications. The Signaling / Control Module 314 can access and / or modify the Signaling / Control data 315. Figure 4 provides a detailed illustration of an exemplary Server node 400 executed in accordance with the present invention. The exemplary Server node 400, which is shown in Figure 4, is a detailed representation of an apparatus that can be used as the Server 104 shown in Figure 1. In the embodiment of Figure 4, the Server 400 node includes a processor 404, the memory 410, a network / inter-network interface 420, coupled together by the link 406. Accordingly, through the link 406, the various components of the access node 400 can exchange information, signals and data. The components 404, 406, 410, 420 of the access node 400 are located within a housing 402. The network / inter-network interface 420 provides a mechanism through which the internal components of the 400 Server node can send and receive signals to / from external devices and network nodes. The network / inter-network interface 420 includes a receiver circuit 422 and a transmitter circuit 424 which are used to couple the node 400 to other network nodes, for example, through copper cables or fiber optic lines. The processor 404 under the control of various modules, for example, routines, included in the memory 410, controls the operation of the Server 400 to execute various signaling and processing. The module included in the memory 410 is executed at the time of startup or when required by other modules that may be present in the memory 410. In the embodiment of Figure 4, the memory 410 of the Server 400 of the present invention includes a Core State Management Module 412 and Core State Management data 413, and an AAA module 415. The Core State Management Module 412 controls the processing of signals received from other Servers, access nodes, or nodes of network concerning the storage and recovery of status. The Core State Management Data 413 includes, for example, state information of the end node. The Core State Management Module 412 can access and / or modify the Core State Management 413 data. The AAA 415 module executes operation pertaining to authentication, authorization and accounting. Figure 5 illustrates an exemplary Local Agent node 500 executed in accordance with the present invention. The exemplary Local Agent node 500 can be used in the system of Figure 1, for example, as the local agent node 109 which serves as a Local Agent. In the embodiment of Figure 5, the local agent node 500 includes an input / output interface 501, a processor 503 and a memory 507, coupled together by the link 502. The elements 501, 502, 503 and 507 of the node Local agent 500 are located within a housing 508, for example, a plastic and / or metal box, represented by the rectangle surrounding the internal elements 501, 502, 503 and 507 of the node. Accordingly, through the link 502 the various components of the access node 500 can exchange information, signals and data. The input / output interface 501 includes circuitry used for coupling the node 500 to other network nodes, for example, through fiber optic lines, and potentially to end nodes, for example, through wireless communication channels. . Processor 503 under the control of various modules, for example, routines, included in memory 507, controls the operation of local agent node 500 to execute various signaling, routing and other operations as will be discussed below. The modules included in the memory 507 are executed at the time of commissioning or as required by other modules. The modules can exchange data, information and signals when they are executed. The modules can also share data and information when they are executed. In the embodiment of Figure 5, the memory 507 of the local agent node 500 of the present invention includes a mobility agent module 506 which includes, for example, parameters, communication session information and / or node status. extreme, security information, and / or other information related to the interaction and / or communication of the end node with an access node and // or another device. Mobility Agent module 506 also includes endpoint node-specific state including mappings between local addresses and end node care addresses. Mobility agent module 506 allows node 500 to support connectivity and mobility management services. end node. Therefore, the local agent node 500 has the ability to provide node mobility, session establishment and session maintenance services for the connected end nodes. The mobility agent module 506 can be executed in a plurality of ways. In the modality of figure 5, it is executed with a collection of sub-modules. As illustrated, the mobility agent module 506 includes the Mobile IPv4 sub-module 505 and the Mobile IPv6 sub-module 504. By including the sub-modules 505 and 504, the mobility agent module 506 has the capability to support multiple versions of Mobile IP signaling including Mobile IPv4 and Mobile IPv6 signaling. In various embodiments, the mobility agent module 506 includes a subset of the sub-modules 505 and 504 that are shown in Figure 5. For example, in the modalities where Mobile IPv6 is not required, the sub-module may be omitted. of Local IPvd Mobile Agent 504. FIG. 6 illustrates an exemplary reduced size IP registration message 800 executed in accordance with the present invention. Said message 800, although sufficient for the purposes of establishing network layer connectivity and redirecting the Mobile IP tunnels, as shown in the invention, is of a size smaller than even the Registration Request message that complies with IPv4. Smallest possible mobile that is shown in the background section. The exemplary reduced size IP registration message 800 includes: a Message Type field 810, a reserved field 820, a "D" (Record Delete) field 830, an "I" (Initial) 840 field, a Message 850, and zero or more Optional extensions 860.

The Message Type field 810 includes a value which identifies said message as an IP registration message of reduced size. In a certain embodiment of this invention, the message type field value identifies the message as a Mobility Management Protocol message designated as RequestRegisterL3. The Reserved 820 field is reserved for future use. In one embodiment of this invention, the reserved field value 820 is set to zero by the sender and ignored by the receiver. The "D" (Record Delete) field 830 includes a value which indicates whether this message is sent to register a network layer or to suppress the registration of a previously registered network layer. The "I" (Initial) field 840 includes a value which indicates whether this message is the initial registration message for this network layer or a subsequent record for a network layer that was previously established. The Message Identifier 850 includes a value which distinguishes the message 800 from at least one other message of the same type (message 800) sent prior to it. In some exemplary embodiments of this invention, the Message Identifier field 850 assumes the values of a sequence number that increases in a monotonic manner. In other exemplary embodiments of this invention, said Message Identifier field 850 assumes the values of a time stamp. In yet other exemplary embodiments of this invention, said Message Identifier field 850 is partially comprised of a sequence number and partially a time stamp. Either zero or more optional Extensions 860 may be included which may comprise several additional parameters. In some exemplary embodiments of this invention, said extensions include the extension of the target access node identifier 870, which identifies the access node to which the message 800 is sent (eg, target access node 530 in FIG. 8) , the last extension of the access node identifier 880, which identifies the access node with which the end node sending the message 800 (eg, end node 510 in FIG. 8) was last connected in the network layer (e.g., access node 520 in Figure 8) and an authentication message 890 of the extension of authenticator 800. In some exemplary embodiments of the invention, each of said extensions 870 and 880 includes at least a Type field, whose value identifies the type of the extension, a length field, whose value identifies the length of the extension and an identifier field, whose value identifies a target access node and a last access node. In some of said embodiments of the invention, the extension of authenticator 890 includes at least one Type field, whose value identifies the type of extension, a length field, whose value identifies the length of the extension and an authenticator field, whose value authenticates the message in a cryptographic manner; said authentication field value calculated based on a shared key between the sender and the receiver. In some exemplary embodiments of this invention, the last extension of the access node identifier 880 is not included when the value of the "I" field 840 indicates that the message 800 is an initial register, while the last extension of the node identifier of access 880 is included when the value of field "I" 840 indicates that message 800 is not an initial record. In some embodiments of this invention, the extension of the authenticator 890 is an optional extension so that it can be omitted from the message 800. Various combinations of optional extensions are possible according to various embodiments of the invention including zero, one, two or three extensions. 890. In an exemplary embodiment of this invention, the Message Type field 810 has a length of 8 bits, the reserved field 820 has a length of 14 bits, the "D" field 830 has a 1 bit length indicator, the "I" field 840 has a 1 bit length indicator, the Message ID 850 is comprised of a 16 bit sequence number and a 32 bit time. In the same embodiment of this invention, when the optional extensions, the target access node identifier 870 and the last access node identifier 880 are included in the message 800, each is composed of an 8 bit type field, a field of length of 8 bits and maximum a Identifier of 64 bits. In the same embodiment of this invention, when the extension of the optional authenticator 890 is included in the message 800, it comprises an 8-bit type field, a 8-bit length field and a maximum 64-bit authenticator. In the same embodiment of this invention, the maximum length of an IP registration message of reduced size 800 is 312 bits, which is significantly smaller than the Registration Request message that complies with the smallest possible MIPv4 which, in the antecedent section is shown with a length of 592 bits. Figure 7 illustrates an exemplary reduced size IP registration response message 900 executed in accordance with the present invention. Said message 900, although sufficient for the purposes of establishing the network layer connectivity and redirecting the Mobile IP tunnels, as shown in the invention, is smaller in size than even the smallest Mobile IPv4 Registration Response message. possible that is shown in the background section. The exemplary reduced size IP registration response message 900 includes: a Message Type field 910, a Message Identifier field 920, a Response Code field 930, a Reserved field 940, a Duration field 950, and zero or more Optional extensions 960. The Message Type field 910 includes a value which identifies said message as an IP registration response message of reduced size. In some embodiments of this invention, the value of the Message type field identifies the IP 900 Registration Response Message as a Mobility Management Protocol message referred to as ResponseMessageL3. The Message Identifier 920 includes a value which compares the message 900 with a corresponding reduced-size IP registration message 800. In some embodiments of this invention the Message Identifier field 920 takes the values from at least part of the value of the message Identifier field 850 of the corresponding reduced-size IP registration message 800, said message 900 is in response to the Response Code field 930 and includes a value which indicates the success or failure of the IP registration operation. The Reserved 940 field is reserved for future use. In a certain embodiment of this invention, the value of this reserved field 940 is set to zero by the sender and ignored by the receiver. The Duration field 950 includes a value which indicates the duration of the IP record. In some embodiments of this invention, the value of the duration field 950 corresponds to the duration of an IP address associated with the message receiver 900. In some of said embodiments of this invention, the message receiver 900 should send another registration message Small size IP before the value of the Duration field 950 expires after receipt of the message 900. Zero or more optional extensions 960 may be included which may include various additional parameters. In some embodiments of this invention, such extensions include the Local Address extension 970, which is an IP address associated with the message receiver 900 (e.g., the IP address of the end node 510 in Figure 8), the extension of Local Agent Address 980, which identifies the address of the Local Mobile IP Agent that provides service to the Local Address included in extension 970 and an authentication message 900 of Authenticator extension 990. In some exemplary embodiments of the invention, each of said extensions 970 and 980 include at least one Type field, whose value identifies the type of the extension, a length field, whose value identifies the length of the extension and an address field, whose value represents a IP adress. In some of said embodiments of the invention, the extension of the authenticator 990 includes at least one Type field, whose value identifies the type of the extension, a length field, whose value identifies the length of the extension and an authenticator field , whose value authenticates the message in a cryptographic way; said authentication field value is calculated based on a shared key between the sender and the receiver. In some exemplary embodiments of this invention, the local address extension 970 and the local agent address extension 980 are only included when the value of the "I" field 840 in the corresponding reduced size IP registration message 800, the message 900 is in response to, indicates an initial registration, while the local address extension 970 and the local agent address extension 980 are not included when the value of the "I" field 840 in the corresponding reduced size IP registration message 800 , message 900 is in response to, indicates a later record. Various combinations of optional extensions are possible according to various embodiments of the invention including zero, one, two or three of the extensions 970, 980, 990. In an exemplary embodiment of this invention, the Message Type field 910 has a length of 8 bits, the Message Identifier 920 is composed of a sequence number of 16 bits, the code field of Response 930 has a length of 8 bits, the Reserved field 940 has a length of 8 bits and the Duration field 950 It has a length of 16 bits. In the same embodiment of this invention, when the local address of optional extensions 970 and the local agent address 980 are included in message 900, each is composed of an 8-bit type field, a length field of 8 bits and an IP address of maximum 32 bits. In the same embodiment of this extension, when the extension of the optional authenticator 990 is included in the message 900, it comprises an 8-bit type field, an 8-bit length field and a maximum 64-bit authenticator. In the same embodiment of this invention, the maximum length of a reduced-size IP registration response message 900 is 232 bits, which is significantly smaller than the registration response message that complies with the smallest possible MIPv4 which , in the antecedent section, it is shown with a length of 560 bits. Figure 8 illustrates exemplary signaling executed in accordance with exemplary embodiments of the invention. The signaling is illustrated in the context of the exemplary system 100 illustrated in Figure 1. The End Node 510 corresponds to any of the end nodes 144, 146, 144 ', 146', 144", 146" of the exemplary system 100 and executed in accordance with exemplary end node execution 200 of Figure 2; The Access Node 520 and the Access Node Target 530 are simplified executions of the exemplary access node 300 of Figure 3 and correspond to any of the access nodes 140, 140 ', 140"in the exemplary system 100 of Figure 1 The Server 540 is a simplified execution of the Server 400 in Figure 4 and corresponds to the Server 104 in the exemplary system 100 in Figure 1. The Local Agent Node 550 is a simplified representation of the local agent 500 in Figure 5 and corresponds to the local agent node 109 in the exemplary system 100 in FIG. 1.

In Figure 8, the vertical solid lines 511, 521, 531, 541 and 551 represent the nodes 510, 520, 530, 540 and 550 at time, wherein the portions of the lines 511, 521, 531, 541 and 551 in the upper part of figure 8 represent the previous time that the parts of said lines in the lower portion of figure 8. The horizontal solid lines 610, 620, 640, 660, 670, 680, 690, 700, 710 and 720 represent signals between the nodes 510, 520, 530, 540 and 550. The wide double arrow lines 600, 630 and 650 represent groups of signals exchanged between nodes 510, 520, 530, 540 and 550. Lines with dashes 621 and 641 represent alternative signals to the signals 620 and 640. The dotted lines 630 and 650 represent optional signals. A signal is transmitted between two nodes if the line representing said signal or group of signals indicates a point on the vertical line representing said node in time. For example, the signal 610 is transmitted at time 610a by the end node 510 and is required by the target access node 530 at time 610c. Now the establishment of the physical layer will be described. In Figure 8, the end node 510, at point 600a transmits a signal, part of the group of signals 600, to the target access node 530 requesting physical layer access to said node 530. The target access node 530 receives the signal, part of the group of signals 600, at point 600c and transmits another signal, part of the group of signals 600, to the end node 510, granting physical layer access to the end node 510. Now the establishment of the signal layer will be described. link. The end node 510 at point 610a transmits the Connection Request message 610 to the target access node 530, requesting link establishment and media access control layer communications with the target access node 530. In some embodiments examples of the invention, the Connection Request message 610 includes a first identifier, which identifies the end node 510. In some embodiments of this invention, said message 610 also includes a second identifier, which identifies the access node with which end node 510 had previously established connection, for example, access node 520. Said target access node 530 receives the Connection Request message 610 at point 610c at which time the parameters (e.g., identifiers) included in said message 610 are stored in the memory of the target access node 530. In other exemplary embodiments of this invention, the message 610 is a Transfer Request message indicating that the end node 510 had previously established communications with this or another access node (for example, access node 520). An exemplary embodiment of Core Context Transfer will be described. At point 620c, said node 530 transmits a Status Request message 620 to the server 540, requesting authorization and another corresponding state to the end node 530. The Status Request message 620 includes at least some of the parameters stored in the point 610c in the memory of the node 530; for example, the identifier of the end node 510. The Server 540 receives the Status Request message 620 at point 620d and searches in its memory for the state associated with the end node 510. In some exemplary embodiments of the invention, in where the server 540 is a core state transfer server, said server 540 transmits the status response message 640 at point 640d including authorization status and another state (e.g., security keys, IP addresses and other parameters) associated with the end node 510. The target node 530 receives said message 640 at the point 640c and stores in its memory at least part of the state associated with the end node 510 that is included in the message 640.

An AAA server mode will now be described. In some other exemplary embodiments of this invention wherein the server 540 is an authentication and authorization server (AAA), server 540 transmits a message, part of an optional group of messages 630, at point 630d, requesting proof of the identity of end node 510. Said node 510 receives the message, part of message group 630, at point 630a and transmits proof of the identity message, part of the message group 630, to the Server 540. In some embodiments of this invention, the server 540 and the end node 510 exchange additional messages proving the identity of both the end node 510 and from the 540 server to each other. When the server 540 is satisfied with the identity of the end node 510 at point 640d, it sends the message 640 including the authorization status and another state (e.g., security keys, IP addresses and other parameters) associated with the node end 510. Target access node 530 receives said message 640 at point 640c and stores in its memory at least part of the state associated with end node 510 that is included in message 640. An exemplary embodiment of Context Transfer Par to Par. In some exemplary embodiments of the invention, instead of the message 620, the target access node 530 sends the message 621, at point 621c, to the access node 520; said access node 520 is the last access node with which the end node 510 had connection. Said message 621, according to this invention, including at least some of the parameters stored in point 610c in the memory of the node 530; for example, the identifier of end node 510. Access node 520 receives message 621 at point 621b and searches in its memory for the state associated with end node 510. Said access node 520 transmits the response message 641 at point 641b including authorization state and other state (e.g., security keys, IP addresses and other parameters) associated with the end node 510. The target node 530 receives said message 641 at point 641c and stores it in its memory for at least part of the state associated with the end node 510 that is included in the message 641. An optional security association phase, used in some embodiments of the present invention, will now be described. In some embodiments of this invention where data traffic coding is required on the link between the end node 510 and the target access node 530, said node 530 transmits a message, part of an optional message group 650, in point 650c, to establish at least one encryption key with end node 510. Said node 510 receives the message, part of message group 650, at point 650a and transmits the key establishment message, part of the group of messages 650, to the target access node 530. In some embodiments of this invention, the target access node 530 and the end node 510 exchange additional messages to establish the encryption key. The termination of the link layer establishment will now be described. The target access node 530, at point 660c, sends the Connection Response message 660, granting at least link layer access to the end node 510. The end node 510 receives said message 660 at the point 660a. In the embodiment of this invention wherein the message 610 is a Transfer Request message, the message 660 is a Transfer Response message. Now the establishment of the Network Layer. The end node 510 builds in its memory and transmits the reduced size IP registration message 670, at point 670a, to the target access node 530 requesting network layer establishment and packet redirection through of said node 530. In some exemplary embodiments of the invention, said reduced IP registration message 670 is executed according to the invention according to the message type 800 of Figure 6. The target access node 530 receives the message 670 at point 670c and stores the values of at least some of the fields included in said message 670 in its memory. The target access node 530 constructs the Mobile IP registration message 680 and transmits it at the point 680c to the local agent 550. According to this invention, the Identification field of the Mobile IP registration request message 680 includes at least one part of the Message Identifier field 850 of message 800 of Figure 6. An initial registration mode will now be described. In an exemplary embodiment of this invention, the reduced size IP registration message 670 executed in accordance with the message 800 in Figure 6, the "I" field 840 indicates the initial registration. In this embodiment of the invention, the target access node 530 constructs the Mobile IP registration message 680 and transmits it at point 680c to the local agent 550. For the construction of the Mobile IP Registration Request 680 message, the access node target 530 combines the state associated with the end node 510 with the state received at point 640c from the server 540. In an embodiment of this invention wherein the server 540 is an AAA server, the state associated with the end node 510 which is stored in the node 530 includes a local address and local agent address values associated with the end node 510, said local address and local agent address values are allowed to be equal to zero. In one embodiment of this invention, the local agent address included in said stored state is not equal to zero and the target access node 530 uses said value as part of the corresponding field of the Mobile IP registration request message 680. In another embodiment of this invention, the local agent address included in said stored state is equal to zero and the target access node 530 uses a local agent address value locally configured as part of the corresponding field of the mobile IP registration request message 680. In another embodiment of this invention, the local address included in said stored state is not equal to zero and the target access node 530 uses said value as part of the corresponding field of the mobile IP registration request message 680. In a further embodiment of this invention, the local address included in said stored state is equal to zero and the target access node 530 uses the value c ero as part of the corresponding field of the mobile IP registration request message 680. Local Agent 550 builds and transmits the registration response message 710 at point 710e to grant the previously received registration request. The target access node 530 receives the registration response message 710 at the point 710c and stores at least part of the values included in the fields of the message 710 in its memory. Said node 530 constructs in memory and transmits at the point 720c the reduced size IP registration message 720 to grant the network layer registration request to the end node 530. In this exemplary embodiment of the invention, said response message of Small-size IP register 720 is executed in accordance with message type 900 of Figure 7. In this embodiment of the invention, the Message Identifier field 920 of message 900 in Figure 7 is copied from the corresponding Message Identifier included in the field of Message Identifier 850 of message 800 in Figure 6, this message is transmitted in response to the local address value included in the message 710 from the local agent 550 is used as part of the value of the local address extension 970 of the message 900 in figure 7, the value of Duration included in said message 710 is used as the upper limit for the value of the duration field 950 of message 900 in figure 7, and the value of local agent address included in said message 710 is used as part of the value of the extension of Agent Address Local 980 of message 900 in figure 7. A subsequent recording mode will now be described. In an exemplary embodiment of this invention, the reduced size IP registration message 670 executed in accordance with the message 800 in Figure 6, the "I" field 840 indicates a non-initial record. In accordance with one embodiment of the invention, as discussed in FIG. 6, in a non-initial registration message 800, the last access node identifier extension 880 is included in said message 800. In accordance with this invention, said last access node identifier is set to an identifier identifying the access node 520. In this embodiment of the invention, the target access node 530 constructs the mobile IP registration message 680 and transmits it at point 680c to the agent 550. For the construction of the Mobile IP Registration Request message 680, the target access node 530 combines the state associated with the end node 510 with the state received at the point 640c from the server 540. In a mode of this extension where the server 540 is a core context transfer server, the state associated with the end node 510 which is stored in the node 530 includes a local address and values e) local agent address associated with the end node 510. In an embodiment of this invention, the target access node 530 uses said local address and local agent address values as part of the corresponding field of the mobile IP registration request message 680. The target access node 530 also constructs a Mobile IP registration message 690 and transmits it at the point 690c to the access node 520, which is identified in the last access node identifier extension of the message 670. The node access 520 receives message 690 at point 690b and transmits a response message 700 at point 700b. The target access node 530 receives said message 700 at point 700c. In another embodiment of this invention, messages 690 and 700 are binding update messages, while in another embodiment of this invention, there are other packet redirection messages. In accordance with this invention, the message 690 identifies at least the end node 510. In one embodiment of this invention, said identifier is the IP address (Local Address) of the end node 510.

The Local Agent 550 builds and transmits the registration response message 710 at point 710e to grant the previously received registration request. The target access node 530 receives the registration response message 710 at the point 710c and stores at least part of the values included in the fields of the message 710 in its memory. Said node 530 constructs in memory and transmits at the point 720c the reduced size IP registration response message 720 to grant the network layer registration request to the end node 510. In the exemplary embodiment of this invention, said message of Small size IP registration response 720 is executed in accordance with the message type 900 of Figure 7. In this embodiment of the invention, the Message Identifier field 920 of the message 900 in Figure 7 is copied from the Message Identifier corresponding to the field of Message Identifier 850 of message 800 in Figure 6, in response to which this message 720 is being transmitted, and the duration value included in said message 710 is used as the upper limit for the value of the field of Duration 950 of message 900 in Figure 7. In this embodiment of the invention, local address extensions and local agent address 970 and 980 of Figure 7 are not included. in the message 720. In an exemplary embodiment of this invention, the end node 510 communicates with the target access node 530 as shown in FIG. 8, while the end node 510 has no other network layer connection. , physical or link established with the same access node or with a different access node. In another exemplary embodiment of this invention, the end node 510 communicates with the target access node 530 as shown in FIG. 8, while the end node 510 has at least one physical network layer connection, or link established with the same access node or with a different access node, for example, access node 520. In various modalities, the nodes described herein are executed using one or more modules to execute the steps corresponding to one or more methods of the present invention, for example, signal processing, message generation and / or transmission steps. Therefore, in some embodiments, various features of the present invention are executed using modules. These modules can be run using software, hardware or a combination of software and hardware. Many of the methods described above or methods steps can be executed using machine executable instructions, such as software, included in a machine-readable medium, such as a memory device, for example, RAM, floppy disk, etc., to control a machine, for example, a general-purpose computer with or without additional hardware, to execute all or portions of the methods described above, for example, on one or more nodes. Accordingly, among other things, the present invention focuses on a machine-readable medium that includes machine executable instructions to cause a machine, e.g., processor and associated hardware, to perform one or more of the steps of the methods described above. . Numerous additional variations to the methods and apparatus of the present invention described above will be apparent to those skilled in the art by virtue of the foregoing description of the invention. Said variations will be considered within the scope of the invention. The methods and apparatus of the present invention can be, and in various embodiments are, used with CDMA, orthogonal frequency division multiplexing (OFDM), or other types of communication techniques which can be used to provide wireless communication links between access nodes and mobile nodes. In some modalities, the access nodes are executed as base stations, which establish communication links with mobile nodes using OFDM and / or CDMA. In various embodiments, the mobile nodes are run as laptops, personal data assistants (PDA), or other portable devices including receiver / transmitter circuits and logic and / or routines, to execute the methods of the present invention.

Claims (40)

NOVELTY OF THE INVENTION Having described the present invention, it is considered as a novelty and, therefore, the content of the following is claimed as a priority: CLAIMS

1. - A method for operating a wireless terminal comprising: transmitting a connection request message to a target base station; receiving a connection response message from the target base station in response to said connection request message; and transmitting an Internet Protocol (IP) registration message, said IP registration message is smaller than a Mobile IPv4 Registration Request message.

2. The method according to claim 1, characterized in that the transmission of the connection request message includes transmitting said connection request message on an air link.

3. The method according to claim 2, characterized in that said connection request message includes a terminal identifier which identifies said wireless terminal.

4. The method according to claim 1, further comprising prior to transmission of said IP registration message, generating said IP registration message, said generation includes: a message type identifier that identifies said message as a message of IP registration; and a message identifier generated by said wireless terminal, the total number of bits included in said IP registration message is less than 480 bits.

5. The method according to claim 4, characterized in that the generated IP registration message does not include a Local Agent address.

6. The method according to claim 5, characterized in that the generated IP registration message also does not include a Local Address.

7. - The method according to claim 6, characterized in that the generated IP registration message also does not include a Duration value.

8. - The method according to claim 7, characterized in that the generated IP registration message also does not include a Care Address.

9. The method according to claim 4, characterized in that said generation includes: incorporating an initial registration indicator value used to indicate whether said IP registration message is an initial registration message for a network layer or a subsequent registration for a network layer that was previously established.

10. The method according to claim 9, characterized in that said initial register indicator value is a one-bit indicator.

11. The method according to claim 4, characterized in that said generation includes: incorporating a value of record suppression indicator which can be established to indicate that said IP registration message is a request to suppress the record of said terminal Wireless

12. The method according to claim 11, characterized in that said value of record suppression indicator is a one-bit indicator.

13. The method according to claim 4, characterized in that said message identifier is a time stamp.

14. The method according to claim 4, characterized in that said message identifier is a sequence number.

15. The method according to claim 4, characterized in that said message identifier is a combination of at least one sequence number and one time stamp.

16. The method according to claim 1, characterized in that said IP registration message includes an initial registration indicator value, the method further comprising: receiving an IP registration response message for said IP registration message, said message The IP registration response includes a Local Address corresponding to said wireless terminal when said initial registration indicator value is set to indicate an initial registration.

17. The method according to claim 16, characterized in that said received IP registration response message does not include the Local Address when said initial registration indicator value is set to indicate a subsequent registration.

18. The method according to claim 17, characterized in that the received IP registration response message includes a duration associated with the Local Address.

19. The method according to claim 17, characterized in that said IP registration message includes a one-bit register deletion indicator which can be set to indicate a registration suppression request, and wherein said response message Recording received includes a recognition indicator and a duration value associated with a Local Address of said wireless terminal.

20. A wireless terminal comprising: a transmission module for transmitting a connection request message to a target base station; a receiving module for receiving a connection response message from the target base station in response to said connection request message; and a registration message generation module IP to generate an Internet Protocol (IP) registration message, said IP registration message is smaller than a Mobile IPv4 Registration Request message.

21. The wireless terminal according to claim 20, characterized in that said transmission module is coupled to an antenna to transmit said connection request message on an air link.

22. The wireless terminal according to claim 21, further comprising: memory including a stored connection request message, the stored connection request message includes a terminal identifier which identifies said wireless terminal.

23. The wireless terminal according to claim 22, further comprising: an IP registration message generating module for generating said registration message including in said registration message: a message type identifier that identifies said message as an IP registration message; and a message identifier generated by said wireless terminal, the total number of bits included in said IP registration message is less than 480 bits.

24. The wireless terminal according to claim 23, characterized in that the generated IP registration message does not include a Local Agent address.

25. - The wireless terminal according to claim 24, characterized in that the generated IP registration message also does not include a Local Address.

26. The wireless terminal according to claim 25, characterized in that the generated IP registration message also does not include a Duration value.

27. The wireless terminal according to claim 26, characterized in that the generated IP registration message also does not include a Care Address.

28. The wireless terminal according to claim 23, characterized in that said IP registration message generation module includes in the generated IP registration message: an initial registration indicator value used to indicate if said IP registration message is an initial registration message for a network layer or a subsequent registration for a network layer that was previously established.

29. The wireless terminal according to claim 28, characterized in that said initial register indicator value is a one-bit indicator.

30. A wireless terminal comprising: a memory that has stored therein an IP registration message, said IP registration message includes less than a total of 480 bits and includes a plurality of elements comprising: an identifier of type of message identifying said message as an IP registration message; and a message identifier which was generated by a wireless terminal.

31. The wireless terminal according to claim 30, characterized in that the stored IP registration message does not include a Local Agent address.

32. - The wireless terminal according to claim 31, characterized in that the stored IP registration message also does not include a Local Address.

33. The wireless terminal according to claim 32, characterized in that the stored IP registration message also does not include a duration value and does not include a Care Address either.

34. The wireless terminal according to claim 30, characterized in that said stored IP registration message: includes an initial registration indicator value used to indicate if said IP registration message is an initial registration message for a network layer. or a subsequent record for a network layer that was previously established.

The wireless terminal according to claim 34, characterized in that said initial register indicator value is a one-bit indicator.

36. The wireless terminal according to claim 30, characterized in that said stored IP registration message further includes: a record suppression indicator value which can be set to indicate that said IP registration message is a request to suppress the registration of said wireless terminal.

37.- The wireless terminal according to claim 36, characterized in that said record suppression indicator value is a one bit indicator.

38.- The wireless terminal according to claim 30, characterized in that said message identifier is a time stamp.

39. The wireless terminal according to claim 30, characterized in that said message identifier is one of i) a sequence number and ii) a combination of at least one sequence number and a time stamp.

40. - The wireless terminal according to claim 39, characterized in that said stored IP registration message also includes an initial registration indicator value.