Optimum routing system

Background of the Invention

Field of the Invention

0001The present invention relates to the management of mobile terminal systems in a packet-switched data network, the computer user under Using services of virtual private networks over a packet-switched wireless High-speed data link with remote access to the Internet and provides for private intranets. In particular, the invention relates to to want to optimize the routing of mobile terminal systems Communication servers.

Description of the Prior technology

0002<figref idrefs="S126">1</figref> provides three business units and their equipment is carried out in collaboration Usually an Internet remote access for user computers <figref>2</figref> by user modems <figref>4</figref> provide. The user computer<figref>2</figref> and the modems <figref>4</figref> constitute end systems.

0003The first business entity is the telephone company (telco for eng. Telephone Company) containing the plain old telephone dialing (POTS for eng. plain old telephone system) or integrated services data network (ISDN for eng. integrated services data network) owns and operates. The Telco, the media in the form of the Public Switched Telephone Network (PSTN for eng. Public Switched Telephone Network)<figref>6</figref> ready about which bits (Or packets) between users and the other two business units flow can.

0004The second business entity is the Internet service provider (ISP for eng. internet service provider). The ISP uses and manages a or more Delivery Points (POPs for eng. points of presence)<figref>8th</figref> in its service area, to which end in Connect network service. An ISP typically aimed at any major local access area, in which the ISP expects to oblige customers, a POP one. Of the POP converts message traffic from the PSTN, which is run by the telco, in digital form so that it intranet backbone through the <figref>10</figref> transfer is owned by the ISP or leased from an intranet backbone provider like MCI, Inc. is. An ISP typically leases fractional or full T1 lines or fractional or full T3 lines from the telco for connectivity to the PSTN. The POPs and the ISP media data center<figref>14</figref> are about the Intranet backbone by a router <figref>12A</figref> connected with each other. The data center houses the web server, mail server, billing and registration server of the ISP and enables the ISP, Web content, and E-mail and web hosting services provide end-users. Future Value-added services by inserting additional Types of servers are added to the data center. The ISP also maintains rout <figref>12A</figref> for connection to the public Internet backbone <figref>20</figref>, In the current model for Remote access have end user service relationships with their telco and their ISP and receive usually separate bills from both. End users access by selecting the nearest POPs and Run a communication protocol known as the point-to-point protocol or PPP (for eng. Point-to-point protocol) of the working group to develop and coordination of Internet Protocols (IETF for eng. Internet Engineering Task Force) is known to the ISP and the ISP to the public Internet <figref>20</figref> to.

0005The third business entity is the private company that be for business reasons own private intranet <figref>18</figref> owns and through the router <figref>12B</figref> operates. Company employees can by performing POTS / ISDN calls (eg from home or on the road) to Remote Access Server <figref>16</figref> the company and running the IETF PPP protocol to the corporate network <figref>18</figref> access. End users pay for access to companies only the price for the connection to the remote access server <figref>16</figref> of the company. The ISP is not involved. The privately held company maintains the router<figref>12B</figref>. to an end user with either the corporate intranet <figref>18</figref> or the public Internet <figref>20</figref> or two to connect.

0006end pay the telco for the cost Telephone calls and the cost of a telephone line to their house. End users pay the ISP for access to the network and the services of ISPs. The present invention takes wireless service providers like Sprint PCS, etc. PrimeCo benefit and it is also Internet service providers like AOL, AT &amp; T Worldnet, etc. benefit.

0007nowadays offer Internet service provider end users internet access services, Webinhaltsdienste, e-mail services, Content hosting services and roaming to. Due to smaller profit margins and in the absence of a framework for carrying out a market segmentation based on features and price, Search ISPs to value-added services to improve profit margins. In the short term are Cab manufacturer be able to ISPs Solutions offer, so that they quicker access, networking virtual private networks (Which is the ability is public safe to use networks as private networks and intranets to connect) Roaming consortia Push techniques and quality of service able to offer. In the longer term also Voice over Internet and mobility offered. The ISPs will use these value-added services to the Straitjacket small profit margins to escape. Many of these value-added services fall into the category of network services and can only through the network infrastructure equipment Tobe offered. Others fall into the category of application services, which support the need of the network infrastructure, while other do not support need of the network infrastructure. Services like faster access, virtual private networking networks, Roaming, mobility, Language, quality of service and QoS-based require billing all enhanced network infrastructure. The invention here describes provides these improved services either directly ready or provides forks to allow these services as future improvements later added can be. Wireless service providers will be able a larger share to win the revenue stream. The ISP will be able to more services offer a better market segmentation.

0008Of the Prior art of interest, coupled to the inventive subject matter is related, is as follows: <patcit><text>EP 0697798</text></patcit>, Filed February 21, 1996 discloses an improvement to a wireless packet data communication system, by a subscriber, a mobile end system (M-ES) (<figref>205</figref>) used, the possibility is given, the interexchange carrier (IXC) (<figref>222</figref> or <figref>224</figref>) select, the while the data a particular communication session over those network paths transfers, for which the subscriber to pay the costs. The system allows it to the subscriber, a preferred network operator in an optional Preferred IXC field that a welcome message added of the end system is to specify. While the registration and authorization procedures, in a Preferred IXC field standard registration protocol messages added is an identifier that the preferred network operator corresponds to between a serving mobile data transit system (MD-IS) (<figref>220</figref>) And a home MD-IS (<figref>240</figref>) transfer. If the participants in the Preferred IXC field a preferred Network operator has specified, then this is preferred Network operator a higher priority granted as a designated preferred network operator, the selected is when the subscriber subscribes to the network services. Each MD-IS is with a new database (<figref>221</figref>. <figref>241</figref>) Provided, which network operator IDs in a corresponding border router address maps that are associated with the preferred network operator is to transfer data packets over to guide the participants from the preferred IXC. Accordingly allows System, data on a per-session basis both ways in the forward and the reverse direction via the the participants preferred network operator to send.

0009WHERE 96/21983 discloses a protocol dependent routing data packets between a mobile station of a packet radio network and an interlocutor (Host) that is connected to an external network. A data packet a foreign protocol (IPX) is a packet radio network, a second protocol (X.25) are used, as in a data packet according to the second Protocol encapsulated transferred. The transferring A packet radio network needs the protocol of the transferred foreign data packet therefore be understood, nor has it the contents of the data packet can interpret. A data packet network is another packet radio networks, data networks or the backbone network over between packet data networks a gateway node (GPRS GSN) connected, which the network-internal protocol (X.25) for dedicated packet network and the protocol of each network to another Networks used. When a data packet over a network gateway node is transferred from one network to another network, the data packet is in a package according to the protocol the new network encapsulated. If the encapsulated data packet arrives at a node, which the protocol of the encapsulated Data packet supported, the encapsulation is stripped away and the data packet is in accordance with the protocol of the data packet retransmitted.

SUMMARY OF THE INVENTION

0010On Method and apparatus according to the present invention are set out in the independent claims, to which the reader is now referred. Preferred features are in the dependent claims cited.

BRIEF DESCRIPTION OF THE DRAWINGS

0011The Invention is in the following description of preferred embodiments Forums referring todescribed exception to the following figures in detail, wherein:

0012<figref idrefs="S126">1</figref> on Configuration diagram of a known remote access architecture through a public telephone network is;

0013<figref idrefs="S127">2</figref> on Configuration diagram of a remote access architecture through a wireless packet switched data network according to the present Invention;

0014<figref idrefs="S128">3</figref> a Endsystemkonfiguration according to a embodiment of the present invention is illustrated;

0015<figref idrefs="S128">4</figref> a other Endsystemkonfiguration according to an embodiment of the present invention is illustrated;

0016<figref idrefs="S128">5</figref> a other Endsystemkonfiguration according to an embodiment of the present invention is illustrated;

0017<figref idrefs="S129">6</figref> on Configuration diagram of selected parts of the architecture of the network of <figref idrefs="S127">2</figref> is that a roaming scenario represents;

0018<figref idrefs="S130">7</figref> on Configuration diagram of a base station with local access points is;

0019<figref idrefs="S131">8th</figref> on Configuration diagram of a base station with remote access points is;

0020<figref idrefs="S132">9</figref> on Configuration diagram of a base station with remote access points is, some of which using a wireless trunk link are connected;

0021<figref idrefs="S133">10</figref> a diagram of a protocol stack for a local access point is;

0022<figref idrefs="S133">11</figref> a diagram of a protocol stack for a remote access point with a wireless trunk is;

0023<figref idrefs="S133">12</figref> a diagram of a protocol stack for a relay function in the base station to support is remote access points with wireless trunks;

0024<figref idrefs="S134">13</figref> a diagram of protocol stacks for implementing of the relay function is, in the <figref idrefs="S133">12</figref> illustrated is;

0025<figref idrefs="S134">14</figref> a diagram of protocol stacks for a relay function in the base station to support is of local access points;

0026<figref idrefs="S135">15</figref> a configuration diagram of selected parts the architecture of the network of <figref idrefs="S127">2</figref> is, having a first end system in the home network from the network to the home network can register and a second system, located in the home network from a foreign network using a home gateway function for a can register anchor, represents;

0027<figref idrefs="S136">16</figref> a configuration diagram of selected parts the architecture of the network of <figref idrefs="S127">2</figref> is, having a first end system in the home network from the network to the home network can register and a second system, located in the home network from a foreign network using a serving inter-working function for a can register anchor, represents;

0028<figref idrefs="S137">17</figref> a ladder diagram of the invitation and response messages To register in a home network from a foreign network and building, Authenticate and configure a data link is;

0029<figref idrefs="S138">18</figref> a configuration diagram of selected parts the architecture of the network of <figref idrefs="S127">2</figref> is, the registration requests and responses for registering a mobile unit is in a home network from the home network;

0030<figref idrefs="S139">19</figref> a configuration diagram of selected parts the architecture of the network of <figref idrefs="S127">2</figref> is, the registration requests and responses for registering a mobile unit in a home network is from a foreign network;

0031<figref idrefs="S140">20</figref> a configuration diagram of protocol stacks is that communications between an end system in a home network and an interworking function is in the home network, wherein the cell site local access points comprising;

0032<figref idrefs="S140">21</figref> a configuration diagram of protocol stacks is that communications between an end system in a home network and an interworking function is in the home network, wherein the cell site remote access points interconnected by a wireless trunk with a wireless Hub are connected;

0033<figref idrefs="S141">22</figref> a configuration diagram of protocol stacks is, the communications between a base station with a Roaming end system is coupled, and a home inter-working function represents;

0034<figref idrefs="S142">23</figref> a configuration diagram of protocol stacks is the communications of an end system in a home network by an interworking function in the home network is using an Internet service provider;

0035<figref idrefs="S142">24</figref> a configuration diagram of protocol stacks is, communications between an end system in a foreign network and a home registration server in a home network during the represents registration phase;

0036<figref idrefs="S143">25</figref> a processing flow diagram showing the Processing of billing data through the customer billing system represents;

0037<figref idrefs="S144">26</figref> and <figref idrefs="S145">27</figref> ladder diagrams are that the registration process for an end system in a home network respectively illustrate in a foreign network;

0038<figref idrefs="S146">28</figref> and <figref idrefs="S147">29</figref> Protocol stack diagrams are representing a Endsystemverbindung in a home network, where a PPP protocol in an interworking function of the home network ends or the PPP protocol terminates in an ISP or intranet;

0039<figref idrefs="S148">30</figref> and <figref idrefs="S149">31</figref> Protocol stack diagrams are representing a Endsystemverbindung in a foreign network, where a PPP protocol in an interworking function of the foreign network ends or the PPP protocol in an ISP or Intranet ends;

0040<figref idrefs="S150">32</figref>. <figref idrefs="S151">33</figref> and <figref idrefs="S152">34</figref> ladder diagrams are that a local handoff scenario, a micro-handoff scenario or a macro-indexing scenario illustrate;

0041<figref idrefs="S153">35</figref> a ladder diagram a global handoff scenario illustrates, the foreign registration server changes and wherein the home gateway function does not change;

0042<figref idrefs="S154">36</figref> a ladder diagram a global handoff scenario illustrates, with both the foreign registration server as also the home inter-working function switch;

0043<figref idrefs="S155">37</figref> and <figref idrefs="S155">38</figref> System configuration diagrams are possible which Compounds illustrate; and

0044<figref idrefs="S156">39</figref> to <figref idrefs="S157">42</figref> various Handoff scenarios illustrate.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

0045The present invention provides computer users with remote access to Internet and private intranets using services virtual private networks over a packet-switched wireless high-speed data link. These users are able to over a wireless connection to the public Internet, private Intranets and their Internet service provider access. The network supports roaming, this means the ability, on the Internet and private intranets using services virtual private networks from anywhere access, where the services by the present invention offered, are available. The network supports also handoffs, ie the ability, to change the user's terminal to the network, without the PPP link between the PPP client and the PPP server to Stören. The network is aimed at users from the horizontal Internet and intranet applications run. These applications include electronic mail, file transfer, browser-based WWW access and other commercial applications around the Internet are established. As the network is based on the IETF standards is, it is possible to Streaming media protocols like RTP, and conference protocols, such as H.323, via the perform network.

0046Other Internet remote access technologies that are already being used or are in various stages of deployment include: wire line dial access circuit switched based on POTS and ISDN, XDSL access, wireless Access based on GSM / CDMA / TDMA wireless packet-switched Access based on GSM / CDMA / TDMA, cable modems, and satellite-based Systems. However, the present invention provides low operational costs, Ease of maintenance, a comprehensive feature set, scalability, an ability the gentle power drop under heavy load conditions and support for improved Network services such as networking of virtual private networks, roaming, mobility and quality of service for each Benefit of users and service providers.

0047What Wireless service provider concerns that a personal communication system spectrum (PCS for eng. personal communications system) possess so enables the present invention They offer wireless packet switched data access services, which can compete with the services that traditional by Wire line telcos are provided that have the PSTN and operate. Wireless service provider may also decide itself to become Internet service provider, in which case they all own and operate network and for users end-to-end services provide.

0048What Internet service provider is concerned, the present invention allows them to bypass the telcos (provided they purchase or rent the spectrum) and offer users direct end-to-end services, perhaps while saving access charges for the telcos, which in future nor can grow as the internet grows to become even bigger, as it is now.

0049The present invention is flexible, so that they wireless service providers may benefit who are not internet service providers and end users only ISP, provide Internet or private intranet access. The Invention can also service providers who are found to end users provide wireless access and internet services. The invention can also service providers who are found wireless access deploy and Internet services, but also allow the wireless Section of the network for access to other ISPs or to private using intranets.

0050In <figref idrefs="S127">2</figref> join end systems <figref>32</figref> (Eg based on a win <figref>95</figref> Personal Computer) using external or internal modems to a wireless network <figref>30</figref> at. These modems allow end systems, medium access control or MAC frame (MAC for eng. Medium Access Control) via a airlink <figref>34</figref> to send and receive. External modems are about a wired or wireless connection connected to the PC. External modems are fixed and for example collocated with directional antennas, which are mounted on the roof, housed. External modems can under Using each of the following means with a user's PC are connected: 802.3, universal serial bus, parallel Port, infrared or even an ISM radio link. Internal modems are preferably PCMCIA cards for laptops and are in the Backplane laptop plugged. Using small omnidirectional antennas they send and receive MAC frames over the airlink.

0051The End system consists of the resources that the location itself the subscriber are. In the case of a fixed installation is the end system from a roof antenna, wireless devices, digital components and finally a desktop computer. It is likely that a participant to has desktop computers already, so the wireless system by Standard interfaces with the PC must be connected. <figref idrefs="S128">3</figref> to <figref idrefs="S128">5</figref> illustrate different options for typical fixed installations of the wireless system. Each of the options, outlined in these figures, has consequences which thus are connected and the installation costs, the operational costs and the practical installation to environmentally induced at installing rich, which is discussed below.

0052The Installation, in <figref idrefs="S128">3</figref> is shown, the present cheapest. In this configuration, only one antenna<figref>21</figref> arranged externally, and an RF cable <figref>22</figref> is connected to the radio <figref>23</figref> connected. Of the Installer, either the paid expert or the participants, just have the antenna <figref>21</figref> on the roof or on the side the building install and an inexpensive external cable <figref>22</figref> along the building an insertion site let down, normally through a hole in the corner of a window frame or through a hole in the wall in the vicinity of an inner floor. The radio <figref>23</figref> is externally from the desktop computer <figref>24</figref> a PCMCIA interface for PC <figref>24</figref>, Losses on long RF cable runs for users which are located at distant points from the access point, can be compensated in series bidirectional RF amplifiers. user near the access point may the additional Losses from long cable runs tolerate, as their propagation losses not as great as in Users are on the edge of the cell.

0053A other arrangement in <figref idrefs="S128">4</figref> illustrated is, involves the integration of radio electronics and the antenna in a common unit <figref>25</figref> on. The connection to the PC <figref>24</figref> would through a proprietary interface and PCMCIA. would benefit the device by a wall transformer <figref>27</figref> a multiple twisted double line <figref>26</figref> supplied are conveyed which both power and digital data. Difficulties in constructing an integrated device include weather resistance, warming and cooling, and server temperature extremes.

0054A Another arrangement consists of an outdoor antenna and an attic mounted subscriber unit. This reduces some of the requirements in terms of low temperature and weather resistance, but it has a cooling to be provided. The subscriber unit is then a Cables connected to the PC.

0055The last and most expensive means by which the digital data from the radio set to a computer or multiple computers to be transmitted, is the use of in an ISM band LANs, such as the WaveLANs, as shown in <figref idrefs="S128">5</figref> shown. The antenna <figref>21</figref> is located on the roof, as in the previous installation, and the radio device can, in the antenna or be placed somewhere else. combines an 802.3 connection the radio with an access point of the wireless LAN. Each of the remote computer equipment inside the house now has access to the wireless LAN <figref>28</figref>, Ideally, the antenna should <figref>29</figref> the access point of the wireless LANs have a directional antenna in building high is disposed and facing downwards, to a supply for the house provide while an RF spread outside the house is minimized. Placing the antenna in the attic raises various problems of the power of the unit on the top floor to cooling LAN radios on. In practice, it seems that a LAN antenna somewhere is disposed in the house, is acceptable as long as the lengths of the LAN access point antenna cables are short.

0056It there may be a need to provide roaming, the decide their laptop computers from their home coverage area take in a different coverage area. The laptop user must use a flat panel directional antenna, which to the access points is addressed. The alignment of the access point is to ensure quality of service crucial. As part of the laptop software provides an alignment indicator guide When aligning the antenna.

0057It it is provided that the antenna is about ½ or ¾ inch thick and an opening of about the same Size as the Laptop (8 ½ '' x 11 '') has. Some means for temporarily Attach the antenna plate on the back of the laptop, such as Velcro fasteners, are for the transport of the antenna appropriately. As soon as of laptop users at the staging point arrives where access is desired, the antenna can be either removed from the back of the laptop and for oriented the best performance or in areas with very strong Signals attached to be left on the laptop. The laptop antenna can with a biaxial orientation mechanism which the azimuth and the height the antenna changes, even are pivotally connected to the laptop. The antenna boards support 45 ° inclined Dual polarization with conical beam shapes to any propagation effects to eliminate, which may affect the signal quality. There also the beam shapes are conical with dual polarization, should the Location of the antenna on both sides does not change the signal quality.

0058A Long-Range wireless coverage is through base stations <figref>36</figref> provided. The supply range defined by the base stations <figref>36</figref> provided will depend on factors such as link budget, capacity and sufficiency. base stations are wireless service provider of personal communications services PCS (for eng. personal communication services) typically installed in cell sites. Base stations multiplex the Endsystemverkehr of its coverage area via a Wireline or microwave backhaul network <figref>38</figref> the mobile switching center (MSC) <figref>40</figref> of the system.

0059The Invention of the MAC and the (physical) PHY layer the air connection, and the type of the modem independently. The Architecture is also from the physical layer and topology the backhaul network <figref>38</figref> independently. The only requirements for the backhaul network are that it for routing Internet Protocol or IP packets between base stations and the MSC with adequate Power must be capable. At the mobile switching center<figref>40</figref> (MSC <figref>40</figref>) completed a packet data IMF or -Netzübergangsfunktion (IMF eng. inter-working function) <figref>52</figref> the wireless protocols for this network. An IP router <figref>42</figref> connects the MSC <figref>40</figref> with the public Internet <figref>44</figref>, Private intranets <figref>46</figref> or the Internet service providers <figref>46</figref>, Billing and directory server <figref>48</figref> in the MSC <figref>40</figref> save Accounting data and directory information. An element management server<figref>50</figref> managed the resources which the base stations, the IWFs and include accounting / directory servers.

0060Of the Billing server collects accounting data for user and sends the data to the billing system the service provider. The interface defined by the accounting server supports will send accounting information in the accounting log format the American grouping of management AMA (American Management Association), or any other suitable Invoice format on a Transport Control Protocol / Internet Protocol, or TCP / IP communication transport (for English. Control Protocol / Internet Protocol) to the billing system (the not shown in the figure).

0061The Network infrastructure provides end systems with a PPP or Point-to-point service. The network provides (1) a fixed wireless access with roaming (Log everywhere, where the wireless assistance available is for End systems and (2) low-rate and mobility handoffs ready. If an end system logs on to a network, it may either a fixed service (ie, stationary and without need of Handoff services) or a mobile service (ie the need Request of indexing services). An end system that is neither fixed yet specified mobile, is specifying the mobile service considered. The actual Registration of the end system is the result of a negotiation with a home registration server on the basis of the requested Service class, the class of service, the user of the end system subscribed, and the service features that are available on the net.

0062If the end system a fixed service registration (ie without indexing services request) and negotiates the end system is located in the home network, is an IWF (interworking function) implemented in the base station to the traffic between the end user and a communications server such as a PPP server (That is, with the point to be connected, for example, an ISP PPP server or a PPP server of the corporate intranet or a PPP server, which is operated by the wireless service provider to provide customers direct access to the public to gain Internet) to convey. It is expected that perhaps 80% of message traffic of this category be why this architecture, the IMF processing at the base stations distributed and message traffic obstruction in a central Mobile switching center avoids.

0063If the end system requests mobile service (from a home network or a foreign network) or if the end system is roaming service (Ie a service from the home network through a foreign network) requests, two IMF are established: a serving IWF, which normally is set in the base station of the network to which the connected end system (either the home network or a foreign network) and a home IWF, normally in the mobile switching center MSC of the home network is set up. Because, it is expected that this situation only about 20% of their communications involving, is the message traffic congestion around the mobile switching center minimized. The serving IWF and the wireless hub to the same location be housed in the same computer set or they may even be programmed in the same computer, so that no tunnel under Using a protocol XTunnnel established between the wireless hub and the serving IWF need be.

0064Based on the available Service features and the requested service type and quality of service can a serving IWF in a foreign network alternatively from service features selected in the foreign MSC will. Generally, the home IWF becomes an anchor point, the while the communication session is not changed, while the serving IWF may change if the end system is sufficiently emotional.

0065The Base station includes an access hub and at least one access point (He was deposed or housed collocated with the access hub) on. Normally, the access hub provides multiple access points. Although the end system according to the teachings this invention to an access point by a wire or a Cable can be connected, the end system in a preferred embodiment by a wireless "air link" to the access point connected, in which case the access hub useful as wireless hub is called. It goes without saying that, although the access hub all description through wireless as " Hub designated " is an end system that by using a wire or a cable an access point is coupled to an access hub, an equivalent implementation is considered and by the term "access hub" is.

0066In the invention comprises a terminal system a Endbenutzerregistrierungsagenten (For example, a software that his on a computer of the end system, Modems or two runs) on the one with an access point and the access point with wireless hub communicates. The wireless hub includes a proxy registration agent (Eg, a software running on a processor in the wireless hub) which of as a proxy for the Endbenutzerregistrierungsagenten acts. Similar concepts, for example, used in the Mobile-IP standard suggested by the IETF are commonly referred to as a foreign agent (FA). Out this reason, the proxy registration agent the present invention as a foreign agent designated, and aspects the foreign agent of the present invention, which by itself foreign different agents of the Mobile IP are as they during this Description will be set forth.

0067at Using the proxy registration agent (ie, the foreign agent) in a base station is the user registration agent of End system adapted to detect a connection point to the grid and at a registration server in the MSC (mobile switching center) register of the home network can be. The home registration server ensures availability each of the plurality of network interworking function modules (IMF) in the network (actually software modules that both processors run) fixed in the MSC and the wireless hub and assigns registered end system IWF (s) to. For each registered end system is a tunnel (using the Xtunnel protocol) between the wireless hub in the base station and an interworking function (IMF) generated in the mobile switching center (MSC), said transported tunnel PPP frames between the end system and the IWF.

0068As used herein, the Xtunnel protocol is a protocol that a In-sequence transport of PPP data frames provides with flow control. This protocol can be standard IP networks or Point-to-point networks or over switched networks like ATM data networks or frame relay data networks to run. Such networks may on T1 or T3 connections based, or they can on radio links, whether agricultural or space-based, based. The Xtunnel protocol can by adapting algorithms from the Layer 2 Tunneling Protocol L2TP (For English. Layer 2 tunneling protocol) are formed. In networks on based compounds found in which data packets lost can be, may be a desirable option a rebroadcast feature.

0069Of the PPP peer (ie, a communication server) of the end system can in the IMF or a corporate intranet or an ISP network sit. If the PPP peer sitting in the IMF, is an end system with a direct internet access provided. If the PPP peer sitting in an Intranet or ISP, is an end system with an intranet access or access to an ISP provided. To support an intranet or ISP access, used the IMF, the layer two tunneling protocol (L2TP) to connect to the intranet or ISP PPP server. From the viewpoint the intranet or ISP PPP server sees the IMF as a Netzugangsserver (NAS for eng. network access server) from. The PPP traffic between the end system and the IMF will be forwarded by the foreign agent in the base station.

0070In the reverse direction (Uplink) are PPP frames, which propagate from the end system to the IWF, over the MAC and air link sent to the base station. The base station will be the frame using the Xtunnel Protocol to the IMF in the MSC on. The IMF puts a PPP server for processing. To access the Internet , the PPP server be in the same machine as the IMF. For an ISP or intranet access is the PPP server in a private network, and the IMF used the layer two tunneling protocol (L2TP) to connect with it.

0071In the forward direction (Downlink) are PPP frames from the PPP server by the IMF using the Xtunnel Protocol forwarded to the base station. The base station de-tunnels downlink frame and passes them on the air connection to the end system continue where it through the PPP layer the end system are processed.

0072The support mobility includes support of handoffs. The MAC layer assists the mobility management software in the base station and the terminal system in the effective implementation of Handoffs. are handoffs from the PPP peer entities and the L2TP tunnel handled transparently. if an end system moves from one base station to another, a new one is XTunnel between the new base station and the original IMF creates. The old XTunnel from the old base station is deleted. PPP frame through the new way transparent.

0073The support network Roaming (ie, when the end user through a foreign wireless service provider with its home wireless service provider sets in conjunction). By using this feature, end systems are able to migrate from the home network to a foreign network and still supplied to whoeverto, provided of course that the foreign wireless service provider and the home wireless service provider the end system have a service agreement.

0074In <figref idrefs="S129">6</figref> Has a roaming end system <figref>60</figref> go to a location, to which a foreign wireless service provider <figref>62</figref> the supply provides. The roaming end system<figref>60</figref> but has a subscriber relationship with the home wireless service provider <figref>70</figref>, In the present invention, the home wireless service provider <figref>70</figref> on contractual relationship with the foreign wireless service provider <figref>62</figref>To provide access services. Therefore, the roaming end system sets <figref>60</figref> via the airlink with the base station <figref>64</figref> the foreign wireless service provider <figref>62</figref> in Connection. Then, data from the roaming end system<figref>60</figref> by the base station <figref>64</figref> by the serving IWF <figref>66</figref> of foreign wireless service provider <figref>62</figref> the home IWF <figref>72</figref> of Home wireless service provider <figref>70</figref> or possibly by the home IWF <figref>72</figref> the home wireless service provider <figref>70</figref> to the Internet service provider <figref>74</figref> forwarded.

0075A services border Provider interface, called I-interface is for communications over Drahtlosdiensteanbieter- or WSP limits (WSP for eng. wireless service provider) used to support roaming. This interface is used to authenticate, register and Transporting the PPP frames of the end system between the foreign WSP and the home WSP used.

0076PPP frame in the uplink and in the downlink direction propagate through the home wireless service provider (WSP) of the end system continued. Alternatively run PPP frames from foreign WSP directly for determining network. The base station in a foreign WSP is the connection point of the end system in the foreign network. This base station sends (and receives) PPP frames to (and from) a serving IWF in the mobile switching center the foreign WSP. The serving IWF continues using a layer two tunnel over the I interface with the home IWF in connection to the PPP frame to transport the end system in both directions. The serving IMF in the foreign WSP collects accounting data for auditing. The Home IWF in the home WSP collects accounting data for billing.

0077The serving IWF in the foreign WSP can with the base station in the same linked system be, whereby the necessity of the X-tunnel is eliminated.

0078During the Registration phase, a registration server in the foreign WSP the identity the home network of the host-end system fixed. Using this Information communicated to the foreign registration server to the Home registration server to authenticate the end system and to register. These registration messages flow over the I-interface. Once the end system has been authenticated and registered, using the Xtunnel Protocol a layer two tunnel between the base station and the serving IMF produced, and another layer two tunnel is formed between the serving IWF and the home IWF generates via the I-Xtunnel. The home IWF continues as before using the L2TPs (Layer 2 Tunnel Protocol) with the PPP partner. during handoffs remains fixed the location of the home IWF and the L2TP tunnel. If the end system from a base station to another base station is moved, a new tunnel between the new base station and the serving IWF generates, and the old tunnel between the old Base station and the serving IWF is deleted. If the end system moved far enough so that a new serving IWF is needed A new I-Xtunnel between the serving IWF and the home IWF generated. The old tunnel between the old serving IWF and the home IWF is deleted.

0079to support supports the roaming the interface I authentication, registration and data transport services across wireless service provider boundaries. Authentication and registration services are using of the IETF Radius protocol supported. Data transport services for transferring PPP frame over a layer two tunnel are supported by using the I-XTunnel protocol. This Protocol is based on the IETF L2TP protocol.

0080As used in this specification, the term home IWF refers to the IWF in the home network of the end system. The term serving IWF refers to the IWF in the foreign network, which end system that temporarily provided. Similar the term home registration server to the registration server in the home network of the terminal system, and the term foreign registration server refers to the registration server in the foreign network, through which can register the end system as it travels.

0081The support network both a fixed and a dynamic IP address assignment for end systems. There are two types of IP addresses that are to be considered. The first is the identity the ENDSYSsystem in its home network. This may be a structured his username in the format user @ domain. This differs from the home IP address, which is used in Mobile IP. The second address is the IP address that the end system via the PPP IPC protocol address is assigned. The domain subfield home address is used to the home domain of the user identify, and is a fully qualified domain name. The user sub-field of the home address is used to the user in the home domain to identify. The user name is on the end system and in the Subscriber database stored at the MSC, and it is the user assigned when he subscribed to the service. The domain part of the field User name during Roaming used to roaming relationships and the home registration server for the purpose of registration and identify authentication. Instead of the structured user name can be used other unique identifier to the home network and the identity of the user the user's home network to identify. This identifier is sent in the registration request by the end system.

0082The PPP IPCP is used to negotiate the IP address for the end system. By using the IP Configuration Protocol IPCP is the end system capable of a fixed or dynamic IP address negotiate.

0083Although the use of the structured user name field and the non-use an IP home address is a phenomenon which the present invention over a known Mobile IP features, the network can be improved To support end systems, which have a user name and only one non-zero home IP address have if the Mobile IP and its use in conjunction with PPP end systems consistently becomes. The PPP server can be configured by the service provider so that he during IPCP address assignment phase assigns IP addresses, which is equal to are like the home IP address of the end system. In this case, the home address and the assigned by the IPCP IP address identical.

0084In <figref idrefs="S130">7</figref> form the base station <figref>64</figref> and air links from end systems a wireless subnet <figref>80</figref>That the air links for end-user access, at least one base station (for example station <figref>64</figref>) And at least a backhaul network (eg <figref>38</figref> from <figref idrefs="S127">2</figref>) from the base station to the MSC <figref>40</figref> (<figref idrefs="S127">2</figref>) Has. The architecture of the wireless subnetwork, for example, a Base station with three sectors, the following logical functions on: <ul><li>1 access point function. access points<figref>82</figref> perform MAC layer bridging and MAC layer association and -Dissoziationsprozeduren by. An access point has a Processor (preferably in the form of a custom Application Specific integrated circuit ASIC), a connection to a wireless Hub (preferably in the form of an Ethernet connection on a map or built into the ASIC), a connection to an antenna (preferably in the form of a card with a data modulator / demodulator and a Transmitter-receiver) and the antenna to which the end system is coupled. processor performs Software, a data bridging function and various other functions in support of registration and Mobility handoffs, as further herein is described to execute. See discussion in relation to <figref idrefs="S133">10</figref>. <figref idrefs="S133">11</figref> and <figref idrefs="S134">14</figref>, access points (APs for eng. access points) take MAC layer frames from the air link and they take, and vice versa to a wireless hub. The MAC layer association and - Dissoziationsprozeduren be used by the AP to a list of end system MAC addresses in their MAC address filter table to lead. An AP may be a MAC layer bridging only perform for end systems whose MAC addresses are present in the table. An access point and its associated wireless Hub are normally housed collocated. In its simplest Form is only one access point port into a wireless hub. If the APs and the wireless hub collocated in the same cell site housed are able they an IEEE 802.3 connection are connected together. Sometimes are access points deducted from the wireless hub and arranged a Wide area connection, such as a wired T1 trunk or also a wireless trunk connected. For cells with multiple sectors Multiple access points are (ie one per sector) used.</li><li>2. Drahtloshubfunktion. The wireless hub<figref>84</figref> leads Fremdagent- or FA procedures, backhaul load balancing (Eg multiple T1) backhaul network connections and Xtunnel procedures through. If support for Quality of Service (QOS) is present, the wireless hub implements the support for QOS by perform the Xtunnel Protocol on backhaul with different QOS attributes. In a cell site with multiple sectors is a single normally Drahtloshubfunktion shared by multiple access points used. A wireless hub includes a processor, a compound to one or more access points (preferably in the form of an Ethernet connection, on a card or in an ASIC built in) and a connection to a backhaul line on. The backhaul line is typically a T1 or T3 communicationsline in the mobile switching center the wireless service provider ends. The connection to the backhaul line formatted data in a preferred format, for example, an Ethernet format, a frame relay format or an ATM format. The processor of the wireless hub carries a Software, a data bridging and various other functions as described herein to support. Please refer discussion in relation to <figref idrefs="S133">12</figref>, <figref idrefs="S134">13</figref> and <figref idrefs="S134">14</figref>,</li></ul>

0085The Base station design supports the following types of Cell architectures: <ul><li>1. Architecture with local APs. In an architecture with local access points APs have a size (Typically> = 2 km) reach. They are in the cell site collocated with the wireless hub accommodated (<figref idrefs="S128">4</figref>). access points can using an IEEE 802.3 network with the wireless hub be connected, or they can directly into the backplane be plugged of the wireless hub, or using any other mechanism (eg, universal serial bus, printer port, Infrared, etc.) to be connected to the wireless hub. It is assumed, that the first alternative the rest of this discussion is used. The cell site may omnidirectional or by adding more access points and sectored antennas to a wireless Hub be sectored.</li><li>2. Architecture with remote APs. In an architecture with remote APs have access points normally a very small Range, usually about 1 km radius, on. They are from the wireless hub (either externally or inside) deposed arranged. A T1 or a wireless trunk preferably links Access points to the cell site where the wireless hub located is. From cell site typically is a wireline backhaul or microwave range for connection to the IWF in the MSC used. If a wireless trunking between the remote AP and the wireless hub is used, be omnidirectional or sectored radios for the Trunking used. The devices for the Trunking to remote access points are preferably collocated housed with the wireless hub and may be prepared using a IEEE 802.3 network be associated with them, or they can directly in the backplane the wireless hub to be infected. These devices are using the term trunk AP designated.</li><li>3. Architecture with mixed APs. In a mixed architecture the wireless subnet must remote and local access points support. Remote access points may for hole filling are added and other capacity reasons. As already mentioned, can T1 or wireless trunks are used to the remote AP to connect to the wireless hub.</li></ul>

0086<figref idrefs="S155">37</figref> and <figref idrefs="S155">38</figref> are System configuration diagrams, which illustrate possible connections. For case (I) is the IMF1 the anchor IWF and serves as the home agent, while the WH1 serving as the foreign agent. A Xtunnel is between the WH1 and the IWF1 used, and the layer-2-Tunnelprotokoll- or L2TP tunnel is used between the IMF1 and the PPP server. For case (Ii) the WH and the serving IWF are housed collocated. The IMF1 is the anchor IWF and the serving IWF IWF2 serves as the foreign agent. An I-Xtunnel is used between the IMF and IWF2, and an L2TP tunnel is used between IWF1 and the PPP server. For case (Iii) is the serving IWF IWF3, and the anchor IWF is IMF1. A Xtunnel used between VP3 and IWF3, an I-Xtunnel is between IWF3 and IMF1 used and an L2TP tunnel is between IMF1 and the PPP server.

0087<figref idrefs="S155">38</figref> illustrates the addition of a wireless section (Trunk AP), the trunk AP housed collocated with the WH can be. For this case, In addition to the three options described above, the following possibilities occurrence. For Case (i) is the trunk AP1 the foreign agent, and IMF1 is the anchor IWF. A Xtunnel is used between the trunk AP1 and the anchor IWF and an L2TP tunnel is between the anchor IWF and the PPP server used. For Case (ii) is the serving IWF2 the foreign agent. A Xtunnel is used between the trunk and the AP2 IWF2, an I-XTunnel is used between the IWF2 and Anchor IMF1, and an L2TP tunnel is used between the anchor IWF and the PPP server. For case (iii) is the serving IMF the foreign agent. A Xtunnel is between the trunk and AP3 the IWF3 used, an I-XTunnel is between IWF3 and the anchor IWF1 used, and a L2TP tunnel is between the anchor IWF1 and the PPP server.

0088<figref idrefs="S156">39</figref> to <figref idrefs="S157">42</figref> illustrate several handoff scenarios, as well as various compounds between the elements of the system.

0089<figref idrefs="S131">8th</figref> provides a cell is with three sectors using local APs only. The access points and the wireless hub are co-located in the base station housed and connected to each other with 802.3 links.

0090<figref idrefs="S132">9</figref> provides the architecture with remote access points <figref>82</figref> represents, the wireless using Trunks <figref>86</figref> to the wireless stroke <figref>84</figref> are connected. Each trunk access point in the A base station, to a wireless point-to-multi-point radio link remote micro access points (R-AP in the figure) ready. The remote Access points provide an air link service available to end-systems. The wireless hub and the trunk access points are co-located in housed the Bass Station and about 802.3 compounds together connected. This figure also remote access points<figref>82R</figref> represents, the via point-to-point T1 links are connected to the wireless hub. are in this scenario no trunk APs required.

0091to support all cell architectures described above and the various Types of access points that could use each cell observed, the network architecture the following rules: <ul><li>1. Access Points function as MAC layer bridges. perform Remote Access Points a MAC bridging between the air link to the end systems and the wireless or T1 trunk to the Cell site through. Local access points perform MAC bridging between the air link to the end systems and the wireless hub through.</li><li>2. Trunk access points also function as MAC layer bridges. they to lead a MAC bridging between the trunk (which to the access points is) and the wireless Stroke by.</li><li>3. The wireless hub is accommodated with all collocated MAC bridges (Ie local access points or trunk access points) connected, wherein initially an 802.3 connection is used.</li></ul>

0092If local access points or remote access points with T1 trunks be used, are also The following rules follow: <ul><li>1. Local access points be accommodated collocated with the wireless hub and 802.3 use of point-to-point links or a shared used 802.3 network associated with it. Remote access points are using point-to-point T1 trunks with the wireless hub connected.</li><li>2. The sectorization is by adding access points with sectored antennas to the cell site support.</li><li>3. For each access point, which is connected to the wireless hub are, there is a foreign agent running in the wireless hub, the participates in end system registration. MAC layer association procedures be used to determine the MAC address filter tables of the access points to keep up to date and the MAC layer bridging efficiently perform. The wireless hub participates in MAC association functions, so that only valid MAC addresses to MAC address filter tables added to the access points will.</li><li>4. The wireless hub forwards frames from the access points under Using the XTunnel Protocol MSC IWF and vice versa, provided that the IMF is not with the wireless hub housed collocated. The MAC address filter table is used to filter out those point-point MAC communication data frame, their MAC addresses are not present in the table. Send The APs MAC broadcast frames and MAC frames associated with the Endsystemregistrierungsfunktion are always regardless of the contents of the MAC address filter table further.</li><li>5. Local access points use ARP to resolve MAC addresses to route IP traffic to the wireless hub. Vice versa also used the wireless hub, the ARP to IP packets to access points to conduct. The UDP / IP is used for network management of access points used.</li><li>6. Remote access points connected via T1, do not use ARP since the connection is a point-to-point connection is.</li><li>7. Support for handoffs is done using the MAC layer.</li></ul>

0093In a cell architecture using wireless trunks and trunk APs, the following rules are followed <ul><li>1. Trunk access points be co-located with the wireless hub and 802.3 use of point-to-point connections, or other suitable Means connected thereto.</li><li>2. The sectorization wireless Trunks is by adding Trunk access points with sectored antennas to the cell site supported.</li><li>3. handoffs over Backhaul sectors carried out using the foreign agent in the wireless hub. For each backhaul sector, there is a foreign agent of the wireless Hub runs.</li><li>4. The trunk APs do not need to the MAC layer end system association participate and -Weiterschaltungsprozeduren. Your MAC address filter tables be dynamically programmed by the wireless hub when end systems to register with the network. The MAC address filter table is used to filter out point-point communication MAC frame. Containing registration packets MAC-round end frames or MAC frames, are always allowed through.</li><li>5. Trunk APs use ARP to resolve MAC addresses to the to direct IP traffic to the wireless hub. Conversely used the wireless hub, the ARP to route IP packets to trunk APs. The UDP / IP is used for network management of trunk APs.</li><li>6. take place in a single wireless trunk sector MAC Association and -Weiterschaltungen from one access point to another under Using the MAC layer with the support of foreign agents wireless hub. associate By using these MAC layer procedures End systems with access points. If end systems from a move access point to another access point, use the Access points a MAC handoff protocol to their MAC address filter tables to update. The wireless hub at the cell site supports Access points in the implementation this function. This support comprises forwarding of MAC layer handoff message (as Access Points are unable directly above the MAC layer to communicate with each other) and authenticating the end system for MAC layer registration and -Weiterschaltung and to update the MAC address filter tables the access points.</li><li>7. The foreign agent for a wireless trunk sector is for the forwarding of frames from its trunk AP to the MSC and vice versa using the protocol Xtunnel responsible. Accordingly, interested the foreign agent for a Trunk AP not for the whereabouts of the end system in terms of access points within this wireless trunk sector. In the downlink direction he received only the context of Mobile IP tunnel to the appropriate trunk AP which a MAC layer bridging used to send the frames to all remote access points to these backhaul sector are connected. The access points consult their MAC address filter tables and forward the MAC frames either via the access network further or delete the MAC frame. As already mentioned, be the MAC address filter tables using MAC layer association and -Weiterschaltungsprozeduren Kept up to date. In the uplink direction MAC frames are forwarded by the access points to the backhaul bridge, which they using the 802.3 connection to the foreign Agents transmitted in the wireless hub.</li><li>8. The ARP is not to send or receive IP packets used to the remote access points. The trunk access points set the MAC address of the wireless hub using BOOTP procedures laid. Conversely, the wireless hub with the MAC address configure remote access points. The UDP / IP is used to Network management of access points and for end system association and -Weiterschaltungsnachrichten Used.</li></ul>

0094IEEE 802.3 Srecken the cell site can faster connections be replaced.

0095<figref idrefs="S133">10</figref> provides the protocol stack for a local access point is. At the base of the stack is the physical Layer PHY. The physical layer PHY carries data to and from an end system over the Air using radio waves as an example.

0096If received from an end system, the AP receives data from the physical Layer and unpacks from the MAC frames (the MAC layer). The Endsystemdatenrahmen then again in a physical Ethernet layer format (IEEE 802.3 format), using it on Ethernet connection be sent to the wireless hub. If the AP-processor data the wireless hub via its Ethernet link (ie, the physical layer), the Data to be transmitted to an end system are receiving, packed the AP data in a medium access control or MAC format, and sends the MAC layer data to its modulator, so that they transmitted to the end system using the PHY layer will.

0097In <figref idrefs="S133">11</figref> are the MAC and the PHY layer to / from the end system from <figref idrefs="S133">10</figref> by a MAC and a PHY for the trunk to the cell site for a remote access point replaced. Specifically, for a T1 trunk preferably higher Datenübertragungssteuerungs- or HDLC protocol (For English. high level data link control protocol) used on the T1.

0098<figref idrefs="S133">12</figref> shows the protocol stack for the wireless hub of the Backhaul line and the trunk to the remote access point interconnects. The trunk to the remote access points is only to support remote access points required (In contrast to the Ethernet, which is coupled to access points). The MAC and PHY layer for the wireless trunk to the remote APs provide a point-to-multi-point connection prepared so that a trunk can be used to remote host APs to communicate in the same sector.

0099Of the wireless hub on the trunk to the remote APs and the Backhaul line (eg, T1 or T3) to the mobile switching center (MSC) of the network together.

0100Of the Protocol stack in the wireless hub implements MAC and PHY layers MSC for what an IP layer (Internet Protocol) is implemented, what a universal Datagrammprotokoll- or UDP layer (for English. Universal Datagram Protocol) implemented network management is (collectively known as UDP / IP are referred to), what a Xtunnel protocol is implemented. The Xtunnel protocol is a new format that Aspects of mobility (Such as in mobile IP) and aspects of the layer 2 tunneling Protocol (L2TP) includes. The XTunnel protocol is used by the wireless Hub with the MSC and between interworking functions (IMF) in different networks or the same network to communicate.

0101In <figref idrefs="S134">13</figref> is the protocol stack for the relay function in the Base station to support represented by remote access points. The relay function has an interface to the backhaul line (depicted as the wireless hub) and an interface to the remote AP (depicted as a trunk AP) on. From the viewpoint of the wireless hub behaves the trunk AP (depicted in <figref idrefs="S134">13</figref>) actually as an AP, the in <figref idrefs="S133">10</figref> illustrated is. Preferably, the base station protocol stacks are in a wireless hub and a trunk AP with an Ethernet in between divided up. In a wireless trunk with N sectors there are N wireless Trunk APs in the cell site and a wireless hub.

0102In <figref idrefs="S134">14</figref> is the base station protocol stack for a cell architecture shown, which uses a local AP. The relay function has (shown an interface with the backhaul line as the wireless hub) and an air link interface with the End system (depicted as an AP) on. From the viewpoint of the wireless hubs behaves the AP (shown in <figref idrefs="S133">11</figref> and <figref idrefs="S134">14</figref>) actually like the trunk AP, the in <figref idrefs="S133">11</figref> illustrated is. Preferably, the base station protocol stacks are in a wireless hub and a trunk AP with an Ethernet in between divided up. In a cell with N sectors there are N access points and a single wireless hub.

0103The Backhaul network from the base station to the MSC has the following attributes: <ul><li>1. The network is to route IP datagrams a position between the base station and the MSC.</li><li>2. The network is secure. It is not a public network. On the Web only traffic from reliable Knots allowed, since the network not only for transporting Endsystemverkehr, but also for transporting authentication, billing, Registration and management traffic is used.</li><li>3. The network has the necessary performance characteristics on.</li><li>4. The base stations support IP over Ethernet links.</li></ul>

0104In a typical application is the service provider for installation and maintaining the backhaul network, on which the operating means are installed, responsible.

0105The support base stations the following backhaul interfaces for communicating with the MSC: <ul><li>1. The base stations support IP over Fractional PPP with HDLC links using point-to-point T1 or T3 connections.</li><li>2. Base stations support IP over frame relay under Using T1 or fractional T3 links.</li><li>3. The base stations support IP over AAL5 / ATM using T1 or fractional T3 links.</li></ul>

0106There All the mentioned above Interfaces on IETF Standardkapselungen based, can commercial Routers are used in the MSC to the physical connections the backhaul network to finish. Higher layers are passed the various servers and other processors and processed.

0107Endsystemregistrierungsprozeduren on MAC layer are supported. Below Endsystemregistrierungsprozeduren be on the MAC layer ignored, except they affect the layers above.

0108end systems can for register a service on their home network or from a foreign network leave. In both scenarios, the end system uses a foreign Agent (FA) in the base station, a connection point to the grid to identify and to register. In the former case is the FA in the home network of the end system. In the latter case, the FA is in a foreign network. In any case, the power used in an IWF unchangeable home network the end system as an anchor point (ie while throughout the session despite mobility). PPP frames to and from the end system are propagated via the FA in the base station the IMF continued in the home network. If the end system is at home, is the home IWF using the Xtunnel-Prototocol directly to the base station connected. It should be noted, that the home IWF are linked to the base station in the same way can. If the end system is roaming, a serving IWF in the foreign network is a I interface connected to the home IWF. The serving IWF forwards frames between the base station and the home IWF on. It should be noted, that the serving IWF to the base station in the same associated manner can be. from the home IWF, data using the L2TP protocol on a PPP server that sit in the same IMF can, or sent to a separate server. The separate server can a private network operator (eg ISP or proprietary intranet) belong and operated by this which the wireless service provider is different. For the duration of the session is the location of the home IWF and the PPP server firmly. If the end system during the emotional connection, it must be with a new foreign agent re-register. There are, however, continue the same home IWF and the same PPP server uses. A new Xtunnel is between the new FA and the IMF created, and the old Xtunnel between the old foreign agent and the IWF is destroyed.

0109<figref idrefs="S135">15</figref> , this network configuration for two end systems A and B represent the two wireless home network of the wireless service provider A (WSP-A). An end system is registered by the wireless home network, and the other by a wireless external network. The home IWF in WSP-A serves as the anchor point for both end systems. For both end systems are forwarded data to home IWF. The Home IWF sets to an Internet service provider PPP server in conjunction which the ISP-A belongs.

0110in this connection it is assumed that both end systems a subscription with the same ISP have. If this were not the case, then the home IWF would so represented, that they would also be connected to another ISP.

0111Within the network of a wireless service provider, data between transmitted base stations and the IMF using the Xtunnel protocol. Data between the IWF and the PPP server are using the Layer 2 Tunnel Protocol (L2TP) transferred. Data between the serving IWF and the home IWF are using the I-Xtunnel protocol transmitted.

0112In a simple scenario can for a user in its home network, requesting a fixed service, the home IWF function in the base station are triggered dynamically. also , the serving IWF function for one Guest users are activated in the base station.

0113Always to use an IWF in the home network, has its advantages and disadvantages. An obvious advantage is simplicity. One disadvantage is that constantly Data to and from a possibly remote home IWF must be forwarded. The alternative is to all to send the necessary information to the serving IWF, thus they contact the ISP / intranet of the end system in conjunction can, and thus the serving IWF billing information in Fast real-time back the billing server can send the home network. This functionality is complex to implement, but more efficient because it reduces the need to Data about Tell potentially long distances from the foreign network to the home network to have to.

0114one For example, consider the case of a user of Chicago emigrated to Hong Kong. If the user's home network in Chicago and the user is using a wireless service provider can register in Hong Kong, then the home IWF is in the first configuration in Chicago Anchor Point, and all data must are managed directly from Hong Kong to Chicago and vice versa. The Home IWF in Chicago will contact the ISP of the user in Chicago in connection. In the second configuration the Endsystembenutzer is an ISP assigned in Hong Kong. Accordingly, the data need not constantly between Chicago and Hong Kong back and be derived. In the second Configuration is the serving IWF as the anchor and changes for the Duration of the session never, even if the end system moves. Of the However, location of the FAs can be due to a Endsystembewegung Change in Hong Kong.

0115<figref idrefs="S136">16</figref> represents the second configuration. In this Figure is WSP-A's home network for the end system A and B. The end system A can be from its home network Register using its home IWF as an anchor and continues using the ISP PPP server with its ISP-A in Connection. The end system B can register from the foreign network of WSP-B and uses a serving IWF, which as the anchor point is used and the end system using the ISP PPP server to an ISP connects. In this configuration have to data for the end system B not from the foreign network to the home network, and vice versa to get redirected.

0116In order to this configuration to work, it must not only roaming agreements give between foreign and native wireless service providers, but it must also agreements between the foreign wireless service provider and the Internet service provider of the end system directly or through be a mediator. In the example set out above does not have to only the wireless service provider in Hong Kong a business agreement have with the wireless service provider in Chicago, but the WSP Hong Kong also has a business agreement with the Chicago ISP user and access to Chicago ISP PPP server in Hong Kong or a business agreement have another local ISP in Hong Kong, a business agreement roaming has with the Chicago ISP user. In addition, the WSP in Hong Kong must be able to identify these roaming relationships dynamically, a user authentication and -Billing perform and establish the appropriate tunnel.

0117It is difficult for these companies that are on the Internet infrastructure business, suitable standards in the IETF work out for all of these scenarios. Accordingly, a preferred embodiment for the present invention, the simpler, potentially less effective to implement configuration, the IWF in the home network always is used as the anchor point. In the presence of a suitable Industry standardization of protocols for Internet roaming should the second configuration as equivalent or alternative embodiment, to be viewed as.

0118On End system must be registered with the wireless network before it can start PPP and send and receive data. The end system passes through First the FA investigation and -Registrierungsphasen. These phases authenticate and register the end system for the wireless service provider. Once these phases over are, the end system starts PPP. This includes the PPP connection establishment phase, the PPP authentication phase and the PPP network control protocol phase. As soon as these phases over are, the end system IP packets is capable of using the to send and receive PPPs.

0119The following discussion assumes that the end system is roaming and register from a foreign network leaves. While the FA investigation stage awaits the end system (through its user registration agent) an announcement the foreign agent or she gets in this. The user registration agent used Advertisement messages sent by a nearby foreign agent, the identity the FAs to identify, and to register. During this phase, the user registration agent chooses the end system a FA, and outputs a registration request to him. The FA acting as a proxy registration agent shall transmit, the registration request to its registration server (the Registration server in the foreign WSP). The registration server uses the User name from the request of the user registration agent, transmitted to the home network of the end system to determine and the registration request for authentication to a registration server in home network. Upon receipt of the registration request, the has been forwarded by the foreign registration server authenticates the home registration server the identity of the foreign registration server, and it also authenticates the identity of the end system. If the Authentication and registration are successful, selects the Home registration server an IMF from the home network to an I-Xtunnel connection between the home IWF and the serving IWF (in the foreign WSP) to create. The IWF in the home network is used for the duration of the PPP session as the anchor point.

0120As soon as the authentication and registration phases are over, the various PPP phases will be started. At the start of PPPs is between the home IWF and requested ISP / intranet PPP server an L2TP connection produced. In the PPP authentication phase, be exchanged using PAP or CHAP PPP passwords, and the ISP or Intranet PPP server authenticates the identity of the end system independently.

0121As soon as this succeeds, the PPP network control phase is started. In this Phase is negotiated an IP address and by the PPP server assigned to the end system, and it is the use of a TCP / IP header compression negotiated. When this is complete, the end system is capable IP packets using PPP to its ISP or a proprietary Intranet to send and receive.

0122It is to be mentioned that two levels of authentication are performed. authentication authenticates the identity the end system for the registration server in the home network and the identities of the foreign network and the home network with one another. sent to carry out this function the foreign agent registration request from the end system to Example, using an IETF Radius protocol in a Radius Access-Request or RADIUS access request packet to a Regis Trieery server in its local MSC. determined by using the domain name of the end system the foreign registration server the identity of the home network and the Home registration server of the end system and encapsulated and transmitted as a Radius proxy agierend the request to the home registration server the end system. If the foreign registration server the identity of the home the end system can not find it, the radius request optional transmit to a registration server as a broker acts (eg one of a consortium of wireless service providers belongs), which the Radius Access-Request in turn to Endheimatregistrierungsserver durchreicht. If the local registration server is unable is the registration request locally or through hatches to supply, then he has the registration request of the foreign Agents from, and the foreign agent, the registration request the end system from. Upon receiving the Radius Access-Request, the home registration server performs the required authentication of the identities of the foreign network and the End system through. If authentication and registration are successful, the responses of the home registration server with an Radius Access-Response Radius access response packet to the foreign registration server, sends a reply to the foreign agent, so that a circulation can be completed. The registration request is rejected, if the home registration server for any reason unable is corresponding to.

0123The second level of authentication verifies the identity of the end system for the Intranet or ISP PPP server. One of the mobility authentication separate PPP authentication allows the infrastructure equipment separated inserted by ISP and possess.

0124<figref idrefs="S137">17</figref> is a ladder diagram, the registration result, the for a represents roaming end system. It is assumed that the PPP server and the home IWF in the same server and not L2TP is required. Note the interactions with billing servers to the accounting for to begin to register the end system, as well as with directory servers, the identity the home registration server and to determine the identity of the end system to authenticate. details information about Accounting, billing, Roaming (between service providers) and payment are hereinafter provided.

0125MAC layer messages user registration agent of the end system may be used, initiate an agent solicitation or agent polling. The MAC layer messages are not shown for clarity.

0126In <figref idrefs="S137">17</figref> calls the end system (mobile unit) initially a announcement from, and the foreign agent replies with an announcement that the end system with information about the network to which the foreign agent belongs including a Guest address of the foreign agent provides. Alternatively can this phase will be omitted, and all network announcements can carried by a continuously emitted MAC layer beacon message. In this case it is assumed that the network is a foreign wireless service provider is. Then, a user registration agent (in the end system) the information about the foreign agent (which the user name and other security credentials included) and its network to include in a request and sends the Request to the foreign agent. The foreign agent as a proxy registration agent forwards the request to the foreign registration server (ie Registry Server the foreign wireless service provider) on. Then intervenes the foreign Registration server recognizes that it is not the home directory is, to the foreign directory server with the FDD in the foreign Wireless service provider to find out how he's registration request, the the home registration server of the wireless service provider to which the end system belongs, to conduct. The foreign registration server responds with the required transmission messages. Then the foreign registration server encapsulates the registration request the end system in a radius access request and passes the encapsulated request to the home registration server the wireless service provider to which the end system belongs. Of the Home registration server accesses the home directory server with the HDD of the home registration server to order at least authentication information about the to learn foreign service providers. Optional accesses the home registration server on the list of participants to order detailed subscriber service profile information (Eg subscribed quality of service options etc.) to learn. If all partners are authenticated, sends the home registration server a start IWF request to the Home IWF and the PPP server. The home IWF and the PPP server start the home accounting server and then send a start IWF response to the home registration server. The home registration server then sends a Radius access response to the foreign registration server. The foreign registration server then sends a start IWF request to the server of the serving IWF. The server of the serving IMF starts the serving accounting server and then sends a Start IWF response to the foreign registration server. The foreign registration server sends a registration reply to the foreign agent, and the foreign agent forwards the registration reply to the end system on.

0127A transmission control protocol or LCP configuration request (LCP for eng. link control protocol) is from the end system through the foreign Sending registration server instructs the home IWF and the PPP server. The home IWF and the PPP server sends an LCP configuration acknowledgment by the foreign registration server to the end system.

0128Similarly a Passwortauthentifizierungsprotokoll- or PAP authentication request by the home IWF and the PPP server sent and confirmed.

0129Alternatively , a query authentication protocol (CHAP for eng. challenge authentication protocol) used for authentication will. Both protocols can be used to authenticate or this phase can be skipped will.

0130Similarly an IP Konfiguratonsprotokoll- or IPCP configuration request by the Home IWF and the PPP server sent and confirmed.

0131The Connection with the end-system may be any of the following reasons be completed: <ul><li>1 initiated by the user Termination. According to this Scenario ends the end system as the first PPP in sliding Wise. This includes terminating the PPP network control protocol (IPCP), after which the PPP connection protocol is terminated. As soon as this is done, can be to delete the end system from Network tab, whereupon the radio link is terminated with the access point.</li><li>2. interruption of the wireless link. This scenario is detected by the modem and reported to the modem driver in the end system. The upper layers of the software are notified to the stack to stop and notify the user.</li><li>3. Interruption of the connection to the foreign agent. This Scenario is the mobility driver in End system detected. After trial and error, with a (potentially new) foreign agent reestablish contact, the driver sends a notice up and signaled the protocol stack and the modem hardware below to terminate the wireless link.</li><li>4. break in the connection with the IMF. Here applies primarily the same as for the interrupt with the foreign agent.</li><li>5. Termination of PPP by IWF or PPP server. This scenario is detected by the PPP software in the end system. The PPP driver the end system is informed of this event. He leads erasure from the network register, whereupon the wireless connection with the Access point is completed.</li></ul>

0132Endsystemdienstkonfiguration refers to the concept of configuring the network service for a End system based on the user's service profile. The subscriber service profile is stored in a directory. The service profile contains Information to enable the software, the wireless data service for the custom set of participants. It includes information, to authenticate the end system, allow the end system, to wander, and connections to the Internet service provider of the establish end system. Preferably, this information shall Other parameters such as quality of service. In addition to the list of participants be a home domain directory (HDD for eng. home domain directory) and a foreign domain directory (FDD for eng. foreign domain directory) for roaming and for authenticating the foreign and home registration server with one another. The HDD stores information about the Home network of the terminal system, and the FDD stores information about foreign networks, which a participant could attend.

0133<figref idrefs="S138">18</figref> shows how this Dir isse in the network architecture map and while Registration for an end system be used, which can be register at home. at Step 0 calls the end system (mobile unit) an announcement and receives they from foreign agent to the end system with information about the to provide power, which belongs to the foreign agent. In this Case is the power of the home wireless service provider. In step 1, user registration agent does (in the end system) the information about the foreign agent, its network and security credentials in a request and sends the request to the foreign Agents. In Step 2 of the foreign agent forwards as a proxy registration agent the request to the home registration server. At step 3 accesses the home registration server to the HDD of the home wireless service provider to, at least to read authentication information. at Step 4 accesses the home registration server to the list of participants to order subscribed detailed subscriber service profile information (eg QoS options etc.) to learn. In step 5, the home registration server notifies the foreign agent access response with the. In Steps 6 and 7 inform the foreign agent of the end system (ie the mobile unit) which Registration reply with.

0134<figref idrefs="S139">19</figref> provides directory usage for an end system represents the register of a foreign network leaves. At step 0 calls the End system (mobile unit) announcing a starting, and the foreign Agent announces on what provides the end system with information about the network to which the foreign agent belongs. In this case, the network is a foreign wireless service provider. In step 1, the user registration server accepts (in the end system) the information about the foreign agent, its network and security credentials in a request and sends the request to the foreign Agents. In Step 2 of the foreign agent forwards as a proxy registration agent the request to the foreign registration server (ie the registration server for the foreign wireless service provider) on. In step 3 engages the foreign registration server to the HDD of foreign wireless service provider to to learn the network to which the end system belongs. at received Step 4 the foreign registration server the invitation of the end system to the home registration server of the home wireless service provider the end system. In step 5, the home registration server accesses the FDD of the home registration server to order at least authentication information about the to learn foreign Diensteanbeiter. In step 6, the home registration server accesses on the list of participants to order detailed subscriber service profile information (Eg subscribed quality of service options etc.) to learn. In step 7, the home registration server notifies the foreign registration server access response with the. At step submitted 8 the foreign registration server the access response to the foreign Agents. In step 9, the foreign agent notifies the end system (ie the mobile unit) registration reply with the.

0135Protocol handling scenarios for processing data carriers and its Stacks for transporting bearer data to and from an end system, the protocol stacks for the cell architectures, the local APs (<figref idrefs="S140">20</figref>) And remote APs (<figref idrefs="S140">21</figref>use).

0136<figref idrefs="S140">20</figref> provides protocol stacks for handling communications between an end system (in its home network) and a home IWF for End system @ Home represents. <figref idrefs="S140">20</figref> shows the protocol handling for a Cell architecture, in which the access point and the wireless hub are housed collocated.

0137<figref idrefs="S140">21</figref> shows the protocol handling for a cell architecture, in which the access point deducted from wireless arranged is. As shown, ends the PPP in the IMF, and the configuration provides a direct Internet ready. The configuration for the case where where the PPP server is separate from the IWF is described later.

0138In <figref idrefs="S140">21</figref> are PPP frames for the end system in Funkverbindungsprotokoll- or RLP frames (for eng. radio link protocol) encapsulated what the remote access point for communicating with the trunk access point (ie, an access point, physically near disposed of wireless hubs) are encapsulated in MAC frames, wherein the remote access point, for example, through a wireless Trunk is connected to the access point. The access point acts as a MAC layer bridge and passes under the air connection to the foreign agent in the wireless hub on. The foreign agent de-encapsulates the RLP frames from the MAC frame, and forwards the RLP frames using the XTunnel protocol the IMF continued. A similar, although the reverse process takes place during the transmission of frames of the IMF to take end system.

0139If the end system moves to another foreign agent, then will automatically create a new Xtunnel between the new foreign agent and the IMF created, so that the PPP traffic between further without Interruption flows.

0140In the cellular architecture with remote AP (<figref idrefs="S140">21</figref>) wireless trunks between the remote AP and the trunk AP used, the air link between the end system and the Access point opposite the frequency (f2) and radio technology of the trunk to another Frequency (f1) to work and use a different wireless technology.

0141<figref idrefs="S141">22</figref> illustrates the protocol stacks for a roaming end system. The serving IWF uses the I-Xtunnel protocol between the serving IWF and the home IWF. The rest of the protocol stack stays unchanged and is not shown. This architecture can by inserting the serving IWF be simplified in the base station, thereby the XWD protocol is eliminated.

0142The RLP layer uses sequence numbers to duplicate PPP datagrams to delete and an in-sequence delivery of PPP datagrams between the end system and the IMF provide. It also provides a configurable Keep-alive mechanism to track the connectivity to monitor between the end system and the IMF. In addition, the RLP layer in an alternative embodiment also Wiederholungssendungs- and flow control services in order that the Gesamtbitfehlerrate Verreducing connection between the end system and the IWF. The RLP between the end system and the IWF is the beginning of the meeting started and remains during the whole session and self Handoffs active.

0143in the Contrary to the specification in Mobile IP RFC (RFC <figref>2003</figref>) is no IP-in-IP encapsulation to tunnel between the foreign agent and the home IWF uses. Instead, a new tunneling protocol used on the the UDP is implemented. This tunneling protocol is a simplified Version of the L2TP protocol. The reasons for this Election are as follows: <ul><li>1. The encapsulation protocol, which is specified in RFC 2003 does not provide flow control or In ready-sequence delivery of packets. The presently described required power these services may in the tunnel over the backhaul. A flow controller may be required to the Amount of retransmissions via the airlink due of packet loss due to flow control problems over the Network between the base station and the MSC or due to flow control problems decrease in the base station or the IMF.</li><li>2. Thus, by using a UDP-based tunneling protocol carried out the implementation at the user level and then from performance reasons after its suppression be placed in the kernel.</li><li>3. When using RFC 2003, there is no easy way, Tunnel under consideration quality of service and to generate load balancing. To account for the QOS, it should be possible tunnel over build links which already provide the required QOS. Second, there is no easy way for use of RFC 2003 provide load balancing to support the traffic load over multiple to distribute connections between the base station and the MSC.</li><li>4. To implement an IP-in-IP encapsulation as specified in RFC specified 2003 need the developer access to the IP source code. In commercial operating systems is the source code for the TCP / IP stack generally the property of other equipment manufacturers. The acquisition of TCP / IP stack from a manufacturer and the implementation of modifications at the IP layer to support the Mobile IP tunnel setup, would be of a developer require a different version of the TCP / IP stack to support. This adds cost and risk added.</li></ul>

0144Although it should be noted that the tunneling protocol between the base station and the IMF is not enabled by default and that the wireless service provider is not capable of operating means to combine and adapt by different manufacturers, is the use of a non-standard tunneling protocol within a single wireless service provider network for end systems and equipment transparent by other manufacturers.

0145The new tunneling protocol is based on the L2TP. is The L2TP se a congested tunnel protocol so that the L2TP high Additional expenses in connection with the tunnel creation and authentication Has. The new tunneling protocol of the present invention has fewer Overhead. The new XTunnel- and I-Xtunnel protocol, the following features comprise: <ul><li>1. The XTunnel- and I-Xtunnel generation adds the Radius Access Request and Radius Access Response messages between the base station and the registration server vendor-specific Extensions added. These extensions negotiate tunnel parameters and to create the tunnel.</li><li>2. The registration server is capable of the actual Work of tunnel construction and the routing of packets to different IP addresses and therefore delegated to another server in the MSC. This makes it possible the registration server, perform load balancing across multiple IWF servers and different QOS for provide different users.</li><li>3. The XTunnel- and I-Xtunnel protocol supports in-band control messages for tunnel management. These messages include echo request / reply for testing the tunnel connectivity, Disconnection request / response / message for separating the tunnel and error for error messages. These Messages are the tunneling media, for example UDP / IP is sent.</li><li>4. The XTunnel- and I-Xtunnel protocol transmits user data via the Tunnel media, for example UDP / IP. The XTunnel- and I-Xtunnel protocol supports Flow control and in-sequence packet delivery.</li><li>5. The XTunnel- and I-Xtunnel protocol can about other Media as UDP / IP for QoS be implemented.</li></ul>

0146The support network a direct Internet connection capability by the PPP in the Home IWF is terminated and IP packets from the IWF to the internet via a Router are forwarded to the default IP routing protocols used. preferably leads the IMF from the RIP, and the router also performs the RIP and possibly Other routing protocols such as OSPF from.

0147The support network a first configuration for a wireless service provider, who is also an Internetservice provider is. In this configuration, the home IWF in the MSC acts as a PPP server. This IMF leads also Internetleitweglenkungsprotokolle like RIP and uses a router to get to the backbone network of the Internet service provider to join.

0148The support network a second configuration for a wireless service provider who wishes to allow end systems, to connect to one or more Internet service provider, because the WSP itself either no ISP or because the WSP agreements has with other ISPs to end users to gain access. To the Example, a wireless service provider opt an end user to provide access, and it can an agreement have a foreign ISP to the user, who is also an account at Foreign ISP has to allow access to the ISP from the WSP network. In this configuration, the running PPP server is not in the home IWF which is installed in the MSC. Instead, a tunneling protocol as L2TP (Layer Two Tunneling Protocol) Back to tunnels used for PPP server of the ISP. <figref idrefs="S133">10</figref> provides the Protocol stack this configuration for an end system that is worth at home.

0149Of the Whereabouts of the home IWF and the ISP PPP server remains fixed throughout the PPP session. also remains the L2TP tunnel between the IWF and the ISP PPP server during all PPP session upright. The physical distance between the IWF and the PPP server is via a router that a dedicated T1 or T3, a Rahmenweiterleitungs- or an ATM network used. The true nature the physical link is from the viewpoint of architecture not important.

0150These supported configuration and the intranet access. For intranet access sits the PPP server in companies are Intranet, and the home IWF uses L2TP to to tunnel to it.

0151For a fixed End system is the protocol handling for intranet or ISP access as in <figref idrefs="S142">23</figref> shown, with the difference that the roaming end system a serving IWF used to be in his home IWF Set connection. The protocol handling between a serving IWF and a home IWF has been described. In<figref idrefs="S142">23</figref> the home IWF may be inserted into the wireless hub, whereby the Xtunnel protocol is eliminated. Even the serving IMF may be inserted into the wireless hub, whereby the Xtunnel protocol is eliminated.

0152<figref idrefs="S142">24</figref> provides the protocol stack, which during Registration phase (end system) can be used for a cell architecture with local access point. The stack for an architecture with remote Access point is very similar.

0153The Scenario shown above is for a roaming end system. are for an end system at home there is no foreign registration server in the registry of the brand.

0154one Note the mobility agent in the end system. The mobility agent in the end system and the foreign agent in the wireless hub are conceptually similar to the Mobile IP RFC 2002. The mobility agent handles network errors using timeouts and retries from. In contrast to known protocol stacks for bearer data no RLP is used. The foreign agent and the registration servers use Radius over UDP / IP to communicate with each other to register the end system.

0155It to consider several aspects of security. The first, the Authenticating the identities of End system and the foreign / home network during the wireless registration phase. The second, to authenticate the identity of the end system with its PPP server during the PPP authentication phase. Third, authentication for storing accounting data for detecting charges and for updating home domain information. The fourth, encryption bearer traffic, the transferred to and from the end system becomes. The fifth, encryption for exchanging accounting information on service provider boundaries.

0156It are shared secret codes used to determine the identity of end systems with their home networks and the identity of the home and the foreign network each other during the wireless registration to authenticate.

0157The Endsystemauthentifizierung uses a common use 128-bit secret code to an identity brand for its registration request to create. The identity mark is calculated using the known MD5 message digest algorithm, as described in Mobile IP RFC 2002, is generated. Alternatively , another algorithm may be used. The shared Secretcode is not in the registration request by the End system sent. It is sent only the identity mark. Upon receipt the registration request from the end system calculates the home registration server the identity mark on the Registration request data using the shared used secret codes again. If the calculated authenticator value matches the authenticator value, was sent by the end system, allows the home registration server, that the registration process is continued. When the values ​​of do not match, logs the home registration server, the event generated a security violation alarm and a "nak" (ie, a negative acknowledgment) for the Prompt.

0158In the registration response makes the home registration server the same, this means it uses the shared secret to a brand identity for the Registration reply to produce, that it sends to the end system. After receiving the reply, the end system calculates the authenticator re using the shared secret. If the calculated value does not match the identity of brand value, the sent by the home registration server in response was, the end system discards the reply and tries again.

0159These Network security concepts are similar to the concepts that in Mobile IP RFC defined of 2002. According to RFC there a mobility security association between each end system and its home network. Each mobility security association defines a collection of security contexts. Each security context defines an authentication algorithm, a mode, a Secret code (shared or public-private), a replay protection and the type of encryption used. In the context of the present Network is the user name of the end system (instead of the Mobile IP home address) used to the mobility security association to identify between the end system and its home network. Another parameter, called the security parameter index (SPI), is used to provide a security context within the mobility security association select. In a basic embodiment of the invention are only the prescribed mobile IP authentication algorithm (MD5 encrypted) and the default mode ( "prefix + suffix") with shared 128-bit secret code supports. Network users can several shared secret codes with their home network define. The mechanism for generating security contexts for end users, wherein each security context a SPI is allocated for setting the contents of the security context (which the shared Secret code included) and for modifying their content is in Described below. While Registration is by the end system using the MD5 algorithm, a 128-bit message digest in a prefix + suffix mode calculated. The shared secret code is used as the prefix and the suffix for the data used that must be protected in the registration request. The thus calculated authenticator along with the SPI and the User name in the registration request by the End system sent. Upon receipt of the registration request the end system directs the foreign registration server the invitation together with the identity mark and the SPI unchanged to the home registration server. Upon receipt of the registration request directly from the end system or indirectly via a foreign registration server used the home registration server the SPI and the User Name to select the security context. calculates the home server the authenticator re using the shared secret. If the computed authenticator value coincides with the value of the brand identity, that was sent in the request by the end system, is the identity the user is successfully authenticated. Otherwise, confirmed the Home registration server the registration request, by the end system is sent, is negative (NAK).

0160The Registration reply by the home registration server is sent to the end system is also performed using the algorithm described previously authenticated. The SPI and the computed authenticator value are in the registration reply message by the home server transmitted to the end system. After receiving the reply, the end system calculates the authenticator new and when the calculated value does not match the transmitted value, it discards the reply and tries again.

0161The End system the user needs for all security contexts that the user with its registration server (s) used in common, using the shared secret code and SPIs are configured. These configuration information for Windows 95-based end-systems preferably stored in a Win 95-Register. While the registry is accessed this information, and they be for Authentication purposes.

0162in the Network used by the foreign agent FA Radius protocols to the end system to register and Xtunnel between the wireless hub and the home and the serving IWF to configure for the end system. generates Upon receipt of a registration request from the end system the FA a Radius Access-Request packet (RADIUS access request packet) stores, its own attributes into the packet, copies the registration request attributes the end system unchanged in this packet and sends the associated request to the registration server in the MSC.

0163A Radius authentication requires that the Radius client (in this Case, the FA in the base station) and the Radius server (in this Case the registration server in the MSC) a secret code for authentication purposes use together. This shared secret is also used to encode all private information transferred between the Radius client and the Radius server will. The shared secret code is a configurable Parameter. The network follows the recommendations in the Radius RFC and uses the shared secret and the MD5 algorithm for authentication and for encryption, if encryption necessary is. The Radius-Access Request packet, which was sent by the FA contains a Radius User-name or RADIUS user name attribute (Which is provided by the end system) and a Radius User Password- or radius-user password attribute. The value of the User-Password attribute is also a configurable value and is amended by the Radius protocol encrypts recommended way. Other network-specific Attributes, which from the point of Radius RFC standards no standard attributes are encoded as vendor specific Radius attributes and sent in the Access-Request packet.

0164The following attributes through the FA in the Radius Access-Request packet sent to its registration server. <ul><li>1. User-Name attribute. This is the user of the end system so, delivered as by the end system in its registration request.</li><li>2. User-Password attribute. This user password is the base station / the wireless hub to the user supplied. It is encoded as described in RFC radius, wherein the secret code is used between the base station and its registration server is shared.</li><li>3. NAS-Port. This is the port on the base station.</li><li>4. NAS-IP-Address. This st the IP address of the base station.</li><li>5. Service-Type. This is a framed service.</li><li>6. Framed Protocol. This is a PPP protocol.</li><li>7. Xtunnel Protocol parameter. These features are enabled sent the base station to specify the parameters that are necessary to build the Xtunnel protocol for the end system. This is a vendor-specific attribute.</li><li>8. AP-IP-Address. This is the IP address of the AP through which the user can register. This is a vendor-specific attribute.</li><li>9. AP MAC Address. This is the MAC address of the AP through which the user can register. This is a vendor-specific attribute.</li><li>10. End system Registration Request. The registration request from the end system is unchanged in copies of this vendor-specific attribute.</li></ul>

0165The following attributes from the registration server in the Radius Access-Response or Radius access response packet sent to the FA: <ul><li>1. Service Type. This is a framed service.</li><li>2. Framed-Protocol. This is a PPP.</li><li>3. Xtunnel Protocol parameter. These features are enabled Sending the registration server in order to specify the parameters, which are necessary for constructing the XTunnel protocol for the end system. This is a vendor-specific attribute.</li><li>4. Home Registration Server Registration Reply. This attribute is sent by the home registration server to the FA. The FA forwards this attribute in a registration response packet to unchanged the end system on. If there is a foreign registration server are on the way, this attribute is not waned through him the FA passed. It is as a vendor-specific attribute coded.</li></ul>

0166Around to provide host-end systems, the foreign network and the home network are using the Radius protocol for authentication and configuration with each billing and billing purposes authenticated. This authentication is the time of End system performed. As already mentioned, used the registration server in the foreign network when a registration request receives from an end system (Encapsulated as a vendor-specific attribute in a radius Access Request packet by the FA), the user name of the end system, the identity the home registration server of the end system by consulting his home domain directory HDD to determine. The following information is in the home domain directory HDD saved and she grabs the foreign registration server to, to forward the registration request of the end system: <ul><li>1. Home Registration Server IP Address. This is the IP address of the home registration server to the registration request to be transmitted.</li><li>2. Foreign Registration Server Machine Id. This is machine ID the foreign registration server in simplified Email Transfer Protocol or SMTP format (for eng. simplified mail transfer protocol) (eg machine @ fgdn wherein machine is the name of the foreign registration server machine and fgdn the fully qualified domain name the domain the foreign registration server).</li><li>3. Tunneling Protocol Parameters. These are parameters for configuring the tunnel between the serving IWF and the home IWF for the end system. These include the tunnel protocol to use between them is, and the parameters for configuring the tunnel.</li><li>4. Shared Secret. This is the shared secret code, the authentication between the foreign registration server and the home registration server to be used. This secret code is to calculate the radius of User-Password attribute in the Radius packet used by the foreign registration server to the home registration server is sent. It is between the two wireless service providers defined.</li><li>5. User-Password. This is the user password, which for the roaming end system is to be used. This user password is used between the two Wireless service providers defined. This password will be using the shared secret codes, as in the radius RFC described, encrypted.</li><li>6. Accounting parameter. These are parameters for configuring billing for the end system that can register. These parameters by the registration server to configure the billing for the End system sent to his IMF.</li></ul>

0167By Use this information generates the foreign registration server a Radius Access-Request adds, its own registration and authentication information in the Radius Access-Request added, copies the registration information by the end system were sent, unchanged in the Radius Access-Request and sends the associated requirement to the home registration server.

0168by Receiving the Radius Access-Request from the foreign registration server (for a questioned roaming end system) or directly from the FA (for an end system at home) the home registration server its own directory server to the shared secret codes to determine the identity of the end system and the identity the foreign registration server in a roaming scenario by New calculation of identity brands to check.

0169by successful processing of the request generates the home registration server a Radius Access-Accept-or Radius Access authorization response packet and sends it to the foreign registration server when the end system migrates, or directly to the FA from which it the Radius Access-Request received. The response contains the registration reply attribute that the FA relays to the end system.

0170If the request can not be processed successfully, generates the home registration server a Radius Access-Reject or Radius Access denial response packet and sends it to the foreign registration server when the end system migrates, or directly to the FA from which it received the Radius Access-Request. The response contains the registration reply attribute that the FA relays to the end system.

0171In a roaming scenario, the response from the home registration server received by the foreign registration server. You will be the foreign registration server using the shared used secret codes to authenticate. After authenticating processed the reply, the foreign registration server and generates in turn, a Radius response packet (Accept or Reject) to dispatch the FA. The foreign registration server copies the registration reply attribute from the Radius response packet access the home registration server unchanged in its Radius response packet. If the FA, the Radius Access-Response or Radius Access-Reject response packet receiving generated it using the registration reply attributes from the Radius response a registration response packet and sends the reply to the end system, whereby the registration circulation sequence is complete.

0172The specify Mobile IP standards that a replay protection for registrations is implemented, said timestamps or nonces used optional will. However, since replay protection, the time stamp used adequately synchronized time of day clocks between the corresponding node heCalls, the present invention implements a Replay protection while registration using nonces, even if a replay protection, the timestamp used prescribed in the Mobile IP standards is and the use of nonces is optional. However, it is a Replay protection, the time stamp used as an alternative embodiment provided.

0173The Replay protection used between nodes, additionally to authentication context, mode, secret code and encryption saved in the security context.

0174The support network the use of PPP PAP (password authentication) and -CHAP (Abfrageauthentifiziertes Password) between the end system and its PPP server. This is independent of the above-described registration and authentication mechanisms. this makes possible it a private intranet or an ISP, the user's identity to check.

0175A authentication Billing and directory services is on 'the relative settlement security described. Access to directory servers of network resources in the same MSC need not be authenticated to become.

0176The support network encryption vehicle data, sent between the end system and the home IWF. The end systems act by selecting the appropriate security context of whether encryption should be on or off. Upon receipt of the registration request Granted, the home registration server of the end system requirement an encryption based on the security context. In addition to storing authentication algorithm, Mode, shared code and replay protection is The security context also used to select the format to be used the encryption algorithm to specify. If the encryption between the end system and the home agent is negotiated, then the entire PPP frame so encrypted before encapsulation in RLP.

0177The IMF, the accounting server and the billing system Part of the same reliable domain in the MSC. These entities are either connected to the same LAN, or part of a reliable Intranets, owned by the wireless service provider and it operates. The transfer of Accounting statistics between the IWF and the accounting server and between the accounting server and the customer billing system do not need using Internet IP security protocols as IP Sec encrypted to become.

0178The Network makes it more difficult to monitor the whereabouts of the end system, since it appears that all PPP frames, the from and go to the end system, regardless of the actual Whereabouts of Endsystemgeräts go through the home IWF.

0179The Accounting data through the serving IWF and the home IWF collected in the network. Billing data obtained by the serving IWF are collected, are sent to a billing server in the MSC of serving IWF sent. Billing data collected by the home IWF sent to an accounting server in the MSC of the home IWF. The Billing data collected by the serving IWF, be through the foreign wireless service provider for auditing and to pay invoices Wireless Served provider boundaries used (to support roaming and mobility). The Billing data collected by the home IWF are for charging the end user and also for payment by wireless service provider boundaries used to handle roaming and mobility.

0180There regardless of the residence of the end system and the place of stay the foreign agent all traffic through the home IWF flows, has the home IWF complete information for creating invoices for the Customer and payment information on using third-party networks.

0181The serving IWF and the home IWF preferably use the Radius accounting protocol for sending accounting records registered End systems. The Radius accounting protocol is as in a IETF RFC draft documents. For the present invention has the protocol by adding proprietary attributes the network and by adding extended a checkpoint marking the Radius Accounting protocol will. Checkpoint marking in this context refers to Periodic updates accounting data to the risk of loss of accounting records minimize.

0182The Radius accounting protocol runs over UDP / IP and used retries based on confirmation and Timeouts. The Radius accounting client (Supplying IMF or home-IMF) will send UDP accounting request packets their accounting server, which confirmations to the billing clients resend.

0183in the Network enter the billing clients (the serving IWF and the home IWF) an accounting start indication at the beginning of user session and an accounting stop indication at the end of the user session out. In the middle of their meetings, billing clients from billing control ads. In contrast, the Radius accounting RFC does not specify a billing control display. The Software of the present invention produces a vendor-specific Accounting attribute for this purpose. This statement attribute is in all Radius Accounting-Request or Radius accounting request packets present which an Acct-Status-Type of Home (Billing Start Ads) exhibit. The value of this attribute is used to the billing server transferred to, whether the accounting record is a control record or not. have control accounting records a time attribute and contain cumulative accounting data from Start the session. The frequency of transferring of control packets is configurable in the present invention.

0184The serving IWF and the home IWF are by their respective Registration server to connect to their accounting servers while the registration phase configured. The configurable accounting parameters include the IP address and UDP port of the accounting server, the frequency of Checkpoint marker that session / multi-session ID and the common used secret code between the client and the billing is to use accounting server.

0185The Network records the following accounting attributes for each registered on the end system. This billing attributes are billing clients in Radius accounting packets at the beginning of Session, at the end of the session and in the middle (control) their Billing servers reported. <ul><li>1. User Name. This attribute is like the previously discussed Radius User-Name attribute. This attribute is used to identify the user and is present in all accounting reports. The format is "user @ domain", where domain of Fully Qualified Domain Name the user's home is.</li><li>2. NAS-IP-Address. This attribute is like the previously discussed radius NAS-IP-Address attribute. This Asttribut is used to the to identify the machine IP address, which the home IWF or the serving IWF performs.</li><li>3. Radio Port. This attribute identifies the radio access in the access point servicing the user. This attribute is encoded as a vendor-specific attribute.</li><li>4. Access Point IP Address. This attribute identifies the IP address of the access point that serves the user. This Attribute is encoded as a vendor-specific attribute.</li><li>5. Service Type. This attribute is as described above Radius Service-Type attribute. The value of this attribute is Framed (Framed).</li><li>6. Framed Protocol. This attribute is as described above Radius Framed-Protocol attribute. The value of this attribute is set so that it displays PPP.</li><li>7. Accounting Status Type. This attribute is like the previously described Radius Acct-Status-Type attribute. The value of this attribute may be starting to the start of a user's session with the highlight Radius client, and it may be stopped at the end to highlight the user's session with the Radius client. For payroll clients is the Acct-Status-Type / Start attribute generated when the end system can register. The Acct-Status-Type / Stop attribute is generated when the end system from some reason Clear the register leaves. For checkpoints is the value of this attribute is also Start and the Accounting Checkpoint or billing control attribute is also available.</li><li>8. Accounting Session Id. This is how the above-described Radius Acct-Session-ID. In a roaming scenario, this session ID assigned by the foreign registration server when the end system a registration request outputs. You we during Registration Sequence transmitted by the foreign registration server to the home registration server. The home network and the foreign network both know the Acct-Session-ID attribute and are capable of outputting this attribute while on their accounting records Send respective accounting server. In an "end system-to-home" scenario is this Attribute generated by the home registration server. The registration server communicates the value of this attribute, the IMF, which it in all accounting records outputs.</li><li>9. Accounting Multi-Session-Id. This is like the previously discussed radius Acct-Multi-Session-Id. This ID is the home registration server assigned when a registration request from a FA directly or a foreign registration server is received for an end system. It is through the home registration server in the registration reply message at foreign Registrierungssertransmitted ver. The or the registration server communicate the value of this attribute of or the IMF (s), which him in all accounting records output.</li></ul>

0186at a reliable Mobility, added the architecture is that ID is used to the accounting records of various IMF for the same to bring end-system related, if the end system moves from one IWF to another. For handoffs on IMF limits the Acct-Session-ID or billing session ID different for accounting records, the coming from different IMF. The Acct-Multi-Session-ID or Multiple billing session ID attribute but is the same for all accounting records, issued by all IMF which supplied the user. Since the session ID and the multi-session ID, both the foreign network as well as the home network are known, they are capable of these attributes issue in accounting reports to their respective accounting server. With the session ID and the multi-session ID are billing systems capable of accounting records about IMF limits in the same wireless service provider and even across wireless service provider boundaries to correlate. <ul><li>1. Accounting Delay Time (billing delay time). See Radius Acct-Delay-Time attribute.</li><li>2-. Accounting Input octets. See Radius Acct-Input-Octets. This attribute is used to keep the number of octets in the eye, sent by the end system (input into the grid from the end system). This count is used to track the PPP frames only. The air link overhead or any additional expense, which is introduced by RLP, etc., is not counted.</li><li>3. Accounting Output octets. See Radius Acct-Output-Octets. This Attribute is used to keep the number of octets in the eye, that are sent to the end system (output from the network to the end system). This count is used to track the PPP frames only. The air link overhead or any additional expense, which is introduced by RLP, etc., is not counted.</li><li>4. Accounting Authentic (billing authentic). See radius Acct-Authentic attribute. The value of this attribute is a function whether the serving IWF or the home IWF to accounting record generated local or remote (sold).</li><li>5. Accounting Session Time. See Radius Acct-Session-Time attribute. This attribute indicates the period of time that provides the user has been. If sent by the serving IWF pursues this Attribute indicates the length of time that the user of the serving IWF was supplied. If sent by the home IWF pursues this Attribute the time that supplies the user from the home IWF has been.</li><li>6. Accounting Input Packets. See Radius Acct-Input-Packets attribute. This attribute indicates the number of packets from the end system received. For a serving IWF pursues this attribute, the number of PPP frames, inputted from an end system in the serving IWF. For a home IWF pursuing this attribute, the number of PPP-yards, from a End system are entered into the home IWF.</li><li>7. Accounting Output Packets. See Radius Acct-Output-Packets attribute. This attribute indicates the number of packets for which to the end system be sent. For a serving IWF pursues this attribute, the number of PPP frames, the serving of an IMF are output to an end system. For a Home IWF pursues this attribute, the number of PPP-yards, the output from a home IWF to an end system.</li><li>8. Accounting Terminate Cause. See Radius Acct-Terminate-Cause attribute. This attribute specifies the reason as to why a user session was terminated. also is a specific reason code available to additional provide details. This attribute is only in accounting reports available at the end of the session.</li><li>9. Network Accounting Terminate Cause. This attribute the cause of the termination of a session detail on. This specific Attribute is encoded as a vendor specific attribute and Accounting is attribute only in a radius at the end of the session reported. The radius-default attribute Acct-Terminat-Cause is also available. This attribute provides specific cause codes ready which are not covered by the Acct-Terminate-Cause attribute.</li><li>10. Network Air Link Access Protocol. This attribute specifies the Airlink access protocol that is used by the end system becomes. This attribute is encoded as a vendor-specific attribute.</li><li>11. Network Backhaul Access Protocol. This attribute specifies the Backhaul access protocol that is used by the access point, to data and to transfer from the end system. This attribute is encoded in vendor specific format.</li><li>12. Network Agent Machine Name. This attribute is the fully qualified domain name the machine that performs the home IWF or the serving IWF. This specific attribute is encoded in vendor specific format.</li><li>13. Network Accounting Check-point. Since the Radius accounting RFC does not Checkpoint package defined, the present invention uses a Radius accounting start packet with this attribute to a Koncontrol point mark. The absence this attribute means a conventional accounting start packet. The presence of this attribute in a accounting start packet means a billing control package. Accounting stop packets have this attribute is not on.</li></ul>

0187In a preferred embodiment, have to each billing package and the appropriate response using authenticates the MD5 and a shared secret will. The IMF are configured with a shared secret key, by them during communication with their Radius accounting server for authentication is used. The shared secret used by the IMF are used to communicate with their billing servers, are in the home / foreign domain directory stored, which is located in the MSC. The shared Secret code for Settlement security are the IMF through its registration server while the Endsystemregistrierungsfolge communicates.

0188The Accounting server software runs in a computer located in the MSC. The function of the Accounting server in the system, it is, Roha refractive data from the Network elements (the home and serving collect IMF) to process the data and to transfer to the billing system To save the wireless service provider. The accounting server has no billing system on. Instead, he has a support for an automatic or manual accounting data transfer mechanism on. When using the automatic accounting data transfer mechanism of the accounting server transfers accounting records in an AMA billing format via a TCP / IP communications to the customer billing system. To this end, the system defines AMA billing record formats for packet data. When using the manual transmission mechanism customers are able to form a band to accounting records at their Billing system transferred to. In order to form the band to their specifications, the customer provided with information to access accounting records so that they they can process, before they write to the tape.

0189In <figref idrefs="S143">25</figref> be the Roha refraction data obtained by the received billing server of the local or supplying IMF are processed and stored by the accounting server. The processing performed by the accounting server includes, Filtering, compression and correlation of Roha refractive data, received from the IMF. A highly available file server, the Active / In standby dual processors and used interchangeable RAID disks, is for buffering the accounting data used, while they traverse the accounting server.

0190Of the delayed billing server the processing of the crude refractive data until an end system his ended session. If an end system terminates its session, processed the accounting server, the Roha refraction data it for the session has collected and stores an accounting summary record in a SQL database. The billing summary sentence that in the SQL database stored, points to an ASN.1 encoded file. This file contains detailed Billing information the meeting of the end system. The data stored in the accounting server stored, then by the billing data transfer agent transferred to the customer billing system. Alternatively, the wireless service provider billing data from the SQL database and / or the ASN.1 encoded file via a transfer tape to the billing system. be The database schema and format of the ASN.1-encoded file documented and the customer this purpose available made. If the volume of processed accounting data stored in the billing system, a high-water mark exceeds, generates the accounting server an NMS alarm. This alarm is canceled when the volume of data stored in the accounting server stored, falls below a low water mark. The High- and low-water mark for producing and canceling the alarm are configurable. The accounting server generates an NMS alarm even if the age of the accounting data stored configurable exceeds threshold. Conversely, the alarm is canceled when the age of the accounting data falls below the threshold.

0191The Subscriber directory is used to gather information about participants store, located in the home network. The home registration server consult this directory while the registration phase to authenticate an end system, and to register. For each participant saves the directory, the following Informations: <ul><li>1. User name (User Name). This field in the subscriber record is the SMTP format (for example, user @ fgdn) wherein the user subfield participating in its wireless home domain and the fgdn subfield the wireless home domain the subscriber identified. This field is by the end system in the registration request during the registration phase Posted. This field is controlled by theThe wireless service provider Participants assigned to the time of application for the network service. This Field is different from the user name field used in PPP becomes.</li><li>2. Mobility Security Association. This field in the subscriber record contains the mobility security association between the subscriber and its home network. As already mentioned, a mobility security association between each station and its home registration server. The mobility security association defines a collection of security contexts. Each defined security context an authentication algorithm, an authentication mode, a shared secret key, a replay protection and an encryption (including without encryption) for use between the end system and its home server. During the Registration calling the home registration server using the user name and the security parameter index (SPI), which by the end system will be delivered in its registration request, information about the security context of the user from the list of participants from. The information in the security context are to Enforce authentication, encryption and replay protection during the session. The mobility security association is by the wireless service provider at the time of application generated. It lies on the wireless service provider if he does the participant either by calling a customer service representative or by accessing the subscriber to a secure Web site leaves, allowed to modify this Agreement. The Web site software exported websites that the wireless service provider of a secure web server for participants accessible power. In this way, participants are able, among other subscriber information, which the Diensteanbeiter may accessible makes to inspect the contents of the mobility security association / to modify.</li><li>3. Modem MAC Address. This field contains the MAC address of the modem, the participants the belongs. In addition to shared secret is this field during Registering used to identify the user. It is possible, a MAC address-based authentication on a per-user basis off. The MAC address is communicated during registration to the home registration server.</li><li>4. Enable MAC Address Authentication (MAC address authentication Sharing). This field is used to determine whether the MAC address-based Authentication enabled (enabled) or disabled (locked) is. If enabled, then checked the home registration server the MAC address of the to be registered end system with this field to determine the identity of the end system to confirm. If disabled, then no check.</li><li>5. Roaming Enabled Flag (roaming Released Flag). If this Field is set to enabled, then the end system to third-party networks may hike. If this field is disabled, the system may not be Foreign networks migrate.</li><li>6. Roaming Domain List (roaming domain list). This field only relevant if the Roaming Enabled Flag is set to enabled is. This field a list of other domains, At the end system may migrate. If the contents of this list is zero and the Roaming Enabled Flag is set to enabled, may the end system wander freely.</li><li>7. Service Enable / Disable Flag (service-enable / disable flag). This field can be set by the system administrator to disable to a service for to suspend a participant. If this field is disabled, the participant may be for to register the service. When the subscriber registers and the value of this field is set to disabled, then the end system of the subscriber immediately disconnected by the network.</li><li>8. Internet Service Provider Association (Internet service provider agreement). This field information about the Internet service provider of the subscriber. This information be by the IMF during the PPP registration phase used to authenticate perform with the Internet service provider for the end system, and also to an L2TP tunnel between the IWF and the PPP server of the Internet service provider to create. The field contains the identity ISP subscriber. The IMF uses this information order to perform Authentication and the structure of the L2TP Tiunnels for the end system at the ISP directory access.</li><li>9. Subscriber's Name & Address Information. This field Name, address, telephone number, fax number, email address, etc. of Participant.</li></ul>

0192The Home domain directory (HDD) is used by the registration server to parameters via retrieve end system, to complete the registration for the end system. By Using this information, determines the registration server, if the end system can register at home or whether the final system Roaming end system is. In the former case, the registration server accepts the function of a home registration server, and treat the end system. In the latter case, the registration server accepts the function of a foreign registration server and forwards as Radius proxy agierend the invitation to real home registration server, whose identity he made this Directory receives. For a Roaming end system include the parameters that are stored in the HDD, the IP address of the home registration server, the home-foreign side shared secret code, the configuration of the tunnel between Home and IMF-sufficient, etc. The HDD is located in the MSC.

0193The following information is stored in the HDD: <ul><li>1. Home Domain Name (home domain name). This field is the key used when searching the HDD for an entry of the fully qualified home domain name matches, the supplied by the end system in its registration request becomes.</li><li>2. Proxy Registration Request (proxy registration request). This Field is used by the registration server, to determine whether he act as a foreign registration server and the registration request by rich of the end system to the real home registration server should.</li><li>3. Home Registration Server DNS name (DNS name of the home registration server). If the proxy registration prompt flag is TRUE (true), then this field is used in the DNS name access the home registration server. Otherwise, this ignored field. The DNS name is the foreign registration server translated into an IP address. The foreign registration server uses the IP address to the registration request the end system forward.</li><li>4. Foreign Domain Name (Stranger domain name). If the proxy registration prompt flag on TRUE (true), then this field is used to the strange domain name for the to identify home registration server of the end system. Otherwise this field is ignored. used the foreign registration server this information, to that of the foreign server in the SMTP format machine ID to produce, for example, machine @ fgdn. This machine ID is by the foreign registration server in the Radius Access-Request or Radius Access request sent to the home registration server.</li><li>5. Shared Secret (Shared secret code). If the Proxy registration prompt flag is (true) to TRUE, the shared secret code between the foreign and the home registration server used their identities to identify each other. Otherwise, the field is ignored.</li><li>6. Tunneling Protocol Parameters. This field is used to store used of parameters to the tunnel to the care of the end system configure. For an end system at home, it includes information on tunnel parameters between the base station and the home IWF and the home IWF to the PPP server. For a Roaming end system comprising tunnel parameters from the base station to serving IWF and the serving IWF to home IWF. For each tunnel contains this field at least the type to use for the tunneling protocol and any tunnel protocol-specific parameters. For example , the identifier for this field include the tunneling protocol L2TP and any additional parameters, which are required to the L2TP tunnel between the IWFD and configure their partner.</li><li>7. Accounting Server Association (Accounting Server Agreement). This field is used to store information by the IMF needs to generate accounting data for the end system. It contains the name of the accounting protocol (eg RADIUS), the DNS name the accounting server and additional Parameters for the payroll log are specific, such as the UDP port number, the shared secret, the IMF in Radius accounting or Radius accounting protocol it must use the frequency the checkpoint marker, the initial value for generating the session / multi-session ID etc. The DNS name of the accounting server in the IP address the billing server translates, which is sent to the IWF.</li></ul>

0194For Drahtlosdiensteanbeiter, have roaming agreements with each other, the HDD is used to authenticate and used to complete the registration process. When a End system is roaming from its home network to a foreign network, consult the foreign registration server in this network, the HDD in its MSC to get information about obtain the home registration of visitors-end system and to authenticate the home network before the visitors end system provided.

0195The software for the home domain directory management preferably represents an HDD management interface for system administrators ready pointing to a graphical user interface (GUI for eng. graphical user interface) based. By using this GUI, system administrators are able the entries view the HDD and update. This GUI is not Use intended by foreign wireless network service providers to perform remote updates based on roaming agreements. they is for use only by reliable personnel of the home wireless service provider determined and works behind firewalls.

0196The Foreign domain directory (FDD) provides functionality ready which is the reverse of the home domain directory. The FDD is used by home registration servers to parameters via the retrieve foreign registration server and the foreign network to the authenticate foreign network and a tunnel between a serving IWF and a home IWF to generate. These parameters include the secret code native-alien mutually shared, the configuration of the tunnel between the home IWF and-sufficient IMF etc. The FDD is preferably located in the MSC of Heimatregistrierungsserv ers. The FDD is the home registration server to register Gast-end systems used.

0197The following information is stored in the FDD: <ul><li>1. Foreign Domain Name. This field is a key when searching the FDD used for an entry of the FQDN the foreign registration server, the registration request the forwards matches.</li><li>2. Shared Secret. This is the shared secret code, uses between the foreign and the home registration server is, to mutually authenticate their identity.</li><li>3. Home IWF-Serving UWF Tunneling Protocol Parameters. This Field is used for storing parameters to the tunnel configure between the home IWF and the serving IWF. This field at least the type to use for the tunnel protocol and any tunnel protocol-specific parameters. For example, this Field identifier include the tunneling protocol L2TP and any additional parameters, which are required to the L2TP tunnel between the serving IWF and the home IWF to configure.</li><li>4. Accounting Server Association (Accounting Server Agreement). This field is used to store information by the home IWF to generate accounting data for the end system needed will. It contains the name of the accounting protocol (eg RADIUS), the DNS name the accounting server and additional Parameters for the payroll log are specific, such as the UDP port number, the shared secret, the use IMF Radius Accounting protocol needs, the frequency the checkpoint marker, the initial value for generating the session / multi-session ID etc. The DNS name of the accounting server in the IP address the billing server translates, which is sent to the foreign agent.</li></ul>

0198For wireless service provider, have roaming agreements with each other, the FDD is used to authenticate and used to complete the registration process. When a End system is roaming from its home network to a foreign network, consult the registration server in the home network, the FDD in its MSC to to get information and authenticate the foreign network, which supplies the end system.

0199The software for The foreign domain directory management preferably provides an FDD management interface for system administrator prepared, which is based on a graphical user interface (GUI). By using this GUI, system administrators are able to the entries in the FDD view and update. This GUI is not for use thought by foreign wireless network service providers in order on the basis of roaming agreements to perform remote updates. they is for use only by reliable personnel of the home wireless service provider determined and works behind firewalls.

0200The Internet service provider directory (ISPD) is the home IWF used to determine the ability of compound manage with ISPs that service agreements with the wireless service provider have, so that participants using the web on their access ISPs. For each Participants, the list of participants one entry for the ISP the subscriber on. This field points to an entry in ISPD. The home IWF uses this information to make the connection with the ISP for build the participants.

0201The supported network architecture Roaming. For roaming between wireless service providers work, the architecture must support the setting up of roaming agreements between wireless service providers. This brings two-fold: (1) updating system directories across wireless service provider and (2) payment of bills between service providers.

0202Around to allow subscribers access to internet service providers, supports the architecture roaming agreements with Internet service providers. This implies that the architecture must be able to send and data data to ISP PPP server to receive from ISP PPP servers (ie, industry-standard protocols as PPP, L2TP and Radius support). It also implies that the architecture directory updates for the edited ISP access and paying bills with ISPs unwinds.

0203If hit roaming agreements between two wireless service providers will have both Vendors update their home and foreign domain directories, to authentication and registration functions for end systems, visiting their networks from the other network support. The Architecture of the present embodiment supports at least manual directory updates. If a roaming agreement two wireless service providers is made, then replace the two Agreement Program Information for populating from their home and foreign domain directories. The actual Updates the directories is done manually by staff of each provider. If later, the information in the Home and foreign domain directories must be updated Swap the two partner agreement the updated information and then apply its updates manually to the directories at.

0204In an alternative embodiment, directory management software includes development standards in the IETF to roaming between Internet service providers to enable to empower and ISPs, roaming relationships automatically manage and identify. This makes a manual Directory assistance is no longer needed. spread the power system Roaming relationships automatically and determined to authenticate visitors end systems and to register.

0205The least processed network architecture and stores the accounting data and provides the data to the billing system the wireless service provider available. It lies on the billing system, paying bills for handle roaming.

0206In an alternative embodiment, are developing standards in the IETF to handle the distribution accounting records received between Internet service providers in the network architecture to to enable ISPs paying bills for perform host-end systems.

0207The supports system software access to IPS and private intranets by supporting the L2TPs between the home IWF and the ISP or intranet PPP server. The Internet service provider directory contains Information for the IMF are useful for creating these tunnels. If access agreements between the wireless service provider and internet service providers are established, this directory is the staff of the wireless service provider updated manually. Automatic updates and an automatic determination of access conditions between the wireless service provider and internet service providers are envisaged and be implemented as soon as the Internet standards further are developed. While the subscriber accesses an Internet service provider, it receives two bills - one from Wireless service provider for the use of the wireless network, and the second from the internet service provider. Although not common by the software the minimum embodiment charging, which the two kinds of fees united, is unwound, it is provided that the software Internet standards Bill payment, once they are developed, use, so participants a common bill based on roaming agreements between can receive the ISP and wireless service providers.

0208The System includes an element management system for managing the network elements on. lead from the element manager System administrators configuration, fulfillment and fault / alarm management functions out. The element management applications run on a Web browser. In Use manage a web browser system administrators the power from anywhere, from where they have a TCP / IP access. The element manager also performs an agent function for a parent Managers from. In this role it exports an SNMP MIB for Alarm and fault monitoring.

0209A parent SNMP manager is SNMP traps taught by alarm conditions. The parent SNMP manager asks the MIB of the element manager regularly with regard to health and the status from the network. The system administrative personnel at the parent Administrator is capable of creating a screen icon representation of the network view and its current alarm state. By pointing and Click on the network element symbol, the system administrative staff using a web browser element management applications perform and detailed management functions perform.

0210Within the network carried out the management of physical and logical Network elements using a combination of the SNMP protocol and internal management application programming interfaces. applications the element manager use SNMP or other management APIs the implementation of Network management functions.

0211Architectural includes an element management system, two different sets of Function elements. The first set of functional elements, which the Konfigurationsdatenserver-, Leistungsdatenüberwachungs-, health / status monitoring and network element recovery software includes, runs on an HA server equipped with RAID disks. The second Set of functional elements, which the management applications includes running on a dedicated non-HA-management system. Even when the Element management system is inoperable, the network elements are more able to run and report alarms, and they are even able from fault conditions to regenerate. However, since all management applications in the non-HA element manager run, then if the element manager fails, recovery actions, the intervention of people in need, not possible to the element manager is operable again.

0212The wireless hubs (reps) in the base stations typically include a Drahtlosdiensteanbeiter (WSP) and are Point-to-point connections, intranets or the Internet with the Registration Server (RS) of the WSP's connected. The WSP registration server is usually a software module running on a processor, to perform certain registration functions. Interworking function units (IWF units) are typically software modules running on a processor, to perform certain connection functions. The IMF units normally Intranets / WAN connected to the registration servers, and the IWF units belong normally the WSP. However, the IMF units need not within the same LAN to be arranged as the registration server. Normally billing and directory servers (also Software modules running on a processor) via a LAN in the data center the service provider (eg, having a center, the one or more processors and various servers and other software modules as host serves) connected to the registration servers. Traffic from the end system is then a router (connected to the LAN) to the public Internet or an ISP intranet passed. The registration server, which is in a WSP foreign network, is as the foreign registration server (FRS) refers, and the registration server in the home network the end system (where the mobile unit acquires their service) arranged is referred to as the home registration server (HRS). The Interworking function unit in the home network as the home IWF is referred to as the Interworking function in the foreign network (ie the network, which is visited from the end system) as the serving IWF is called.

0213For fixed wireless services (ie, a non-moving end system) can an end system in a Service on the home network from the home network (eg to-home service) or from a foreign network (eg, a roaming service) register leave. The receiving end system an announcement, by an agent (eg, an agent function in software is implemented) sent in the wireless hub via the access point becomes. It is both a MAC-layer registration as well as to accomplish a network layer registration. These can be to improve effectiveness linked.

0214For end system at home (<figref idrefs="S144">26</figref>) Is the network layer registration (Like a local registration) on the wireless hub to which the end system just connected is sent to the home registration server. An IWF in the home network the end system is the anchor or home IWF. In this way, PPP frames plant and from the end system via the wireless hub continues to home IWF in the home network. If the end system is at home, the home IWF is a Xtunnel protocol with the wireless hub.

0215for a wireless roaming service (<figref idrefs="S145">27</figref>) If the foreign registration server during the registration phase the identity of the home network for the roaming end system fixed. Using this information, communicates the foreign registration server to the home registration server, to authenticate the end system and to register. The stranger Registration server then assigns a serving IWF, and it is an I-Xtunnel Protocol connection between the home IWF and the serving IWF for the roaming end system prepared. The serving IWF passes frame between the wireless hub and the home IWF on. From the home IWF are data to a PPP server (ie, point-to-point protocol server) sent, seated in the same IMF. However, if the data to a corporate intranet or an ISP's intranet that his should have their own PPP server, go, the data on the be sent L2TP protocol to the separate PPP server. The separate belongs Server usually an Internet service provider, the wireless service provider is different, and is operated by the latter. For the duration the meeting remain fixed the whereabouts of the home IWF and the PPP server. The MAC layer registration can with the network layer registration connected are to overhead of separate communications for MAC layer and save the network layer registration; however, it may advantageously be not to link these registration processes so the WSP resources with other wireless networks, which only the IETF Mobile IP support, can cooperate.

0216A Registration creates three tables. A Table 1 each associated access point, and Table 1 identifies each connection (That is, each end system) by a connection ID (CID for engl. connection ID) and assigns the connection ID in a specific Drahtlosmodem- or WM address (WM for eng. wireless modem) (ie, the address of the end system or the End system) to. A table 2 is associated with each wireless hub (WH) and Table 2 associates each connection id corresponding wireless modem address, Access point and a Xtunnel ID (XID) to. A Table 3 each Interworking function (IMF) associated with, and Table 3 associates each connection id a corresponding wireless modem address, Drahtloshubadresse, Xtunnel ID and a corresponding IP Port (IP / port) to. The for this Tables described items are shown to contain only relevant entries, the discussion for mobility management contribute. In reality, there are other important fields that also must be included. table 1: connection table at AP <img img-content="tb" img-format="tif" he="13" wi="65" file="00980001.tif" /><img img-content="tb" img-format="tif" he="13" wi="65" file="00990001.tif" /> table 2: connection table at WH <img img-content="tb" img-format="tif" he="33" wi="102" file="00990002.tif" /> table 3: connection table at the IMF <img img-content="tb" img-format="tif" he="39" wi="126" file="00990003.tif" />

0217The Protocol stack Dialup users at home in a network, as well as for Guest users are in <figref idrefs="S146">28</figref> to <figref idrefs="S149">31</figref> shown. <figref idrefs="S146">28</figref> illustrates protocol stacks for direct Internet access through a fixed (ie, non-moving) end system be used at home, where a PPP protocol message in the Home IWF (normally housed collocated with the wireless hub) ends, which the message to and from an IP router and from there the public Internet forwards. <figref idrefs="S147">29</figref> illustrated Protocol stacks for Internet remote access (ie, either private corporate networks or an ISP) by a fixed (ie, non-moving) end system be used at home, where a PPP protocol message by the home IWF (normally housed collocated with de wireless hub) forwards to a PPP server of the private corporate intranet or ISP. <figref idrefs="S148">30</figref> illustrates protocol stacks for direct Internet access by a walking, but fixed (ie not moving) or a moving end system be used, with the PPP protocol in the home IWF (typically in a mobile switching center the home network disposed) ends, which delivers the message and forwarding of an IP router. Note in<figref idrefs="S148">30</figref>How the message traffic in addition to the home IWF a serving IWF (typically collocated with the wireless Hub housed) happened. <figref idrefs="S149">31</figref> illustrated Protocol stacks for Internet remote access (ie, either private corporate networks or an ISP) by a wandering, but fixed (ie not moving) or a moving end system are used to, with a PPP protocol message by the home IWF (typically in a mobile switching center the home network arranged) to a PPP server of the private corporate intranets or ISPs is forwarded. Note in<figref idrefs="S149">31</figref>How the message traffic in addition to the home IWF a serving IWF (typically collocated with the wireless Hub housed) happened. If the serving IWF and the wireless Hub collocated on the same computer set housed or even in the same computer are programmed, it is not necessary to provide a Tunnel using the Xtunnel protocol between the serving IWF and the wireless hub to build.

0218equivalent Variants of this protocol stack (for example, the RLP for mobile units at home on wireless hub instead of the serving IWF or the Home IWF are completed) are also provided. If the IMF located remotely from the wireless hub, and the packages potentially on a transmitted lossy IP network between the IWF and the wireless hub can be, It is preferable that the RLP protocol ends on the wireless hub. Another variant is that the Xtunnel between the wireless hub and the IMF does not have the UDP / IP up to be needed. Xtunnel can using the frame relay / ATM link layer being constructed. The use of UDP / IP makes it easier, however, the Drahtloshub- and IMF software from one network to another to move.

0219It can four handoff scenarios take place, and they are referred to as follows: (i) local mobility, (Ii) micro-mobility, (Iii) macro mobility and (iv) global mobility. In none of the four scenarios (in one embodiment of the invention) a Leitwegoptimierungsoption considered so that the whereabouts the home registration server and the ISP PPP server does not change. In Alternatively, the invention with route optimization can change the ISP PPP server. This aspect is, however, discussed below. In addition, the locations change the foreign registration server and IWF in the first three scenarios not.

0220Of the proposed Mobile-IP standard by IETF requires that an end system, whenever the IP subnet changes to which it is connected, a registration request message sends to the home agent in its home subnet. These news performs Guest address, under the reached the end system in the new subnet can be. When traffic, for example, from an ISP to an end system Sending begins the home agent traffic destined for the end system, and transmits the traffic then the host address. identifies the host address a particular foreign agent in the foreign subnet. The stranger Agent of an end system may in the end system or in a separate node sitting, which in turn transmits the traffic to the end system (Ie, a proxy registration agent). Mobile IP handoffs refer to the exchange of control messages between the agent an end system, the home agent of a terminal system and possibly its corresponding hosts (CHs for eng. CORRESPONDING hosts) a (at Leitwegoptimierungsoption).

0221For the proposed would the Mobile IP standard from IETF it difficult to latency and Skalierbarkeitsziele for all movements in a large to achieve interconnection network. The present hierarchical mobility management but achieved such goals. For small movements (eg a change of access points) only MAC-layer registrations needed. For larger movements Network layer registrations are performed. The present hierarchical mobility management differs from the flat-structure used in the IETF of the proposed Mobile IP standard is used, and the model of-sufficient / Anchor interworking function, the in cellular systems like CDPD (based on a standard, which is promoted by the Forum of digital cell packet data) is used.

0222As in <figref idrefs="S150">32</figref> shown, wraps the local mobility handoff Endsystembewegungen (as MN for mobile node, mobile node) between APs from which to same wireless hub includes. Therefore is only one MAC-layer re-registration is required. The end system receives a Drahtloshubankündigung from a new AP and responds with a registration request, that is addressed to the new AP.

0223Of the new AP (ie AP, the registration request from the end system receives) creates new entries in its connection table and forwards the registration message to its wireless hub on. In local mobility handoffs changes the wireless hub not. The wireless hub recognizes the registration request the end system as a MAC level registration request and update them in its connection table to obtain the compound to reflect the new AP. Then delete the old AP the connection entry from its connection table. There are at least three ways like the old AP the old entries delete can, namely (I) timed, (Ii) upon receipt of a copy of the relayed MAC layer agreement message from the new AP to the wireless hub (if this information notice a round end message), and (iii) on notification with the wireless hub via the Need to delete the entry.

0224As in <figref idrefs="S151">33</figref> shown, wound the micro mobility handoff Endsystembewegungen (as MN for mobile node, mobile node) between wireless hubs from which belong to the same registration server and where the end system still can be powered by the existing serving IWF. If an announcement received from a new wireless hub (through a new AP) is, the end system sends a message to the registration server inviting them to register. The registration request is from the new AP to the new wireless hub to the registration server forwarded.

0225If the registration server determines that the existing IWF yet can be used, the registration server sends a build Xtunnel request or build XTunnel prompt reply request the existing IWF, a Xtunnel to the new wireless Hub build. Later sends the registration server a tear down Xtunnel request or tear XTunnel request message, to the existing IMF prompt, the existing Xtunnel with the old wireless hub degrade. The XTunnel-'s structural and tear XTunnel prompt messages can linked in a message will. A foreign registration server transmits the registration message not to the home registration server, as there is no change from IMF is neither the serving still the home IWF is,.

0226by Receiving a positive build XTunnel reply and a positive Xtunnel degradation response from the IWF sends the registration server a registration reply to the end system. As the registration reply reaches the new wireless hub, the connection table at the new wireless hub is updated to the connection to the new AP to reflect. The new AP updates its MAC filter address table and connection table after receiving a message from the new wireless hub, and the registration reply is forwarded to the end system.

0227Of the Registration server sends a release message to the old wireless hub. when the old wireless hub, the release message receives, it updates its connection table and the MAC filter address table and the connection table of the old AP.

0228As in <figref idrefs="S152">34</figref> shown, wraps the macro mobility handoff Movement between wireless hubs from which, although a change of bring serving IWF in the foreign network with them, but no change bring the registration server with it. If an announcement received from a new wireless hub (through a new AP) is, the end system sends a message to the registration server the network layer registration prompt. The registration request is from the new AP to the new wireless hub to the registration server forwarded.

0229Of the Registration server recognizes that it is a foreign registration server is if the end system is not to the network of the current registration server belongs. This foreign registration server determines the identity of the home registration server by using a request, preferably a Radius Access or Radius Access request (RA request) to the remote directory server (Like a big Yellow Pages), and he then assigns an appropriate IWF to order the serving to be IMF and transmitted a registration request to the home registration server, preferably through a Radius Access request (RA request), to the home registration server of the newly selected IWF to inform.

0230Of the Home registration server authenticates the registration request by using a request, preferably a Radius Access or Radius Access request (RA request), to the home directory server. After authenticating the request and determining that the existing home IWF still can be used, the home registration server the home IWF to a new I-Xtunnel for newly assigned serving build IMF and supplying the existing I-Xtunnel to old IMF degrade. Upon receiving a positive build I-XTunnel setup response sends a positive and I-tear XTunnel reply from the home IWF the home registration server a registration reply to the foreign registration server.

0231Of the foreign registration server then instructs the newly assigned IWF, build a Xtunnel the new wireless hub. After receiving a positive build XTunnel Answer , the foreign Registration server the old IMF, the Xtunnel to the old wireless hub degrade. Upon receiving a positive Build XTunnel reply and a positive tear XTunnel response sends the foreign registration server a registration reply to the end system.

0232If the registration reply reaches the new wireless hub, is the connection table updated on new wireless hub to to reflect the connection to the new AP. The new AP updates its MAC filter address table and connection table after receiving a message from the new wireless hub, and the registration reply is forwarded to the end system.

0233Of the Registration server sends a release message to the old wireless hub. When the old wireless hub, the release message receives, it updates its connection table and the MAC filter address table, and the old AP updates its MAC filter address table and connection table after receiving a message from the old wireless hub.

0234The global mobility handoff handles movement between wireless hubs from which a change bring the registration server itself. <figref idrefs="S153">35</figref> illustrated global mobility switching, wherein the home IWF does not change, and <figref idrefs="S154">36</figref> illustrates a global mobility handoff, wherein the home IWF changes. If an announcement from a new wireless hub (through a new AP) in a foreign network is received, the end system sends a message to the foreign prompt registration server to Netzuschichtregistrierung. The registration request is from the new AP to the new wireless Hub to the new foreign registration server forwarded.

0235Of the Registration server recognizes that it is a foreign registration server is if the end system is not to the network of the current registration server belongs. This foreign registration server determines the identity of the home registration server by using a request, preferably a Radius Access or Radius Access request (RA request), to the foreign directory server (Like a big Yellow Pages), and he then assigns an appropriate IWF to order the serving to be IMF and transmitted a registration request to the home registration server, preferably through a Radius Access request (RA request), to the home registration server of the newly selected IWF to inform.

0236Of the Home registration server authenticates the registration request by using a request, preferably a Radius Access or Radius Access request (RA request), to the home directory server. After authenticating the request and determining that the existing home IWF can still be used (<figref idrefs="S153">35</figref>) includes the home registration server to the home IWF, a new I-Xtunnel to serving IWF, the new through the new foreign registration server has been assigned to build. The home registration server sends also a message for deletion from the register of the old foreign registration server and has the home IWF to the existing IT tunnel to the existing serving reduce IWF of the old foreign network. Upon receiving a positive I build XTunnel Answer and a positive I-tear XTunnel reply from the home IWF sends the home registration server a registration reply to the new foreign registration server.

0237Of the new foreign registration server then instructs the newly assigned IMF to build a Xtunnel the new wireless hub. by Receiving a positive build XTunnel reply sends the foreign registration server a registration reply to the end system. As the registration reply to the new wireless achieved hub, the connection table at the new wireless hub is updated to reflect the connection to the new AP. Of the new AP updates its MAC filter address table and its Connection table after receiving a message from the new wireless Hub, and the registration reply is forwarded to the end system.

0238Of the old foreign registration server, the old IMF, the Xtunnel to the old wireless hub degrade. Upon receiving a positive Tear XTunnel reply or simultaneously with the tear XTunnel request sends the old foreign registration server a release message to the old wireless hub. When the old wireless hub, the release message receives, it updates its connection table and the MAC filter address table, and the old AP updates its MAC filter address table and connection table after receiving a message from the old wireless hub.

0239Alternatively chooses the Home registration server once the home registration server the registration request from the new foreign registration server authenticates and determined that the existing home IWF can no longer be used (<figref idrefs="S154">36</figref>) a new home IWF and instructs the new home IWF, a new Layer 2 tunneling protocol tunnel (L2TP) tunnel) at the present PPP server (Eg the PPP server in a connected ISP intranet) build. Then, the Home registration server, the old home IWF to, its L2TP tunnel traffic to transfer to the new home IWF.

0240Then includes the home registration server, the new home IWF to a new I-Xtunnel to serving IWF, passing through the new foreign was registration server reassigned to build. The home registration server also sends a message for deletion from the register to the old foreign registration server and instructs the home IWF, the existing I-Xtunnel to existing serving IWF of the old foreign network degrade. After receipt of a positive I build XTunnel response and a positive I-tear XTunnel Answer sends the home registration server a registration reply to the new foreign registration server.

0241Of the new foreign registration server then instructs the newly assigned IMF to build a Xtunnel the new wireless hub. by Receiving a positive build XTunnel reply sends the foreign registration server a registration reply to the end system. As the registration reply to the new wireless achieved hub, the connection table at the new wireless hub is updated to reflect the connection to the new AP. Of the new AP updates its MAC filter address table and its Connection table after receiving a message from the new wireless Hub, and the registration reply is forwarded to the end system.

0242Of the old foreign registration server, the old IMF, the Xtunnel to the old wireless hub degrade. Upon receiving a positive Tear XTunnel reply or simultaneously with the tear XTunnel request sends the old foreign registration server a release message to the old wireless hub. When the old wireless hub, the release message receives, it updates its connection table and the MAC filter address table, and the old AP updates its MAC filter address table and connection table after receiving a message from the old wireless hub.

0243end systems, which according to the present Invention are constructed, interact with networks, the proposed in accordance with the Mobile-IP standards of IETF are built up, and end systems according to the proposed Mobile-IP standards of IETF are constructed interact with networks, which according to the present Invention are constructed.

0244The Main differences between the present invention and the IETF Mobile IP (RFC2002, a standard document) are: <ul><li>(I) The present invention uses a hierarchical approach to mobility management rather than a flat structure as in the proposed IETF Mobile-IP standard. A small mobility resulting in a small area no network-level registration. A micro-mobility brings the construction of a new XTunnels and the dismantling of existing XTunnels with it. A global mobility brings at least the construction of a new I-XTunnels and the dismantling of existing I-XTunnels apart from the fitting / removal the XTunnels with it. Global mobility brings sometimes the Construction of a new L2TP tunnels and the transfer L2TP state from the existing L2TP Tunnel to the new L2TP tunnel with it.</li><li>(Ii) In the present invention, a user name plus an area for identifying a remote dial-up user instead of a fixed home address as in the case of the proposed IETF Mobile IP standards used. </li><li>(Iii) In the present invention, registration and Routing functions performed by separate entities. The two functions be in the proposed IETF Mobile-IP standard by the home agent executed and both functions are in the proposed IETF Mobile-IP standard executed by the foreign agent. In contrast, in an embodiment of the present Invention, the registration in the registration server performed and Routing functions are both the home and serving IWF and the wireless hub (also called access hub) executed.</li><li>(Iv) The present invention utilizes three tunnels per PPP session. The Xtunnel is more like a link layer tunnel between the wireless hub and the serving IWF. The I-Xtunnel between the serving IWF and the home IWF is more like the tunnel between home and foreign agents in the proposed IETF Mobile-IP standard. But He also has additional Skills on, over and above those proposed by the Mobile IP standard tunnel beyond. The L2TP tunnel is used only when the home IWF no PPP server is. The number of these tunnels can by combining some functions in the same node, as described above, be reduced.</li><li>(V) In the present invention finds a wireless registration place before a PPP session begins while the proposed IETF Mobile-IP standard takes place a Mobile IP registration, After a PPP session enters the open state. </li><li>(Vi) In the present invention, the network entity which the agent advertisement (Ie, the wireless hub) announces, not on a direct link to the end systems whereas for the proposed IETF Mobile-IP standard the agent advertisement must have a TTL of 1, which means that the end systems a have direct connection to the foreign agent. It should also the agent advertisement in the present invention, no extension to the ICMP router advertisements as in the proposed IETF Mobile-IP standard.</li></ul>

0245end systems in the present invention should support an agent polling. If an end system in the present invention, a visited network, which the proposed IETF supports Mobile IP standard, waits it until it an agent advertisement listen. If there is no agent advertisement within an acceptable time frame receives, it sends an agent call around.

0246In the present invention may Network operators with other networks that support the proposed IETF Mobile-IP standard, such Negotiate that the end systems of the present invention, the other networks want to use, Home addresses can be assigned. If the end system of the present invention receives the agent advertisement, can find it, that the power which it visited, no power of the present Invention, and consequently uses the assigned home address, to register.

0247For networks, support the proposed IETF Mobile-IP standard, the PPP session starts before the Mobile IP registration, and it is likely that the PPP server accommodated in such networks collocated with the foreign agent is. In one embodiment, is a SNAP header used to PPP frames in the MAC frame of the present encapsulate invention (in a manner similar to the Ethernet format example), and the foreign agent interprets this format as proprietary PPP format over Ethernet encapsulation. Therefore can the end system of the present invention and its PPP partners in a open state occur before the foreign agent a agent advertisement transferred to begins, and the end system of the present invention may be register.

0248Around End systems, the proposed IETF Mobile-IP standard support to allow, in Networks to work on the nature of the present invention are Such mobile units at least capable of similar MAC layer registrations perform. By performing the agent advertisement message format similar to Agent advertisement message format according to the proposed IETF Mobile-IP standard, a visitor-end system the agent advertisement interpret and register with a wireless hub. In the present invention are Registrierungsaufforderungs- and registration reply messages similar to Registrierungsaufforderungs- and registration reply messages to the proposed IETF Mobile IP standard (without any unnecessary extensions), such that the rest of the mobility management features of the present invention for visitors-end systems is transparent.

0249There End systems that support the proposed IETF Mobile-IP standard, expect that a PPP session starts before Mobile IP registration, begins an optional feature in wireless hubs of the present invention PPP, LCP and NCP packets to be interpreted according to the MAC layer registration.

0250Around to avoid being lost in handoffs traffic, used mobility management the present invention, the NO-before break concept. For local mobility is a Make before break contact connection by converting the MAC-layer registration message, which is passed through the new AP to the wireless hub, in reaches a round end message. In this way, the old AP hear from the new registration and transmit packets, the for the end system are intended and not transferred to the new AP were.

0251For micro mobility information about added the new wireless hub in the Xtunnel-release message, the exchange between the serving IWF and the old WH becomes. In this way, the old wireless hub, in a hearing Xtunnel-release message of the serving IWF transmit buffered packets. Alternatively knows the RLP layer at the IWF, the sequence number, the old by the wireless hub confirmed so far has been.

0252simultaneously knows the IMF, the current send sequence number of the last packet, which was sent to the old wireless hub. Therefore, the IMF those packages that angeord between these two numbersare net, transfer them to the new wireless hub, before newer packets to the new wireless hub. It is believed that the RLP layer is able to double Filtering packets. The second solution is the first solution probably preferable because the old wireless hub may is unable to communicate directly with another.

0253For macro mobility, the old serving IWF addition to the packet transmission, from the old wireless hub takes place at the new wireless hub, packages transmit to the new serving IWF. Everything is to be done, is the identity of the new serving IWF to forward in the I-tear XTunnel message to the new serving IWF. Another possibility, to achieve the same result, is the home IWF in the missing to let transmit packets to the new serving IWF, instead to ask the old serving IWF to do this, since the home IWF I-Xtunnel sequence number, which was confirmed as the last of the old serving IWF, and the current I-Xtunnel sequence number, that was sent by the home IWF knows.

0254The A method of estimating, how much buffer per mobile unit per AP per wireless hub per IMF should be allocated in such a way that a loss of traffic between Handoffs can be minimized is the end system for the AP for the wireless hub for the IMF, the packet arrival rate and the indexing time to appreciate leave. This information is to the old AP of the wireless Hubs passed the IMF to determine how much traffic at should be entrusted to handoffs at each of the new AP.

0255Around To achieve route optimization in the present invention, chooses the The end system's PPP server, the closest to the serving IWF is. Without route optimization, excessive transport delays and excessive use the physical line happen.

0256To the Example, an end system that a subscription to a home network in New York City has, migrate to Hong Kong. To connect produce between an ISP in Hong Kong, the end system would have a serving IMF, which is set up in a wireless hub in Hong Kong, and a home IWF, the furnishings in the home network in New York City is having. A message would then from the end system (migrated to Hong Kong) by the serving IWF (in Hong Kong) and the home IWF (in New York City) and back are routed to the ISP in Hong Kong.

0257A preferred solution is, by the serving IWF turn on (in Hong Kong) directly to the Hong Kong ISP. The serving IWF acts like the home IWF. In this embodiment, consist roaming agreements between foreign and de home wireless providers. Also communicate the various accounting / billing systems automatically each other, so that the account information is shared will. The accounting and billing information exchange may be performed using such standards as the standard, the proposed by the ROAMOPS working group of the IETF.

0258The serving IWF but still the closest PPP server (needs to For the Hong Kong ISP) determine. In the present embodiment undergoes the foreign registration server of the end system's desire to connect with a PPP server (eg a Hong Kong ISP) when a registration request receives from the end system. If the foreign registration server determines that the serving IMF closer the desired PPP server (eg the Hong Kong ISP) than the home IWF has the foreign registration server, the serving IWF to, an L2TP tunnel to its nearest PPP server produce (in contrast to the PPP server, which is closest to the Home registration server and the home IWF is). Then informed the foreign Registration server to the home registration server that the end system is powered by the serving IWF and the foreign PPP.

0259In an alternative embodiment, determines the foreign registration server that the serving IWF closer to desired PPP server (eg, the Hong Kong ISP) than the home IWF when a registration request receives from the end system. The foreign registration server forwards the registration request message with an attached Message, which information the serving IWF indicating and an announcement that route optimization is preferred further to the home registration server. simultaneously , the foreign registration server, the serving IWF to a produce L2TP tunnel to the PPP server. After approving the registration request , the home registration server the home IWF to the L2TP state be transferred to the foreign IWF.

0260After this , preferred (serving for illustrative and not limiting) executionto form a novel network architecture with wireless end users, the are to migrate capable has been described, it should be mentioned that in view of the teachings set forth above modifications and variations may be made by professionals. For example, the Links which have been described herein in known Link protocols (eg IP, TCP / IP, L2TP, IEEE 802.3, etc.) make reference; However, the invention provides other connection protocols in the links before having the same or similar Data delivery capabilities provide. The agents, acting in the above-described embodiments can be in the form of software-controlled processors, or they can be a Another form of control (eg, programmable logic arrays) be. The acting agents can be grouped, as described above, or otherwise grouped be connecting teachings as long as they described to herein hold and the security and authentication teachings as described herein, subdue. also , a single access point (ie wireless hub) or one interworking function unit (IWF unit) a multi-channel capability provide. In this way, a single access point or Access hub or a single IWF unit to the traffic from multiple End systems to act and what to herein as separate access points, Zugangshubs or IWF units describes sees a correspondence with a single before multi-channel access point, or -Zugangshub -IWF unit.