FI111586B - Manage the migration adapter on the gateway server - Google Patents

Abstract

The invention relates to a gateway where bearer adapters are managed dynamically, thus allowing adding new bearer adapters dynamically while the gateway server is able to communicate with already existing bearer adapters. Also according to the present invention the gateway server has been arranged to enable deleting bearer adapters dynamically while the gateway server is able to communicate with still existing bearer adapters. The invention also relates to a method for managing bearer adapters and to a computer program product for managing bearer adapters at a server.

Description

111586

Manage the migration adapter on the gateway server

The present invention relates to the management of transport adapters 5 in a gateway server. It is particularly suited to a mobile protocol such as WAP (Wireless Application Protocol) to allow a mobile terminal to access the Internet.

The term '' Internet 'is commonly used to describe information, content that can be accessed using a terminal, typically a PC connected via a modem to a telecommunications network. Content can be stored in many different locations remote from the connecting computer, although each remote location is also connected to a telecommunications network. Content can be built using HTML (HyperText Mark-up Language). The Internet is made operational by a specification of 15 standard information systems that use multiple protocols, such as TCP (Transfer Control Protocol), UDP (User Datagram Protocol) and IP (Internet Protocol), to control the flow of information over a number of different components of the Internet. TCP and UDP apply to preventing and correcting errors in transmitted Internet data. IP refers to structuring and routing data.

In addition, other application-specific protocols may be provided to manage and manipulate various information available over the Internet, such as accessing HTTP HTML content, accessing FTP files, or accessing SMTP e-mail.

25 The Internet is physically built around the hierarchy of telecommunications and data communication networks, such as local area networks (LANs), regional telephone networks and international telephone networks. These networks are internally and externally connected by so-called "" routers ", which receive information from the source host or previous router in the transmission chain and route it to the destination host or subsequent router in the transmission chain.

As the use of mobile phones increases, so does the need for a mobile Internet connection, from a laptop connected to a mobile phone or an integrated computer / mobile device. Such. 111586 2 is typically intended to obtain content from the Internet. It has also been proposed to provide Internet access to advanced mobile terminals, so-called communicators and smartphones, e.g. via WAP (Wireless Application Protocol). WAP has an architecture with a protocol stack having 5 application layers (called Wireless Application Environment or WAE), a session layer (called Wireless Session Protocol or WSP), a connection event layer (called Wireless Transaction Protocol or WTP), a security layer (called Wireless Transport Layer Security or WTLS) and Transport Layer (called Wireless Datagram 10 Protocol or WDP) as shown in Figure 1. The layers above, as well as other services and applications, access each layer of the architecture. These protocols are designed to work across a variety of bearer services such as Short Message Service (SMS), Circuit Switched Data (CSD), General Packet Radio Service (GPRS), etc. The specification for the WAP architecture and protocol layers is available at htm: // www .wapforum.org /.

One of the WAP specifications found in the URL above is the Wireless Datagram Protocol (WDP) specification. It determines that there is an application layer (Adaptation Layer) between the WAP stack and the bearers. An application layer is a WDP-20 protocol layer that maps WDP protocol functions directly to a particular bearer. The application layer is different for each bearer and handles specific capabilities and features of that bearer service. In addition, in the WAP gateway or server, the application layer is also called a tunnel (Tunnel), which terminates and forwards WDP packets to the WAP-25 proxy / server through a tunneling protocol, which is the interface between the gateway supporting the bearer service and the WAP proxy / server.

The application layer, or Bearer Adapter, as it is called in this document 30, is thus a component that connects the WAP server to the wireless network. Thus, multiple gateways must have multiple gateways to support multiple gateways. New networks will become available as networks evolve. For example, GSM GPRS is not yet in use, but it is estimated to be operational within one or two years. Third generation • 111586 3 systems are also expected to be operational within two to five years. Thus, operators and companies that maintain gateway servers, such as WAP gateways, will likely need to upgrade the server to support new bearers. A gateway may also be provided which initially has only one bearer and then adds other bearers to complement the range by serving different clients (i.e. terminals that support a particular bearer). The protocol stack (WAP stack in WAP) must support every transport adapter.

A gateway has now been invented, where the migration adapters are dynamically controlled 10, thus allowing new dynamical adapters to be dynamically added, both after installation of the gateway server and while being able to communicate with other existing adapters. Also according to the present invention, the gateway server is configured to enable the removal of migration adapters dynamically, both after the installation of the gateway server 15 and while the gateway server is able to communicate with other still existing transport adapters.

Allowing the addition and / or deletion of gateway adapters while the gateway server is able to communicate with the existing gateway adapters 20 is advantageous since it allows the gateway adapters to be managed without interrupting the operation of the gateway server. Thus, the migration adapters can be added without restarting the server.

In a preferred embodiment of the invention, the dynamic insertion of the transport adapters is accomplished by creating a new thread in the protocol stack for each transport adapter. In this way, the new stack adapter is supported by the protocol stack, without having to stop the gateway server to reconfigure the protocol stack. Dynamic deletion of migration adapters is accomplished by providing a transport port between the transport adapter and the protocol stack 30, where deleting the transport adapter results in deleting the specific transport adapter from the transport port memory, although in that particular embodiment the thread remains in the protocol stack until next time. The bearer port monitors that the protocol stack is not trying to send anything to the removed bearer adapter.

5 111586 4

Further, the management and control of migration adapters has been simplified with a graphical user interface that allows the administrator to both dynamically add and remove migration adapters with simple choices made through the graphical user interface.

According to a first aspect of the invention, there is provided a server for managing transport adapters which each transport adapter uses to communicate with a terminal over a particular wireless network, comprising: means for dynamically adding a transport adapter to the server while the server is capable of communicating with existing transport adapters.

In one particular embodiment, the invention comprises a gateway server serving a plurality of mobile terminals. It can be a WAP gateway.

For example, commands such as WAP requests can be sent in short message messages (produced by SMS) and sent to the WAP / HTTP gateway. The gateway interprets these as WAP packets and executes the necessary HTTP connection events on the origin server. It then sends back the WAP message on the same bearer, i.e. as a result SMS.

20

In another particular embodiment, the server comprises generating means for generating a thread in response to the insertion of the transport adapter and pointing means for pointing the created thread to the inserted transport adapter.

In accordance with another aspect of the invention, there is provided a method of controlling migration adapters used by a server for communicating with a terminal over a specific wireless network, comprising: dynamically adding a migration adapter to a server while the server is able to communicate with existing migration adapters.

The migration adapter is added by creating a specific thread to which the inserted migration adapter is addressed.

More specifically, the thread is created in a wireless protocol stack. Further, in the method of the invention, the migration adapter 111586 is dynamically removed from the server while the server is able to communicate with the existing migration adapters.

According to a third aspect of the invention, there is provided a computer program product 5 for managing transport adapters on a server used by each transport adapter for communicating with a terminal over a particular wireless network, comprising: machine-language programming means for dynamically

The invention is preferably implemented as software that, when downloaded to a computer, acts as a gateway server according to the present invention.

The invention will now be described in detail with reference to the accompanying drawings, in which Fig. 1 illustrates a protocol stack arrangement in WAP (Wireless Application Protocol), 20 Fig. 2 illustrates a communications system, Fig. 3 illustrates a gateway interface embedded in hardware, Fig. Figure 6a shows a portion of a graphical user interface for enabling dynamic adapter control according to the present invention, Figure 6b shows a portion of a graphical user interface for enabling configuration of transfer adapters, Figures 7a-d show signaling and between functional blocks when creating, starting, stopping the migration adapter and removal.

111586 6

In the following example, communication is described with reference to the WAP (Wireless Application Protocol) mentioned above. It should be noted that the invention is not limited to the use of WAP, and other protocols and specifications may be used.

Figure 2 illustrates a communication system comprising a plurality of mobile terminals 2 having access to the Internet 4. The mobile terminals transmit signals 6 which are received and transmitted by the wireless network 8. A wireless network may be a variety of network systems, such as GSM, CDMA IS-95, TDMA IS-136, and UMTS, and may use different types of communication within one and the same system 10, e.g., SMS, GPRS, or HSCSD communication within GSM. . Thus, several different transmission paths can be used to transmit the signals 6. The WAP requests 6 received by the network 8 are routed to the proxy or gateway server 12. The server 12 translates the WAP requests into HTTP requests and thus allows the mobile terminals 2 to request information from the web server 14 and thus browse the Internet 4. The proxy 15 encodes the information received from the web server 14. a suitable format, and then transmitted by the wireless network to the mobile terminal 2, which requested it. The answer comprises WML (Wireless Mark-up Language). WML is a title-based display language that provides navigation support, data entry, hyperlinks, text and slideshow, and forms. It is an HTML-like 20 browsing language. The mobile terminal 2 processes and uses the information. If the web server 14 provides the content in WAP / WML format, the server 12 may retrieve such content directly from the web server 14. However, if the web server provides the content in the web format (such as HTML), the filter may be used to translate the content from the WAP / WML format.

25 WAP is applicable to a variety of systems including GSM-900, GSM-1800, GSM-1900, CDMA IS-95, TDMA IS-136, Broadband IS-95 and third generation systems such as IMT-2000, UMTS and W-CDMA .

Although Figure 2 shows information to be retrieved from the Internet, the proxy itself may contain the desired information. For example, the subscriber may retrieve information from the proxy file system.

In addition to the web server 14, the mobile terminals may communicate with the WTA server 18 (Wireless Telephony Application). Other types of origin servers are also possible.

Figure 3 shows a gateway server embedded in hardware, such as computer 20. Computer 20 has dynamic memory, processing power, and memory for storing all the programs needed to execute the gateway server, such as application program, protocol stack, and operating system.

The computer 20 comprises a user interface such as a keyboard 22 and a server program 24 of the display 23 and 10. The server program 24 has an application program 26 for handling the protocol events below, such as requesting a WML server request, and protocol stacks such as WAP protocol stack 28 and HTTP protocol stack 30. data flows, including instructions, requests and information, between the computer and various networks, including 15 dial-up networks 32, the Internet 34, and the data network and circuit-switched data networks 35. The application program 26 may further execute a program visible on screen 23 and controlled by keyboard 22 e.g. with a mouse). Computer 20 communicates with Internet 34 via HTTP protocol stack 30 and interface 36. Computer 20 communicates with telephone network 34 and computer network 35 via interfaces 38 and 40.

The server program 24 also comprises a gateway 42 that converts between HTTP and WAP. SMS messaging can be provided through a data interface via appropriate hardware to the operator's network.

Individual threads 44 25 in application program 26 and WAP protocol stack 28 use processors 46 in computer 20 to perform the necessary processing tasks. Threading for processors is provided by the threading services 48 in the operating system 50 of the computer 20.

As shown in Figure 1, the WAP stack is built on so-called transmission paths 30 (which provide data telecommunication services). These bearers can be, for example, SMS or CSD. The transfer paths have their own protocol and are implemented through protocol stack implementations.

111586 8

Figure 4 shows a functional block diagram (included in software) of a gateway server according to the present invention, at least to the extent that the invention is understood. The gateway server includes a Wireless Protocol Stack (WPS) 50, such as the WAP stack shown in Figure 1. Below the WPS 5 are various transport adapters 51 which access different paths via the transport drivers 52. Now, a bearer port 53 is provided between the WPS and the bearer adapters, which isolates the WPS bearer from the bearers and controls the starting and stopping of data telecommunication traffic between the bearer adapter and the WPS.

The bearer port 53 further includes a link to the bearer control member 54 which controls and configures the bearer adapter operation. The bearer manager 54 receives control commands from the administrator 55, which is allowed to control the operation of the transfer adapter by the user interface 56, such as the keypad 22 and display 23 shown in Figure 3, accessing the Internet, such as a web server.

15

The gateway server uses the bearer port 53 and the bearer adapter 51 in two ways: 1) To send data to a particular wireless network, 2) To control and monitor the bearer activity.

Between bearer port 53 and WPS 50 is an interface 58a, herein referred to as LWDPBI, which is an interface for transmitting and receiving WDP data telegrams and retrieving information from the transport adapter 51. The data threads are further transmitted between the transport port and the transport adapter 58b.

Thus, the interfaces 58a and 58b form the interface 25 performing the above-mentioned step 1). Further, an interface 59 is provided between the bearer control member 54 and the bearer port 53 for controlling and configuring the operation of the bearer adapter 51.

This interface 59 is called l_BGM and thus implements step 2) above. Through the user interface 56, migration adapters can be added, removed, controlled, configured and monitored.

30

The various operations and functional blocks shown in Figure 4 are preferably implemented as software blocks executed by processor 46 by calling threads 44 in protocol stack 28 and application program 26. Threads relative to transport adapters 51 are shown in greater detail in Figure 5.

111586 9

All services on interface 59 (l_BAM) are called in a single control thread context, MgmtCntx 6 1, which is a thread in the server application program 26. i_WDPBI-pa \ ve \ u) a, i.e. services over interface 58, calls two threads of 5 WPS (via transport port). The WPS has a single thread, SendContext 62, for transmitting data from the WPS and controlling the operation of the bearer. Upon transmission, the SendContext 62 retrieves the data telegram from the buffer in WPS 50 and transmits it on the transmission path whose identifier the data telegram contains, and then retrieves the next data telegram from the buffer. The data telegram is thus transmitted only to one transmission line 10 at a time. Therefore, adding or removing transport adapters does not interfere with the operation of SendContext 62 thread, which merely states that data threads go to different transport adapters than before.

Similarly, the management thread MgmtCntx 61 has calls to only one bearer at a time, and thus adding or removing transport adapters 15 while the server is able to communicate with existing transport adapters does not interfere with the operation of the control thread. Another thread in the WPS, RecvContext 63, 64, receives data from the transport adapter 51. When creating a new transport adapter 51, the thread SendContext 62 performs initialization operations between the WPS and the transport port, and the thread RecvContext 63, 64 receives a block request.

20

Each single bearer 51 divides the threads MgmtCntx 61 and SendCntx 62, and each instance has its own thread recvCntx, which is created in WPS when the bearer adapter is created. This is illustrated by the fact that the first transport adapter BA1 has a recvCntxt 63 thread and the second transport adapter BA2 has a second thread 25 recvCntx2 64. This is because the server cannot control when it has something to receive, i.e., data can come from two different 30 bearers at the same time. Therefore, a dedicated thread for each transmission path to ensure reception runs smoothly on the server. In a preferred embodiment, a new thread 44 (FIG. 3) is created (recvCntx) in protocol stack 50 (Ref. 28 in FIG. 3) upon receipt of an instruction to create a new transport adapter 51. When the transport adapter is connected to WPS 50, the transport adapter identifier is at the gateway 53.

The WPS forwards the identifier as a parameter in each function call via interface 58. By creating a new thread for the new migration adapter while the server is able to communicate with the existing migration adapters 5, the server does not have to be restarted to install this new migration adapter on the protocol stack and thus does not have to interrupt the server operation.

The following describes the threads for ease of understanding of the invention. The thread is basically the execution path through the program and may be the smallest unit of execution timed on the processor. The thread consists of a stack, the state of the CPU registers, and an entry in the system timer execution list.

The thread is a single consecutive execution stream in program code and has a single 15 execution point. To process a simple process, a program comprising a single thread can be used. For more complex processes involving running multiple applications, the program may rely on multiple threads. Operating systems usually provide thread control for an application (creation, termination, and entry point: at the beginning of the program code).

20

The process consists of one or more threads and program code, data, and other resources in memory. Typical software resources include open files, semaphores, and dynamically allocated memory. Each thread allocates all process resources in the process. The program runs when the system timer gives 25 of its threads a performance control. The timer decides which threads should be in motion and when they should be in motion. The lower priority threads may have to wait while the higher priority threads complete their task. In multiprocessor machines, the timer can transfer individual strands to different processors to '' balance 'the load with a central processing unit.

Each thread operates independently in the process. Unless they are visible to each other, the threads perform individually and are unaware of the other threads in the process. However, common resource-sharing threads must coordinate their work, for example, using semaphores or other interprocess communication methods.

Dynamic bearer removal is enabled by providing 5 bearer port 53 between WPS 50 and bearer adapters 51 to isolate WPS from bearers. When a command is received from the UI 56 to the transport manager 54 to remove the transport adapter, that particular transport adapter is removed from the transport port 53.

In this sense, the transport port holds a list, i.e. stores information about each transport adapter. The thread recvCntx 63, 64 for that particular migration adapter stays at 10 WPS until the server is shut down. However, during that time, if the WPS attempts to send something to the removed migration adapter, the transmission port returns an error message.

The gateway server may simultaneously include a plurality of migration adapters 51 for the same or different wireless networks. Therefore, there may be two different gateway adapters for SMS messages, or alternatively the same gateway adapter could be used to send short messages via two different SM-SCs (Short Message Service Center).

20 To dynamically control the migration adapters, the transmission control functions are further enhanced by a user interface 56 for the gateway server administrator.

Thus, a gateway server according to the present invention is provided with a user interface that allows the administrator to dynamically add new bearer paths while the server is able to communicate with existing gateway adapters in the gateway. The migration adapters can advantageously be added, removed, controlled, configured and monitored by a user interface, preferably comprising a graphical interface (on screen 23), by which the operation of the migration adapter and the operation of the gateway server as a whole can be easily controlled.

The graphical user interface is preferably windows based and comprises one control window for installing, configuring, starting and stopping the migration adapter, and another window which is a monitoring window for monitoring the operation of the migration adapter, its statistics and log information. Alternatively, there may be a third window for log information only. The control window may contain an icon. 111586 12 for each migration adapter, and selecting one of the icons opens the migration adapter control field as shown in Figure 6a. Administrator 55 creates a new instance of the migration adapter using the UI 56. At creation, the administrator enters the name of the migration adapter instance and selects the migration adapter type 5 from the list. After creation, the administrator configures the instance of the migration adapter unless the default settings (stored on the gateway server during installation) are acceptable. The server dynamically loads new software and creates a migration adapter instance by creating a new thread as described above. After the creation, the state of the transition adapter instance 10 is 'stopped'. Figure 6a shows standard Windows software soft keys for starting and stopping the migration adapter (Start / Stop), configuring the migration adapter (Configure), creating new migration adapters, and removing the migration adapters.

15

The instance of the migration adapter can be configured in 'stopped' and 'running' mode. The adapter adapter instance is configured by modifying the properties string of the adapter adapter instance. If the migration adapter instance is in the 'running' state, the change in the property value may not be active immediately, but the next 20 migration adapter instances will be started. Regardless of its status, the server stores new values for the properties. Figure 6b shows an example of a configuration dialog in a migration adapter management UI.

Thus, dynamically creating and deleting bearers is simplified by a graphical user interface 25, which is simple to use by administrator 55 and allows dynamic migration adapter control, while the gateway server is able to communicate with existing migration adapters on the gateway server. The graphical interface makes it easy for an administrator to manage migration adapters without having to be proficient in 30 computer programming languages.

Figs. 7a-d show signaling diagrams between the bearer control element 54, the WPS 50, the bearer port 53, and the bearer adapter 51 when creating, deleting, starting, and stopping the bearer. Figures 7a-d do not show signaling 13. 111586 interface, but it shows the action to create, create (7a), start (7b), stop (7c), and remove (7d) incoming access control interface from the interface.

Fig. 7a shows a signaling diagram when a transition adapter is created. From above, the first signal shows the bearer control member configuring the new bearer adapter. When completed, the transfer port will be notified of the new transfer adapter. The bearer port then creates a thread in the WPS, after which the bearer manager is notified of the added bearer adapter. Thereafter, 10 data telecommunication traffic may begin to use that newly added transmission path. The LWDPBI.init and l_WDPBI.open signals represent call initiation and data telecommunication opening events from the SendContext thread when the WPS should send data telegrams. Thereafter, the / _ WDPBI.receiveBuffer signalW makes a blocking request from the RecvContext thread.

15

Fig. 7b shows a signaling diagram when a transport adapter is started. Starting from the top, the first signal shows the bearer control member activating the bearer adapter. When this is complete, the transport port will be notified when a specific transport adapter is started. The LWDPBI.init and IJNDPBi.open signals 20 represent call initiation and data telecommunication traffic opening events from the SendContext thread that came from the WPS when a new migration adapter was created (Figure 7a) and which the communication path communicates to the migration adapter when the adapter is started. The bearer port then returns a call to the bearer manager indicating that a particular bearer adapter has been triggered for data telecommunication traffic. Thereafter, the LWDPBI.receiveBuffer signal represents a blocking call from the RecvContext thread that came from WPS when a new migration adapter was created (Fig. 7a) and whose transmission port communicates with the migration adapter when the transmission path is started.

Fig. 7c shows a signaling diagram when the transport adapter is stopped. Starting from top 30, the first signal shows the bearer control member stopping the bearer to notify the bearer port of stopping a particular bearer. The WDPBI.closeAll · and WDPBI.shutdown signals represent events from the SendConfexf thread that are communicated from the transport port to the transport adapter stating that the transport adapter is stopped and cannot send.

111586 14

The bearer port then returns a call to the bearer manager indicating that a particular bearer adapter has been stopped. The receiveBuffer Returns event then issues a blocking request from RecvContext, which is communicated from the transport port to the transport adapter stating that the transport adapter is stopped and cannot receive. A particular 5 transition adapter is then stopped and cannot send and receive.

Fig. 7d shows a signaling diagram when the transport adapter is removed. From above, the first signal shows a bearer control member deleting a bearer adapter informing the bearer port of the removal of a particular bearer adapter 10. The bearer port removes a specific bearer adapter from memory and returns a call to the bearer manager indicating that a particular bearer adapter has been removed. This removes the migration adapter, and the RecvContext thread associated with that particular migration adapter is destroyed the next time the gateway server is stopped.

This description illustrates embodiments and embodiments of the invention by way of examples. It will be apparent to one skilled in the art that the invention is not limited to the details of the above embodiments, and that the invention may be embodied in other forms without departing from the features of the invention. For example, although the foregoing relates to mobile terminals browsing the Internet, it will be appreciated that communications may be of various types including sending and receiving information, handling communication events such as sending and receiving financial transactions, e-mail or messages. The range of measures includes access to services such as weather reports, news, stock quotes, Flight Schedules, ringtone downloads, banking services including data acquisition and payments. It can occur in communication environments other than the Internet. The embodiments thus disclosed should be considered as illustrative but not limiting. Thus, the scope of the invention is limited only by the appended claims. Accordingly, the various embodiments of the invention as defined in claim 30, including equivalent embodiments, are within the scope of the invention.

Claims (20)

111586 A method for controlling migration adapters, each transport adapter being used by a server to communicate with a terminal over a particular wireless network, the method comprising: dynamically adding a migration adapter to a server while the server is able to communicate with existing migration adapters. The method of claim 1, further comprising: dynamically removing the migration adapter from the server while the server 10 is able to communicate with the existing migration adapters. The method of claim 1, further comprising: generating a specific thread to which the added transfer adapter is addressed. The method of claim 3, further comprising: generating said thread in a protocol stack on the server. The method of claims 1 and 2, further comprising: transferring data between the protocol stack and the migration adapter through the bearer port 20, and identifying data from each bearer to the bearer port when creating the bearer and deleting a particular bearer from the bearer port when removing the bearer. 25 The method of claim 5, further comprising: when removing the migration adapter, keeping a specific thread addressed until the next time the server is stopped. The method of claim 1, further comprising: controlling the operation of the transport adapters by a user interface. 111586 The method of claim 7, wherein the controlling comprises adding, deleting, starting, stopping, configuring, and monitoring the operation of the transport adapters. The method of claim 7 or 8, further comprising: controlling the operation of the migration adapters with a graphical Windows-based user interface. The method of any one of the preceding claims, wherein the terminals comprise mobile terminals, e.g., mobile phones that support WAP (Wireless Application Protocol). A server for managing transport adapters, each transport adapter (51) being used in a server to communicate with a terminal over a particular wireless network 15 (8), the server comprising: means (53, 56, 63) for dynamically adding a transport adapter (51) to the server with existing migration adapters. The server of claim 11, wherein the server further comprises a user interface (56, 22, 23) for allowing the server administrator (55) to dynamically add the migration adapter while the server is capable of communicating with existing migration adapters. The server of claim 11, wherein the server further comprises creating means (50,53) for generating a thread (63,64) in response to inserting the transport adapter (51) and pointing means (50,53) for pointing the created thread (63,64) to the added transport adapter (51). . The server of claim 11, wherein the server further comprises a wireless protocol stack (50) for implementing the wireless protocol and transferring data between the protocol stack and the migration adapter (51), isolating the wireless protocol stack (50) from the transmission port (53) and storing data from each siirtotiesovittimesta. The server of claim 11, wherein the server further comprises 5 deletion means (56, 54, 53) for dynamically removing the migration adapter from the server while the server is able to communicate with the existing migration adapters. The server according to claims 14 and 15, wherein the deletion means 10 is arranged to remove the transport adapter (51) from the transport port (53) and the transport port (53) is arranged to stop communicating to the deleted transport adapter. The server of claim 12, wherein the user interface (56) further comprises a graphical Windows-based user interface. A server according to any one of claims 11 to 17, comprising a gateway server serving a plurality of mobile terminals. 20 The server of claim 18, comprising a WAP gateway. A computer program product for controlling migration adapters on a server, each transmission adapter being used on a server to communicate with a terminal over 25 specific wireless networks, comprising: machine-language programming means (53, 56, 63) for dynamically adding with. 111586