USB application adopting bluetooth profile with a sharing implementation

• US 20050071487A1
• Filed: 09/29/2003
• Published: 03/31/2005
• Est. Priority Date: 09/29/2003
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Lu, Fan, Du, Wenkai
• Granted Patent: US 7,415,525 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

A Short Range Connectivity Server (SRCS) is provided to manage transport connections. The SRCS is a standalone server that runs multiple service controllers using OBEX over Bluetooth and USB. The SRCS manages all transports enabling a transport plug in strategy to be adopted. This architecture provides a generic management mechanism to create and manage the transport layer connections. Modular design components enable Bluetooth and USB application development to be undertaken without requiring knowledge of the details of the individual transport protocols. This results in a completely transparent mechanism for application development regardless of transport. The SRCS is in charge of the higher layer services controllers. Additionally, a Service Controller framework is provided for Object Exchange Protocol (OBEX) related services.

Claims

1. A method for managing at least one transport connection comprising:

providing a generic architecture management framework;

creating at least one transport layer connection;

adopting at least one profile from one transport protocol to another transport protocol; and

reusing at least one profile component from one transport protocol for another transport protocol via a central short range connectivity management mechanism.

2. A method as in claim 1, where one protocol is a Bluetooth protocol.

3. A method as in claim 1, where one protocol is a Universal Serial Bus protocol.

4. A method as in claim 1, where one protocol is an Infrared Data Association protocol.

5. A method as in claim 1, where one protocol is an RS232 protocol.

6. A method as in claim 1, where one protocol is a wireless protocol.

7. A method as in claim 1, where another protocol is a wired protocol.

8. A method as in claim 1, where the generic architecture framework comprises an object exchange related service.

9. A method as in claim 1, wherein managing the at least one transport connection comprises providing a short range connectivity application, application engine and generic platform.

10. A method as in claim 1, wherein managing the at least one transport connection further comprises service registration and discovery.

11. A method as in claim 1, wherein managing the at least one transport connection further comprises loading a connectivity component to perform channel reservation and service registration for a Bluetooth protocol.

12. A method as in claim 1, wherein managing the at least one transport connection further comprises loading a connectivity component to perform channel reservation and service registration for a Universal Serial Bus protocol.

13. A method as in claim 1, wherein managing the at least one transport connection further comprises establishing a link between an object exchange data link library and a service controller.

14. A method as in claim 1, wherein managing the at least one transport connection further comprises providing an application programming interface to manage at least one service for a Bluetooth protocol.

15. A method as in claim 1, wherein managing the at least one transport connection further comprises providing an application programming interface to manage at least one service for a Universal Serial Bus protocol.

16. A computer program stored on a computer readable media for directing a computer to execute a method that comprises:

creating at least one transport layer connection;

processing transport layer initialization, connection, and registration functionality;

adopting at least one profile from one transport protocol to another transport protocol; and

reusing at least one profile component from one transport protocol for at least one other transport protocol via a central short range connectivity management mechanism.

17. A mobile terminal, comprising a wireless transceiver, a data processor, and a memory for use in communicating with at least one of a wired and a wireless protocol utilizing a transport software subsystem that is used in common with a plurality of transport protocols.

18. A mobile terminal as in claim 17, where the common transport mechanism operates in conjunction with an operating system.

19. A mobile terminal as in claim 18, where the operating system comprises a Symbian operating system.

20. A mobile terminal as in claim 17, where one protocol is a Bluetooth protocol.

21. A mobile terminal as in claim 17, where one protocol is a Universal Serial Bus protocol.

22. A mobile terminal as in claim 17, where the common transport mechanism provides an application programming interface to manage at least one service for a Bluetooth protocol.

23. A mobile terminal as in claim 17, where the common transport mechanism provides an application programming interface to manage at least one service for a Universal Serial Bus protocol.

24. A method for managing at least one transport connection comprising providing a generic architecture management framework, creating at least one transport layer connection, adopting at least one profile from one transport protocol to another transport protocol, and reusing at least one profile component from one transport protocol for at least one other transport protocol via a central short range connectivity management mechanism, wherein creating a transport layer connection comprises receiving a service management request and performing protocol registration through at least one of a socket server and a communication server.