Wireless extended proximity networks: systems, methods and program products

• US 20050135286A1
• Filed: 12/23/2003
• Published: 06/23/2005
• Est. Priority Date: 12/23/2003
• Status: Abandoned Application

• Current Assignee: Nokia Solutions and Networks US LLC (Nokia Corporation)
• Original Assignee: Nokia Solutions and Networks US LLC (Nokia Corporation)
• Inventors: Nurminen, Jukka K., Bakos, Balazs, Fodor, Szabolcs
• Application Number:
  US10/742,799
• Publication Number:
  US 20050135286A1
• Time in Patent Office: Days
• US Class Current: 370/310
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 84/22 with access to wired networks
• CPC Class Codes: H04W 92/18 between terminal devices

Abstract

A wireless proximity network is extended to provide peer-to peer communication among ad hoc networks. A mobile device (peer) coupled to an access point serves an adhoc network via a short-range communication link. The peer executes a Bluetooth protocol stack. Each peer has a routing table about all the peers in the adhoc network. A peer to peer software layer (P2P) runs on top of the Bluetooth protocol stack and beneath a multi-user application layer. The P2P software handles application deployment, peer management and communications for applications and provides information about existing peers on the adhoc network; routes messages between peers within an ad hoc network and from one peer to another in different adhoc networks. The access point is connected to a wireless LAN via a wireless router. The access point has an IP-BT address conversion table and communicates with other access points via wireless routers using TCP/IP protocols.

Claims

1. In a short-range wireless system, a wireless extended proximity network, comprising:

a) a plurality of access points, each access point coupled to a proximity network including at least one mobile device for peer to peer communication;

b) means coupling the access points in a network; and

c) means installed in each mobile device and access point enabling each peer to communicate with any peer in the mesh network.

2. The proximity network of claim 1 further comprising:

d) router means connecting each access point to the mesh network.

3. The proximity network of claim 1 further comprising:

e) short-range communication links connecting each access point to mobile devices in an associated proximity network.

4. The proximity network of claim 1 further comprising:

f) means included in each access point enabling communication with other access point using Transaction Control Protocol/Internet Protocol (TCP/IP) and/or UDP/IP.

5. The proximity network of claim 1 wherein the means enabling each peer to communicate with any peer in the mesh network comprises middleware installed in a short-range communication protocol stack beneath an application layer in the stack.

6. The proximity network of claim 5 wherein the middleware comprises a connection class and a network class, the connection class representing and managing IP sockets or short range based connection channels and the network class responsible for routing messages, managing connections and maintaining a list of available peers.

7. The proximity network of claim 6 further comprises a network listener interacting with the network class to inform the application layer about different network events.

8. The proximity network of claim 6 further comprises at least one mobile information device protocols (MIDP) and at least one application program interface (API) interacting with the connection class.

9. The proximity network of claim 6 further comprises a message class implementing input messaging for the connection class.

10. The proximity network of claim 6 further comprises an outgoing message queue class implementing outgoing messaging and storage for the connection class.

11. The proximity network of claim 6 further comprises an incoming message class implementing message receiving for the network class.

12. The proximity network of claim 1 further comprising

g) means installed in each access point and mobile device listing all peers in the network.

13. The proximity network of claim 1 further comprising

h) means installed in each access point converting mobile device addresses to mesh network addresses.

14. The proximity network of claim 1 wherein the mesh network is a wired or wireless local area network.

15. The proximity network of claim 1 wherein the means coupling the access point to the mesh network is a wireless router.

16. A method enabling a peer in a communication network to communicate with any peer in a mesh network, comprising:

a) forming a plurality of proximity networks, each proximity network including at least one mobile device coupled to an access point;

b) coupling the access points in a mesh network; and

c) installing middleware in the access points and the mobile devices enabling mobile devices to communicate with any mobile device in the mesh network on a peer to peer basis.

17. The method of claim 16 further comprising:

d) installing short-range communication links between the access points and the mobile devices.

18. The method of claim 16 comprising:

e) installing in each access point and mobile device a routing table listing all peer addresses and connections in the mesh network.

20. The method of claim 16 further comprising:

g) installing the middleware in a short range communication protocol stack beneath an application layer in the stack.

21. The method of claim 16 wherein the middleware in sending a message further comprises:

(a) entering a routing table and selecting connections for forwarding the message;

(b) adding the message to an outgoing queue of the selected connections and (c) sending the message from the outgoing queue on a first in-first out basis.

22. The method of claim 16 wherein the middleware in receiving a message from a client application further comprises (a) maintaining a connection thread for receiving incoming data;

(b) creating a message from the incoming data;

(c) identifying the recipient of the message;

(d) storing the message in an incoming message queue; and

(e) notifying the client application when the message is removed from the incoming message queue.

23. The method of claim 16 wherein the middleware in joining a peer-to-peer network further comprises:

(a) creating a connection object based a URL type;

(b) initiating a connection using the URL;

(c) notifying an application attempting to join the peer-to-peer network;

(d) sending a “

Peer Update Request Message”

to the network, and (e) updating routing tables in the network by processing “

Peer Update Answer”

message.

24. The method of claim 16 wherein the middleware leaves a peer-to-peer network further comprises:

(a) sending a “

Close Connection”

message to active connections to notify the end of the connection;

(b) terminating the connection;

(c) removing the connection and updating a routing table; and

(d) notifying a related application of the network departure.

19. The method of claim 167 comprising;

f) installing in each access point a conversion table for converting mobile device addresses to mesh addresses of access point.

25. A method of communicating on a peer to peer in a mesh network of adhoc short range communication networks, comprising:

a) maintaining a list of existing peers in a mesh network;

b) receiving a message from a sending peer in an adhoc network, the received message containing a recipient address of a receiver peer;

c) analyzing the received message;

d) based on the recipient address in the received message, determining a next level address for forwarding the received message without changing the recipient address in the received message;

e) replacing the next level of address without changing the recipient address in order to forward the message to the receiver peer; and

f) coupling the sending and receiver peers for communication with each other.

26. The method of claim 25 wherein the next level address of the received message is an address, which is in a different protocol address than in, the received message.

27. The method of claim 25 wherein the received message address is a Bluetooth address and the next level address is an IP address.

28. The method of claim 25 wherein receiving the message identified by the next level address is sent to the next level address and the next level address is converted to the Bluetooth address of the recipient address under the coverage of the next access point.

29. A medium, executable in a computer system, for enabling a peer in a communication network to communicate with any peer in a mesh network, the medium comprising:

a) program code for forming a plurality of proximity networks, each proximity network including at least one mobile device coupled to an access point;

b) program code for coupling the access points in a mesh network

c) program code installing middleware in a communication protocol stack enabling mobile devices to communicate with any mobile device in the mesh network on a peer to peer basis.

30. The medium of claim 29 further wherein the middleware in sending a message, comprises:

(a) program code entering a routing table and selecting connections for forwarding the message;

(b) program code adding the message to an outgoing queue of the selected connections; and

(c) program code sending the message from the outgoing queue on a first in-first out basis.

31. The medium of claim 29 wherein the middleware in receiving a message from a client application, comprises:

(a) program code maintaining a connection thread for receiving incoming data;

(b) program code creating a message from the incoming data;

(c) program code identifying a recipient of the message;

(d) program code storing the message in an incoming message queue; and

(e) program code notifying the client application when the message is removed from the incoming message queue.

32. The medium of claim 29 wherein the middleware in joining a peer-to-peer network, comprises:

(a) program code creating a connection object based on a URL type;

(b) program code initiating a connection using the URL;

(c) program code notifying an application attempting to join the peer-to-peer network;

(d) program code sending a “

Peer Update Request Message”

to the network, and

(e) program updating routing tables in the network by processing “

Peer Update Answer”

message.

33. The medium of claim 29 wherein the middleware leaves a peer-to-peer network, comprises:

(a) program code sending a “

Close Connection”

message to active connections to notify the end of the connection;

(b) program code terminating the connection;

(c) program code removing the connection and updating a routing table; and

(d) program code notifying a related application of the network departure.

34. A method enabling a user to continue to receive data while temporarily disconnected from a proximity network comprising:

(a) connecting a user attending an event to a proximity network via an access point having a coverage area;

(b) activating an application in the mobile device for acquisition of services from the proximity network;

(c) executing the application while connected to the proximity network;

(d) temporarily moving out of the coverage area of the access point;

(e) detecting the departure of the user from the proximity network by the access point;

(f) storing application data of the user in the access point while the user is out of the coverage area of the access point; and

(g) providing the stored application data to the user upon reconnection to the access point.

35. Apparatus enabling a user to continue to receive data while temporarily disconnected from a proximity network comprising:

(a) means connecting a user attending an event to a proximity network via an access point having a coverage area;

(b) means activating an application in a mobile device for acquisition of services from the proximity network;

(c) means executing the application while the mobile device is connected to the proximity network;

(d) means detecting the departure of the user from the proximity network by the access point;

(f) means storing application data in the access point while the user is out of the coverage area of the access point; and

(g) means providing the stored application data to the user upon reconnection to the access point.