A computationally implemented method includes, but is not limited to determining that a computing device that was presenting an item has been transferred from a first user to a second user, and presenting, via the computing device, one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware in one or more machines or article of manufacture configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
A computationally implemented system includes, but is not limited to: means for determining that a computing device that was presenting an item has been transferred from a first user to a second user; and means for presenting, via the computing device, one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
A computationally implemented system includes, but is not limited to: circuitry for determining that a computing device that was presenting an item has been transferred from a first user to a second user; and circuitry for presenting, via the computing device, one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
An article of manufacture including a non-transitory storage medium bearing one or more instructions for determining that a computing device that was presenting an item has been transferred from a first user to a second user; and one or more instructions for presenting, via the computing device, one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
A method for determining that a computing device that was presenting an item has been transferred from a first user to a second user, wherein said determining that a computing device that was presenting an item has been transferred from a first user to a second user, is performed via at least one of a machine, article of manufacture, or composition of matter; and for presenting, via the computing device, one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
a shows a computing device 10* being transferred between two users in an exemplary environment 100.
b shows one type of movement that may be detected/monitored by the computing device 10* of
c shows another type of movement that may be detected/monitored by the computing device 10* of
d shows another type of movement that may be detected/monitored by the computing device 10* of
e shows overall 3-dimensional movements of the computing device 10* of
a shows a particular implementation of the computing device 10* of
b shows another implementation of the computing device 10* of
c shows another perspective of the transfer determining module 102* (e.g., the transfer determining module 102′ and the transfer determining module 102″) of
d shows another perspective of the highlighted portion presenting module 104* (i.e., the highlighted portion presenting module 104′ and the highlighted portion presenting module 104″) of
e shows various types of sensors 120 that may be included in the computing device 10′ and the computing device 10″ of
a is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
b is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
c is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
d is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
e is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
f is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
g is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
h is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
i is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
j is a high-level logic flowchart of a process depicting alternate implementations of the transfer determining operation 402 of
a is a high-level logic flowchart of a process depicting alternate implementations of the highlighted portion presenting operation 404 of
b is a high-level logic flowchart of a process depicting alternate implementations of the highlighted portion presenting operation 404 of
c is a high-level logic flowchart of a process depicting alternate implementations of the highlighted portion presenting operation 404 of
a illustrates an example item 701a being displayed by the computing device 10* of
b illustrates an example highlighted portion 702b of the example item 701a of
c illustrates another example highlighted portion 702c of the example item 701a of
d illustrates another example highlighted portion 702d of the example item 701a of
e illustrates an example portion 720e of another example item 701b being highlighted in accordance with some implementations.
f illustrates another example portion 720f of the example item 701b of
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
Advances in computing technologies and related technologies (e.g., visual display technology, battery technology, etc.) in recent years have greatly facilitated in the development of computing devices having increasingly smaller form factors while still maintaining exceptional processing capabilities. Examples of such computing devices include, for example, laptops, Netbooks, tablet computers (i.e., “slate” computers), e-readers, Smartphones, and so forth. Because of their compactness, such devices are becoming much easier to share among multiple users. That is, due to their small form factors, such devices allow users of such devices to easily hand-off such devices to friends, family, co-workers, clients, and so forth, in order to share the content and/or applications being presented through such devices.
For example, suppose a user of a tablet computer is reading an electronic book (e.g., an eBook, a digital book, etc.) through the tablet computer. While reading the electronic book, the user comes across an interesting passage (e.g., a paragraph) located on a particular portion of a particular page of the electronic book that the user wants to share with a friend sitting across a table from the user. Typically, in order to show the passage of interest to the friend, the user will simply pass or handover the tablet computer to the friend thereby allowing the friend to view the passage that the user was interested in. Unfortunately, by simply passing the tablet computer to the friend, the tablet computer, along with displaying the passage of interest, may also be displaying many other passages from the electronic book that may not be of interest to the user (or the friend), thus making it difficult for the friend to easily find the passage of interest without the help of the user. And even after the user helps the friend find the passage of interest, the friend may not be able to digest the passage of interest because it may not be in a format that is easily digestible by the friend (e.g., if the friend is elderly and has poor eyesight and the passage may be in a textual format that is too small to read or if the friend does not read the language that the passage is written in, such as English, then the friend may not be able to understand the passage).
Suppose further that the same user uses a tablet computer at work for a variety of tasks including, for example, to electronically sign documents. Typically business contracts are signed by a number of people including, for example, the owners or representatives of business, clients, vendors, etc. For various legal and business reasons, contracts that are typically signed in the business context (as well as in familial and personal context) tend to be highly complex and difficult to decipher. Thus, it is often difficult and cumbersome for signers of such electronic documents to quickly and easily figure out where in such documents do the signers actually write their signatures upon receiving the tablet computer that the documents are being displayed through.
In accordance with various embodiments, computationally implemented methods, systems, and articles of manufacture are provided that can determine whether a computing device (e.g., a portable or mobile computing device such as a tablet computer, an e-reader, a smartphone, and so forth) that was presenting an electronic item (e.g., an application or an application interface, a productivity document such as a word processing or spreadsheet document, an audio file, a video file, an image file or folder, a website, an electronic or digital book, and so forth) has been transferred from a first user to a second user; and to visually and/or audibly present, via the computing device, one or more highlighted portions of the electronic item (herein simply “item”), the one or more highlighted portions being highlighted in response, at least in part, to determining that the computing device has been transferred from the first user to the second user. In various embodiments, a computing device may be defined as an electronic device having electronic circuitry for executing one or more functionalities. In some cases, a computing device may include one or more processors (e.g., microprocessors, central processing units or CPUs, array processors, vector processors, controllers, and so forth).
In various embodiments, the computing device may have been transferred from the first user to the second user when control over the computing device has been transferred from the first user to the second user. For these embodiments, a user (e.g., the first user or the second user) may have control over the computing device when, for example, the user is, relative to other users, nearest or closest to the computing device, when the user is situated in a particular location relative to the particular orientation of the computing device (e.g., when the user is located on the side of the computing device that a display device is located at and is centered with respect to the display device), and/or when the user has physical possession of the computing device such as by holding the computing device with one or two hands or by simply being in physical contact with the computing device. Thus, a transfer of a computing device from a first user to a second user may have occurred when, for example, the second user replaces the first user as being nearest to the computing device, when the second user replaces the first user generally at a particular location relative to the specific orientation of the computing device and/or when the possession of the computing device transfers from the first user to the second user.
As will be described in greater detail herein, a portion of an item may be highlighted in a variety of different ways in various alternative embodiments. For example, in some cases, highlighting of the portion of the item may be by formatting (e.g., font style or size, color scheme, brightness, zoom view, increased audio volume or audio bass, language, and so forth) the portion differently from how the portion was formatted prior to the transfer of the computing device and/or by having a format that is different from the format of non-highlighted portions of that item that may be concurrently presented with the highlighted portions. Alternatively or additionally, a portion of the item may be highlighted by simply encircling the portion with a boarder or boarders such as a line.
As will be further described herein, the portion or portions of the item to be highlighted as well as the type of highlighting that may be applied to the portion or portions may depend on which user is the computing device being transferred to. For example, in some cases, the determination as to whether the computing device has been transferred from a first user to a second user may include an operation to identify the second user, and based on the identification of the second user select the appropriate portion or portions of the item to highlight and/or the type or types of highlighting to apply. In some embodiments, the second user may be identified based on the biometric characteristics or gestures exhibited by the second user.
Referring now to
Note that although the front-side 17a of the computing device 10* of
Referring now to
There are a number of ways to determine whether a computing device 10* is or has been transferred from one user to another user. For instance, in some cases, various sensor-provided data may be collected in order to make such a determination. Such data may indicate various environmental aspects surrounding the computing device 10* and/or aspects of the computing device 10* itself (e.g., movements displayed or exhibited by the computing device 10* as a result of being in contact with one or more users). For example, when the computing device 10* of
One way to track the movements or gestures of the first user 20 is to track the movements of the computing device 10* itself (note that another way to detect the gestures of the first user 20 is to observe visually the gestures—visual cues—exhibited by the first user 20 via one or more image capturing devices 304, which will be described in greater detail below). That is, these gestures that may be exhibited by the first user 20 during the transfer of a computing device 10* from the first user 20 to the second user 30 may cause the computing device 10* to be spatially moved in particular ways. Thus, in order to detect whether a computing device 10* is being transferred from a first user 20 to a second user 30, the spatial movements of the computing device 10* may be tracked in order to detect signature movements that when detected as occurring at least infer the transfer of the computing device 10* between the first user 20 and the second user 30. For example, the computing device 10* may maintain in its memory 114 (see
One way to monitor for such movements of the computing device 10* is to directly detect such movements using one or more “movement” sensors that are designed to directly detect/measure spatial movements of the computing device 10*. Examples of such movement sensors include, for example, inertia sensors, accelerometers (e.g. three-axis or 3D accelerometers), gyroscopes, and so forth. These sensors (herein movement sensors 302—see
Since not all movements of the computing device 10* that may be detected will be as a result of the computing device 10* being transferred between two users, in various embodiments and as will be further described herein, the computing device 10* may be endowed with particular logic for determining (e.g., identifying) which movements associated with the computing device 10* that have been detected indicates or at least suggests that the computing device 10* is or has been transferred from, for example, a first user 20 to a second user 30 and which detected movements may merely be “noise movements.”
Various types of movements of the computing device 10* may be tracked in order to determine or at least infer that the computing device 10* is being transferred between, for example, a first user 20 and a second user 30. Examples of the types of movements that may be tracked include, for example, the overall three-dimensional movements of the computing device 10*, or specific types of movements including tilt type movements, spin-rotation type movements, spatial relocation type movements, vibration movements, and so forth of the computing device 10*. In order to determine or at least infer that the computing device 10* has been transferred from a first user 20 to a second user 30, these movements of the computing device 10* may be, individually or in combination, tracked using one or more sensors 120 that may be included with the computing device 10* as illustrated in
Referring now to
One type of tilt that may be detected/monitored is tilt 42a of the computing device 10* that may occur when the computing device 10* is at least partially rotated around a central horizontal axis 43a. A second type of tilt that may be detected is tilt 42b, which may occur when the computing device 10* is at least partially rotated around a bottom horizontal axis 43b. Although not depicted, another type of tilt that may occur and that may be monitored is when the computing device 10* is at least partially rotated around an angular axis 43c that is angular with respect to a horizontal axis (e.g., axis 43a or 43b) and is parallel to the plane of the backside 17b similar to axis 43a and axis 43b. Yet another type of tilt that may occur and that may also be monitored is when the computing device 10* is at least partially rotated around a vertical axis 43d. Note that although the vertical axis 43d is depicted as being centered along the backside 17b of the computing device 10*, just like the horizontal axis 43b, the vertical axis 43d does not have to be centered on the backside 17b and instead, may be offset from the center of the backside 17b of the computing device 10* (e.g., may be closer to one end of the device rather than an opposite end of the device. Although only a few types of tilts were illustrated in
By detecting that the computing device 10* has been tilted in a particular manner from a first tilt orientation to a second tilt orientation, a determination or an inference may be made that the computing device 10* has been transferred from the first user 20 to the second user 30. In particular, when the first user 20, for example, is handing off or transferring the computing device 10* to the second user 30, the first user 20 may tilt the computing device 10* in a particular way that may be identifiable. Thus, when the computing device 10* is being transferred from a first user 20 to a second user 30 (or vice versa), the computing device 10*(or rather the logic endowed with the computing device 10*) may track the movements of the computing device 10* as it moves from a first tilt orientation (e.g., the tilt of the computing device 10* at the beginning of the transfer or when the first user 20 was using or had possession of the computing device 10*) to a second tilt orientation (e.g., the tilt of the computing device 10* at the end of the transfer or when the second user 30, for example, has obtained possession of the computing device 10*).
In order to make a determination or at least an inference that a transfer was made between two users such as from the first user 20 to the second user 30 (or vice versa), the computing device 10* or at least the logic endowed in the computing device 10* may track and examine the particular movements of the computing device 10* (e.g., how the computing device 10* was reoriented from a first tilt orientation to a second tilt orientation including speed and cadence of the reorientation) as the computing device 10* moves from the first tilt orientation to a second tilt orientation. The computing device 10* may additionally or alternatively analyze the second tilt orientation (e.g., the tilt of the computing device 10* after it has finished being reoriented) at least with respect to the first tilt orientation in order to determine or infer that the computing device 10* has been transferred. To further determine or at least infer that the computing device 10* has been transferred from the first user 20 to the second user 30, for example, the examination/analysis of the detected tilt movements of the computing device 10* may involve comparing the detected tilt movements of the computing device 10* with catalogued or library tilt movements (which may be stored in the memory 114 of the computing device 10*) that are identified as being movements associated with transfer of the computing device 10* between two users.
That is, the computing device 10* may maintain in its memory 114 (see
Thus, another aspect of tilt orientation changes that may be considered in order to determine or infer that a transfer has taken place is to simply look at the end points of the tilt reorientation and their differences. In other words, to analyze the first tilt orientation (e.g., the tilt orientation of the computing device 10* before the computing device 10* being reoriented) and the second tilt orientation (e.g., the end tilt orientation of the computing device 10* after it has been reoriented) with respect to each other, and the differences between the first tilt orientation and the second tilt orientation. Thus, in some embodiments, the computing device 10* may also or additionally maintain a catalogue or library of changes of tilt orientation (e.g., tilt orientation changes) that have been previously identified as tilt changes that occur when, for example, a computing device 10* is transferred between two users. Such catalogue or library of tilt orientation changes may be stored as part of a movement library 170 stored in memory 114 (see
Referring now to
Referring back to
By detecting that the computing device 10* has been spin rotated in a particular manner, a determination or an inference may be made that the computing device 10* has been transferred from the first user 20 to the second user 30. In particular, when the first user 20 is, for example, handing off or transferring the computing device 10* to the second user 30, the first user 20 may spin rotate the computing device 10* in a particular way. Thus, when the computing device 10* is being transferred from, for example, the first user 20 to the second user 30, the computing device 10*(or rather the logic endowed with the computing device 10*) may track the movements of the computing device 10* as it moves from a first spin orientation (e.g., the orientation of the computing device 10* at the beginning of the transfer or when the first user 20 was using the computing device 10*) to a second spin orientation (e.g., the orientation of the computing device 10* at the end of the transfer or when the second user 30 has obtained possession of the computing device 10*).
Similar to the tilt or tilt movement detection/analysis described earlier, in order to make a determination or at least an inference that a transfer was made from, for example, the first user 20 to the second user 30 (or vice versa), the computing device 10* or at least the logic endowed in the computing device 10* may scrutinize the particular movements of the computing device 10* as the computing device 10* spin rotates from a first orientation to a second orientation. The computing device 10* may additionally or alternatively analyze the second orientation (e.g., the orientation of the computing device 10* after it has finished being spin rotated) at least with respect to the first orientation (e.g., the orientation of the computing device 10* before it was spin rotated) in order to determine or at least infer that the computing device 10* has been transferred.
To further determine or at least infer that the computing device 10* has been transferred from the first user 20 to the second user 30, the examination/analysis of the detected spin rotation of the computing device 10* from the first orientation to the second orientation may involve comparing the detected spin rotation movement of the computing device 10* with catalogued or library spin rotation movements that are identified as being associated with transfer of the computing device 10*. That is, the computing device 10* may maintain in its memory 114 (see
Turning now to
In some cases, the computing device 10*(or rather the logic endowed with the computing device 10*) may additionally or alternatively analyze the second spatial location 48 with respect to the first spatial location 46 in order to determine or at least infer that the computing device 10* has been transferred from the first user 20 to the second user 30. To further determine or at least infer that the computing device 10* has been transferred from, for example, the first user 20 to the second user 30, the examination/analysis of the detected spatial relocation movements of the computing device 10* may be compared with catalogued or library signature spatial relocation movements that have been identified as being associated with the transfer of the computing device 10 between two users. That is, the computing device 10* may maintain in its memory 114 (see
In some embodiments, in order to determine or at least infer that the computing device 10* has been transferred from the first user 20 to the second user 30 (or vice versa), the computing device 10* may be endowed with logic that detects/monitors vibrations. That is, each user who may come in contact with the computing device 10* may pass on to the computing device 10* unique vibration pattern or signature (e.g., as a result of the heartbeat of the “touching” user). Thus, when the first user 20 is holding the computing device 10*, the computing device 10* may vibrate in a particular vibration pattern that is associated with the first user 20. In contrast, when the computing device 10* has been transferred to the second user 30 and the second user 30 is holding the computing device 10*, the computing device 10* may vibrate in a manner that is associated with the second user 30. Therefore, one way to determine whether the computing device 10* has been transferred from the first user 20 to the second user 30 (or vice versa) is to detect/monitor at least changes in vibrations exhibited by the computing device 10*.
In some cases, this may involve the computing device 10*(or at least the logic endowed with the computing device 10*) initially detecting the particular vibration pattern of the computing device 10* when the computing device 10* is being held by, for example, the first user 20, and to detect when the computing device 10* no longer vibrates in such a manner. In order to determine whether the computing device 10* has been transferred from the first user 20 to the second user 30, the computing device 10* in some cases may be further designed to determine that the computing device 10* is vibrating in a way that matches with a vibration pattern (e.g., signature vibration pattern) of the second user 30. By making such a determination, an inference may be made that the computing device 10* is being held or is in contact with the second user 30.
In some embodiments, the computing device 10* may include logic that is designed to determine whether the computing device 10* has moved away from the first user 20 in order to determine whether, for example, the computing device 10* has been transferred from the first user 20 to the second user 30. That is, by making such a determination, at least an inference may be made that the computing device 10* has been transferred from the first user 20 to the second user 30. In some embodiments, in order to make such a determination, data from a combination of sensors 120 may be processed and analyzed. That is, in order to determine whether the computing device 10 has moved away from, for example, the first user 20, a combination of one or more movement sensors 302 (see
For example, the computing device 10* in some cases may employ one or more movement sensors 302 to detect the actual movements of the computing device 10* and one or more image capturing devices 304 (along with facial recognition system/application) to determine that a face associated with the first user 20 is moving away from the computing device 10* and/or to detect gestures made or exhibited by the first user 20 (e.g., such as the first user extending his/her arm out as to offer the computing device 20 to another user) that at least infers that the computing device 10* is moving away from the first user 20. Based on the data provided by both the movement sensors 302 and the image capturing devices 304, at least an inference may be made that the computing device 10* has moved away from the first user 20*.
In some embodiments, and as illustrated in
As described briefly above, in addition to directly detecting the movements of the computing device 10* using movement sensors 302 (e.g., inertia sensors, accelerometers, gyroscopes, and so forth), other types of environmental aspects may be detected/monitored in order to determine whether the computing device 10* has been transferred from a first user 20 to a second user 30. For instance, in some cases, the computing device 10* or the logic endowed with the computing device 10* may be designed to detect, using one or more image capturing devices 304, certain visual cues that when detected at least infers the transfer of the computing device 10* from a first user 20 to a second user 30. For example, in some embodiments, the computing device 10* may be endowed with certain logic that is able to detect certain visual cues, such as gestures made by a first user 20 that when visually detected as occurring at least infers that the computing device 10* has been transferred from the first user 20 to another user. In the same or alternative embodiments, the computing device 10* may additionally or alternatively be endowed with logic that at least detects, via one or more image capturing devices 304, changes in lighting in the proximate vicinity of the computing device 10*. That is, generally when an object is moved from one spatial location to another spatial location, as in the case of a computing device 10* being transferred between two users, the object will be exposed to changes in lighting conditions. Thus, by merely detecting changes in lighting conditions of the computing device 10*, at least an inference may be made that the computing device 10* is being transferred between users.
Alternatively or additionally, in some embodiments, the computing device 10* may be endowed with a facial recognition system (e.g., facial recognition software or application) that when employed with one or more image capturing devices 304 may be used in order to determine the presence or absence of a face associated with the first user 20 or the second user 30 within the proximate vicinity of the computing device 10*. If the face associated with the first user 20 is not detected in the proximate vicinity of the computing device 10* and/or if a face not associated with the first user 20 is detected in the proximate vicinity of the computing device 10*, such as the face of the second user 30, then a determination or at least an inference may be made by the computing device 10* or by the endowed logic of the computing device 10* that a transfer of the computing device 10* from the first user 20 to the second user 30 may have occurred. The phrase “proximate vicinity” as used here is in reference to the immediate area surrounding the computing device 10* such as within a distance from the computing device 10* from which an object or a person is visually (or audibly) discernable or identifiable by the computing device 10* using, for example, a facial recognition system (or a voice verification/recognition system). Depending on sensitivity of the various systems, this may mean the immediate area around the computing device 10* that is within three feet, within five feet, within six feet, and so forth, of the computing device 10*.
In some cases, an inference that the computing device 10* has been transferred from, for example, the first user 20 to the second user 30 will not be made at least until the computing device 10*(or the logic endowed with the computing device 10*) determines that the face of a person other than the first user 20 is detected as being in the proximate vicinity of the computing device 10* and is detected as being located at one or more specified locations relative to the specific orientation of the computing device 10*. For example, in some cases, the inference that the computing device 10* has been transferred from, for example, the first user 20 to the second user 30 will not be made at least until it is determined that the face of the second user 30 is determined to be in the proximate vicinity of the computing device 10* and is detected as being at or near the center axis 18a of the display side (e.g., front side 17a) of the computing device 10*. Note that since the computing device 10* may be endowed with multiple sensors 120 (e.g., image capturing devices 304 and/or audio capturing devices 306) located on both the front side 17a as well as the backside 17b of the computing device 10*, it may be possible to detect the presence of a person or a face of the person on either side of the computing device 10*.
Another type of visual cues that the computing device 10* or the endowed logic of the computing device 10* may look for in order to determine whether the computing device 10* has been transferred from, for example, a first user 20 to a second user 30 is the presence or absence of one or more eyes (e.g., irises or retinas) in the proximate vicinity of the computing device 10* that are determined to be associated with the first user 20 or the second user 30. In particular, if the eyes of the first user 20 is determined not to be at least in the field of view of an image capturing device 304 (e.g., an image capturing device 304 that employs the viewing port 16 disposed on the front side 17a) of the computing device 10* and/or if one or more eyes of another person (e.g., second user 30) other than the first user 20 is determined to be in the field of view of the image capturing device 304, then at least an inference may be made that the computing device 10* has been transferred from the first user 20 to the second user 30.
In some cases, an inference that the computing device 10* has been transferred from for example, the first user 20 to the second user 30 (or vice versa) will not be made until the computing device 10 (or at least the logic endowed with the computing device 10*) determines that the eye of a person other than the first user 20 is detected in the proximate vicinity of the computing device 10* and is detected as being located at one or more specified locations (e.g., near or along the center axis 18a of the front side 17a) relative to the specific orientation of the computing device 10*. In other words, the inference or determination that the computing device 10* has been transferred from the first user 20 to the second user 30, for example, will not be made at least until it is determined that the eye or eyes of the second user 30 is determined to be in the proximate vicinity of the computing device 10* and is detected as being at one or more specified locations on the display side (e.g., the front side 17a) of the computing device 10*.
In various embodiments, the computing device 10* or at least the logic that may be endowed with the computing device 10* may be designed to detect and/or track absence or presence of one or more audio cues in the proximate vicinity of the computing device 10* in order to determine or at least infer as to whether the computing device 10* has been transferred from, for example, a first user 20 to a second user 30 (or vice versa). For example, in some embodiments, the computing device 10* may be endowed with voice verification system or application that may be designed to detect, via one or more audio capturing devices 306 (e.g., one or more microphones), a voice in the proximate vicinity of the computing device 10* having a voice pattern that may be different from the signature voice pattern of the first user 20. By making such a determination and/or by detecting absence for at least a predefined period of time of a voice pattern associated with the first user 20 in the proximate vicinity of the computing device 10*, an inference may be made that the computing device 10* has been transferred from, for example, the first user 20. In some embodiments, an inference may be made that the computing device 10* has been transferred from, for example, the first user 20 to the second user 30 when a voice pattern belonging to a person other than the first user 20 is detected in the proximate vicinity of the computing device 10* and is detected being originating from a point on the display side (e.g., the front side 17a) of the computing device 10*.
In some embodiments, the computing device 10* or at least the logic endowed with the computing device 10* may be designed to determine the transfer of the computing device 10* from the first user 20 to the second user 30 based on combination of one or more detected movements of the computing device 10*, one or more detected visual cues, and/or one or more detected audio cues. That is, since in many situations, a particular type of data or measurement (e.g., detected movements of the computing device 10* or detected visual cues in the proximate vicinity of the computing device 10*) may not reliably or conclusively indicate that the transfer of the computing device 10* from the first user 20 to the second user 30 has occurred, in various embodiments, the computing device 10* may make the determination as to whether the computing device 10* has been transferred based on different types of measurements (e.g., movements of the computing device 10*, visual cues, and/or audio cues).
As described earlier, in response to determining that the computing device 10* has been transferred from the first user 20 to the second user 30, the computing device 10* or at least the logic that may be endowed with the computing device 10* may selectively highlight one or more selective portions of the item that was being presented by the computing device 10* prior to the transfer of the computing device 10* from the first user 20 to the second user 30. In some cases, the one or more portions to be highlighted may be based, at least in part, to a selection made by a user, such as the first user 20, as to which portion or portions of the item are to be highlighted. Alternatively or additionally the selection of which portion or portions to be highlighted may be based on determining which portion or portions are associated with the second user 30. In order to make such a determination, the computing device 10* or its endowed logic may be designed to identify the second user 30 based on, for example, biometric data collected using one or more sensors 120. These concepts will be described in greater detail herein.
Referring now to
Referring now to
Turning now to
d illustrates yet another highlighted portion 702d (which again corresponds to paragraph 742 of
e and 7f illustrates how different portions of an example item 701b may be highlighted based on the determination that the computing device 10* has been transferred from the first user 20 to the second user 30 and in response to ascertaining which portion of the item is associated with which user (e.g., which portions being associated with the first user 20 and which portions being associated with the second user 30). Referring particularly now to
In response to a determination that the computing device 10* is in the control of or is being possessed by Freddy (e.g., first user 20), which could be based on detected biometric characteristics (e.g., face, eye, voice, movement, etc.) of Freddy in the proximate vicinity of the computing device 10*, only portion 720e of the example item 701b may be highlighted. That is, the computing device 10* may be endowed with logic that is able to automatically identify Freddy using, for example, sensors 120 that detect biometric characteristics of Freddy, and based on the identification as well as determining that Freddy has control (possession) of the computing device 10* and determining which portions of the item 701b are associated with Freddy (or his identity), the appropriate portion or portions of the item 701b may be highlighted.
After Freddy (e.g., first user 20) has signed the item 701b (e.g., electronic contract) at the portion 720e of the item 701b that has been highlighted, Freddy may then transfer or hand-off the computing device 10* to Mike Mouse (e.g., second user 30) so that Mike can sign the example item 701b. Turning now to
Referring now to
Note that the embodiments of the computing device 10* illustrated in
Referring particularly now to
In various embodiments, the transfer determining module 102′ of
Turning now to
Note that although
In various embodiments, the memory 114 of the computing device 10′ of
Turning now to
Referring now to
e illustrates the various types of sensors 120 that may be included with the computing device 10* (e.g., the computing device 10′ of
A more detailed discussion related to the computing device 10* of
Further, in
In any event, after a start operation, the operational flow 400 of
In addition to the transfer determining operation 402, operational flow 400 may include a highlighted portion presenting operation 404 for presenting, via the computing device, one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining. For instance, the highlighted portion presenting module 104* (e.g., the highlighted portion presenting module 104′ of
As will be further described herein, the transfer determining operation 402 and the highlighted portion presenting operation 404 of
As further illustrated in
In the same or different implementations, the transfer determining operation 402 may additionally or alternatively include an operation 504 for determining that the computing device has been transferred from the first user to the second user based, at least in part, on data provided by one or more sensors. For instance, the transfer determining module 102* of the computing device 10* of
Data from various types of sensors 120 may be used in order to determine whether the computing device 10* has been transferred. For example, and as further illustrated in
In the same or different implementations, operation 504 may include an operation 506 for determining that the computing device has been transferred from the first user to the second user based, at least in part, on data provided by one or more image capturing devices as further depicted in
In the same or alternative implementations, operation 504 may include an operation 507 for determining that the computing device has been transferred from the first user to the second user based, at least in part, on data provided by one or more audio capturing devices. For instance, the transfer determining module 102* of the computing device 10* of
In some cases, operation 504 may include an operation 508 for determining that the computing device has been transferred from the first user to the second user based, at least in part, on data provided by a combination of a movement sensor, an image capturing device, and/or an audio capturing device. For instance, the transfer determining module 102* of the computing device 10* of
In various implementations, the transfer determining operation 402 of
As further illustrated in
For example, a facial recognition system or application may be used in order to determine whether the face of the first user 20* is detected in the vicinity of the computing device 10* (e.g., in the visual range of a webcam or other types of image capturing devices 304 that may be part of the computing device 10*). In other cases, a voice recognition system or application may be used in order to determine whether the voice of the first user 20 is detected in the vicinity of the computing device 10*. In still other cases, other sensing or detecting means for detecting indicators (e.g., signature movements or vibration) that indicate the presence or absence of the first user 20 in the proximate vicinity (e.g., close vicinity) of the computing device 10* may be employed in order to determine whether the first user 20 has possession of the computing device 10*.
In some cases, operation 510 may, in turn, include an operation 511 for detecting that the computing device is no longer in a particular tilt orientation that the computing device was detected as having when the computing device was in the possession of the first user by at least detecting that the computing device has been reoriented from the particular tilt orientation to another tilt orientation that when detected at least suggests that the computing device has been transferred between at least two users as further depicted in
In the same or different implementations, operation 510 may include an operation 512 for detecting that the computing device is no longer in a particular tilt orientation that the computing device was detected as having when the computing device was in the possession of the first user by at least detecting that the computing device has been reoriented from the particular tilt orientation to another tilt orientation having an angular tilt that is at least a predefined percentage different from an angular tilt associated with the particular tilt orientation that the computing device was detected as having when the computing device was in the possession of the first user as further depicted in
In various implementations, the operation 509 for determining that the computing device has been transferred from the first user to the second user by at least detecting that the computing device has moved in a particular manner that when detected as occurring at least suggests that the computing device has been transferred between at least two users may involve detecting that the computing device 10* has at least been relocated away from a particular location. For example, in some implementations, operation 509 may include an operation 513 for detecting that the computing device has moved in the particular manner by at least detecting that the computing device is no longer at a particular spatial location that the computing device was detected as being located at when the computing device was in possession of the first user prior to said transfer as depicted in
In various implementations, operation 513 may include an operation 514 for detecting that the computing device is no longer at the particular spatial location that the computing device was detected as being located at when the computing device was in the possession of the first user prior to said transfer by at least detecting that the computing device has been relocated from the particular spatial location to another spatial location that when detected at least suggests that the computing device has been transferred from the first user to the second user. For instance, the spatial location detecting module 214 of the computing device 10* detecting that the computing device 10* is no longer at the particular spatial location 46 (see
In the same or different implementations, operation 513 may include an operation 515 for detecting that the computing device is no longer at a particular spatial location that the computing device was detected as being located at when the computing device was in the possession of the first user prior to said transfer by at least detecting that the computing device has been relocated from the particular spatial location to another spatial location that is at least a predefined distance away from the particular spatial location that the computing device was detected as being located at when the computing device was in the possession of the first user prior to said transfer. For instance, the spatial location detecting module 214 of the computing device 10* detecting that the computing device 10* is no longer at a particular spatial location (e.g., spatial location 46 of
Turning to
In the same or different implementations, operation 509 may include an operation 517 for detecting that the computing device has moved in the particular manner by at least detecting that the computing device has moved away from the first user. For instance, the particular movement detecting module 210 including the moving away detecting module 217 (see
In some implementations, operation 517 may further include an operation 518 for detecting that the computing device has moved away from the first user by at least detecting that the computing device has moved a predefined distance away from the first user. For instance, the moving away detecting module 217 of the computing device 10* detecting that the computing device 10* has moved away from the first user 20 by at least detecting that the computing device 10* has moved a predefined distance away from the first user 20. In doing so, the computing device 10* may filter out movements that may be considered “noise” (e.g., random or accidental relocation movements of the computing device 10* caused by, for example, the random or accidental movements of the first user 20 holding the computing device 10*).
In various embodiments, operation 509 may involve tracking or sensing one or more vibrations that may be exhibited by the computing device 10* through its physical contact with one or more users. That is, users may each be associated with different and relatively distinct signature vibration patterns (e.g., distinct heart rates). Thus, by detecting at least a change in vibration as exhibited by the computing device 10* as a result of, for example, the computing device 10* being passed from one user to another user, at least an inference may be made that a transfer of the computing device 10* has occurred. Thus, in various implementations, operation 509 may include an operation 519 for detecting that the computing device has moved in the particular manner by at least detecting that the computing device is no longer vibrating in a manner that matches with a vibration pattern that the computing device was detected as having when the computing device was in possession of the first user prior to said transfer as further illustrated in
As further illustrated in
In the same or different implementations, operation 509 may include an operation 521 for detecting that the computing device has moved in the particular manner by at least detecting that the computing device is not vibrating in a manner that matches with a signature vibration pattern that is associated with the first user. For instance, particular movement detecting module 210 including the vibration detecting module 218 of the computing device 10* determining that the computing device 10* has moved in a particular manner when the vibration detecting module 218 at least detects that the computing device 10* is not vibrating in a manner that matches with a signature vibration pattern that is associated with the first user 20.
Referring now to
As further illustrated in
In some cases, operation 523 may further include an operation 524 for detecting that the computing device is exhibiting one or more three-dimensional movements that matches with the one or more signature three-dimensional movements by detecting that the computing device is exhibiting one or more three-dimensional movements that matches with one or more signature three-dimensional movements that are particularly associated with the first user and that when detected as occurring at least suggests transfer of the computing device from the first user to another user. For instance, the three-dimensional movement detecting module 219 of the computing device 10* detecting that the computing device 10* is exhibiting one or more three-dimensional movements that matches with the one or more signature three-dimensional movements by detecting that the computing device 10* is exhibiting one or more three-dimensional movements that matches with one or more signature three-dimensional movements (e.g., as indicated in the movement library 170 of the memory 114) that are particularly associated with the first user 20 and that when detected as occurring at least suggests transfer of the computing device 10* from the first user 20 to another user (e.g., the second user 30).
In some implementations, the one or more signature three-dimensional movements of the computing device 10* may be the one or more signature movements of the computing device 10* that may be exhibited by the computing device 10* when the first user 20 is passing-off (e.g., transferring) the computing device 20 to another user. For these implementations, the computing device 10* may be endowed with logic that may allow the computing device 10* to detect and learn its own movements when the computing device 10* is being handed-off from the first user 20 to another user, and based on such detected/learned movements (e.g., signature movements) the computing device 10*(or its endowed logic) may determine or at least infer that the computing device 10* has been transferred from the first user 20 to another user whenever it detects movements that matches with the previously detected/learned movements. In various implementations, the movements of the computing device 10* may be monitored using one or more movements sensors 302 and/or one or more image capturing devices 304.
In the same or different implementations, operation 523 may include an operation 525 for detecting that the computing device is exhibiting one or more three-dimensional movements that matches with the one or more signature three-dimensional movements by detecting that the computing device is exhibiting one or more three-dimensional movements that matches with one or more generic signature three-dimensional movements that are not particularly associated with the first user and that when detected as occurring at least suggests transfer of the computing device between two users. For instance, the three-dimensional movement detecting module 219 of the computing device 10* detecting that the computing device 10* is exhibiting one or more three-dimensional movements that matches with the one or more signature three-dimensional movements by detecting that the computing device 10* is exhibiting one or more three-dimensional movements that matches with one or more generic signature three-dimensional movements that are not particularly associated with the first user 20 (e.g., one or more generic signature three-dimensional movements of the computing device 10* that are not associated with any specific user) and that when detected as occurring at least suggests transfer of the computing device 10* between two users.
Referring now to
As further illustrated in
In the same or different implementations, operation 526 may include an operation 528 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by detecting at least a change in lighting in the proximate vicinity of the computing device that when detected as occurring at least suggests that the computing device has at least moved. For instance, the visual cue detecting module 220 including the lighting change detecting module 221 (see
In some cases, operation 528 may further include an operation 529 for detecting at least the change in lighting in the proximate vicinity of the computing device by detecting at least a predefined amount of change in lighting in the proximate vicinity of the computing device within a predefined time period as further depicted in
In the same or different implementations, operation 526 may include an operation 530 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by at least detecting presence of at least one face in the proximate vicinity of the computing device not associated with the first user. For instance, the visual cue detecting module 220 including the face detecting module 222 (see
As further illustrated in
In some cases, operation 526 may alternatively or additionally include an operation 532 for detecting the presence or absence of the one or more visual cues in, the proximate vicinity of the computing device by at least detecting presence of a first face associated with the first user and a second face associated with the second user in the proximate vicinity of the computing device, the second face being detected as being closer to the computing device than the first face. For instance, the visual cue detecting module 220 including the face detecting module 222 of the computing device 10* detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device 10* when the face detecting module 222 at least detects presence of a first face associated with the first user 20 and a second face associated with the second user 30 in the proximate vicinity of the computing device 10*, the second face being detected as being closer to the computing device 10* than the first face of the first user 20. Note that in this particular implementation, the computing device 10* or at least the logic endowed with the computing device 10* may only need to recognize that the first face and the second face are two different faces belonging to, for example, two different users.
In the same or different implementations, operation 526 may include an operation 533 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by detecting presence of at least one eye in the proximate vicinity of the computing device not associated with the first user as further depicted in
In some cases operation 533 may further include an operation 534 for detecting the presence of the at least one eye in the proximate vicinity of the computing device not associated with the first user by at least detecting presence of at least one eye in the proximate vicinity of the computing device that is recognized as being associated with the second user. For instance, the eye detecting module 223 of the computing device 10* detecting the presence of the at least one eye in the proximate vicinity of the computing device 10* not associated with the first user 20 by at least detecting presence of at least one eye in the proximate vicinity of the computing device 10* that is recognized by, for example, the endowed logic of the computing device 10* as being associated with the second user 30. Thus, in some cases, the computing device 10* may store in its memory 114 images of eyes (e.g., images of irises or retinas) belonging to one or more users including, for example, the second user 30.
In the same or different implementations, operation 526 may include an operation 535 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by at least detecting presence of a first one or more eyes associated with the first user and a second one or more eyes associated with the second user in the proximate vicinity of the computing device, the second one or more eyes being detected as being closer to the computing device than the first one or more eyes as illustrated in
In the same or different implementations, operation 526 may include an operation 536 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by at least detecting absence of the one or more visual cues associated with the first user in the proximate vicinity of the computing device for at least a predefined period of time, the absence of the one or more visual cues for at least a predefined period of time being indicative of the first user not being in the proximate vicinity of the computing device as further illustrated in
As further illustrated in
In the same or different implementations, operation 536 may include an operation 538 for detecting the absence of the one or more visual cues associated with the first user in the proximate vicinity of the computing device by at least detecting absence of one or more eyes associated with the first user in the proximate vicinity of the computing device as further depicted in
In various implementations, operation 526 for determining that the computing device has been transferred from the first user to the second user by at least detecting presence or absence of one or more visual cues in proximate vicinity of the computing device that when detected as occurring at least suggests transfer of the computing device between two users may further include an operation 539 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by at least detecting visually that the computing device has moved away from the first user as further depicted in
Turning now to
As further illustrated in
In some cases, operation 541 may include an operation 542 for detecting visually the presence or absence of the one or more visual cues at the one or more specific locations relative to the front-side of the computing device by detecting visually at least disappearance of one or more features associated with the first user at the one or more specific locations relative to the front-side of the computing device. For instance, the visual cue detecting module 220 of the computing device 10* detecting visually the presence or absence of the one or more visual cues at the one or more specific locations (e.g., predefined locations) relative to the front-side 17a of the computing device 10* by detecting visually at least disappearance of one or more features (e.g., face or one or more eyes) associated with the first user 20 at the one or more specific locations (e.g., predefined locations) relative to the front-side 17a of the computing device 10*.
In some cases, operation 541 may include an operation 543 for detecting visually the presence or absence of the one or more visual cues at the one or more specific locations relative to the front-side of the computing device by detecting visually at least appearance of one or more features associated with the second user at the one or more specific locations relative to the front-side of the computing device. For instance, the visual cue detecting module 220 of the computing device 10* detecting visually the presence or absence of the one or more visual cues at the one or more specific locations relative to the front-side 17a of the computing device 10* by detecting visually at least appearance of one or more features (e.g., a face or one or more eyes) associated with the second user 30 at the one or more specific locations relative to the front-side 17a of the computing device 10*. As those of ordinary skill will recognize, the visual detection of the second user 30 (e.g., the face or one or more eyes of the second user 30) in the proximate vicinity (e.g., immediate surrounding area such as within three, four, or five feet) of the computing device 10* may be in many cases a better indicator that the computing device 10* has been transferred to the second user 30 than the detection of the absence of the first user 20 (e.g., the face or one or more eyes of the first user 20) in the proximate vicinity of the computing device 10*.
In some implementations, operation 426 may include an operation 544 for detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device by at least detecting visually one or more gestures exhibited by the first user that when detected as occurring at least suggests transfer of the computing device from the first user to another user. For instance, the visual cue detecting module 220 including the gesture detecting module 225 of the computing device 10* detecting the presence or absence of the one or more visual cues in the proximate vicinity of the computing device 10* when the gesture detecting module 225 detecting visually one or more gestures exhibited by the first user 20 (e.g., the first user 20 extending his/her arm out as if to offer/transfer the computing device 10* to the second user 30) that when detected as occurring at least suggests transfer of the computing device 10* from the first user 20 to another user 30.
Turning now to
As further illustrated in
In the same or different implementations, operation 545 may additionally or alternatively include an operation 547 for detecting the presence or absence of the one or more audio cues in the proximate vicinity of the computing device by at least detecting presence of at least one audio voice pattern not associated with the first user in the proximate vicinity of the computing device. For instance, the audio cue detecting module 226 including the voice pattern detecting module 228 (see
In some implementations, operation 547 may further include an operation 548 for detecting the presence of the at least one audio voice pattern not associated with the first user in the proximate vicinity of the computing device by at least detecting presence of at least one audio voice pattern that is recognized as being associated with the second user in the proximate vicinity of the computing device. For instance, the voice pattern detecting module 228 of the computing device 10* detecting the presence of the at least one audio voice pattern not associated with the first user 20 in the proximate vicinity of the computing device 10* by at least detecting presence of at least one audio voice pattern that is recognized by, for example, the endowed logic of the computing device 10* as being associated with the second user 30 in the proximate vicinity of the computing device 10*.
In various implementations, the transfer determining operation 402 of
As further illustrated in
In some alternative implementations, the transfer determining operation 402 may include an operation 551 for determining that the computing device has been transferred from the first user to the second user by detecting presence or absence of one or more visual cues in the proximate vicinity of the computing device and by detecting presence or absence of one or more audio cues in proximate vicinity of the computing device as depicted in
As further illustrated in
In the same or different implementations, the transfer determining operation 402 may include an operation 553 for determining that the computing device has been transferred from the first user to the second user by determining that the computing device that was presenting at least one portion of the item and that was determined to be located proximate to and having a particular orientation relative to the first user has been transferred from the first user to the second user. For instance, the transfer determining module 102* of the computing device 10* determining that the computing device 10* has been transferred from the first user 20 to the second user 30 by determining that the computing device 10* that was presenting at least one portion of the item and that was determined to be located proximate to (e.g., within five feet) and having a particular orientation relative to the first user 20 (e.g., front-side 17a facing the first user 20) has been transferred from the first user 20 to the second user 30.
In the same or different implementations, the transfer determining operation 402 may include an operation 554 for determining that the computing device that was presenting the item has been transferred from the first user to the second user by determining that the computing device that was presenting an open or active item and that was in possession of the first user has been transferred from the first user to the second user. For instance, the transfer determining module 102* of the computing device 10* determining that the computing device 10* that was presenting the item has been transferred from the first user 20 to the second user 30 by determining that the computing device 10* that was presenting an open or active item (e.g., an open electronic document or file, an open website, an active application, and so forth) and that was in possession of the first user 20 has been transferred from the first user 20 to the second user 30.
In the same or different implementations, the transfer determining operation 402 may include an operation 555 for determining that the computing device that was presenting the item has been transferred from the first user to the second user by determining that the computing device that was visually and/or audibly presenting an electronic item has been transferred from the first user to the second user. For instance, the transfer determining module 102* of the computing device 10* determining that the computing device 10* that was presenting the item has been transferred from the first user 20 to the second user 30 by determining that the computing device 10* that was visually and/or audibly presenting an electronic item (e.g., a digital book, a video file such as a feature movie, an email, and so forth) has been transferred from the first user 20 to the second user 30.
In some cases, operation 555 may further include an operation 556 for determining that the computing device that was visually and/or audibly presenting the electronic item has been transferred from the first user to the second user, the electronic item being one of an electronic document, an electronic file, or an electronic message. For instance, the transfer determining module 102* of the computing device 10* determining that the computing device 10* that was visually and/or audibly presenting the electronic item has been transferred from the first user 20 to the second user 30, the electronic item being one of an electronic document (e.g., a productivity document such as a word processing or spreadsheet document), an electronic file (e.g., electronic photo album), or an electronic message (e.g., email or text message).
Referring now to
As further illustrated in
In some implementations, operation 558 may further include an operation 559 for identifying biometrically the second user based on one or more movement characteristics, one or more facial characteristics, one or more retinal characteristics, and/or one or more voice characteristics of the second user. For instance, the biometric user identifying module 232 of the computing device 10* identifying biometrically the second user 30 based on one or more movement characteristics (e.g., as sensed by, for example, one or more movement sensors 302), one or more facial characteristics (e.g., as sensed by one or more image capturing devices 304), one or more retinal characteristics (e.g., as sensed by one or more image capturing devices 304), and/or one or more voice characteristics of the second user 30 (e.g., as sensed by one or more audio capturing devices 306).
In various implementations, operation 557 may include an operation 560 for identifying the second user based on data provided by one or more movement sensors, one or more image capturing devices, and/or one or more audio capturing devices. For instance, the user identifying module 230 of the computing device 10* identifying the second user 30 based on data provided by one or more movement sensors 302, one or more image capturing devices 304, and/or one or more audio capturing devices 306.
Referring back to the highlighted portion presenting operation 404 of
In the same or alternative implementations, the highlighted portion presenting operation 404 of
As further illustrated in
In the same or different implementations, operation 662 may include an operation 664 for presenting the one or more highlighted portions with the one or more unhighlighted portions of the item by presenting the one or more highlighted portions having one or more color and/or brightness schemes that are different from one or more color and/or brightness schemes of the one or more unhighlighted portions. For instance, the highlighted portion presenting module 104* including the unhighlighted portion presenting module 234 of the computing device 10* presenting the one or more highlighted portions 702* with the one or more unhighlighted portions 704* of the item 701* by presenting the one or more highlighted portions 702* having one or more color and/or brightness schemes (e.g., increased brightness or different color or colors for the background of the highlighted portion or portions 702*) that are different from one or more color and/or brightness schemes of the one or more unhighlighted portions 704*.
In the same or different implementations, operation 662 may include an operation 665 for presenting the one or more highlighted portions with the one or more unhighlighted portions of the item by presenting the one or more highlighted portions that include one or more backgrounds that are different from one or more backgrounds of the one or more unhighlighted portions. For instance, the highlighted portion presenting module 104* including the unhighlighted portion presenting module 234 of the computing device 10* presenting the one or more highlighted portions 702* with the one or more unhighlighted portions 704* of the item 701* by presenting the one or more highlighted portions 702* that include one or more backgrounds (e.g., having different background color or pattern) that are different from one or more backgrounds of the one or more unhighlighted portions 704*.
In the same or different implementations, operation 662 may include an operation 666 for presenting the one or more highlighted portions with the one or more unhighlighted portions of the item by presenting the one or more highlighted portions that include one or more audio schemes that are different from one or more audio schemes of the one or more unhighlighted portions. For instance, the highlighted portion presenting module 104* including the unhighlighted portion presenting module 234 of the computing device 10* presenting the one or more highlighted portions 702* with the one or more unhighlighted portions 704* of the item 701* by presenting the one or more highlighted portions 702* that include one or more audio schemes (e.g., increase audio volume or more bass) that are different from one or more audio schemes of the one or more unhighlighted portions 704*.
In the same or different implementations, operation 662 may include an operation 667 for presenting the one or more highlighted portions with the one or more unhighlighted portions of the item by presenting the one or more highlighted portions that are encircled by one or more boarders. For instance, the highlighted portion presenting module 104* including the unhighlighted portion presenting module 234 of the computing device 10* presenting the one or more highlighted portions 702* with the one or more unhighlighted portions 704* of the item 701* by presenting the one or more highlighted portions 702* that are encircled by one or more boarders 706 (see
In the same or different implementations, operation 662 may include an operation 668 for presenting the one or more highlighted portions with the one or more unhighlighted portions of the item, the one or more highlighted portions having been previously presented prior to said transfer of the computing device from the first user to the second user in one or more unhighlighted formats. For instance, the highlighted portion presenting module 104* including the unhighlighted portion presenting module 234 of the computing device 10* presenting the one or more highlighted portions 702* with the one or more unhighlighted portions 704* of the item 701*, the one or more highlighted portions 702* having been previously presented prior to said transfer of the computing device 10* from the first user 20 to the second user 30 in one or more unhighlighted formats.
In the same or different implementations, operation 662 may include an operation 669 for presenting the one or more highlighted portions with the one or more unhighlighted portions of the item by presenting the one or more highlighted portions that are displayed at a greater brightness than the one or more unhighlighted portions. For instance, the highlighted portion presenting module 104* including the unhighlighted portion presenting module 234 of the computing device 10* presenting the one or more highlighted portions 702* with the one or more unhighlighted portions 704* of the item 701* by presenting the one or more highlighted portions 702* that are displayed via, for example, a display device 12 at a greater brightness than the one or more unhighlighted portions 704*.
In some cases the one or more highlighted portions 702* of the item 701* to be presented through the highlighted portion presenting operation 404 of
As further illustrated in
Operation 671, in turn, may include an operation 672 for presenting the one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining and in response to being selected for highlighting by the first user prior to the transfer of the computing device from the first user to the second user, the first user having provided the selection by selecting from the item one or more portions for highlighting through a user interface in some implementations. For instance, the highlighted portion presenting module 104* of the computing device 10* presenting the one or more highlighted portions 702* of the item 701*, the one or more highlighted portions 702* being highlighted in response, at least in part, to determining that the computing device 10* has been transferred from the first user 20 to the second user 30 and in response to being selected for highlighting by the first user 20 as detected by, for example, the highlighting selection detecting module 106* prior to the transfer of the computing device 10* from the first user 20 to the second user 30, the first user 20 having provided the selection by selecting from the item 701b one or more portions (e.g., highlighted portions 702* prior to transfer) for highlighting through a user interface 110 (e.g., a touch screen, a keypad or a keyboard, a mouse, and so forth).
In some cases, operation 672 may further include an operation 673 for presenting the one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining and in response to being selected for highlighting by the first user prior to the transfer of the computing device from the first user to the second user, the first user having provided the selection by having designated the one or more portions of the item for highlighting via a touch screen. For instance, the highlighted portion presenting module 104* of the computing device 10* presenting the one or more highlighted portions 702* of the item 701*, the one or more highlighted portions 702* being highlighted in response, at least in part, to determining that the computing device 10* has been transferred from the first user 20 to the second user 30 and in response to being selected for highlighting by the first user 20* as detected by, for example, the highlighting selection detecting module 106* prior to the transfer of the computing device 10* from the first user 20 to the second user 30, the first user 20 having provided the selection by having designated the one or more portions of the item 701* for highlighting via a touch screen (e.g., display device 12). In various implementations, the first user 20 may select one or more portions of an item 701* for highlighting by simply marking (e.g., tagging) the one or more portions to be highlighted via, for example, a touch screen. The marking of the one or more portions may be by, for example, circling 710, checking or x-ing 712, writing a line 714, next to the portion to be highlighted, and so forth as illustrated in
For example, in some cases, operation 672 may include an operation 674 for presenting the one or more highlighted portions of the item, the one or more highlighted portions being highlighted in response, at least in part, to said determining and in response to being selected for highlighting by the first user prior to the transfer of the computing device from the first user to the second user, the first user having provided the selection by only tagging one or more parts respectively of the one or more portions of the item through a display device, the one or more portions being entirely highlighted in response to the marking of the one or more parts of the one or more portions. For instance, the highlighted portion presenting module 104* of the computing device 10* presenting the one or more highlighted portions 702* of the item 701*, the one or more highlighted portions 702* being highlighted in response, at least in part, to determining that the computing device 10* has been transferred from the first user 20 to the second user 30 and in response to being selected for highlighting by the first user 20 as detected by, for example, the highlighting selection detecting module 106* prior to the transfer of the computing device 10* from the first user 20 to the second user 30, the first user 20 having provided the selection by only tagging (e.g., marking by writing a check marking, clicking, tapping, etc.) one or more parts respectively of the one or more portions of the item 702* through a display device 12, the one or more portions being entirely highlighted in response to the marking of the one or more parts of the one or more portions. In other words, if the first user 20 wishes to highlight certain portions of an item 702* after the computing device 10* has been transferred to the second user 30, then the first user 20 may merely mark or tag only part of the portion to be highlighted by simply writing, tapping, or clicking only part of the portion of the item to be highlighted. Thus, in some cases, an item 701* may be divided into multiple portions. For example, in the example item 701a, each of the illustrated paragraphs may be distinct portions of the item 701b. A user, such as first user 20, may select a particular portion for highlighting merely by writing a check mark (e.g., or clicking or tapping via a touch screen) only a small part of the portion to be highlighted.
In some cases, the highlighted portion presenting operation 404 of
As further illustrated in 6c, in various implementations, operation 675 may include one or more additional operations in various alternative implementations. For example, in some implementations, operation 675 may include an operation 676 for ascertaining that the one or more portions of the item that are to be highlighted are specifically associated with the second user by ascertaining that the one or more portions of the items that are to be highlighted being specifically associated with identity of the second user. For instance, the user association ascertaining module 236 including the user identity association ascertaining module 238 (see
In some cases, operation 676 may in turn include an operation 677 for ascertaining that the one or more portions of the items that are to be highlighted are specifically associated with identity of the second user by identifying the second user based, at least in part, on one or more biometric characteristics of the second user as sensed by one or more sensors. For instance, the user identity association ascertaining module 238 including the user identifying module 240 (see
In some implementations, operation 677 may include an operation 678 for identifying the second user based, at least in part, on the one or more biometric characteristics of the second user by identifying the second user based, at least in part, on one or more movement characteristics of the second user as sensed by one or more movement sensors. For instance, the user identifying module 240 of the computing device 10* identifying the second user 30* based, at least in part, on the one or more biometric characteristics of the second user 30 by identifying the second user 30 based, at least in part, on one or more movement characteristics (e.g., signature movements including, for example, signature heart or pulse vibration or signature gestures) of the second user 30 as sensed by one or more movement sensors 302.
In some implementations, operation 677 may include an operation 679 for identifying the second user based, at least in part, on one or more biometric characteristics of the second user by identifying the second user based, at least in part, on one or more facial or retinal characteristics of the second user as sensed by one or more image capturing devices. For instance, the user identifying module 240 of the computing device 10* identifying the second user 30* based, at least in part, on one or more biometric characteristics of the second user 30 by identifying the second user 30 based, at least in part, on one or more facial or retinal characteristics of the second user 30 as sensed by one or more image capturing devices 304.
In some implementations, operation 677 may include an operation 680 for identifying the second user based, at least in part, on one or more biometric characteristics of the second user by identifying the second user based, at least in part, on one or more voice characteristics of the second user as sensed by one or more audio capturing devices. For instance, the user identifying module 240 of the computing device 10* identifying the second user 30* based, at least in part, on one or more biometric characteristics of the second user 30 by identifying the second user 30 based, at least in part, on one or more voice characteristics (e.g., signature voice pattern) of the second user 30 as sensed by one or more audio capturing device 306.
In some implementations, operation 677 may include an operation 681 for identifying the second user based, at least in part, on one or more biometric characteristics of the second user by identifying the second user based, at least in part, on one or more biometric characteristics of the second user as sensed by two or more combinations of a movement sensor, an image capturing device, and/or an audio capturing device. For instance, the user identifying module 240 of the computing device 10* identifying the second user 30* based, at least in part, on one or more biometric characteristics of the second user 30 by identifying the second user 30 based, at least in part, on one or more biometric characteristics of the second user 30 as sensed by at least two or more combinations of a movement sensor 302, an image capturing device 304, and/or an audio capturing device 306.
Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems and/or other technologies described herein can be effected (e.g., hardware, software, and/or firmware in one or more machines or articles of manufacture), and that the preferred vehicle will vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation that is implemented in one or more machines or articles of manufacture; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware in one or more machines or articles of manufacture. Hence, there are several possible vehicles by which the processes and/or devices and/or other technologies described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware in one or more machines or articles of manufacture.
The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuitry (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuitry, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
In a general sense, those skilled in the art will recognize that the various aspects described herein which can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof can be viewed as being composed of various types of “electrical circuitry.” Consequently, as used herein “electrical circuitry” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment). Those having skill in the art will recognize that the subject matter described herein may be implemented in an analog or digital fashion or some combination thereof.
Those having skill in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system generally includes one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. Furthermore, it is to be understood that the invention is defined by the appended claims.
It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations.
In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).
In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
The present application is related to and claims the benefit of the earliest available effective filing date(s) from the following listed application(s) (the “Related applications”) (e.g., claims earliest available priority dates for other than provisional patent applications or claims benefits under 35 USC §119(e) for provisional patent applications, for any and all parent, grandparent, great-grandparent, etc. applications of the Related application(s)). All subject matter of the Related applications and of any and all parent, grandparent, great-grandparent, etc. applications of the Related applications, including any priority claims, is incorporated herein by reference to the extent such subject matter is not inconsistent herewith. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/065,885, entitled ACCESS RESTRICTION IN RESPONSE TO DETERMINING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 30 Mar. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/065,964, entitled ACCESS RESTRICTION IN RESPONSE TO DETERMINING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 31 Mar. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/066,848, entitled PROVIDING GREATER ACCESS TO ONE OR MORE ITEMS IN RESPONSE TO DETERMINING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 25 Apr. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/066,917, entitled PROVIDING GREATER ACCESS TO ONE OR MORE ITEMS IN RESPONSE TO DETERMINING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 26 Apr. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/135,314, entitled PROVIDING PARTICULAR LEVEL OF ACCESS TO ONE OR MORE ITEMS IN RESPONSE TO DETERMINING PRIMARY CONTROL OF A COMPUTING DEVICE, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 29 Jun. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/135,392, entitled PROVIDING PARTICULAR LEVEL OF ACCESS TO ONE OR MORE ITEMS IN RESPONSE TO DETERMINING PRIMARY CONTROL OF A COMPUTING DEVICE, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 30 Jun. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/199,237, entitled SELECTIVE ITEM ACCESS PROVISION IN RESPONSE TO ACTIVE ITEM ASCERTAINMENT UPON DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 22 Aug. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/199,286, entitled SELECTIVE ITEM ACCESS PROVISION IN RESPONSE TO ACTIVE ITEM ASCERTAINMENT UPON DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 23 Aug. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/200,743, entitled PROVIDING GREATER ACCESS TO ONE OR MORE ITEMS IN RESPONSE TO VERIFYING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 28 Sep. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/200,800, entitled PROVIDING GREATER ACCESS TO ONE OR MORE ITEMS IN RESPONSE TO VERIFYING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 29 Sep. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/317,827, entitled PRESENTATION FORMAT SELECTION BASED AT LEAST ON DEVICE TRANSFER DETERMINATION, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 27 Oct. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/317,832, entitled PRESENTATION FORMAT SELECTION BASED AT LEAST ON DEVICE TRANSFER DETERMINATION, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 28 Oct. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/373,679, entitled ASCERTAINING PRESENTATION FORMAT BASED ON DEVICE PRIMARY CONTROL DETERMINATION, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 23 Nov. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/373,796, entitled ASCERTAINING PRESENTATION FORMAT BASED ON DEVICE PRIMARY CONTROL DETERMINATION, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 29 Nov. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. To Be Assigned, entitled MARKING ONE OR MORE ITEMS IN RESPONSE TO DETERMINING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 8 Dec. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. To Be Assigned, entitled MARKING ONE OR MORE ITEMS IN RESPONSE TO DETERMINING DEVICE TRANSFER, naming Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene as inventors, filed 14 Dec. 2011, which is currently co-pending or is an application of which a currently co-pending application is entitled to the benefit of the filing date. The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation, continuation-in-part, or divisional of a parent application. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTO Official Gazette Mar. 18, 2003. The present Applicant Entity (hereinafter “Applicant”) has provided above a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization, such as “continuation” or “continuation-in-part,” for claiming priority to U.S. patent applications. Notwithstanding the foregoing, Applicant understands that the USPTO's computer programs have certain data entry requirements, and hence Applicant has provided designation(s) of a relationship between the present application and its parent application(s) as set forth above, but expressly points out that such designation(s) are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).
Number | Date | Country | |
---|---|---|---|
Parent | 13065885 | Mar 2011 | US |
Child | 13374479 | US | |
Parent | 13065964 | Mar 2011 | US |
Child | 13065885 | US | |
Parent | 13066848 | Apr 2011 | US |
Child | 13065964 | US | |
Parent | 13066917 | Apr 2011 | US |
Child | 13066848 | US | |
Parent | 13135314 | Jun 2011 | US |
Child | 13066917 | US | |
Parent | 13135392 | Jun 2011 | US |
Child | 13135314 | US | |
Parent | 13199237 | Aug 2011 | US |
Child | 13135392 | US | |
Parent | 13199286 | Aug 2011 | US |
Child | 13199237 | US | |
Parent | 13200743 | Sep 2011 | US |
Child | 13199286 | US | |
Parent | 13200800 | Sep 2011 | US |
Child | 13200743 | US | |
Parent | 13317827 | Oct 2011 | US |
Child | 13200800 | US | |
Parent | 13317832 | Oct 2011 | US |
Child | 13317827 | US | |
Parent | 13373679 | Nov 2011 | US |
Child | 13317832 | US | |
Parent | 13373796 | Nov 2011 | US |
Child | 13373679 | US | |
Parent | 13374352 | Dec 2011 | US |
Child | 13373796 | US |