Apple Inc. v. Smith Interface Techs., LLC
`IPR2024-01090 | Smith EX2011 | Page 1 of 275
`
`

`

`patent" and doesnoteliminate the needof applicantsto file additional documents and fees in countries where patent
`protection is desired.
`
`Almost every country has its own patent law, and a person desiring a patent in a particular country must make an
`application for patent in that country in accordancewith its particular laws. Since the laws of many countries differ
`in various respects from the patent law of the United States, applicants are advised to seek guidance from specific
`foreign countries to ensure that patent rights are not lost prematurely.
`
`Applicants also are advised that in the case of inventions madein the United States, the Director of the USPTO must
`issue a license before applicants can apply for a patent in a foreign country. Thefiling of a U.S. patent application
`serves as a request for a foreign filing license. The application's filing receipt contains further information and
`guidance asto the status of applicant's license for foreign filing.
`
`Applicants may wish to consult the USPTO booklet, "General Information Concerning Patents”(specifically, the
`section entitled "Treaties and Foreign Patents") for more information on timeframes and deadlinesfor filing foreign
`patent applications. The guide is available either by contacting the USPTO Contact Center at 800-786-9199, or it
`can be viewed on the USPTO website at http://“www.uspto.gov/web/offices/pac/doc/general/index.html.
`
`For information on preventing theft of your intellectual property (patents, trademarks and copyrights), you may wish
`to consult the U.S. Government website, http:/Avww.stopfakes.gov. Part of a Department of Commerceinitiative,
`this website includes self-help "toolkits" giving innovators guidance on how to protectintellectual property in specific
`countries such as China, Korea and Mexico. For questions regarding patent enforcementissues, applicants may
`call the U.S. Governmenthotline at 1-866-999-HALT (1-866-999-4158).
`
`LICENSE FOR FOREIGN FILING UNDER
`
`Title 35, United States Code, Section 184
`
`Title 37, Code of Federal Regulations, 5.11 & 5.15
`
`GRANTED
`
`if the phrase "IF REQUIRED, FOREIGN FILING
`The applicant has been granted a license under 35 U.S.C. 184,
`LICENSE GRANTED"followed by a date appears on this form. Such licenses are issuedin all applications where
`the conditions for issuance of a license have been met, regardless of whether or not a license may be required as
`set forth in 37 CFR 5.15. The scope andlimitations of this license are set forth in 37 CFR 5.15(a) unless an earlier
`license has been issued under 37 CFR 5.15(b). The license is subject to revocation upon written notification. The
`date indicatedis the effective date of the license, unless an earlier license of similar scope has been granted under
`37 CFR 5.13 or 5.14.
`
`This licenseis to be retained by the licensee and maybe usedat any time onor after the effective date thereof unless
`it is revoked. This license is automatically transferred to any related applications(s) filed under 37 CFR 1.53(d). This
`license is not retroactive.
`
`The grantof a license doesnot in any way lessen the responsibility of a licensee for the security of the subject matter
`as imposed by any Governmentcontract or the provisions of existing laws relating to espionage and the national
`security or the export of technical data. Licensees should apprise themselvesof current regulations especially with
`respect to certain countries, of other agencies, particularly the Office of Defense Trade Controls, Department of
`State (with respect to Arms, Munitions and Implements of War (22 CFR 121-128)); the Bureau of Industry and
`page 2 of 3
`
`Page 2 of 275
`
`Page 2 of 275
`
`

`

`Security, Department of Commerce (15 CFR parts 730-774); the Office of Foreign AssetsControl, Department of
`Treasury (31 CFR Parts 500+) and the Department of Energy.
`
`NOT GRANTED
`
`No license under 35 U.S.C. 184 has been granted at this time, if the phrase "IF REQUIRED, FOREIGN FILING
`LICENSE GRANTED" DOESNOTappear on this form. Applicant maystill petition for a license under 37 CFR 5.12,
`if a license is desired before the expiration of 6 months from thefiling date of the application. If 6 months has lapsed
`from thefiling date of this application and the licensee has not received any indication of a secrecy order under 35
`U.S.C. 181, the licensee mayforeign file the application pursuant to 37 CFR 5.15(b).
`
`
`SelectUSA
`
`The United States represents the largest, most dynamic marketplace in the world and is an unparalleled location
`for business investment, innovation and commercialization of new technologies. The USAoffers tremendous
`resources and advantagesfor those who invest and manufacture goods here. Through SelectUSA, our nation
`works to encourage, facilitate, and accelerate business investment. To learn more about why the USAis the best
`country in the world to develop technology, manufacture products, and grow your business, visit SelectUSA.gov.
`
`page 3 of 3
`
`Page 3 of 275
`
`Page 3 of 275
`
`

`

`
`
`InternationalApplication Number: Pe
`
`
`
`
`
`
`
`USER INTERFACE SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT
`
` Title of Invention:
`
`
`
`Paes
`
`ant date: O1/11/2012 UEDUVIJE
`O12 INTEFSW 00001746 304964
`250.00 CR
`620.00 CR
`
`61581918
`
`310.00 DA
`
`First Named Inventor/Applicant Name:
`
`
`
`
`
`
`
`
`Attorney Docket Number:
`
`|
`
`SMITHO70+
`
`Application Type:
`
`Paymentinformation:
`
`Submitted with Payment
`
`Paymentwassuccessfully received in RAM
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 4 of 275
`
`Pages
`Multi
`File Size(Bytes)/
`t Description
`D
`Document
`
`
`
`Number Message Digest|Part/.zip|ocumen P (if appl.)
`
`
`
`
`
`Page 4 of 275
`
`

`

`PTO/SB/14 (11-08)
`Approved for use through 09/30/2010. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`document maybe printed and included in a paper filed application.
`
`Application Data Sheet 37 CFR 1.76
`
`—
`
`Title of Invention
`
`USER INTERFACE SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT
`
`The application data sheetis part of the provisional or nonprovisional application for whichit is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`
`Secrecy Order 37 CFR 5.2
`
`[_] Portions or all of the application associated with this Application Data Sheet mayfall under a Secrecy Order pursuant to 37 CFR 5.2 (Paper filers only. Applications that fall under Secrecy Order may notbefiled electronically.)
`
`Applicant Information:
`
`Applicant 1
`Applicant Authority ®!nventor|CQlLegal Representative under 35 U.S.C. 117 C©Party ofInterest under 35 U.S.C. 118
`
`PrefixGivenName Middle Name
`Family Name
`Suffix
`
`(©) Active US Military Service
`(© NonUS Residency
`Residence Information (Select One) @ US Residency
`
`City|Palo Alto Country of Residencd|USState/Province
`
`
`Mailing Address of Applicant:
`
`PPesticode[C*omyJS
`All
`Inventors Must Be Listed - Additional
`Inventor
`Information blocks may be
`generated within this form by selecting the Add button.
`
`CorrespondenceInformation:
`
`Enter either Customer Number or complete the Correspondence Information section below.
`For further information see 37 CFR 1.33(a).
`
`[_] An Addressis being provided for the correspondenceInformation of this application.
`
`Customer Number
`
`92045
`
`Email Address
`
`pcaldwell@thecaldwellfirm.com
`
`:
`
`Application Information:
`
`Application Type
`
`E
`
`
`Suggested Technology Center(if any) Pe
`
`
`
`
`Total Numberof Drawing Sheets(if any)|«|SuggestedFigureforPublication(ifany)|__|
`
`0
`
`EFS Web 2.2.2
`
`Page 5 of 275
`
`

`

`PTO/SB/14 (11-08)
`Approved for use through 09/30/2010. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`USER INTERFACE SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT
`
`Publication Information:
`
`[_] Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`
`Request Not to Publish. | hereby requestthat the attached application not be published under 35 U.S.
`C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the subject of
`an application filed in another country, or under a multilateral international agreement, that requires publication at
`
`— Title of Invention
`eighteen months after filing.
`92045
`by selecting the Add button.
`Add button.
`
`Foreign Priority Information:
`This section allows for the applicant to claim benefit of foreign priority and to identify any prior foreign application for which priority is
`not claimed. Providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b)
`and 37 CFR 1.55(a).
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32).
`
`
`
`
`
`Enter the Representative Name_sectioneither Customer Number or complete below. If both sections
`
`
`are completed the Customer Numberwill be used for the Representative Information during processing.
`
`
`
`Please Select One: © US Patent Practitioner|©) Limited Recognition (37 CFR 11.9)(@) Customer Number
`
`Customer Number
`
`
`
`Domestic Benefit/National Stage Information:
`This section allows for the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c) or indicate National Stage
`entry from a PCT application. Providing this information in the application data sheet constitutes the specific reference required by
`35 U.S.C. 119(e) or 120, and 37 CFR 1.78(a)(2) or CFR 1.78(a)(4), and need not otherwise be made part of the specification.
`
`Application Number
`
`Continuity Type
`
`Prior Application Number
`
`Filing Date (YYYY-MM-DD)
`
`a A
`
`dditional Domestic Benefit/National Stage Data may be generated within this form
`
`Application Number
`ParentFiling Date (YYYY-MM-DD)
`Priority Claimed
`a (
`Additional Foreign Priority Data may be generated within this form by selecting the
`
`AssigneeInformation:
`Providing this information in the application data sheet does not substitute for compliance with any requirement of part 3 of Title 37
`
`of the CFR to have an assignment recorded in the Office.
`
`Page 6 of 275
`
`EFS Web 2.2.2
`
`Page 6 of 275
`
`

`

`PTO/SB/14 (11-08)
`Approved for use through 09/30/2010. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`. Attorney Docket Number|SMITHO70+.
`
`
`Application Data Sheet 37 CFR 1.76
`—
`Application Number
`
`Title of Invention
`
`USER INTERFACE SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT
`
`button.
`
`If the Assignee is an Organization check here.
`
`Xx
`
`Organization Name
`
`PA4TENTS1, LLC
`
`Mailing AddressInformation:
`
`Address1
`
`Address 2
`
`1201 Orange St.
`
`#600
`
`Email Address
`
`Additional Assignee Data may be generated within this form by selecting the Add
`
`Signature:
`A signature of the applicant or representative is required in accordance with 37 CFR 1.33 and 10.18. Please see 37
`CFR 1.4(d) for the form of the signature.
`
`Date (YYYY-MM-DD)
`
`[Patrick E. Caldwell
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to
`complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR
`COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 2.2.2
`
`Page 7 of 275
`
`Page 7 of 275
`
`

`

`SMITH070+
`
`USER INTERFACE SYSTEM, METHOD, AND COMPUTER PROGRAM
`
`PRODUCT
`
`CROSS-REFERENCE TO RELATED APPLICATIONS
`
`[0001]
`
`If any definitions (e.g. figure reference signs, specialized terms, examples,
`
`data, information, etc.) from any related material (e.g. parent application, other related
`
`application, material incorporated by reference, material cited, extrinsic reference,etc.)
`
`conflict with this application (e.g. abstract, description, summary, claims, etc.) for any
`
`purpose(e.g. prosecution, claim support, claim interpretation, claim construction,etc.),
`
`then the definitions in this application shall apply.
`
`BACKGROUND AND FIELD OF INVENTION
`
`[0002]
`
`Embodiments of the present invention generally relate to consumer electronic
`
`devices, particularly cell phones, tablets, and other mobile devices (however,
`
`applicability is also relevant to non-mobile devices).
`
`Page 8 of 275
`
`Page 8 of 275
`
`

`

`-2-
`
`BRIEF SUMMARY
`
`[0003]
`
`A system, method, and computer program product are provided for a touch or
`
`pressure signal-based interface. In operation, a touch or pressure signal is received in
`
`association with a touch interface of a device. To this end, a user experienceis altered,
`
`utilizing the signal. In different embodiments, various features may be further
`
`incorporated in association with the system, method, and computer program product, for
`
`improvement purposes.
`
`Page 9 of 275
`
`Page 9 of 275
`
`

`

`-3-
`
`BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
`
`[0004]
`
`So that the features of various embodiments of the present invention can be
`
`understood, a more detailed description, briefly summarized above, may be had by
`
`reference to various embodiments, some of whichare illustrated in the accompanying
`
`drawings. It is to be noted, however, that the accompanying drawings illustrate only
`
`embodiments and are therefore not to be considered limiting of the scope of various
`
`embodiments of the invention, for the invention may admit to other effective
`
`embodiments. The following detailed description makes reference to the accompanying
`
`drawings that are now briefly described.
`
`[0005]
`
`Figure 1 illustrates a network architecture, in accordance with one
`
`embodiment.
`
`[0006]
`
`Figure 2 showsa representative hardware environment that may be associated
`
`with the servers and/or clients of Figure 1, in accordance with one embodiment.
`
`[0007]
`
`Figure 3 shows a methodfor altering a user experience based on a received
`
`signal, in accordance with one embodiment.
`
`[0008]
`
`Figure 4 shows a method for defining a selection made within a user interface
`
`based in part on contact pressure, in accordance with one embodiment.
`
`[0009]
`
`Figure 5 showsa pressure-sensitive user interface for making a selection, in
`
`accordance with one embodiment.
`
`[0010]
`
`Figure 6 shows a method for determining the context of a contact pressure-
`
`based selection and choosing an appropriate selection function, in accordance with one
`
`embodiment.
`
`[0011]
`
`Figure 7 shows a device having a backtouchinterface, in accordance with one
`
`embodiment.
`
`[0012]
`
`Figure 8 shows a methodfor providing feedback to the user of a backtouch
`
`interface, in accordance with one embodiment.
`
`Page 10 of 275
`
`Page 10 of 275
`
`

`

`-4-
`
`[0013]
`
`Figure 9 showsa pressure-sensitive user interface for making a selection using
`
`a backtouch interface, in accordance with one embodiment.
`
`[0014]
`
`Figure 10 showsa userinterface for defining settings associated with a
`
`backtouch interface, in accordance with one embodiment.
`
`[0015]
`
`Figure 11 showsa userinterface for defining settings associated with a
`
`pressure-sensitive interface, in accordance with one embodiment.
`
`[0016]
`
`Figure 12 shows a methodfor assisting a user in defining touch states, in
`
`accordance with one embodiment.
`
`[0017]
`
`Figure 13 showsa user interface for assisting a user in defining touchstates,
`
`in accordance with one embodiment.
`
`[0018]
`
`Figure 14 showsa user interface for indicating that a backtouch or pressure-
`
`sensitive interface is activated, in accordance with one embodiment.
`
`[0019]
`
`Figure 15 showsa user interface for defining a backtouch feedbackstyle, in
`
`accordance with one embodiment.
`
`[0020]
`
`Figure 16 showsan alternative method for defining a selection made within a
`
`user interface based in part on contact pressure, in accordance with one embodiment.
`
`[0021]
`
`Figure 17 showsa user interface for performing operations on a selection, in
`
`accordance with one embodiment.
`
`[0022]
`
`Figure 18 shows a methodforutilizing contact pressure-based gestures, in
`
`accordance with one embodiment.
`
`[0023]
`
`Figure 19 shows an example of a contact pressure-based gesture for scrolling
`
`a text field, in accordance with one embodiment.
`
`[0024]
`
`Figure 20 showsan example of a multitouch pressure gesture for indicating a
`
`direction, in accordance with one embodiment.
`
`Page 11 of 275
`
`Page 11 of 275
`
`

`

`5-
`
`[0025]
`
`Figure 21 shows an example of a multitouch pressure gesture for indicating a
`
`rotation, in accordance with one embodiment.
`
`[0026]
`
`Figure 22 showsan example of a front-back gesture, in accordance with one
`
`embodiment.
`
`[0027]
`
`Figure 23 showsan example of a virtual control knob gesture, in accordance
`
`with one embodiment.
`
`[0028]
`
`Figure 24 showsa methodfor gesture differentiation, in accordance with one
`
`embodiment.
`
`[0029]
`
`Figure 25 shows an example of an “anchor and move” gesture, in accordance
`
`with one embodiment.
`
`[0030]
`
`Figure 26 shows an example of a twist gesture, in accordance with one
`
`embodiment.
`
`[0031]
`
`Figure 27 shows a methodfor determining touch states using a touch-sensitive
`
`interface, in accordance with one embodiment.
`
`[0032]
`
`Figure 28 shows examples of pattern-based gestures, in accordance with one
`
`embodiment.
`
`[0033]
`
`Figure 29 showsfile sharing triggered by a gesture, in accordance with one
`
`embodiment.
`
`[0034]
`
`Figure 30 shows an example of touch-based device authentication, in
`
`accordance with one embodiment.
`
`[0035]
`
`Figure 31 shows an example of multi-device facial recognition, in accordance
`
`with one embodiment.
`
`[0036]
`
`Figure 32 showstwodisplays combinedto function as one, in accordance
`
`with one embodiment.
`
`Page 12 of 275
`
`Page 12 of 275
`
`

`

`-6-
`
`[0037]
`
`Figure 33 showsa user interface for defining custom gestures, in accordance
`
`with one embodiment.
`
`[0038]
`
`Figure 34 showsa user interface for defining pressure inputs for a custom
`
`gesture, in accordance with one embodiment.
`
`[0039]
`
`Figure 35 showsa user interface for defining touch inputs for a custom
`
`gesture, in accordance with one embodiment.
`
`[0040]
`
`Figure 36 showsa user interface for defining surface inputs for a custom
`
`gesture, in accordance with one embodiment.
`
`[0041]
`
`Figure 37 showsa user interface for summarizing contact inputs for a custom
`
`gesture, in accordance with one embodiment.
`
`[0042]
`
`Figure 38 showsa user interface for defining system inputs for a custom
`
`gesture, in accordance with one embodiment.
`
`[0043]
`
`Figure 39 showsa pressure-sensitive user interface containing a virtual
`
`trackball, in accordance with one embodiment.
`
`[0044]
`
`Figure 40 shows a device with slide pads, in accordance with one
`
`embodiment.
`
`[0045]
`
`Figure 41 showsan exampleof a slide pad gesture for performing an auxiliary
`
`function, in accordance with one embodiment.
`
`[0046]
`
`Figure 42 showsa user interface for providing quick access to favorite
`
`operations, in accordance with one embodiment.
`
`[0047]
`
`Figure 43 shows a device with a non-uniform display, in accordance with one
`
`embodiment.
`
`[0048]
`
`Figure 44 showsa light valve technique, in accordance with one embodiment.
`
`Page 13 of 275
`
`Page 13 of 275
`
`

`

`-7-
`
`[0049]
`
`Figure 45 shows a device display mixing color pixels with black and white
`
`pixels, in accordance with one embodiment.
`
`[0050]
`
`Figure 46 showsa device display mixing color with black and white across a
`
`matrix, in accordance with one embodiment.
`
`[0051]
`
`Figure 47 shows a modulated display, in accordance with one embodiment.
`
`[0052]
`
`Figure 48 showsa device with a display having a non-uniform backlight, in
`
`accordance with one embodiment.
`
`[0053]
`
`Figure 49 shows a device having a removable back sensoror display, in
`
`accordance with one embodiment.
`
`[0054]
`
`Figure 50 showsa user interface containing an adaptive soft keyboard, in
`
`accordance with one embodiment.
`
`[0055]
`
`Figure 51 showsa user interface with context-sensitive backlighting, in
`
`accordance with one embodiment.
`
`[0056]
`
`Figure 52 shows a 3D layereduserinterface, in accordance with one
`
`embodiment.
`
`[0057]
`
`Figure 53 shows a device which may be converted into a 3D layer enabled
`
`device, in accordance with one embodiment.
`
`[0058]
`
`Figure 54 shows a 3D layered user interface for augmentedreality, in
`
`accordance with one embodiment.
`
`[0059]
`
`Figure 55 showsa device with user gaze tracking sensors, in accordance with
`
`one embodiment.
`
`[0060]
`
`Figure 56 showsthe use of eye tracking to generate 3D depth cues, in
`
`accordance with one embodiment.
`
`[0061]
`
`Figure 57 showsa layered display, in accordance with one embodiment.
`
`Page 14 of 275
`
`Page 14 of 275
`
`

`

`-8-
`
`[0062]
`
`Figure 58 showsan automultoscopic display, in accordance with one
`
`embodiment.
`
`[0063]
`
`Figure 59 showsa layered display containing depth fused 3D images, in
`
`accordance with one embodiment.
`
`[0064]
`
`Figure 60 showsa light field camera, in accordance with one embodiment.
`
`[0065]
`
`Figure 61 shows a 3D layered userinterface with a floating soft keyboard, in
`
`accordance with one embodiment.
`
`[0066]
`
`Figure 62 shows a backtouch enabled 3D layered userinterface, in accordance
`
`with one embodiment.
`
`[0067]
`
`Figure 63 showsa tactile feedback enabled display, in accordance with one
`
`embodiment.
`
`[0068]
`
`Figure 64 showsa watch-based display extension, in accordance with one
`
`embodiment.
`
`[0069]
`
`Figure 65 shows a wireless storage ring and key, in accordance with one
`
`embodiment.
`
`[0070]
`
`Figure 66 shows a 3D layered user interface having a clipboard layer, in
`
`accordance with one embodiment.
`
`[0071]
`
`Figure 67 shows a 3D layered user interface having an operation layer, in
`
`accordance with one embodiment.
`
`[0072]
`
`Figure 68 showsa user interface for providing touch feedback, in accordance
`
`with one embodiment.
`
`[0073]
`
`Figure 69 showsa user interface for providing increased security, in
`
`accordance with one embodiment.
`
`Page 15 of 275
`
`Page 15 of 275
`
`

`

`-9-
`
`[0074]
`
`Figure 70 showsa userinterface for presenting a contextual menu, in
`
`accordance with one embodiment.
`
`Page 16 of 275
`
`Page 16 of 275
`
`

`

`-10-
`
`DETAILED DESCRIPTION
`
`[0075]
`
`Figure 1 illustrates a network architecture 100, in accordance with one
`
`embodiment. As shown,a plurality of networks 102 is provided. In the context of the
`
`present network architecture 100, the networks 102 may each take any form including,
`
`but not limited to a local area network (LAN), a wireless network, a wide area network
`
`(WAN)suchasthe Internet, peer-to-peer network,etc.
`
`[0076]
`
`Coupled to the networks 102 are servers 104 which are capable of
`
`communicating over the networks 102. Also coupled to the networks 102 and the servers
`
`104 is a plurality of clients 106. Such servers 104 and/or clients 106 may each include a
`
`desktop computer, lap-top computer, hand-held computer, mobile phone, personal digital
`
`assistant (PDA), tablet computer, peripheral (e.g. printer, etc.), any component of a
`
`computer, and/or any other type of logic. In order to facilitate communication among the
`
`networks 102, at least one gateway 108 is optionally coupled therebetween.
`
`[0077]
`
`Figure 2 showsa representative hardware environmentthat may be associated
`
`with the servers 104 and/or clients 106 of Figure 1, in accordance with one embodiment.
`
`Such figure illustrates a typical hardware configuration of a mobile device in accordance
`
`with one embodiment having a central processing unit 210, such as a microprocessor, and
`
`a numberof other units interconnected via a system bus 212.
`
`[0078]
`
`The mobile device shownin Figure 2 includes a Random Access Memory
`
`(RAM) 214, Read Only Memory (ROM)216, an I/O adapter 218 for connecting
`
`peripheral devices such as disk storage units 220 to the bus 212, a user interface adapter
`
`222 for connecting a keyboard 224, a mouse 226, a speaker 228, a microphone 232,
`
`and/or other user interface devices such as a touch screen (not shown)to the bus 212,
`
`communication adapter 234 for connecting the mobile device to a communication
`
`network 235 (e.g., a data processing network) and a display adapter 236 for connecting
`
`the bus 212 to a display device 238.
`
`Page 17 of 275
`
`Page 17 of 275
`
`

`

`-l|1-
`
`[0079]
`
`The mobile device may haveresident thereon any desired operating system.
`
`It
`
`will be appreciated that an embodiment may also be implemented on platforms and
`
`operating systems other than those mentioned. One embodiment maybe written using
`
`JAVA,C, Objective C, and/or C++ language, or other programming languages, along
`
`with an object oriented programming methodology. Object oriented programming (OOP)
`
`has becomeincreasingly used to develop complex applications.
`
`[0080]
`
`Of course, the various embodiments set forth herein may be implemented
`
`utilizing hardware, software, or any desired combination thereof. For that matter, any
`
`type of logic may be utilized which is capable of implementing the various functionality
`
`set forth herein.
`
`[0081]
`
`Figure 3 shows a method 300, in accordance with one embodiment. As an
`
`option, the method may be implemented in the context of the architecture and
`
`environment of any subsequent Figure(s). Of course, however, the method may be
`
`implemented in any desired environment.
`
`[0082]
`
`As shownin operation 302, a signal is received in association with a touch
`
`interface of a device. In one embodiment, the signal may include a pressure signal which
`
`is indicative of a magnitude of pressure. In the context of the present description, such
`
`pressure signal may include anysignalthat is a function of or related to a pressure
`
`applied to the device. In one embodiment, such pressure signal maybe indicative of a
`
`magnitude of pressure being applied to a touch interface of the device. In various
`
`embodiments, such pressure signal may be generated by a pressure sensor including, but
`
`not limited to those described in the context of subsequently described embodiments, or
`
`any other mechanism,for that matter, that is capable of generating the pressure signal.
`
`[0083]
`
`In other embodiments, the signal may include a touch signal indicative of a
`
`touch interface being touched. In the context of the present description, such touch signal
`
`may or maynotbe indicative of a magnitude of pressure being applied to a touch
`
`interface of the device. For example, such touch signal may, in one embodiment, simply
`
`Page 18 of 275
`
`Page 18 of 275
`
`

`

`-12-
`
`indicate whether applied pressure is sensed, or not, e.g. not necessarily gauge any more
`
`than two pressure states, including pressure-sensed and pressure-not-sensed,etc.
`
`[0084]
`
`Also in the context of the present description, the aforementioned device may
`
`include any device including, but not limited to those described in the context of this
`
`and/or subsequently described embodiments. Further, in various embodiments, the touch
`
`interface may or may not be combined with a display. For example,if the touch interface
`
`is combined with a display, the touch interface may include a touch screen. Thus, the
`
`touch interface may, in various embodiments, include, but is not limited to a touch screen
`
`or any other interface responsive to touch that is described in the context of this and/or
`
`subsequently described embodiments.
`
`[0085]
`
`In one optional embodiment, the touch interface may be positioned ona first
`
`face of a device that includes a display on a second face thereof. Further, the first face
`
`and second face may include any respective faces(e.g. front, back, left side, right side,
`
`top side, bottom side, etc.) that are different. Just by way of example, in various
`
`embodiments, the first face and the second face may be on opposite faces of the device of
`
`the device. Further, the first face may include a side face and the second face may
`
`include a front face of the device. Evenstill, the first face may include a back face and
`
`the second face may include a front face of the device. Of course, the touch interface
`
`maybe positioned on the sameface as the display, in other embodiments.
`
`[0086]
`
`Asindicated in operation 304, a user experience maybealtered,utilizing the
`
`signal. In the context of the present description, the user experience may include any
`
`aspect of the device that is capable of being directly or indirectly experienced by a user
`
`including, but not limited to those described in the context of this and/or subsequently
`
`described embodiments.
`
`[0087]
`
`For example, in the context of an embodiment involving the pressure signal,
`
`the user experience maybealtered as a function of the magnitude of the pressure being
`
`applied to the touch interface, utilizing the pressure signal. Just by way of example, in
`
`various embodiments, the user experience may be altered by causing input to the device,
`
`by causing output from the device, by causing processing by the device, etc. In other
`
`Page 19 of 275
`
`Page 19 of 275
`
`

`

`-13-
`
`embodiments involving a touch signal, the user experience maybe altered in any manner,
`
`utilizing the touch signal (dependentor independentof any fluctuation of pressure).
`
`[0088]
`
`Of course, the foregoing embodiments maybe altered by adding and/or
`
`removing various features. For example, in one embodiment, the pressure signal may be
`
`received whichis indicative of the magnitude of pressure being applied to a touch
`
`interface positioned on a first face of a device that includes a display on a second face
`
`thereof. To this end, the user experience maybe altered as a function of the magnitude of
`
`the pressure being applied to the touch interface, utilizing the pressure signal.
`
`[0089]
`
`In another embodiment, a pressure signal may be received whichis indicative
`
`of a magnitude of pressure being applied to a touch screen. To this end, the user
`
`experience may be altered as a function of the magnitude of the pressure being applied to
`
`the touch screen,utilizing the pressure signal.
`
`Instill yet another optional embodiment, a
`
`touch signal may be received whichis indicative of a touch interface being touched,
`
`where the touch interface is positioned on a first face of a device that includes a display
`
`on a second face thereof. To this end, the user experience maybealtered, utilizing the
`
`touch signal. Again, any of the features described above (or hereinafter, for that matter)
`
`may or may not be combined in any desired manner.
`
`[0090]
`
`Moreillustrative information will now be set forth regarding various optional
`
`architectures and features with which the foregoing techniques discussed in the context of
`
`any of the present or previous figure(s) may or may not be implemented,per the desires
`
`of the user. For instance, various optional examples and/or options associated with the
`
`operations 302 and/or 304, and/or other optional features have been and will be set forth
`
`in the context of a variety of possible embodiments. It should be strongly noted,
`
`however, that such informationis set forth for illustrative purposes and should not be
`
`construed as limiting in any manner. Anyof such features may be optionally
`
`incorporated with or without the inclusion of other features described.
`
`[0091]
`
`Figure 4 shows a method 400 for defining a selection made within a user
`
`interface based in part on contact pressure, in accordance with one embodiment. As an
`
`option, the method 400 may be implemented in the context of the architecture and
`
`Page 20 of 275
`
`Page 20 of 275
`
`

`

`-14-
`
`environment of the previous Figures or any subsequent Figure(s). Of course, however,
`
`the method 400 may becarried out in any desired environment. It should also be noted
`
`that the aforementioned definitions may apply during the pres