HK1140894B - A communication system, a user identification card and its operating method - Google Patents

Description

Communication system, subscriber identity module card and operating method thereof

Technical Field

The present invention relates to a wireless phone, and more particularly, to a wireless phone having a subscriber identity card built therein.

Background

Cellular, satellite and other types of mobile telephones are well known. Cellular telephones and other user terminals typically include a removable Subscriber Identity Module (SIM) card on which a service-Subscriber key (service-Subscriber key) is stored. When a user accesses the cellular or satellite network, the key is used to authenticate and identify whether the user is a user within the cellular or satellite network. Cellular network operators typically provide voice call services, data communication services, and Short Message Services (SMS). Each mobile telephone has one or more cellular network-specific transceivers for providing voice, data, and short message communications. For example, a transceiver supporting a GSM cellular network connection is different from a transceiver supporting a north american CDMA cellular network connection.

The mobile phone may support a variety of additional functions such as Global Positioning System (GPS) reception operation, Near Field Communication (NFC), bluetooth communication, Frequency Modulation (FM) radio reception, infrared communication, and the like. Typically, mobile phones must have built-in (build-in) hardware and software to support these additional functions. For example, when communicating with other bluetooth devices, the mobile phone must have a bluetooth compatible transceiver (i.e., a transceiver that can support a bluetooth air interface). In GPS operation, the mobile phone must have a GPS receiver capable of acquiring the frequencies transmitted by the GPS satellites. For near field communication with a reader, smart card or other NFC device, the mobile phone must have an NFC compatible radio. To support short-range Infrared (IR) data communication between a mobile phone and a computer or a Personal Digital Assistant (PDA), the mobile phone needs to have an Infrared transceiver, i.e., a Light Emitting Diode (LED) and its supporting circuits. The hardware to support these additional functions is expensive. The user must purchase an expensive handset with a variety of additional features even though it only requires one or two of the features. Furthermore, when a user needs a function that is not supported by his or her existing handset, he/she must upgrade the device in order to obtain additional functions.

Other drawbacks and disadvantages of the prior art will become apparent to those of ordinary skill in the art in view of the present description of the system as it is being variously described.

Disclosure of Invention

The device and the operation method of the present invention will be explained in detail with reference to the accompanying drawings and examples.

According to an aspect of the present invention, there is provided a communication system including:

a telephone comprising a user input interface, a first wireless transceiver, and a first application program interface;

a subscriber identification card (SIM) inserted in the phone, the SIM card including a memory, a second wireless transceiver, and a second application program interface.

The phone uses the subscriber service key stored in the memory of the SIM card to obtain a plurality of services provided by the wireless network via the first transceiver in accordance with the first communication protocol.

The first application program interface interacts with the second application program interface in response to user selections entered via the user input interface,

through interaction of the first application programming interface with the second application programming interface, the phone communicates with a node using the second wireless transceiver in accordance with a second communication protocol.

Preferably, the telephone communicates with the node via a wireless link.

Preferably, the plurality of services provided by the wireless network includes a voice call service.

Preferably, the first application program interface adds an icon corresponding to the second wireless transceiver to a list of available functions for the phone.

Preferably, the first application program interface interacts with the second application program interface corresponding to the selected icon.

Preferably, the telephone receives the first application program interface from a second memory.

Preferably, the second storage is a remote web server (remote web server).

Preferably, the phone retrieves (retrieves) the first application program interface from the remote web server over the wireless network using the first wireless transceiver.

According to another aspect of the present invention, there is provided a subscriber identity card comprising:

a memory storing a user service key;

a wireless receiver that receives data from a device in accordance with a communication protocol; and

an application program interface that enables the phone to operate the wireless receiver when a subscriber identification card is inserted in the phone.

Preferably, the subscriber identity card further comprises: a wireless transmitter for transmitting data to the device.

Preferably, the application program interface enables the telephone to operate the wireless transmitter when the subscriber identity card is inserted in the telephone.

Preferably, the subscriber identity card further comprises: telephone function control software.

Preferably, the application program interface and the telephone function control software enable the telephone to operate the wireless receiver through its user input interface.

Preferably, when the subscriber identity card is inserted in the phone, said application program interface looks up a counterpart (counter) of said application program interface in said phone.

Preferably, when the api does not find the counterpart in the phone, the api adds information to the user service key.

According to still another aspect of the present invention, there is provided an operating method for a phone and a subscriber identity card inserted in the phone; the telephone comprising a first wireless transceiver, a user input interface for operating the first wireless transceiver; the user identification card comprises a second wireless transceiver and a first application program interface; the method comprises the following steps:

the first application program interface causes the phone to retrieve a second application program interface and install the second application program interface on the phone;

a second application program interface assigns (designation) a portion of a user input interface to operate the second wireless transceiver; and

in response to selection of the assigned portion of the user input interface, the first application program interface enables communication through the second wireless transceiver.

Preferably, the method further comprises: a second application program interface is received through the first wireless transceiver.

Preferably, the method further comprises: receiving, by the first wireless transceiver, an updated first application program interface and an updated second application program interface.

In order that the various aspects of the invention may be more readily understood and put into practical effect, several embodiments will now be described in detail with reference to the accompanying drawings, which are included to illustrate and not to limit the invention.

Drawings

Fig. 1 is a block diagram of a mobile phone that may support a number of additional functions via a radio transceiver (radio) disposed on a subscriber identity card inserted into the phone, in accordance with various embodiments of the present invention;

FIG. 2 is a block diagram of additional hardware and software modules disposed in a cellular telephone (cellular phone) and SIM to enable the cellular telephone to obtain additional services in accordance with one or more embodiments of the present invention;

FIG. 3 is a block diagram of additional hardware and software modules disposed in a cellular telephone (cellular phone) and SIM to enable the cellular telephone to acquire GPS services in accordance with one or more embodiments of the present invention;

FIG. 4 is a block diagram of a cellular telephone interacting with a Bluetooth device via a wireless transceiver on its subscriber identity card in accordance with one or more embodiments of the present invention;

FIG. 5 is a block diagram of a satellite phone interacting with an NFC device via an NFC compatible radio on a subscriber identification card inserted therein in accordance with one or more embodiments of the present invention;

FIG. 6 is a flowchart of a method of operating an Application Program Interface (API) resident on a subscriber identity card, wherein the subscriber identity card includes a radio transceiver device, and the API allows a telephone to use the radio transceiver device on the subscriber identity card when the subscriber identity card is inserted into the telephone, in accordance with one or more embodiments of the present invention; and

fig. 7 is a flow diagram of a method of operation of an application program interface resident in a phone that communicates through a wireless transceiver device on a subscriber identity card inserted therein in accordance with one or more embodiments of the present invention.

Detailed Description

Fig. 1 is a block diagram of a mobile phone that may support a number of additional functions via a radio transceiver (radio) disposed on a subscriber identity card (SIM) inserted in the phone, in accordance with various embodiments of the present invention. The phone 120 receives a number of additional services through a radio 140 on the SIM130 inserted in the phone 120. The phone 120 is a cellular phone or satellite phone or other type of wireless phone that supports subscription services. Subscribers to the cellular/satellite network use the cellular/satellite phone 120 to obtain a plurality of services provided by the cellular/satellite network. Cellular/satellite phone 120 includes a cellular/satellite transceiver, memory, a display screen, a user input interface, a speaker, and a microphone for enabling communication with a cellular/satellite network using the cellular/satellite transceiver. A cellular/satellite transceiver is a transceiver for transmitting and receiving signals on a frequency band allocated for cellular/satellite communications. During operation, the SIM130 remains inserted in the phone 120, with the subscriber service key stored in the SIM's memory. The phone 120 authenticates itself to the communication network (cellular/satellite communication network) through the access point 110 using the subscriber service key stored in the SIM 130. Based on the identification, the cellular/satellite network verifies whether the phone 120 has authority to obtain one or more services provided by the cellular/satellite network. Such as, but not limited to, voice call services, data services, and short message services.

In another embodiment, telephone 120 is a cellular telephone and radio 140 of SIM130 is, for example, but not limited to, an FM receiver. The radio transceiver device 140 is a Radio Frequency (RF) receiver adapted to acquire signals transmitted by FM radio stations. The cellular radio of the cellular telephone (handset) 120 is adapted to acquire signals transmitted by another cellular radio station and not to acquire signals transmitted by an FM radio station because the FM radio station and the cellular radio station operate on different frequency bands. In addition to the FM radio 140, the SIM130 includes first extended Application Program Interface (API) software. The cellular phone 120 receives the second extended API software from a web site (Website) or from the SIM130, or from various external resources through the computer. The cellular telephone 120 stores the second extended API in the memory of the telephone 120. The second extended API interacts with the user input interface of cellular telephone 120 so that the user can use cellular telephone 120 to operate FM radio 140 on SIM130, with SIM130 remaining plugged in to cellular telephone 120. For example, the user input interface of the cellular phone 120 may be a keypad (keypad), the second extended API assigning a pair of keys of the keypad for turning the FM radio 140 on, off, and tuning the FM radio 140 to a different FM radio station. The user can operate the FM radio receiving apparatus 140 by using the pair of keys on the keypad. In another embodiment, the user input interface may be a touch screen. In yet another embodiment, the second extended API installs an icon (icon) corresponding to the FM receiver into the list of available functions of the cellular phone 120 and/or adds an entry (item) corresponding to the FM receiver to the list of available functions of the cellular phone 120. The user operates the FM receiver by selecting an installed icon and/or an installed entry from the list of available functions.

When the user selects one of the set keys or selects an icon corresponding to the FM radio 140, the second extended API interacts with the first extended API stored in the SIM 130. The second extended API requests the first extended API to turn on the FM radio 140 in response to the user selecting the button designated as FM radio 140 "on". The first extended API turns on the FM radio 140 in response to the request, and transmits the signal acquired by the FM radio 140 to the cellular phone 120. The second extended API then passes the signal acquired by FM radio 140 to the microphone of cellular telephone 120.

As one non-limiting example, a user may sign up for voice and data services provided by a cellular network operator. A user purchases SIM130 from a carrier, and an FM radio 140 is disposed in SIM 130. The SIM130 has a subscriber service key and a first extended API stored in the SIM130 memory. When the SIM130 is inserted in the cellular telephone 120, the cellular telephone 120 is allowed to use the subscriber service key to prove its identity to the cellular network. After identification, the cellular network operator verifies that the cellular telephone 120 can use voice and data services provided by the cellular network operator. To operate the FM receiver on the SIM130, the user downloads the second extension API from the carrier website using a personal computer or notebook, and then forwards the second extension API to the cellular telephone 120 using a wired connection (connected connection). The second extended API installs additional control options on the phone 120 such as radio on, radio off, radio channel change, etc. The user uses these additional control options to operate FM radio 140 on SIM 130. Signals transmitted by the FM radio transmitter 174 are received by the FM radio 140 and the received signals are heard through a microphone on the telephone 120. Although there is no FM receiver built into phone 120, cellular phone 120 may receive signals of an FM radio station through an FM receiver on SIM130, where SIM130 is plugged into cellular phone 120. The first extended API in SIM130 interacts with the second extended API in phone 120 enabling operation of the FM receiver on the SIM using the user input interface of cellular phone 120.

The radios 140 on the SIM130 may be, for example, GPS receivers, bluetooth radios, NFC-compliant radios, and the like. When SIM130 is inserted in phone 120 and radio 140 is a GPS receiver, cellular phone 120 receives signals from GPS satellites 172 through radio 140 on SIM 130. The phone 120 is provided with a second extended API by the cellular network operator or by the manufacturer of the SIM130 with the radio 140 or by a third party. In another embodiment, the phone 120 is a satellite phone and communicates with a satellite over a satellite frequency band. If a SIM with a bluetooth radio 140 is inserted in the satellite phone 120, the phone 120 may additionally communicate with a bluetooth enabled device 178. The phone 120 sends and receives information to and from the bluetooth enabled device 178 through the bluetooth radio 140 on the SIM 130. If the radio 140 on the SIM130 is capable of receiving and transmitting signals in accordance with (bursturant) NFC, the phone 120 communicates with the NFC-compliant device 176 via the radio 140. The telephone 120 uses the radio on the telephone 120 to communicate with the communication network (cellular or satellite) to which the telephone is subscribed. A number of additional services 160 may be available to the phone 120 with the SIM130 inserted, depending on the type of radio 140 on the SIM 130.

The radios 140 on the SIM130 are one or more of a GPS receiver, FM receiver, NFC radio, bluetooth radio, and the like. The cellular or satellite network needs to identify and authenticate the cellular or satellite phone using the user service password (which has been stored in the SIM before the cellular/satellite phone has acquired the services provided by the cellular/satellite network). The SIM is an integral part of the cellular/satellite phone. The GPS architecture, FM wireless network, NFC-compatible device, or bluetooth-compatible device no longer requires authentication of the GPS receiver/FM receiver/NFC transceiver/bluetooth transceiver before communicating with another transceiver of the same type. The GPS receiver, FM receiver, NFC device, and bluetooth device do not require a SIM. The operation and business model of cellular/satellite networks is different from that of FM wireless networks, bluetooth devices, NFC devices, and GPS devices.

Fig. 2 is a block diagram of additional hardware and software modules disposed in a cellular telephone and SIM that enable the cellular telephone to obtain additional services in accordance with one or more embodiments of the present invention. The hardware and software modules provided in the cellular telephone 250 and the SIM 210 enable the cellular telephone 250 to obtain a number of additional services through the radio 140 on the SIM. Cellular telephone 250 includes a display screen/display 262, a display interface (I/F)264, processing circuitry 266, memory 268, a cellular transceiver 270, a user input interface (I/F)272, and telephone function acquisition software 274. A typical user input I/F272 is a keypad. In one embodiment, the display 262 is a touch screen that, in addition to a keypad, also serves as a user input I/F for the cellular telephone 250. The cellular transceiver 270 is used to transmit and receive signals over the frequency band in which the cellular network operates. The cellular telephone 250 communicates with the access point/base station 294 through a cellular transceiver 270. The access point 294 is communicatively connected to the backbone cellular network.

SIM 210 includes a memory 220 on which is stored an Integrated Circuit Card Identifier (ICCID)222 for identifying SIM 210, an International Mobile Subscriber Identity (IMSI)224 for identifying the network operator issuing SIM 210, and an authentication key (Ki) 226 for use by SIM 210 during authentication of telephone 250. The service software 234 includes code required by the SIM 210 to perform subscriber management functions, including, for example: generate keys during authentication of telephone 250 by the cellular network, store location information of telephone 250, and update location information when a change in the location of telephone 250 occurs.

SIM 210 additionally includes a radio 230, a radio I/F232, and an extended API 236. The wireless transceiving means 230 is one or more of a receiver and a transmitter. For example, the radio 230 is a satellite radio receiver. The frequency band of operation of the satellite receiver is different from the frequency band in which the cellular transceiver 270 operates. Extended API236 is a component that enables SIM 210 to manage interactions between wireless transceiver device 230 and telephone 250 when SIM 210 is plugged into telephone 250. SIM 210 also optionally includes telephone function control software 238.

The cellular telephone 250 must prove its identity to the cellular network before using the services provided by the cellular network. The authentication process begins with the cellular telephone 250 retrieving the IMSI 224 from the SIM 210 (inserted in the telephone 250) and sending this IMSI 224 to the access point 294 via the cellular transceiver 270. The cellular telephone 250 then passes the information received from the access point 294 to the SIM 210, or vice versa, via the transceiver 270. Once the authentication is successful, the cellular telephone 250 receives the location information from the access point 294 and passes this location information to the SIM 210 for storage in the memory 220. The cellular telephone sends and receives short messages, voice and data from the access point 294 through the transceiver 270. The extended API236 looks up its counterpart (counter) in the phone 250. In one embodiment, this information is displayed on display 262 of telephone 250 when the counterpart of this extended API236 is not present in telephone 250. SIM 210 uses telephone function control software 238 to access the display 262 of telephone 250.

Telephone 250 receives extended API response 276 from one or more storage devices via a wired connection (wired connection), extended API response 276 from a web site via access point 294 and cellular transceiver 270, extended API response 276 from a cellular network operator's server via access point 294 and cellular transceiver 270, and so on. The extension API counterpart 276 is code for causing the telephony function access software 274 and the extension API236 to interact. The extended API counterpart 276 provides a working channel for operating the radio 230 on the SIM 210 via the user input I/F272 of the phone 250. If the user input I/F272 is a plurality of keys, the extended API correspond 276 identifies a portion of the keys of the user input I/F272 that are used to operate the wireless transceiving means 230. The wireless transceiver 230 is, for example but not limited to, an NFC compatible transceiver. The extended API counterpart 276 identifies the keys from the user input I/F272 and causes the "receive", "transmit", "stop" functions in the wireless transceiving apparatus 230. If user input I/F272 of telephone 250 is a touch screen, extended API correspondence 276 adds an entry or icon corresponding to wireless transceiving device 230 to the list of available functions of telephone 250. A user browsing this list of available functions operates the radio 230 on the SIM 210 via the touch screen 262 of the phone 250 and using the newly added entry or icon.

For example, the user selects a key corresponding to the "receive" function of the wireless transceiver device 230 via the user input I/F272. The extended API counterpart 276 sends a request to the extended API236 to set the wireless transceiving means 230 in the receiving mode in response to the user's selection. In response to this request, extended API236 instructs wireless transceiving device 230 to receive data from an external source. Extension API236 further instructs transceiver 230 to pass the received data to processing circuitry 266 of telephone 250. The processing circuitry 266 executes instructions from the extended API counterpart 276 to store the received data in the memory 268 of the phone or to process the received data for future use. Conventional cellular telephone 250, although not equipped with an NFC radio, can communicate with NFC-compliant devices through radio 230 on the SIM (plugged into cellular telephone 250).

Fig. 3 is a block diagram of additional hardware and software modules disposed in a cellular telephone and SIM that enable the cellular telephone to acquire GPS services in accordance with one or more embodiments of the present invention. As shown in fig. 1, additional hardware and software modules in cellular telephone 120 and SIM130 enable cellular telephone 120 to acquire GPS services. The SIM 310 is inserted in the cellular phone 350. The phone 350 uses the information stored in the memory 338 of the SIM 310 to authenticate itself to the cellular network. After verification is passed, the cellular telephone 350 communicates with the cellular network using the cellular transceiver 370 and through the access point 394. The phone 350 is adapted to obtain a plurality of services offered by the cellular network operator via the access point 394. These multiple services include, for example, but are not limited to, voice services, data services, and short message services.

The SIM 310 includes additional hardware, such as a GPS receiver 320, and additional software, such as a receiver I/F332, GPS service software 334, a first GPS API340, and phone function control software 336. The telephony feature control software 336 is independent of the additional hardware and may be independent of the additional software. The GPS receiver 320 is used to receive signals from GPS satellites 390. The GPS service software 334 ascertains the location of the SIM 310 based on signals received by the GPS receiver 320 from the GPS satellites 390. The first GPS API340 allows the cellular telephone 350 to acquire signals received by the GPS receiver 320 or to interact with the GPS service software 334. The telephone function control software 336 interacts with the user input I.F 372 of the telephone 350 to modify the list of functions available on the telephone 350. Additional hardware and additional software are embedded in the SIM 310 by the SIM manufacturer. The cellular network operator writes network specific information into the memory 338 of the SIM 310. A user of the cellular telephone 350 who cannot obtain GPS service due to the absence of a GPS receiver in the telephone 350 may purchase the SIM 310 from a cellular network operator and insert the SIM 310 into the cellular telephone 350. Whenever the phone 350 needs to acquire one or more of the services provided by the cellular network, the phone 350 uses the network-specific information stored in the SIM 310 memory 338 to authenticate itself to the cellular network.

The phone 350 requires additional software: a second GPS API376 for interacting with the GPS service software 334 and receiving signals received by the GPS receiver 320. The phone 350 receives the second GPS API376 from the memory device through a wired connection or the second GPS API376 from the cellular network operator through the access point 394. The storage device is one or more compact discs, USB memory, or computer memory, etc. The second GPS API376 is copied from the memory device into the memory 368 of the phone 350, for example, by a laptop computer. In another embodiment, phone 350 receives second GPS API376 from a remote server side of the SIM manufacturer using packet data services provided by the cellular network operator. The second GPS API376 enables the phone 350 to control the GPS receiver 320 on the SIM 310.

When the SIM 310 is plugged in the cellular telephone 350, the first GPS API340 looks for the second GPS API in the telephone 350. When the presence of the second GPS API376 in the phone 350 is detected, the first GPS API340 instructs the phone function control software 336 to modify the list of available functions on the phone 350. The phone function control software 336 interacts with the second GPS API376 and adds entries to the list. The user acquires GPS service by selecting a new entry from the list of available functions. The phone function control software 336 interacts with the second GPS API376 to further add sub-entries to the entry corresponding to the GPS service. By selecting one or more of the sub-entries, the user is able to, for example and without limitation, turn on GPS receiver 320, turn off GPS receiver 320, view location information generated by GPS service software 334 on the display screen via display interface 364 and processing circuit 366 of telephone 350, receive GPS service updates via GPS receiver 320, store GPS service updates 380 into the memory of telephone 350. The phone function control software 336 interacts with the second GPS API376 through the first GPS API 340. The second GPS API376 passes an indication from the first GPS API340 to the phone function acquisition software 374 corresponding to adding an entry and/or sub-entry to the list of available functions. For example, the user selects a sub-entry corresponding to the position information displayed on the display screen 362. In response to the user selection, the second GPS API376 requests the first GPS API340 to send location information to the phone 350. The first GPS API340 retrieves the location information from the GPS service software 334 and forwards it to the second GPS API 376. The second GPS API376 instructs the phone function acquisition software 374 to display the location information on the display 362. The phone function acquisition software 374 responds to this indication by displaying the location information retrieved from the SIM 310 on the display 362. The GPS service software 334 determines the location of the SIM 310 (i.e., the phone 350) based on the signals received by the GPS receiver 320. In yet another embodiment, the GPS service software 334 is placed in the phone 350 to conserve the processing functionality of the SIM 310. The phone 350 receives GPS service software from a storage device via a wired connection or a wireless connection. The storage device is one or more compact discs, a web server, or a USB memory.

Fig. 4 is a block diagram of a cellular telephone interacting with a bluetooth device via a radio on its subscriber identity card in accordance with one or more embodiments of the present invention. The cellular telephone 462 interacts with the bluetooth device 470 through the radio 482 on the SIM460, wherein the cellular telephone 462 receives from the memory device the software necessary for operating the radio 482. The SIM460 includes a memory 492 for storing cellular network specific information and subscriber specific information. The SIM460 remains plugged into the phone 462 at all times so that the cellular phone 462 can always obtain cellular network specific information and subscriber specific information. Before the phone 462 acquires the services provided by the cellular network, the cellular phone 462 authenticates itself to the cellular network using the cellular network specific information and the subscriber specific information stored in the SIM 460. The cellular telephone 462 includes a transceiver for transmitting and receiving signals over the operating frequency band of the cellular network. The phone 462 establishes a first wireless communication link with the first access point 430 and communicates with the first access point 430 over the first wireless link using the transceiver.

The SIM460 includes a bluetooth radio 482, a radio I/F484, bluetooth services software 486, a bluetooth API488, and phone function control software 490. The cellular phone 462 communicates with bluetooth enabled devices using a bluetooth radio 482 on the SIM 460. An Application Program Interface (API) or software is provided on the phone 462 that interacts with a SIM side bluetooth API488 to operate the bluetooth radio 482. The cellular phone 462 retrieves the phone's side API from memory via a wired connection and/or a wireless connection. For example, the phone side API is stored in a web server 420 belonging to the bluetooth radio manufacturer. The user of phone 462 receives the phone-side API from web server 420 over a second wireless link on laptop 450. The laptop 450 is configured to receive data packets from the second access point 440 via the second wireless link using the ieee802.11x protocol. The second access point 440 is communicatively connected to the web server 420 through an internet backbone (internet backbone). The cellular phone 462 is wired to the notebook computer 450. The phone 462 receives phone side APIs from the laptop 450 through a wired connection.

In another embodiment, the phone 462 receives the phone-side API from the first access point 430 over the first wireless link. The first access point 430 is communicatively coupled to the web server 420 via a backbone cellular network 432 and a backbone internet network 410. If the cellular phone 462 subscribes to packet data services provided by the cellular network, the cellular phone 462 receives the phone-side API from the first access point 430. In yet another embodiment, the phone-side API is stored in a second web server belonging to the cellular network operator. The cellular phone 462 receives the phone-side API from the second web server through the first access point 430 (implemented through the first wireless connection in another embodiment). In addition, the phone side API may also be stored in the compact disc. Telephone 462 does not have a disc reader (disc reader), so telephone 462 retrieves the phone side API from the compact disc via notebook computer 450 (including the compact disc reader).

The phone 462, equipped with a phone side API, interacts with a SIM side API488 to operate and control the bluetooth radio 482. The phone side API, along with SIM side API488 and phone function control software 490, modifies the user input I/F of phone 462, using which bluetooth radio 482 can be operated and controlled. The user input I/F of phone 462 is one or more of a plurality of keys or a touch screen or the like. Bluetooth radio manufacturers release updated and/or new versions of the phone side API and/or SIM side API 488. Phone 462 retrieves updated and/or new versions of the two APIs (phone side API and/or SIM side API 488) from web server 420 via laptop 450. In addition, phone 462 may also receive updated and/or new versions of the two APIs from first Access Point (AP)430 using a cellular transceiver on phone 462. Phone 462 sends the updated and/or new version of SIM-side API488 to SIM 460.

Fig. 5 is a block diagram of a satellite phone interacting with an NFC device via an NFC-compliant radio on a subscriber identification card inserted therein in accordance with one or more embodiments of the invention. Satellite phone 540 communicates with NFC device 530 through NFC-compliant radio 552 on SIM550 (inserted in satellite phone 540). Satellite phone 540 includes a transceiver for receiving data from satellite 520 and transmitting data to satellite 520. The satellite phone 540 is adapted to communicate with all satellites belonging to the satellite network 510 via the transceiver, although the phone 540 only communicates with one satellite at a time. The data may be one or more of voice data, packet data, short messages, and the like. After satellite network 510 authenticates satellite phone 540, satellite phone 540 may communicate with satellite 520. During the authentication process, the satellite phone 540 retrieves user-subscription data from the memory 558 of the SIM550 and transmits the user-subscription data to the satellite 520. The SIM550 remains plugged into the phone 540 so that the satellite phone 540 can obtain the user subscription data. After the satellite network 510 successfully authenticates, the satellite phone 540 begins communicating with the satellite 520 over the first wireless link. The satellite phone 540 stores the network specific information in the memory 558 of the SIM 550. The satellite phone 540 uses the user subscription data and network specific information each time the satellite phone opens a communication call with the satellite 520 or any other satellite belonging to the satellite network 510.

The SIM550 includes an NFC radio 552, a radio I/F554, and a first API 556. NFC radio 552 is used to transmit data to and receive data from a second NFC radio over a range of a few centimeters to a few meters (as opposed to the transceiver on satellite receiver 540 communicating over hundreds of kilometers of distance with satellite 520). The transceivers (not shown) on the NFC radio 552 and the satellite phone 540 conform to different wireless link communication protocols. The user may operate NFC radio 552 using the input I/F of satellite phone 540. The input I/F of the satellite phone 540 is one or more of a keypad, a display screen, a touch screen, a pen, and the like. Satellite phone 540 needs to use the input I/F of satellite phone 540 through a second API to operate NFC radio 552 on SIM 550. When SIM550 is plugged into satellite phone 540, satellite phone 540 looks up the second API. In one embodiment, the second API is stored in the compact disc 570. The manufacturer of the NFC radio 552 provides the user with a compact disc 570. The user forwards the second API from the compact disc 570 to the laptop 580, which in turn forwards the second API from the laptop 580 to the satellite phone 540 via the wired connection. The second API may also be stored in various storage devices, such as USB memory, DVD, etc.

The second API is a code that interacts with the first API556 using the input I/F of the satellite radio 540 to ensure that the NFC radio 552 can be operated. The first API556 is another code that interacts with the NFC wireless transceiver I/F554. The second API interacts with telephony feature acquisition software stored in the phone 540. The second API instructs the phone function acquisition software to add an entry/icon into the list of available functions of the phone 540 and/or to assign one or more keys from the keys of the phone 540 for NFC radio operation based on the type of I/F input by the satellite phone 540. If the input I/F of satellite phone 540 is a combination of a display and keys, the second API and phone function acquisition software adds an entry to the list of available functions. The user operates the NFC radio 552 by selecting the new entry and selecting the standard key, such as but not limited to an ON key and an OFF key. After the user selects the open button, the second API interacts with the first API556 in response to the selection of the newly added entry, and the first API instructs the NFC radio 552 through the radio I/F554 to begin receiving or transmitting data from the NFC compliant device.

By way of example, satellite phone 540 is in proximity to an Automated Teller Machine (ATM)530, ATM 530 being used to read signals transmitted by the NFC radio. The user desires to authenticate himself to ATM 530 using user identification information stored in satellite phone 540. After selecting the open key of the keys, the user selects the entry corresponding to the NFC transceiver. In response to this selection, the second API sends the user identification information to the first API 556. The first API556 forwards this user identification information to the NFC radio 552. The NFC radio 552 transmits this user identification information to the ATM 530 over the second wireless link. Satellite receiver 540 communicates with ATM 530 over NFC radio 552 over a second wireless link using the NFC protocol. In this example, satellite radio 540 operates as NFC radio 552 to identify with ATM 530. In another embodiment, NFC radio 552 receives data from a second NFC device when satellite phone 540 is within a few centimeters of the second NFC device. The first API556 forwards the received data to the second API. The second API interacts with the display I/F of the phone 540 and displays the received data on the display screen of the satellite phone 540.

Fig. 6 is a flow diagram of a method of operation of an application program interface residing on a subscriber identity card, wherein the subscriber identity card includes a radio, the API allowing the phone to use the radio on the subscriber identity card when the subscriber identity card is inserted into the phone, in accordance with one or more embodiments of the present invention. As can be seen from the operation of fig. 6, the API is placed on the SIM containing the radio, wherein the API allows the phone to use the radio on the SIM when the SIM is plugged in the phone. The method begins with a SIM including a radio being inserted into a phone. The phone is a cellular phone, a satellite phone, or any other type of phone; these phones use the subscriber service key stored in the SIM to authenticate themselves to the cellular or satellite network or any other type of communication network before communicating with the communication network. In step 610, the API looks up a second API (which may be referred to as a phone-side API in the phone). If the API does not find a phone side API, the next step 620 is entered where the cellular/satellite/communications network is notified by the API. The API or SIM cannot communicate directly with the communication network. The telephone is used to send and receive data from the communication network through a transceiver on the telephone. The API embeds a message into the user service key that the phone side API on the phone does not exist. During the identification and authentication process, the phone sends the user service key to the communication network. The communication network receiving the user service key from the phone through the transceiver notices that there is no phone side API on the API. The communication network sends an alert message to the phone instructing the phone to download and install the phone side API. In addition, the communication network also sends a number of options for retrieving the telephony side API. The options include a remote web server, local storage such as a CD, and the like. If the phone has signed up for data service, a phone-side API from a remote web server may be received over the communication network. If the phone is not signed up for data service, the only option left is to receive the phone side API from local storage via the computer/laptop. Since the phone does not have a CD reader, a computer/notebook computer is required. If the local storage is a USB storage device and the phone has a USB port, the phone can directly receive phone-side APIs from the USB storage device. An API called SIM side API may be aware of the existence of phone side APIs on the phone through phone side APIs. In another embodiment, the SIM side API is aware of the existence of the phone side API when the phone side API first interacts with the SIM side API.

Once the phone side API is located on the phone, the SIM side API modifies the phone's user input I/F and/or adds functionality to the phone by interacting with the phone side API, as shown in step 630. The purpose of the SIM side API is to ensure that the user is able to operate the radio on the SIM through the user input I/F of the phone. The user input I/F of the phone is for example but not limited to a keyboard, a touch screen, etc. The phone may operate the radios on the SIM in the following ways, for example: selecting a key on a keyboard, selecting an entry on an available list, etc.

In step 640, the SIM side API receives a receive request from the phone side API. In step 645, the SIM side API, in response to the request, instructs the radio on the SIM to begin receiving data from the external resource. The phone side API triggers (trigger) this request by, for example, selecting a key from the phone's keypad or an icon from the phone's display. The radios on the SIM are bluetooth radios, NFC radios, FM receivers, GPS receivers, etc. The radio on the SIM is used to send and receive data from the second radio over a second wireless link, wherein communication between the radio on the SIM and the second radio does not require user authentication, as opposed to forced user authentication and identification by a cellular or satellite network. For example, the radio on the SIM is an NFC radio. The wireless transceiving means is for communicating with a second NFC-compliant device via the NFC protocol. No separate operator provides NFC services, so the NFC radios on the SIM do not perform user identification and authentication. The radio on the SIM receives data from an external source, i.e. an NFC-compliant device, following instructions from the SIM-side API. In step 650, the SIM side API forwards the data received on the phone SIM to the phone side API. Although the transceiver on the phone is not NFC compatible, the SIM side API enables the phone to receive data from NFC compatible devices through the NFC radio on the SIM. The data includes one or more of audio, video, pictures, multimedia, circuit switched data, packet switched data, short messages, and the like.

In step 660, the SIM side API receives a send request from the phone side API. In step 665, the SIM side API responds to the request by receiving data from the phone side API and forwarding the data to the wireless transceiver device on the SIM. In step 670, the SIM side API instructs the wireless transceiving means on the SIM to transmit data. The SIM side API ensures that the phone can send data through the radio on the SIM. In step 680, the SIM side API receives a software update message from the phone side API. The software update message relates to an update of an API on the SLM side, or an update of a service provided by a network through which the radio on the SIM receives and transmits data, or an update of driver software of the radio on the SIM. At step 685, the SIM-side API receives a software update from the phone-side API. If the software update is an update of the SIM side API, the SIM side API installs the software update.

Fig. 7 is a flow diagram of a method of operation of an application program interface resident in a phone that communicates through a wireless transceiver device on a subscriber identity card inserted therein in accordance with one or more embodiments of the present invention. In the embodiment shown in fig. 7, the phone is a cellular or satellite phone or other variety of phones that uses the subscriber service key stored in the SIM to authenticate and identify with the cellular or satellite network or any proprietary communication network. After the proprietary communication network is identified and verified, the phone is allowed to use the services provided by the communication network. The SIM remains plugged in the phone at all times unless service or replacement, etc. is no longer required. The phone has a transceiver for transmitting/receiving data to/from the private network through the transceiver. The SIM is provided with a wireless transceiver. The radio on the SIM is one of an FM receiver, an NFC radio, a bluetooth radio, a GPS receiver, etc. The business model of FM wireless networks, bluetooth devices, NFC devices, and GPS receivers is different from cellular/satellite networks, so unlike cellular/satellite networks, there is no need to use a SIM for authentication and identification.

In step 720, the API placed on the phone ensures that the phone can communicate using the wireless transceiver on the SIM in addition to using the transceiver on the phone to communicate with the proprietary communication network. If the radio on the SIM is a bluetooth radio, the API on the phone ensures that the phone can communicate with the bluetooth device using the bluetooth radio on the SIM. The SIM has a second API, referred to as the SIM-side API, placed on the SIM. The phone side API interacts with the SIM side API and phone function acquisition software disposed on the phone which ensures that the user input I/F of the phone is used to operate and control the radio on the SIM. As an example, the user input I/F of the phone is the display and keypad, and the radio on the SIM is the FM receiver. The phone side API instructs the phone function acquisition software to add an entry/icon to the phone's list of available functions. In step 730, after selecting the new entry/icon from the list of available functions, a key is selected from the keypad to use the FM receiver on the SIM. For example, the user selects the newly added entry/icon and then selects the "on" key on the keypad. The phone side API requests the SIM side API to turn on the FM receiver in response to the selection, as shown in step 740. In step 745, the phone side API further requests the SIM side API to forward the data received by the FM receiver to the phone. The SIM side API turns on the FM receiver and forwards data received by the FM receiver to the phone side API. The phone side API receives data forwarded by the SIM side API. If audio data, the phone side API forwards the data to the phone's speakers. If the data is image data, the phone side API displays the data on the display of the phone. If video data, the phone side API forwards the data to a multimedia player available on the phone.

For example, the transceiver on the SIM is a bluetooth transceiver. The user selects the newly added entry/icon, then selects the file from the phone's memory, and then selects the "on" key on the keypad. The phone side API retrieves the selected file from the phone's memory in response to the three selections, forwards the selected file to the SIM side API and requests the SIM side API to send the selected file via the wireless transceiver on the SIM, as shown in steps 760, 765, 770.

In another embodiment, the user selects an entry corresponding to "update" from the available list, as shown in step 780. If so, the phone side API responds to the selection, requesting the SIM side API to receive updates through the radio on the SIM. The updates may include one or more of updates to SIM-side APIs, updates to phone-side APIs, and so on. In another embodiment, the phone side API retrieves updates from the cellular/satellite network through a cellular/satellite transceiver on the phone. Typically, the updates are stored at a remote web server, from which the phone that has subscribed to the packet data services of the cellular/satellite network retrieves the updates through the cellular/satellite network and using a cellular/satellite transceiver on the phone, as shown in step 785. The phone side API installs the update and/or forwards the update to the desired destination. If the update belongs to an update of the SIM side API, then the phone side API forwards the update of the SIM side API to the SIM after receiving the update via the cellular/satellite transceiver.

The terms "circuit" and "circuitry" as used herein refer to either individual circuits or portions of multi-function circuits that perform multiple primary functions. For example, the processing circuitry may be implemented with a single chip processor or multiple processing chips, in accordance with one of the embodiments. Likewise, in one embodiment, the first circuit and the second circuit are combined on the same single chip, while in another embodiment, separate chips may be used independently to operate. The term "chip" as used herein relates to an integrated circuit. Circuits and circuitry may comprise, or include both general purpose or special purpose hardware, and associated software, such as firmware or object code.

As one of ordinary skill in the art will readily appreciate, the terms "operatively connected" and "communicatively coupled" as used herein encompass both a direct connection and an indirect connection via another component, element, circuit, or module. For indirect connections, the connection components, connection elements, connection circuits or connection modules do not modify the information of the signals, but may adjust their current, voltage and/or current values. It will also be understood by those of ordinary skill in the art that references to a connection (e.g., one element interfacing another element) include both direct and indirect connections, and that the connection between the two elements is in the same manner as "operably connected" and "communicatively connected".

The invention also describes the implementation of proprietary functions and relationships in connection with the method steps. The block diagrams of the functional groupings and the division and order of the method steps are arbitrarily defined herein for convenience of description. The partitioning and ordering can have other definitions as long as the proprietary functions and relationships are reasonably performed. Any such division or sequence is within the spirit and scope of the present invention.

The invention has been described in connection with functional block diagrams/modules illustrating the performance of certain important functions. For convenience of description, the division of these functions into block diagrams/modules is arbitrarily defined. The partition may have other definitions as long as it can reasonably perform some important function. For example, the functional module is a software and/or hardware module for performing a desired function, but is not limited to only hardware or only software. Similarly, flow diagrams are arbitrarily defined to illustrate certain significant functionality. For extension, the flow defines the division or order of the program blocks to perform some important function either in addition or as before.

It will also be apparent to those of ordinary skill in the art that functional building blocks and other illustrative blocks, modules, and components may be implemented as described herein, or by discrete components, application specific integrated circuits, processors executing appropriate software and the like, or any combination thereof.

Moreover, although the foregoing embodiments have been described in some detail for purposes of clarity of understanding. However, the present invention is not limited to these examples. It will be apparent to those skilled in the art that various changes and modifications may be made therein without departing from the spirit and scope of the invention. Such modifications or variations are intended to fall within the scope of the appended claims.

Claims (9)

1. A communication system, comprising:

a telephone comprising a user input interface, a first wireless transceiver, and a first application program interface;

a subscriber identification card inserted in the telephone, the subscriber identification card including a memory, a second wireless transceiver, and a second application program interface;

the telephone using the subscriber service key stored in the subscriber identity card memory to obtain a plurality of services provided by the wireless network via the first transceiver according to a first communication protocol;

the second application program interface searches the telephone for the first application program interface; when the second application programming interface does not find the first application programming interface in the phone, the second application programming interface adding information to the user service key, the phone receiving the first application programming interface from one or more storage devices via a wired connection, from a web address via an access point and a cellular transceiver, or from a server of a cellular network operator via an access point and a cellular transceiver;

the first application program interface interacting with the second application program interface in response to a user selection input via a user input interface; and

through interaction of the first application programming interface with the second application programming interface, the phone communicates with a node using the second wireless transceiver according to a second communication protocol.

2. The communication system of claim 1, wherein the telephone communicates with the node via a wireless link.

3. The communication system of claim 1, wherein the plurality of services provided by the wireless network includes a voice call service.

4. The communication system of claim 1, wherein the first application program interface adds an icon corresponding to the second wireless transceiver to a list of available functions for the phone.

5. The communication system of claim 4, wherein the first application program interface interacts with the second application program interface corresponding to the selected icon.

6. A subscriber identification card, comprising:

a memory storing a user service key;

a wireless receiver that receives data from a device in accordance with a communication protocol; and

an application program interface that enables the phone to operate the wireless receiver when a subscriber identification card is inserted in the phone;

when the user identification card is inserted into a telephone, the application program interface searches the telephone for a corresponding piece of the application program interface; when the API does not find the counterpart in the phone, the API adds information to the user service key.

7. The subscriber identity card of claim 6, further comprising: a wireless transmitter for transmitting data to the device.

8. A method of operation for a telephone and a subscriber identity card inserted in the telephone, the telephone comprising a first wireless transceiver, a user input interface for operating the first wireless transceiver; the user identification card comprises a second wireless transceiver and a first application program interface; characterized in that the method comprises:

the first application program interface enables the telephone to retrieve the second application program interface and installs the second application program interface on the telephone, wherein the first application program interface searches the second application program interface in the telephone, and when the first application program interface does not search the second application program interface in the telephone, the first application program interface embeds the message that the second application program interface does not exist in the user service key sent to the communication network; the phone receiving the second application program interface from one or more storage devices, from a web site through the access point and the cellular transceiver, or from a server of a cellular network operator through the access point and the cellular transceiver over a wired connection;

a second application program interface assigns a portion of a user input interface to operate the second wireless transceiver; and

in response to selection of the assigned portion of the user input interface, the first application program interface enables communication through the second wireless transceiver.

9. The method of claim 8, further comprising: a second application program interface is received through the first wireless transceiver.