SYSTEM ACCESS USING A MOBILE DEVICE
FIG2 is a block diagram illustrating an exemplary mobile device, according to some embodiments
The mobile device and system may include any suitable hardware to implement functionality described herein. Accordingly, this hardware may include a processor subsystem coupled to a system memory and I/O interfaces(s) or devices via an interconnect (e.g., a system bus). Although described as a mobile device, this device may be any of various types of devices, including, but not limited to, a server system, personal computer system, desktop computer, laptop or notebook computer, mainframe computer system, tablet computer, handheld computer, workstation, network computer, a consumer device such as a mobile phone, music player, or personal data assistant (PDA). The mobile device and/or system may also implement various functionality by executing program instructions embodied in a non-transitory computer readable medium. FIG2, described in further detail below, shows additional non-limiting examples of hardware embodiments. Turning now to FIG2, a block diagram of a mobile device 130 is depicted, according to some embodiments. Mobile device 130 may include wireless interface 132, SE 134, and biosensor 138. In the illustrated embodiments, mobile device 130 further includes a secure enclave processor (SEP) 210, cellular interface 220, CPU 230, memory 240, peripherals 250 coupled via a communication fabric 260. As shown, SEP 210 may include one or more processors P 212, a secure memory 214, and one or more security peripherals 216. SE 134 may include one or more processors P 222 and a memory 224. CPU 320 may include one or more processors P 232. Memory 240 may store an interface application 242. In some embodiments, mobile device 130 may be implemented differently than shown. Although FIG2 depicts components within mobile device 130, it is noted that similar components may exist in computer systems used to implement other functionality described herein such as functionality described with respect to system 110 or mobile device 160. Accordingly, these systems may also include CPUs, memory, various network interfaces, and peripherals such as those described above.
block diagram
242
application
228
as public-key information
226
applets
224
memory
214
memory
216
security peripherals
260
Communication fabric
220
cellular interface
250
Peripherals
134
SE
210
SEP
230
CPU
218
template templates
130
device
222
processor
2
ECP
232
processors
138
biosensor
240
memory
132
wireless interface
['4. The apparatus of claim 1, wherein, to share access to one or more functions of the system with another device, the apparatus is configured to: receive a certificate signing request from the other device; verify the received certificate using a root certificate of a an authorized entity associated with the other device; authenticate a user of the apparatus; sign the certificate using the private key of the apparatus established during the pairing session with the system; and transmit the signed certificate to the other device.']