Many computing systems and devices now typically include some form of display. Displays are becoming more common for various reasons, such as decreasing manufacturing costs due to advancing technologies and increasing functionalities. For example, displays can act as input and output devices (e.g., touch sensitive displays) and can also show varying types of media with ease (e.g., high-definition videos and images).
Touch sensitive displays are increasingly used in computing systems and devices that involve some user interaction. Unlike typical input devices, such as keypads or pointing devices, touch sensitive displays can accommodate a wider range of inputs, such as keyboard entries and gestures. Touch sensitive displays can, therefore, facilitate greater user interactions between the users and the computing systems since there is less restriction on the types of user inputs that can be received by the system.
Certain displays can operate to show and/or receive data of varying degrees of security. For example, a point of sale system can receive authentication information from a user, via a touch sensitive device, to complete a payment transaction while also engaging the user for other purposes, such as marketing campaigns. However, data involved in payment transactions needs to comply with industry security protocols and can require increased data processing by the point of sale system that can cause delays in the operation of the point of sale system as a whole.
The drawings, described below, are provided for purposes of illustration, and not of limitation, of the aspects and features of various examples of embodiments described herein. For simplicity and clarity of illustration, elements shown in the drawings have not necessarily been drawn to scale. The dimensions of some of the elements may be exaggerated relative to other elements for clarity. It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the drawings to indicate corresponding or analogous elements or steps.
The various embodiments described herein generally relate to a user interface system operable to provide secured and unsecured modes for handling data. Some of the described embodiments can be directed to receiving secured and unsecured touch input. The user interface system can include a touch sensitive computing device in one embodiment. In some described embodiments, the user interface system can be for providing secured and unsecured outputs. Some other embodiments of the user interface system may involve receiving secured and unsecured touch input as well as providing secured and unsecured outputs.
Data being provided or received at a computing system such as a user interface system typically cannot be easily distinguished based on security levels and/or requirements. Secured data generally needs to comply with certain industry security protocols and thus, the processing of such secured data can consume a substantial portion of the processing resources available at the computing system. However, unsecured data does not need to comply with any industry security protocols and processing the unsecured data in the same manner as the secured data can impair the operation of the computing system as a whole.
For example, touch sensitive computing devices with touch sensitive displays can generally facilitate greater user interactions between the users and the respective computing system than most typical input devices, such as keypads or pointing devices. Touch sensitive displays can accommodate a wider range of inputs, such as keyboard entries and gestures and so, the design of the user interfaces for the touch sensitive computing device are less restricted by the types of inputs that can be used.
Points of sale systems, for example, that incorporate a user interface system can receive authentication information from a user to complete a payment transaction and can also engage the user for other purposes, such as marketing campaigns offered by the merchant. The data involved in payment transactions, however, needs to comply with industry security protocols, which can consume a substantial portion of the processing resources at the point of sale system. Processing of both the transaction data and unsecured data in the same manner is likely to impair the operation of the point of sale system.
It will be appreciated that numerous specific details are set forth in order to provide a thorough understanding of the example embodiments described herein. However, it will be understood by those of ordinary skill in the art that the embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the embodiments described herein. Furthermore, this description and the drawings are not to be considered as limiting the scope of the embodiments described herein in any way, but rather as merely describing the implementation of the various embodiments described herein.
Reference is first made to
The user interface system 110 can be in electronic communication with a secured server 120 and a data server 130 via a network 140. The user interface system 110 can also receive input, directly or indirectly, from the user 10. For example, the user interface system 110 can receive input indirectly from the user 10 via a payment card 150 or a computing device.
The secured server 120 can operate generally with secured data while the data server 130 can operate generally with other data. Each of the secured server 120 and the data server 130 may include one or more processors with computing processing abilities and memory such as a database(s) or file system(s).
For example, when the user interface system 110 operates to receive data, the secured server 120 can operate based generally on secured data provided from the user interface system 110, and the data server 130 can operate based on other data provided from the user interface system 110. When the user interface system 110 operates to provide data, the secured server 120 can operate to provide secured data while the data server 130 can operate to provide the other data to the user interface system 110.
It will be understood that, although only one secured server 120 and one data server 130 are shown in
The network 140 can generally be any network capable of carrying data, including the Internet, Ethernet, plain old telephone service (POTS) line, public switch telephone network (PSTN), integrated services digital network (ISDN), digital subscriber line (DSL), coaxial cable, fiber optics, satellite, mobile, wireless (e.g., Wi-Fi, WiMAX), SS7 signaling network, fixed line, local area network, wide area network, and others, including any combination of these, capable of interfacing with, and enabling communication between, the user interface system 110, the secured server 120 and the data server 130.
In some embodiments, different networks can be provided for each of the secured server 120 and the data server 130. A secured network may be provided to facilitate electronic communication between the user interface system 110 and the secured server 120. For example, when the user interface system 110 operates as a point-of-sale system, the secured server 120 can be a payment processing gateway for authorizing payment transactions initiated at the point-of-sale system and the data server 130 can be a merchant server for facilitating other operations available via the point-of-sale system, such as marketing campaigns or loyalty programs offered by the merchant. The secured network between the payment processing gateway (secured server) 120 and the point-of-sale system (user interface system) 110 can therefore be provided to enable secured and encrypted data transfer, whereas another network can be used to provide data transfer between the merchant server (data server) 130 and the point-of-sale system (user interface system) 110.
The user interface system 110 can include any computing device with a display or operable with a display. The display may be a touch sensitive display in some embodiments. The computing device can also be operable to connect to the network 140. The computing device may couple to the network 140 through a wired or wireless connection. Example computing devices may include at least a processor and memory. In one embodiment, the computing device may be an electronic tablet device, a personal computer, workstation, server, portable computer, mobile device, personal digital assistant, laptop, smart phone, WAP phone, an interactive television, video display terminals, gaming consoles, and portable electronic devices or any combination of these.
Reference will be made to
The interface module 230 can include a secure input controller 232 and an input controller 234. As shown in
Each of the input controller 234 and the secure input controller 232 can receive input data provided via the touch sensitive display 212, and interpret the touch input accordingly.
The secure input controller 232 can be dedicated to receiving and interpreting touch input that requires compliance with certain security protocols. The secure input controller 232 can receive secured input directly from the touch sensitive display 212, or indirectly via the input controller 234. Compliance with security protocols can involve various control measures that require substantial processing power, such as maintenance of a firewall, regular updates of anti-virus software applications, restriction to access, application of various encryption protocols, etc. The secure input controller 232, therefore, is likely to operate slower than the input controller 234, which is not limited by the security protocols.
In some embodiments, the touch sensitive display 212 can include a secured display portion for receiving only secured touch input. Any data received at the secured display portion will be processed by the secure input controller 232.
The secure input controller 232 can, in some embodiments, operate in conjunction with the input controller 234. The input controller 234 can receive touch input from all regions of the touch sensitive display 212 or, if there is a secured display portion, the input controller 234 can receive touch input from regions of the touch sensitive display 212 apart from the secured display portion. The secure input controller 232 can then receive data based on the touch input provided from the input controller 234. Based on the data provided by the input controller 234, the secure input controller 232 can identify the secured touch input and prevent the secured touch input from being provided to the processing module 210.
With the input controller 234 and the secure input controller 232, the touch sensitive system 200A may, therefore, engage in different modes of operations, such as a non-secure input mode and a secure input mode. In some embodiments, the touch sensitive system 200A can be engaged in the secure input mode in response to a signal received from a software application stored at the touch sensitive system 200A or a signal received from the secured server 120.
During the non-secure input mode, the touch sensitive system 200A can receive input at the touch sensitive display 212 that is not limited by security protocols and can be provided directly to the processing module 210. The touch sensitive system 200A can couple the input controller 234 to the processing module 210 for communicating the received touch input to the processing module 210. In some embodiments, the input controller 234 can be coupled to the processing module 210 via the secure input controller 232. The input controller 234 may be coupled to the secure input controller 232 via an Inter-Integrated Circuit (I2C) connection. Similarly, the secure input controller 232 may be coupled to the processing module 210 via an I2C connection.
During the secure input mode, the touch sensitive system 200A can receive input at the touch sensitive display 212 that needs to comply with security protocols. As described, the secure input controller 232 can receive the secured touch input directly from the touch sensitive display 212 (e.g., via a secured display portion) and/or indirectly via the input controller 234.
After receiving the touch data from the touch sensitive display 212 and/or the input controller 234, the secure input controller 232 can block at least some of the touch inputs received at the touch sensitive display 212 from being provided to the processing module 210. By blocking at least some of the touch inputs from being communicated to the processing module 210, the secure input controller 232 can control the type of data that is provided to the processing module 210. For example, data such as authentication information are not provided to the processing module 210.
In some embodiments, the touch sensitive system 200A can activate an indicator 250 to visually show that the secure input mode is engaged. The indicator 250 can be operatively coupled to the secure input controller 232 so that when the secure input controller 232 is engaged in the secure input mode, the secure input controller 232 can also activate the indicator 250. The indicator 250 may be a LED or other visual indicator provided at the touch sensitive system 200A.
Reference will now be made to
Similar to the touch sensitive system 200A shown in
The interface module 230′ of the point-of-sale system 200B, like the interface module 230 of
The interface module 230′ also includes a card interface module 236, a contactless interface module 238 and a tamper-resistance measure module 240.
The card interface module 236 and the contactless interface module 238 operate to receive and process data from the payment card 150 or other compatible computing devices. Each of the card interface module 236 and the contactless interface module 238 can be operatively coupled to the secure input controller 232, as shown in
Referring still to
Another embodiment of the user interface system 110 will now be described with reference to
Similar to the touch sensitive system 200A of
The processing module 210′ of the display system 200C includes a secure processing module 252 and a device processing module 254. The secure processing module 252, like the secure input controller 232, can include processing components that are configured to comply with security protocols. As a result, the secure processing module 252 may operate slower than the device processing module 254. The device processing module 254 can be native to the computing device(s) providing the display system 200C.
Similar to the touch sensitive system 200A and the point-of-sale system 200B, when operating in the secure input mode, the display system 200C can receive input at the touch sensitive display 212 that needs to comply with security protocols. The secure input controller 232 can receive the secured touch input and initiate operation by the secure processing module 252.
During the non-secure input mode, the display system 200C can receive input at the touch sensitive display 212 that is not limited by security protocols and can be provided directly to the device processing module 254.
An example operation of the point-of-sale system 200B will now be described with reference to
The point-of-sale system 300 includes a touch sensitive display 312, a chip reader 336a, a magnetic strip reader 336b, and a contactless reader 338. It will be understood that the point-of-sale system 300 illustrated in
In response to a selection of the form of payment or detection of an insertion of the payment card 150 at the chip reader 336a, the point-of-sale system 300 can be engaged in the secured mode since the touch input being received is authentication information that needs to comply with the payment security protocols. The point-of-sale system 300 may similarly be engaged in the secured mode in response to a signal received from the payment processing gateway 120. As shown in
Continuing with reference to
In the example of
Referring now to
The embodiment shown in the block diagram 500 can operate as a display system. The display system 500 includes a display 512, a processing module 510 and an interface module 530. The processing module 510 includes a secure processing module 552 and a device processing module 554. The interface module 530 includes a secure output controller 532 and an output controller 534.
Unlike the systems 200A to 200C, the display system 500 does not include a touch sensitive display 212. Instead, the display 512 can operate to show various data information.
As shown in
During a secure output mode, for example, the secure output controller 532 can detect that the data to be provided to the display 512 requires compliance with certain security protocols. Accordingly, the secure output controller 532 can couple the secure processing module 552 with the display 512 to facilitate control of the display 512 by the secure processing module 552. On the other hand, during a non-secure output mode, the secure output controller 532 can couple the device processing module 554 with the display 512 so that the device processing module 554 controls the display 512. An example will now be described with reference to
Various embodiments have been described herein by way of example only. Various modification and variations may be made to these example embodiments without departing from the spirit and scope of the invention, which is limited only by the appended claims. Also, in the various user interfaces illustrated in the figures, it will be understood that the illustrated user interface text and controls are provided as examples only and are not meant to be limiting. Other suitable user interface elements may be possible.
This application claims the benefit of U.S. Provisional Application No. 62/027,855, filed Jul. 23, 2014, which application is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4304385 | Farouche et al. | Dec 1981 | A |
5331138 | Saroya | Jul 1994 | A |
5494136 | Humble | Feb 1996 | A |
5970146 | McCall | Oct 1999 | A |
6062477 | Wike, Jr. et al. | May 2000 | A |
6098888 | Praden | Aug 2000 | A |
6157966 | Montgomery et al. | Dec 2000 | A |
6766994 | Serbinski et al. | Jul 2004 | B2 |
7004385 | Douglass | Feb 2006 | B1 |
7048184 | Persky | May 2006 | B2 |
7597250 | Finn | Oct 2009 | B2 |
7866546 | Vance | Jan 2011 | B1 |
8261064 | Ditzman | Sep 2012 | B2 |
8558685 | Long et al. | Oct 2013 | B2 |
8768838 | Hoffman | Jul 2014 | B1 |
8788428 | Weston | Jul 2014 | B2 |
8944322 | White | Feb 2015 | B2 |
9047639 | Quintiliani et al. | Jun 2015 | B1 |
9092766 | Bedier et al. | Jul 2015 | B1 |
9129274 | Mocko et al. | Sep 2015 | B1 |
9257018 | Edwards et al. | Feb 2016 | B2 |
9286494 | Lamfalusi et al. | Mar 2016 | B1 |
9589428 | Edwards et al. | Mar 2017 | B2 |
9741211 | Skiles | Aug 2017 | B2 |
9881288 | Bell et al. | Jan 2018 | B1 |
9911266 | Weston et al. | Mar 2018 | B2 |
9916570 | Edwards et al. | Mar 2018 | B2 |
9946506 | Ting et al. | Apr 2018 | B2 |
9965116 | Wolter | May 2018 | B1 |
20020082993 | Hoyos et al. | Jun 2002 | A1 |
20020166891 | Stoutenburg et al. | Nov 2002 | A1 |
20030004876 | Jacobson | Jan 2003 | A1 |
20030066893 | Yap et al. | Apr 2003 | A1 |
20030135406 | Rowe | Jul 2003 | A1 |
20030135751 | O'Donnell | Jul 2003 | A1 |
20030191713 | Yap et al. | Oct 2003 | A1 |
20040043650 | Yang et al. | Mar 2004 | A1 |
20050039052 | O'Donnell et al. | Feb 2005 | A1 |
20050283403 | Ramirez et al. | Dec 2005 | A1 |
20060168663 | Vijloen et al. | Jul 2006 | A1 |
20060226224 | Henry | Oct 2006 | A1 |
20060242696 | Cruzado et al. | Oct 2006 | A1 |
20070251997 | Brown et al. | Nov 2007 | A1 |
20070257110 | Schmidt et al. | Nov 2007 | A1 |
20090006262 | Brown et al. | Jan 2009 | A1 |
20090102813 | Mamba | Apr 2009 | A1 |
20090119221 | Weston et al. | May 2009 | A1 |
20090173790 | Hart et al. | Jul 2009 | A1 |
20090222383 | Tato et al. | Sep 2009 | A1 |
20090307142 | Mardikar | Dec 2009 | A1 |
20100057620 | Li et al. | Mar 2010 | A1 |
20100211469 | Salmon et al. | Aug 2010 | A1 |
20100262504 | Tamura | Oct 2010 | A1 |
20110176004 | Chaussade | Jul 2011 | A1 |
20110199308 | Nativel | Aug 2011 | A1 |
20120023026 | Chen et al. | Jan 2012 | A1 |
20120066079 | Falzone et al. | Mar 2012 | A1 |
20120197744 | Rose et al. | Aug 2012 | A1 |
20120242526 | Perez et al. | Sep 2012 | A1 |
20120254038 | Mullen | Oct 2012 | A1 |
20120290420 | Close | Nov 2012 | A1 |
20130006847 | Hammad et al. | Jan 2013 | A1 |
20130050084 | Soffer | Feb 2013 | A1 |
20130144731 | Baldwin et al. | Jun 2013 | A1 |
20130153656 | Skiles | Jun 2013 | A1 |
20130155595 | Herring et al. | Jun 2013 | A1 |
20130198086 | Mardikar | Aug 2013 | A1 |
20130246171 | Carapelli | Sep 2013 | A1 |
20130299574 | Theobald | Nov 2013 | A1 |
20140022211 | Karpin et al. | Jan 2014 | A1 |
20140047390 | Thorsander et al. | Feb 2014 | A1 |
20140071043 | Jung et al. | Mar 2014 | A1 |
20140089174 | Carapelli et al. | Mar 2014 | A1 |
20140095387 | Colnot | Apr 2014 | A1 |
20140096222 | Colnot | Apr 2014 | A1 |
20140097249 | Gomez | Apr 2014 | A1 |
20140101035 | Tanner et al. | Apr 2014 | A1 |
20140172607 | Skiles | Jun 2014 | A1 |
20140214688 | Weiner | Jul 2014 | A1 |
20140252089 | Bostwick | Sep 2014 | A1 |
20140256251 | Caceres | Sep 2014 | A1 |
20140283857 | Liu | Sep 2014 | A1 |
20150095134 | Parker et al. | Apr 2015 | A1 |
20150095241 | Edwards | Apr 2015 | A1 |
20150100498 | Edwards | Apr 2015 | A1 |
20150199882 | Fernando et al. | Jul 2015 | A1 |
20150261314 | Herring et al. | Sep 2015 | A1 |
20150363757 | Mocko et al. | Dec 2015 | A1 |
20160005020 | Fernando et al. | Jan 2016 | A1 |
20160012465 | Sharp | Jan 2016 | A1 |
20160051067 | Law et al. | Feb 2016 | A1 |
20160070964 | Conrad | Mar 2016 | A1 |
20160117529 | Bedier et al. | Apr 2016 | A1 |
20160117659 | Bedier et al. | Apr 2016 | A1 |
20160117662 | Bedier et al. | Apr 2016 | A1 |
20160124627 | Beatty et al. | May 2016 | A1 |
20160148023 | Lamfalusi et al. | May 2016 | A1 |
20170154334 | Lewis et al. | Jun 2017 | A1 |
20170221035 | Edwards et al. | Aug 2017 | A1 |
20170308882 | Bedier et al. | Oct 2017 | A1 |
20170311737 | Law et al. | Nov 2017 | A1 |
20170364888 | Bell et al. | Dec 2017 | A1 |
20180039965 | Han et al. | Feb 2018 | A1 |
20180150818 | Mocko et al. | May 2018 | A1 |
20180174013 | Lee | Jun 2018 | A1 |
20180174391 | Weston et al. | Jun 2018 | A1 |
Number | Date | Country |
---|---|---|
2015349752 | Jul 2017 | AU |
2 955 454 | Jan 2016 | CA |
106716470 | May 2017 | CN |
2011051757 | May 2011 | WO |
2012078990 | Jun 2012 | WO |
2015001468 | Jan 2015 | WO |
2016014346 | Jan 2016 | WO |
Entry |
---|
IEEE Dictionary, p. 247, 2007, (IA/PE/PSE) 1100-1999, 599-1985w, definition of ‘coupling’ provided withing text of Office Action. |
Authoritative Dictionary of IEEE Standards Terms, 7th Edition, available at https://ieeexplore.ieee.org/document/4116787 (Year: 2000). |
Maxim Integrated, “Application Note 4809: Designing Next-Generation Payment Terminals That Meet PCI PTS 3.x Requirements”, attached as PDF file, downloaded from https://www.maximintegrated.com/en/app-notes/index.mvp/id/4809, dated May 19, 2011 (Year: 2011). |
International Search Report and Written Opinion for International Application No. PCT/US15/40819, dated Oct. 13, 2015. |
Extended European Search Report for European Patent Application No. 15825575.2, dated Nov. 28, 2017. |
Non-Final Office Action dated May 21, 2015, for U.S. Appl. No. 14/592,102, of Chen, Y., et al., filed Jan. 8, 2015. |
Final Office Action dated Dec. 9, 2015, for U.S. Appl. No. 14/592,102, of Chen, Y., et al., filed Jan. 8, 2015. |
Non-Final Office Action dated Apr. 12, 2016, for U.S. Appl. No. 14/982,840, of Edwards, T., et al., filed Dec. 29, 2015. |
Non-Final Office Action dated Jul. 20, 2016, for U.S. Appl. No. 14/848,123, of Guise, M., et al., filed Sep. 8, 2015. |
Notice of Allowance dated Oct. 24, 2016, for U.S. Appl. No. 14/982,840, of Edwards, T., et al., filed Dec. 29, 2015. |
Final Office Action dated Jan. 27, 2017, for U.S. Appl. No. 14/848,123, of Guise, M., et al., filed Sep. 8, 2015. |
Non-Final Office Action dated Mar. 31, 2017, for U.S. Appl. No. 15/241,901, of Edwards, T., et al., filed Aug. 19, 2016. |
Notice of Acceptance for Australian Patent Application No. 2015349752, dated Jul. 3, 2017. |
Notice of Allowance dated Oct. 30, 2017, for U.S. Appl. No. 15/241,901, of Edwards, T., et al., filed Aug. 19, 2016. |
Non-Final Office Action dated Feb. 20, 2018, for U.S. Appl. No. 15/793,187, of Mocko, C.L., et al., filed Oct. 25, 2017. |
Notice of Allowance dated Jun. 18, 2018, for U.S. Appl. No. 15/793,187, of Mocko, C.L., et al., filed Oct. 25, 2017. |
Non-Final Office Action dated Jun. 28, 2018, for U.S. Appl. No. 15/003,649, of Chen, Y., et al., filed Jan. 21, 2016. |
Non-Final Office Action dated Jun. 29, 2018, for U.S. Appl. No. 15/003,580, of Chen, Y., et al., filed Jan. 21, 2016. |
International Search Report and Written Opinion for International Application No. PCT/US2015/051082, dated Dec. 18, 2015. |
International Search Report and Written Opinion for International Application No. PCT/US2015/051090 dated Dec. 21, 2015. |
Office Action for European Patent Application No. 15 825 575.2, dated Oct. 1, 2018. |
Final Office Action dated Feb. 21, 2019, for U.S. Appl. No. 15/003,649, of Chen, Y., et al., filed Jan. 21, 2016. |
Non-Final Office Action dated Feb. 26, 2019, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018. |
Summons to Oral Proceeding for European Patent Application No. 15825575.2, dated Mar. 6, 2019. |
Non-Final Office Action dated Apr. 2, 2019, for U.S. Appl. No. 15/003,580, of Chen, Y., et al., filed Jan. 21, 2016. |
Non-Final Office Action dated Sep. 5, 2019, for U.S. Appl. No. 16/051,381, of Chen, Y., et al., filed Jul. 31, 2018. |
Number | Date | Country | |
---|---|---|---|
20160026990 A1 | Jan 2016 | US |
Number | Date | Country | |
---|---|---|---|
62027855 | Jul 2014 | US |