WO2010060344A1 - Handset, smart card and method for controlling peripheral devices of handset with smart card - Google Patents
Handset, smart card and method for controlling peripheral devices of handset with smart card Download PDFInfo
- Publication number
- WO2010060344A1 WO2010060344A1 PCT/CN2009/074809 CN2009074809W WO2010060344A1 WO 2010060344 A1 WO2010060344 A1 WO 2010060344A1 CN 2009074809 W CN2009074809 W CN 2009074809W WO 2010060344 A1 WO2010060344 A1 WO 2010060344A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- interface
- communication module
- smart card
- handset
- peripheral devices
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/545—Interprogram communication where tasks reside in different layers, e.g. user- and kernel-space
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Definitions
- the present invention relates to a mobile communication terminal, particularly to a handset, a smart card and a method for controlling peripheral devices of the handset with the smart card.
- a smart card such as the Next Generation Mega-SIM (NGMS) card, is now widely used in handsets to control peripheral devices of handsets. It is characterized in that the handset side has independent CPU and external devices; the smart card side also has independent CPU; a portion of application programs resides in the smart card side and the handset side accesses the server at the smart card side in Web mode and carries out application programs; and some application programs running at the smart card side need to access and control external devices of the handset side.
- NGMS Next Generation Mega-SIM
- FIG. 1 shows a illustrative configuration diagram of a prior art handset and a smart card, in which the smart card is a UICC (universal integrated chip card) and is provided with a web server, application programs, Java virtual machines (JVM) and communication protocols; and the handset side is provided with application programs, browser kernel and communication protocols (OS/FS, 7816, USB) and uses a TPAK platform.
- the smart card is a UICC (universal integrated chip card) and is provided with a web server, application programs, Java virtual machines (JVM) and communication protocols
- JVM Java virtual machines
- OS/FS browser kernel and communication protocols
- a general feature is that the smart card serves as a web server and some application programs are also provided in the smart card.
- the handset side accesses the server on the smart card in a Web mode and runs some corresponding application programs.
- This has the advantage of having some operations conducted by the CPU of the smart card, hence improving the performance of the overall system.
- the relationship between the application programs and the bottom layer device drivers needs to be handled.
- the bottom layer drivers of a handset are accessed via application programs on the handset side. Disadvantages of this mainly include the following two aspects.
- One disadvantage is that the complete control flow is long and the response time is long.
- Fig. 2 shows a control flow of controlling peripheral devices of a handset with a NGMS card. While application programs on the NGMS card are controlling peripheral devices of the handset, first, the application programs in the card determines control operations and transmits the operations to the corresponding application programs in the handset via TCP/IP. Next, the application programs in the handset analyze the received operations and then call the corresponding bottom layer drive interface to control peripheral devices to carry out corresponding operations.
- the curve across the handset and the smart card indicates the path of the control flow. It can be seen that in the control flow, application programs on the handset side are involved.
- Fig. 3 depicts a prior art control flow of opening an audio device (Audio device/dev/dsp) of a handset with a smart card.
- the control flow includes:
- the NGMS application program determines that the current operation is an open operation with the target of "/dev/dsp"; (2) It transmits this operation to the corresponding application program in the handset via TCP/IP; (3) The handset application program analyzes the received operation and calls the corresponding bottom layer drive interface: open interface, that is, Open ("dev/dsp"); (4) The Audio driver carries out Open() operation and returns a result indicating if the operation is successful; (5) The handset application program transmits the received result to the NGMS application program; (6) The NGMS application program receives the result. Till now, the Open operation is over and the process can continue.
- This control flow has the following disadvantages. It is necessary to implement corresponding application programs on the handset side repeatedly and then these application programs can be used to call the bottom layer device drivers. For different peripheral devices, interfaces between their NGMSs and application programs on the handset side need to be defined. The smart card and the handset are associated with each other too closely, and once one of them changes, corresponding parts thereof need to be changed totally. The control flow is relatively long and the system response time is not perfect.
- the present invention provides a handset, a smart card and a method for directly controlling peripheral devices of the handset by use of the smart card.
- the control flow can be simplified, the system response time and the system performance can be improved.
- the present invention provides a handset, in which a smart card is pluggable, the smart card comprising application programs for peripheral devices that are stored therein and a second communication module for communicating with the handset; the handset including: the peripheral devices; a card interface, adapted to interface with the smart card; and a first communication module, adapted to communicate with the second communication module of the smart card, and provide an uniform bottom layer drive interface for the peripheral devices, so that the second communication module maps the bottom layer drive interface provided by the first communication module to the smart card and provides the mapped bottom layer drive interface to the application programs in the smart card for use; when the application programs in the smart card call drive interfaces for the peripheral devices that are provided by the second communication module, the first communication module receives interface calls sent by the second communication module, and maps the received interface call to a drive interface of an actual peripheral device, so that the actual peripheral device performs a interface call operation.
- the peripheral device returns the result of the interface call operation to the first communication module; the first communication module sends the result to the second communication module; so that the second communication module returns the result to the application programs in the smart card.
- the handset may utilize Linux platform.
- the bottom layer drive interfaces provided by the first communication module include an open interface, a write interface, a read interface, an I/O control interface and a close interface for the peripheral devices.
- the open interface, the write interface, the read interface, the VO control interface and the close interface call corresponding drive interfaces in accordance with types of the peripheral devices.
- the first communication module processes a corresponding interrupt request, buffers data from the peripheral devices, and sends the data to the smart card.
- the present invention provides a smart card for a handset, the handset including peripheral devices, a card interface adapted to interface with the smart card, and a first communication module adapted to communicate with the smart card and provide an uniform bottom layer drive interface for the peripheral devices; the smart card including: application programs relating for the peripheral devices stored therein: a second communication module, adapted to communicate with the handset, map the bottom layer drive interface provided by the first communication module to the smart card, and provide the mapped bottom layer drive interface to the application programs in the smart card for use; wherein, when the application programs in the smart card call drive interfaces for the peripheral devices that are provided by the second communication module, the second communication module sends interface calls to the first communication module, so that the first communication module maps the received interface call to a drive interface of an actual peripheral device and the actual peripheral device performs a interface call operation.
- the present invention further provides a method for controlling peripheral devices of a handset by use of a smart card; the smart card is inserted in an card interface of the handset; a first communication module is provided between device drivers and upper layer application programs in the handset, is adapted to communicate with the smart card, and provides an uniform bottom layer drive interface for the peripheral devices; a second communication module is provided at a lower layer of application programs in the smart card, is adapted to communicate with the handset, maps the bottom layer drive interface provided by the first communication module to the smart card, and provides the mapped bottom layer drive interface to the upper layer application programs in the smart card for use; the method comprising: calling, by the upper layer application programs in the smart card, drive interfaces of the peripheral devices that are provided by the second communication module; sending, by the second communication module, interface calls to the first communication module; mapping, by the first communication module, the received interface calls to a drive interface of an actual peripheral device; and performing, by the actual peripheral device, a interface call operation.
- Fig. 1 is an illustrative configuration diagram of a prior art handset and a smart card
- Fig. 2 shows a control flow of controlling peripheral devices of a handset with a NGMS card in prior art
- Fig. 3 is a control flow diagram of opening an audio device of a handset with a smart card in prior art
- Fig. 4 is a structure block diagram of a handset and a smart card according to an embodiment of the present invention.
- Fig. 5 shows a control flow of controlling peripheral devices of a handset with a NGMS card according to an embodiment of the present invention
- Fig. 6 is a control flow diagram of opening an audio device of a handset with a smart card according to an embodiment of the present invention.
- Fig. 7 is a flow chart of controlling an audio module of a handset with a smart card according to an embodiment of the present invention.
- Fig. 4 shows a structure block diagram of a handset and a smart card according to an embodiment of the present invention.
- the smart card may be inserted into a card interface in the handset.
- Peripheral devices of the handset include, for example, an audio module, a video module and a camera head.
- Fig. 5 shows a control flow of controlling peripheral devices of a handset by use of a NGMS card according to an embodiment of the present invention.
- the Linux platform is utilized by the handset and the smart card.
- the present invention is not limited to handsets using Linux platform, and may also be applied to handsets using other platforms.
- the handset on the left side is provided with application programs, a driving socket module, TCP/IP protocol, device drivers and peripheral devices.
- the smart card on the right side is provided with application programs, a driving socket module and TCP/IP protocol.
- the curve across the handset and the smart card indicates the path of the control flow. It can be seen that in the control flow, it is not needed to go through application programs on the handset side (i.e., Handset Apps).
- a driver socket module (also known as DriverWrap module or DriverWrap) is added between the device driver and upper layer application programs, and primarily performs functions of communicating as a communication module and providing a uniform calling interface for upper layers by calling bottom layer device drivers, serving as a socket.
- DriverWrap module also known as DriverWrap module or DriverWrap
- Primary functions of the driver socket module on the handset side are as follows:
- Linux bottom layer device driver generally provides fundamental functions of open(), write(), read(), ioctl () and close() for opening, writing, reading, input output controlling and closing the peripheral devices respectively.
- Special functions of some special devices such as mmap() (mapping a file to memory) and release() (releasing resources), may be implemented by ioctl(). Therefore, in Linux system, the uniform drive interface provided by the DriverWrap layer may be defined as open(), write(), read(), ioctl() and close().
- the DriverWrap module needs to process corresponding interrupt request, buffer data from the device and then transmit it to the smart card side actively.
- asynchronous operations are manually converted into synchronous operations, to reduce complexity of interaction with application programs on the smart card side.
- a DriverWrop module is also added under application programs, and achieves following primary functions:
- the driver socket modules on the handset side and the smart card side, as communicating modules, may be implemented as hardware, software or combination thereof.
- Fig. 6 is a control flow diagram of opening an audio device of a handset by use of a smart card according to an embodiment of the present invention, in which the control flow of the method of an embodiment of the present invention is illustrated with opening Audio device/dev/dsp as an example. Explanation of the control flow is as follows: (1) The NGMS application program calls the interface provided by DriverWrap: Open("/dev/dsp");
- the DriverWrap on the handset side transmits the performed result to the NGMS side, and the DriverWrap on the NGMS side returns it to the application programs of NGMS.
- the DriverWrap encapsulates and provides a uniform interface, thereby reducing association between the handset and the NGMS side;
- control flow of embodiments of the present invention is simple and therefore can enhance the time of system response.
- Fig. 7 is a flow chart of controlling an audio module of a handset with a smart card according to an embodiment of the present invention, in which an illustrative procedure of controlling audio module of the handset by using a smart card is described, as a whole, with playing music and adjusting volume as an example. Explanation of the control flow is as follows:
- the smart card calls the open() interface to open the audio device, e.g., "dev/dsp"; and the open() interface opens the actual peripheral devices on the handset side via the DriverWrap module;
- the smart card transmits the music data to be played to the audio device via the write() interface; and the write() interface transmits music data to an actual peripheral device on the handset side via the DriverWrap module;
- the smart card calls ioctl() interface to adjust volume; and the ioctl() interface controls volume of the actual peripheral device on the handset side via the DriverWrap module;
- the smart card calls the close() interface to close the device which is open; and the close() interface closes the actual peripheral device on the handset side via the DriverWrap module.
- Each step in this procedure may refer to the example of opening Audio device /dev/dsp shown in Fig. 6.
- Benefits of versatility and independence lie in that, if this method is used and a smart card needs to be supported by a certain handset, the handset only needs to implement DriverWrap as required, to realize the control over peripheral devices of the handset by using the smart card. But, if this method is not used, the handset side will refer to detail design of the smart card side to accommodate interaction between them. At the same time, after using the DriverWrap, the controlling effect can be achieved even if the operating system on the handset side is not identical to that on the smart card side. From this viewpoint, the present invention is favorable for spread and application of smart cards.
- peripheral devices are controlled by use of a smart card according to embodiments of the present invention, a simplified control flow can be obtained, and the system response time and the system performance can be improved.
Abstract
A handset, a smart card and a method for controlling peripheral devices of the handset with the smart card are provided. The smart card is pluggable in the handset. The smart card includes application programs for peripheral devices tored therein and a second communication module for communicating with the handset. The handset includes: the peripheral devices; a card interface, and a first communication module adapted to communicate with the smart card, and provide a uniform bottom layer drive interface for the peripheral devices, so that the second communication module maps the bottom layer drive interface provided by the first communication module to the smart card and provides the mapped bottom layer drive interface to the application programs in the smart card for use. When the application programs in the smart card call drive interfaces for the peripheral devices provided by the second communication module, the first communication module receives interface calls sent by the second communication module, and maps the received interface call to a drive interface of an actual peripheral device, so that the actual peripheral device performs an interface call operation.
Description
Handset, Smart Card and Method For Controlling Peripheral Devices of
Handset with Smart Card
Technical Field
The present invention relates to a mobile communication terminal, particularly to a handset, a smart card and a method for controlling peripheral devices of the handset with the smart card.
Background Art
A smart card, such as the Next Generation Mega-SIM (NGMS) card, is now widely used in handsets to control peripheral devices of handsets. It is characterized in that the handset side has independent CPU and external devices; the smart card side also has independent CPU; a portion of application programs resides in the smart card side and the handset side accesses the server at the smart card side in Web mode and carries out application programs; and some application programs running at the smart card side need to access and control external devices of the handset side. Fig. 1 shows a illustrative configuration diagram of a prior art handset and a smart card, in which the smart card is a UICC (universal integrated chip card) and is provided with a web server, application programs, Java virtual machines (JVM) and communication protocols; and the handset side is provided with application programs, browser kernel and communication protocols (OS/FS, 7816, USB) and uses a TPAK platform.
In current common smart card solutions, a general feature is that the smart card serves as a web server and some application programs are also provided in the smart card. During the system operates, the handset side accesses the server on the smart card in a Web mode and runs some corresponding application programs. This has the advantage of having some operations conducted by the CPU of the smart card, hence improving the performance of the overall system. However, in this case, in order to
provide some applications such as audio-related applications on the smart card, the relationship between the application programs and the bottom layer device drivers needs to be handled. In prior art method, generally, the bottom layer drivers of a handset are accessed via application programs on the handset side. Disadvantages of this mainly include the following two aspects. One disadvantage is that the complete control flow is long and the response time is long. The other is that corresponding application programs need to be further run on the handset side, which is adverse to the improvement of system performance. For example, Fig. 2 shows a control flow of controlling peripheral devices of a handset with a NGMS card. While application programs on the NGMS card are controlling peripheral devices of the handset, first, the application programs in the card determines control operations and transmits the operations to the corresponding application programs in the handset via TCP/IP. Next, the application programs in the handset analyze the received operations and then call the corresponding bottom layer drive interface to control peripheral devices to carry out corresponding operations. In Fig. 2, the curve across the handset and the smart card indicates the path of the control flow. It can be seen that in the control flow, application programs on the handset side are involved.
Fig. 3 depicts a prior art control flow of opening an audio device (Audio device/dev/dsp) of a handset with a smart card. The control flow includes:
(1) The NGMS application program determines that the current operation is an open operation with the target of "/dev/dsp"; (2) It transmits this operation to the corresponding application program in the handset via TCP/IP; (3) The handset application program analyzes the received operation and calls the corresponding bottom layer drive interface: open interface, that is, Open ("dev/dsp"); (4) The Audio driver carries out Open() operation and returns a result indicating if the operation is successful; (5) The handset application program transmits the received result to the NGMS application program; (6) The NGMS application program receives the result.
Till now, the Open operation is over and the process can continue.
This control flow has the following disadvantages. It is necessary to implement corresponding application programs on the handset side repeatedly and then these application programs can be used to call the bottom layer device drivers. For different peripheral devices, interfaces between their NGMSs and application programs on the handset side need to be defined. The smart card and the handset are associated with each other too closely, and once one of them changes, corresponding parts thereof need to be changed totally. The control flow is relatively long and the system response time is not perfect.
Summary of the Invention
In order to solve the above problems in prior art, the present invention provides a handset, a smart card and a method for directly controlling peripheral devices of the handset by use of the smart card. According to embodiments of the present invention, the control flow can be simplified, the system response time and the system performance can be improved.
The present invention provides a handset, in which a smart card is pluggable, the smart card comprising application programs for peripheral devices that are stored therein and a second communication module for communicating with the handset; the handset including: the peripheral devices; a card interface, adapted to interface with the smart card; and a first communication module, adapted to communicate with the second communication module of the smart card, and provide an uniform bottom layer drive interface for the peripheral devices, so that the second communication module maps the bottom layer drive interface provided by the first communication module to the smart card and provides the mapped bottom layer drive interface to the application
programs in the smart card for use; when the application programs in the smart card call drive interfaces for the peripheral devices that are provided by the second communication module, the first communication module receives interface calls sent by the second communication module, and maps the received interface call to a drive interface of an actual peripheral device, so that the actual peripheral device performs a interface call operation.
According to an embodiment of the present invention, the peripheral device returns the result of the interface call operation to the first communication module; the first communication module sends the result to the second communication module; so that the second communication module returns the result to the application programs in the smart card.
The handset may utilize Linux platform.
According to an embodiment of the present invention, the bottom layer drive interfaces provided by the first communication module include an open interface, a write interface, a read interface, an I/O control interface and a close interface for the peripheral devices.
According to an embodiment of the present invention, in the first communication module, the open interface, the write interface, the read interface, the VO control interface and the close interface call corresponding drive interfaces in accordance with types of the peripheral devices.
According to an embodiment of the present invention, in the case that the peripheral devices request for sending data to the application programs, the first communication module processes a corresponding interrupt request, buffers data from the peripheral devices, and sends the data to the smart card.
The present invention provides a smart card for a handset, the handset including peripheral devices, a card interface adapted to interface with the smart card, and a first communication module adapted to communicate with the smart card and provide an
uniform bottom layer drive interface for the peripheral devices; the smart card including: application programs relating for the peripheral devices stored therein: a second communication module, adapted to communicate with the handset, map the bottom layer drive interface provided by the first communication module to the smart card, and provide the mapped bottom layer drive interface to the application programs in the smart card for use; wherein, when the application programs in the smart card call drive interfaces for the peripheral devices that are provided by the second communication module, the second communication module sends interface calls to the first communication module, so that the first communication module maps the received interface call to a drive interface of an actual peripheral device and the actual peripheral device performs a interface call operation.
The present invention further provides a method for controlling peripheral devices of a handset by use of a smart card; the smart card is inserted in an card interface of the handset; a first communication module is provided between device drivers and upper layer application programs in the handset, is adapted to communicate with the smart card, and provides an uniform bottom layer drive interface for the peripheral devices; a second communication module is provided at a lower layer of application programs in the smart card, is adapted to communicate with the handset, maps the bottom layer drive interface provided by the first communication module to the smart card, and provides the mapped bottom layer drive interface to the upper layer application programs in the smart card for use; the method comprising: calling, by the upper layer application programs in the smart card, drive interfaces of the peripheral devices that are provided by the second communication module; sending, by the second communication module, interface calls to the first communication module; mapping, by the first communication module, the received
interface calls to a drive interface of an actual peripheral device; and performing, by the actual peripheral device, a interface call operation.
Brief Description of Drawings
Fig. 1 is an illustrative configuration diagram of a prior art handset and a smart card;
Fig. 2 shows a control flow of controlling peripheral devices of a handset with a NGMS card in prior art;
Fig. 3 is a control flow diagram of opening an audio device of a handset with a smart card in prior art;
Fig. 4 is a structure block diagram of a handset and a smart card according to an embodiment of the present invention;
Fig. 5 shows a control flow of controlling peripheral devices of a handset with a NGMS card according to an embodiment of the present invention;
Fig. 6 is a control flow diagram of opening an audio device of a handset with a smart card according to an embodiment of the present invention; and
Fig. 7 is a flow chart of controlling an audio module of a handset with a smart card according to an embodiment of the present invention.
Detail Description
Fig. 4 shows a structure block diagram of a handset and a smart card according to an embodiment of the present invention. The smart card may be inserted into a card interface in the handset. Peripheral devices of the handset include, for example, an audio module, a video module and a camera head.
Fig. 5 shows a control flow of controlling peripheral devices of a handset by use of a NGMS card according to an embodiment of the present invention. In this embodiment and the following other embodiments, as an example, the Linux platform
is utilized by the handset and the smart card. However, the present invention is not limited to handsets using Linux platform, and may also be applied to handsets using other platforms. As shown in Fig. 5, the handset on the left side is provided with application programs, a driving socket module, TCP/IP protocol, device drivers and peripheral devices. The smart card on the right side is provided with application programs, a driving socket module and TCP/IP protocol. In Fig. 5, the curve across the handset and the smart card indicates the path of the control flow. It can be seen that in the control flow, it is not needed to go through application programs on the handset side (i.e., Handset Apps).
As shown in Fig. 5, at the handset side, a driver socket module (also known as DriverWrap module or DriverWrap) is added between the device driver and upper layer application programs, and primarily performs functions of communicating as a communication module and providing a uniform calling interface for upper layers by calling bottom layer device drivers, serving as a socket. Primary functions of the driver socket module on the handset side are as follows:
(1) Providing uniform bottom layer drive interface.
Taking the Linux system as an example, Linux bottom layer device driver generally provides fundamental functions of open(), write(), read(), ioctl () and close() for opening, writing, reading, input output controlling and closing the peripheral devices respectively. Special functions of some special devices, such as mmap() (mapping a file to memory) and release() (releasing resources), may be implemented by ioctl(). Therefore, in Linux system, the uniform drive interface provided by the DriverWrap layer may be defined as open(), write(), read(), ioctl() and close().
(2) Implementation of interfaces.
In DriverWrap, an uniform interface of open(), write(), read(), ioctl() and close() calls corresponding drive interface and returns corresponding return values in accordance with specific device.
(3) Interrupt processing.
In case that a bottom layer device transmits data actively to a upper layer application program, the DriverWrap module needs to process corresponding interrupt request, buffer data from the device and then transmit it to the smart card side actively.
(4) Converting asynchronous operation to synchronous operation.
In the DriverWrap module, asynchronous operations are manually converted into synchronous operations, to reduce complexity of interaction with application programs on the smart card side.
(5) Communication with a DriverWrap module on the smart card side on the basis of TCP/IP.
At the smart card side, a DriverWrop module is also added under application programs, and achieves following primary functions:
(1) Mapping the uniform interface of the DriverWrap module on the handset side to the smart card side.
(2) Providing the mapped uniform interface to upper layer application programs of the smart card for use.
(3) Communication with the DriverWrap module on the handset side on the basis of TCP/IP.
The driver socket modules on the handset side and the smart card side, as communicating modules, may be implemented as hardware, software or combination thereof.
Fig. 6 is a control flow diagram of opening an audio device of a handset by use of a smart card according to an embodiment of the present invention, in which the control flow of the method of an embodiment of the present invention is illustrated with opening Audio device/dev/dsp as an example. Explanation of the control flow is as follows:
(1) The NGMS application program calls the interface provided by DriverWrap: Open("/dev/dsp");
(2) The DriverWrap on the NGMS side transmits the interface call Open("/dev/dsp") to the DriverWrap on the handset side;
(3) The DriverWrap on the handset side maps the received Open() to the Open() interface of the actual Audio driver;
(4) The Audio driver performs Open() operation and returns the performed result; and
(5) The DriverWrap on the handset side transmits the performed result to the NGMS side, and the DriverWrap on the NGMS side returns it to the application programs of NGMS.
This control flow has the following advantages:
(1) The DriverWrap encapsulates and provides a uniform interface, thereby reducing association between the handset and the NGMS side;
(2) The uniform interface of DriverWrap can enhance its versatility greatly. The NGMS application program will not concern implementation of bottom layer of the handset side, and only needs to satisfy the interface of the DriverWrap; and
(3) With respect to prior art implementations, the control flow of embodiments of the present invention is simple and therefore can enhance the time of system response.
Fig. 7 is a flow chart of controlling an audio module of a handset with a smart card according to an embodiment of the present invention, in which an illustrative procedure of controlling audio module of the handset by using a smart card is described, as a whole, with playing music and adjusting volume as an example. Explanation of the control flow is as follows:
(1) The smart card calls the open() interface to open the audio device, e.g., "dev/dsp"; and the open() interface opens the actual peripheral devices on the handset
side via the DriverWrap module;
(2) The smart card transmits the music data to be played to the audio device via the write() interface; and the write() interface transmits music data to an actual peripheral device on the handset side via the DriverWrap module;
(3) During playing, the smart card calls ioctl() interface to adjust volume; and the ioctl() interface controls volume of the actual peripheral device on the handset side via the DriverWrap module;
(4) After completing playing, the smart card calls the close() interface to close the device which is open; and the close() interface closes the actual peripheral device on the handset side via the DriverWrap module.
Each step in this procedure may refer to the example of opening Audio device /dev/dsp shown in Fig. 6.
By comparing the prior art with the above-mentioned embodiments of the present invention, it can be seen that the present invention has the following two major beneficial effects:
(1) Versatility and independence. this method is independent of platforms of the handset side and the smart card side; and the uniform calling interface makes the handset independent from the NGMS each other.
Benefits of versatility and independence lie in that, if this method is used and a smart card needs to be supported by a certain handset, the handset only needs to implement DriverWrap as required, to realize the control over peripheral devices of the handset by using the smart card. But, if this method is not used, the handset side will refer to detail design of the smart card side to accommodate interaction between them. At the same time, after using the DriverWrap, the controlling effect can be achieved even if the operating system on the handset side is not identical to that on the
smart card side. From this viewpoint, the present invention is favorable for spread and application of smart cards.
(2) Improvement of system performance.
The peripheral devices are controlled by use of a smart card according to embodiments of the present invention, a simplified control flow can be obtained, and the system response time and the system performance can be improved.
Claims
1. A handset, in which a smart card is pluggable, the smart card comprising application programs for peripheral devices that are stored therein and a second communication module for communicating with the handset; the handset comprising: the peripheral devices; a card interface, adapted to interface with the smart card; and a first communication module, adapted to communicate with the second communication module of the smart card, and provide an uniform bottom layer drive interface for the peripheral devices, so that the second communication module maps the bottom layer drive interface provided by the first communication module to the smart card and provides the mapped bottom layer drive interface to the application programs in the smart card for use; wherein, when the application programs in the smart card call drive interfaces for the peripheral devices that are provided by the second communication module, the first communication module receives interface calls sent by the second communication module, and maps the received interface call to a drive interface of an actual peripheral device, so that the actual peripheral device performs a interface call operation.
2. The handset according to claim 1, wherein, the actual peripheral device returns the result of the interface call operation to the first communication module; the first communication module sends the result to the second communication module; and the second communication module returns the result to the application programs in the smart card.
3. The handset according to claim 1, wherein, the handset utilizes Linux platform.
4. The handset according to claim 3, wherein, the bottom layer drive interfaces provided by the first communication module comprise an open interface, a write interface, a read interface, an I/O control interface and a close interface for the peripheral devices.
5. The handset according to claim 4, wherein, in the first communication module, the open interface, the write interface, the read interface, the I/O control interface and the close interface call corresponding drive interfaces in accordance with types of the peripheral devices.
6. The handset according to claim 1, wherein, in the case that the peripheral devices request for sending data to the application programs, the first communication module processes a corresponding interrupt request, buffers data from the peripheral devices, and sends the data to the smart card.
7. A smart card for a handset, wherein the handset comprises peripheral devices, a card interface adapted to interface with the smart card, and a first communication module adapted to communicate with the smart card and provide an uniform bottom layer drive interface for the peripheral devices; the smart card comprising: application programs for the peripheral devices that are stored therein; and a second communication module, adapted to communicate with the handset, map the bottom layer drive interface provided by the first communication module to the smart card, and provide the mapped bottom layer drive interface to the application programs in the smart card for use; wherein, when the application programs in the smart card call drive interfaces for the peripheral devices that are provided by the second communication module, the second communication module sends interface calls to the first communication module, so that the first communication module maps the received interface call to a drive interface of an actual peripheral device and the actual peripheral device performs a interface call operation.
8. A method for controlling peripheral devices of a handset by use of a smart card, wherein, the smart card is inserted in an card interface of the handset; a first communication module is provided between device drivers and upper layer application programs in the handset, is adapted to communicate with the smart card, and provides an uniform bottom layer drive interface for the peripheral devices; a second communication module is provided at a lower layer of application programs in the smart card, is adapted to communicate with the handset, maps the bottom layer drive interface provided by the first communication module to the smart card, and provides the mapped bottom layer drive interface to the upper layer application programs in the smart card for use; the method comprising: calling, by the upper layer application programs in the smart card, drive interfaces of the peripheral devices that are provided by the second communication module; sending, by the second communication module, interface calls to the first communication module; mapping, by the first communication module, the received interface calls to a drive interface of an actual peripheral device; and performing, by the actual peripheral device, a interface call operation.
9. The method according to claim 8, further comprising: returning, by the actual peripheral device, the result of the interface call operation to the first communication module; sending, by the first communication module, the result to the second communication module; and returning, by the second communication module, the result to the application programs in the smart card.
10. The method according to claim 8, wherein, the handset utilizes Linux platform.
11. The method according to claim 10, wherein, the bottom layer drive interfaces provided by the first communication module comprise an open interface, a write interface, a read interface, an I/O control interface and a close interface for the peripheral devices.
12. The method according to claim 11, wherein, in the first communication module, the open interface, the write interface, the read interface, the VO control interface and the close interface call corresponding drive interfaces in accordance with types of the peripheral devices.
13. The method according to claim 8, wherein, in the case that the peripheral devices request for sending data to the application programs, the first communication module processes a corresponding interrupt request, buffers data from the peripheral devices, and sends the data to the smart card.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200810178334 CN101754443B (en) | 2008-11-28 | 2008-11-28 | Mobile phone, intelligent card and method for using the intelligent card to control the peripheral equipment of the mobile phone |
| CN200810178334.2 | 2008-11-28 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2010060344A1 true WO2010060344A1 (en) | 2010-06-03 |
Family
ID=42225250
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2009/074809 WO2010060344A1 (en) | 2008-11-28 | 2009-11-05 | Handset, smart card and method for controlling peripheral devices of handset with smart card |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101754443B (en) |
| WO (1) | WO2010060344A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104392261B (en) * | 2014-10-17 | 2018-02-27 | 上海新储集成电路有限公司 | A kind of SIM card and the mobile terminal with the SIM card |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1277701A (en) * | 1998-08-13 | 2000-12-20 | 布尔Cp8公司 | Method for communication between a user station and a network, in particular such as internet, and implementing architecture |
| US20060080381A1 (en) * | 2004-04-15 | 2006-04-13 | Rasmus Villefrance | Data transfer |
| CN1773528A (en) * | 2004-11-12 | 2006-05-17 | 厦门盛华电子科技有限公司 | Mobile telephone smart card with radio-frequency communication function and peripheral processing device |
| CN1992737A (en) * | 2005-12-27 | 2007-07-04 | 中兴通讯股份有限公司 | Communication method of mobile telephone |
| US20080011828A1 (en) * | 2006-07-14 | 2008-01-17 | Microsoft Corporation | Smart card terminal side data and management framework |
| CN101203030A (en) * | 2006-12-13 | 2008-06-18 | 联想(北京)有限公司 | Apparatus and method for identifying authority by mobile terminal multi-mode protocol stack |
-
2008
- 2008-11-28 CN CN 200810178334 patent/CN101754443B/en not_active Expired - Fee Related
-
2009
- 2009-11-05 WO PCT/CN2009/074809 patent/WO2010060344A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1277701A (en) * | 1998-08-13 | 2000-12-20 | 布尔Cp8公司 | Method for communication between a user station and a network, in particular such as internet, and implementing architecture |
| US20060080381A1 (en) * | 2004-04-15 | 2006-04-13 | Rasmus Villefrance | Data transfer |
| CN1773528A (en) * | 2004-11-12 | 2006-05-17 | 厦门盛华电子科技有限公司 | Mobile telephone smart card with radio-frequency communication function and peripheral processing device |
| CN1992737A (en) * | 2005-12-27 | 2007-07-04 | 中兴通讯股份有限公司 | Communication method of mobile telephone |
| US20080011828A1 (en) * | 2006-07-14 | 2008-01-17 | Microsoft Corporation | Smart card terminal side data and management framework |
| CN101203030A (en) * | 2006-12-13 | 2008-06-18 | 联想(北京)有限公司 | Apparatus and method for identifying authority by mobile terminal multi-mode protocol stack |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101754443A (en) | 2010-06-23 |
| CN101754443B (en) | 2012-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8738815B2 (en) | System and method for virtualizing the peripherals in a terminal device to enable remote management via removable portable media with processing capability | |
| US11151010B2 (en) | Resource configuration method, mobile terminal and storage medium | |
| US9781211B2 (en) | Storage device having master and slave storage device modes | |
| WO2023284699A1 (en) | Protocol stack data transmission method based on linux system, and computer device and storage medium | |
| US7941812B2 (en) | Input/output virtualization through offload techniques | |
| US9635549B2 (en) | Providing subscriber identity module function | |
| US9137249B2 (en) | Local proxy system and method | |
| WO2020119316A1 (en) | Terminal system architecture, communication system and communication method, and storage medium | |
| US11182210B2 (en) | Method for resource allocation and terminal device | |
| WO2022257654A1 (en) | Data network sharing method and apparatus, electronic device, and storage medium | |
| WO2010060344A1 (en) | Handset, smart card and method for controlling peripheral devices of handset with smart card | |
| WO2012129930A1 (en) | Multi-standard drive method and system, and terminal | |
| Li et al. | LyraNET: a zero-copy TCP/IP protocol stack for embedded operating systems | |
| WO2023240941A1 (en) | Method and apparatus for downloading data, and secure element | |
| US7930445B2 (en) | Computer system using remote I/O and I/O data transfer method | |
| KR101863677B1 (en) | System and method for interfacing between terminal and smart card | |
| WO2010086731A1 (en) | System and method for virtualizing the peripherals in a terminal device to enable remote management via removable portable media with processing capability | |
| KR100806037B1 (en) | Method and apparatus for executing program of mobile communication terminal by uicc | |
| CN109408429B (en) | Caching method and device for low-speed interface | |
| JP5848741B2 (en) | Communication method between host and wireless internet access module, and host communication module | |
| CN114866534B (en) | Image processing method, device, equipment and medium | |
| CN117851296A (en) | Method and device for invoking and controlling camera by browser | |
| WO2019049542A1 (en) | Information processing device and information processing method | |
| KR100863608B1 (en) | combo card including Bridge for memory card | |
| CN115344348A (en) | Intelligent network card virtual machine migration method based on libvirt and qemu |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09828604 Country of ref document: EP Kind code of ref document: A1 |
|
| DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 09828604 Country of ref document: EP Kind code of ref document: A1 |