CN106778193B - Client and UI interaction method - Google Patents
Client and UI interaction method Download PDFInfo
- Publication number
- CN106778193B CN106778193B CN201610998983.1A CN201610998983A CN106778193B CN 106778193 B CN106778193 B CN 106778193B CN 201610998983 A CN201610998983 A CN 201610998983A CN 106778193 B CN106778193 B CN 106778193B
- Authority
- CN
- China
- Prior art keywords
- usbkey
- middleware
- component
- primitive
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
Abstract
The invention discloses a client and a UI interaction method, and belongs to the technical field of UI interaction. The client side is internally provided with a USBKey middleware, the USBKey middleware comprises a UI component and a non-UI component, and the UI component refers to all parts of the USBKey middleware related to a UI interaction function; the UI component comprises a plurality of UI modules realized aiming at different UI framework operating environments; and the USBKey middleware starts a corresponding UI module according to the UI frame operating environment of the client side where the USBKey middleware is positioned, and the non-UI component and the UI component are communicated in a process communication mode through a UI communication interface. According to the client and the UI interaction method, the UI module in the USBKey middleware with the UI interaction function is stripped, and the UI components suitable for different UI frame operation environments are arranged, so that the USBKey middleware can be suitable for different UI frame operation environments, and the difficult problem of deployment of the USBKey middleware caused by different UI frames is solved.
Description
Technical Field
The invention relates to the technical field of USBKey, in particular to a client and UI interaction method.
Background
The USBKey is hardware equipment taking a USB as an interface standard, is internally provided with a single chip microcomputer or an intelligent card chip, has a cryptographic operation function, has a private storage space with certain capacity, can store a private key and a digital certificate of a user, realizes the authentication of the identity of the user by utilizing a public key algorithm which is internally arranged in the USBKey, and ensures the security of the user authentication because the private key of the user is stored in a coded lock and cannot be read by using any mode theoretically.
With the development of internet and electronic commerce, the USBKey is being recognized and used by more and more users as an "electronic key" for network user identification and data protection. In the process of UI data interaction by connecting the USBKey and an upper computer (client), a USBKey middleware needs to be installed in the upper computer, an upper layer security application (application layer) in the upper computer calls the USBKey middleware, and the USBKey middleware carries out APDU instruction interaction with a USBKey main chip through USB drive. However, in practical applications, there are generally multiple release branches for a certain os, for example, there are multiple release branches such as Ubuntu, fedora, and Debian for a Linux os, and desktop environments, window managers, and graphic application frameworks (hereinafter, abbreviated as UI frameworks) installed in different Linux releases are all different. Even though the same Linux distribution is adopted, the system environment configurations used by the end users of the USBKey products generally differ from one another. In the development stage of the UI application program, different UI frameworks mean different UI design concepts, different UI calling interface conventions, different data structure definitions and different compiling dependent environments. Therefore, to implement the deployment of the USBKey middleware for different system UI frameworks, multiple software products need to be developed respectively. On the premise of not changing the environment configuration of a user system, how to operate USBKey middleware containing a UI interaction function in more systems with different versions is a difficult problem.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a client and a UI interaction method, which can realize the normal operation of the USBKey middleware with the UI interaction function under various different UI framework operation environments.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
a client is provided with a USBKey middleware, wherein the USBKey middleware comprises a UI component and a non-UI component, and the UI component refers to all parts related to UI interaction functions in the USBKey middleware; the UI component comprises a plurality of UI modules realized aiming at different UI framework operating environments; the USBKey middleware starts a corresponding UI module according to the UI frame operating environment of the client side where the USBKey middleware is located; the USBKey middleware further comprises:
UI communication interface UI _ API: the method is used for communication between the non-UI component and the UI component in a process communication mode.
Further, the usb key middleware as described above further includes: the UI interface library is used for packaging and storing UI calling primitives; the UI calling primitive is a primitive which is determined according to a UI interaction scene related to the USBKey middleware, agreed between a non-UI component and a UI component and is irrelevant to an operating system platform; and the non-UI component and the UI component adopt the UI calling primitive for communication.
Further, in the client described above, the UI framework operating environment includes a Java operating environment, a Qt operating environment and a GTK operating environment under the Linux operating system.
Further, the usb key middleware as described above further includes:
the UI component management interface is used for managing the UI component of the USBKey middleware; the management includes addition, modification, or deletion of UI modules.
The embodiment of the invention also provides a UI interaction method based on the client, which comprises the following steps:
the USBKey middleware determines and starts a UI module corresponding to the UI frame operation environment according to the UI frame operation environment of the client side where the USBKey middleware operates;
and the non-UI component of the USBKey middleware sends UI request information to the enabled UI module in an interprocess communication mode, and the UI module calls a UI interface of the client to finish corresponding UI interaction actions according to the received UI request information.
Further, according to the UI interaction method, the non-UI component sends UI request information to the UI module by using a UI call primitive; the calling primitive is a primitive which is determined according to a UI interaction scene related to the USBKey middleware, agreed between a non-UI component and a UI component and is irrelevant to an operating system platform.
Further, according to the UI interaction method, the UI interaction scene comprises user password acquisition and verification, prompting of user key pressing, and providing of a user selection list for user selection.
Further, a UI interaction method as described above, the UI invoking primitive includes a UI session start primitive begin session, a UI session end primitive EndSession, a password input dialog box display primitive PIN _ Show, a user password acquisition primitive PIN _ GetPIN, a password error prompt and re-input primitive PIN _ Retry, a password input box closing primitive PIN _ Finish, a Waiting dialog box display primitive Waiting _ Show, a Waiting dialog box closing primitive Waiting _ Finish, a List selection box display primitive List _ Show, and a user selection acquisition and dialog box closing primitive List _ GetSel.
Further, according to the UI interaction method described above, the usb key middleware determines and runs the UI module corresponding to the UI frame running environment according to the UI frame running environment of the client, and includes:
and the non-UI component sequentially sends UI session starting primitives to the plurality of UI modules, and determines the UI modules receiving the response data within the set time as the UI modules corresponding to the running environment of the UI framework.
Further, in the UI interaction method as described above, the USBkey middleware determines and runs the UI component corresponding to the UI framework running environment according to the UI framework running environment of the client, and includes:
the USBKey middleware sends request information for acquiring the UI frame running environment to the client;
and the USBKey middleware determines and operates the UI module corresponding to the UI frame operation environment according to the UI frame operation environment information returned by the client.
The invention has the beneficial effects that: according to the client and the UI interaction method provided by the invention, the UI module in the USBKey middleware with the UI interaction function is stripped, and the UI components suitable for different UI frame operation environments are arranged, so that the USBKey middleware can be suitable for different UI frame operation environments, and the difficult problem of deployment of the USBKey middleware caused by different UI frames is solved.
Drawings
Fig. 1 is a schematic structural diagram of a client according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a non-UI component communicating with a UI component in accordance with certain implementations of the invention;
FIG. 3 is a flowchart illustrating a UI interaction method according to an embodiment of the invention;
fig. 4 is a diagram illustrating state machine transition between UI call primitives according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and the detailed description.
Fig. 1 shows a schematic structural diagram of a client in the specific embodiment of the present invention, and as can be seen from the diagram, a usb key middleware is installed in the client, where the usb key middleware includes a UI component 10 and a non-UI component 20, and the UI component 10 refers to all parts related to UI interaction functions in the usb key middleware; the UI component 10 comprises a plurality of UI modules 11 realized aiming at different UI framework running environments; the USBKey middleware starts a corresponding UI module according to the UI frame operating environment of the client side where the USBKey middleware is located; in order to realize data interaction between the UI component 10 and the non-UI, the USBKey middleware further comprises a UI communication interface UI _ API30, and the non-UI component 20 and the UI component 10 communicate in a process communication mode through the communication interface.
In this embodiment, the client is a device that can be communicatively connected to the USBkey, and can be connected to the USBkey signature verification server via a network or the like to perform data interaction, and the device includes, but is not limited to, a PC and the like. The USBKey middleware is provided by a USBKey equipment provider, is originally stored in the USBKey, and is installed in the client when the USBKey is connected with the client for the first time, and is software for operating the USBKey. The USBKey middleware realizes a group of public interfaces and provides cryptographic functional services depending on the USBKey, such as encryption and decryption, signature verification, management of keys and containers, management of certificates and the like. The USBKey middleware carries out APDU instruction interaction with the USBKey main chip through the USB drive, and the upper layer security application can realize the cryptography application only by calling an interface provided by the middleware.
In the client provided in the embodiment, all UI components 10 related to UI (User Interface) interaction functions in the installed USBkey middleware are separated, and a plurality of UI modules 11 suitable for different UI frame operating environments are respectively set for different UI frame operating environments, so that the USBkey middleware can operate in more UI frame operating environments, and even if the UI frame operating environment of the client of a User changes, the corresponding UI module can be selected to realize normal UI interaction without separately developing different USBkey middleware products for different UI frame operating environments.
In addition, by separating the UI component 10 from the non-UI component 20, if the USBkey middleware is required to support a new UI framework operating environment (when the USBkey middleware does not have a corresponding UI module) or modify a part of the middleware related to the UI interaction function, only a new UI module needs to be developed or the UI module needs to be modified, and the non-UI component of the USBkey middleware does not need to be modified, so that the workload is greatly reduced, and the updating efficiency is improved.
In this embodiment, the UI framework operating environment includes, but is not limited to, a Java operating environment, a Qt operating environment, a GTK operating environment, and the like in the Linux operating system, and correspondingly, the UI component includes UI modules implemented based on Java, qt, and GTK, that is, three corresponding UI modules for implementing the UI interaction function are respectively written corresponding to the three UI frameworks.
In the present embodiment, except for the UI component 10, other parts (including the non-UI part and the UI communication interface UI _ API) in the USB middleware operate in a process started by the upper layer security application software, and the UI component is a UI application developed based on a different UI framework and has an independent process, so that data interaction between the non-UI component of the USB middleware and the UI module 11 of the UI component 10 can be performed in an inter-process communication manner. In this embodiment, the USBkey middleware further includes a UI component communication interface UI _ API, as shown in fig. 2, an application process in which a non-UI component of the USBkey middleware is located communicates with a UI application process (UI process) in which a UI module is located through a UI _ API interface, and in the figure, UI _ Server and UI _ Resource respectively represent a UI Server corresponding to the UI process and a Resource required by the Server.
In this embodiment, in order to improve the data transmission efficiency between the non-UI component 20 and the UI module 11, the USBkey middleware further includes a UI interface library, and the UI interface library is used to encapsulate and store UI call primitives, where the UI call primitives are primitives that are determined according to the UI interaction scenario related to the USBkey middleware, agreed between the non-UI component and the UI component, and are unrelated to the operating system platform.
The non-UI component 20 and the UI component 10 call UI calling primitives in a UI interface library through the UI communication interface UI _ API30 to realize data interaction, so that the non-UI component of the USBKey middleware realizes UI interaction operation through the platform-independent UI calling primitives and the UI module of the UI component through interprocess communication, and the USBKey middleware can run under operating systems of various different UI frameworks.
To implement the management of the UI module 11 in the UI component 10, in an embodiment of the present invention, the USBkey middleware further includes a UI component management interface 40. The UI component unit management interface 40 is used for managing the UI component of the USBKey middleware; the management comprises adding, modifying or deleting the UI module and the like.
Based on the client shown in fig. 1, the present embodiment further provides a UI interaction method, as shown in fig. 3, the method mainly includes the following steps:
step S1: the USBKey middleware determines and operates a UI module corresponding to the UI frame operation environment according to the UI frame operation environment of the client where the USBKey middleware operates;
step S2: and the non-UI component of the USBKey middleware sends UI request information to the enabled UI module in an inter-process communication mode, and the UI module calls a UI interface of the client to complete corresponding UI interaction actions according to the received UI request information.
In this embodiment, the non-UI component sends UI request information to the UI module by using a corresponding UI call primitive, where the UI call primitive is a UI call primitive that is determined according to a UI interaction scenario related to the USBkey middleware, agreed between the non-UI component and the UI component of the USBey middleware, and is unrelated to the operating system platform. The UI interaction scene refers to an application scene related to user interface display when the USBKey middleware processes the USBKey service flow, and comprises user password acquisition and verification, user key prompting, user selection list providing for user selection and the like.
The UI calling primitive only describes an abstract UI display or interaction behavior and is irrelevant to a UI function provided by a system UI framework of a client side, a non-UI component of the USBKey middleware and the UI component are agreed mutually, the UI calling primitive is packaged in a UI interface library in the USBKey middleware, and an upper layer security application process where the non-UI component is located completes the sending of UI request information to a process where a certain UI module of the UI component is located through calling the UI calling primitive with the corresponding meaning in the UI interface library according to needs. In this embodiment, the UI call primitive and the functions of the primitives are shown in the following table.
| UI Call primitive | Function(s) |
| BeginSession | Starting a UI session |
| EndSession | Ending a UI session |
| PIN_Show | Display password entry dialog |
| PIN_GetPIN | Obtaining a password entered by a user |
| PIN_Retry | Prompting the user of password error and re-entering |
| PIN_Finish | Close password entry dialog |
| Waiting_Show | Displaying a waiting dialog |
| Waiting_Finish | Closing a waiting dialog |
| List_Show | Display list selection box |
| List_GetSel | Obtaining user selection item and closing dialog box |
As can be seen from the above table, the call primitives include, but are not limited to, a UI session start primitive BeginSession, a UI session end primitive EndSession, a password input dialog box display primitive PIN _ Show, a user password acquisition primitive PIN _ GetPIN, a password error prompt and re-input primitive PIN _ Retry, a password input box close primitive PIN _ Finish, a wait dialog box display primitive wait _ Show, a wait dialog box close primitive wait _ Finish, a List selection box display primitive List _ Show, and a user selection acquisition and dialog box close primitive List _ GetSel. Of course, other call primitives may be employed as desired. In this embodiment, the state machine transition between the call primitives is as shown in fig. 4.
In an embodiment of the present invention, a manner for the USBkey middleware to determine and operate the UI module corresponding to the UI frame operation environment according to the UI frame operation environment of the client is as follows:
and the non-UI component of the USBKey middleware sequentially sends UI session starting primitives to a plurality of UI modules of the UI component, and determines the UI module which receives response data within set time as the UI module corresponding to the running environment of the UI framework.
When a non-UI component of the USBKey middleware calls a BeginSession primitive in a UI interface library (a UI session starting primitive is sent to a UI module of the UI component in an interprocess communication mode), the primitive is sequentially sent to each UI module respectively, connection between the UI module and the UI module is tried to be established, if response data is received within set time after the primitive is sent to a certain UI module, the UI module with the response is determined to be matched with the running environment of the UI framework where the USBKey middleware runs, and the UI module is started to complete the subsequent UI interaction process.
In practical application, the USBKey tries to connect the operated UI module (the current UI module operated last time) first, if the connection is not responded, the USBKey sequentially sends a UI conversation starting primitive to other UI modules until the connection request is responded by a certain UI module, and if all the UI modules do not respond, the USBKey prompts that the start of the UI module fails.
In another embodiment of the present invention, the mode of determining and operating the UI module corresponding to the UI frame operating environment according to the UI frame operating environment of the client by the USBkey middleware is as follows:
the USBKey middleware sends request information for acquiring the UI frame operation environment to the client;
and the USBKey middleware determines and operates the UI module corresponding to the UI frame operation environment according to the UI frame operation environment information returned by the client.
According to the client and the UI interaction method provided by the embodiment, the USBKey middleware initiates UI interaction with the UI component through the UI calling primitive which is irrelevant to the platform, the USBKey middleware realizes the mutual operation with heterogeneous UI components through interprocess communication, the universality of the USBKey middleware in various UI frame operation environments is improved, the workload of the USBKey middleware during updating is reduced, and the updating efficiency is improved. The heterogeneous structure means that software modules developed based on different programming languages and different architectures can be arranged between the UI component and the non-UI component of the USBKey.
The invention is further described below in connection with an actual UI interaction scenario.
In this embodiment, a PC is taken as an example for the client, and a UI interaction scenario is a user password acquisition and verification scenario in online payment, and the process is as follows:
the USBKey is connected with the PC by a connection mode including but not limited to USB connection or Bluetooth connection and the like. The method comprises the steps that an online payment application (upper layer security application) on a PC calls a USBKey middleware, a non-UI component of the USBKey middleware sequentially sends UI session starting primitives to UI modules of the UI component in an interprocess communication mode, the UI module returning response data is determined to be a UI module corresponding to the running environment of a UI frame of a client, the UI module is started, data of a password input dialog box display primitive is sent to the UI module in the interprocess communication mode, the UI module calls a graphical interface of the UI frame of a PC operating system after receiving the data sent by the non-UI component, a password input box pops up on a user interface of the PC, after a user inputs a password, the UI module extracts password content and sends the content to the non-UI component in the interprocess communication mode, the non-UI component completes password verification of the USBKey, if the password is correct, the USBKey returns password verification passing information to the middleware, the non-UI module sends the password input box closing primitive to the UI module, completes closing of the input box, password obtaining and verification are completed, if the password is correct, the USBKey returns password verification passing information to the UI module, the password input box, the password input primitive again, the non-UI module prompts the user to input the UI module to input the primitive again, and the user.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is intended to include such modifications and variations.
Claims (10)
1. A client, characterized by: the client side is internally provided with a USBKey middleware, the USBKey middleware comprises a UI component and a non-UI component, and the UI component refers to all parts related to UI interaction functions in the USBKey middleware; the UI component comprises a plurality of UI modules realized aiming at different UI framework operating environments; the USBKey middleware starts a corresponding UI module according to the UI frame operating environment of the client side where the USBKey middleware is located; the USBKey middleware further comprises:
UI communication interface UI _ API: the method is used for communication between the non-UI component and the UI component in a process communication mode.
2. The client according to claim 1, wherein: the USBKey middleware further comprises: the UI interface library is used for packaging and storing UI calling primitives; the UI calling primitive is a primitive which is determined according to a UI interaction scene related to the USBKey middleware, agreed between a non-UI component and a UI component and is irrelevant to an operating system platform; and the non-UI component and the UI component adopt the UI calling primitive for communication.
3. The client according to claim 1, wherein: the UI framework operating environment comprises a Java operating environment, a Qt operating environment and a GTK operating environment under a Linux operating system.
4. A client according to any one of claims 1 to 3, wherein: the USBKey middleware further comprises:
the UI component management interface is used for managing the UI component of the USBKey middleware; the management includes addition, modification, or deletion of UI modules.
5. A UI interaction method based on any of claims 1 to 4, comprising the following steps:
the USBKey middleware determines and starts a UI module corresponding to the UI frame operation environment according to the UI frame operation environment of the client side where the USBKey middleware operates;
and the non-UI component of the USBKey middleware sends UI request information to the enabled UI module in an interprocess communication mode, and the UI module calls a UI interface of the client to finish corresponding UI interaction actions according to the received UI request information.
6. A UI interaction method according to claim 5, characterized in that: the non-UI component sends UI request information to the UI module by adopting a UI calling primitive; the calling primitive is a primitive which is determined according to a UI interaction scene related to the USBKey middleware, agreed between a non-UI component and a UI component and is irrelevant to an operating system platform.
7. A UI interaction method according to claim 5 or 6, characterized in that: the UI interaction scene comprises user password acquisition and verification, prompting of user key pressing and provision of a user selection list for user selection.
8. A UI interaction method according to claim 7, characterized in that: the UI call primitives include a UI session start primitive BeginSession, a UI session end primitive EndSession, a password input dialog box display primitive PIN _ Show, a user password acquisition primitive PIN _ GetPIN, a password error prompt and re-input primitive PIN _ Retry, a password input box close primitive PIN _ Finish, a Waiting dialog box display primitive Waitng _ Show, a Waiting dialog box close primitive Waitng _ Finish, a List selection box display primitive List _ Show, and a user selection acquisition and dialog box close primitive List _ GetSel.
9. A UI interaction method according to claim 8, characterized in that: the USBKey middleware determines and operates a UI module corresponding to the UI frame operation environment according to the UI frame operation environment of the client, and comprises the following steps:
and the non-UI component sequentially sends UI session starting primitives to the plurality of UI modules, and determines the UI module which receives the response data within the set time as the UI module corresponding to the UI framework operating environment.
10. A UI interaction method according to claim 8, characterized in that: the USBKey middleware determines and operates a UI component corresponding to the UI framework operation environment according to the UI framework operation environment of the client, and comprises the following steps:
the USBKey middleware sends request information for acquiring the UI frame operation environment to the client;
and the USBKey middleware determines and operates the UI module corresponding to the UI frame operation environment according to the UI frame operation environment information returned by the client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610998983.1A CN106778193B (en) | 2016-11-14 | 2016-11-14 | Client and UI interaction method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610998983.1A CN106778193B (en) | 2016-11-14 | 2016-11-14 | Client and UI interaction method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106778193A CN106778193A (en) | 2017-05-31 |
| CN106778193B true CN106778193B (en) | 2023-02-03 |
Family
ID=58973530
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610998983.1A Active CN106778193B (en) | 2016-11-14 | 2016-11-14 | Client and UI interaction method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106778193B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109992267A (en) * | 2019-03-12 | 2019-07-09 | 厦门网宿有限公司 | A kind of client of cloud application |
| CN113434228A (en) * | 2021-06-21 | 2021-09-24 | 青岛海尔科技有限公司 | Page request method and device, storage medium and electronic device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1569096A1 (en) * | 2004-02-27 | 2005-08-31 | Research In Motion Limited | System and method for executing wireless applications using common UI components from a UI repository |
| CN101122940A (en) * | 2007-09-30 | 2008-02-13 | 金蝶软件（中国）有限公司 | USBKEY integration method and device |
| CN101751718A (en) * | 2008-11-28 | 2010-06-23 | 爱思开电讯投资（中国）有限公司 | Intelligent card providing two operating system environments |
| CN102866925A (en) * | 2012-09-06 | 2013-01-09 | 深圳市九洲电器有限公司 | Communication method and system for middleware and user interface |
| WO2013010665A1 (en) * | 2011-07-19 | 2013-01-24 | Giesecke & Devrient Gmbh | Method for securing a transaction |
| CN103778389A (en) * | 2012-10-18 | 2014-05-07 | 美国博通公司 | Integration of untrusted framework component with secure operating system environment |
| CN104102859A (en) * | 2014-07-09 | 2014-10-15 | 深圳市茁壮网络股份有限公司 | JavaScript-based middleware authorization method and device |
| CN104102876A (en) * | 2014-07-17 | 2014-10-15 | 北京握奇智能科技有限公司 | Device for safeguarding operational security of client side |
| CN104809413A (en) * | 2015-05-13 | 2015-07-29 | 上海瓶钵信息科技有限公司 | Trusted user interface framework of mobile platform based on TrustZone |
| CN105900105A (en) * | 2014-02-06 | 2016-08-24 | 英特尔公司 | Media protection policy enforcement for multiple-operating-system environments |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8220002B2 (en) * | 2008-01-25 | 2012-07-10 | Microsoft Corporation | Isolation of user-interactive components |
| US20150268706A1 (en) * | 2014-03-24 | 2015-09-24 | Qualcomm Incorporated | System and method for memory power management in a system on a chip with multiple execution environments |
-
2016
- 2016-11-14 CN CN201610998983.1A patent/CN106778193B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1569096A1 (en) * | 2004-02-27 | 2005-08-31 | Research In Motion Limited | System and method for executing wireless applications using common UI components from a UI repository |
| CN101122940A (en) * | 2007-09-30 | 2008-02-13 | 金蝶软件（中国）有限公司 | USBKEY integration method and device |
| CN101751718A (en) * | 2008-11-28 | 2010-06-23 | 爱思开电讯投资（中国）有限公司 | Intelligent card providing two operating system environments |
| WO2013010665A1 (en) * | 2011-07-19 | 2013-01-24 | Giesecke & Devrient Gmbh | Method for securing a transaction |
| CN102866925A (en) * | 2012-09-06 | 2013-01-09 | 深圳市九洲电器有限公司 | Communication method and system for middleware and user interface |
| CN103778389A (en) * | 2012-10-18 | 2014-05-07 | 美国博通公司 | Integration of untrusted framework component with secure operating system environment |
| CN105900105A (en) * | 2014-02-06 | 2016-08-24 | 英特尔公司 | Media protection policy enforcement for multiple-operating-system environments |
| CN104102859A (en) * | 2014-07-09 | 2014-10-15 | 深圳市茁壮网络股份有限公司 | JavaScript-based middleware authorization method and device |
| CN104102876A (en) * | 2014-07-17 | 2014-10-15 | 北京握奇智能科技有限公司 | Device for safeguarding operational security of client side |
| CN104809413A (en) * | 2015-05-13 | 2015-07-29 | 上海瓶钵信息科技有限公司 | Trusted user interface framework of mobile platform based on TrustZone |
Non-Patent Citations (1)
| Title |
|---|
| 基于ATL的智能卡中间件的实现;何林等;《微计算机信息》;20050315(第03期);185-186,487 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106778193A (en) | 2017-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5534520B2 (en) | System and method for browser-based access to smart cards | |
| US10096025B2 (en) | Expert engine tier for adapting transaction-specific user requirements and transaction record handling | |
| US20160125386A1 (en) | Multi-tiered secure mobile transactions enabling platform | |
| US20140089185A1 (en) | Isolating distinct service provider widgets within a wallet container | |
| TW202044019A (en) | Access method based on H5 access mode, access component thereof and mobile terminal | |
| CN108681662A (en) | A kind of method and device of installation procedure | |
| EP3436935A1 (en) | Pre-formed instructions for a mobile cloud service | |
| CN109995523B (en) | Activation code management method and device and activation code generation method and device | |
| US20170286652A1 (en) | Security model for network information service | |
| CN110362318A (en) | Using dispositions method, device, equipment and storage medium | |
| CN112562217A (en) | Flow engine design, communication mode and working method of self-service terminal control system | |
| CN106778193B (en) | Client and UI interaction method | |
| CN111242462A (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN112448909A (en) | Electronic lock management method, device, system and storage medium | |
| US11803463B2 (en) | Systems and methods for software integration validation | |
| CN115344401A (en) | XFS realizing method, device, equipment and readable storage medium based on Hongmon system | |
| CN108737402A (en) | Mobile terminal safety means of defence and device | |
| CN114579334A (en) | Communication method, communication device, electronic equipment and storage medium | |
| CN114398082B (en) | Compatible operation method and device for frame type block chain application | |
| CN113360172B (en) | Application deployment method, device, computer equipment and storage medium | |
| CN108446219A (en) | Operating method, system, medium and the computing device of application program | |
| CN113253995B (en) | Method, device, equipment and storage medium for developing block chain system | |
| WO2024066749A1 (en) | Blockchain transaction execution method and apparatus, program product, device, and medium | |
| US20240104223A1 (en) | Portable verification context | |
| CN108388788B (en) | A kind of method and device for calling USB KEY bottom library |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |