U.S. patent application number 13/893390 was filed with the patent office on 2013-10-17 for system and method for managing a wireless device from removable media with processing capability.
The applicant listed for this patent is Cassis International Pte Ltd.. Invention is credited to Leandro Quitalig Galvez, Kwang Wee Lee.
Application Number | 20130273899 13/893390 |
Document ID | / |
Family ID | 42245581 |
Filed Date | 2013-10-17 |
United States Patent
Application |
20130273899 |
Kind Code |
A1 |
Lee; Kwang Wee ; et
al. |
October 17, 2013 |
SYSTEM AND METHOD FOR MANAGING A WIRELESS DEVICE FROM REMOVABLE
MEDIA WITH PROCESSING CAPABILITY
Abstract
Systems and methods for managing a wireless device from
removable media with processing capability are described. One
aspect may include a system for operating the radio hardware of a
wireless device from a media device, comprising a media device,
including a processor; a memory, coupled to said processor; and a
radio host side peer layer, adapted to run on said memory and said
processor, and adapted to communicate with the radio hardware of
said wireless device.
Inventors: |
Lee; Kwang Wee; (Singapore,
SG) ; Galvez; Leandro Quitalig; (Singapore,
SG) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Cassis International Pte Ltd. |
Singapore |
|
SG |
|
|
Family ID: |
42245581 |
Appl. No.: |
13/893390 |
Filed: |
May 14, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12386208 |
Apr 14, 2009 |
8442509 |
|
|
13893390 |
|
|
|
|
61206454 |
Jan 30, 2009 |
|
|
|
61206453 |
Jan 30, 2009 |
|
|
|
61206427 |
Jan 30, 2009 |
|
|
|
61206797 |
Feb 4, 2009 |
|
|
|
Current U.S.
Class: |
455/419 |
Current CPC
Class: |
G06F 13/385 20130101;
G09G 5/006 20130101; G06F 3/147 20130101; G09G 2360/18 20130101;
H04W 8/22 20130101; G06F 9/44584 20130101; G06F 9/445 20130101;
G09G 2370/16 20130101 |
Class at
Publication: |
455/419 |
International
Class: |
H04W 8/22 20060101
H04W008/22 |
Claims
1. A system for operating the radio hardware of a wireless device
from a media device, the system comprising: a wireless device,
including: a processor; a memory coupled to said processor; radio
hardware coupled to said processor; and a radio API adapted to run
on said memory and said processor, adapted to communicate with said
radio hardware of said wireless device, and adapted to communicate
with the media device.
2. The system of claim 1, wherein said radio API is adapted to
communicate with a radio host side peer layer of the media
device.
3. The system of claim 1, wherein said radio API is adapted to run
a daemon program.
4. The system of claim 1, wherein said radio API is adapted to
communicate with the media device through a communication link.
5. The system of claim 4, wherein said communication link is a data
bus.
6. The system of claim 4, wherein said communication link is
wireless.
7. The system of claim 1, wherein said radio API is adapted to
transmit data for configuring one or more settings of said radio
hardware to the media device.
8. The system of claim 1, wherein said radio API is adapted to
receive data from the media device for operating said radio
hardware.
9. A system for operating the radio hardware of a wireless device
from a media device, the system comprising: a media device,
including: a first memory, a processor coupled to said first
memory, and a radio host side peer layer adapted to run on said
processor and said first memory, wherein said radio host side peer
layer is adapted to communicate with the radio hardware of the
wireless device.
10. The system of claim 9, wherein said media device is removably
coupled to the wireless device.
11. The system of claim 10 wherein said media device is
mechanically connected to the wireless device.
12. The system of claim 10, wherein said media device adheres to a
SIM, SAM, SD, micro SD, or USB dongle form factor.
13. The system of claim 9, wherein said media device is a removable
media card.
14. The system of claim 9, wherein said first memory is RAM.
15. The system of claim 14, wherein said media device includes a
second memory, and wherein said second memory is ROM.
16. The system of claim 9, wherein said radio host side peer layer
is adapted to communicate with the radio hardware of the wireless
device through a communication link.
17. The system of claim 16, wherein said communication link is a
data bus.
18. The system of claim 16, wherein said communication link is
wireless.
19. The system of claim 9, wherein said processor is adapted to run
an embedded operating system.
20. The system of claim 19, wherein said embedded operating system
is Linux, Win CE, or Symbian.
21. The system of claim 9, wherein said processor is adapted to run
an embedded graphics engine for providing a graphical user
interface.
22. The system of claim 21, wherein said embedded graphics engine
is X-Windows.
23. The system of claim 9, wherein said processor is adapted to run
an embedded runtime environment.
24. The system of claim 23, wherein said runtime environment is
MatchBox, Android, QT, MontaVista, or Openmoko.
25. The system of claim 9, wherein said radio host side peer layer
is adapted to communicate with a radio API of the wireless
device.
26. The system of claim 9, wherein said radio host side peer layer
is adapted to run a daemon program.
27. The system of claim 9, wherein said radio host side peer layer
is adapted to communicate with the radio hardware of the wireless
device using an application layer protocol.
28. The system of claim 9, wherein said radio host side peer layer
is adapted to communicate radio hardware command data for operating
the radio hardware of the wireless device from the media device to
the wireless device.
29. The system of claim 9, wherein said radio host side peer layer
emulates the radio hardware of the wireless device.
30. The system of claim 29, wherein said radio host side peer layer
is adapted to communicate data corresponding to one or more radio
hardware settings for the radio hardware of the wireless device
from the media device to the wireless device.
31. The system of claim 30, wherein said radio hardware settings
include a setting corresponding to frequency, channel, or
power.
32. A system for operating the radio hardware of a wireless device,
from a media device comprising: a wireless device, including: a
first processor, a first memory coupled to said first processor,
radio hardware coupled to said first processor, and a radio API,
adapted to run on said first memory and said first processor, and
adapted to communicate with said radio hardware of said wireless
device; a media device, including: a second processor, a second
memory coupled to said second processor, a radio host side peer
layer, adapted to run on said second memory and said second
processor; and said radio API of the wireless device adapted to
communicate with said radio host side peer layer of the media
device, and said radio host side peer layer of the media device
adapted to communicate with said radio API of the wireless
device.
33. The system of claim 32, wherein said wireless device is a
cellular telephone.
34. The system of claim 33, wherein said cellular telephone is an
OpenMoko Neo FreeRunner.
35. The system of claim 32, wherein said radio hardware includes a
CDMA or GSM antenna.
36. The system of claim 35, wherein said radio hardware is for
receiving and transmitting CDMA, GPRS, GSM, Bluetooth, or Wi-Fi
signals.
37. The system of claim 32, wherein said processor is a baseband
processor.
38. The system of claim 32, wherein said wireless device further
includes one or more peripheral devices adapted to be run by said
processor.
39. The system of claim 38, wherein at least one of said peripheral
devices is a microphone or speaker.
40. The system of claim 38, wherein at least one of said peripheral
devices is adapted to receive input from a user.
41. The system of claim 40, wherein at least one of said peripheral
devices is a keypad, joystick, push button, or camera.
42. The system of claim 40, wherein at least one of said peripheral
devices is an audio device.
43. The system of claim 38, wherein at least one of said peripheral
devices is a wireless network interface device.
44. The system of claim 32, wherein said wireless device further
includes a hardware configuration module for storing data
corresponding to one or more radio hardware settings for said radio
hardware.
45. The system of claim 44, wherein said radio hardware settings
include a setting corresponding to frequency, channel, or
power.
46. The system of claim 32, wherein said radio API is adapted to
run a daemon program.
47. The system of claim 32, wherein said radio API is adapted to
communicate with said media device through a communication
link.
48. The system of claim 47, wherein said communication link is a
data bus.
49. The system of claim 47, wherein said communication link is
wireless.
50. The system of claim 32, wherein said radio API is adapted to
transmit data for configuring one or more settings of the radio
hardware of said media device.
51. The system of claim 32, wherein said radio API is adapted to
receive data from said media device for operating said radio
hardware.
52. The system of claim 32, wherein said media device is removably
coupled to the wireless device.
53. The system of claim 52, wherein said media device is
mechanically connected to the wireless device.
54. The system of claim 33, wherein said media device adheres to a
SIM, SAM, SD, micro SD, or USB dongle form factor.
55. The system of claim 32, wherein said media device is a
removable media card.
56. The system of claim 32, wherein said second memory is RAM.
57. The system of claim 32, wherein said media device includes a
third memory, and wherein said third memory is ROM.
58. The system of claim 32, wherein said second processor is
adapted to run an embedded operating system.
59. The system of claim 58, wherein said embedded operating system
is Linux, Win CE, or Symbian.
60. The system of claim 32, wherein said second processor is
adapted to run an embedded graphics engine for providing a
graphical user interface.
61. The system of claim 60, wherein said embedded graphics engine
is X-Windows.
62. The system of claim 32, wherein said second processor is
adapted to run an embedded runtime environment.
63. The system of claim 62, wherein said runtime environment is
MatchBox, Android, QT, MontaVista, or Openmoko.
64. The system of claim 32, wherein said radio host side peer layer
is adapted to run a daemon program.
65. The system of claim 32, wherein said radio host side peer layer
is adapted to communicate with said radio hardware of the wireless
device using an application layer protocol.
66. The system of claim 32, wherein said radio host side peer layer
is programmed to transmit radio hardware command data for operating
said radio hardware of the wireless device.
67. The system of claim 66, wherein said radio host side peer layer
is adapted to transmit data corresponding to one or more radio
hardware settings for said radio hardware of said wireless
device.
68. The system of claim 67, wherein said radio hardware settings
include a setting corresponding to frequency, channel, or
power.
69. A system for operating the radio hardware of a wireless device,
from a media device comprising: a wireless device, including: a
means for processing, a means for storing coupled to said means for
processing, a means for transmitting and receiving radio signals
coupled to said processing means; and a means for unwrapping
hardware commands, adapted to run on said means for storing and
said means for processing, adapted to communicate with said means
for transmitting and receiving radio signals of said wireless
device, and adapted to communicate with the media device.
70. A system for operating the radio hardware of a wireless device,
from a media device comprising: a media device, including: a means
for processing, a means for storing coupled to said means for
processing, and a means for emulating radio hardware, adapted to
run on said means for storing and said means for processing, and
adapted to communicate with the radio hardware of said wireless
device.
71. The system of claim 70, wherein said media device is removably
coupled to the wireless device.
72. The system of claim 71, wherein said media device is
mechanically connected to the wireless device.
73. The system of claim 71, wherein said media device adheres to a
SIM, SAM, SD, micro SD, or USB dongle form factor.
74. A system for operating the radio hardware of a wireless device,
from a media device comprising: a wireless device, including: a
first means for processing, a first means for storing coupled to
said first means for processing, a means for transmitting and
receiving radio signals coupled to said first processing means, and
a means for unwrapping hardware commands, adapted to run on said
first storing means and said first processing means, and adapted to
communicate with said means for transmitting and receiving radio
signals of said wireless device; a media device, including: a
second means for processing, a second means for storing coupled to
said second means for processing, a means for emulating radio
hardware, adapted to run on said second means for storing and said
second means for processing; and said means for unwrapping hardware
commands of the wireless device adapted to communicate with said
means for emulating radio hardware of the media device, and said
means for emulating radio hardware of the media device adapted to
communicate with said means for unwrapping hardware commands of the
wireless device.
75. The system of claim 74, wherein said media device is removably
coupled to the wireless device.
76. The system of claim 75, wherein said media device is
mechanically connected to the wireless device.
77. The system of claim 75, wherein said media device adheres to a
SIM, SAM, SD, micro SD, or USB dongle form factor.
78. A method for operating the radio hardware of a wireless device
from a media device comprising: a. mapping, on the wireless device,
a processor of the media device, via a radio API; b. receiving, on
the wireless device, wrapped packets containing radio hardware
commands from the media device; c. unwrapping, on the wireless
device, wrapped packets containing radio hardware commands; d.
executing, by the radio hardware on the wireless device, said radio
hardware commands.
79. The method of claim 78, further including the step of
communicating, by said radio API, with a radio host side peer layer
of the media device.
80. The method of claim 78, further including the step of running a
daemon program on said radio API.
81. The method of claim 79, wherein said communicating step further
includes communicating with the media device through a
communication link.
82. The method of claim 81, wherein said communicating step further
includes communicating through said radio API.
83. The method of claim 81, wherein said communication link is a
data bus.
84. The method of claim 81, wherein said communication link is
wireless.
85. The method of claim 78, further including the step of
transmitting, from the wireless device, data for one or more
configuration settings of the radio hardware to the media
device.
86. The method of claim 78, wherein the executing step is performed
by the radio hardware of the wireless device.
87. A method for operating the radio hardware of a wireless device
from a media device comprising: a. emulating, on the media device,
a hardware interface for communicating with a runtime environment;
b. mapping, by a radio host side peer layer on the media device,
the radio hardware of the wireless device to the emulated hardware
interface so the media devices operates as if directly connected to
radio hardware; c. wrapping, by a radio host side peer layer on the
media device, radio hardware commands; d. sending, by a radio host
side peer layer on the media device, the wrapped radio hardware
commands to the wireless device; and e. executing commands on the
media device as if the radio hardware of the wireless device is
directly connected to the media device.
88. The method of claim 87, wherein said media device is removably
coupled to the wireless device.
89. The method of claim 88, wherein said media device is
mechanically connected to the wireless device.
90. The method of claim 88, wherein said media device adheres to a
SIM, SAM, SD, micro SD, or USB dongle form factor.
91. The method of claim 87, wherein said media device is a
removable media card.
92. The method of claim 87, further including the step of
communicating with the radio hardware of the wireless device by a
communication link.
93. The method of claim 92, wherein said communicating step further
includes communicating through said radio host side peer layer.
94. The method of claim 92, wherein the communication link is a
data bus.
95. The method of claim 92, wherein the communication link is
wireless.
96. The method of claim 87, further including the step of running a
daemon program on said radio host side peer layer.
97. The method of claim 87, wherein said communicating step further
includes communicating with the radio hardware of the wireless
device using an application layer protocol.
98. The method of claim 87, further including the step of
transmitting radio hardware command data to the wireless device for
operating the radio hardware of the wireless device.
99. The method of claim 87, further including the step of
transmitting, from the media device to the wireless device, one or
more radio hardware settings for the radio hardware of the wireless
device.
100. The method of claim 99, wherein said radio hardware settings
include a setting corresponding to frequency, channel, or
power.
101. The method of claim 87, wherein the executing step is
performed by a processor of the media device.
102. A method for operating the radio hardware of a wireless device
from a media device comprising: a. emulating, on the media device,
a hardware interface for communicating with a runtime environment;
b. mapping, by a radio host side peer layer on the media device,
the radio hardware of the wireless device to the emulated hardware
interface so the media devices operates as if directly connected to
radio hardware; c. wrapping, by a radio host side peer layer on the
media device, radio hardware commands; d. sending, by a radio host
side peer layer on the media device, the wrapped radio hardware
commands to the wireless device; e. mapping, on the wireless
device, a processor of the media device so the radio hardware
operates as if directly connected to said processor, via a radio
API; f. receiving, on the wireless device, wrapped packets
containing radio hardware commands from the media device; g.
unwrapping, on the wireless device, wrapped packets containing
radio hardware commands; h. executing, by the wireless device, said
radio hardware commands.
103. The method of claim 102, further comprising the step of
running a daemon program on said radio API.
104. The method of claim 102, further including the step of
communicating between the wireless device and the media device
through a communication link.
105. The method of claim 104, wherein said communicating step
further includes communicating with the media device through the
radio API.
106. The method of claim 104, wherein said communication link is a
data bus.
107. The method of claim 104, wherein said communication link is
wireless.
108. The method of claim 102, further including the step of
transmitting, on the wireless device, data for configuring one or
more settings of the radio hardware to the media device.
109. The method of claim 102, wherein said media device is
removably coupled to the wireless device.
110. The method of claim 109, wherein said media device is
mechanically connected to the wireless device.
111. The method of claim 110, wherein said media device adheres to
a SIM, SAM, SD, micro SD, or USB dongle form factor.
112. The method of claim 102, wherein said media device is a
removable media card.
113. The method of claim 102, wherein said communicating step
further includes communicating from the media device to the
wireless device through the radio host side peer layer.
114. The method of claim 102, further comprising the step of
running a daemon program on said radio host side peer layer.
115. The method of claim 102, wherein said communicating step
further includes communicating by the media device with the radio
hardware of the wireless device using an application layer
protocol.
116. The method of claim 102, further including the step of
transmitting, from the media device to the wireless device, one or
more radio hardware settings for the radio hardware of the wireless
device.
117. The method of claim 116, wherein said radio hardware settings
include a setting corresponding to frequency, channel, or
power.
118. The method of claim 102, wherein the executing step is
performed by the radio hardware of the wireless device.
119. The method of claim 102, wherein the executing step further
includes executing said radio hardware commands on the media device
as if the radio hardware of the wireless device is directly
connected to the media device.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Patent
Application Ser. Nos. 61/206,454, 61/206,453, and 61/206,427, filed
Jan. 30, 2009, and U.S. Provisional Patent Application Ser. No.
61/206,797, filed Feb. 4, 2009, the disclosures of which are
incorporated herein by reference.
FIELD OF THE INVENTION
[0002] The present invention relates to a system and method for
managing a wireless device from removable media with processing
capability.
BACKGROUND OF THE INVENTION
[0003] Current wireless device designs function with all the
software layers residing in the handset, utilizing the main
processor and attached radio hardware. The application and runtime
environments are dependent on the hardware architecture of each
specific handset. User applications and run-time environments on
each handset lose portability and compatibility if the user were to
change to a handset with some hardware architecture changes.
[0004] It may be desirable to have a system and method for managing
a wireless device from removable media with processing capability.
This makes the runtime environment and application independent of
the wireless radio hardware that is implemented on the wireless
handset. The removable media with the processor and installed
software can be connected to any other wireless handset with a
different wireless radio hardware configuration and still function
properly.
SUMMARY OF THE INVENTION
[0005] Embodiments of the present invention may provide a method
and system that may include a remote processor package housed in
removable media accessing a wireless radio modem in a wireless
device, wherein the access takes place via a communication link. In
one aspect, the present invention may provide for a remote
processor package system housed in removable media.
[0006] One aspect may include a system for operating the radio
hardware of a wireless device from a media device, comprising a
media device, including a processor; a memory, coupled to said
processor; and a radio host side peer layer, adapted to run on said
memory and said processor, and adapted to communicate with the
radio hardware of said wireless device. Another aspect may include
a method for operating the radio hardware of a wireless device from
a media device comprising emulating, on the media device, a
hardware interface that a runtime environment will communicate
with; mapping, on the media device, the radio hardware of the
wireless device using a radio API so the runtime environment and an
application operate as if directly connected to hardware, via a
radio host side peer layer; and executing the application and
runtime environment on the radio hardware as if the hardware is
directly connected to the media device. Another aspect may include
a system for operating the radio hardware of a wireless device from
a media device, comprising a wireless device, including a
processor; a memory, coupled to said processor; radio hardware,
coupled to said processor; and a radio API, adapted to run on said
memory and said processor, adapted to communicate with said radio
hardware of said wireless device, and adapted to communicate with
the media device.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] Features and other aspects of embodiments of the present
invention are explained in the following description taking in
conjunction with the accompanying drawings, wherein:
[0008] FIG. 1 illustrates a radio modem control block diagram for a
typical wireless handset;
[0009] FIG. 2 illustrates a radio modem control block diagram for a
processor in a removable media device according to one aspect of
the system and method of the present disclosure;
[0010] FIG. 3A illustrates a flow chart for the host peer radio API
according to one aspect of the system and method of the present
disclosure;
[0011] FIG. 3B illustrates an SMS flow chart for the host peer
radio API for SMS messages according to one aspect of the system
and method of the present disclosure;
[0012] FIG. 4 illustrates a host processor and wireless radio
handset according to one aspect of the system and method of the
present disclosure; and
[0013] FIG. 5 illustrates a block diagram of the removable media
device hardware design.
DETAILED DESCRIPTION
[0014] Various embodiments of the present invention will now be
described in greater detail with reference to the drawings.
[0015] As shown in FIG. 1, typical architecture for a wireless
handset 101 includes a processor 102 located in the handset. The
current wireless handset design 101 has all the software layers
stored in the handset, using the main processor and attached radio
hardware 107. Current wireless handset design 101 includes the
software layers for the application 103, the runtime environment
104, the wireless radio hardware framework 105, and the embedded
operating system kernel 106 located entirely in the wireless
handset 101. Additionally, current wireless handset design 101
includes a microphone 110 connected to an audio codec 109, which is
connected to the main processor 102. The audio codec 109 is then
connected to the speaker 108.
[0016] As shown in FIG. 2, one aspect of the present invention may
include a radio host side peer layer 203 located on the removable
media device 202 under the wireless radio hardware framework layer
105. Further aspects may include a removable media device 202
conforming to the SD, micro SD, SIM, MMC, or SAM form factors.
Other aspects may include wireless radio hardware conforming to the
GSM or CDMA standards. The wireless device 201 may implement a
radio API 205 that maps the command to the GSM or CDMA hardware.
The radio API 205 may virtually map the GSM or CDMA hardware device
on the wireless handset to the processor that is on the removable
media device 202. The radio API 205 is a special wrapper routine
that may add additional information to the standard AT command for
wireless modem hardware 107 over a communication link 206. Other
aspects may include an embedded OS 106 running on the removable
media device.
[0017] FIG. 5 illustrates a block diagram of the removable media
device hardware design. One aspect of a removable media device 202
may include a processor 502 with RAM 501, ROM 503, and a
communication link 206.
[0018] In one aspect, the main processor functions of the handset
201 may be relocated to removable media device 202. This removable
media device 202 may be connected to the main handset 201 via a
communication link 206. In the wireless device 201, the wireless
radio 107 may be controlled by a basic processor 204 in the handset
201 that implements a radio API 205. The basic processor 204 in the
handset may be connected by a communication link 206 to the main
processor 502 in the removable media 202 where the user interface
and the application 103 are operating. A radio host side peer layer
203 implemented under the hardware control framework 105 may enable
a runtime environment 104 or an application 103 to be executed on
the removable media 202 as if each were executed on the main
processor 204 in the wireless handset 201. The radio host side peer
layer 203 may map the hardware from the wireless handset 201 using
the radio API 205. The radio API 205 may include the radio
equipment and network error standard definitions for error handling
sequences. The radio host side peer layer 203 may act as a virtual
hardware device. The radio host side peer layer 203 may receive
hardware commands from the device driver and put a TCP/IP wrapper
over the hardware command. The radio host side peer layer 203 may
then send the TCP/IP-wrapped hardware command to the radio API 205
on the handset side. The radio API 205 may remove the TCP/IP
wrapper and send the command to the hardware device 107 in the
wireless handset 201. During the boot up sequence, the radio host
peer layer 203 may negotiate with the radio API 205 on the handset
201 side to determine what devices are supported and what device
driver to install in the removable media device 202. During
negotiation, the radio API 205 on the handset 201 may communicate
to the host peer layer 203 what hardware and functionality the
handset 201 is equipped with. The radio host peer layer 203 may
then load the appropriate drivers on the removable media device
202, corresponding to the hardware configuration of the
handset.
[0019] In one aspect, registering the handset 201 with the network
or getting network information from the radio hardware 107 may be
accomplished by the runtime environment 104 in the removable media
device 202 by sending a command to the radio host peer layer 203
that communicates through a radio API 205 using a logical port on a
communication link 206 to the basic processor 204 on the wireless
handset 201. In one aspect, the communication link 206 may be a
bus, such as USB. In other aspects, the communication link 206 may
be a wireless connection. In further aspects, the communication
link 206 may be a high-speed bus. Further aspects include, but are
not limited to USB, SD, micro SD, SIM, SAM, and MMC as a
communication link 206. This API 205 may translate the command into
a command to the wireless radio modem hardware 107 to register or
get network information. The reply may be sent back to the API
logical port and back to the radio host peer layer 203 and up the
software layer with the reply.
[0020] Making voice phone calls from an application 103 running on
the removable media device 202 may be accomplished by appending the
number to call on the command to be sent to the radio host peer
layer 203 that communicate through a radio API 205 using a logical
port 207 on the communication link 206 to the basic controller on
the wireless handset 201. This API 205 may translate the command to
a command to the wireless radio modem hardware 107 to make a call
to that number. If successful, the voice channel to the speaker 108
and microphone 110 may be routed by the audio codec 109 to link to
the wireless radio modem 107. A success or failure message may be
sent back to the API logical port 205 and back to the radio host
peer layer 203 and up the software layer that is asking for the
service. To terminate the call, the application 103 may send a
radio API 205 command through the same path to terminate the radio
call. In another aspect, when making a call, the handset 201 may
behave as a device or slave to the removable media device 202, but
the handset 201 may still need to execute the radio API program 205
or monitor the radio hardware 107 for incoming calls or SMS
messages. In other aspects, a handset 201 may still contain a basic
processor 204 or baseband processor to handle real-time processes
such as monitoring the network and relaying commands from the radio
API 205 to the remote processes.
[0021] In another aspect, sending SMS messages may be similar to
making a call where a radio API 205 for SMS is sent to the wireless
handset basic processor 204 with the number to send and the message
payload. The radio API 205 may reply to the application with a
success or an error code.
[0022] According to one aspect, the flow charts in FIG. 3A and FIG.
3B illustrate the process of sending an SMS message. First, the
process starts 301 and a host peer application waits for a user
input or request 302. If such a request is present 303, the host
peer application retrieves the request type and any data to be
processed 304. Next, the data is sent to the host peer device
daemon 305. The host peer device daemon checks the data 306 to
determine whether it is a command or an event 307. If the data is
an event, the host peer device daemon sends an event code back to
the host peer application 308. If the data is a command, the host
peer device daemon encapsulates the AT command and data to be
forwarded 309. Next, the host peer device daemon sends the
encapsulated AT command and data to the handset via a communication
link 310. Then the host peer device daemon waits for an event or
response from the handset 311. If an event is received from the
handset 312, the host peer device daemon returns to check more data
being received from the host peer application. If an event is not
received 313, the handset receives the encapsulated AT command and
data via the communication link 314. Next, the handset sends the AT
command to the baseband processor 315. The baseband processor then
waits for an event or response from a wireless network 316. If an
event is not received 317, it continues waiting for an event. If an
event is received, the baseband processor sends back AT events or
errors to the host peer application through the communication link
318. The process to send an SMS message is now completed 319.
[0023] Accessing HSPDA or GPRS networks may be accomplished by
sending a radio API command to set up a internet network. Once that
network is made, the basic controller in the handset 204 may set up
a TCP/IP network bridge 207 that connects the OS 106 on the
removable media device 202 to the internet via the TCP/IP bridge
207 to the wireless radio modem 107. The OS 106 on the removable
media device 202 may treat the wireless radio modem 107 as a modem
device. Web Browser and internet applications may then make use of
this service.
[0024] FIG. 4 shows an implementation of the removable media device
202 and the wireless radio handset 201.
[0025] In one aspect, an OpenMoko Neo Free Runner handset may be
used, though any hardware configuration is possible. In further
aspects, handset applications and the runtime environment may be
removed and replaced with the radio API 205. In other aspects, a
Samsung S3C2443 development board may be used as the removable
media device 202.
[0026] In another aspect, Linux may be chosen as an open source
operating system 106. Other operating systems available may
include, but are not limited or restricted to Win CE, Symbian or
any other embedded operating system. Another aspect may include X
Window, but any other graphic system may be used 402. Another
aspect may include MatchBox as a runtime environment, but any
runtime environment such as Android, QT, MontaVista, Openmoko, or
any other runtime environment may be used 104.
[0027] In one aspect, the radio hardware 107 may not be present in
the removable media device 202; instead, the radio driver 404 may
pass the radio command to the host peer API or a daemon 401. In
further aspects, the radio driver 404 may control virtual hardware
406 using the radio API 205 in the remote handset 201. The wireless
radio handset 201 may include an OS 408 and a driver 409. The
removable media device 202 may have a USB driver 403. The flow of
information from an application 103 that requires access to the
radio hardware 107 is depicted by the arrow and the sequence in the
numbered bubble shown in FIG. 4. The sequence is as follows,
including when a SMS application sends out an SMS message:
[0028] The user may complete the SMS message and may execute the
send command, the application may send the AT command with data to
the radio device driver software, as shown by 451.
[0029] The radio driver software driver on the removable media
device may not have wireless modem hardware. Instead of sending
directly to the hardware, the radio driver software may send the
command to the host peer API or daemon software, as shown by
452.
[0030] The host peer API may encapsulate the command and data into
a TCP/IP packet and may send the packet to the communication link,
as shown by 453.
[0031] The removable media device may function as though the
wireless handset is a CDC RNDIS/ethernet device and may send the
TCP/IP packet to the wireless handset at a certain port number, as
shown by 454.
[0032] The wireless handset may receive the packet and may send the
packet to the radio API running on the wireless handset baseband
processor, as shown by 455.
[0033] The radio API on the wireless handset may listen to the
TCP/IP at a certain port number. Once the packet is received, the
radio API may remove the AT command and data from the packet, as
shown by 456. As there may be differences in AT commands for
different radio hardware, the radio API may check if this command
is directly supported by this radio hardware and performs the
necessary command changes if it supports the hardware command set.
Thus, different hardware configurations may still work because the
radio API performs the compatibility changes with the AT
command.
[0034] As shown by 457, the wireless radio modem hardware may
receive the command and may execute an error code and may return
the error code to the calling application through the reverse order
of information flow (e.g., step 457 back to step 451).
[0035] Advantages of embodiments of the present invention may
include one or more of the following: (1) the cost of handset may
be lower and may require shorter development time because the
handset only requires implementing the radio API with a lower
performance processor; (2) the user interface, runtime environment
and applications may not need to be developed for the handset
because they may already be implemented in the removable media
device.
[0036] In another aspect, the applications and runtime environment
can be run on any handset that implements the radio API. In further
aspects, the applications and runtime environment are portable
across all handsets implementing the radio API without changes to
their code.
[0037] In one aspect, all the application and data stored in the
removable media device is portable and will run on any handset that
implement the radio API. In further aspects, the user may preserve
their applications and data even if when transferring the removable
media device to a handset with a different hardware design, as long
as the radio API is implemented.
[0038] Although illustrative embodiments have been shown and
described herein in detail, it should be noted and will be
appreciated by those skilled in the art that there may be numerous
variations and other embodiments that may be equivalent to those
explicitly shown and described. For example, the scope of the
present invention is not necessarily limited in all cases to
execution of the aforementioned steps in the order discussed.
Unless otherwise specifically stated, terms and expressions have
been used herein as terms of description, not of limitation.
Accordingly, the invention is not to be limited by the specific
illustrated and described embodiments (or the terms or expressions
used to describe them) but only by the scope of claims.
* * * * *