CN106778193A - A kind of client and UI exchange methods - Google Patents
A kind of client and UI exchange methods Download PDFInfo
- Publication number
- CN106778193A CN106778193A CN201610998983.1A CN201610998983A CN106778193A CN 106778193 A CN106778193 A CN 106778193A CN 201610998983 A CN201610998983 A CN 201610998983A CN 106778193 A CN106778193 A CN 106778193A
- Authority
- CN
- China
- Prior art keywords
- usbkey
- middlewares
- components
- 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.)
- Granted
Links
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of client and UI exchange methods, belong to UI interaction techniques field.USBkey middlewares are installed, the USBkey middlewares include UI components and non-UI components, and the UI components refer to all parts for being related to UI interactive functions in USBkey middlewares in the client；The UI components include several UI modules realized for different UI frameworks running environment；USBkey middlewares UI framework running environment of client according to where it enables corresponding UI modules, is communicated using process communication mode by UI communication interfaces between non-UI components and UI components.Client provided by the present invention and UI exchange methods, it is stripped out by by the UI modules in the USBkey middlewares with UI interactive functions, and it is provided with the UI components suitable for different UI frameworks running environment, USBkey middlewares is applied under different UI framework running environment, solve because of the deployment problem of the USBkey middlewares that UI frameworks different band is come.
Description
Technical field
The present invention relates to USBkey technical fields, and in particular to a kind of client and UI exchange methods.
Background technology
USBKey is a kind of hardware device with USB as interface standard, its built-in single-chip microcomputer or intelligent card chip, possesses close
Code calculation function, there is the secret memory space of certain capacity, the private key and digital certificate of user can be stored, using USBKey
Built-in public key algorithm realizes the certification to user identity, because private key for user is stored in coded lock, in theory using any
Mode cannot all read, therefore ensure that the security of user authentication.
With internet and the development of ecommerce, USBKey is used as network user identity identification and the " electricity of data protection
Sub- key ", is recognized and is used by increasing user.USBkey is connected with host computer (client) and carries out UI data
, it is necessary to install USBKey middlewares in host computer in interactive process, the upper layer security application (application layer) in host computer is led to
Cross and call USBKey middlewares, USBkey middlewares are driven by USB and carry out APDU instruction interactions with USBKey master chips.But
In practical application, for a certain operating system, multiple release branches are typically had, such as (SuSE) Linux OS, just had
The multiple release such as Ubuntu, Fedora, Debian branch, desktop environment, the window pipe carried in different Linux releases
Reason device, graphics application program framework (hereinafter referred to as UI frameworks) etc. are all not quite similar.Even identical Linux is issued
Version, the system environments configuration that the terminal user of USBKey products is used is generally also each variant.In UI application development ranks
Section, different UI frameworks mean that different UI design concepts, different UI calling interfaces agreements, different data structures are determined
Adopted, different compilings relies on environment.Therefore, to realize for different system UI frameworks deployment USBKey middlewares, generally meaning
Taste to be needed to develop many money software products respectively.On the premise of user system environment configuration is not changed, how to make to be handed over comprising UI
The USBKey middlewares of mutual function are operated in the system of more different editions, are always a problem.
The content of the invention
For defect present in prior art, it is an object of the invention to provide a kind of client and UI exchange methods,
Realize the normal operation under the various different UI framework running environment of USBkey middlewares with UI interactive functions.
To achieve the above object, the technical solution adopted by the present invention is as follows：
A kind of client, is provided with USBkey middlewares in the client, the USBkey middlewares include UI components
With non-UI components, the UI components refer to all parts for being related to UI interactive functions in USBkey middlewares；The UI components
Including the UI modules that several are realized for different UI frameworks running environment；The UI of USBkey middlewares client according to where it
Framework running environment enables corresponding UI modules；The USBkey middlewares also include：
UI communication interfaces UI_API：For being communicated using process communication mode between non-UI components and UI components.
Further, a kind of client as described above, the USBkey middlewares also include：U/I interface storehouse, for encapsulating
Storage UI calls primitive；It is the determination of UI interaction scenarios, the non-UI according to involved by USBkey middlewares that the UI calls primitive
The primitive unrelated with operating system platform arranged between component and UI components；Used between the non-UI components and UI components
The UI calls primitive to be communicated.
Further, a kind of client as described above, the UI frameworks running environment is included under (SuSE) Linux OS
Java Runtime Environment, Qt running environment and GTK running environment.
Further, a kind of client as described above, the USBkey middlewares also include：
UI assembly management interfaces, are managed for the UI components to USBkey middlewares；The management is included to UI moulds
Increase, modification or the deletion of block.
A kind of UI exchange methods based on the client are additionally provided in the embodiment of the present invention, is comprised the following steps：
USBkey middlewares according to its operation where client UI framework running environment, it is determined that and enable its with it is described
The corresponding UI modules of UI framework running environment；
The non-UI components of USBkey middlewares send UI and ask letter by interprocess communication mode to the UI modules for being enabled
Breath, UI modules call the U/I interface of client to complete corresponding UI interactive actions according to the UI solicited messages for receiving.
Further, a kind of UI exchange methods as described above, non-UI components call primitive to send UI to UI modules using UI
Solicited message；It is described that to call primitive be UI interaction scenarios according to involved by USBkey middlewares determine, non-UI components and UI
The primitive unrelated with operating system platform arranged between component.
Further, a kind of UI exchange methods as described above, the UI interaction scenarios include user cipher obtain and checking,
Prompting user key-press, offer user's selective listing are selected for user.
Further, a kind of UI exchange methods as described above, the UI calls the primitive to include UI session start primitive
BeginSession, UI conversation end primitive EndSession, Password Input dialog box display primitive PIN_Show, user cipher
Obtain primitive PIN_GetPIN, code error prompting and re-enter primitive PIN_Retry, Password Input frame and close primitive PIN_
Finish, wait dialog box display primitive Waiting_Show, wait dialog box close primitive Waiting_Finish, list choosing
Select frame display primitive List_Show and user's options is obtained and dialog box closes primitive List_GetSel.
Further, a kind of UI exchange methods as described above, USBkey middlewares run ring according to the UI frameworks of client
Border, it is determined that and run its UI module corresponding with the UI frameworks running environment, including：
Non- UI components send UI session start primitive to several UI modules successively, and response will be received in setting time
The UI modules of data, are defined as the UI module corresponding with UI framework running environment.
Further, a kind of UI exchange methods as described above, USBkey middlewares run ring according to the UI frameworks of client
Border, it is determined that and run its UI component corresponding with the UI frameworks running environment, including：
USBkey middlewares send the solicited message for obtaining UI framework running environment to client；
The UI framework running environment information that USBkey middlewares are returned according to client determines and runs it with the UI frames
The corresponding UI modules of frame running environment.
The beneficial effects of the present invention are：Client provided by the present invention and UI exchange methods, by that will be handed over UI
UI modules in the USBkey middlewares of mutual function are stripped out, and are provided with the UI groups suitable for different UI frameworks running environment
Part, enables USBkey middlewares to be applied under different UI framework running environment, solves because of UI frameworks different band
The deployment problem of USBkey middlewares.
Brief description of the drawings
Fig. 1 is a kind of structural representation of client in the specific embodiment of the invention；
Fig. 2 is the schematic diagram of non-UI components and UI assembly communications in the specific embodiment of the invention；
Fig. 3 is a kind of schematic flow sheet of UI exchange methods in the specific embodiment of the invention；
Fig. 4 is that each UI calls state machine transition diagram between primitive in the specific embodiment of the invention.
Specific embodiment
With reference to Figure of description, the present invention is described in further detail with specific embodiment.
Fig. 1 shows a kind of structural representation of client in the specific embodiment of the invention, as can be seen from Figure, should
USBkey middlewares are installed, the USBkey middlewares include UI components 10 and non-UI components 20, the UI groups in client
Part 10 refers to all parts for being related to UI interactive functions in USBkey middlewares；The UI components 10 include several for not
With the UI modules 11 that UI frameworks running environment is realized；USBkey middlewares UI framework running environment of client according to where it is opened
With corresponding UI modules；In order to realize the data interaction between UI components 10 and non-UI, the USBkey middlewares also include UI
Communication interface UI_API30, is led to by the communication interface between non-UI components 20 and UI components 10 using process communication mode
Letter.
In present embodiment, described client is can be communicatively coupled with USBkey, and can be by the side such as network
The equipment that formula is connected and carries out data interaction with USBkey signature verification service devices, including but not limited to PC etc..The USBkey
Middleware is that USBkey equipment suppliers provide, and USBkey middlewares are initially stored in USBkey, in USBkey and visitor
During the first connection of family end, USBkey middlewares can be installed in client, be the software for operating USBkey.In USBKey
Between part realize one group of common interface, there is provided depend on the cryptographic functions service of USBKey, such as encrypting and decrypting, signature sign test,
Management key and container, management certificate etc..USBKey middlewares are driven by USB and carry out APDU instruction friendships with USBKey master chips
Mutually, the interface that the safety applications on upper strata only need to call middleware to provide is capable of achieving cryptographic applications.
Client provided in present embodiment, UI is related in the USBkey middlewares that it is installed
The UI components 10 of (User Interface) interactive function are separated, and are respectively provided with for different UI framework running environment
Several are applied to the UI modules 11 of different UI frameworks running environment so that USBkey middlewares can operate in it is more
UI framework running environment in, even if the UI framework running environment of the client of user changes, it is also possible to select corresponding
UI modules realize normal UI interactions, and without individually being developed in the middle of different USBkey for different UI frameworks running environment
Part product.
Additionally, being separated by by UI components 10 and non-UI components 20, new UI frames are supported if necessary to USBkey middlewares
Frame running environment (when USBkey middlewares do not have corresponding UI modules) or the part to being related to UI interactive functions in middleware are entered
During row modification, it is only necessary to develop new UI modules or UI modules are modified, and need not be to the non-of USBkey middlewares
UI components are modified, and greatly reduce workload, improve renewal efficiency.
In present embodiment, the UI frameworks running environment includes but is not limited to the Java operations under (SuSE) Linux OS
Environment, Qt running environment and GTK running environment etc., accordingly, the UI components include the UI realized based on Java, Qt, GTK
Module, that is, correspond respectively to three kinds of UI frameworks and write three kinds of corresponding UI modules for realizing UI interactive functions respectively.
In actual applications, USBkey middlewares are by upper layer security application call, in present embodiment, in USB middlewares
In addition to above-mentioned UI components 10, other parts (including the non-UI parts and UI communication interface UI_API) all operate in upper layer security
In the process that application software starts, UI components are the UI application programs based on different UI Development of Framework, with independent process, because
This, line number can be entered between the non-UI components and the UI modules 11 of UI components 10 of USBkey middlewares using interprocess communication mode
According to interaction.In present embodiment, the USBkey middlewares also include UI assembly communication interface UI_API, as shown in Fig. 2
Application process where the non-UI components of USBkey middlewares is entered by UI_API interfaces with the UI application programs where UI modules
Journey (UI processes) is communicated, in figure, UI_Server and UI_Resource represent respectively UI servers corresponding to UI processes and
Resource needed for server.
It is described in order to improve the data transmission efficiency between non-UI components 20 and UI modules 11 in present embodiment
USBkey middlewares also include U/I interface storehouse, and primitive is called in U/I interface storehouse for sealed storage UI, and it is root that the UI calls primitive
Determining according to the UI interaction scenarios involved by USBkey middlewares, arranging between non-UI components and UI components and operating system
Platform-independent primitive.
The UI in U/I interface storehouse is called by the UI communication interfaces UI_API 30 between non-UI components 20 and UI components 10
Primitive is called to realize data interaction, the non-UI components for realizing USBkey middlewares call primitive and UI by platform-independent UI
The UI modules of component realize UI interactive operations by Inter-Process Communication, USBkey middlewares is operated in various different UI frames
Under the operating system of frame.
To realize the management to UI modules 11 in UI components 10, in one embodiment of the present of invention, in the middle of the USBkey
Part also includes UI assembly managements interface 40.The UI assembly units management interface 40, for the UI components to USBkey middlewares
It is managed；The management includes increase, modification or deletion to UI modules etc..
A kind of UI exchange methods are additionally provided based on the client shown in Fig. 1, in present embodiment, as shown in figure 3, should
Method is mainly included the following steps that：
Step S1：The UI framework running environment of client of the USBkey middlewares according to where its operation, it is determined that and running
Its UI module corresponding with the UI frameworks running environment；
Step S2：The non-UI components of USBkey middlewares send UI using interprocess communication mode to the UI modules for being enabled
Solicited message, UI modules call the U/I interface of client to complete corresponding UI interactive actions according to the UI solicited messages for receiving.
In present embodiment, the non-UI components call primitive to send UI solicited messages to UI modules using corresponding UI,
Wherein, UI calls the non-UI groups that primitive is the UI interaction scenarios according to involved by USBkey middlewares determine USBey middlewares
The UI unrelated with operating system platform arranged between part and UI components calls primitive.The UI interaction scenarios refer to USBkey
Middleware is involved to show relevant application scenarios with user interface when USBkey operation flows are processed, including user is close
Code is obtained and checking, prompting user key-press and offer user selective listing are for user's selection etc..
The UI calls primitive only to describe a kind of abstract UI displayings or interbehavior, the system UI frameworks institute with client
The UI functions of offer are unrelated, mutually arranged by non-UI components and the UI components of USBkey middlewares, and UI calls primitive to be packaged in
In U/I interface storehouse in USBkey middlewares, upper layer security application process where non-UI components is as desired by calling UI to connect
The UI of correspondence implication calls primitive in mouth storehouse, and the hair of UI solicited messages is completed to the process where a certain UI modules of UI components
Send.In present embodiment, the UI calls the function of primitive and each primitive as shown in the table.
| UI calls primitive | Function |
| BeginSession | Start a UI session |
| EndSession | Terminate a UI session |
| PIN_Show | Display Password Input dialog box |
| PIN_GetPIN | Obtain the password of user input |
| PIN_Retry | Prompting user cipher mistake, re-enters |
| PIN_Finish | Close Password Input dialog box |
| Waiting_Show | Display waits dialog box |
| Waiting_Finish | Close and wait dialog box |
| List_Show | Display list choice box |
| List_GetSel | Obtain user's options, close box |
As can be seen from the above table, it is described to call primitive including but not limited to UI session starts primitive BeginSession, UI
Conversation end primitive EndSession, Password Input dialog box display primitive PIN_Show, user cipher obtain primitive PIN_
GetPIN, code error point out and re-enter primitive PIN_Retry, Password Input frame to close primitive PIN_Finish, wait
Dialog box display primitive Waiting_Show, wait dialog box close primitive Waiting_Finish, list choice box display original
Language List_Show and user's options are obtained and dialog box closes primitive List_GetSel.It is of course also possible to according to reality
Need to call primitive using other.In present embodiment, the above-mentioned state machine conversion respectively called between primitive is as shown in Figure 4.
In one embodiment of the present of invention, USBkey middlewares according to the UI framework running environment of client, it is determined that and transporting
Row its UI module corresponding with the UI frameworks running environment a kind of mode be：
The non-UI components of USBkey middlewares send UI session start primitive to its several UI module of UI components successively,
The UI modules of response data will be received in setting time, is defined as the UI module corresponding with UI framework running environment.
(to the UI of UI components during BeginSession primitive in the non-UI component calls U/I interface storehouse of USBkey middlewares
Module sends UI session starts primitive by Inter-Process Communication mode), the primitive is sent respectively to each UI module successively, attempt
Connection between the two is set up, if after sending the primitive to a certain UI modules, reply data is have received in setting time,
The UI modules that then determining this has response are and match with the UI framework running environment where the operation of USBkey middlewares, then enable
The UI modules are completing follow-up UI interaction flows.
In actual applications, USBkey can first attempt connecting UI modules (the current preceding UI moulds for once running for having run
Block), if connection is not responded, UI session start primitive can be successively sent to other UI modules again, until the connection request
By the response of a certain UI modules, if all UI modules are not responded, UI modules are pointed out to start failure.
In an alternative embodiment of the invention, USBkey middlewares according to the UI framework running environment of client, it is determined that simultaneously
The mode for running its UI module corresponding with the UI frameworks running environment is：
USBkey middlewares send the solicited message for obtaining UI framework running environment to client；
The UI framework running environment information that USBkey middlewares are returned according to client determines and runs it with the UI frames
The corresponding UI modules of frame running environment.
Client and UI exchange methods provided in present embodiment, USBkey middlewares by with platform-independent UI
Call and initiated between primitive and UI components UI to interact, USBkey middlewares realize the UI components with isomery by Inter-Process Communication
Mutual operation, improve versatility of the USBkey middlewares in various UI frameworks running environment, reduce USBkey middlewares
Workload during renewal, improves renewal efficiency.Wherein, the isomery, refers between the UI components of USBkey and non-UI components
It can be the software module for being based respectively on different programming languages, different frameworks to develop.
The present invention is conducted further description with reference to actual UI interaction scenarios.
Client is illustrated by taking PC as an example in the present embodiment, and UI interaction scenarios are that the user cipher in online payment is obtained
And scene is verified, flow is as follows：
USBkey is connected with PC, and connected mode includes but is not limited to USB connections or bluetooth connection etc..Online payment on PC
Call USBkey middlewares using (upper layer security application), the non-UI components of USBkey middlewares using interprocess communication mode to
Each UI modules of its UI component send UI session start primitive successively, and the UI modules for returning to response data are defined as and client
The corresponding UI modules of the UI framework running environment at end, enable the UI modules, and be sent to by Inter-Process Communication mode close
Code input dialogue frame shows the data of primitive, after UI modules receive the data that non-UI components send, calls PC operating systems
UI frameworks graphic interface, PC user interface eject Password Input frame, after user input password, UI modules extract
Code content simultaneously sends that content to non-UI components by Inter-Process Communication mode, and the password of USBkey is completed by non-UI components
Checking, if password is correct, USBkey returns to password authentification by information to middleware, and non-UI components send password to UI modules
Input frame closes primitive, completes the closing of Password Input frame, and password is obtained and checking is completed, if code error, non-UI components
Then code error prompting is sent to UI modules and re-enter primitive, then continue to show Password Input frame, point out user again defeated
Enter password.
Obviously, those skilled in the art can carry out various changes and modification without deviating from essence of the invention to the present invention
God and scope.So, if these modifications of the invention and modification belong to the scope of the claims in the present invention and its equivalent technology
Within, then the present invention is also intended to comprising these changes and modification.
Claims (10)
1. a kind of client, it is characterised in that：USBkey middlewares, the USBkey middlewares bag are installed in the client
UI components and non-UI components are included, the UI components refer to all parts for being related to UI interactive functions in USBkey middlewares；Institute
State the UI modules that UI components are realized including several for different UI frameworks running environment；USBkey middlewares visitor according to where it
The UI framework running environment at family end enables corresponding UI modules；The USBkey middlewares also include：
UI communication interfaces UI_API：For being communicated using process communication mode between non-UI components and UI components.
2. a kind of client according to claim 1, it is characterised in that：The USBkey middlewares also include：U/I interface
Storehouse, primitive is called for sealed storage UI；It is the UI interaction scenarios according to involved by USBkey middlewares that the UI calls primitive
The primitive unrelated with operating system platform determining, arranging between non-UI components and UI components；The non-UI components and UI groups
Primitive is called to be communicated using the UI between part.
3. a kind of client according to claim 1, it is characterised in that：The UI frameworks running environment is grasped including Linux
Make Java Runtime Environment under system, Qt running environment and GTK running environment.
4. according to a kind of client that one of claims 1 to 3 is described, it is characterised in that：The USBkey middlewares also include：
UI assembly management interfaces, are managed for the UI components to USBkey middlewares；The management is included to UI modules
Increase, change or delete.
5. a kind of UI exchange methods based on any client in Claims 1-4, comprise the following steps：
The UI framework running environment of client of the USBkey middlewares according to where its operation, it is determined that and enabling it with the UI frames
The corresponding UI modules of frame running environment；
The non-UI components of USBkey middlewares send UI solicited messages, UI by interprocess communication mode to the UI modules for being enabled
Module calls the U/I interface of client to complete corresponding UI interactive actions according to the UI solicited messages for receiving.
6. a kind of UI exchange methods according to claim 5, it is characterised in that：Non- UI components call primitive to UI using UI
Module sends UI solicited messages；It is described that to call primitive be that UI interaction scenarios according to involved by USBkey middlewares determine, non-
The primitive unrelated with operating system platform arranged between UI components and UI components.
7. a kind of UI exchange methods according to claim 5 or 6, it is characterised in that：The UI interaction scenarios include user
Password is obtained and checking, prompting user key-press, offer user's selective listing are selected for user.
8. a kind of UI exchange methods according to claim 7, it is characterised in that：The UI calls primitive to be opened including UI sessions
Beginning primitive BeginSession, UI conversation end primitive EndSession, Password Input dialog box display primitive PIN_Show, use
Family password obtains primitive PIN_GetPIN, code error prompting and re-enters primitive PIN_Retry, Password Input frame closes original
Language PIN_Finish, wait dialog box display primitive Waiting_Show, wait dialog box close primitive Waiting_Finish,
List choice box shows that primitive List_Show and user's options are obtained and dialog box closes primitive List_GetSel.
9. a kind of UI exchange methods according to claim 8, it is characterised in that：UI of the USBkey middlewares according to client
Framework running environment, it is determined that and run its UI module corresponding with the UI frameworks running environment, including：
Non- UI components send UI session start primitive to several UI modules successively, and response data will be received in setting time
UI modules, be defined as the UI module corresponding with UI framework running environment.
10. a kind of UI exchange methods according to claim 8, it is characterised in that：USBkey middlewares are according to client
UI framework running environment, it is determined that and run its UI component corresponding with the UI frameworks running environment, including：
USBkey middlewares send the solicited message for obtaining UI framework running environment to client；
The UI framework running environment information that USBkey middlewares are returned according to client determines and runs it to be transported with the UI frameworks
The corresponding UI modules of row environment.
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 true CN106778193A (en) | 2017-05-31 |
| CN106778193B 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) |
Cited By (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 (12)
| 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 |
| US20090193434A1 (en) * | 2008-01-25 | 2009-07-30 | Microsoft Corporation | Isolation of user-interactive components |
| 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 |
| CN104102876A (en) * | 2014-07-17 | 2014-10-15 | 北京握奇智能科技有限公司 | Device for safeguarding operational security of client side |
| CN104102859A (en) * | 2014-07-09 | 2014-10-15 | 深圳市茁壮网络股份有限公司 | JavaScript-based middleware authorization method and device |
| CN104809413A (en) * | 2015-05-13 | 2015-07-29 | 上海瓶钵信息科技有限公司 | Trusted user interface framework of mobile platform based on TrustZone |
| 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 |
| CN105900105A (en) * | 2014-02-06 | 2016-08-24 | 英特尔公司 | Media protection policy enforcement for multiple-operating-system environments |
-
2016
- 2016-11-14 CN CN201610998983.1A patent/CN106778193B/en active Active
Patent Citations (12)
| 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 |
| US20090193434A1 (en) * | 2008-01-25 | 2009-07-30 | Microsoft Corporation | Isolation of user-interactive components |
| 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 |
| 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 |
| 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的智能卡中间件的实现", 《微计算机信息》 * |
Cited By (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106778193B (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108027926B (en) | Authentication system and method for service-based payment | |
| US10699277B2 (en) | Security for mobile payment applications | |
| EP4081921B1 (en) | Contactless card personal identification system | |
| CN109804376A (en) | User and equipment certification for web application | |
| US20160189135A1 (en) | Virtual chip card payment | |
| CN108229956A (en) | Network bank business method, apparatus, system and mobile terminal | |
| CN105656890A (en) | FIDO (Fast Identity Online) authenticator, system and method based on TEE (Trusted Execution Environment) and wireless confirmation | |
| US20140172741A1 (en) | Method and system for security information interaction based on internet | |
| CN102496112B (en) | Three-screen payment system based on intelligent SD card and realization method thereof | |
| CN103188241A (en) | User account management method based on mobile intelligent terminal number | |
| CN105101169A (en) | Method and apparatus of information processing by trusted execution environment, terminal and SIM card | |
| CN106657032A (en) | System and method for realizing identity identification and data authentication based on security medium confidential short message | |
| CN109766152A (en) | A kind of exchange method and device | |
| CN106204968A (en) | A kind of many hardware adaptation device based on POS and adaptation method thereof | |
| KR20230009370A (en) | Augmented Reality Card Activation Experience | |
| CN103975567A (en) | Dual-factor authentication method and virtual machine device | |
| CN104835038A (en) | Networking payment device and networking payment method | |
| CN106778193A (en) | A kind of client and UI exchange methods | |
| CN110766388B (en) | Virtual card generation method and system and electronic equipment | |
| CN105871840B (en) | A kind of certificate management method and system | |
| CN108737402A (en) | Mobile terminal safety means of defence and device | |
| CN102983969A (en) | Security login system and security login method for operating system | |
| US20140090032A1 (en) | System and method for real time secure image based key generation using partial polygons assembled into a master composite image | |
| KR101795849B1 (en) | Authentication apparatus and method for connectivity of fintech services, and computer program for the same | |
| CN107315610A (en) | Realize method, device and the computer-readable recording medium of cryptographic function |
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 |