Customer framework for embedded applications

• US 20070198997A1
• Filed: 06/17/2004
• Published: 08/23/2007
• Est. Priority Date: 06/17/2003
• Status: Abandoned Application

• Current Assignee: Stmicroelectronics Belgium N.V. (STMicroelectronics NV)
• Original Assignee: Stmicroelectronics Belgium N.V. (STMicroelectronics NV)
• Inventors: Jacops, Davy, Quanten, Erik
• Application Number:
  US10/561,082
• Publication Number:
  US 20070198997A1
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

The present invention provides a framework so that software can be embedded into a telecommunications semiconductor device such as an integrated circuit or into a chip. The framework is an API. The telecommunications device may support a telecommunications protocol, e.g. a wireless protocol such as BT. For example the BT Layers above an HCI can support different profiles and/or Applications. The semiconductor devices according to the present invention are particularly suitable for products where no host processor is available to provide the process engine to run the applications software. The semiconductor devices according to the present invention can include an ASIC, an integrated circuit, a multicarrier module (MCM) a printed circuit board or similar. Such devices may find advantageous use in small apparatus, e.g. wireless linked headphones.

Claims

1. A library of software program products, the library comprising a set of routines for an embedded software application requiring SW protocol layers, profiles and/or application code embedded on a processor, the library providing an interface between the software application running on the processor and the SW protocol layers and/or the profiles and/or the application code.

2. The library according to claim 1 wherein the interface is between the software application running on the processor and a telecommunications module.

3. The library according to claim 2 wherein the telecommunications module is the Bluetooth lower layer SW protocol.

4. The library according to claim 2, wherein the interface uses telecommunications controller interface communications.

5. The library according to claim 4 wherein the communications are HCI communications for communication with the telecommunications module.

6. The library according to claim 2, wherein the software application communicates with a telecommunications module for executing a telecommunications protocol.

7. The library according to claim 6 wherein the software application communicates with a hardware input/output interface.

8. The library according to claim 7 stored on a computer readable medium.

9. The library according to claim 8, wherein the medium is a CD-ROM or DVD-ROM or a memory or data storage device.

13. Host processing system for executing the library of computer programs in accordance with claim 1.

10. A telecommunications device with an interface towards an underlying operating system, to layers of a telecommunications protocol and optionally towards any hardware available for an embedded application.

11. The telecommunications device according to claim 10 wherein the interface communicates with the telecommunications protocol via telecommunications controller interface communications.

12. The telecommunications device according to claim 10, wherein the interface is an API.

14. An API for providing functions to a software application requiring SW protocol layers, profiles and/or application code embedded on a processor, the API communicating towards an underlying operating system, to layers of a telecommunications protocol and optionally towards any hardware available for an embedded application.

15. An API according to claim 14, wherein the API communicates with the protocol layers using HCI communications.

16. The API of claim 14, stored on a computer readable medium.

17. A method of embedding a software application requiring SW protocol layers, profiles and/or application code embedded on a processor, the method comprising:

generating API for communicating towards an underlying operating system, to layers of a telecommunications protocol and optionally towards any hardware available for an embedded application.

18. Method of operating a telecommunications device with an interface towards an underlying operating system, to layers of a telecommunications protocol and optionally towards any hardware available for an embedded application.

19. The method according to claim 18, wherein the interface is an API.