Apple Ex. 1018
`Apple Inc. v. Firstface Co., Ltd.
`IPR2019-00614
`Page 00001
`
`

`

`peeeee. 106
`eM Carrier=
`
`160
`
`denenennee
`
`). 2
`
`110
`
`Patent Application Publication
`
`Apr. 4, 2013 Sheet 1 of 14
`
`US 2013/0082974 Al
`
`ra
`
`Seeeeee”
`
`186
`
`s,
`
`188
`
`12:34 PMPhotos leCamera3)
`
`.3 4 136a |
`
`43
`
`Weather
`140
`
`Maps
`144
`
`142
`
`:
`
`©
`
`150 152
`
`184
`
`104
`
`FIG. 1
`
`IPR2019-00614 Page 00002
`
`IPR2019-00614 Page 00002
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 2 of 14
`
`US 2013/0082974 Al
`
`-UON}e007
`
`paseg
`
`S0INeS
`
`
`
`@dIA8SBOIS@OlAI8S
`
`
`
`
`
`IPSN)Buibessoj;uoneBiaen
`
`
`
`YIOMJONPSYSPA
`
`812
`
`Ray
`CAS
`
`q00L
`
`0ee
`
`SSC
`
`0SOrz0€Z
`
`
`
`qua}uo0yJOYIO,
`
`
`
`(s)J84si|qnd(s)e01eg
`
`022092
`
`¢Old
`
`IPR2019-00614 Page 00003
`
`IPR2019-00614 Page 00003
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 3 of 14
`
`| geet Carrier
`&
`4:3
`
`Wednesday, April 20
`
`US 2013/0082974 Al
`
`IPR2019-00614 Page 00004
`
`IPR2019-00614 Page 00004
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 4 of 14
`
`US 2013/0082974 Al
`
`Enter Passcode
`
`LI
`
`Cancel
`
`2
`
`0
`
`8
`
`TUV
`
`WXYZ
`
`1
`
`4
`
`i
`
`PQRS
`
`Emergency
`
`IPR2019-00614 Page 00005
`
`IPR2019-00614 Page 00005
`
`

`

`420 7
`
`4:30
`
`Wednesday, April 20
`
`slide to unlock
`
`
`
`410a tb‘\S
`
`FIG. 4A
`
`IPR2019-00614 Page 00006
`
`Patent Application Publication
`
`Apr. 4, 2013 Sheet 5 of 14
`
`US 2013/0082974 Al
`
`400
`
`beeeeestOEE _—— _|Carrier =
`
`I|
`
`|I
`
`I|
`
`|I
`
`I|
`
`|I
`
`I|
`
`IPR2019-00614 Page 00006
`
`

`

`Apr. 4, 2013 Sheet 6 of 14
`
`410d
`
`Wednesday,April 20
`
`410a
`
`410b
`
`410c
`
`IPR2019-00614 Page 00007
`
`Patent Application Publication
`
`400
`
`US 2013/0082974 Al
`
`|__| 402
`|—“learier=
`4:30
`
`7 |||||I|I4 1 ||||4
`
`IPR2019-00614 Page 00007
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 7 of 14
`
`US 2013/0082974 Al
`
`510b
`
`500
`
`Lo| 502
`
`7 |||||||I4 1 |||I4
`
`FIG. 5A
`
`IPR2019-00614 Page 00008
`
`IPR2019-00614 Page 00008
`
`

`

`510¢
`
`510b
`
`FIG. 5B
`
`IPR2019-00614 Page 00009
`
`Patent Application Publication
`
`Apr. 4, 2013 Sheet 8 of 14
`
`US 2013/0082974 Al
`
`500
`
`KK [> pp
`
`7 |||||||I4 1 |||I4
`
`IPR2019-00614 Page 00009
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 9 of 14
`
`US 2013/0082974 Al
`
`600
`
`_—— |Carrier =
`
`-----a
`|
`lo
`om
`| e+e |
`|__| 602
`
`i
`4:30
`
`620~->-”
`
`Wednesday, April 20
`
`606
`
`slide to unlock
`
`c
`iC
`\
`610a 610b \.__
`
`IPR2019-00614 Page 00010
`
`I|
`
`|I
`
`I|
`
`|I
`
`I|
`
`|I
`
`I|
`
`|
`
`IPR2019-00614 Page 00010
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 10 of 14
`
`US 2013/0082974 Al
`
`600
`
`|1602
`
`_—— _|Carrier =
`
`fg)
`4:30
`
`Wednesday,April 20
`
`608
`
`630a 630b \.. _” 630c 630d
`
`610a
`
`610d
`
`re
`
`iC
`
`i ‘
`
`620~->-”
`
`FIG. 6B
`
`IPR2019-00614 Page 00011
`
`IPR2019-00614 Page 00011
`
`

`

`620-7)
`
`Patent Application Publication
`
`Apr. 4, 2013 Sheet 11 of 14
`
`US 2013/0082974 Al
`
`600
`
`Wednesday,April 20
`
`7 |||||||I4 1 |||I4
`
`610a
`
` 610b
`
`610c
`
`610d
`
`630a
`
`630b 630 630d
`
`FIG. 6C
`
`IPR2019-00614 Page 00012
`
`IPR2019-00614 Page 00012
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 12 of 14
`
`US 2013/0082974 Al
`
`Wednesday,April 20
`
`tl! el Carrier <=4:30
`
`FIG. 7
`
`IPR2019-00614 Page 00013
`
`IPR2019-00614 Page 00013
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 13 of 14
`
`US 2013/0082974 Al
`
`800
`
`\
`
`Enforcing a security wall with respect to
`
`applications on a computer, wherein
`enforcing the security wall includes
`preventing accessto the applications until
`a security input is received
`
`receiving the security input from the user
`
`Receiving a predefined input through a
`home button on a touch-sensitive display
`of the computer
`
`Providing access to a particular
`application in responseto receiving the
`predefined input by allowing a user to
`accessthe particular application without
`
`FIG. 8
`
`IPR2019-00614 Page 00014
`
`IPR2019-00614 Page 00014
`
`

`

`Patent Application Publication
`
`Apr. 4, 2013 Sheet 14 of 14
`
`US 2013/0082974 Al
`
`perating System Instructions
`
`ensor Processing Instructions
`honeInstructions
`lectronic Messaging Instructions
`Web Browsing Instructions
`Media Processing Instructions
`PS/Navigation
`Instructi
`
`Other SoftwareInstructions
`Security Instructions
`
`*
`
`“
`
`958
`960
`962
`964
`966
`o¢8
`70
`
`1
`974
`
`grocesceesecsecesceeeceetcen;
`Positioning System
`Hoonnanenccenecosncenccesccos/
`
`Other Sensor(s)
`
`Light Sensor
`
`sesseesssssesseefunsecesseesnsesseenesessesssnaferleefaefeeee
`
`MemoryInterface
`
`906
`
`Camera
`Subsystem
`
`i
`
`924 Subsystem(s)
`Wireless
`Communication
`Audio Subsystem | 930
`+>}
`ee 926
`©
`
`918
`
`916
`
`910
`
`912
`
`914
`
`920
`
`922
`
`928
`
`ommunication Instructions UIInstructions
`Processor(s)
`
`
`: 902
`
`904
`
`Peripherals
`terface
`
`|
`i»!
`
`9
`
`42
`
`1/0 Subsystem
`
`944
`
`Touch-Screen Controller
`
`OtherInput Controller
`
`(8)
`
`946
`
`Devices
`
`04g
`
`FIG. 9
`
`940
`
`IPR2019-00614 Page 00015
`
`IPR2019-00614 Page 00015
`
`

`

`US 2013/0082974 Al
`
`Apr. 4, 2013
`
`QUICK ACCESS USER INTERFACE
`
`TECHNICAL FIELD
`
`[0001] This disclosure relates generally to providing quick
`access to applications on a computing device.
`
`BACKGROUND
`
`[0002] Computing devices often implement security mea-
`sures to prevent unwanted or accidental access to applica-
`tions, features, or information provided by the computing
`devices. Computing devices frequently store sensitive infor-
`mation that a user may not want other users to view. Users
`mayalso generally wantto restrict access to their computing
`devices by other users as a matter of personal preference.
`Example security measures implemented on computing
`devices to prevent unwanted access include enforcing a secu-
`rity wall to prevent access to applications on the computing
`device unless a particular security input is received. Typically,
`a security code, password, or particular sequence of other
`inputs is required as a security input to access applications on
`a computing device when a security wall is implemented on
`the device.
`
`[0003] Although enforcementof the security wall restricts
`unwanted access to applications on a computing device, the
`security wall also prevents the ownerofthe computing device
`from easily accessing applications on the computing device.
`In someinstances, the user attempting to access the comput-
`ing device is the owner of the computing device or an autho-
`rized user. Further, some applications on the computing
`device may be associated with private information while
`other applications havelittle or no private aspect.
`
`SUMMARY
`
`In a first general aspect, a method for providing
`[0004]
`quick access to applications on a computing device is dis-
`closed. A security wall is enforced with respect to applica-
`tions on the computer, wherein enforcing the security wall
`includes preventing access to the applications until a security
`input is received. A predefined input is received through a
`home button on a touch-sensitive display of the computer.
`Access is provided to a particular application in response to
`receiving the predefined input, wherein providing access to
`the particular application includes allowing a user to access
`the particular application without receiving the security input
`from the user.
`
`Implementations can include any orall of the fol-
`[0005]
`lowing features. The homebutton includes a portion of the
`touch-sensitive display having both touch-sensitive andpres-
`sure-sensitive properties. The method further comprises
`receiving a second instance of the predefined input through
`the homebutton andproviding access to a second application
`concurrently with providing access to the particular applica-
`tion, wherein providing access to the second application
`includes allowing a user to access the second application
`without receiving the security input from the user. The pre-
`defined input includes a first upward motion of a user in
`contact with the homebutton and a second upward motion of
`the user in contact with the home button within a particular
`amount oftime. Providing accessto the particular application
`includes generating for display a visual object representing
`the particular application on the touch-sensitive display,
`wherein the visual object is displayed concurrently with a
`second visual object for bypassing the security wall. Provid-
`
`ing access to the particular application includes allowing the
`user to accessa first portion ofthe particular application while
`the security wall is enforced with respect to a remaining
`portion ofthe particular application.
`[0006] The particular application includesat least one of a
`camera application, a remote controller for multimedia player
`application, a calculator application, a media player applica-
`tion, or a voice control application. The method further com-
`prises receiving a second predefined input through the home
`button and presenting a login pagefortraversing the security
`wall. Enforcing the security wall occurs after the computer
`has concludeda full boot sequence. The method further com-
`prises automatically waking the computer from a sleep mode
`in responseto receiving the predefined input.
`[0007]
`In a second general aspect, a computer program
`productis tangibly embodied in a computer-readable storage
`medium and includes instructions that, when executed,
`enforce a security wall with respect to applications on the
`computer, wherein enforcing the security wall includes pre-
`venting access to the applications until a security input is
`received. A predefined input is received through a homebut-
`ton on the computer having multi-touch sensitivity. Access is
`providedto a particular application in response to receiving
`the predefined input, wherein providing accessto the particu-
`lar application includes allowing a user to access the particu-
`lar application without receiving the security input from the
`user.
`
`Implementations can include anyorall of the fol-
`[0008]
`lowing features. The homebutton includesa region of a touch
`screen of the computer having multi-touch sensitivity, the
`region of the touch screen separate from a touch-sensitive
`display of the computer. Providing access to the particular
`application includes generating for display a visual object
`representing the particular application on the touch-sensitive
`display and hiding a second visual object for bypassing the
`security wall. Providing access to the particular application
`includes allowing the user to access a first portion of the
`particular application while the security wall is enforced with
`respect to a remaining portion of the particular application.
`The particular application includes at least one of a camera
`application, a remote controller for multimedia player appli-
`cation, a calculator application, a media player application, or
`a voice control application. The operations further include
`automatically waking the computer from a sleep mode in
`responseto receiving the predefined input.
`[0009] The details of one or more implementations of the
`subject matter described in this specification are set forth in
`the accompanying drawingsandthe description below. Other
`features, aspects, and advantages of the subject matter will
`become apparent from the description, the drawings, and the
`claims.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0010]
`device.
`
`FIG. 1 is a block diagram of an example mobile
`
`FIG. 2 is a block diagram of an example network
`[0011]
`operating environmentfor the mobile device of FIG.1.
`[0012]
`FIGS. 3A-3B are block diagrams of an example
`implementation ofthe mobile device of FIG. 1 with a security
`wall in standby mode.
`[0013]
`FIGS. 4A-4B are block diagrams of an example
`implementation of the mobile device of FIG. 1 in a quick
`access mode.
`
`IPR2019-00614 Page 00016
`
`IPR2019-00614 Page 00016
`
`

`

`US 2013/0082974 Al
`
`Apr. 4, 2013
`
`FIGS. 5A-5B are block diagrams of an example
`[0014]
`implementation of the mobile device of FIG. 1 in a quick
`access mode.
`
`FIGS. 6A-6C are block diagrams of an example
`[0015]
`implementation of the mobile device of FIG. 1 in a quick
`access mode.
`
`FIG. 7 is a block diagram of an example implemen-
`[0016]
`tation of the mobile device of FIG. 1 in a quick access mode.
`[0017]
`FIG. 8 is a flow diagram illustrating an example
`process for providing quick access to applications on a com-
`puting device.
`[0018]
`FIG. 9 is a block diagram of exemplary hardware
`architecture for implementing the user interfaces and pro-
`cesses described in reference to FIGS. 1-8.
`
`[0019] Like reference numbers and designations in the
`various drawings indicate like elements.
`
`DETAILED DESCRIPTION
`
`[0020] A computing device can implementa security wall
`to prohibit unwanted users from accessing functionality pro-
`vided by the computing device. Instead of applying the secu-
`rity wall to all functionality of the computing device, the
`computing device can allow user accessto functionality when
`a specific input is received at the computing device. Accord-
`ingly, a security input that is normally required to bypass the
`security wall is not required for access to certain applications
`on the computing device. The applications that do not require
`the usual security input may be grouped and presented in a
`cluster of visual objects in responseto a specific input from a
`user.
`
`FIG. 1 is a block diagram of an example mobile
`[0021]
`device 100. The mobile device 100 can be, for example, a
`handheld computer, a personal digital assistant, a cellular
`telephone, a network appliance, a camera, a smart phone, an
`enhanced general packet radio service (EGPRS) mobile
`phone, a network base station, a media player, a navigation
`device, an email device, a game console, or other electronic
`device or a combination of any two or more of these data
`processing devices or other data processing devices.
`Although the description below refers generally to mobile
`device 100, any computing device, including a personal com-
`puter, laptop, or tablet, may be used in accordance with the
`features described in the present disclosure.
`
`Mobile Device Overview
`
`In some implementations, the mobile device 100
`[0022]
`includes a touch-sensitive display 102. The touch-sensitive
`display 102 can implementliquid crystal display (LCD) tech-
`nology, light emitting polymerdisplay (LPD) technology, or
`some other display technology. The touch-sensitive display
`102 can be sensitive to haptic and/or tactile contact with a
`user.
`
`In some implementations, the touch-sensitive dis-
`[0023]
`play 102 can comprise a multi-touch-sensitive display 102.A
`multi-touch-sensitive display 102 can, for example, process
`multiple simultaneous touch points,
`including processing
`data related to the pressure, degree and/or position of each
`touch point. Such processing facilitates gestures and interac-
`tions with multiple fingers, chording, and otherinteractions.
`Other touch-sensitive display technologies can also be used,
`e.g., a display in which contact is made using a stylus or other
`pointing device. An example of a multi-touch-sensitive dis-
`play technology is described in U.S. Pat. Nos. 6,323,846;
`
`6,570,557; 6,677,932; and U.S. Patent Publication No. 2002/
`0015024A1, each of which is incorporated by reference
`herein in its entirety.
`[0024]
`In some implementations, the mobile device 100
`can display one or more graphical user interfaces on the
`touch-sensitive display 102 for providing the user access to
`various system objects and for conveying information to the
`user. In some implementations, the graphical user interface
`can include one or more display objects 104, 106. Each ofthe
`display objects 104, 106 can be a graphic representation of a
`system object. Some examples of system objects include
`device functions, applications, windows,files, alerts, events,
`or other identifiable system objects.
`
`Example Mobile Device Functionality
`
`In some implementations, the mobile device 100
`[0025]
`can implement multiple device functionalities, such as a tele-
`phonydevice, as indicated by a phone object 110; an e-mail
`device, as indicated by the e-mail object 112; a network data
`communication device, as indicated by the Web object 114; a
`Wi-Fi base station device (not shown); and a media process-
`ing device, as indicated by the media player object 116. In
`some implementations, particular device objects 104,e.g., the
`phone object 110, the e-mail object 112, the Web object 114,
`and the media player object 116, can be displayed in a menu
`bar 118. In some implementations, each of the device func-
`tionalities can be accessed from a top-level graphical user
`interface, such as the graphical user interface illustrated in
`FIG. 1. The objects 110, 112, 114 and 116 represent visual
`indicators of applications on the mobile device 100. Touching
`one of the objects 110, 112, 114 or 116 can, for example,
`invoke the corresponding functionality.
`[0026]
`In some implementations, the mobile device 100
`can implement network distribution functionality. For
`example, the functionality can enable the user to take the
`mobile device 100 and its associated network while traveling.
`In particular,
`the mobile device 100 can extend Internet
`access (e.g., via Wi-Fi) to other wireless devices in the vicin-
`ity. For example, mobile device 100 can be configured as a
`base station for one or more devices. As such, mobile device
`100 can grant or deny network access to other wireless
`devices.
`
`In some implementations, upon invocation of par-
`[0027]
`ticular device functionality, the graphical userinterface of the
`mobile device 100 changes, or is augmentedor replaced with
`anotheruser interface or user interface elements,to facilitate
`user access to particular functions associated with the corre-
`sponding device functionality. For example, in response to a
`user touching the phone object 110, the graphical user inter-
`face of the touch-sensitive display 102 may present display
`objects related to various phone functions; likewise, touching
`ofthe email object 112 may cause the graphicaluser interface
`to present display objects related to various email functions;
`touching the Web object 114 may cause the graphical user
`interface to present display objects related to various Web-
`surfing functions; and touching the media player object 116
`may cause the graphical user interface to present display
`objects related to various media processing functions.
`[0028]
`In some implementations, the top-level graphical
`userinterface environmentor state of FIG. 1 can be restored
`
`by pressing a home button 120 located near the bottom of the
`mobile device 100. The home button 120 may be a hardware
`tactile button that can be depressed physically such that the
`homebutton 120 undergoes motion without movingthe sur-
`IPR2019-00614 Page 00017
`
`IPR2019-00614 Page 00017
`
`

`

`US 2013/0082974 Al
`
`Apr. 4, 2013
`
`rounding region or touch-sensitive display 102. In some
`implementations, the home button 120 may include multi-
`touch capabilities similar to the multi-touch-sensitive display
`102. Alternatively, the home button 120 may be a “virtual”
`button thatis built into a screen ofthe mobile device 100, such
`as immediately below the touch-sensitive display 102. Fur-
`ther, in some implementations, the touch-sensitive display
`102 may extend to the bottom of the mobile device 100 to
`encompass the homebutton 120 so that a specific region ofthe
`touch-sensitive display 102 comprises the home button 120.
`A user’s contact with the specific region maytrigger various
`responsesin the mobile device 100 depending on the motion
`or amountofpressure ofthe contact. A home button 120 with
`multi-touch capabilities may process multiple simultaneous
`touch points, including processing data related to the pres-
`sure, degree and/or position of each touch point. Such pro-
`cessing mayfacilitate gestures and interactions with multiple
`fingers, chording, and other interactions or touch-sensitive
`display technologies. In some instances, the region of the
`touch-sensitive display 102 comprising the virtual home but-
`ton 120 may provide a certain level of feedback or resistance
`to simulate a physical tactile button. The virtual home button
`120 may not be visible, but in certain implementations, a
`visual indicator may highlight the region comprising the
`homebutton 120, such as a lighted area ofthe touch-sensitive
`display 102 within the vicinity of the home button 120. In
`some implementations, each corresponding device function-
`ality may have corresponding “home” display objects dis-
`played on the touch-sensitive display 102, and the graphical
`userinterface environment of FIG. 1 can be restored by press-
`ing the “home”display object.
`[0029]
`In some implementations, the top-level graphical
`user interface can include additional display objects 106, such
`as a short messaging service (SMS) object 130, a calendar
`object 132, a photos object 134, a camera object 136, a cal-
`culator object 138, a stocks object 140, a weather object 142,
`a maps object 144, a notes object 146, a clock object 148, an
`address book object 150, and a settings object 152. Touching
`the SMSdisplay object 130 can, for example, invoke an SMS
`messaging environment and supporting functionality. Like-
`wise, each selection of a display object 132, 134, 136, 138,
`140, 142, 144, 146, 148, 150 and 152 can invoke a corre-
`sponding object environmentand functionality.
`[0030] Additional and/ordifferent display objects can also
`be displayed in the graphical user interface of FIG. 1. For
`example, if the device 100 is functioning as a base station for
`other devices, one or more “connection” objects may appear
`in the graphical user interface to indicate the connection. In
`some implementations, the display objects 106 can be con-
`figured by a user, e.g., a user may specify which display
`objects 106 are displayed, and/or may download additional
`applications or other software that provides other functional-
`ities and corresponding display objects.
`[0031]
`In some implementations, the mobile device 100
`can include one or more input/output (J/O) devices and/or
`sensor devices. For example, a speaker 160 anda microphone
`162 can be included to facilitate voice-enabled functional-
`
`ities, such as phoneand voice mail functions. In some imple-
`mentations, a loud speaker 164 can be includedto facilitate
`hands-free voice functionalities, such as speaker phone func-
`tions. An audio jack 166 can also be included for use of
`headphonesand/or a microphone.
`[0032]
`In some implementations, a proximity sensor 168
`can be includedto facilitate the detection ofthe user position-
`
`ing the mobile device 100 proximateto the user’s ear and, in
`response, to disengage the touch-sensitive display 102 to
`prevent accidental function invocations. In some implemen-
`tations, the touch-sensitive display 102 can be turned off to
`conserve additional power when the mobile device 100 is
`proximateto the user’s ear.
`[0033] Other sensors can also be used. For example, in
`some implementations, an ambient light sensor 170 can be
`utilized to facilitate adjusting the brightness of the touch-
`sensitive display 102. In some implementations, an acceler-
`ometer 172 can be utilized to detect movement of the mobile
`
`device 100, as indicated by the directional arrow 174. Accord-
`ingly, display objects and/or media can be presented accord-
`ing to a detected orientation, e.g., portrait or landscape. In
`some implementations, the mobile device 100 may include
`circuitry and sensors for supporting a location determining
`capability, such as that provided by the global positioning
`system (GPS)or otherpositioning system (e.g., systems using
`Wi-Fi access points, television signals, cellular grids, Uni-
`form Resource Locators (URLs)). In some implementations,
`a positioning system (e.g., a GPS receiver) can be integrated
`into the mobile device 100 or provided as a separate device
`that can be coupled to the mobile device 100 through an
`interface (e.g., port device 190) to provide access to location-
`based services.
`
`[0034] The mobile device 100 can also include a camera
`lens and sensor 180. In some implementations, the camera
`lens and sensor 180 can be located on the back surface of the
`
`mobile device 100. The camera can capture still images and/
`or video.
`
`[0035] The mobile device 100 can also include one or more
`wireless communication subsystems, such as a 802.11b/g
`communication device 186, and/or a Bluetooth™ communi-
`cation device 188. Other communication protocols can also
`be supported, including other 802.x communication proto-
`cols (e.g., WiMax, Wi-Fi), code division multiple access
`(CDMA), global system for mobile communications (GSM),
`Enhanced Data GSM Environment (EDGE), 3G (e.g., EV-
`DO, UMTS, HSDPA), etc.
`[0036]
`In some implementations, a port device 190, e.g., a
`Universal Serial Bus (USB)port, or a docking port, or some
`other wired port connection, can be included. Theport device
`190 can, for example, be utilized to establish a wired connec-
`tion to other computing devices, such as other communica-
`tion devices 100, a personal computer, a printer, or other
`processing devices capable of receiving and/or transmitting
`data. In some implementations, the port device 190 allows the
`mobile device 100 to synchronize with a host device using
`one or more protocols.
`
`Network Operating Environment
`
`FIG. 2 is a block diagram of an example network
`[0037]
`operating environment200 for the mobile device 100 of FIG.
`1. The mobile device 100 of FIG. 1 can, for example, com-
`municate over one or more wired and/or wireless networks
`210 in data communication. For example, a wireless network
`212, e.g., a cellular network, can communicate with a wide
`area network (WAN)214, such as the Internet, by use of a
`gateway 216. Likewise, an access point 218, such as an 802.
`11g wireless access point, can provide communication access
`to the wide area network 214. In some implementations, both
`voice and data communications can be established over the
`wireless network 212 and the access point 218. For example,
`the mobile device 100a@ can place and receive phonecalls
`IPR2019-00614 Page 00018
`
`IPR2019-00614 Page 00018
`
`

`

`US 2013/0082974 Al
`
`Apr. 4, 2013
`
`(e.g., using VoIP protocols), send and receive email messages
`(e.g., using POP3 protocol), and retrieve electronic docu-
`ments and/or streams, such as web pages, photographs, and
`videos, over the wireless network 212, gateway 216, and wide
`area network 214 (e.g., using TCP/IP or UDP protocols).
`Likewise, the mobile device 1005 can place and receive
`phonecalls, send and receive e-mail messages, and retrieve
`electronic documents over the access point 218 and the wide
`area network 214. In some implementations,
`the mobile
`device 100 can be physically connected to the access point
`218 using one or more cables and the access point 218 can be
`a personal computer. In this configuration, the mobile device
`100 can be referred to as a “tethered” device.
`
`[0038] The mobile devices 100a and 1006 can also estab-
`lish communications by other means. For example, the wire-
`less device 100a can communicate with other wireless
`
`devices, e.g., other wireless devices 100, cell phones, etc.,
`over the wireless network 212. Likewise, the mobile devices
`100a and 1008 can establish peer-to-peer communications
`220, e.g., a personal area network, by use of one or more
`communication subsystems, such as the Bluetooth™ com-
`munication device 188 shown in FIG. 1. Other communica-
`tion protocols and topologies can also be implemented.
`[0039] The mobile device 100 can, for example, communi-
`cate with one or more services 230, 240, 250, 255, and 260
`and/or one or more content publishers 270 over the one or
`more wired and/or wireless networks 210. For example, a
`navigation service 230 can provide navigation information,
`e.g., map information, location information, route informa-
`tion, and other information, to the mobile device 100. In the
`example shown, a user ofthe mobile device 1005 has invoked
`amap functionality, e.g., by touching the maps object 144 on
`the top-level graphical user interface shown in FIG. 1, andhas
`requested and received a map for the location “1 Infinite
`Loop, Cupertino, Calif?”
`[0040] A messaging service 240 can, for example, provide
`e-mail and/or other messaging services. A media service 250
`can, for example, provide access to mediafiles, such as song
`files, movie files, video clips, and other media data. A loca-
`tion-based service 255 can, for example, provide data or
`content based on a current location of the mobile device 100.
`One or more other services 260 can also be utilized by the
`mobile device 100, including a syncing service, an activation
`service and a software update service that automatically
`determines whether software updates are available for soft-
`ware on the mobile device 100, then downloads the software
`updates to the mobile device 100 where the updates can be
`manually or automatically unpacked and/orinstalled.
`[0041] The mobile device 100 can also access other data
`over the one or more wired and/or wireless networks 210. For
`example, content publishers 270, such as newssites, RSS
`feeds, web sites, blogs, social networking sites, developer
`networks, etc., can be accessed by the mobile device 100.
`Such access can be provided by invocation of a web browsing
`function or application (e.g., a browser) in response to a user
`touching the Web object 114.
`
`Exemplary Display of Applications
`
`FIGS. 3A-3B depict example displays of enforcing
`[0042]
`a security wall on a computing device. Computing devices
`generally can be configured to implementa security wall to
`restrict unwanted or accidental access to functionality pro-
`vided by the computing devices. FIG. 3A illustrates imple-
`mentation of an example security measure for restricting
`
`access to applications on a mobile device 300. The mobile
`device 300 can enter a “stand-by” or “locked” mode as
`depicted in FIG. 3A. In a stand-by mode, mobile device 300
`can enforce a security wall to prohibit access to functionality,
`applications, and information usually provided by the mobile
`device 300. In someinstances, limited features can be pre-
`sented during a stand-by modeofthe mobile device 300, such
`as a current time and date, an indicator of remaining battery
`life, or a cellular reception signal strength. The remaining
`functionality provided by mobile device 300, however, can be
`restricted until a security input is received by the mobile
`device 300.
`
`[0043] Mobile device 300 can require different security
`inputs before a user is given access to functionality of the
`mobile device 300. In FIG. 3A, a sliding motion performed by
`a user in contact with the touch-sensitive display 302 can
`trigger unlocking of the mobile device 300. For example, the
`user may perform a sliding motion in a particular direction on
`a certain slider region 304 of the touch-sensitive display 302
`to unlock the mobile device 300. In general, the requiring of
`the sliding motion input prevents accidental unlocking of the
`mobile device 300. A different input can also be required to
`unlock the mobile device 300, such as entering a security code
`on the touch-sensitive display 302, as depicted in FIG. 3B. As
`seen in FIG. 3B, a screen for entering the security code is
`presented on the touch-sensitive display 302 before a useris
`allowed to unlock and access applications on the mobile
`device 300. This prevents users who do not have permission
`to access applications on the mobile device 300 from gaining
`access to applications.
`[0044]
`In some instances, the home button on a mobile
`device is used to allow immediate or quick access to certain
`applications on the mobile device without input of a security
`code. FIGS. 4A-4B illustrate example displays of quickly
`accessing certain applications on a mobile device 400 through
`ahomebutton 420 on the mobile device 400. Initially, a slider
`region 404 is present on the touch-sensitive display 402 to
`require a sliding motion input for preventing accidental
`unlocking of the mobile device 400. A user may perform a
`sliding motion in the slider region 404 to unlock the mobile
`device 400 orto bring up a security screen, similar to FIG. 3B,
`for inputting a security code. Alternatively, the user may
`bypass the sliding input or security screen by entering a
`predefined input using the home button 420 to enter a “quick
`access” mode of the mobile device 400 in which certain
`applications may be immediately available to the user, regard-
`less of whether a security wall may be enforced with respect
`to applications on the mobile device 400. In some implemen-
`tations, for example, touching the home button 420 may
`trigger an animationto transition visual objects 410 onto the
`touch-sensitive display 102. Each of the visual objects may
`representan application available to the user without entering
`the sliding motion in theslider region 404 or a security code.
`As seen in FIG. 4A, the visual objects 410 may initially be
`hidden from view. As the visual objects 410 are transitioned
`onto the touch-sensitive display 402, they may appear from
`below the slider region 404as if theyare initially located just
`below the visible area of the touch-sensitive display 402, as
`seen in FIG. 4A. As the objects 410 moveup onto the display
`402