A mobile point-to-point protocol

<u>Field of the Invention</u>

0001This invention relates generally to communications and, more particularly, to packet communications systems.

<u>Background of the Invention</u>

0002One use of the Internet as a communications vehicle is as an enhanced data back-bone for coupling together workgroups to provide what is referred to as a "virtual private network" (VPN). One application of a VPN is in a corporate environment such that employees, e.g., at home, can remotely access, via the Internet, corporate data networks. A VPN provides security, and authentication, for a remote user to join a closed user group notwithstanding the use of public facilities. In effect, the use of a VPN provides a WAN-like vehicle to the corporation and its employees. (Although the corporate network could also provide direct remote access, e.g., a user dials directly into the corporate network, there are economic advantages to the use of a VPN.)

0003To provide a VPN, tunneling protocols are used such as the "Point-to-Point Tunneling protocol" (PPTP) and the "Layer 2 Forwarding" (L2F) protocol. Generally speaking, a tunnel protocol enables the creation of a private data stream via a public network by placing one packet inside of another. In the context of a VPN, an IP packet is placed inside another IP packet. In an attempt to develop an industry standard, the Internet Engineering Task Force (IETF) is developing the "Layer 2 Tunneling Protocol" (L2TP), which is a hybrid of the PPTP and L2F protocols (e.g., see <nplcit id="ncit0001" npl-type="s"><text>K. Hamzeh, T. Kolar, M. Littlewood, G. Singh Pall, J.Taarud, A. J. Valencia, W. Verthein; Layer Two Tunneling Protocol "L2TP"; Internet draft, March, 1998</text></nplcit>).

0004For a remote user, a typical form of access to a VPN is via a "plain-old-telephone service" (POTS) connection to an "Internet service provider" (ISP) that provides the VPN service.; For example, a user incorporates an analog modem into a personal computer, or equivalent, and has a customer account with a particular ISP, referred to herein as the "home" ISP. (It is also assumed that the user's personal computer is properly configured to support one of the above-mentioned tunneling protocols.) The user accesses the VPN by simply making a data call to the home ISP, e.g., dialing a telephone number associated with the "home" ISP and then "logging in" to the VPN.

<u>Summary of the Invention</u>

0005Access to an ISP is via a network access server (NAS). We have realized that in a Personal Communications Service (PCS) wireless environment the above-described tunneling protocols do not allow a remote user, on an existing call, to change the NAS that is providing access to a VPN. As such, the user's physical mobility may disconnect, or drop, the user from the existing VPN connection.

0006Therefore, and in accordance with one aspect of the invention, apparatus and methods for transferring packet data provide a "hand-off' feature that allows an exist point-to-point (PPP) connection to be transferred from one packet server to another packet server.

0007In an embodiment of the invention, three new hand-off control messages are defined for use with the packet servers, namely: (i) Continued Call Request, (ii) Continued Call Reply, and (iii) Continued Call Connect. These three new control messages comprise a L2TP control message header, message identifier (e.g., continued call request, etc.), and a number of fields. As a result, the user does not have to terminate the current PPP connection and then re-establish a new PPP connection.

0008Advantageously, such a hand-off control message or call continue transaction can be initiated by any of the servers involved in the hand-off scenario. For instance, assume an initial arrangement where a point-to-point call is set up and in progress between a user and a private network via a first packet server (e.g., a first Serving LAC) and a second packet server (e.g., an Anchor LAC). If, for example, the user moves out of the region served by the first packet server into a region served by a third packet server (e.g., a second Serving LAC), then a hand-off control message transaction, according to the invention, is initiated. In accordance with the invention, the second Serving LAC may initiate the call continue transaction or the Anchor LAC may initiate the call continue transaction. Alternatively, in accordance with another aspect of the invention, radius servers respectively associated with the packet servers may be employed to perform the call continue transaction.

0009In another aspect of the invention, assuming that a communication path is not yet established between the second packet server (e.g., Anchor LAC) and the third packet server (e.g., the second Serving LAC), a communication path (e.g., tunnel) set-up control message transaction may be performed concurrent with the call continue transaction.

0010<patcit id="pcit0001" dnum="EP0622924A2"><text>EP 0 622 924 A2</text></patcit> describes a method and apparatus which permits mobile computers equipped with modems for cellular telephone systems to obtain various classes of data conununication services, as well as voice service, including taking part in local-area networks. The LAN's may be composed of real LANs in establishments or of other mobile computers. In this way, mobile computers can take part in mainstream client-server computing and also establish ad hoc wireless LANs using the cellular telephone system.

0011<patcit id="pcit0002" dnum="EP0910198A2"><text>EP 0 910 198 A2</text></patcit> describes a wireless data network which includes a wireless packet switched data network for end users that divides mobility management into local, micro, macro and global connection handover categories and minimizes handoff updates according to the handover category. The network integrates MAC handoff messages with network handoff messages. The network separately directs registration functions to a registration server and direct routing functions to inter-working function units.

<u>Summary of the Invention</u>

0012A method and apparatus according to the present invention arc set out in the independent claims, to which the reader is now referred. Preferred features are laid out in the dependent claims.

0013Further, in yet another aspect of the invention, at least one packet server (e.g., the Anchor LAC) monitors state variables associated with the packet servers (e.g., the second Serving LAC and the private network) from which it receives packet data.

<u>Brief Description of the Drawing</u>

0014<ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> shows a communications system in accordance with the principles of the invention;</li><li><figref idref="f0002 f0003">FIGs. 2 - 3</figref> show flow charts of illustrative methods for use in the communications system of <figref idref="f0001">FIG. 1</figref>;</li><li><figref idref="f0004">FIG. 4</figref> shows an illustrative multi-hop message flow;</li><li><figref idref="f0004 f0005 f0006">FIGs. 5 - 7</figref> show illustrative control message transactions;</li><li><figref idref="f0007">FIG. 8</figref> shows another embodiment of a communications system in accordance with the principles of the invention;</li><li><figref idref="f0008">FIG. 9</figref> shows an illustrative hand-off message flow;</li><li><figref idref="f0009">FIG. 10</figref> shows a flow chart of an illustrative method for use in the communications system of <figref idref="f0007">FIG. 8</figref>;</li><li><figref idref="f0010">FIG. 11</figref> shows illustrative control message transactions;</li><li><figref idref="f0011">FIG. 12</figref> shows another embodiment of a communications system in accordance with the principles of the invention;</li><li><figref idref="f0008">FIG. 13</figref> shows an illustrative hand-off message flow;</li><li><figref idref="f0012">FIG. 14</figref> shows a flow chart of an illustrative method for use in the communications system of <figref idref="f0011">FIG. 12</figref>;</li><li><figref idref="f0013">FIG. 15</figref> shows illustrative control message transactions;</li><li><figref idref="f0014">FIG. 16</figref> shows an illustrative high level block diagram of Network Access Server; and</li><li><figref idref="f0015 f0016">FIGs. 17 - 18</figref> show illustrative control message transactions for outgoing calls.</li><li><figref idref="f0017">FIG. 19</figref> shows alternative illustrative control message transactions;</li><li><figref idref="f0018">FIG. 20</figref> shows further alternative illustrative control message transacations;</li><li><figref idref="f0019">FIG. 21</figref> shows still futher alternative illustrative control message transactions;</li><li><figref idref="f0020">FIG. 22</figref> shows an embodiment employing radius servers for performing a control message transaction; and</li><li><figref idref="f0021">FIG. 23</figref> shows another embodiment employing radius servers for performing a control message transaction.</li></ul>

<u>Detailed Description</u>

0015It is to be appreciated that, for ease of reference, the following detailed description is divided into three topical sections: multi-hop point-to-point protocol; mobile point-to-point protocol; and payload message overviews and congestion control for mL2TP.

<u>Multi-Hop Point-to-Point Protocol</u>

0016<figref idref="f0001">FIG. 1</figref> shows an illustrative communications system 100 in accordance with the principles of the invention. Other than the inventive concept, the elements are well-known and will not be described in detail. For example, personal computer (PC) 110 includes data communications equipment (not shown) for dial-up access through public-switched-network (PSTN) 110 to ISP B for establishing an Internet connection. Likewise, the solid lines between elements of communications system 100 are representative of well-known communications facilities between the respective endpoints, e.g., the connection between PC 110 and PSTN 110 is representative of a local loop connection, the connection between ISP B and Internet 120 is supported by asynchronous transfer mode (ATM) over a synchronous optical network (SONET), etc. Further, its assumed that the reader is familiar with the above-mentioned L2TP protocol.

0017As can be observed from <figref idref="f0001">FIG. 1</figref>, communications system 100 comprises two ISPs: ISP A, represented by ISP A Network, and ISP B, represented by ISP B Network. The ISP B Network comprises Network Access Server (NAS) 115, which includes a point-of-presence (POP) router (not shown) as known in the art, a local network 120, and a router 125. Similarly, the ISP A Network comprises NAS 155, a local network 160, and a router 165. It is assumed that ISP A provides a VPN service for remotely located employees to access an illustrative Corporate Network via Network Server (NS) 135, which provides, among other functions, a routing and firewall capability. (The Corporate network is assumed to be, e.g., a collection of local area networks (not shown) suitably protected behind NS 135.

0018We have observed that a remote user may, even if only temporarily, be located in a portion of the country that is not served by ISP A but is, instead, served by ISP B. Further, ISP A may desire to extend such VPN coverage to other areas. Therefore, and in accordance with the principles of the invention, a remote user is allowed fo access a VPN via a visiting, or serving, ISP in addition to their home, or anchor, ISP. (Although it is assumed that ISP A and ISP B are different service providers, this is not necessary to the inventive concept, e.g., they could just be separate networks within the same ISP.) Thus, a user (not shown) located at PC 105 can access the corporate network while, e.g., roaming, about the country.

0019At this point, the following definitions are assumed: <ul id="ul0002" list-style="none" compact="compact"><li><b>mL2TP -</b> the L2TP protocol as defined in <nplcit id="ncit0002" npl-type="s"><text>K. Hamzeh, T. Kolar, M. Littlewood, G. Singh Pall, J.Taarud, A. J. Valencia, W. Verthein; Layer Two Tunneling Protocol "L2TP"; Internet draft, March, 1998</text></nplcit>; <i>plus modifications as described herein</i>;.</li><li><b>LAC -</b> mL2TP Access Control, i.e., an NAS that supports mL2TP;</li><li><b>LNS</b> - a NS that supports mL2TP;</li><li><b>Anchor LAC</b> - a LAC that supports tunneling to the LNS for providing a VPN Service; and</li><li><b>Serving LAC</b> - a LAC that supports tunneling to the Anchor LAC.</li></ul>

0020These definitions are used to simplify an illustrative description of the inventive concept. As such, and as those in the art will realize, the inventive concept is not so limited and can be applied to any tunneling protocol and associated processing equipment.

0021In accordance with the inventive concept, the ISP A network illustrates an Anchor LAC 155 and the ISP B network illustrates a Serving LAC 115. As described further below, and in accordance with the principles of the invention, communications system 100 of <figref idref="f0001">FIG. 1</figref> provides a multi-hop tunnel. The example of <figref idref="f0001">FIG. 1</figref> illustrates a two-hop tunnel. One hop is from the ISP B Network to the ISP A Network and the other hop is from the ISP A Network to the Corporate Network.

0022Reference should now be made to <figref idref="f0002">FIG. 2</figref>, which shows an illustrative high-level flow chart of a method in accordance with the principles of the invention. (It is presumed that Serving LAC 115 and the other respective servers are suitably programmed to carry out the below-described methods using conventional programming techniques, which, as such, will not be described herein.) In step 205, the remote user initiates a PPP (Point-to-Point Protocol) connection to ISP B via PSTN 110. In step 210, Serving LAC 115 partially authenticates the user (e.g., using a predefined "username" and "password") and accepts the connection (represented by dotted line 1 of <figref idref="f0001">FIG. 1</figref>). (Alternatively, DNIS (dialed number identification service), CLID (calling line identification), or other equivalent forms of identification could be used.) Obviously, if Serving LAC 115 can not authenticate the user, the connection is not accepted (this step is not shown).

0023As background, and as known in the art, when a remote user wishes to establish a new PPP session, PC 110 initiates a PPP LCP (Link Control Protocol) Config Request to the Serving LAC. The Serving LAC completes both the PPP LCP and PPP PAP/CHAP phases, as known in the art, with the user's equipment before initiating any communication with the Anchor LAC in accordance with the inventive concept. (For secure Conduits, the IETF has defined two protocols for security over PPP connections - the Password Authentication Protocol (PAP) and the Challenge-Handshake Authentication Protocol (CHAP) (e.g., see IETF Request for Comment (RFC) 1334, <i>"PPP Authentication Protocols"</i>)<i>.</i>

0024In step 215, Serving LAC 115 determines is the remote user desires to use a VPN service. This selection could, e.g., be directly associated with particular "usernames" and/or be associated with a separate request from the user, e.g., via a pop-up "HyperText Transport Protocol" (http) form provided by Serving LAC 115.) If the remote user does not request a virtual dial-up service, Serving LAC 115 provides standard Internet access is step 220. However, if the remote user desires to use a VPN, then Serving LAC 115 identifies as associated Anchor LAC in step 225 (described below).

0025Serving LAC 115 stores a VPN table that <i>a priori</i> associates, e.g., a user's identification with a particular Anchor LAC. A portion of such a table is shown below in Table One. In this example, the remote user associated with PC 110 is associated with Anchor LAC ISPA.com, i.e., Anchor LAC 155. <tables id="tabl0001" num="0001"><table frame="all"><title><b><u>Table 1</u></b></title><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="30mm" /><colspec colnum="2" colname="col2" colwidth="23mm" /><thead><row><entry align="center" valign="top">User Identification</entry><entry align="center" valign="top">Anchor LAC</entry></row></thead><tbody><row><entry align="center">usemame</entry><entry align="center">ISPA.com</entry></row></tbody></tgroup></table></tables>

0026It should be noted that equivalent structures, or operations, could be used, such as simply maintaining a list of fields formatted as "username@ISPA.com", where the portion after the "@" symbol indicates the Anchor LAC. Alternatively, ISP B may maintain a database mapping users to services. In the case of a virtual-dial-up, i.e., an identification of the remote user as being associated with a VPN service, the mapping further identifies the Anchor LAC. Alternatively, the Serving LAC can utilize a Radius Access Request/Response transaction with its local Radius Server for this task, as known in the art.

0027In step 230, Serving LAC 115 checks to see if a tunnel exists between itself and Anchor LAC 155. As such, Serving LAC 115 maintains a table, as illustrated in Table Two, below, of current tunnels, represented by a tunnel identification (Tid) value, associated call identifiers (Cid) of calls currently using that tunnel, and the associated Anchor LAC IP address. <tables id="tabl0002" num="0002"><table frame="all"><title><b><u>Table 2</u></b></title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="38mm" /><thead><row><entry align="center" valign="top"><i>Tid</i></entry><entry align="center" valign="top"><i>Cid</i></entry><entry align="center" valign="top"><i>Anchor LAC IP Address</i></entry></row></thead><tbody><row><entry align="center">2</entry><entry align="center">5</entry><entry align="center">h.j.k.l</entry></row></tbody></tgroup></table></tables>

0028If no tunnel connection currently exists between the Serving LAC and the Anchor LAC, then a tunnel is initiated by Serving LAC 115 to the Anchor LAC in step 235 (described below). Once a tunnel exists between the Serving LAC and the Anchor LAC, Serving LAC 115, in step 240, allocates a new Cid, updates Table Two, and initiates a session with Anchor LAC 155 by forwarding a VPN request to Anchor LAC 155 via local network 120, router 125, Internet 130, router 165, and local network 160 (described further below). In this request, Serving LAC 115 conveys user identification information to Anchor LAC 155.

0029Turning now to <figref idref="f0003">FIG. 3</figref>, Anchor LAC 155 receives the request in step 305. In step 310, Anchor LAC 155 also performs authentication of the remote user (e.g., using a predefined "username" and "password" as noted above) and accepts the connection (represented by dotted line 2 of <figref idref="f0001">FIG. 1</figref>). (Alternatively, like the Serving LAC, DNIS, CLID, or other equivalent forms of identification could be used.) If Anchor LAC 155 can not authenticate the user, the connection is not accepted (this step is not shown). In this case, Serving LAC 115 similarly must convey an error message back to the remote user (not shown).

0030Anchor LAC 155 stores a VPN table that <i>a priori</i> associates, e.g., a user's identification with a particular LNS. A portion of such a table is shown below in Table Three. In this example, the remote user associated with PC 110 is associated with LNS 135, represented by IP address g.h.i.j. <tables id="tabl0003" num="0003"><table frame="all"><title><b><u>Table 3</u></b></title><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="30mm" /><colspec colnum="2" colname="col2" colwidth="13mm" /><thead><row><entry align="center" valign="top">User Identification</entry><entry align="center" valign="top">LNS</entry></row></thead><tbody><row><entry align="center">username</entry><entry align="center">g.h.i.j</entry></row></tbody></tgroup></table></tables>

0031Similar to Serving LAC 115, it should be noted that equivalent structures, or operations, could be used. For example, the Anchor LAC may also perform this function via Radius Access Request/Response messages with a Home Radius Server. In step 315, Anchor LAC 155 checks if this is a valid VPN request using Table Three. If this is not a valid request, Anchor LAC 155 denies the request in step 320. If this is a valid request, Anchor LAC 155 identifies the associated LNS from Table Three in step 325.

0032It is assumed that the Anchor LAC maintains the following connection table for each direction of communication for each established VPN session with a remote user: <tables id="tabl0004" num="0004"><table frame="all"><title><b><u>Table 4</u></b></title><tgroup cols="8"><colspec colnum="1" colname="col1" colwidth="23mm" /><colspec colnum="2" colname="col2" colwidth="12mm" /><colspec colnum="3" colname="col3" colwidth="12mm" /><colspec colnum="4" colname="col4" colwidth="22mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="21mm" /><colspec colnum="8" colname="col8" colwidth="26mm" /><thead><row rowsep="0"><entry align="center" valign="top" /><entry namest="col2" nameend="col3" align="center" valign="top"><i>Serving LAC</i></entry><entry align="center" valign="top"><i>Serving LAC</i></entry><entry namest="col5" nameend="col6" align="center" valign="top"><i>LNS</i></entry><entry align="center" valign="top"><i>LNS</i></entry><entry align="center" valign="top"><i>User Assigned</i></entry></row><row><entry align="center" valign="top"><i>Connection #</i></entry><entry align="center" valign="top"><i>Tid</i></entry><entry align="center" valign="top"><i>Cid</i></entry><entry align="center" valign="top"><i>IP Address</i></entry><entry align="center" valign="top"><i>Tid</i></entry><entry align="center" valign="top"><i>Cid</i></entry><entry align="center" valign="top"><i>IP Address</i></entry><entry align="center" valign="top"><i>IP Address</i></entry></row></thead><tbody><row><entry align="center">5</entry><entry align="center">2</entry><entry align="center">5</entry><entry align="center">d.e.f.g</entry><entry align="center">1</entry><entry align="center">3</entry><entry align="center">g.h.i.j</entry><entry align="center">a.b.c.d</entry></row></tbody></tgroup></table></tables>

0033Anchor LAC associates with each VPN session a connection number. In addition, this connection number is mapped to the respective user. This table lists, by connection number, the Serving LAC IP Address (with associated tunnel ID and Call ID values for that hop), and the associated LNS IP Address (with associated tunnel ID and Call ID values for that associated hop). In step 330, Anchor LAC 155 establishes the VPN session (performs an authentication check, etc.). (Again, if LNS 135 should deny the VPN request (e.g., because of no authentication of the remote user or no capacity), appropriate error messages are generated by the Anchor LAC and the Serving LAC.) Other than the inventive concept, the VPN session with LNS 135 is established as in the prior art. For example, and in accordance with the principles of the invention, in establishing a new VPN session Anchor LAC 155 allocates a new Cid and updates Table 4, e.g., adds a new connection. This last connection is represented by dotted line 3 of <figref idref="f0001">FIG. 1</figref>.

0034At this point, the connectivity is a point-to-point PPP session whose endpoints are the remote user's networking application on one end, as represented by PC 105, and the termination of this connectivity into LNS 135 PPP support on the other. It should be noted that accounting, if necessary, can be performed at the Serving LAC, the Anchor LAC, as well as the LNS, i.e., each element may count packets, octets and connection start and stop times.

0035In support of the above-described multi-hop virtual dial up service, a form of the L2TP (mL2TP) protocol is used and described further below. As in L2TP, there are two parallel components of mL2TP operating over a given tunnel: control messages between each LAC-LNS pair, and payload packets between the same LAC-LNS pair. The latter are used to transport mL2TP encapsulated PPP packets for user sessions between the LAC-LNS pair. As in L2TP, the <i>Nr</i> (Next Received) and <i>Ns</i> (Next Sent) fields are always present in control messages and are optionally present in payload packets. The control messages and payload messages use different sequence number states. For the above-mentioned LAC/LNS pair scenario, there are no changes to the L2TP draft protocol definition as far as the maintenance and usage of (<i>Nr, Ns</i>) is concerned.

0036However, as between the connection between the Serving LAC and the Anchor LAC, the Anchor LAC merely monitors the (<i>Nr, Ns</i>) values sent by the Serving LAC. That is, and in accordance with the inventive concept, the Anchor LAC simply retransmits the values received from the Serving LAC to the LNS. In addition, the Anchor LAC now updates its (State Received, State Sent) values (<i>Sr, Ss),</i> with the corresponding (<i>Nr, Ns</i>) values it has observed from the packets sent by the Serving LAC. Since there will, undoubtedly, be packet losses between the Serving LAC and the Anchor LAC, the <i>Ss</i> (<i>Sr</i>) value at the Anchor LAC may be smaller (smaller) than the <i>Ss</i> (<i>Sr</i>) value at the Serving LAC. In addition, the Anchor LAC maintains two sets of (<i>Sr, Ss</i>) variables, one for the Serving LAC/Anchor LAC control connection and the other for the Anchor LAC/LNS control connection.

0037Before PPP tunneling can occur, in accordance with the inventive concept, between the Serving LAC, the Anchor LAC, and the LNS, control messages must be exchanged between them. Control messages are exchanged over the same tunnel which will be subsequently used to forward payload data once mL2TP call control and management information have been passed (described below).

0038In accordance with the inventive concept, additional Attribute Value Pairs (AVP)s (described below) are defined for use in the L2TP control messages (hence becoming mL2TP control messages). These additional AVPs are for supporting the multi-hop features and call transfer features described above. As defined in L2TP, AVPs are used to further specify control signaling.

0039As noted above, for the above-described LAC/LNS pair case, there is no change to the procedure described in the above-mentioned L2TP draft. As such, only the multi-hop case, requires additional procedures, described below.

0040An illustrative multi-hop message flow is shown in <figref idref="f0004">FIG. 4</figref>. As can be observed from <figref idref="f0004">FIG. 4</figref>, a tunnel (identified by a Tid value) and a call (identified by a Cid value) are established between the Serving LAC and the Anchor LAC. Similarly, a tunnel and a call are established between the Anchor LAC and the LNS. As shown in <figref idref="f0004">FIG. 4</figref>, the inventive concept requires the Serving LAC establish a tunnel to the Anchor LAC. In the context of this invention, the Serving LAC treats the Anchor LAC as an LNS and L2TP procedures are used to initially set up the tunnel.

0041Once a tunnel has been established, a number of control message transactions occur in order to set up a PPP session in accordance with the principles of the invention. These are illustrated in <figref idref="f0004 f0005 f0006">FIGs. 5 - 7</figref>. In these FIGs., only the relevant fields are shown for the various control messages. Note, if the tunnel-id and call-id for the tunnel between the Serving LAC and the Anchor LAC are different from those values for the tunnel between the Anchor LAC and LNS, the Anchor LAC modifies the relevant fields in the packet headers before relaying them in either direction.

0042As shown in <figref idref="f0004">FIG. 5</figref>, the Serving LAC first sends a Start-Control-Connect-Request Message (SCCRQ) message (as defined in L2TP) to the Anchor LAC to configure the tunnel between them. Upon receipt of this message, the Anchor LAC then responds with an Start-Control-Connect-Reply Message (SCCRP) (this occurs subsequent to any above-described authentication). The Serving LAC confirms with a Start-Control-Connection-Connect (SCCCN) message to the Anchor LAC.

0043Following the start control connection message exchanges shown in <figref idref="f0004">FIG. 5</figref>, the Serving LAC sends an Incoming-Call-Request (ICRQ) message to the Anchor LAC as shown in <figref idref="f0005">FIG. 6</figref>. The Incoming-Call-Request message contains sufficient user data and credentials to enable the Anchor LAC to identify the LNS.

0044As noted earlier, if no tunnel exists between the Anchor LAC and the LNS, the Anchor LAC first initiates the SCCR, SCCRP, SCCCN message exchanges with the LNS as defined in L2TP. Once the tunnel exists, an unused slot within the tunnel, a Cid, is allocated by the Anchor LAC. At this point, and in accordance with the principles of the invention, the Anchor LAC relays the ICRQ message (from the Serving LAC) to notify the LNS of this new dial-up session. As shown in <figref idref="f0005">FIG. 6</figref> the Anchor LAC modifies the ICRQ message accordingly before relaying it to the LNS. The modified fields are indicated by a "*", e.g., the assigned call ID. The Anchor LAC also adds a hidden AVP to inform LNS what receive window size it can support. (Note that with the additional hop, the Anchor LAC records the maximum window size negotiated for both the control/payload connections. Also, the window size for the control connection between the Serving LAC and Anchor LAC may be different from that of the control connection between the Anchor LAC and LNS and buffering may be required. To eliminate additional buffering and sequence number monitoring, the Anchor LAC optionally adds an AVP to inform the LNS what receive window size for the payload session the Anchor LAC can support in the Anchor LAC-Serving LAC direction. As a result, the LNS will include only appropriate receive window size values in its ICRP reply and hence only one window size for the payload session in the LNS-Anchor LAC-Serving LAC direction.

0045As noted earlier, the LNS either accepts the connection or rejects it. Rejections MUST include a result condition and MAY include an error indication. In either case, the LNS sends an Incoming-Call-Reply (ICRP) message to the Anchor LAC as shown in <figref idref="f0005">FIG. 6</figref>. The Anchor LAC then modifies the ICRP message appropriately and relays it to the Serving LAC in accordance with the invention (again, modified fields are indicated by an "*" in <figref idref="f0005">FIG. 6</figref>). Since the packet processing delay (PPD) field received from the LNS only includes the processing delay at the LNS, the Anchor LAC add to this value the processing delay at its own node. Then, the ICRQ message is relayed to the Serving LAC.

0046In response, the Serving LAC sends an Incoming-Call-Connected (ICCN) message to the Anchor LAC as shown in <figref idref="f0006">FIG. 7</figref>. Inside this message, the Serving LAC passes all the LCP Config Request information as well as the Proxy Authentication Information. That is, the Serving LAC is forwarding the results of the LCP Config Request/Ack, PPP PAP/CHAP performed with the user's equipment. The Anchor LAC modifies the PPD field of the received ICCN message before relaying it to the LNS. Currently, no use is made the tx connect speed and rx connect speed.) Although not shown, and in accordance with the invention, the Anchor LAC also relays all the Set-Link-Info, Hello and Wan-Error-Notify messages defined in L2TP. (It should be observed that the description above illustrates the concept of multi-hop packet tunnel. For example, <figref idref="f0001">FIG. 1</figref> represents a 2-hop packet tunnel.

0047It should be observed that the multi-hop mL2TP tunnels described above occur exclusively at the frame layer. As such, actual policies of address management by the LNS are irrelevant to the above-described Virtual dial-up service since, for all purposes of the PPP protocol handling, the remote user appears to have connected at the LNS.

<u>Mobile Point-to-Point Protocol</u>

0048Turning now to <figref idref="f0007">FIG. 8</figref>, another embodiment of the inventive concept is shown. <figref idref="f0007">FIG. 8</figref> is similar to <figref idref="f0001">FIG. 1</figref>. Other than the inventive concept, the elements are well-known and will not be described in detail. Like numbers indicate like functions and will not be further described except where necessary.

0049In <figref idref="f0007">FIG. 8</figref>, PC 805 includes data communications equipment (not shown) for establishing wireless access through Personal Communications Service (PCS) wireless network 810 to the Internet. PCS Wireless services are known in the art and will not be described in detail. PCS wireless network 810 comprises a plurality of mobile switching centers as represented by elements 815 and 820. Each switching center serves a geographical area (not shown). It is assumed that elements 815 and 820 include an NAS, e g., Serving LACs similar to Serving LAC 115 of <figref idref="f0001">FIG. 1</figref>. Initially, it is assumed that the remote user establishes a VPN session to the corporate network using the above-described multi-hop technique. In particular, the remote user is in a geographical area such that this initial connection is routed through element 815 via connections 814 and 816. In the context of a wireless PCS application, the initial PPP connection is between element 815 and PC 805. Although shown as a part of the switching elements for simplicity, the NAS functions could also be performed in separate pieces of equipment. Similarly, the other elements such as a local network and router are not shown for simplicity.

0050We have realized that in a wireless environment tunneling protocols, such as L2TP, do not allow a remote user to change the existing PPP connection from one switching element to another. For example, assuming for the moment that <figref idref="f0007">FIG. 8</figref> does not embody the inventive concept, when the remote user roams, e.g., to a geographical area served by element 820 (and hence a different NAS) the user's communication session is handed-off to element 820 as known in the art. However, the existing PPP connection - and hence the VPN session - is dropped and must be re-established since, as noted, there is no ability to transfer existing PPP connections from one NAS to another. In this context, the communications system of <figref idref="f0007">FIG. 8</figref> overcomes this problem.

0051Therefore, and in accordance with the invention, an NAS or LAC incorporates a "hand-off" feature that allows the existing NAS to hand-off an existing PPP connection to another NAS. In accordance with this feature, 3 new control messages are defined, namely: (i) Continued Call Request, (ii) Continued Call Reply, and (iii) Continued Call Connect. As a result of the above, the user does not have to terminate the current PPP connection and then re-establish a new PPP connection. These 3 new control messages comprise a L2TP control message header, message identifier (e.g., continued call request, etc.), and a number of fields (described below).

0052In accordance with the inventive concept, an illustrative hand-off message flow is shown in <figref idref="f0008">FIG. 9</figref>. As can be observed from <figref idref="f0008">FIG. 9</figref>, a tunnel (identified by a Tid value) and a call (identified by a Cid value) are initially established between element 815, which includes a Serving LAC, and the Anchor LAC. Similarly, a tunnel and a call are established between the Anchor LAC and the LNS. (A method for establishing this initial VPN session was described above.) As shown in <figref idref="f0008">FIG. 9</figref>, the inventive concept allows the existing Serving LAC to transfer the existing PPP connection to a new Serving LAC, as represented by element 820.

0053Reference should now be made to <figref idref="f0009">FIG. 10</figref>, which is an illustrative flow chart of a method for use in providing a "hand-off feature". As noted, it is assumed that a VPN session exists between PC 805 and the Corporate network via element 815, which includes a Serving LAC, and Anchor LAC 155. In accordance with the inventive concept, PCS wireless network 810 adds to the existing call state variables additional variables indicating the presence (or lack thereof) of a PPP connection for each wireless call, and if a PPP connection exists, PPP connection information that includes the Anchor LAC identification, e.g., the IP address of the Anchor LAC.

0054In step 405 of <figref idref="f0009">FIG. 10</figref>, PCS wireless network 810 detects the need for a hand-off because PC 805 has moved from the geographical area served by element 815 to another geographical area, e.g., the area served by element 820, which includes another Serving LAC. In step 410, PCS Wireless system provides element 820 with notification of the impending hand-off. (The method(s) used by a wireless system to detect and prosecute a hand-off are known in the art and not relevant to the inventive concept. As such, they will not be described herein and are represented by signaling path 811 of <figref idref="f0007">FIG. 8</figref>.) Since the call state information now includes a PPP session indicator and PPP call information, the new Serving LAC (of element 820) identifies the Anchor LAC in step 415. In step 420, the new Serving LAC (of element 820) checks to see if there is an existing tunnel between itself and the identified Anchor LAC, here Anchor LAC 155.

0055If no tunnel exists, the new Serving LAC first establishes a tunnel (as described earlier) in step 425. Then, and in accordance with the inventive concept, the new Serving LAC sends a Continued-Call-Request (CCRQ) message to the Anchor LAC in step 430. This CCRQ message includes the user's name associated with the existing PPP connection, the Tid and Cid values to be used for the transferred (new) PPP session.

0056In step 435, the Anchor LAC recovers the user's name from the received CCRO message and uses this information to determine the LNS and IP address of the old Serving LAC, e.g., from a connection table represented by Table Four, above (this recovered information could also include the respective User Datagram Protocol (UDP) port number). In this step, the Anchor LAC sends a Call-Disconnect-Notify message (e.g., see L2TP) to the old Serving LAC and also identifies in, e.g., Table Four, above, the existing call variables associated with this PPP connection to the remote user, such as old tunnel-id, and old call-id. On the other hand, if the Anchor LAC should reject the Continued-Call-Request, the Serving LAC either sends a signal back to the user so that the existing PPP session can be torn down and a new PPP session can be initiated or the PPP session is simply dropped (steps not shown).

0057In step 440, the Anchor LAC replies with a Continued-Call-Reply (CCRP) message with an appropriate Receive Window Size. The CCRP message includes information on the current <i>Nr</i> and <i>Ns</i> values. In step 445, the Anchor LAC updates its connection table, e.g., Table 4, above, by replacing the entries for the Tid, Cid, and Serving LAC IP address fields (identified in step 435), with the new call information for the existing PPP connection. In step 450, the new Serving LAC stores the <i>Nr, Ns,</i> into its <i>Sr, Ss,</i> values and also stores the receive window size from the received CCRP message, if necessary, and sends a Continued-Call-Connect (CCCN) message to the Anchor LAC, which completes the hand-off.

0058In support of the above-described hand-off feature for a PPP protocol, <figref idref="f0010">FIG. 11</figref> illustrates the above-mentioned new control message transactions in accordance with the principles of the invention. As shown in <figref idref="f0010">FIG. 11</figref>, a CCRQ message is sent to the identified Anchor LAC.

0059In this embodiment, a CCRQ message preferably comprises the following fields: <ul id="ul0003" list-style="dash" compact="compact"><li>Assigned Cid,</li><li>Call Serial No.,</li><li>Bearer Type,</li><li>Physical Channel ID,</li><li>Dialed No.,</li><li>Dialing No.,</li><li>Sub-Address,</li><li>Anchor LAC,</li><li>Challenge,</li><li>User AVP, <ul id="ul0004" list-style="dash" compact="compact"><li>User's name, and</li><li>User's MIN/phone.</li></ul></li></ul>

0060The Anchor LAC field presumes that this information is available during the hand-off. Alternatively, if the hand-off process does not provide information about the Anchor LAC to the New Serving LAC, the hand-off process must then provide enough user information to the New Serving LAC so that the New Serving LAC can search for the Anchor LAC information using help from a Foreign Radius Server as known in the art. That is, the New Serving LAC enquires about the Anchor LAC from a Home Radius Server via Radius Access/Response messages.

0061The User AVP information includes user information (such at the user's name) and other user credentials, e.g. multi-hop virtual dial up service, user's identity (MIN), service provider's phone number etc.

0062Subsequent to the CCRQ message, the Anchor LAC sends a Call-Disconnect-Notify message to the old Serving LAC. Then, the Anchor LAC replies with a Continued-Call Reply (CCRP) message that includes the current <i>Sr, Ss</i> values that it maintains.

0063In this embodiment, a CCRP message preferably comprises the following fields: <ul id="ul0005" list-style="dash" compact="compact"><li>Assigned Cid,</li><li>Call Serial No.</li><li>Result-Code,</li><li>Receive Window Size,</li><li>PPD,</li><li>Sequence No. AVP: <i>Nr, Ns,</i></li><li>ACCM AVP,</li><li>Last Sent LCP Config. Request,</li><li>Last Rcv LCP Config. Request,</li><li>Challenge, and</li><li>Challenge Response.</li></ul>

0064Finally, the new Serving LAC replies with a Continued-Call Connect (CCCN) message. In this embodiment, a CCCN message preferably comprises the following fields: <ul id="ul0006" list-style="dash" compact="compact"><li>Connect Speed,</li><li>Framing Type,</li><li>Modified Window Size AVP,</li><li>PPD, and</li><li>Challenge Response.</li></ul>

0065An alternative embodiment with respect to the control message transactions according to the invention is shown in <figref idref="f0017">FIG. 19</figref>. In such an embodiment, the hand-off control messages (CCRQ, CCRP, and CCCN) are advantageously combined with the tunnel configuration (establishment) control messages (SCCRQ, SCCRP, and SCCCN) and are, respectively, concurrently transmitted between LACs. In this manner, transfer latency between the New Serving LAC and the anchor LAC is significantly improved.

0066In this case, it is assumed that an existing PPP connection or session is already in progress between, for example, PC 805, Serving LAC 815, Anchor LAC 155 and NS 135 (<figref idref="f0007">FIG. 8</figref>). Then, in accordance with the mobility of the user, the PC 805 moves into the coverage region of another serving LAC, e.g., Serving LAC 820. As mentioned, use of conventional methodology would result in the PPP connection being dropped, thus requiring that the call be re-established. However, according to the invention, the call is handed-off to the new Serving LAC without interruption from the perspective of the user. In the previous embodiment, assuming that a tunnel does not already exist between the new ServingLAC and the Anchor LAC, the process for establishing a tunnel, for example, as illustrated in <figref idref="f0004">FIG. 5</figref>, must be performed prior to the hand-off message exchange, for example, as illustrated in <figref idref="f0010">FIG. 11</figref>. However, in accordance with the embodiment illustrated in <figref idref="f0017">FIG. 19</figref>, the tunnel establishment process and hand-off process are performed concurrently. Advantageously, the latency associated with the communications between the new Serving LAC and the Anchor LAC is significantly reduce.

0067Thus, in order to concurrently perform tunnel establishment and call hand-off, the new Serving LAC (e.g., 820 in <figref idref="f0007">FIG. 8</figref>) attaches the SCCRQ message to the CCRQ message before it sends the CCRQ message to the Anchor LAC. Then, as described above, the Anchor LAC uses the user's information to determine the old Tid value, old Cid value, and old IP/UDP port and sends a Call-Disconnect-Notify (CDN) message to the old Serving LAC. Then, the Anchor LAC replies to the new Serving LAC with the SCCRP message appended to the CCRP message, Lastly, the new Serving LAC transmits the combined CCCN and SCCCN messages to the Anchor LAC. It is to be appreciated that while the tunnel establishment control messages are appended to the hand-off control messages, the individual functions and information contained therein, as described above in detail, remain unchanged.

0068Also, while <figref idref="f0017">FIG. 19</figref> shows certain fields as comprising the hand-off control messages, such messages may contain the same or similar fields as shown in the messages shown in <figref idref="f0010">FIG. 11</figref>. In addition, it is to be appreciated that any of the fields shown in the context of <figref idref="f0017">FIGs 19</figref>, <figref idref="f0018">20</figref> and <figref idref="f0019">21</figref> with respect to CCRQ, CCRP, and CCCN, may be present in the same messages of <figref idref="f0010">FIG. 11</figref>, and vice versa. Also, since these embodiments are illustrative in nature, none of the messages described herein are necessarily limited to the fields shown.

0069It is to be appreciated that the term "AVP" refers to Attribute Value Pairs, as is known in PPP operations. Such AVPs are information contained in particular fields of the messages which provide the recipient equipment with relevant information. For example, Window Size AVP and Modified Window Size AVP are fields which respectively indicate to the recipient the window capacity of the sender and a notification to modify the window size. Also, ACCM AVP refers to an Asynchronous Control Character Map AVP. This is a four octet bit map that enables/disables character escapes for 32 ASCII control characters in range 00(hex) to iF(hex). Further, the Sequence No. AVP is the field used to transmit the state variables, <i>Nr</i> and <i>Ns,</i> between servers. Still further, the fields referred to as "Last Sent LCP (Link Control Protocol) Config. Request" and "Last Rcv LCP (Link Control Protocol) Config. Request" are LCP options that are negotiated between servers during an LCP phase associated with the set-up of a PPP session, as is known in the art.

0070Referring now to <figref idref="f0018">FIG. 20</figref>, a further alternative embodiment for performing the hand-off control message transaction is shown. In such an embodiment, it is to be appreciated that the Anchor LAC advantageously initiates the hand-off control message transaction with the new Serving LAC, rather than the new Serving LAC. That is, with respect to the arrangement illustrated in <figref idref="f0007">FIGs 8</figref>, and <figref idref="f0008">9</figref>, rather than the new serving LAC 820 initiating the hand-off control message transaction, the Anchor Lac initiates the transaction, once it receives an indication from the PCS 810 (via a wireless link layer) that the PC 805 has moved from the region covered by the Serving LAC 815 to the region covered by the Serving LAC 820. Thus, as shown in <figref idref="f0018">FIG. 20</figref>, the Anchor LAC transmits the CCRQ message to the new Serving LAC, the new Serving LAC returns the CCRP message, and the Anchor LAC replies with the CCCN message. It is to be appreciated that the information contained in each message, and functions thereof, are similar to that discussed previously and, therefore, will not be repeated here. However, it may be noted that because the Anchor LAC initiates the transactions in <figref idref="f0018">FIG. 20</figref>, the fields in the CCRQ message of <figref idref="f0018">FIG. 20</figref>, sent by the Anchor LAC, are similar to the fields in the CCRP message in <figref idref="f0017">FIG. 19</figref>, sent by the Anchor LAC. This is due to the fact that the Anchor LAC has this information and sends it to the Serving LAC regardless of who initiates the transaction.

0071Also, it is to be appreciated that, as in the embodiment shown with respect to <figref idref="f0017">FIG. 19</figref>, the tunnel establishement control message transaction may also be initiated by the Anchor LAC and, thus, the control message, SCCRQ, SCCRP, and SCCCN, may be respectively combined and concurrently transmitted with the hand-off control messages, CCRQ, CCRP and CCCN.

0072Turning now to <figref idref="f0011">FIG. 12</figref>, another embodiment of the inventive concept is shown, in the context of transferring an existing PPP connection from one NAS to another NAS, where the old NAS has a connection to the LNS. In this example, there is no Serving LAC per se, but simply, e.g., an Anchor LAC that is directly supporting an existing PPP connection. <figref idref="f0011">FIG. 12</figref> is similar to <figref idref="f0007">FIG. 8</figref>. Other than the inventive concept, the elements are well-known and will not be described in detail. Like numbers indicate like functions and will not be further described except where necessary.

0073In <figref idref="f0011">FIG. 12</figref>, PC 805 includes data communications equipment (not shown) for establishing wireless access through Personal Communications Service (PCS) wireless network 910 to the Internet. PCS Wireless services are known in the art and will not be described in detail. PCS wireless network 910 comprises a plurality of mobile switching centers as represented by elements' 875 and 880. Each switching center serves a geographical area (not shown). It is assumed that elements 875 and 880 include an NAS, e.g., LACs similar to Anchor LAC 115 of <figref idref="f0001">FIG. 1</figref>. Initially, it is assumed that the remote user establishes a VPN session to the corporate network as known in the art using, e.g., that portion of L2TP. In particular, the remote user is in a geographical area such that this initial connection is routed through element 875 via connections 874 and 876 to LNS 935. In the context of a wireless PCS application, the initial PPP connection is between element 875 and PC 805. Although shown as a part of the switching elements for simplicity, the NAS functions could also be performed in separate pieces of equipment. Similarly, the other elements such as a local network and router are not shown for simplicity.

0074In this embodiment, the same hand-off procedure is carried out for the LAC/LNS pair except that the above-described CCRQ, CCRP, CCCN messages are exchanged between the new LAC and LNS. In accordance with the inventive concept, an illustrative hand-off message flow is shown in <figref idref="f0008">FIG. 13</figref>. As can be observed from <figref idref="f0008">FIG. 13</figref>, a tunnel (identified by a Tid value) and a call (identified by a Cid value) are initially established between element 875, which includes a LAC, and LNS 935. As shown in <figref idref="f0008">FIG. 13</figref>, the inventive concept allows the existing LAC to transfer the existing PPP connection to a new LAC, as represented by element 880.

0075Reference should now be made to <figref idref="f0012">FIG. 14</figref>, which is an illustrative flow chart of a method for use in providing a "hand-off feature". As noted, it is assumed that a VPN session exists between PC 805 and the Corporate network via element 875, which includes a LAC. In accordance with the inventive concept, PCS wireless network 910 adds to the existing call state variables additional variables indicating the presence (or lack thereof) of a PPP connection for each wireless call, and if a PPP connection exists, PPP connection information that includes the LNS identification, e.g., the IP address of the LNS.

0076In step 505 of <figref idref="f0012">FIG. 14</figref>, PCS wireless network 910 detects the need for a hand-off because PC 805 has moved from the geographical area served by element 875 to another geographical area, e.g., the area served by element 880, which includes another LAC. In step 510, PCS Wireless system provides element 880 with notification of the impending hand-off (The method(s) used by a wireless system to detect and prosecute a hand-off are known in the art and not relevant to the inventive concept. As such, they will not be described herein and are represented by signaling path 911 of <figref idref="f0011">FIG. 12</figref>.) Since the call state information now includes a PPP session indicator and PPP call information, the new LAC (of element 880) identifies the LNS in step 515. In step 520, the new LAC (of element 880) checks to see if there is an existing tunnel between itself and the identified LNS, here LNS 935.

0077If no tunnel exists, the new LAC first establishes a tunnel (as described earlier) in step 525. Then, and in accordance with the inventive concept, the new LAC sends a Continued-Call-Request (CCRQ) message to the LNS in step 530. This CCRQ message includes the user's name associated with the existing PPP connection, the Tid and Cid values to be used for the transferred (new) PPP session.

0078In step 535, the LNS recovers the user's name from the received CCRQ message and uses this information to determine the IP address of the old LAC (this recovered information could also include the respective User Datagram Protocol (UDP) port number). In this step, the LNS sends a Call-Disconnect-Notify message (e.g., see L2TP) to the old LAC and also identifies in, e.g., a connection table similar to that shown in Table Four, above, but sans the Serving LAC information etc., the existing call variables associated with this PPP connection to the remote user, such as old tunnel-id, and old call-id. On the other hand, if the LNS should reject the Continued-Call-Request, the new LAC either sends a signal back to the user so that the existing PPP session can be torn down and a new PPP session can be initiated or the PPP session is simply dropped (steps not shown) .

0079In step 540, the LNS replies with a Continued-Call-Reply (CCRP) message with an appropriate Receive Window Size. The CCRP message includes information on the current <i>Nr</i> and <i>Ns</i> values. In step 545, the LNS updates its connection table by replacing the entries for the Tid, Cid, and LAC IP address fields (identified in step 535), with the new call information for the existing PPP connection. In step 550, the new LAC updates the <i>Nr, Ns,</i> and receive window size from the received CCRP message, if necessary, and sends a Continued-Call-Connect (CCCN) message to the LNS, which completes the hand-off.

0080In support of the above-described hand-off feature for a PPP protocol, <figref idref="f0013">FIG. 15</figref> illustrates the above-mentioned new control message transactions in accordance with the principles of the invention. As shown in <figref idref="f0013">FIG. 15</figref>, a CCRQ message is sent to the identified LNS. Alternatively, if the hand-off process does not provide information about the LNS to the new LAC, the hand-off process must then provide enough user information to the new LAC so that the new LAC can search for the LNS information using help from a Foreign Radius Server as known in the art. That is, the new LAC enquires about the LNS from a Home Radius Server via Radius Access/Response messages. Subsequent to the CCRQ message, the LNS sends a Call-Disconnect-Notify message to the old LAC. Then, the LNS replies with a Continued-Call Reply (CCRP) message that includes the current <i>Sr, Ss</i> values that it maintains. Finally, the new LAC replies with a Continued-Call Connect (CCCN) message.

0081As described above, a PPP connection is transferred from one NAS to another NAS. In support of the newly defined messages, additional call states are defined for the respective NAS as illustrated in Tables 5 and 6, below. <tables id="tabl0005" num="0005"><table frame="all"><title><b><u>Table 5 - New LAC (or NAS)</u></b></title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="30mm" /><colspec colnum="2" colname="col2" colwidth="45mm" /><colspec colnum="3" colname="col3" colwidth="24mm" /><colspec colnum="4" colname="col4" colwidth="29mm" /><thead><row><entry align="center" valign="top">Call State</entry><entry align="center" valign="top">Event</entry><entry align="center" valign="top">Action</entry><entry align="center" valign="top">New State</entry></row></thead><tbody><row><entry align="center">idle</entry><entry align="center">hand-off notification</entry><entry align="center">Send CCRQ</entry><entry align="center">wait-CCRP-reply</entry></row><row><entry align="center">wait-CCRP-reply</entry><entry align="center">Receive CCRP, not accepted</entry><entry align="center">Clean-up</entry><entry align="center">idle</entry></row><row><entry align="center">wait-CCRP-reply</entry><entry align="center">Receive CCRP, accepted</entry><entry align="center">Send CCCN</entry><entry align="center">established</entry></row></tbody></tgroup></table></tables>

0082As can be observed, the additional, or, new, call state for mL2TP associated with the new LAC (or NAS) for a continued call is the wait-CCRP-reply state.

0083Referring now to <figref idref="f0019">FIG. 21</figref>, still a further alternative embodiment for performing the hand-off control message transaction is shown. In such an embodiment, it is to be appreciated that the LNS initiates the hand-off control message transaction with the new Serving LAC, rather than the new Serving LAC. That is, with respect to the arrangement illustrated in <figref idref="f0011">FIGs 12</figref> and <figref idref="f0008">13</figref>, rather than the new serving LAC 880 initiating the hand-off control message transaction, the LNS initiates the transaction, once it receives an indication from the PCS 910 (via a wireless link layer) that the PC 805 has moved from the region covered by the Serving LAC 875 to the region covered by the Serving LAC 880. Thus, as shown in <figref idref="f0019">FIG. 21</figref>, the LNS transmits the CCRQ message to the new Serving LAC, the new Serving LAC returns the CCRP message, and the LNS replies with the CCCN message. It is to be appreciated that the information contained in each message, and functions thereof, are similar to that which was discussed previously and, therefore will not be repeated here. Also, it is to be appreciated that, as in the embodiment shown with respect to <figref idref="f0017">FIG. 19</figref>, the tunnel establishment control message transaction may also be initiated by the LNS and, thus, the control messages, SCCRQ, SCCRP, and SCCCN, may be respectively combined and concurrently transmitted with the hand-off control messages, CCRQ, CCRP, and CCCN.

0084Referring now to <figref idref="f0020">FIGs 22</figref> and <figref idref="f0021">23</figref>, respective alternative embodiments for performing a hand-off control message transaction, according to the invention, by employing radius servers are shown. Particularly, <figref idref="f0020">FIG. 22</figref> shows an arrangement similar to the arrangement shown in <figref idref="f0007">FIGs 8</figref> and <figref idref="f0008">9</figref>, while <figref idref="f0021">FIG 23</figref> shows an arrangement similar to the arrangement shown in <figref idref="f0011">FIGs 12</figref> and <figref idref="f0008">13</figref>. As previously mentioned radius servers, as are known in the art, may be used by the other servers (e.g., Serving LAC, Anchor LAC, LNS) employed in the communication path to assist in identifying and/or confirming particular information necessary for performing communication functions. For instance, as mentioned, a radius server operatively coupled to a Serving LAC may contain a database which associates a particular user with a particular Anchor LAC. In this way, the Serving LAC consults with its radius server to determine such information. Likewise, the Anchor LAC may consult a radius server (home), operatively coupled thereto, to determine similar information pertaining to a user and the LNS with which he is associated.

0085However, according to the invention, the radius servers may be advantageously utilized to also perform a hand-off control message transaction therebetween. That is, rather than a Serving LAC and an Anchor LAC or a Serving LAC and an LNS performing the transaction, respective radius servers operatively coupled thereto and to one another are used to transfer these control messages. In such case, the Serving LAC, Anchor LAC, and LNS are merely tasked with performing any additional processing caused by these messages.

0086<figref idref="f0020">FIG. 22</figref> shows such an arrangement int he context of a hand-off of a PPP connection from and old Serving LAC 815 to a new Serving LAC 820 with respect to the Anchor LAC. A radius server 822, associated with the new Serving LAC 820, is in communication with a radius server 824, associated with the Anchor LAC. Thus, according to the invention, when a hand-off notification is received from the PCS 810 (<figref idref="f0007">FIG. 8</figref>), the radius servers 822 and 824 directly transfer the control messages, CCRQ, CCRP, and CCCN, therebetween. In accordance with the invention, either radius server may initiate the transfer.

0087Similarly, <figref idref="f0021">FIG. 23</figref> shows such an arrangement in the context of a hand-off of a PPP connection from an old Serving LAC 875 to a new Serving LAC 880 with respect to the LNS 935. A radius server 922, associated with the new Serving LAC 880, is in communication with a radius server 924, associated with the LNS. Thus, according to the invention, when a hand-off notification is received from the PCS 910 (<figref idref="f0011">FIG. 12</figref>), the radius servers 922 and 924 directly transfer the control messages, CCRQ, CCRP, and CCCN, therebetween. In accordance with the invention, either radius server may initiate the transfer.

<u>Payload Message Overviews and Congestion Control for mL2TP</u>

0088With respect to payload messages for-mL2TP, the Serving LAC and the LNS follow L2TP procedures. The Anchor LAC swaps the Tid and Cid for the payload packets. The Anchor LAC also monitors the (<i>Nr, Ns</i>) values sent by the Serving LAC. (It should be noted that since there may be packet losses between the Serving LAC and the Anchor LAC, it is expected that both the <i>Sr</i> and <i>Ss</i> values at the Anchor LAC may be lagging behind those values maintained at the Serving LAC.) The Anchor LAC does not change the (<i>Nr, Ns</i>) of the payload packets in either directions. The Anchor LAC only makes use of its own <i>Sr, Ss</i> values when it receives a Continued-Call Request message from a new Serving LAC.

0089With respect to congestion control, the L2TP requirements on when to abide to receive window size, when to send <i>Nr</i>/<i>Ns,</i> and when to send an ACK apply to mL2TP. In addition, mL2TP also has the following additional requirements for the Serving LAC and the Anchor LAC.

0090The Anchor LAC is required to monitor the (<i>Nr, Ns</i>) value sent by the Serving LAC. The Anchor LAC should include the (<i>Sr, Ss</i>) value it maintains in the Continued-Call-Reply message when it replies to the Continued-Call-Connect message it receives from a Serving LAC. Since a network between the Serving LAC and an Anchor LAC is lossy, the <i>Sr</i> value maintained by an Anchor LAC may be lagging behind the Serving LAC.

0091The following is a detailed description of the payload processing rules associated with mL2TP, as affected by the multi-hop point-to-point protocol of the invention. As mentioned, for the multi-hop scenario, the Anchor LAC performs the swappin gof the Tid and Cid values for the payload packets. In addition, the Anchor LAC maintains a 4 tuple state variable (<i>Sr^S,Ss^S,Sr^L,Ss^L</i>) for nL2TP payload packets. The Anchor LAC stores the (<i>Nr, Ns</i>) value sent by the Serving LAC in (<i>Sr^S, Ss^S</i>) and the (<i>Nr, Ns</i>) values from the LNS in (<i>Sr^L',Ss^L</i>)<i>.</i>

0092Note that since there may be packet losses and/or delay between the serving 1AC and the Anchor LAC, it is expected that <i>Sr^S</i> &lt; <i>Sr</i> and <i>Ss^S</i> &lt; <i>Ss,</i> where <i>Sr</i> and <i>Ss</i> are the state variables maintained at the serving LAC. Similarly, since there are also packet losses and/or delays between the Anchor LAC and LNS, it is expected that <i>Sr^L</i> &lt; <i>Sr</i> and <i>Ss^L</i> &lt; <i>Ss,</i> where <i>Sr</i> and <i>Ss</i> are the state variables maintained at the LNS. It is to be appreciated that the Anchor LAC will not change the (<i>Nr, Ns</i>) values of the payload packets in either direction. Three example are given below to illustrate how state variable monitoring according to the invention operates.

0093The first monitoring example is with respect to the case where the communication scenario converts from the one-hop to a two-hop arrangement. It is to be understood that a one-hop arrangement includes, for example, communication links between a PC, an Anchor LAC, and an LNS. A two-hop arrangement includes, for example, communication links between a PC, a Serving LAC, an Anchor LAC, and an LNS. If the Anchor LAC previously maintains a two tuple state variable for a PPP session and receives a CCRQ message, then the Anchor LAC knows that it needs to convert from a one-hop session to a two-hop session. The Anchor LAC first sets <i>Nr = Sr</i> and <i>Ms</i> = <i>Ss</i> in the CCRP message using its current two tuple state variable, (<i>Sr, Ss</i>)<i>.</i> Then, the Anchor LAC changes the state variables into four typle, setting <i>Sr^s</i> = <i>Sr , Ss^S' = Ss, Sr^L</i> = <i>x ,</i> and <i>Sr^L</i> = <i>x</i>. When the Anchor LAC receives the first packet from the LNS after the handover, it updates the <i>Ss^L</i> and <i>Sr^L</i> variables with the observed (<i>Nr, Ns</i>) values. For example, assume the old LAC has <i>Ss</i> = 13 and <i>Sr</i> = 6, and the LNS has <i>Ss</i> = 7 and <i>Sr</i> = 10. The Old LAC, which is now the Anchor LAC, sets <i>Nr = Sr</i> and <i>Ns</i> = <i>Ss</i> in the CCRP message. After the handover, the new Serving LAC has <i>Ss</i> = 13 and <i>Sr</i> = 6, the LNS has <i>Ss</i> = 7+ and <i>Sr</i> = 10+, and the Anchor LAC (old LAC) has <i>Ss^S =</i> 13, <i>Sr^s =</i> 6, <i>Ss^L</i> = 7 +, and <i>Sr^L</i> = 10 +. It is to be appreciated that the plus sign (+) at the end of certain values means that the value could be larger, depending on whether the sequence numbers are being updated during the hand-off process.

0094The second monitoring example is with respect to the case where the communication scenario converts from a two-hop to a one-hop arrangement. Again, it is to be understood that a one-hop arrangement includes, for example, communication links between a PC, an Anchor LAC, and an LNS, while a two-hop arrangement includes, for example, communication links between a PC, a Serving LAC, an Anchor LAC, and an LNS. If the Anchor LAC receives indication that a two-hop PPP session is turned into a one-hop session (e.g., receiving a link layer handover message rather than a mL2TP CCRQ message), the Anchor LAC turns the four tuple state variable into a two tuple state variable and sets <i>Ss</i> = <i>Ss^S</i> and <i>Sr</i> = <i>Ss^L.</i> For example, assume the new Serving LAC has <i>Ss</i> = 13 and <i>Sr</i> = 5, the LNS has <i>Ss</i> = 7 and <i>Sr</i> = 10, and the Anchor LAC has <i>Ss^S =</i> 12, <i>Sr^S</i> = 4, <i>Ss^L</i> = 6, and <i>Sr^L</i> = 9. Then, after conversion from the two-hop to the one-hop arrangement, the Anchor LAC has <i>Ss</i> = 12 and <i>Sr</i> = 6 and the LNS has <i>Ss =</i> 7+ and <i>Sr =</i> 10+.

0095The third monitoring example is with respect to the case where the communication scenario converts from a two-hop to another two-hop arrangement, for example, as shown in <figref idref="f0008">FIG. 9</figref>. If the Anchor LAC receives a CCRQ message and the PPP session is already a two-hop session, then the Anchor LAC knows that there is a change of Serving LACs. The Anchor LAC then sets <i>Nr</i> = <i>Ss^L</i> and <i>Ns</i> = <i>Ss^S</i> in the CCRP message. The Anchor LAC also updates <i>Sr^S</i> to <i>Sr^S</i> = <i>Ss^L.</i> For example, assume the old Serving LAC has SS = 13 and Sr = 5, the LNS has Ss = 7 and Sr = 10, and the Anchor LAC has <i>Ss^S</i> = 12, <i>Sr^S</i> = 4, <i>Ss^L</i> = 6, and <i>Sr^L</i> = 9. Then, the Ancor LAC sets <i>Ns</i> = <i>Ss^S</i> and <i>Nr</i> = <i>Ss^L</i> in the CCRP message sent to the new Serving LAC. After the handover, the new Serving LAC has Ss = 12 and Sr = 6, the LNS has Ss = 7+ and Sr = 10+, and the Anchor LAS has <i>Ss^S</i> = 12, <i>Sr^S</i> = 4, <i>Ss^L</i> = 6+, and <i>Sr^L</i> = 9 +.

0096In addition, the Serving LAC implements a full receiver rather than a simple receiver, as referred to in the art. This requirement is to prevent the new Serving LAC from passing out-of-sequence or duplicate packets to upper layers when there is a change of Serving LAC during the lifetime of a PPP session.

0097Turning briefly to <figref idref="f0014">FIG. 16</figref>, a high level block diagram of a representative NAS is shown. An NAS is a stored-program-control based processor architecture and includes processor 650, memory 660 for storing program instructions and data, e.g., the above-mentioned connection tables, etc., and communications interface(s) 665 for 5 coupling to one or more communication facilities as represented by path 666.

0098The foregoing merely illustrates the principles of the invention and it will thus be appreciated that those skilled in the art will be able to devise numerous alternative arrangements which, although not explicitly described herein, embody the invention. For example, although the inventive concept was described in the context of a Serving ) NAS initiating the establishment of a multi-hop tunnel for incoming calls, the inventive concept is equally applicable to, e.g. the LNS initiating the establishment of a multi-hop sequence for outgoing calls. Such modifications are straightforward and will not be described herein as illustrated by <figref idref="f0015 f0016">FIGs. 17 - 18</figref>.