Method and apparatus for establishing compatibility between cordless telephone applications and physical hardware of the cordless telephone

• US 6,484,025 B1
• Filed: 01/07/2000
• Issued: 11/19/2002
• Est. Priority Date: 01/07/2000
• Status: Expired due to Term

• Current Assignee: Skyworks Solutions Incorporated
• Original Assignee: Conexant Systems Incorporated (Synaptics Incorporated)
• Inventors: Chan, Virginia M., O'Donnell, Desmond T., Munukutla, Venkateswarlu, Huang, Zhiming
• Primary Examiner(s): MAUNG, NAY AUNG
• Application Number:
  US09/479,127
• Time in Patent Office: 1,047 Days
• Field of Search: 455/418, 455/419, 455/420, 455/422, 455/426, 455/462, 455/463, 455/550, 455/575
• US Class Current: 455/418
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/72502 with one base station connected to a single line

Abstract

A method and apparatus are provided for exchanging information between a cordless telephone application and physical hardware of a cordless telephone system. The method includes the steps of intercepting information exchanged between the application and the physical hardware, processing the intercepted information in order to ascertain whether the exchange requires at least one API macro and translating between the at least one API macro and a telephone command to be executed by the physical hardware of the cordless telephone system.

Claims

1. A method for exchanging information between a cordless telephone application and physical hardware of a cordless telephone system, the method comprising the steps of:

intercepting information exchanged between the application and the physical hardware;

processing the intercepted information in order to ascertain whether the exchange requires at least one API macro; and

translating between the at least one API macro and a telephone command to be executed by the physical hardware of the cordless telephone system.

2. The method of claim 1, wherein the step of intercepting information further includes the steps of

retrieving the intercepted information transmitted from the application; and

storing the intercepted information within a first storage buffer.

3. The method of claim 2, wherein the retrieving step further includes the step of checking whether there exists information within the first storage buffer after a preselected period of time.

4. The method of claim 2, wherein the step of retrieving the intercepted information further includes the steps of

copying the intercepted information from the first storage buffer into a second storage buffer;

and

scanning the intercepted information for a predetermined character.

5. The method of claim 1, wherein the step of processing the intercepted information further includes the step of determining whether the intercepted information contains an API macro and identifying the API macro to determine the type of the API macro.

6. The method of claim 5, wherein the type of API macro may include those to operate an RF link, audio hardware, keypad, light emitting diodes, liquid crystal display, battery, serial port, volatile and nonvolatile memory, and switches.

7. The method of claim 6, wherein audio hardware includes a codec, dac, hook relay, at least one telephone line, caller identification device, speakerphone, ring indicator, ringer, and microphone.

8. The method of claim 1, wherein the step of translating further includes the steps of:

translating the API macro into a corresponding hardware driver command; and

transmitting the corresponding hardware driver command to a specific hardware driver to perform the specific telephone operation.

9. The method of claim 8 wherein the API macro includes audio interface macros and link interface macros.

10. The method of claim 8 wherein the API macro includes information necessary to perform the specific telephone operation.

11. The method of claim 8 wherein the API macro includes an API macro being one from a plurality of API macros including ALLOCATE_RX_BUFFER, ESTABLISH_LINK, INITIALIZE_LINK, READ_SYSTEM_PARAMETERS, RELEASE_LINK, REQUEST_LINK_STATUS, RESET_DATA_TRANSMIT, RESET_LINK, SEND_DATA, SET_LS_NOTIFY_SERVICE_ADDRESS, SET_RECEIVE_SERVICE_ADDRESS, WRITE_SYSTEM₁₃ PARAMETERS, CONFIRM, INTERPRET_DATA, LINK_STATUS_NOTIFY, AUDIODRIVERSTATUS, CONFIGAE, CONFIGCODEC, DELAY, DISABLEAUXDAC, DISABLESPEAKERPH, ENABLEAUXDAC, ENABLECDCSAMPLES, ENABLESPEAKERPH, MUTESPEAKERPH, OFFHOOK, ONHOOK, READAEPARAM, READCDCREG, READDELAYVALUE, RESETAE, RESETCODEC, SLEEPAE, SLEEPCODEC, STARTTONE, STOPTONE, TRANSFERVALUE, UNMUTESPEAKERPH, WRITEAEPARAM, WRITECDCREG, WRITETOAUXDAC, ZEROCDCSAMPLES.

12. The method of claim 1 further including the step of polling for a result message from the executed telephone. command.

13. The method of claim 12, wherein after the polling step, the method further comprises the steps of:

receiving the result code from a hardware device driver;

translating the result code into a status message corresponding to the result code; and

transferring the status message to the application.

14. In a cordless telephone system employing an Application Programming Interface and executing a cordless telephone application producing a API macro representing specific telephone operations, a method comprising the steps of:

initializing the application programming interface so that the cordless telephone is able to receive the API macro;

intercepting information transmitted from the application to a hardware device of the cordless telephone system;

processing the intercepted information in order to ascertain whether the information includes the API macro;

translating the API macro into a telephone command to be executed by the corresponding hardware device of the cordless telephone system; and

polling the hardware device for a result code of the executed telephone command.

15. The method of claim 14, wherein the API macro representing telephone commands remains independent of the cordless telephone system.

16. A communication interface for allowing physical hardware of a cordless telephone to become compatible with an application of the cordless telephone through an Application Programming Interface, the communication interface comprising:

first means for receiving a API macro from the application and for interpreting it into a series of commands corresponding to the API macro; and

second means for receiving the series of commands from the first means and for executing a corresponding function on a cordless telephone system.

17. The communications interface of claim 16, wherein the first means includes a programmed embedded processor and an application specific integrated circuit of a cordless telephone system.

18. The communications interface of claim 16, wherein the second means includes a programmed embedded processor and an application specific integrated circuit of a cordless telephone system.

19. The communications interface of claim 16, wherein the API macro includes specified command identifiers followed by data required to perform a specific telephone operation.

20. The communications interface of claim 16, further comprising

third means for storing information including the received API macro; and

fourth means coupled to the first and third means for processing information transmitted from the first means to determine whether the API macro is within the information.

21. A communication interface for enabling a communication application, being executed on a cordless telephone system and generating a API macro to become compatible with an Application Programming Interface, the communication interface comprising:

a device that is capable of sending and retrieving information of the cordless telephone system;

a first task that is capable of processing information received from the application to determine whether the API macro is within the information; and

a second task that is capable of the specific telephone command represented by the API macro.

22. The communication interface of claim 21 wherein the device is a hardware driver interface.

23. The communication interface of claim 21 wherein the first and second tasks are software functions of a communication interface.

24. A method for exchanging information between a telephone application and associated physical hardware including an embedded processor of a wireless telephone system, the method comprising the steps of:

intercepting information exchanged between the application and the physical hardware;

processing the intercepted information in order to ascertain whether the exchange requires at least one API macro; and

translating between the at least one API macro and a telephone command to be executed by the physical hardware of the wireless telephone system.