JP2009512343A - Base station method and apparatus for establishing a connection - Google Patents

Abstract

  A method and apparatus for establishing a communication link is disclosed that is used to support communication with one or more end nodes, eg, mobile devices. Various features use efficient messages and signals to establish an initial link to the first access node and a new link from the first access node to the second access node during the handoff operation. The present invention relates to a mobile node that controls the establishment of.

Description

  The present invention relates to communication systems, and more particularly to a method and apparatus for establishing a connection in, for example, a cellular communication network.

  Communication systems often include a plurality of network nodes coupled to an access node in which end nodes such as mobile devices are coupled to the network. Network nodes may be arranged in a hierarchy. Access authentication and authorization (AAA) servers are nodes that are typically relatively high in the network hierarchy. They typically provide information used for security and access control purposes. Access nodes often have a secure link with an AAA server when such a server is used. This secure link may be through one or more nodes in the hierarchy.

  Operators typically use the RADIUS protocol and associated RADIUS AAA server to manage access sessions in an IP network. AAA systems may be based on new protocols such as DIAMETER in the future. In systems using a RADIUS AAA server, the local access router typically issues one or more RADIUS access requests to the authentication server when a user attempts to gain access to the operator's network during the access session. And authenticate a user based on its identity, such as a network access identifier (NAI). AAA databases typically have the stored identities of those users who are authorized to access the system, along with the service functions that they can invoke. If the user is successfully authenticated, its access port on the access device is configured with a policy state corresponding to the user's service authorization. Service authorization is typically delivered to the access router via RADIUS by an authorization server. While authorized, use of the service during the access session is recorded by the access router and sent as an account record to the account server using an account request message in the RADIUS protocol. The account server may be part of the AAA server or may be a separate server that uses the same protocol as the authorization server. If a user is connected to multiple access routers during a single session, the multiple sessions must be aggregated in the account server.

  AAA systems typically manage IP address assignment (HoA), dynamically assign HA, distribute MN profiles to access routers, and authenticate MIP messages to ensure air links Used with Mobile IP to distribute security keys. A mobile node, an end node that can change its network attachment point, typically sends a MIP message to gain access to a system that initiates an AAA request to authenticate and authorize the mobile node. . The AAA MN profile and 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 attachment points when moving from one cell to another, for example. This involves changing the connection point of the MN from a first access node such as a first router to a second access node such as a second router. This process is commonly known as handoff. As part of the handoff, the MN's CoA / CCoA must be updated so that the packet is redirected to the MN via the new access router and then converted to the HA using MIP signaling. As part of the handoff process, at least part of the state information of the first access router corresponding to the MN involved in the handoff needs to be transferred 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 state information previously delivered via RADIUS to the AR where the MN access session began. State transfer also includes, for example, air link security vector, MN-NAI, MN IP address, MN-EUI-64, remaining MIP registration lifetime, MN multicast group membership, authorization control state, resource reservation state, Many other possible items of diff-serv status, SIP session status, compressor status, MN scheduling history and / or MN specific AR status information may be included.

  In at least one known system, the transfer of state information during a handoff sends a state transfer message over the communication network to the old access node to which the mobile node was connected, the new mobile node connected Achieved by a secure access node. In the response, the old access node sends status information to the new access node. Alternatively, the core node is used to store the state associated with a given mobile node. When the mobile node attempts to move to another target access node, the target access node can retrieve the state associated with the mobile node from the core node.

  With Mobile IP (versions 4 and 6), also known as MIPv4 [MIPv4] and MIPv6 [MIPv6], the mobile node (MN) care-of-address to its home agent (HA). The temporary location indicated by (CoA) can be registered. The HA then makes the persistent address of the MN, also called the home address (HoA), so that packets for that MN can be redirected to its current location using IP encapsulation technology (tunneling). And a registered CoA (also called binding). The CoA used by the MN can be an address belonging to a foreign agent (FA) in the access router if MIPv4 is used, or in this case a collocated care-of address (collocated It can be an address temporarily assigned to the MN itself from the prefix of the access router called “care-of address” (CCoA). The latter model is also applicable to MIPv4, while MIPv6 is the only mode of operation. Note that for the purposes of this document, the terms CCoA and CoA, along with registration and binding update (BU), are interchangeable because they are the corresponding terms for MIPv4 and MIPv6.

  The smallest possible MIPv4-compatible registration request 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 a mobile IP field (at least 192 bits long) as shown below.

  The minimum possible MIPv4-compliant registration request message shown above may lead to inefficient use of resources 592 if it must be sent over the radio link for registration and handoff purposes. Bit length. In practice, it should be noted that a typical MIPv4 compliant registration request message is much larger than the calculated minimum, but that minimum is used for illustrative purposes.

  The smallest possible MIPv4-compatible registration 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 a mobile IP field (at least 160 bits long) as shown below.

  The minimum possible MIPv4-compatible registration response message shown above may lead to inefficient use of resources 560 if it must be sent over the radio link for registration and handoff purposes. Bit length. In practice, it should be noted that a typical MIPv4-compatible registration response message is much larger than the calculated minimum value, but the minimum value is used for illustrative purposes. Finally, as is well known to those skilled in the art, the smallest possible Mobile IPv6 (MIPv6) compliant binding Ack (which corresponds to a MIPv4 registration response) is less than the smallest possible MIPv4 compliant registration response message. Note that it is large.

  Also, as is well known to those skilled in the art, the minimum possible Mobile IPv6 (MIPv6) compliant binding update (which corresponds to a MIPv4 registration request) is larger than the smallest possible MIPv4 compliant registration request message. Please note that.

  From the above considerations, a new implementation that establishes a network link to an access node when the mobile node first registers with the network, handoffs to a new access node, or otherwise when the mobile node enters a new cell, It will be appreciated that there is a need for more efficient methods.

RELATED APPLICATIONS This application is a US Provisional Application No. 60 / 725,589, filed Oct. 11, 2005, “WIRELESS TERMINAL METHODS AND APPARATUS FOR ESTABLISHING CONNECTIONS AND BASE, filed Oct. 11, 2005, which is expressly incorporated herein by reference. It claims the benefits of “STATION METHODS AND APPARATUS FOR ESTABLISHING CONNECTIONS”.

The present invention relates to a method and apparatus for establishing a connection between a wireless terminal and an access node.

  Various methods and apparatus of the present invention can be used to establish a communication link with one or more mobile nodes. The established link can be used to support a communication session with one or more end nodes, eg, mobile devices.

  Various novel features relate to the mobile node's method of controlling the establishment of the initial link to the first access node. Other methods use highly efficient messages and signals to establish a new link as part of the mobile node handoff from the first access node to the second access node during the handoff operation. It is about.

  Often, very efficient messages that are much shorter than Mobile IPv4 or IPv6 messages, which may be used to perform similar tasks, are generated, used and stored by various embodiments of the present invention.

  Some features relate to the method and apparatus of the wireless terminal with the new message of the present invention stored in the wireless terminal, while other features relate to the method and apparatus of the new access node. is there.

  The present invention also relates to a data storage device, such as a memory device, for storing one or more of the novel messages of the present invention.

  Additional features and advantages of the invention will be discussed in the detailed description which follows.

Detailed description

  The method and apparatus of the present invention for establishing links and network connections to an access node used to support a communication session with one or more end nodes, eg, mobile devices, provides extensive communication. It can be used with the system. For example, the present invention may be used with systems that support mobile communication devices, such as a node book computer with a modem, a PDA, and a wide variety of other devices that support a wireless interface among the mobility targets of the device. Can be done.

  FIG. 1 illustrates an exemplary communication system 100 implemented by the present invention, such as a cellular communication network comprising a plurality of nodes interconnected by communication links, for example. Nodes in the exemplary communication system 100 exchange information using signals, such as messages based on a communication protocol such as the Internet Protocol (IP). The communication link of system 100 may be implemented using, for example, wire, fiber optic cable, and / or wireless communication technology. The exemplary communication system 100 includes a plurality of end nodes 144, 146, 144 ′, 146 ′, 144 ″, 146 ″ that access the communication system via a plurality of access nodes 140, 140 ′, 140 ″. Including. End nodes 144, 146, 144 ′, 146 ′, 144 ″, 146 ″ may be, for example, wireless communication devices or terminals, and access nodes 140, 140 ′, 140 ″ may be, for example, wireless access routers or It may be a base station. The exemplary communication system 100 also includes a plurality of other nodes 104, 106, 109, 110 and 112 that are used to provide interconnectivity or to provide specific services or functions. In particular, the exemplary communication system 100 includes a server 104 that is used to assist in the transfer and storage of state for end nodes. Server node 104 may be an AAA server, a context transfer server, or a server that includes both AAA server functions and context transfer server functions.

  The example system 100 of FIG. 1 shows a network 102 that includes a server 104, a home agent node 109, and a node 106, all connected to an intermediate network node 110 by corresponding network links 105, 108, and 107, respectively. The intermediate network node 110 in the network 102 also provides interconnectivity to network nodes that are external to the network 102 via the network link 111. The network link 111 is connected to another intermediate network node 112 that provides further connectivity to the plurality of access nodes 140, 140 ′, 140 ″ via network links 141, 141 ′, 141 ″, respectively. .

  Each access node 140, 140 ′, 140 ″ has a plurality of N respectively via the corresponding access links (145, 147), (145 ′, 147 ′), (145 ″, 147 ″). It is shown as providing connectivity for end nodes (144, 146), (144 ', 146'), (144 ", 146"). Within the exemplary communication system 100, each access node 140, 140 ', 140' 'is shown as using a wireless technology, such as a wireless access link, to provide access. For example, radio coverage areas such as communication cells 148, 148 ', 148' 'of each access node 140, 140', 140 '' are shown as circles surrounding the corresponding access node.

  The exemplary communication system 100 is then used as a reference for the description of various embodiments of the invention. Alternative embodiments of the invention include 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 homes or other agents, the number and types of links, and between nodes The various interconnect topologies include a variety of network topologies that may differ from that of the exemplary communication system 100 shown in FIG.

  In various embodiments of the present invention, some of the functional entities shown in FIG. 1 may be omitted or combined. Also, the location or placement of these functional entities in the network may be different.

  FIG. 2 shows a detailed view of an exemplary end node 200, such as a mobile node, implemented in accordance with the present invention. The exemplary end node 200 shown in FIG. 2 is used as any one of the end nodes 144, 146, 144 ′, 146 ′, 144 ″, 146 ″ shown in FIG. A detailed display of the device that may be performed. In the embodiment of FIG. 2, end node 200 includes a processor 204, a wireless communication interface 230, a user input / output interface 240 and a memory 210 coupled together by a bus 206. Accordingly, various components of end node 200 can exchange information, signals and data via bus 206. The components 204, 206, 210, 230, and 240 of the end node 200 are disposed in the housing 202.

  The wireless communication interface 230 provides a mechanism by which internal components of the end node 200 can send and receive signals to / from external devices such as access nodes and network nodes. The wireless communication interface 230 includes, for example, a receiving circuit 232 with a corresponding receiving antenna 236 and a corresponding transmitting antenna 238 used to couple the end node 200 to another network node via a wireless communication channel, for example. A transmission circuit 234 provided.

  The exemplary end node 200 also includes a user input device 242 such as a keypad and a user output device 244 such as a display coupled to the bus 206 via a user input / output interface 240. Thus, user input / output devices 242, 244 can exchange information, signals and data with other components of end node 200 via user input / output interface 240 and bus 206. User input / output interface 240 and associated devices 242, 244 provide a mechanism by which a user can operate end node 200 to accomplish various tasks. In particular, user input device 242 and user output device 244 allow the user to control applications such as end node 200 and modules, programs, routines and / or functions that execute in memory 210 of end node 200. Provide the function to make.

  A processor 204 under the control of various modules, such as routines contained within memory 210, controls the operation of end node 200 to perform various signaling and processing as discussed below. . Modules included in memory 210 are executed at startup or when called by another module. Modules may exchange data, information and signals when executed. Modules may also share data and information when executed. In the embodiment of FIG. 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 processing related to generation of a signal such as a message and transmission / reception of the signal, for example, for storage of state information, retrieval, and management of processing. Messages stored in the 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 reduced messages of the present invention that are smaller, eg, smaller in size, than conventional mobile IPv4 and / or v6 messages. The message stored in the memory may be a generated and / or received message. This message is discussed in more detail below. Signaling / control data 214 includes status information such as parameters, status and / or other information regarding the operation of the end node. In particular, the signaling / control data 214 may include configuration information 216 such as end node identification information and operational information 218 such as information about the current processing status, pending response status, and the like. Module 212 may access and / or modify data 214, such as updating configuration information 216 and / or operational information 218, for example.

  FIG. 3 shows a detailed view of an exemplary access node 300 implemented in accordance with the present invention. The exemplary access node 300 shown in FIG. 3 is a detailed display of devices that may be used as any one of the access nodes 140, 140 ′, 140 ″ shown in FIG. It is. In the embodiment of FIG. 3, the access node 300 includes a processor 304, a memory 310, a network / internetwork interface 320, and a wireless communication interface 330, all coupled together by a bus 306. Thus, various components of the access node 300 can exchange information, signals and data via the bus 306. The components 304, 306, 310, 320, and 330 of the access node 300 are arranged inside the housing 302.

  Network / internetwork interface 320 provides a mechanism by which internal components of access node 300 can send and receive signals to / from external devices and network nodes. The network / internetwork interface 320 includes a receive circuit 322 and a transmit circuit 324 that are used to couple the node 300 to another network node, for example, via copper or fiber optic lines. The wireless communication interface 330 also provides a mechanism by which internal components of the access node 300 can send and receive signals to / from external devices and network nodes. The wireless communication interface 330 includes, for example, a reception circuit 332 including a corresponding reception antenna 336, a transmission circuit 334 including a corresponding transmission antenna 338, and the like. Interface 330 is used, for example, to couple access node 300 to another network node via a wireless communication channel.

  A processor 304 under control of various modules, such as routines included in memory 310, controls the operation of access node 300 to perform various signaling and processing. Modules included in memory 310 are executed at startup or when called by another module that may be present in memory 310. Modules may exchange data, information and signals when executed. Modules may also share data and information when executed. In the embodiment of FIG. 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. Corresponding to each of these modules, memory 310 also includes state management data 313 and signaling / control data 315. Messages stored in the memory 310 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 reduced messages of the present invention that are smaller, eg, smaller in size, than conventional mobile IPv4 and / or v6 messages. The memory 310 also includes a mobile IPv4 and / or mobile IPv6 registration message 680. The message stored in the memory may be a generated and / or received message. This message is discussed in more detail below.

  The state management module 312 controls the processing of signals received from end nodes or other network nodes with respect to state storage and retrieval. The state management data 313 includes end node related information such as state or partial state, or current end node state location when stored in some other network node. The state management module 312 may access the state management data 313 and / or modify the state management data 313.

  Signaling / control module 314 may process signals to / from end nodes via wireless communication interface 330 and network / Internet as needed for other operations such as basic wireless functions, network management, etc. Controls the processing of signals to / from another network node via work interface 320. Signaling / control data 315 includes, for example, end node related data regarding radio channel allocation for basic operations, and other network related data such as support / management server addresses, configuration information for basic network communications, etc. Including. Signaling / control module 314 may access signaling / control data 315 and / or modify signaling control data 315.

  FIG. 4 shows a detailed view of an exemplary server node 400 implemented in accordance with the present invention. The exemplary server node 400 shown in FIG. 4 is a detailed display of devices that may be used as the server 104 shown in FIG. In the embodiment of FIG. 4, server node 400 includes a processor 404, a memory 410, and a network / internetwork interface 420 coupled together by a bus 406. Accordingly, various components of access node 400 can exchange information, signals and data via bus 406. The components 404, 406, 410, and 420 of the access node 400 are disposed inside the housing 402.

  Network / internetwork interface 420 provides a mechanism by which internal components of server node 400 can send and receive signals to / from external devices and network nodes. The network / internetwork interface 420 includes a receive circuit 422 and a transmit circuit 424 that are used to couple the node 400 to another network node, for example, via copper or fiber optic lines.

  A processor 404 under the control of various modules, such as routines contained in the memory 410, controls the operation of the server 400 to perform various signaling and processing. Modules included in memory 410 are executed at startup or when called by another module that may be present in memory 410. In the embodiment of FIG. 4, the memory 410 of the server 400 of the present invention includes a core state management module 412, a core state management data 413, and an AAA module 415.

  The core state management module 412 controls the processing of signals received from another server, access node or network node for state storage and retrieval. The core state management data 413 includes, for example, end node state information. The core state management module 412 may access the core state management data 413 and / or modify the core state management data 413.

  The AAA module 415 performs operations related to authentication, authorization, and account.

  FIG. 5 shows an exemplary home agent node 500 implemented in accordance with the present invention. The example home agent node 500 can be used in the system of FIG. 1, for example, as the home agent node 109 that functions as a home agent. In the embodiment of FIG. 5, home agent node 500 includes an input / output interface 501, a processor 503 and a memory 507 coupled together by a bus 502. Elements 50 1, 502, 503 and 507 of home agent 500 are placed inside a housing 508, such as a plastic and / or metal case, represented by a rectangle surrounding the internal elements 501, 502, 503 and 507 of the node. Is done. Thus, various components of access node 500 can exchange information, signals and data via bus 502. Input / output interface 501 includes circuitry used to couple, for example, node 500 to another network node via a fiber optic line and possibly to an end node via a wireless communication channel.

  A processor 503 under the control of various modules, such as routines contained in memory 507, for example, of home agent node 500 to perform various signaling, routing, and other operations as discussed below. Control the behavior. Modules contained in the memory 507 are executed at startup or when called by another module. Modules may exchange data information and signals when executed. Modules may also share data and information when executed. In the embodiment of FIG. 5, the memory 507 of the home agent node 500 of the present invention may include, for example, parameters, communication session and / or end node state information, security information, and / or end of access node and / or another device. A mobility agent module 506 is included that includes other information regarding node interaction and / or communication. The mobility agent module 506 also includes an end node specific state that includes a mapping between the end node's home address and care-of address.

  The mobility agent module 506 allows the node 500 to support end node mobility and connectivity management services. Accordingly, the home agent node 500 can provide node mobility, session establishment, and session maintenance services to connected end nodes. The mobility agent module 506 may be implemented in multiple ways. In the embodiment of FIG. 5, mobility agent module 506 is implemented using a set of submodules. As shown, the mobility agent module 506 includes a mobile IPv4 submodule 505 and a mobile IPv6 submodule 504. By including sub-modules 505 and 504, mobility agent module 506 can support multiple versions of Mobile IP including Mobile IPv4 and Mobile IPv6 signaling. In various embodiments, mobility agent module 506 includes a subset of sub-modules 505 and 504 shown in FIG. For example, in an embodiment where Mobile IPv6 is not required, the Mobile IPv6 Home Agent sub-module 504 may be omitted.

  FIG. 6 illustrates an exemplary reduced size IP registration message 800 implemented in accordance with the present invention. The message 800 is sufficient for network layer connectivity setup and mobile IP tunnel redirection, as shown in the present invention, but the minimum possible shown in the background section. The size is smaller than the registration request message corresponding to mobile Ipv4. An exemplary reduced size IP registration message 800 includes a message type field 810, a reservation field 820, a “D” (deregistration) field 830, an “I” (first) field 840, a message identifier 850, and zero or more optional Including the extension 860.

  Message type 810 includes a value that identifies the message as a reduced size IP registration message. In some embodiments of the invention, the value of the message type field identifies this message as a mobility management protocol message called an L3 registration request message.

  Reserved field 820 is reserved for future use. In one embodiment of the invention, the value of the reserved field 820 is set to zero by the sender and ignored by the receiver.

  The “D” (deregistration) field 830 is a value indicating whether this message is sent to register a network layer or to be deregistered from a previously registered network layer. Including.

  The “I” (first) field 840 is a value indicating whether this message is the first registration message for this network layer or a subsequent registration for a previously established network layer. Including.

  Message identifier 850 includes at least a value that distinguishes message 800 from another message of the same type (message 800) as previously transmitted. In some exemplary embodiments of the invention, the message identifier field 850 takes a monotonically increasing sequence number value. In another exemplary embodiment of the invention, the message identifier field 850 takes a timestamp value. In still another embodiment of the present invention, the message identifier field 850 is configured in part by a sequence number or in part by a time stamp.

  Zero or more optional extensions 860 that may include various additional parameters may be included. In some exemplary embodiments of the invention, such an extension is a target access node identifier extension 870 that identifies the access node (eg, target access node 530 of FIG. 8) to which message 800 is sent, message. A final access node identifier extension 880 that identifies the last connected access node (eg, access node 520 of FIG. 8) to which the end node transmitting 800 (eg, end node 510 of FIG. 8) was last connected at the network layer, and message 800 Authenticator extension 890 to be authenticated is included. In some exemplary embodiments of the invention, each of the extensions 870 and 880 has a type field whose value identifies the type of extension, and a length field whose value identifies the length of the extension. , And its value at least includes an identifier field that identifies one of the target access node and the final access node. In some such embodiments of the invention, the authenticator extension 890 has a type field whose value identifies the type of extension, a length field whose value identifies the length of the extension, and A value is calculated based on a key shared between the sender and the recipient and includes at least an authenticator field that cryptographically authenticates the message. In some exemplary embodiments of the invention, if the “I” field 840 indicates that the message 800 is an initial registration, the final access node identifier extension 880 is not included, while the message 800 If the “I” field 840 indicates that is not the first registration, the last access node identifier extension 880 is included. In some embodiments of the invention, the authenticator extension 890 is an arbitrary extension and may be omitted from the message 800. Various combinations of any extension are possible according to various embodiments of the present invention, including zero, one, two or three extensions 890.

  In the exemplary embodiment of the invention, message type field 810 is 8 bits long, reserved field 820 is 14 bits long, “D” field 830 is a 1-bit long flag, and “I” field 840. Is a 1-bit flag, and the message identifier 850 is composed of a 16-bit sequence number and a 32-bit time stamp. In the same embodiment of the invention, if any extension, target access node identifier 870 and final access node identifier 880 are included in message 800, each is an 8-bit type field, an 8-bit length field. And an identifier of up to 64 bits. In the same embodiment of the invention, the optional authenticator extension 890, when included in the message 800, comprises an 8-bit type file, an 8-bit length field, and a maximum 64-bit authenticator. In the same embodiment of the present invention, the maximum length of the reduced size IP registration message 800 is 312 bits which is significantly smaller than the smallest possible MIPv4-compatible registration request message shown in the background section as 592 bits long. It is.

  FIG. 7 illustrates an exemplary reduced size IP registration response message 900 implemented in accordance with the present invention. The message 900 is sufficient for network layer connectivity setup and mobile IP tunnel redirection, as shown in the present invention, but the minimum possible shown in the background section The size is smaller than the registration request message of the mobile Ipv4. 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 reservation field 940, a validity period field 950 and any zero or more extensions 960.

  The message type field 910 includes a value that identifies the message as a reduced size IP registration response message. In some embodiments of the invention, the value of the message type field identifies the IP registration response message 900 as a mobility management protocol message called an L3 registration response message.

  Message identifier 920 includes a value that matches message 900 with the corresponding reduced size IP registration message 800. In some embodiments of the present invention, the message identifier field 920 takes a value from at least a portion of the value of the message identifier field 850 of the corresponding reduced size IP registration message 800 and returns a response to the response code field 930. The message 900 within includes a value indicating success or failure of the IP registration operation.

  Reserved field 940 is reserved for future use. In some embodiments of the invention, the value of the reservation field 940 is set to zero by the sender and ignored by the receiver.

  The validity period field 950 includes a value indicating the validity period of the IP registration. In some embodiments of the present invention, the value of the validity period field 950 corresponds to the validity period of the IP address associated with the recipient of the message 900. In some such embodiments of the present invention, the recipient of the message 900 must send another reduced size IP registration message before the value of the lifetime field 950 expires after the message 900 is received. I must.

  Zero or more optional extensions 960 that may include various additional parameters may be included. In some embodiments of the invention, such extensions are the home address extension 970, extension 970, which is the IP address associated with the recipient of the message 900 (eg, the IP address of the end node 510 of FIG. 8). Includes a home agent address extension 980 that identifies the address of the mobile IP home agent that functions for the home address contained within, and an authenticator extension 990 that authenticates the message 900. In some exemplary embodiments of the invention, each of the extensions 970 and 980 has a type field whose value identifies the type of extension, and a length field whose value identifies the length of the extension. , And an address field whose value represents an IP address. In some such embodiments of the invention, the authenticator extension 990 has a type field whose value identifies the type of extension, a length field whose value identifies the length of the extension, and A value is calculated based on a key shared between the sender and the recipient and includes at least an authenticator field that cryptographically authenticates the message. In some exemplary embodiments of the present invention, the home address extension 970 and home agent address extension 980 have the value of the “I” field 840 in the corresponding reduced size IP registration message 800, message 900, respectively. Included only in the response to indicate the first registration, while the home address extension 970 and home agent address extension 980 are the “I” field in the corresponding reduced size IP registration message 800, message 900. It is not included when the value of 840 indicates the next registration in the response. Various combinations of any extension are possible according to various embodiments of the present invention, including zero, one, two or three extensions 970, 980, 990.

  In an exemplary embodiment of the invention, the message type field 910 is 8 bits long, the message identifier 920 is composed of a 16 bit sequence number, the response code field 930 is 8 bits long, and the reserved field 940 Is 8 bits long, and the validity period field 950 is 16 bits long. In the same embodiment of the invention, if any extension home address 970 and home agent address 980 are included in message 900, each is an 8-bit type field, an 8-bit length field, and a maximum. It consists of a 32-bit IP address. In the same embodiment of this extension, if the optional authenticator extension 990 is included in the message 900, it comprises an 8-bit type file, an 8-bit length field, and a maximum 64-bit authenticator. . In the same embodiment of the present invention, the maximum length of the reduced size IP registration response message 900 is significantly greater than the smallest possible MIPv4-compatible registration response request message, shown in the background section as 560 bits long. Small 233 bits.

  FIG. 8 illustrates exemplary signaling performed by an exemplary embodiment of the present invention. This signaling is shown in the context of the exemplary system 100 shown in FIG. End node 510 corresponds to any of end nodes 144, 146, 144 ′, 146 ′, 144 ″, 146 ″ of exemplary system 100, and the exemplary end node of FIG. Implemented by implementation 200. Access node 520 and target access node 530 are simplified implementations of exemplary access node 300 of FIG. 3 and are among access nodes 140, 140 ′, 140 ″ of exemplary system 100 of FIG. Corresponds to anything. Server 540 is a simplified implementation of server 400 of FIG. 4 and corresponds to server 104 of exemplary system 100 of FIG. Home agent node 550 is a simplified representation of home agent 500 of FIG. 5 and corresponds to home agent node 109 of exemplary system 100 of FIG.

  The vertical solid lines 511, 521, 531, 541 and 551 in FIG. 8 are the same as the line 511, 521, 531, 541 and 551 at the top of FIG. Represents the nodes 510, 520, 530, 540 and 550 in the time, also representing the previous time. Horizontal solid lines 610, 620, 640, 660, 670, 680, 690, 700, 710 and 720 represent signals between nodes 510, 520, 530, 540 and 550. Wide double arrow lines 600, 630 and 650 represent groups of signals exchanged between nodes 510, 520, 530, 540 and 550. Dashed lines 621 and 641 represent alternative signals for signals 620 and 640. Dotted lines 630 and 650 represent arbitrary signals. A signal is transmitted between two nodes when a line representing such a signal or group of signals indicates a point with a vertical line representing the node in time. For example, signal 610 is transmitted by end node 510 at time 610a and received by target access node 530 at time 610c.

  Here, the establishment of the physical layer is described. In FIG. 8, the end node 510 transmits a signal that is part of the signal group 600 to the target node 530 at point 600a to request the node 530 to access the physical layer. Target access node 530 receives a signal that is part of signal group 600 at point 600c, transmits another signal that is part of signal group 600 to end node 510, and provides access to the physical layer to end node 510. To give.

  Here, the establishment of the link layer is described. The end node 510 sends a connection request message 610 to the target access node 530 at point 610 a requesting link establishment and media access control layer communication with the target access node 530. In some exemplary embodiments of the invention, connection request message 610 includes a first identifier that identifies end node 510. In some embodiments of the invention, the message 610 also includes a second identifier that identifies the access node to which the end node 510 has previously established a connection, such as, for example, the access node 520. The target access node 530 receives the connection request message 610 at a point 610 c where the parameter (eg, identifier) included in the message 610 is stored in the memory of the target access node 530. In another embodiment of the present invention, message 610 is a handoff request message indicating that end node 510 has previously established communication with this access node or another access node (eg, access node 520). .

  An exemplary core context transfer embodiment will now be described. At point 620c, the node 530 sends a status request message 620 to the server 540 requesting permission and other status corresponding to the end node 530. The status request message 620 includes at least some of the parameters stored at point 610c in the memory of the node 530, such as an identifier of the end node 510, for example. Server 540 receives status request message 620 at point 620d and searches its memory for the status associated with end node 510. In some exemplary embodiments of the present invention, if the server 540 is a core state transfer server, the server 540 may allow the authorization state and other states (eg, security key, IP address) corresponding to the end node 510. Status response message 640 is transmitted at point 640d. The target node 530 receives the message 640 at point 640c and stores at least a portion of the state associated with the end node 510 included in the message 640 in its memory.

  An embodiment of an AAA server is described. In some other embodiments of the present invention, if server 540 is an authentication and authorization (AAA) server, server 540 sends a message that is part of any message group 630 at point 630d and the end node Request evidence for 510 identities. The node 510 receives a message that is part of the message group 630 at point 630 a and sends a message of proof of identity that is part of the message group 630 to the server 540. In some embodiments of the invention, server 540 and end node 510 exchange additional messages that prove to each other the identities of both end node 510 and server 540. If the server 540 is satisfied with the identity of the end node 510 at point 640d, the server 540 sends a message 640 that includes the authorization state and other states (eg, security key, IP address, and other parameters) associated with the end node 510. The target access node 530 receives the message 640 at point 640c and stores at least a portion of the state associated with the end node 510 included in the message 640 in its memory.

  An exemplary peer-to-peer context transfer embodiment is described. In some exemplary embodiments of the invention, at point 621c, the target access node 530 sends a message instead of message 620 to the access node 520, which is the last access node to which the end node 510 had a connection. 621 is transmitted. In accordance with the present invention, the message 621 includes at least some of the parameters stored at point 610c in the memory of the node 530, such as an identifier of the end node 510, for example. Access node 520 receives message 621 at point 621b and searches for its memory for the state associated with end node 510. The access node 520 sends a response message 641 at point 641b, including the authorization status and other status (eg, security key, IP address and other parameters) associated with the end node 510. The target node 530 receives the message 641 at point 641c and stores at least a portion of the state associated with the end node 510 included in the message 641 in its memory.

  Now, any security-related steps used in some embodiments of the invention will be described. In some embodiments of the invention where encryption of data traffic is required on the link between the end node 510 and the target access node 530, the node 530 is at point 650c and is encrypted with at least the end node 510. Send a message that is part of an arbitrary message group 650 to establish the activation key. The node 510 receives a message that is part of the message group 650 at point 650 a and sends a key establishment message that is part of the message group 650 to the target access node 530. In some embodiments of the invention, target access node 530 and end node 510 exchange additional messages to establish an encryption key.

  Here, the completion of the establishment of the link layer is described. The target access node 530 sends a connection response message 660 at point 660 c to provide at least link layer access to the end node 510. End node 510 receives the message 660 at point 660a. In the embodiment of the present invention, when the message 610 is a handoff request message, the message 660 is a handoff response message.

  Here, the establishment of the network layer is described. At point 670 a, end node 510 constructs a reduced size IP registration message 670 in its memory and sends it to target access node 530 to establish a network layer with node 530 and through node 530. Request packet redirection. In some exemplary embodiments of the present invention, the reduced size IP registration message 670 is implemented by the present invention according to message type 800 of FIG. 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 the message 670 in its memory. The target access node 530 constructs a mobile IP registration message 680 at point 680c and sends it to the home agent 550. According to the present invention, the identification field of the mobile IP registration request message 680 includes at least a part of the message identification field 850 of the message 800 of FIG.

  Here, the first registration embodiment will be described. In one exemplary embodiment of the present invention, a reduced size IP registration message 670 is implemented in response to message 800 of FIG. 6, and the “I” field 840 indicates the initial registration. In this embodiment of the invention, the target access node 530 constructs a mobile IP registration message 680 at point 680c and sends it to the home agent 550. For 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 from the server 540 at point 640c. In one embodiment of the invention, if server 540 is an AAA server, the state associated with end node 510 stored in node 530 is allowed to be equal to zero, the home associated with end node 510. Contains address and home agent address values. In one embodiment of the invention, the home agent address contained in the stored state is not equal to zero and the target access node 530 uses the value as part of the corresponding field of the mobile IP registration request message 680. use. In another embodiment of the present invention, the home agent address included in the stored state is equal to zero and the target access node 530 uses the locally configured home agent address value in the mobile IP registration request message 680. Use as part of the corresponding field. In another embodiment of the invention, the home address contained in the stored state is not equal to zero and the target access node 530 uses the value as part of the corresponding field of the IP registration request message 680. . In a further embodiment of the invention, the home address contained in the stored state is equal to zero and the target access node 530 uses a value of zero as part of the corresponding field of the Mobile IP Registration Request message 680. .

  The home agent 550 constructs and sends a registration response message 710 at point 710e to provide the previously received registration request. The target access node 530 receives the registration response message 710 at point 710c and stores at least a portion of the value contained in the field of the message 710 in its memory. The node 530 constructs and transmits a reduced size IP registration message 720 in memory to provide a network layer registration request to the end node 530 at point 720c. In this exemplary embodiment of the invention, the reduced size IP registration response message 720 is implemented according to the message type 900 of FIG. In this embodiment of the present invention, the message identification field 920 of the message 900 of FIG. 7 is derived from the corresponding message identifier contained in the message identification field 850 of the message 800 of FIG. 6, to which this message was sent in response. The home address value copied and included in the message 710 from the home agent 550 is used as part of the value of the home address extension 970 of the message 900 in FIG. 7 is used as an upper limit for the value of the validity period field 950 of the message 900 of FIG. 7, and the home agent address value contained in the message 710 is the value of the message 900 of FIG. As part of the value of the home agent address extension 980 It is use.

  The following registration embodiment will now be described. In one exemplary embodiment of the present invention, a reduced size IP registration message 670 is implemented in response to message 800 of FIG. 6, and “I” field 840 indicates a non-first registration. As described with respect to FIG. 6, in one non-initial registration message 800, the last access node identifier extension 880 is included in the message 800 according to one embodiment of the present invention. According to the present invention, the final access node identifier is set to an identifier for identifying the access node 520.

  In this embodiment of the invention, the target access node 530 constructs a mobile IP registration message 680 at point 680c and sends it to the home 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 and the state received from the server 540 at point 640c. In one embodiment of this extension, if the server 540 is a core context transfer server, the state associated with the end node 510 stored in the node 530 is the home address and home agent address value associated with the end node 510. Including. In one embodiment of the invention, the target access node 530 uses the home address and home agent address value as part of the corresponding field of the mobile IP registration request message 680.

  Target access node 530 also constructs mobile IP registration message 690 at point 690c and transmits it to access node 520 identified in the final access node identifier extension of message 670. Access node 520 receives message 690 at point 690b and transmits response message 700 at point 700b. The target access node 530 receives the message 700 at point 700c. In another embodiment of the present invention, messages 690 and 700 are binding update messages, while in another embodiment of the present invention there is another packet redirect message. In accordance with the present invention, message 690 identifies at least end node 510. In this embodiment of the invention, the identifier is the IP address (home address) of the end node 510.

  The home agent 500 constructs and sends a registration response message 710 at point 710e to provide a previously received registration request. The target access node 530 receives the registration response message 710 at point 710c and stores at least a portion of the values contained in the fields of the message 710 in its memory. The node 530 constructs and transmits a reduced size IP registration response message 720 in memory to provide a network layer registration request to the end node 510 at point 720c. In the exemplary embodiment of the present invention, the reduced size IP registration response message 720 is implemented according to the message type 700 of FIG. In this embodiment of the invention, the message identification field 920 of the message 900 of FIG. 7 includes the corresponding message identifier included in the message identification field 850 of the message 800 of FIG. 6 to which this message 720 was sent in response. And the validity period value included in the message 710 is used as an upper limit for the value of the validity period field 950 of the message 900 of FIG. In this embodiment of the invention, the home address and home agent address extensions 970 and 980 of FIG. 7 are not included in message 720.

  In one exemplary embodiment of the present invention, end node 510 communicates with target access node 530, as shown in FIG. 8, while end node 510 has been established with the same or different access node. It does not have any other physical link or network layer connection. In another exemplary embodiment of the present invention, end node 510 communicates with target access node 530 as shown in FIG. 8, while end node 510 has the same or different access, eg, access node 520. Has at least one physical link or network layer connection established with the node.

  In various embodiments, the nodes described herein may perform steps corresponding to one or more methods of the present invention, such as signal processing, message generation and / or transmission steps, for example. Implemented using one or more modules. Thus, in some embodiments, various features of the present invention are implemented using modules. Such modules may be implemented using software, hardware, or a combination of software and hardware. Many of the methods or method steps described above can be performed by, for example, in one or more nodes, for example, in one or more nodes, to control a machine such as a general purpose computer with or without additional hardware. To implement all or part, it can be implemented using machine-executable instructions, such as software, contained in a machine-readable medium such as RAM, floppy disk, etc. . Accordingly, the present invention particularly relates to a machine-readable medium comprising machine-executable instructions for causing a machine, such as a processor and associated hardware, to perform one or more steps of the above-described method.

  In view of the above description of the invention, many additional variations on the method and apparatus of the invention described above will be apparent to those skilled in the art. Such variations are to be considered within the scope of the invention. The methods and apparatus of the present invention may be used in various embodiments to provide CDMA, orthogonal frequency division multiplexing (OFDM), or a wireless communication link between an access node and a mobile node, Used with various other types of communication technologies. In some embodiments, the access node is implemented as a base station that establishes a communication link with the mobile node using OFDM and / or CDMA. In various embodiments, the mobile node is a notebook computer, personal digital assistant (PDA), or other device that includes receiver / transmitter circuitry and logic and / or routines to implement the method of the present invention. Implemented as a portable device.

1 shows a network of an exemplary communication system implemented by the present invention. FIG. 3 illustrates an exemplary end node implemented by the present invention. FIG. 3 illustrates an exemplary access node implemented by the present invention. FIG. 4 illustrates an exemplary server node implemented in accordance with the present invention. FIG. 3 illustrates an exemplary home agent node implemented by the present invention. FIG. 4 illustrates an exemplary reduced size IP registration message implemented by the present invention. FIG. 4 illustrates an exemplary reduced size IP registration response message implemented by the present invention. FIG. 3 illustrates exemplary signaling performed by the present invention when an end node transitions from one access node to another.

Claims (20)

Receive mobile IP registration message of reduced size,
A method of operating a base station, comprising generating at least one mobile IPv4 or mobile IPv6 registration message from the reduced size mobile IP registration message.   The method of claim 1, wherein receiving the reduced size mobile IP registration message comprises receiving a registration message over an air link.   3. The method of claim 2, wherein the reduced size mobile IP registration message includes a base station identifier that identifies the base station.   Prior to receiving the reduced size mobile IP registration message, further comprising storing state information corresponding to the wireless terminal, wherein the state information includes a home address, a home agent address, and wireless terminal profile information. The method of claim 2 comprising at least one of:   5. The method of claim 4, further comprising receiving at least one of a home address, a home agent address, and wireless terminal profile information from another node different from the wireless terminal prior to the storing step.   5. The method of claim 4, wherein at least one of Mobile IPv4 and Mobile IPv6 registration messages includes generating a registration message that includes a home agent address value that was not included in the reduced size mobile IP registration message.   Generating at least one of the Mobile IPv4 and Mobile IPv6 registration messages further includes including a home agent address value, wherein the home address value is received and stored from the additional node. The method of claim 6, wherein the method is a home agent address value.   8. The method of claim 7, wherein the home address value is zero if the stored information corresponding to the wireless terminal does not include a non-zero home address value.   Generating at least one of the Mobile IPv4 and Mobile IPv6 registration messages further includes incorporating a care of address identifying the base station into the generated Mobile IPv4 and Mobile IPv6 registration messages. The method of claim 6 comprising.   The method of claim 10, wherein the reduced size mobile IP registration message includes a message identifier, the message identifier including at least one of a sequence number and a time stamp.   The method of claim 11, wherein the message identifier includes both a sequence number and a time stamp.   The method according to claim 5, wherein the other node different from the wireless terminal node is an authentication and authorization server.   6. The method of claim 5, wherein the other node different from the wireless terminal node is another base station to which the wireless terminal was previously connected. A receiver module for receiving a reduced size mobile IP registration message;
A base station comprising a signal generation module for generating at least one mobile IPv4 or mobile IPv6 registration message from the reduced size mobile IP registration message.   The base station of claim 15, wherein the receiver module is a radio receiver module that receives a registration message over an air link.   And further comprising a memory for storing the received reduced size mobile IP registration message, the memory including a stored reduced size mobile IP registration message including a base station identifier identifying the base station. Item 16. A base station according to item 16.   The base station according to claim 16, wherein the memory further includes state information corresponding to the wireless terminal, and the state information includes at least one of a home address, a home agent address, and wireless terminal profile information.   19. The base station according to claim 18, further comprising a network interface that receives at least one of a home address, a home agent address, and wireless terminal profile information from another node different from the wireless terminal.   The signal generation module accesses the stored state information, and from the stored state information, is not included in the reduced size mobile IP registration message, but from the reduced size mobile IP registration message. 19. The base station according to claim 18, comprising means for retrieving a home agent address value included in at least one of the generated mobile IPv4 or mobile IPv6 registration message.   The signal generation module further comprises means for obtaining the additional node received home agent address value from stored information included in at least one of the generated Mobile IPv4 or Mobile IPv6 registration messages. The base station according to claim 20.

Images