Roaming method for maintaining connectivity through heterogeneous wireless networks, and system for realizing the same

[0001] This application claims priority of Taiwanese application no. 093138919, filed on Dec. 15, 2004.

[0002] 1. Field of the Invention

[0003] This invention relates to a roaming method for maintaining connectivity between a client and a server of a system through heterogeneous wireless networks.

[0004] 2. Description of the Related Art

[0005] A conventional wireless device, such as a mobile phone or a personal digital assistant (PDA), that supports internet protocol (IP) connectivity is currently available in the marketplace. In a conventional method, such as the Mobile IP protocol, for maintaining an IP connectivity, the conventional wireless device uses two IP addresses, namely a home address and a care-of address, and requires the existence of a home agent and a foreign agent. The home address makes the conventional wireless device logically attached to its home network. When the conventional wireless device is not attached to its home network, and is therefore attached to a foreign network, the conventional wireless device is assigned with the care-of address. Whenever the conventional wireless device moves, the conventional wireless device registers its new care-of address to its home agent. To receive data packets, the home agent receives all the data packets destined for the wireless device via the home address, and delivers the data packets to the foreign network via the care-of address.

[0006] The aforementioned conventional method is disadvantageous in that the data packets are not directly sent to the conventional wireless device, and is applicable only for an IP-based wireless network.

[0007] Therefore, the main object of the present invention is to provide a roaming method for maintaining connectivity between a client and a server of a system through heterogeneous wireless networks.

[0008] Another object of the present invention is to provide a system that is capable of maintaining connectivity between a client and a server thereof through heterogeneous wireless networks.

[0009] According to one aspect of the present invention, a roaming method for maintaining connectivity between a client and a server through heterogeneous wireless networks comprises the steps of:

[0010] A) establishing an initial connection between the client and the server through a first selected one of the heterogeneous wireless networks;

[0011] B) detecting disconnection of the initial connection; and

[0012] C) establishing a current connection between the client and server through a second selected one of the heterogeneous wireless networks upon detecting that the initial connection has been disconnected in step B).

[0013] A system operable in heterogeneous wireless networks comprises a client and a server configured for establishing an initial connection therebetween through a first selected one of the heterogeneous wireless networks, and for establishing a current connection therebetween through a second selected one of the heterogeneous wireless networks upon detecting that the initial connection has been disconnected. As such, the client and the server are able to maintain connectivity therebetween through the heterogeneous wireless networks.

[0019] Referring to FIG. 1, the preferred embodiment of a system according to this invention is shown to include a client 1 and a server 2.

[0020] The system further includes set of program instructions for enabling the client 1 and the server 2 to maintain connectivity therebetween through heterogeneous wireless networks 5, such as an internet protocol (IP) based network and a Bluetooth piconet, in a manner to be described hereinafter.

[0021] With further reference to FIG. 2, the system implements protocols in layers, namely application layer, paging layer, dynamic link layer, and network layer. Application software that provides network services is implemented at the application layer. The aforementioned program instructions are implemented at the dynamic link layer. It is to be noted below that the network layer a physical layer. Errors in the physical layer are intercepted and processed at the dynamic link layer.

[0022] The client 1 and the server 2 are configured for establishing an initial connection therebetween through a first selected one of the heterogeneous wireless networks 5, which will be hereinafter referred to as the first wireless network. In particular, each of the client 1 and the server 2 first selects the first wireless network. The client 1 then initiates a first connection request to the server 2 that contains a server address associated with the first wireless network. When the server 2 accepts the first connection request, the initial connection is established between the client 1 and the server 2. In this embodiment, the server address of the server 2 may be one of a dynamic internet protocol (IP) address, a fixed IP address, and a device address.

[0023] The client 1 and the server 2 are further configured for conducting data packet transactions therebetween through the initial connection. In particular, with further reference to FIG. 3, each of the client 1 and the server 2 is provided with a buffer device 4 for storing the data packets transacted therebetween. The buffer device 4 of each of the client 1 and the server 2 has a receive buffer area 42 for received data packets, and a transmit buffer area 41 for data packets to be transmitted. In this embodiment, each of the receive and transmit buffer areas 41, 42 of the buffer device 4 of the client 1 and server 2 has four addressable storage locations.

[0024] The client 1 and the server 2 are further configured to track addressable storage locations of transacted data packets in the buffer device 4 thereof.

[0025] In this embodiment, each of the client 1 and the server 2 tracks addressable storage locations using a receive data pointer, as indicated by arrow 421, a read data pointer, as indicated by arrow 421, a transmit data pointer as indicated by arrow 411, a write data pointer, as indicated by arrow 412, and a transmit complete pointer, as indicated by arrow 413.

[0026] The receive data pointer of the client 1 is associated with the receive buffer area 42, and points at the addressable storage location of the receive buffer area 42 at which a data packet is currently being received.

[0027] The read data pointer is associated with the receive buffer area 42, and points at the addressable storage location of the receive buffer area 42 at which a data packet is currently being read by the application software. It is noted that when the read data pointer is moved such that the read data pointer points at the addressable storage location of the receive buffer area 42 currently pointed at by the receive data pointer, reading operation of the application software from the receive buffer area 42 is temporarily disrupted.

[0028] The write data pointer is associated with the transmit buffer area 41, and points at the addressable storage location of the transmit buffer area 41 at which a data packet is currently being written by the application software.

[0029] The transmit data pointer is associated with the transmit buffer area 41, and points at the addressable storage location of the transmit buffer area 41 at which a data packet is currently being transmitted. It is noted that when the write data pointer is moved such that the write data pointer points at the addressable storage location of the transmit buffer area 41 currently pointed at by the transmit data pointer, writing operation of the application software in the transmit buffer area 41 is temporarily disrupted.

[0030] In this embodiment, each of the client 1 and the server 2 transmits a data packet only after a read complete signal is received. Moreover, each of the client 1 and the server 2 transmits the read complete signal only after the read data pointer is moved. As such, movement of the receive data pointer such that the receive data pointer points at the addressable storage location currently pointed at by the read data pointer is unlikely. Therefore, the data packet at the addressable storage location that is pointed at by the read data pointer, which is being read by the application software, will never be overwritten.

[0031] The transmit complete data pointer is associated with the transmit buffer area 41, and points at the addressable storage location of the transmit buffer area 41 at which a data packet is completely transmitted.

[0032] It is noted that movements of the receive data pointer, the read data pointer, the transmit data pointer, the write data pointer, and the transmit complete pointer are controlled by the application software.

[0033] In this embodiment, the client 1 and the server 2 are able to conduct dummy signal transactions therebetween through the initial connection when there are no data packets to be transacted through the initial connection.

[0034] The initial connection is deemed to be disconnected when a predetermined time period has elapsed since a latest signal transaction between the client 1 and the server 2. In particular, each of the client 1 and the server 2 transmits a data packet (or a dummy signal) within the predetermined time period. Each of the client 1 and the server 2 regards the initial connection to be disconnected when the predetermined time period has elapsed since a latest receipt of a data packet (or a dummy signal).

[0035] The client 1 and the server 2 are further configured to interrupt the data packet transactions therebetween upon detecting that the initial connection has been disconnected. That is, the client 1, after deeming the initial connection to be disconnected, ceases from transmitting of data packets. The same holds true for the server 2.

[0036] The client 1 and server 2 are further configured for establishing a current connection therebetween through a second selected one of the heterogeneous wireless networks 5, which will be hereinafter referred to as the second wireless network, upon detecting that the initial connection has been disconnected. In particular, the system further includes a mapping table 3 that is maintained by a mapping table server (not shown). During the initial connection, the server 2 registers the server addresses thereof to the mapping table 3 to obtain an identification code. The mapping table 3 maps the identification code obtained by the server 2 to the server addresses of the server 2. The server 2 transmits the identification code thereof to the client 1. When the initial connection is disconnected, the client 1 accesses the mapping table 3, and queries the mapping table 3 using the identification code of the server 2 so as to obtain the server address associated with the second wireless network. Thereafter, the client 1 initiates a second connection request to the server 2 that contains the server address obtained thereby from the mapping table 3. When the server 2 accepts the second connection request, the current connection is established between the client 1 and the server 2.

[0037] The client 1 and the server 2 are further configured for resuming the data packet transactions therebetween through the current connection with reference to the tracked addressable storage locations to ensure continuity of the data packet transactions therebetween. In particular, the server 2, during the current connection, transmits the receive data pointer thereof to the client 1. The client 1 determines the addressable storage location of the data packet that was transmitted thereby but was not received by the server 2 before the initial connection was disconnected based on the receive data pointer received from the server 2 and the transmit data pointer thereof. Thereafter, the client 1 resumes transmission of the data packet starting from the addressable storage location determined thereby and onward. Similarly, the client 1, during the current connection, transmits the receive data pointer thereof to the server 2. The server 2 determines the addressable storage location of the data packet that was transmitted thereby but was not received by the client 1 before the initial connection was disconnected based on the receive data pointer received from the client 1 and the transmit data pointer thereof. Thereafter, the server 2 resumes transmission of the data packet starting from the addressable storage location determined thereby and onward.

[0038] The preferred embodiment of a roaming method for maintaining connectivity between the client 1 and the server 2 of the system through the heterogeneous wireless networks 5 according to this invention includes the steps shown in FIG. 4A.

[0039] The roaming method of this embodiment is implemented as a set of program instructions that is installed in the client 1 and the server 2.

[0040] In step 10, each of the client 1 and the server 2 is provided with the buffer device 4.

[0041] In step 15, the mapping table 3 is provided.

[0042] In step 20, the client 1 and the server 2 establish the initial connection therebetween through the first wireless network.

[0043] In this embodiment, with further reference to FIG. 4B, step 20 further includes the following sub-steps performed by the client 1:

[0044] sub-step 201: the client 1 detects the heterogeneous wireless networks 5;

[0045] sub-step 202: the client 1 selects one of the heterogeneous wireless networks 5, i.e., the first wireless network;

[0046] sub-step 203: the client 1 initiates the first connection request to the server 2 that contains the server address of the server 2 associated with the first wireless network such that the initial connection is established once the server 2 accepts the first connection request;

[0047] sub-step 204: the client 1 receives the identification code from the server 2 through the initial connection;

[0048] sub-step 205: the client 1 defines the receive and transmit buffer areas 42, 41 of the buffer device 4 thereof;

[0049] sub-step 206: the client 1 conducts data packet (or dummy signal) transactions with the server 2 through the initial connection; and

[0050] sub-step 207: the client 1 tracks the addressable storage locations of transacted data packets in the buffer device 4 thereof using the aforementioned pointers thereof.

[0051] With further reference to FIG. 4C, step 20 further includes the following sub-steps performed by the server 2:

[0052] sub-step 208: the server 2 detects the heterogeneous wireless networks 5;

[0053] sub-step 209: the server 2 selects one of the heterogeneous wireless networks 5, i.e., the first wireless network;

[0054] sub-step 210: the server 2 initiates a registration request to the mapping table 3 that contains the server addresses thereof associated with the first wireless network to obtain the identification code;

[0055] sub-step 211: the server 2 detects the first connection request from the client 1 through the first wireless network;

[0056] sub-step 212: when the server 2 detects the first connection request from the client 1, the flow proceeds to step 213. Otherwise, the flow goes back to step 211;

[0057] sub-step 213: the server 2 accepts the first connection request so as to establish the initial connection with the client 1 through the first wireless network;

[0058] sub-step 214: the server 2 transmits the identification code thereof to the client 1 through the initial connection;

[0059] sub-step 215: the server 2 defines the receive and transmit buffer areas 42, 41 of the buffer device 4 thereof;

[0060] sub-step 216: the server 2 conducts data packet (or dummy signal) transactions with the client 1 through the initial connection; and

[0061] sub-step 217: the server 2 tracks the addressable storage locations of transacted data packets in the buffer device 4 thereof using the aforementioned pointers thereof.

[0062] With further reference to FIG. 4D, step 20 further includes the following sub-steps performed by the mapping table server:

[0063] sub-step 218: the mapping table server detects the registration request from the server 2;

[0064] sub-step 219: when the mapping table server detects the registration request, the flow proceeds to step 220. Otherwise, the flow goes back to sub-step 218; and

[0065] sub-step 220: the mapping table server generates the identification code, maps the identification code generated thereby to the server addresses in the mapping table 3, and transmits the identification code to the server 2. Thereafter, the flow goes back to step 214.

[0066] In step 30, each of the client 1 and the server 2 detects disconnection of the initial connection.

[0067] In this embodiment, with further reference to FIG. 4E, step 30 includes the following sub-steps performed by the client 1:

[0068] sub-step 301: the client 1 determines whether the predetermined time period has elapsed since the latest receipt of a data packet (or a dummy signal);

[0069] sub-step 302: when the client 1 determines that the predetermined time period has elapsed since the latest receipt of a data packet (or a dummy signal), the flow proceeds to step 303. Otherwise, the flow goes back to step 301;

[0070] sub-step 303: the client 1 regards the initial connection to be disconnected; and

[0071] sub-step 304: the client 1 interrupts the data packet transactions with the server 2. That is, the client 1 ceases further transmission of the data packets.

[0072] With further reference to FIG. 4F, step 30 further includes the following sub-steps performed by the server 2:

[0073] sub-step 305: the server 2 determines whether the predetermined time period has elapsed since the latest receipt of a data packet (or a dummy signal);

[0074] sub-step 306: when the server 2 determines that the predetermined time period has elapsed since the latest receipt of a data packet (or a dummy signal), the flow proceeds to step 307. Otherwise, the flow goes back to step 305;

[0075] sub-step 307: the server 2 regards the initial connection to be disconnected; and

[0076] sub-step 308: the server 2 interrupts the data packet transactions with the client 1. That is, the server 2 ceases further transmission of the data packets.

[0077] In step 40, the client 1 and the server 2 establish the current connection therebetween through the second wireless network.

[0078] In this embodiment, with further reference to FIG. 4G, step 40 includes the following sub-steps performed by the client 1:

[0079] sub-step 401: the client 1 detects the heterogeneous wireless networks 5;

[0080] sub-step 402: the client 1 selects one of the heterogeneous wireless networks 5, i.e., the second wireless network;

[0081] sub-step 403: the client 1 determines whether there is a need to access the mapping table 3 based on the server address of the server 2 associated with the second wireless network;

[0082] sub-step 404: when the client 1 determines that there is a need to access the mapping table 3, i.e., the server address of the server 2 associated with the second wireless network is a dynamic IP address and is therefore not a fixed IP address or a Bluetooth device address, the flow proceeds to step 405. Otherwise, the flow proceeds to step 406.

[0083] sub-step 405: the client 1 accesses the mapping table 3, and queries the mapping table 3 using the identification code of the server 2 so as to obtain the server address of the server 2 associated with the second wireless network;

[0084] sub-step 406: the client 1 initiates the second connection request to the server 2 that contains the server address of the server 2 associated with the second wireless network such that the current connection is established once the server 2 accepts the second connection request;

[0085] sub-step 407: the client 1 determines whether the second connection request initiated thereby was accepted by the server 2;

[0086] sub-step 408: when the client 1 determines that the second connection request initiated thereby was accepted by the server 2, the flow proceeds to step 412. Otherwise, the flow proceeds to step 409.

[0087] sub-step 409: the client 1 determines whether all of the heterogeneous wireless networks 5 have been previously selected;

[0088] Sub-step 410: when the client 1 determines that all of the heterogeneous wireless networks 5 have been selected, the flow proceeds to step 411. Otherwise, the flow goes back to step 402 to change the second wireless network.

[0089] sub-step 411: the client 1 generates a connection error;

[0090] sub-step 412: the client 1 transmits the receive data pointer thereof to the server 2 through the current connection;

[0091] sub-step 413: the client 1 receives the receive data pointer of the server 2 from the server 2 through the current connection; and

[0092] sub-step 414: the client 1 resumes the data packet transactions with the server 2 with reference to the addressable storage location tracked in sub-step 207, thereby ensuring continuity of the data packet transactions with the server 2.

[0093] With further reference to FIG. 4H, step 40 includes the following sub-steps performed by the server 2:

[0094] sub-step 415: the server 2 detects the heterogeneous wireless networks 5;

[0095] sub-step 416: the server 2 selects one of the heterogeneous wireless networks 5;

[0096] sub-step 417: the server 2 determines whether the server address thereof associated with the second wireless network is identical to the server address thereof associated with the first wireless network;

[0097] sub-step 418: when the server 2 determines that the server address thereof associated with the second wireless network is identical to the server address thereof associated with the first wireless network, the flow proceeds to step 420. Otherwise, the flow proceeds to step 419;

[0098] sub-step 419: the server 2 initiates a registration request to the mapping table 3 that contains the server address associated with the second wireless network and the identification code thereof;

[0099] sub-step 420: the server 2 detects the second connection request from the client 1 through the second wireless network;

[0100] sub-step 421: when the server 2 detects the second connection request from the client 1, the flow proceeds to step 422. Otherwise, the flow goes back to step 420;

[0101] sub-step 422: the server 2 accepts the second connection request so as to establish the current connection with client 1 through the second wireless network;

[0102] sub-step 423: the server 2 transmits the receive data pointer thereof to the client 1 through the current connection;

[0103] sub-step 424: the server 2 receives the receive data pointer of the client 1 from the client 1 through the current connection; and

[0104] sub-step 425: the server 2 resumes the data packet transactions with the client 1 with reference to the addressable storage location tracked in sub-step 217, thereby ensuring continuity of the data packet transactions with the client 1.

[0105] While the present invention has been described in connection with what is considered the most practical and preferred embodiment, it is understood that this invention is not limited to the disclosed embodiment but is intended to cover various arrangements included within the spirit and scope of the broadest interpretation so as to encompass all such modifications and equivalent arrangements.