Patent Description:
Existing approaches to secure payment via an electronic device typically limit access to input and output components of the electronic device during the secure payment process. For instance, an operating system of the electronic device might not be permitted to access a touch screen of the electronic device during the secure payment process. As such, a user of the electronic device will be prevented from utilizing other functions of the electronic device during the secure payment process. As a result, the user's ability to multi-task and/or efficiently employ their electronic device is significantly reduced. Document <CIT> discloses methods for using multiple processors on a device.

Provided herein are system, apparatus, device, method and/or computer program product embodiments, and/or combinations and sub-combinations thereof, for tablet mode switching.

An example method embodiment may include steps for implementing tablet mode switching. Steps of the method may include entering, by an electronic device, a payment mode associated with a secure processor of the electronic device; suspending access, by a primary processor of the electronic device, to a component of the electronic device; determining that the electronic device is connected to a docking hub; permitting the primary processor to access a peripheral device connected to the docking hub via a pair connection; and receiving, by the primary processor, user input from the peripheral device connected to the docking hub via the pair connection.

An example apparatus embodiment may include a touch-sensitive display; a connection interface; one or more memory components including a payment application and a system application; and one or more processors and/or circuits coupled to the memory components. Further, the processors may be configured to execute the system application on a primary processor of the processors; suspend access, by the primary processor, to the touch-sensitive display; execute, in a payment mode, the payment application via a secure processor of the one processors; determine that the electronic device is connected to a docking hub via the connection interface; and display, on a touch display of the docking hub, information associated with the system application.

Another example apparatus embodiment may include instructions stored thereon that, when executed by at least one computing device, causes the computing device to perform operations for tablet mode switching. The operations may include entering, by an electronic device, a payment mode associated with a secure processor of the electronic device; suspending access, by a primary processor of the electronic device, to a component of the electronic device; determining that the electronic device is connected to a docking hub; permitting the primary processor to access a peripheral device connected to the docking hub via a pair connection; and receiving, by the primary processor, user input from the peripheral device connected to the docking hub via the pair connection.

Provided herein are system, apparatus, device, method and/or computer program product embodiments, and/or combinations and sub-combinations thereof, for implementing tablet mode switching.

<FIG> is a block diagram of a device system <NUM> implementing tablet mode switching, according to some embodiments. <FIG> illustrates an electronic device <NUM> and a docking hub <NUM> configured to connect with the electronic device <NUM> via a device-to-docking hub connection <NUM> (e.g., a universal serial bus type C (USB-C) connection). Some examples of the electronic device <NUM> include, but are not limited to, tablets, smartphones, mobile devices, personal computers, laptop computers, appliances, internet of things (IoT) devices, wearables, etc. In some embodiments, the electronic device <NUM> may be a device configured to present audio information, graphical content, videos, websites, and media streams. Additionally, some examples of the docking hub <NUM> include kiosks, point of sale stations, or any other device connectable to the electronic device <NUM> and including display functionality and/or user input functionality (e.g., a touch screen, a keyboard, a mouse, a voice dictation interface, etc.).

As illustrated in <FIG>, the electronic device <NUM> may include a touch screen interface <NUM> and a card reader device <NUM>. In some embodiments, the card reader device <NUM> may include at least one of a magnetic strip reader (MSR), a EMV card reader, a contactless payment device, a smart card reader, and so forth. Further, the electronic device <NUM> may be configured to provide one or more applications. For example, the electronic device <NUM> may include a shopping application for managing the purchase of items sold at a retail establishment associated with the electronic device <NUM>. Additionally, the electronic device <NUM> may include a payment application for processing payment information associated with a financial card (e.g., a credit card, a debit card, a rewards card, etc.) read by the card reader device <NUM> in connection with a purchase order at the retail establishment.

In some embodiments, an employee <NUM> may use the electronic device <NUM> to assist a consumer <NUM> in purchasing one or more items from the retail establishment. For instance, the consumer <NUM> may endeavor to purchase a set of composition notebooks from the retail establishment. As such, the employee <NUM> may select the set of composition notebooks within the shopping application via the touch screen interface <NUM>. Once the set of composition notebooks has been selected, the employee <NUM> or the consumer <NUM> may cause the electronic device <NUM> to enter a secure payment mode for receiving payment information from the consumer <NUM>. For example, the employee <NUM> may select a control (e.g., a virtual button), presented within a graphical user interface (GUI) of the electronic device <NUM> that causes the electronic device <NUM> to enter a secure payment mode.

Within the secure payment mode, a secure processor of the electronic device <NUM> may possess exclusive access to the touch screen interface <NUM> and execute the payment application to facilitate receipt of payment for the set of composition notebooks. As a result, the shopping application may no longer access the touch screen interface <NUM> of the electronic device <NUM>. In some embodiments, the payment application may perform a payment workflow in the secure payment mode. For instance, the payment application may request the consumer <NUM> swipe a debit card in the card reader device <NUM> to obtain payment information and provide an authentication personal identification number (PIN) code to the payment application via the touch screen interface <NUM>. In addition, the payment workflow may present graphical information on the touch sensitive interface <NUM> for entering the PIN code. For example, the payment workflow may present a virtual PIN entry control including alpha numeric elements within a GUI. Further, the payment application may validate the payment information and authentication PIN code. By including PIN code entry via the electronic device <NUM>, the identity of the consumer <NUM> may be ascertained without intervention of the employee <NUM>. However, as described herein, the security of the PIN code is subject to strict controls, as promulgated by the payment card industry (PCI) data security standard (DSS) among other domestic and international standards, designed to substantially reduce the ability to compromise PIN codes through an attack on the electronic device <NUM>.

As illustrated in <FIG>, the docking hub <NUM> may be connected to a touch screen interface <NUM>. Further, as described in detail herein, the electronic device <NUM> may be paired with the docking hub <NUM> while in the secure payment mode. In response, the shopping application may continue its execution on the primary processor of the electronic device <NUM>. Additionally, the employee <NUM> may utilize the shopping application via the touch screen interface <NUM> connected to the docking hub <NUM>, while the consumer <NUM> employs the touch interface <NUM> to complete the payment workflow of the payment application. As such, the electronic device <NUM> may be able to securely provide payment processing via the secure processor while contemporaneously providing other functionality of the electronic device <NUM> via the primary processor.

<FIG> is a block diagram of a device system <NUM> implementing tablet mode switching, according to some embodiments. <FIG> illustrates a tablet device <NUM> and a docking hub <NUM> connected via a pair connection <NUM>. In some embodiments, the tablet device <NUM> and the docking hub <NUM> may be electronic devices that are distributed to customer operated and owned locations, such as retail establishments. Further, the tablet device <NUM> may provide access to information associated with products and/or services provided in the retail establishments. Further, the tablet device <NUM> may be used by employees and consumers within the retail establishments to facilitate the purchase of goods or services from the retail establishments.

As illustrated in the example of <FIG>, the tablet device <NUM> may include a primary processor <NUM>, a secure processor <NUM>, an operating system <NUM>, one or more applications <NUM>(<NUM>)-(N), a payment application <NUM>, a card reader device <NUM>, a security module <NUM>, input/output (I/O) devices <NUM> (e.g., a touch sensitive display <NUM>), and a communication device <NUM>. In various embodiments, the tablet device <NUM> may be any type of electronic device including but not limited to smartphones, mobile devices, personal computers, laptop computers, appliances, internet of things (IoT) devices, wearables, etc., or any other type of device or computing system capable of performing secure payment processes.

As referred to herein, in some embodiments, a "processor" may refer to circuitry and/or logic capable of executing processes and/or procedures according to machine-readable instructions. For example, a processor may retrieve machine-readable instructions from a storage medium, execute processes for processing signals based at least in part on the retrieved instructions and provide a result based at least in part on the processed data. The processor may be embedded on an integrated circuit to support specific predetermined functionality. In some embodiments, a processor may be characterized as a "controller," "microcontroller," "microprocessor" and/or other programmable logic device capable of executing instructions.

The primary processor <NUM> may execute the operating system <NUM> and the applications <NUM>(<NUM>)-(N). The operating system <NUM> may be an application program configured to manage the basic functions of the tablet device <NUM>. For instance, the operating system <NUM> may be configured to schedule tasks, manage storage of data on the tablet device <NUM>, provide common services to the applications <NUM>(<NUM>)-(N) , and communicate with peripheral devices. Some examples of the operating system <NUM> may include Google's Android™ operating system, Microsoft's Windows™ operating system, Apple's Mac OS/X® or iOS operating systems, some variety of the Linux operating system, or the like.

As used herein, and in some embodiments, an "application" may refer to any application or software (e.g., client, agent, application, mobile application, web application, hybrid application, computer program, desktop application, or module) operable to run on the tablet device <NUM>. For example, the application <NUM>(<NUM>) may be a shopping application for purchasing items sold at a retail establishment associated with the tablet device <NUM>. Some other examples of applications <NUM>(<NUM>)-(N) include inventory management software, customer relationship management software, financials administration software, and warehouse management software.

As used herein, in some embodiments, a "secure processor" may refer to a cryptographic processor coupled to at least one of a secure storage random-number generator, secure storage including secure firmware and/or encryption/decryption keys, or tamper detection sensors. Further, the secure firmware may include the payment application <NUM>, an encryption/decryption method using the encryption /decryption keys, and one or more authentication methods. Additionally, in some embodiments, the secure processor <NUM> may be configured with tamper-proof functionality, anti-eavesdropping functionality, sensitive access protection, and an auto-erase function. An example of a secure processor includes a secure microcontroller.

Additionally, the secure processor <NUM> may execute the payment application <NUM>. Further, the payment application <NUM> may be configured to process payment information via one or more steps of a payment workflow. In some embodiments, the payment workflow may include steps for determining a consumer's financial information, determining whether a financial card is a debit card or a credit card, sending a payment authorization request <NUM> to a payment network <NUM> (e.g., an electronic funds transfer point of sale network) via a communication network <NUM>, requesting input of pin information (e.g., a PIN code) associated with the financial card via the input/output (I/O) devices <NUM> (e.g., the touch sensitive display <NUM>), encrypting the pin information, sending the encrypted pin information <NUM> to the payment network <NUM> via the communication network <NUM>, and receiving a payment authorization response <NUM> corresponding to the payment authorization request <NUM> via the communication network <NUM>. Additionally, the payment network <NUM> may determine the payment authentication response <NUM> based on verifying the financial account associated with the financial card has the necessary funds to complete the transaction, and verifying that the pin information corresponds to the financial card.

The communication network <NUM> may include any combination of a private network, personal area network (PAN), Local-Area Network (LAN), Wide-Area Network (WAN), or the Internet. Further, the connection between the tablet device <NUM>, the docking hub <NUM>, the payment network <NUM>, and the communication network(s) <NUM> may be a wireless connection (e.g., Bluetooth or other short range wireless technology, cellular, Wi-Fi connection, etc.), or a wired connection (e.g., Ethernet, universal serial bus (USB), etc.), or a combination thereof. In some embodiments, the tablet device <NUM>, the docking hub <NUM>, and the payment network <NUM> may employ one or more communication protocols to send and receive information over the communication network <NUM>.

In some embodiments, the payment information may correspond to a financial account and/or financial card (e.g., a credit card, a debit card, a rewards card, etc.). Further, the payment information may be obtained from the financial card via the card reader device <NUM> or another peripheral of the tablet device <NUM>. For example, an employee or consumer within the retail establishment may cause the card reader device <NUM> to read a financial card to obtain to the payment information. In some other examples, the payment information may be obtained from a financial card or a device associated with the financial card via contact or contactless communication, e.g., radiofrequency identification, near-field communication, etc. In yet still some other examples, the payment information may be manually entered in to the tablet device <NUM> via the input/output (I/O) devices <NUM> (e.g., the touch sensitive display <NUM>).

Further, the secure processor <NUM> may execute the payment application within a secure payment mode. Within the secure payment mode, the primary processor <NUM> may not be provided access to the touch sensitive display <NUM>. As a result, the tablet device <NUM> substantially reduces the risk of a malicious actor obtaining unauthorized access to PIN codes through an attack. In some embodiments, the secure payment mode may abide by protocols and/or practices set forth by domestic and/or international security organizations. For example, as described above, the secure payment mode may operate in accordance with PCI standards (e.g., PCI DSS, PCI pin transaction security (PTS), etc.).

For example, an employee <NUM> may utilize the shopping application of the tablet device <NUM> to organize the purchase of a set of composition notebooks. Further, the employee <NUM> may indicate to the shopping application that the employee <NUM> is done selecting items for purchase and prepared to begin the payment process. As a result, the shopping application <NUM>(<NUM>) may call for the execution of a payment workflow of the payment application <NUM> via the secure processor <NUM>. During the payment workflow, the payment application <NUM> may request that the employee <NUM> or the consumer <NUM> swipe a financial card <NUM> of the consumer <NUM>. In addition, the payment application <NUM> may request that the consumer <NUM> enter a PIN code associated with the financial card <NUM> via the touch sensitive display <NUM>.

Further, given that the tablet device <NUM> is operating within the secure payment mode, the touch sensitive display <NUM> may be inaccessible to the primary processor <NUM> and the shopping application <NUM>. As such, the shopping application <NUM> may be unable to display information to the touch sensitive display <NUM>. In addition, the shopping application <NUM> may be unable to access the PIN code information input by the consumer <NUM> via the touch sensitive display <NUM>.

In some embodiments, the tablet device <NUM> may employ a switching module <NUM> (e.g., an analog switch) to switch between the normal operation mode of the tablet device <NUM> and the secure payment mode of the tablet device <NUM>. For example, when the tablet device <NUM> enters the secure payment mode, the switching module <NUM> may disable access by the primary processor <NUM> to one or more of the I/O devices <NUM>, e.g., the touch sensitive display <NUM>. Thereby preventing access by the operating system <NUM> and/or applications <NUM>(<NUM>)-(N) to the touch sensitive display <NUM>. Further, the switching module <NUM> may ensure that input data <NUM> captured at the touch sensitive display <NUM> is routed to the secure processor <NUM>, and graphical data <NUM> generated by the payment application <NUM> is routed to the touch sensitive display <NUM>. Additionally, when the payment application <NUM> completes one or more steps of the payment workflow, the switching module <NUM> may switch back to the normal operation mode from the secure payment mode and re-enable access by the primary processor <NUM> to the touch sensitive display <NUM>.

In some embodiments, prior to the switch from the normal operation mode to the secure payment mode, the operating system <NUM> or one of the applications <NUM>(<NUM>)-(N) may determine a context of the normal operation mode of the tablet device <NUM>. For example, the operating system <NUM> may determine the applications currently executing on the primary processor <NUM> and the graphical information currently displayed on the touch sensitive display <NUM>. Additionally, the operating system <NUM> may store or otherwise maintain the context while the tablet device <NUM> is in the secure payment mode.

The docking hub <NUM> may include or be connected to a touch sensitive display <NUM>. For instance, the docking hub <NUM> may be connected to the touch sensitive display <NUM> via a USB-C connection or a high-definition multimedia interface (HDMI) connection. In addition, the docking hub <NUM> may include a communication device <NUM>, and a device identifier <NUM>. As illustrated in <FIG>, the tablet device <NUM> and the docking hub <NUM> may be paired via the pair connection <NUM>. For instance, the communication device <NUM> and the communication device <NUM> may establish the pair connection <NUM> between the tablet device <NUM> and the docking hub <NUM>. The pair connection <NUM> may be a wired or wireless personal area network employing at least one of USB, FireWire, Wi-Fi, Bluetooth, ultra-wide band, Z-Wave, ZigBee, Thread, or any other capable technology. For example, the pair connection <NUM> may be a USB-C connection. As such, the communication device <NUM> may be a USB-C male interface and the communication device <NUM> may be a USB-C female interface, or vice versa. As another example, the communication device <NUM> and the communication device <NUM> may be wireless devices, and the pair connection <NUM> may be a wireless channel capable of transmitting graphical information from the tablet device <NUM> to the docking hub <NUM>, and/or input data captured at the docking hub <NUM> to the tablet device <NUM>. Further, the tablet device <NUM> can connect (i.e., dock) or disconnect (i.e., undock) from the docking hub <NUM> via a wireless pair connection <NUM> using a proximity sensor and/or software switch.

In some embodiments, when the tablet device <NUM> is in secure payment mode and the pair connection <NUM> has been established, the tablet device <NUM> may permit the primary processor <NUM> to utilize the touch sensitive display <NUM> of the docking hub <NUM>. For example, graphical data associated with the operating system <NUM> and/or the applications <NUM>(<NUM>)-(N) may be displayed on the touch sensitive display <NUM>. In some instances, the operating system <NUM> may identify the context associated with the last state of the normal operating mode, and restore the context using the primary processor <NUM> and the touch sensitive display <NUM>. For example, the graphical information displayed on touch sensitive display <NUM> by the applications <NUM>(<NUM>)-(N) in the context may be displayed on the touch sensitive display <NUM>.

Further, the employee <NUM> may provide input to the operating system <NUM> and/or the applications <NUM>(<NUM>)-(N) via the touch sensitive display <NUM>. As such, the employee <NUM> may continue to operate the tablet device <NUM> while the consumer <NUM> securely completes the payment workflow in the secure payment mode without risking compromising the secrecy of the PIN code or any other payment information associated with the consumer <NUM>.

Further, when the consumer <NUM> completes at least one step of the payment workflow, the switching module <NUM> may switch the tablet device <NUM> back to the normal operating mode from the secure payment mode. For example, the switching module <NUM> may re-enable access by the primary processor <NUM> to the I/O devices (e.g., the touch sensitive display <NUM>). In other words, the switching module <NUM> may ensure that input data captured at the touch sensitive display <NUM> is routed to the primary processor <NUM>, and graphical data generated by the operating system <NUM> or the applications <NUM>(<NUM>)-(N) is routed to the touch sensitive display <NUM>. In some embodiments, prior to the switch from the secure payment mode to the normal operation mode, the operating system <NUM> or one of the applications <NUM>(<NUM>)-(N) may determine a context of the normal operation mode of the tablet device <NUM>. For example, the operating system <NUM> may determine the graphical information currently displayed on the touch sensitive display <NUM>. Additionally, the operating system <NUM> may display the graphical information on the touch sensitive display <NUM> after the switch from the secure payment mode to normal operating mode.

In some embodiments, the security module <NUM> may verify the docking hub <NUM> using the device identifier <NUM> of the docking hub <NUM>. Further, if the security module <NUM> determines that the docking hub <NUM> is an authorized device, the security module <NUM> may permit the tablet device <NUM> and the docking hub <NUM> to form the pair connection <NUM>. If the security module <NUM> determines that the docking hub <NUM> is unauthorized device, the security module <NUM> may prevent formation of the pair connection <NUM>. In other words, the security module <NUM> may prevent transmission of the graphical data <NUM> and/or the input data <NUM> between the tablet device <NUM> and the docking hub <NUM> when the docking hub <NUM> is not an authorized device.

In some examples, the device identifier <NUM> may be assigned to the tablet device <NUM> at the time the tablet device <NUM> is manufactured in a manufacturing facility. In some other instances, the device identifier <NUM> is assigned to hardware and/or software installed on the tablet device <NUM>. For example, an administrator may purchase software and install the software on the tablet device <NUM>. As a result, the identifier of the software may become the device identifier <NUM> of the docking hub <NUM>. In some embodiments, the device identifier <NUM> may be a vendor identifier common to electronic devices manufactured by the vendor or a unique identifier particular to the docking hub <NUM>.

Further, in some embodiments, the docking hub <NUM> may recharge a battery of the tablet device <NUM>, and/or provide power for operating the tablet device <NUM> for extended periods. For example, the docking hub <NUM> may provide power to the tablet device via the USB-C connection (i.e., the pair connection) between the tablet device <NUM> and docking hub <NUM>.

Further, in some embodiments, the docking hub <NUM> may be a point of sale device configured to facilitate payment processes. Consequently, the tablet device <NUM> and docking hub <NUM> may each be configured to independently facilitate financial transactions.

<FIG> is a flowchart for a method <NUM> for a process for implementing zero touch deployment and dynamic configuration in a managed device system, according to some embodiments. Method <NUM> can be performed by processing logic that can comprise hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executing on a processing device), or a combination thereof. It is to be appreciated that not all steps may be needed to perform the disclosure provided herein. Further, some of the steps may be performed simultaneously, or in a different order than shown in <FIG> as will be understood by a person of ordinary skill in the art.

Method <NUM> shall be described with reference to <FIG> and <FIG>. However, method <NUM> is not limited to that example embodiment.

In <NUM>, the electronic device may enter a payment mode associated with a secure processor of the electronic device. For instance, the employee <NUM> may utilize the shopping application <NUM>(<NUM>) of the tablet device <NUM> to organize the purchase of a set of composition notebooks. Further, the employee <NUM> may indicate to the shopping application <NUM>(<NUM>) that the consumer <NUM> is done shopping and prepared to begin the payment process by selecting a control of a graphical user interface associated with the shopping application <NUM>(<NUM>). As a result, the shopping application <NUM>(<NUM>) may call for the execution of a payment workflow of the payment application <NUM> via the secure processor <NUM> within a secure payment mode.

Further, the payment workflow may request the consumer <NUM> provide PIN code information associated with the financial card <NUM> read by the card reader device <NUM>. For example, the payment workflow may present graphical information on the touch sensitive display <NUM> including a virtual PIN entry control comprising alpha numeric elements. Additionally, the payment workflow may receive the PIN code information via the touch sensitive display <NUM>, and validate the PIN code.

In some embodiments, the switching module <NUM> may switch the tablet device <NUM> from a normal operation mode to the secure payment mode. Further, prior to the switch from the normal operation mode to the secure payment mode, the operating system <NUM> or one of the applications <NUM>(<NUM>)-(N) may determine a context of the normal operation mode of the tablet device <NUM>. For example, the operating system <NUM> may determine the applications currently executing on the primary processor <NUM> and the graphical information currently displayed on the touch sensitive display <NUM>. Additionally, the operating system <NUM> may store or otherwise maintain the context while the tablet device <NUM> is in the secure payment mode.

In <NUM>, the electronic device may suspend access, by a primary processor of the electronic device, to a component of the electronic device. For instance, the tablet device <NUM> may suspend access by the primary processor <NUM> to the one or more of the I/O devices <NUM> (e.g., the touch sensitive display <NUM>). In some embodiments, the switching module <NUM> may render the touch sensitive display <NUM> inaccessible to the primary processor <NUM> and the software programs (e.g., the operating system <NUM> or the applications <NUM>(<NUM>)-(N)) executing on the primary processor <NUM>.

In <NUM>, the electronic device may determine that the electronic device is connected to a docking hub. For example, the tablet device <NUM> may operate an event listener that detects that the tablet device <NUM> has been connected to or may be connected to the docking hub <NUM>. In response, the tablet device <NUM> and the docking hub <NUM> may form the pair connection <NUM> via the communication device <NUM> and the communication device <NUM>.

As described herein, in some embodiments, the security module <NUM> may permit the tablet device <NUM> to form the pair connection <NUM> based upon determining that the docking hub <NUM> is an authorized device. For instance, the docking hub docking hub <NUM> may send the device identifier <NUM> to the tablet device <NUM>. Upon receipt of the device identifier <NUM>, the security module <NUM> may determine whether the docking hub <NUM> is an authorized device based on the device identifier <NUM>. In some examples, the security module <NUM> may compare the device identifier <NUM> to a whitelist and/or blacklist of device identifiers. In some other examples, the security module <NUM> may evaluate whether device identifier <NUM> matches an expected format associated with valid device identifiers.

In some embodiments, the tablet device <NUM> may determine that a connection (e.g., a physical connection) exists or is available with the docking hub <NUM> prior to entering the secure payment mode. In some other embodiments, the tablet device <NUM> may determine that a connection (e.g., a physical connection) exists or is available with the docking hub <NUM> after entering the secure payment mode. For example, the docking hub <NUM> may receive the tablet device <NUM> after the tablet device <NUM> has entered the secure payment mode.

In <NUM>, the tablet device may permit the primary processor to access a peripheral device connected to the docking hub. For example, tablet device <NUM> may permit software programs executing on the primary processor <NUM> to send the graphical data <NUM> to the touch sensitive display <NUM> of the docking hub <NUM>. In some embodiments, the switching module <NUM> may route the graphical data <NUM> from the primary processor <NUM> to the communication device <NUM> for transmission to the touch sensitive display <NUM> via the pair connection <NUM> and the communication device <NUM>.

In some embodiments, the operating system <NUM> may identify a context of the normal operating mode determined prior to entering the secure payment mode. Further, the operating system <NUM> may restore the context via the primary processor <NUM> and the touch sensitive display <NUM>.

In <NUM>, the tablet device may receive, by the primary processor, user input from the peripheral device connected to the docking hub. For example, tablet device <NUM> may permit software programs executing on the primary processor <NUM> to receive the input data <NUM> from the touch sensitive display <NUM> of the docking hub <NUM>. In some embodiments, the switching module <NUM> may route the input data <NUM> to the primary processor <NUM> from the pair connection <NUM> via the communication device <NUM>.

<FIG> illustrate an example device <NUM> for implementing tablet mode switching, according to some embodiments. As illustrated in <FIG>, the electronic device <NUM> (e.g., the electronic device <NUM>) may include a primary operating system (OS) ecosystem <NUM> (e.g., the primary processor <NUM>, the operating system <NUM>, and the applications <NUM>(<NUM>)-(N)), a secure payment ecosystem <NUM> (e.g., the secure processor <NUM>, and the payment application <NUM>), a switching module <NUM> (e.g., the switching module <NUM>), and a touch sensitive display <NUM> (e.g., the touch sensitive display <NUM>).

Further, <FIG> illustrates the electronic device <NUM> in a normal operating mode wherein the switching module <NUM> routes operation data <NUM> between the primary OS ecosystem <NUM> and the touch sensitive display <NUM>. <FIG> illustrates the electronic device <NUM> in a secure payment mode wherein the switching module <NUM> routes payment data <NUM> between the secure payment ecosystem <NUM> and the touch sensitive display <NUM>. As described in detail herein, the components of the primary OS ecosystem <NUM> may be prevented from accessing the touch sensitive display <NUM> in the secure payment mode. In other words, access to the touch sensitive display <NUM> may be restricted to the components of the secure payment ecosystem <NUM>. Further, the switching module <NUM> may control whether the electronic device <NUM> is in the normal operating mode or the secure payment mode. In addition, when the electronic device <NUM> is in the secure payment mode, the primary OS ecosystem <NUM> may access a docking hub <NUM> or peripheral devices connected to the docking hub <NUM>, as further described herein.

Various embodiments may be implemented, for example, using one or more well-known computer systems, such as computer system <NUM> shown in <FIG>. One or more computer systems <NUM> may be used, for example, to implement any of the embodiments discussed herein, as well as combinations and sub-combinations thereof.

Computer system <NUM> may include one or more processors (also called central processing units, or CPUs), such as a processor <NUM>. Processor <NUM> may be connected to a communication infrastructure or bus <NUM>.

Computer system <NUM> may also include user input/output device(s) <NUM>, such as monitors, touch-sensitive displays, card reader devices, microphones, cameras, motion sensors, location sensors, NFC reader devices, keyboards, pointing devices, etc., which may communicate with communication infrastructure <NUM> through user input/output interface(s) <NUM>.

One or more of processors <NUM> may be a graphics processing unit (GPU). In an embodiment, a GPU may be a processor that is a specialized electronic circuit designed to process mathematically intensive applications. The GPU may have a parallel structure that is efficient for parallel processing of large blocks of data, such as mathematically intensive data common to computer graphics applications, images, videos, etc..

Computer system <NUM> may also include a main or primary memory <NUM>, such as random access memory (RAM). Main memory <NUM> may include one or more levels of cache. Main memory <NUM> may have stored therein control logic (i.e., computer software) and/or data.

Removable storage unit <NUM> may include a computer usable or readable storage device having stored thereon computer software (control logic) and/or data. Removable storage drive <NUM> may read from and/or write to removable storage unit <NUM>.

Secondary memory <NUM> may include other means, devices, components, instrumentalities or other approaches for allowing device applications and/or other instructions and/or data to be accessed by computer system <NUM>. Such means, devices, components, instrumentalities or other approaches may include, for example, a removable storage unit <NUM> and an interface <NUM>. Examples of the removable storage unit <NUM> and the interface <NUM> may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and/or any other removable storage unit and associated interface.

Communication interface <NUM> may enable computer system <NUM> to communicate and interact with any combination of external devices, external networks, external entities, etc. (individually and collectively referenced by reference number <NUM>). For example, communication interface <NUM> may allow computer system <NUM> to communicate with external or remote devices <NUM> over communications path <NUM>, which may be wired and/or wireless (or a combination thereof), and which may include any combination of LANs, WANs, the Internet, etc. Control logic and/or data may be transmitted to and from computer system <NUM> via communication path <NUM>.

Computer system <NUM> may also be any of a personal digital assistant (PDA), desktop workstation, laptop or notebook computer, netbook, tablet, smart phone, smart watch or other wearable, appliance, part of the Internet-of-Things, and/or embedded system, to name a few non-limiting examples, or any combination thereof.

Computer system <NUM> may be a client or server, accessing or hosting any applications and/or data through any delivery paradigm, including but not limited to remote or distributed cloud computing solutions; local or on-premises software ("on-premise" cloud-based solutions); "as a service" models (e.g., content as a service (CaaS), digital content as a service (DCaaS), software as a service (SaaS), managed software as a service (MSaaS), platform as a service (PaaS), desktop as a service (DaaS), framework as a service (FaaS), backend as a service (BaaS), mobile backend as a service (MBaaS), infrastructure as a service (IaaS), etc.); and/or a hybrid model including any combination of the foregoing examples or other services or delivery paradigms.

Any applicable data structures, file formats, and schemas in computer system <NUM> may be derived from standards including but not limited to JavaScript Object Notation (JSON), Extensible Markup Language (XML), Yet Another Markup Language (YAML), Extensible Hypertext Markup Language (XHTML), Wireless Markup Language (WML), MessagePack, XML User Interface Language (XUL), or any other functionally similar representations alone or in combination. Alternatively, proprietary data structures, formats or schemas may be used, either exclusively or in combination with known or open standards.

In some embodiments, a tangible, non-transitory apparatus or article of manufacture comprising a tangible, non-transitory computer useable or readable medium having control logic (software) stored thereon may also be referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system <NUM>, main memory <NUM>, secondary memory <NUM>, and removable storage units <NUM> and <NUM>, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system <NUM>), may cause such data processing devices to operate as described herein.

It is to be appreciated that the Detailed Description section, and not any other section, is intended to be used to interpret the claims. Other sections can set forth one or more but not all exemplary embodiments as contemplated by the inventor(s), and thus, are not intended to limit this disclosure or the appended claims in any way.

While this disclosure describes exemplary embodiments for exemplary fields and applications, it should be understood that the disclosure is not limited thereto. Other embodiments and modifications thereto are possible, and are within the scope of this disclosure. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and/or entities illustrated in the figures and/or described herein. Further, embodiments (whether or not explicitly described herein) have significant utility to fields and applications beyond the examples described herein.

Claim 1:
A method comprising:
entering, by an electronic device, a payment mode associated with a secure processor of the electronic device;
suspending access, for an application executing on a primary processor of the electronic device, to a component of the electronic device, wherein the component of the electronic device includes at least one of a display device or a user input device and wherein the payment mode comprises restricting access to the at least one of the display device or the user input device by a payment application executing on the secure processor;
determining that the electronic device is connected to a docking hub;
permitting the primary processor to access a peripheral device connected to the docking hub via a pair connection;
receiving, by the primary processor, user input from the peripheral device connected to the docking hub via the pair connection;
entering a normal operating mode associated with the primary processor based on completion of a step of a payment workflow associated with the payment mode; and
re-enabling access by the primary processor to the component of the electronic device.