Behavioral fingerprinting via social networking interaction
Summary by NHIP
Family Relation Fingerprinting System
The system receives transaction data and obtains family relation indications via social networking interactions to create behavioral fingerprints. It acquires hardware-based sensor locations from other authorized users to determine physical proximity and approves transactions based on that proximity.
Claim Score by NHIP
Abstract
Disclosed herein are example embodiments for behavioral fingerprinting via social networking interaction. For certain example embodiments, at least one indication of family relation for at least one authorized user may be obtained via at least one social networking interaction, and the at least one indication of family relation may be incorporated into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user.

Term
Projected expiry 23 November 2031.
- Priority
- Filed
- Granted
- Today
- Projected expiry
44 claims: 3 independent, 41 dependent
- 1Broadest claimClaim Score 37, narrow(NHIP)A system, comprising:circuitry configured for receiving at least one indication of at least one transaction conducted at least partially via at least one user device associated with at least one authorized user, including at least receiving at least one location of the at least one user device associated with the at least one authorized user;circuitry configured for obtaining at least one indication of a relation between the at least one authorized user and at least one other authorized user via at least one social networking interaction;circuitry configured for acquiring at least one location indicated by at least one hardware-based position sensor of at least one user device associated with the at least one other authorized user;circuitry configured for determining at least one indication of physical proximity between the at least one authorized user and the at least one other authorized user based at least partially on the at least one location of the at least one user device associated with the at least one authorized user and the at least one location indicated by the at least one hardware-based position sensor of the at least one user device associated with the at least one other authorized user;and circuitry configured for approving the at least one transaction conducted at least partially via the at least one user device associated with the at least one authorized user based at least partially on the at least one indication of physical proximity between the at least one authorized user and the at least one other authorized user, including at least approving the at least one transaction conducted at least partially via the at least one user device associated with the at least one authorized user if the at least one indication of physical proximity indicates that the at least one user device associated with the at least one other authorized user is within at least one approved proximity of the at least one user device associated with the at least one authorized user.
- 2A system, comprising:at least one computing device;and one or more instructions which, when executed on the at least one computing device, cause the at least one computing device to perform one or more operations including at least: receiving at least one indication of at least one transaction conducted at least partially via at least one user device associated with at least one authorized user, including at least receiving at least one location of the at least one user device associated with the at least one authorized user;obtaining at least one indication of a relation between the at least one authorized user and at least one other authorized user via at least one social networking interaction;acquiring at least one location indicated by at least one hardware-based position sensor of the at least one user device associated with the at least one other authorized user;determining at least one indication of physical proximity between the at least one authorized user and the at least one other authorized user based at least partially on the at least one location of the at least one user device associated with the at least one authorized user and the at least one location indicated by the at least one hardware-based position sensor of the at least one user device associated with the at least one other authorized user;and approving the at least one transaction conducted at least partially via the at least one user device associated with the at least one authorized user based at least partially on the at least one indication of physical proximity between the at least one authorized user and the at least one other authorized user, including at least approving the at least one transaction conducted at least partially via the at least one user device associated with the at least one authorized user if the at least one indication of physical proximity indicates that the at least one user device associated with the at least one other authorized user is within at least one approved proximity of the at least one user device associated with the at least one authorized user.
- 3A method, comprising:receiving at least one indication of at least one transaction conducted at least partially via at least one user device associated with at least one authorized user, including at least receiving at least one location of the at least one user device associated with the at least one authorized user;obtaining at least one indication of a relation between the at least one authorized user and at least one other authorized user via at least one social networking interaction;acquiring at least one location indicated by at least one hardware-based position sensor of the at least one user device associated with the at least one other authorized user;determining at least one indication of physical proximity between the at least one authorized user and the at least one other authorized user based at least partially on the at least one location of the at least one user device associated with the at least one authorized user and the at least one location indicated by the at least one hardware-based position sensor of the at least one user device associated with the at least one other authorized user;and approving the at least one transaction conducted at least partially via the at least one user device associated with the at least one authorized user based at least partially on the at least one indication of physical proximity between the at least one authorized user and the at least one other authorized user, including at least approving the at least one transaction conducted at least partially via the at least one user device associated with the at least one authorized user if the at least one indication of physical proximity indicates that the at least one user device associated with the at least one other authorized user is within at least one approved proximity of the at least one user device associated with the at least one authorized user, wherein at least one of the receiving, obtaining, acquiring, determining, or approving is at least partially implemented using at least one processing device.
Independent claims3
170 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001The present application is related to and/or claims the benefit of the earliest available effective filing date(s) from the following listed application(s) (the “Priority Applications”), if any, listed below (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 Priority Application(s)). In addition, the present application is related to the “Related Applications,” if any, listed below.
PRIORITY APPLICATIONS
0000<ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0002">(1) For purposes of the USPTO extra-statutory requirements, the present application claims benefit of priority of U.S. Provisional Patent Application No. 61/632,836, entitled “Behavioral Fingerprint Based Authentication”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and Clarence T. Tegreene as inventors, filed 24 Sep. 2011, which was filed within the twelve months preceding the filing date of the present application or is an application of which a currently co-pending application is entitled to the benefit of the filing date.</li><li id="ul0002-0002" num="0003">(2) For purposes of the USPTO extra-statutory requirements, the present application claims benefit of priority of U.S. Provisional Patent Application No. 61/572,309, entitled “Network Acquired Behavioral Fingerprint for Authentication”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and Clarence T. Tegreene as inventors, filed 13 Oct. 2011, which was filed within the twelve months preceding the filing date of the present application or is an application of which a currently co-pending application is entitled to the benefit of the filing date.</li><li id="ul0002-0003" num="0004">(3) 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,685, entitled “Behavioral Fingerprint Device Identification”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and 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.</li><li id="ul0002-0004" num="0005">(4) 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,684, entitled “Behavioral Fingerprint Controlled Automatic Task Determination”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and 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.</li><li id="ul0002-0005" num="0006">(5) 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,680, entitled “Behavioral Fingerprint Controlled Theft Detection and Recovery”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and 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.</li><li id="ul0002-0006" num="0007">(6) 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,677, entitled “Trust Verification Schema Based Transaction Authorization”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and 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.</li><li id="ul0002-0007" num="0008">(7) 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,682, entitled “Social Network Based Trust Verification Schema”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and 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.</li><li id="ul0002-0008" num="0009">(8) For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/475,564, entitled “Behavioral Fingerprint Based Authentication”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and Clarence T. Tegreene as inventors, filed 18 May 2012, 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.</li><li id="ul0002-0009" num="0010">(9) For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/538,385, entitled “Network Acquired Behavioral Fingerprint for Authentication”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and Clarence T. Tegreene as inventors, filed 29 Jun. 2012, 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.</li><li id="ul0002-0010" num="0011">(10) For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/552,502, entitled “Relationship Based Trust Verification Schema”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and Clarence T. Tegreene as inventors, filed 18 Jul. 2012, 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.</li><li id="ul0002-0011" num="0012">(11) For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 13/563,599, entitled “Multi-Device Behavioral Fingerprinting”, naming Marc E. Davis, Matthew G. Dyor, Daniel A. Gerrity, Xuedong (XD) Huang, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud, Nathan Myhrvold, and Clarence T. Tegreene as inventors, filed 31 Jul. 2012, 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.</li></ul></li></ul>
RELATED APPLICATIONS
0013None
0014The 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 USPTO further has provided forms for the Application Data Sheet which allow automatic loading of bibliographic data but which require identification of each application as a continuation, continuation-in-part, or divisional of a parent application. 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 and in any ADS filed in this application, but expressly points out that such designations 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).
0015If the listings of applications provided above are inconsistent with the listings provided via an ADS, it is the intent of the Applicant to claim priority to each application that appears in the Priority Applications section of the ADS and to each application that appears in the Priority Applications section of this application.
0016All subject matter of the Priority Applications and the Related Applications and of any and all parent, grandparent, great-grandparent, etc. applications of the Priority Applications and the Related Applications, including any priority claims, is incorporated herein by reference to the extent such subject matter is not inconsistent herewith.
BRIEF DESCRIPTION OF THE FIGURES
0017<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram of a user device, a server device, and at least one behavioral fingerprint, any of which may be involved individually or jointly in example authentication scenarios in accordance with certain example embodiments.
0018<figref idref="DRAWINGS">FIG. 2A</figref> is a schematic diagram of multiple user devices, multiple server devices, and at least one behavioral fingerprint, any of which may be involved individually or jointly in example authentication scenarios in accordance with certain example embodiments.
0019<figref idref="DRAWINGS">FIG. 2B</figref> is a schematic diagram of multiple user devices, multiple server devices, and multiple example locations for at least a portion of at least one behavioral fingerprint in accordance with certain example embodiments.
0020<figref idref="DRAWINGS">FIG. 3</figref> is a schematic diagram illustrating an example behavioral fingerprint including one or more example indicators of one or more behavior-related acts in accordance with certain example embodiments.
0021<figref idref="DRAWINGS">FIG. 4</figref> is a schematic diagram of an example user device including one or more example components in accordance with certain example embodiments.
0022<figref idref="DRAWINGS">FIG. 5</figref> is a schematic diagram of an example server device including one or more example components in accordance with certain example embodiments.
0023<figref idref="DRAWINGS">FIGS. 6A and 6B</figref> are schematic diagrams of an example user device and an example server device, respectively, that have one or more functional units in accordance with certain example embodiments.
0024<figref idref="DRAWINGS">FIG. 7A</figref> is a schematic diagram that includes at least one example device that is capable of handling scenarios for behavioral fingerprinting via social networking interaction in accordance with certain example embodiments.
0025<figref idref="DRAWINGS">FIGS. 7B-C</figref> are schematic diagrams that include at least one example device and that depict example scenarios for implementing behavioral fingerprinting via social networking in accordance with certain example embodiments.
0026<figref idref="DRAWINGS">FIG. 8A</figref> is a flow diagram illustrating an example method for at least one device with regard to behavioral fingerprinting via social networking in accordance with certain example embodiments.
0027<figref idref="DRAWINGS">FIGS. 8B-8M</figref> depict example additions or alternatives for a flow diagram of <figref idref="DRAWINGS">FIG. 8A</figref> in accordance with certain example embodiments.
0028<figref idref="DRAWINGS">FIGS. 9A-9G</figref> depict example additions or alternatives for a flow diagram of <figref idref="DRAWINGS">FIG. 8A</figref> in accordance with certain example embodiments.
DETAILED DESCRIPTION
0029In 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.
0030<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram <b>100</b> of a user device, a server device, and at least one behavioral fingerprint, any of which may be involved individually or jointly in example authentication scenarios in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, by way of example but not limitation, schematic diagram <b>100</b> may include at least one user device <b>102</b>, at least one user <b>104</b>, at least one network <b>106</b>, at least one channel <b>108</b>, at least one behavioral fingerprint <b>110</b>, or at least one server device <b>112</b>. More specifically, at least one channel <b>108</b> may extend from or lead to a device <b>102</b> or <b>112</b> to facilitate communication therewith.
0031For certain example embodiments, a user <b>104</b> may correspond to or be utilizing at least one user device <b>102</b>. A user <b>104</b> may utilize a user device <b>102</b> in accordance with a usage that may be at least partially represented by, modeled by, incorporated into, stored at, tracked by, summarized in, a combination thereof, etc. at least one behavioral fingerprint <b>110</b>. A user device <b>102</b> may comprise, by way of example but not limitation, a mobile phone, a smart phone, a mobile terminal, a laptop or notebook computer, a personal digital assistant (PDA), a netbook, an entertainment appliance (e.g., a television, a gaming console, a set-top box, a music player, a combination thereof, etc.), a portable gaming device, a user equipment, a tablet or slate computer, a desktop computer, a personal navigation device (PND), a vehicle with user-accessible computational capabilities, videoconferencing equipment, some combination thereof, or so forth. A user <b>104</b> may comprise, by way of example only, at least one person, a couple, siblings, a family, a partnership, an organizational group, a company, a robotic user (e.g., a computational entity), an electronic agent, a portion thereof, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0032For certain example embodiments, a network <b>106</b> may comprise, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. A network may comprise, by way of example but not limitation, one or more of: a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a public-switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, some combination thereof, or so forth. A node may comprise, by way of example but not limitation, a server; a router; an end user device, such as a mobile phone, a tablet computer, a desktop computer, an entertainment appliance, a vehicle, a combination thereof, etc.; a switch; a base station; a gateway; some combination thereof; or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0033For certain example embodiments, a channel <b>108</b> may comprise, by way of example but not limitation, one or more of: at least one wired link, at least one wireless link, at least part of public network, at least part of a private network, at least part of a packet-switched network, at least part of a circuit-switched network, at least part of an infrastructure network, at least part of an ad hoc network, at least part of a PSTN, at least part of a cable network, at least part of a cellular network connection, at least part of an Internet connection, at least part of a Wi-Fi connection, at least part of a WiMax connection, at least part of an internet backbone, at least part of a satellite network, at least part of a fiber optic network, multiple instances of any of the above, one or more network nodes, some combination of the above, or so forth. A channel <b>108</b> may include one or more nodes (e.g., a telecommunication node, an access point, a base station, an internet server, a gateway, an internet or telecommunications switch, a combination thereof, etc.) through which signals are propagated. A communication may comprise, by way of example but not limitation, a transmission of data, a reception of data, an exchange of data, a flow of data (e.g., between or among two or more intermediate nodes or endpoints), some combination thereof, or so forth. A user device <b>102</b> may communicate with a server device <b>112</b>, or vice versa, via one or more signals (not explicitly shown) using one or more channels <b>108</b>. A couple of examples of channels <b>108</b> are illustrated in schematic diagram <b>100</b> (as well as in additional figures, such as schematic diagram <b>200</b>A of <figref idref="DRAWINGS">FIG. 2A</figref>). Signals may propagate via one or more channels <b>108</b>. Signals, by way of example but not limitation, may comprise, electrical signals, magnetic signals, electromagnetic signals, photonic signals, wireless signals, wired signals, multiples ones thereof, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0034For certain example embodiments, a server device <b>112</b> may comprise, by way of example but not limitation, one or more of: a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0035For certain example embodiments, at least one behavioral fingerprint <b>110</b> may comprise, by way of example but not limitation, one or more indicators representing one or more behaviors of at least one user with respect to at least one user device. Examples of one or more indicators representing one or more behaviors of at least one user with respect to at least one user device may include, but are not limited to, one or more indicators representing one or more habits of at least one user with respect to at least one user device, one or more indicators representing usage of at least one user device by at least one user, one or more indicators representing one or more actions of at least one user with respect to at least one user device, some combination thereof, or so forth. Additionally or alternatively, at least one behavioral fingerprint <b>110</b> may comprise, by way of example but not limitation, one or more indicators representing one or more predicted acts (e.g., behaviors, such as habits, usages, actions, a combination thereof, etc.) of at least one user with respect to at least one device. Additionally or alternatively, at least one behavioral fingerprint <b>110</b> may comprise, by way of example but not limitation, at least one status of a user that is utilizing or that corresponds to a user device. For certain example implementations, a user whose behavior is being monitored to at least partially establish at least a portion of at least one behavioral fingerprint <b>110</b> may comprise an authorized user, which is described herein below. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0036For certain example embodiments, a user may be utilizing a user device, by way of example but not limitation, if the user is accessing the user device, if the user is interacting with the user device, if the user is carrying the user device, if the user is providing input to the user device, if the user is receiving output from the user device, if the user is directing operation of the user device, some combination thereof, or so forth. A user may correspond to a user device, by way of example but not limitation, if the user is an authorized user of the user device. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0037For certain example embodiments, a user <b>104</b> of a user device <b>102</b> may comprise an authorized user of the user device <b>102</b>: if the user <b>104</b> comprises, by way of example but not limitation, a true owner, a manager, an information technology (IT) specialist, a controller, a purchaser, a lessee, an approved borrower, a primary user, a combination thereof, etc. of the user device <b>102</b>; if the user <b>104</b> is or has been authorized by a true owner, a manager, an IT specialist, a controller, a purchaser, a lessee, an approved borrower, a primary user, a combination thereof, etc. of the user device <b>102</b>; some combination thereof; or so forth. In certain example implementations, a determination that a user <b>104</b> comprises (e.g., is, is becoming, is being designated, a combination thereof, etc.) an authorized user of a user device <b>102</b>: may be effectuated if or when a user first registers a profile, an account, a combination thereof, etc. on a device (e.g., after a purchase or a ‘hard’ reset); may be effectuated if or when one or more ‘sign-ins’ (e.g., entry of a password, code, PIN, pattern, biometric input, a combination thereof, etc.) are performed by a user; may be effectuated if or when one or more user ID/secret information combinations (e.g., entry of an account name, email address, individualized identification, a combination thereof, etc. along with a corresponding password, code, PIN, pattern, biometric input, a combination thereof, etc.) are entered by a user; may be effectuated if or when a given user is identified as, designated as, or otherwise indicated to comprise an authorized user by one who is already an authorized user; some combination of such authorized user determinations; or so forth. An authorized user may add a new authorized user, by way of example only: by providing a name or other identification of another user or his or her biometric information (e.g., a facial photo, a voice sample, a fingerprint image, a retinal scan, a combination thereof, etc.); by providing a name or other identification of a user or temporary or permanent secret information, such as a password, a code, a PIN, a pattern, biometric input, a combination thereof, etc. (e.g., that a newly authorized user may be capable of changing or confirming); some combination thereof; or so forth. An authorized user, such as a true owner or IT specialist, may be empowered to remove someone from a list of authorized user(s). In certain example embodiments, different authorized users may have different levels of authorization (e.g., different levels of access, capabilities, rights, privileges, a combination thereof, etc.) with respect to a given user device <b>102</b>. For certain example implementations, but by way of example only, one authorized user may comprise an administrator with full access rights or privileges, yet another authorized user may comprise a regular, non-administrative, or junior user with fewer access rights or privileges. Additionally or alternatively, one authorized user may have full access rights to applications and content stored on a device or associated with a particular account/profile, yet another authorized user may have restricted access rights to applications or content stored on a device such that access is prevented, for instance, to particular device settings or adult content. Other approaches to providing different levels of authorization may also or instead be implemented. By way of example only, an authorized user who is a true owner may add a new authorized user that is permitted to utilize existing applications and content but is prohibited from adding new applications or making particular purchases (e.g., individual purchases above a predetermined dollar amount or multiple purchases beyond a total dollar amount).
0038<figref idref="DRAWINGS">FIG. 2A</figref> is a schematic diagram <b>200</b>A of multiple user devices, multiple server devices, and at least one behavioral fingerprint, any of which may be involved individually or jointly in example authentication scenarios in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 2A</figref>, by way of example but not limitation, schematic diagram <b>200</b>A may include at least one user device <b>102</b>, at least one user <b>104</b>, at least one network <b>106</b>, at least one channel <b>108</b>, at least one behavioral fingerprint <b>110</b>, or at least one server device <b>112</b>. More specifically, schematic diagram <b>200</b>A may include, by way of example only, three user devices <b>102</b> (e.g., a user device <b>102</b>A, a user device <b>102</b>B, or a user device <b>102</b>C, etc.), two server devices <b>112</b> (e.g., a server device <b>112</b>A, or a server device <b>112</b>B, etc.), or two behavioral fingerprints <b>110</b> (e.g., a behavioral fingerprint <b>110</b><i>a</i>, or a behavioral fingerprint <b>110</b><i>b</i>, etc.).
0039For certain example embodiments, a user <b>104</b> may correspond to or be utilizing multiple user devices <b>102</b>, such as at least two of user device <b>102</b>A, user device <b>102</b>B, or user device <b>102</b>C, at least partially simultaneously or from time to time. By way of example only, a user <b>104</b> may own at least two of: a mobile phone, a tablet computer, a vehicle with an intelligent computing apparatus, a laptop computer, or a desktop computer. For certain example implementations, at least part of a combined behavioral fingerprint <b>110</b> (e.g., a behavioral fingerprint <b>110</b><i>a</i>/<b>110</b><i>b</i>) may be associated with a user <b>104</b> and each corresponding user device <b>102</b>. Additionally or alternatively, an individualized behavioral fingerprint <b>110</b> (e.g., a behavioral fingerprint <b>110</b><i>a </i>or a behavioral fingerprint <b>110</b><i>b</i>) may be associated with a user <b>104</b> and each corresponding individual or respective user device <b>102</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0040For certain example embodiments, a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b</i>; an at least partially combined instantiation of at least two of a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b</i>; a portion of a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b</i>; a combination thereof; etc. may be distributed across or stored at, by way of example only, one or more of: a user device <b>102</b>A, a user device <b>102</b>B, a user device <b>102</b>C, a network <b>106</b> or node thereof, a server device <b>112</b>A, a server device <b>112</b>B, some combination thereof, or so forth. Additionally or alternatively, a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b</i>; an at least partially combined instantiation of at least two of a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b</i>; a portion of a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b</i>; a combination thereof; etc. may be transmitted, received, exchanged, a combination thereof, etc., by way of example only, via one or more of: at least one network <b>106</b>, one or more channels <b>108</b>, some combination thereof, or so forth. A user device <b>102</b> or a server device <b>112</b> may transmit, receive, exchange, a combination thereof, etc. at least a portion of a behavioral fingerprint <b>110</b>, <b>110</b><i>a</i>, or <b>110</b><i>b </i>directly between or among devices <b>102</b> or <b>112</b> or indirectly via at least one node (not explicitly shown) of one or more networks <b>106</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0041<figref idref="DRAWINGS">FIG. 2B</figref> is a schematic diagram <b>200</b>B of multiple user devices, multiple server devices, and multiple example locations for at least a portion of at least one behavioral fingerprint in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 2B</figref>, by way of example but not limitation, schematic diagram <b>200</b>B may include at least one user device <b>102</b>, at least one user <b>104</b>, at least one network <b>106</b>, at least one channel <b>108</b>, at least one behavioral fingerprint <b>110</b>, or at least one server device <b>112</b>. More specifically, schematic diagram <b>200</b>B may include, by way of example only, three user devices <b>102</b> (e.g., a user device <b>102</b>A, a user device <b>102</b>B, or a user device <b>102</b>C, etc.), two server devices <b>112</b> (e.g., a server device <b>112</b>A, or a server device <b>112</b>B, etc.), or six behavioral fingerprints <b>110</b> (e.g., a behavioral fingerprint <b>110</b><i>c</i>, a behavioral fingerprint <b>110</b><i>d</i>, a behavioral fingerprint <b>110</b><i>e</i>, a behavioral fingerprint <b>110</b><i>f</i>, a behavioral fingerprint <b>110</b><i>g</i>, or a behavioral fingerprint <b>110</b><i>h</i>, etc.).
0042For certain example embodiments, a given behavioral fingerprint <b>110</b> or portion thereof may be located at (stored at, distributed at least partially across, accessible from, associated with, a combination thereof, etc.) one or more devices <b>102</b> or <b>112</b>. By way of example only, a behavioral fingerprint <b>110</b><i>c </i>may be located at a user device <b>102</b>A, a behavioral fingerprint <b>110</b><i>d </i>may be located at a user device <b>102</b>B, a behavioral fingerprint <b>110</b><i>e </i>may be located at a user device <b>102</b>C, a behavioral fingerprint <b>110</b><i>f </i>may be located at a network <b>106</b> (e.g., at a cloud service or system), a behavioral fingerprint <b>110</b><i>g </i>may be located at a server device <b>112</b>A, or a behavioral fingerprint <b>110</b><i>h </i>may be located at a server device <b>112</b>B. For certain example implementations, any one or more of behavioral fingerprints <b>110</b><i>c</i>-<b>110</b><i>h </i>may comprise one or more separate or individualized behavioral fingerprints <b>110</b>; may comprise one or more combined, amalgamated, distributed, a combination thereof, etc. behavioral fingerprints <b>110</b>; may comprise at least a portion of at least one behavioral fingerprint <b>110</b>; some combination thereof; or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0043For certain example embodiments, at least one behavioral fingerprint <b>110</b> (e.g., of behavioral fingerprints <b>110</b><i>c</i>-<b>110</b><i>h</i>) may be associated with at least one user <b>104</b> or one or more of user devices <b>102</b>A, <b>102</b>B, or <b>102</b>C. For certain example implementations, a behavioral fingerprint <b>110</b><i>c</i>, which may be stored at a user device <b>102</b>A, may be associated with a user <b>104</b> and user device <b>102</b>A. For certain example implementations, a behavioral fingerprint <b>110</b><i>g</i>, which may be stored at a server device <b>112</b>A, may be associated with a user <b>104</b> and a user device <b>102</b>A. For certain example implementations, a behavioral fingerprint <b>110</b><i>h</i>, which may be stored at a server device <b>112</b>B, may be associated with a user <b>104</b>, a user device <b>102</b>B, and a user device <b>102</b>C. For certain example implementations, a behavioral fingerprint <b>110</b><i>c</i>, which may be stored at a user device <b>102</b>A and associated therewith, and a behavioral fingerprint <b>110</b><i>d</i>, which may be stored at a user device <b>102</b>B and associated therewith, may be individually or jointly associated with a user <b>104</b>. A behavioral fingerprint <b>110</b><i>c </i>and a behavioral fingerprint <b>110</b><i>d </i>may be identical to each other, partially the same, different from one another, updated to keep one at least partially coherent or consistent with the other, some combination thereof, or so forth. For certain example implementations, a behavioral fingerprint <b>110</b><i>d</i>, which may be stored at a user device <b>102</b>B and associated therewith, and a behavioral fingerprint <b>110</b><i>g</i>, which may be stored at a server device <b>112</b>A and associated with a user device <b>102</b>C, may be individually or jointly associated with a user <b>104</b>. A behavioral fingerprint <b>110</b><i>d </i>and a behavioral fingerprint <b>110</b><i>g </i>may be identical to each other, partially the same, different from one another, updated to keep one at least partially coherent or consistent with the other, some combination thereof, or so forth. For certain example implementations, a behavioral fingerprint <b>110</b><i>e</i>, which may be stored at a user device <b>102</b>C and associated therewith, and a behavioral fingerprint <b>110</b><i>h</i>, which may be stored at a server device <b>112</b>B and also associated with user device <b>102</b>C, may be individually or jointly associated with a user <b>104</b>. A behavioral fingerprint <b>110</b><i>e </i>and a behavioral fingerprint <b>110</b><i>h </i>may be identical to each other, partially the same, different from one another, updated to keep one at least partially coherent or consistent with the other, some combination thereof, or so forth. For certain example implementations, a behavioral fingerprint <b>110</b><i>e</i>, which may be stored at a user device <b>102</b>C, may be associated with a user <b>104</b> and a user device <b>102</b>B. Although each user device <b>102</b> and server device <b>112</b> (and network <b>106</b>) is shown in schematic diagram <b>200</b>B as having a behavioral fingerprint <b>110</b> located there at, one or more user devices <b>102</b> or server devices <b>112</b> (or networks <b>106</b>) may alternatively not have a behavioral fingerprint <b>110</b> located there at. Furthermore, other additional or alternative approaches may instead be implemented.
0044For certain example embodiments, a behavioral fingerprint <b>110</b> (including but not limited to any one or more of behavioral fingerprints <b>110</b><i>a</i>-<b>110</b><i>h</i>) may comprise a whole behavioral fingerprint, a portion of a behavioral fingerprint, a behavioral fingerprint associated with a single user device, a behavioral fingerprint associated with multiple user devices, a part of a distributed behavioral fingerprint, a whole behavioral fingerprint that is distributed across multiple devices, a portion or a whole behavioral fingerprint that is located at one device, one or more indicators of one or more behavior-related acts, some combination thereof, or so forth. Examples of behavioral fingerprint(s) <b>110</b> are described further herein below with particular reference to <figref idref="DRAWINGS">FIG. 3</figref>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0045<figref idref="DRAWINGS">FIG. 3</figref> is a schematic diagram <b>300</b> illustrating an example behavioral fingerprint including one or more example indicators of one or more behavior-related acts in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, by way of example but not limitation, schematic diagram <b>300</b> may comprise a behavioral fingerprint <b>110</b>, which behavioral fingerprint <b>110</b> may include any one or more of indications of various acts <b>302</b>-<b>322</b> or other indications <b>324</b>. Example indications <b>302</b>-<b>324</b> that are illustrated may include, but are not limited to, user interface actions <b>302</b>, user movements <b>304</b>, locations visited <b>306</b>, social network interactions <b>308</b>, communication modes employed <b>310</b>, entity interactions <b>312</b>, apps employed <b>314</b>, transactions conducted <b>316</b>, user statuses <b>318</b>, other acts <b>320</b>, predicted acts <b>322</b>, other indications or indicators <b>324</b>, some combination thereof, or so forth. More specifically, locations visited <b>306</b> may include physical locations visited <b>306</b><i>a</i>, virtual locations visited <b>306</b><i>b</i>, a combination thereof, etc., or social network interactions <b>308</b> may include social network members <b>308</b><i>a</i>, social network messages <b>308</b><i>b</i>, a combination thereof, etc. Additional or alternative implementations to those of schematic diagram <b>300</b> for a behavioral fingerprint <b>110</b> are described further herein below as well as above. Moreover, a behavioral fingerprint <b>110</b> may alternatively include more, fewer, or different indication(s) from those that are illustrated without departing from claimed subject matter.
0046For certain example embodiments, one or more user interface actions <b>302</b> may include, but are not limited to, a type of user interaction (e.g., buttons, keys, physical keyboard, touch screen, swipes, virtual buttons, virtual keyboard, multi-finger touch, speech, textual, movement sensing input such as a shake or a twist, a combination thereof, etc.), a speed of user interaction (e.g., speech rate, speech cadence, typing speed, swiping speed, scrolling speed, speed moving between or among windows or apps, duration of a swipe or press of a virtual or physical key or button, a combination thereof, etc.), a user input apparatus (e.g., a built-in microphone, a wireless microphone, a built-in keyboard, a virtual keyboard, a detachable/attachable keyboard, a wireless keyboard, an input apparatus identifiable such as by name or number, a combination thereof, etc.), a position of user interaction (e.g., a location of touch for a touch-sensitive screen having a keyboard or button or swipe area, a location of a swipe, a length of a swipe, an offset from a designated key or slide area, a combination thereof, etc.), a user output apparatus (e.g., a screen, a built-in speaker, a separate speaker, a vibration unit, an integrated output apparatus, a wired output apparatus, a wireless output apparatus, an output apparatus identifiable such as by name or number, a combination thereof, etc.), some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0047For certain example embodiments, one or more user movements <b>304</b> may include, but are not limited to, device orientation (e.g., cardinal direction a device is pointed at, angle a device is held at, a combination thereof, etc.), device shakes or deformations (e.g., how a device is moved to provide input, how a device is pressed or twisted or curved to provide input, a combination thereof, etc.), a pattern of vibrations or jostling applied to or experienced by a device during daily use (e.g., as a result of carrying it, commuting with it, placing it in a pack or purse, placing it in a pocket, a combination thereof, etc.), some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0048For certain example embodiments, one or more locations visited <b>306</b> may include, but are not limited to, locations that a user carries, sends, places, or travels with a device; locations that a user directs software to acquire data from or send data to; some combination thereof; or so forth. For certain example implementations, physical locations visited <b>306</b><i>a </i>may include, but are not limited to, an address, a room, a store, a building, a neighborhood, a city, a state, a country, one or more satellite positioning system (SPS) coordinates, a check-in location, a business, one or more geographical (e.g., cardinal) coordinates, a geographical zone (e.g., coordinates or approximate position in conjunction with a distance or range), some combination thereof, or so forth. For certain example implementations, virtual locations visited <b>306</b><i>b </i>may include, but are not limited to, an internet address, a web page, a web site, a social network, a destination within a social network, a virtual world, a destination within a virtual world, a chat room, a bulletin board, a blog, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0049For certain example embodiments, one or more social network interactions <b>308</b> may include, but are not limited to, accessing a social network, reading a communication from one or more social network members, sending a communication to one or more social network members, changing profile or account information for a social network, viewing publicly-available social network information (e.g., viewing a person's wall, board, stream, pinning, a combination thereof, etc.), viewing private social network information (e.g., viewing a targeted or personalized message, tweet, picture, a combination thereof, etc.), searching for entities on a social network, playing games via a social network, experiencing entertainment (e.g., video, audio, clips, pictures, a combination thereof, etc.) via a social network, a listing of which social network(s) are accessed, an order of which social networks are accessed, a day or time of accessing particular social network(s), some combination thereof, or so forth. For certain example implementations, social network member interactions <b>308</b><i>a </i>may include, but are not limited to, identifying or listing members interacted with via receiving, retrieving, sending, replying to a combination thereof, etc. one or more communications; noting particular social network protocols or modes (e.g., wall writing or viewing, tweet sending or receiving, picture sending or viewing, public versus private communicating, a combination thereof, etc.) used to communicate with particular members individually or in groups; noting particular social network protocols or modes used to communicate with particular member groups; some combination thereof; or so forth. For certain example implementations, social network message interactions <b>308</b><i>b </i>may include, but are not limited to, noting (e.g., recording, memorializing, storing, identifying, a combination thereof, etc.) messages sent or received, noting an order of message sending or viewing, noting a type (e.g., a social network protocol) of message sent or received, noting a number of messages sent or received, noting a duration between arrival of a message (e.g., generally or from a particular member) and viewing of the message, noting a duration between arrival or viewing of a message (e.g., generally or from a particular member) and responding to the message, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0050For certain example embodiments, one or more communication modes employed <b>310</b> may include, but are not limited to, speech, a phone call, a voice-over-internet-protocol (VoIP) communication, text messaging, instant messaging, a video communication (e.g., a video call, a video conference, a combination thereof, etc.), a social-network-based communication (e.g., a communication that is effectuated at least partially using a social network app, web site, service, a combination thereof, etc.), some combination thereof, or so forth. Additionally or alternatively, one or more communication modes employed <b>310</b> may include, but are not limited to, indications of which communication mode is employed if/when responding to a received communication of a given communication mode (e.g., it may be noted that an authorized user may respond to most phone calls or phone calls from particular people with text messages). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0051For certain example embodiments, one or more entity interactions <b>312</b> may include, but are not limited to, identification of at least one entity (e.g., business, service, person, social network member, group, organization, a combination thereof, etc.) that a user interacts with (e.g., with or without an indication of a communication mode, such as via a telephone capability, via email, via instant messaging, via a social network communication protocol, via VoIP, via a video capability, via a speech capability, a combination thereof, etc.), a listing of entities interacted with, an order of entities interacted with, notations of when (e.g., a day, a time, days of week, a combination thereof, etc.) entities are interacted with, notations of how (e.g., a communication mode used, a duration, a combination thereof, etc.) entities are interacted with, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0052For certain example embodiments, one or more apps employed <b>314</b> may include, but are not limited to, identification of one or more apps (e.g., applications, native applications, downloaded applications, installed applications, software applications, web applications, a combination thereof, etc.) employed (e.g., accessed, started, opened, launched, viewed, consulted, manipulated, configured, installed, executed, a combination thereof, etc.) by a user, a listing of apps employed, an order of apps employed, a notation of a time or a day at which apps are employed, a notation of duration(s) for which apps are employed, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0053For certain example embodiments, one or more transactions conducted <b>316</b> may include, but are not limited to, an identification of transactions (e.g., exchanges of consideration, purchases, orders, downloads, a combination thereof, etc.) conducted (e.g., initiated, requested, consummated, effectuated, accomplished, monitored, a combination thereof, etc.), a list of transactions, a notation of times or days of transactions, a notation of transaction amounts, a notation of at least one party to one or more transactions, a notation of items (e.g., physical items such as food or electronics, virtual items such as songs or movies or games or in-game abilities, a combination thereof, etc.) or services (e.g., physical services such as a massage or a car wash, virtual services such as streaming media or a membership, a combination thereof, etc.) involved in one or more transactions, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0054For certain example embodiments, one or more user statuses <b>318</b> may include, but are not limited to, a location status update, a health status update, an alert (e.g., as to whether a person has possession or has lost possession of a device; as to whether a device has exceeded some percentage—e.g. 50% or 75% or 100%—of an allotted amount, such as of minutes of talking, bytes of data, messages of texting, dollars of a fund, time of use, etc.; as to where a person is currently located; a combination thereof; etc.), a current (e.g., most recent, present, a combination thereof, etc.) activity update, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0055For certain example embodiments, one or more other acts <b>320</b> may include, but are not limited to, other user behaviors, user habits, user actions, user movements, user interactions, user visitations, user transactions, device features (e.g., capabilities, native applications, operating system functions, a combination thereof, etc.) employed, a combination thereof, etc. that a device may monitor (e.g., detect, observe, discern, ascertain, a combination thereof, etc.); other acts reflecting user behavior; other acts described herein; some combination thereof; or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0056For certain example embodiments, one or more predicted acts <b>322</b> may include, but are not limited to, an act that is predicted based at least partially on any one or more of other indications <b>302</b>-<b>320</b>; an act that is predicted to be performed by an authorized user; an act corresponding to a particular likelihood level of re-occurring; an act that is predicted to re-occur in view of one or more observed acts of at least one authorized user of one or more user devices; an act that is predicted to occur based at least partially on a statistical analysis (e.g., a likelihood function, a histogram evaluation, a probabilistic approach, a Bayesian analysis, a stochastic mechanism, a correlation procedure, a probability density function, a normal/Gaussian distribution, a cumulative distribution function, an expected value, a combination thereof, etc.) of one or more historically-monitored acts; an act that has been repeatedly performed in certain manner(s) or at particular time(s) such that it can be expected to be performed again in such certain manner(s) or at such particular time(s); an act that is derived or results from a conversion of monitored act(s) corresponding to one device to at least one act corresponding to another device; some combination thereof; or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0057For certain example embodiments, one or more other indications <b>324</b> may include, but are not limited to, static characteristics of an authorized user, individuals that are related to an authorized user, characteristics of individuals that are related to an authorized user; nature of relationships between or among an authorized user and other individuals, some combination thereof, or so forth. Non-exhaustive examples of other indications or indicators <b>324</b> are provided herein below with particular reference to <figref idref="DRAWINGS">FIGS. 7A-7C, 8A-8M, and 9A-9G</figref>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0058<figref idref="DRAWINGS">FIG. 4</figref> is a schematic diagram <b>400</b> of an example user device including one or more example components in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 4</figref>, a user device <b>102</b> may include one or more components such as: at least one processor <b>402</b>, one or more media <b>404</b>, logic <b>406</b>, circuitry <b>408</b>, at least one communication interface <b>410</b>, at least one interconnect <b>412</b>, at least one power source <b>414</b>, at least one user interface <b>416</b>, one or more sensors <b>418</b>, some combination thereof, or so forth. Furthermore, as shown in schematic diagram <b>400</b>, one or more media <b>404</b> may comprise one or more instructions <b>420</b>, at least one behavioral fingerprint <b>110</b>, one or more settings or parameters <b>422</b>, some combination thereof, or so forth; a communication interface <b>410</b> may comprise at least one wireless communication interface <b>410</b><i>a</i>, at least one wired communication interface <b>410</b><i>b</i>, some combination thereof, or so forth; or a user interface <b>416</b> may comprise at least one user input interface <b>416</b><i>a</i>, at least one user output interface <b>416</b><i>b</i>, some combination thereof, or so forth. However, a user device <b>102</b> may alternatively include more, fewer, or different component(s) from those that are illustrated without departing from claimed subject matter.
0059For certain example embodiments, a user device <b>102</b> may include or comprise at least one electronic device. User device <b>102</b> may comprise, for example, a computing platform or any electronic device having at least one processor or memory. Processor <b>402</b> may comprise, by way of example but not limitation, any one or more of a general-purpose processor, a specific-purpose processor, a digital signal processor (DSP), a processing unit, some combination thereof, or so forth. A processing unit may be implemented, for example, with one or more application specific integrated circuits (ASICs), DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors generally, processing cores, discrete/fixed logic circuitry, controllers, micro-controllers, microprocessors, some combination thereof, or so forth. Media <b>404</b> may bear, store, contain, include, provide access to, a combination thereof, etc. instructions <b>420</b>, which may be executable by a processor <b>402</b>; at least one behavioral fingerprint <b>110</b>; one or more settings/parameters <b>422</b>; some combination thereof; or so forth. Instructions <b>420</b> may comprise, by way of example but not limitation, a program, a module, an application or app (e.g., that is native, that runs in a browser, that runs within a virtual machine, a combination thereof, etc.), an operating system, a combination thereof, etc. or portion thereof; operational data structures; source code, object code, just-in-time (JIT) compiled code, a combination thereof, etc.; processor-executable instructions; other code; some combination thereof; or so forth. Media <b>404</b> may comprise, by way of example but not limitation, processor-accessible or non-transitory media (e.g., memory, random access memory (RAM), read only memory (ROM), flash memory, hard drives, disk-based media, disc-based media, magnetic storage, optical storage, volatile memory, nonvolatile memory, a combination thereof, etc.) that is capable of bearing instructions, a behavioral fingerprint, settings, parameters, some combination thereof, or so forth.
0060For certain example embodiments, execution of instructions <b>420</b> by one or more processors <b>402</b> may transform user device <b>102</b> into a special-purpose computing device, apparatus, platform, machine, some combination thereof, or so forth. Instructions <b>420</b> may comprise, for example, instructions that are capable of realizing at least a portion of one or more flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings. Settings/parameters <b>422</b> may comprise, by way of example but not limitation, one or more settings or parameters that may be established or determined by a user or other entity, one or more or settings or parameters that may be determined or detected by a user device <b>102</b>, one or more settings or parameters that may be received from another device that determined or detected them, one or more settings or parameters that may determine at least partly how a user device <b>102</b> is to operate or respond to a situation or a behavioral fingerprint, one or more settings or parameters (e.g., values) that may be used to realize flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings. Settings/parameters <b>422</b> may control at least partially how at least one behavioral fingerprint <b>110</b> is configured, stored, shared, used, applied, some combination thereof, or so forth. Additionally or alternatively, at least a portion of settings/parameters <b>422</b> may be at least partially integrated with at least one behavioral fingerprint <b>110</b>.
0061For certain example embodiments, logic <b>406</b> may comprise hardware, software, firmware, discrete/fixed logic circuitry, a combination thereof, etc. that is capable of performing or facilitating performance of flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings. Circuitry <b>408</b> may comprise hardware, software, firmware, discrete/fixed logic circuitry, a combination thereof, etc. that is capable of performing or facilitating performance of flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings, wherein circuitry <b>408</b> comprises at least one physical or hardware component or aspect.
0062For certain example embodiments, one or more communication interfaces <b>410</b> may provide one or more interfaces between user device <b>102</b> and another device or a person/operator. With respect to a person/operator, a communication interface <b>410</b> may include, by way of example but not limitation, a screen, a speaker, a keyboard or keys, a microphone, or other person-device input/output apparatuses. A wireless communication interface <b>410</b><i>a </i>or a wired communication interface <b>410</b><i>b </i>may also or alternatively include, by way of example but not limitation, a transceiver (e.g., a transmitter or a receiver), a radio, an antenna, a wired interface connector or other similar apparatus (e.g., a network connector, a universal serial bus (USB) connector, a proprietary connector, a Thunderbolt® or Light Peak® connector, a combination thereof, etc.), a physical or logical network adapter or port, a frequency converter, a baseband processor, a combination thereof, etc. to communicate wireless signals or wired signals via one or more wireless communication links or wired communication links, respectively, such as over at least one channel <b>108</b> (e.g., of <figref idref="DRAWINGS">FIGS. 1 and 2A</figref>). Communications with at least one communication interface <b>410</b> may enable transmitting, receiving, or initiating of transmissions, just to name a few examples.
0063For certain example embodiments, at least one interconnect <b>412</b> may enable signal communication between or among components of user device <b>102</b>. Interconnect <b>412</b> may comprise, by way of example but not limitation, one or more buses, channels, switching fabrics, some combination thereof, or so forth. Although not explicitly illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, one or more components of user device <b>102</b> may be coupled to interconnect <b>412</b> via a discrete or integrated interface. By way of example only, one or more interfaces may couple a communication interface <b>410</b> or a processor <b>402</b> to at least one interconnect <b>412</b>. For certain example embodiments, at least one power source <b>414</b> may provide power to one or more components of user device <b>102</b>. Power source <b>414</b> may comprise, by way of example but not limitation, a battery, a power connector, a solar power source or charger, a mechanical power source or charger, a fuel source, some combination thereof, or so forth.
0064For certain example embodiments, at least one sensor <b>418</b> may sense, produce, or otherwise provide at least one sensor value. Sensors <b>418</b> may include, by way of example only, a camera, a microphone, an accelerometer, a thermometer, a satellite positioning system (SPS) sensor, a barometer, a humidity sensor, a compass, a gyroscope, a magnetometer, a pressure sensor, an oscillation detector, a light sensor, an inertial measurement unit (IMU), a tactile sensor, a touch sensor, a flexibility sensor, a microelectromechanical system (MEMS), some combination thereof, or so forth. Values provided by at least one sensor <b>418</b> may comprise, by way of example but not limitation, an image, a sound recording, an acceleration value, a temperature, SPS coordinates, a barometric pressure, a humidity level, a compass direction, a gyroscopic value, a magnetic reading, a pressure value, an oscillation value, an ambient light reading, inertial readings, touch detections, finger placements, flex detections, some combination thereof, or so forth.
0065For certain example embodiments, a user interface <b>416</b> may enable one or more users to interact with user device <b>102</b>. Interactions between a user and a user device may relate, by way of example but not limitation: to touch/tactile/feeling/haptic sensory (e.g., a user may shake, rotate, decline/incline, bend, twist, or move a user device which may be detected by a gyroscope, an accelerometer, a compass, a combination thereof, etc.; a user may press a button, slide a switch, rotate a knob, etc.; a user may touch a touch-sensitive screen; a device may vibrate; some combination thereof; or so forth), to sound/hearing/speech sensory (e.g., a user may speak into a microphone, a device may generate sounds via a speaker, a combination thereof, etc.), to sights/vision sensory (e.g., a device may activate one or more lights, modify an image presented on a display screen, a combination thereof, etc.), some combination thereof, or so forth.
0066For certain example embodiments, a user interface <b>416</b> may comprise a user input interface <b>416</b><i>a</i>, a user output interface <b>416</b><i>b</i>, some combination thereof, or so forth. A user input interface <b>416</b><i>a </i>may comprise, by way of example but not limitation, a microphone, a button, a switch, a dial, a knob, a wheel, a trackball, a key, a keypad, a keyboard, a touch-sensitive screen, a touch-sensitive surface, a camera, a gyroscope, an accelerometer, a compass, a virtual button/slider/keyboard/etc. presented on a touch-sensitive screen, some combination thereof, or so forth. A user output interface <b>416</b><i>b </i>may comprise, by way of example but not limitation, a speaker, a screen (e.g., with or without touch-sensitivity), a vibrating haptic feature, some combination thereof, or so forth. Certain user interfaces <b>416</b> may enable both user input and user output. For example, a touch-sensitive screen may be capable of providing user output and accepting user input. Additionally or alternatively, a user interface <b>416</b> component (e.g., that may be integrated with or separate from a user device <b>102</b>), such as a headset that has a microphone and a speaker, may enable both user input and user output.
0067However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, or so forth. For instance, it should be understood that for certain example implementations components that are illustrated separately in <figref idref="DRAWINGS">FIG. 4</figref> may not necessarily be separate or mutually exclusive. For example, a given component may provide multiple functionalities. By way of example only, a single component such as a USB connector may function as a wired communication interface <b>410</b><i>b </i>or a power source <b>414</b>. Additionally or alternatively, a single component such as a display screen may function as a communication interface <b>410</b> with respect to a user, as a user input interface <b>416</b><i>a</i>, or as a user output interface <b>416</b><i>b</i>. Additionally or alternatively, one or more instructions <b>420</b> may function to realize at least part of a behavioral fingerprint <b>110</b> or at least one setting or parameter <b>422</b>.
0068It should also be understood that for certain example implementations components that are illustrated in schematic diagram <b>400</b> or described herein may or may not be integral with or integrated into a user device <b>102</b>. For example, a component may be removably connected to a user device <b>102</b>, a component may be wirelessly coupled to a user device <b>102</b>, some combination thereof, or so forth. By way of example only, instructions <b>420</b> may be stored on a removable card having at least one medium <b>404</b>. Additionally or alternatively, a user interface <b>416</b> (e.g., a wired or wireless headset, a screen, a video camera, a keyboard, a combination thereof, etc.) may be coupled to a user device <b>102</b> wirelessly or by wire. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0069<figref idref="DRAWINGS">FIG. 5</figref> is a schematic diagram <b>500</b> of an example server device including one or more example components in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 5</figref>, a server device <b>112</b> may include one or more components such as: at least one processor <b>502</b>, one or more media <b>504</b>, logic <b>506</b>, circuitry <b>508</b>, at least one communication interface <b>510</b>, at least one interconnect <b>512</b>, at least one power source <b>514</b>, at least one entity interface <b>516</b>, some combination thereof, or so forth. Furthermore, as shown in schematic diagram <b>500</b>, one or more media <b>504</b> may comprise one or more instructions <b>518</b>, at least one behavioral fingerprint <b>110</b>, one or more settings or parameters <b>520</b>, some combination thereof, or so forth; or communication interface <b>510</b> may comprise at least one wireless communication interface <b>510</b><i>a</i>, at least one wired communication interface <b>510</b><i>b</i>, some combination thereof, or so forth. However, a server device <b>112</b> may alternatively include more, fewer, or different component(s) from those that are illustrated without departing from claimed subject matter.
0070For certain example embodiments, a server device <b>112</b> may include or comprise at least one processing or computing device or machine. Server device <b>112</b> may comprise, for example, a computing platform or any electronic device or devices having at least one processor or memory. Processor <b>502</b> may comprise, by way of example but not limitation, any one or more of a general-purpose processor, a specific-purpose processor, a digital signal processor (DSP), a processing unit, some combination thereof, or so forth. A processing unit may be implemented, for example, with one or more application specific integrated circuits (ASICs), DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors generally, processing cores, discrete/fixed logic circuitry, controllers, micro-controllers, microprocessors, some combination thereof, or so forth. Media <b>504</b> may bear, store, contain, include, provide access to, a combination thereof, etc. instructions <b>518</b>, which may be executable by a processor <b>502</b>; at least one behavioral fingerprint <b>110</b>; one or more settings/parameters <b>520</b>; some combination thereof; or so forth. Instructions <b>518</b> may comprise, by way of example but not limitation, a program, a module, an application or app (e.g., that is native, that runs in a browser, that runs within a virtual machine or server, a combination thereof, etc.), an operating system, a combination thereof, etc. or portion thereof; operational data structures; source code, object code, just-in-time (JIT) compiled code, a combination thereof, etc.; processor-executable instructions; other code; some combination thereof; or so forth. Media <b>504</b> may comprise, by way of example but not limitation, processor-accessible or non-transitory media (e.g., memory, random access memory (RAM), read only memory (ROM), flash memory, hard drives, disk-based media, disc-based media, magnetic storage, optical storage, volatile memory, nonvolatile memory, a combination thereof, etc.) that is capable of bearing instructions, at least one behavioral fingerprint, settings, parameters, some combination thereof, or so forth.
0071For certain example embodiments, execution of instructions <b>518</b> by one or more processors <b>502</b> may transform server device <b>112</b> into a special-purpose computing device, apparatus, platform, machine, some combination thereof, or so forth. Instructions <b>518</b> may comprise, for example, instructions that are capable of realizing at least a portion of one or more flow diagrams methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings. Settings/parameters <b>520</b> may comprise, by way of example but not limitation, one or more settings or parameters that may be established by a user or other entity, one or more settings or parameters that may be determined by a server device <b>112</b>, one or more settings or parameters that may be determined by a user or other entity, one or more settings or parameters that may be detected by a server device <b>112</b>, one or more settings or parameters that may be received from another device that detected them, one or more settings or parameters that may determine at least partly how a server device <b>112</b> is to operate or respond to a situation or a behavioral fingerprint, one or more settings or parameters (e.g., values) that may be used to realize flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings. Settings/parameters <b>520</b> may control at least partially how at least one behavioral fingerprint <b>110</b> is configured, stored, shared, used, applied, some combination thereof, or so forth. Additionally or alternatively, at least a portion of settings/parameters <b>520</b> may be at least partially integrated with at least one behavioral fingerprint <b>110</b>.
0072For certain example embodiments, logic <b>506</b> may comprise hardware, software, firmware, discrete/fixed logic circuitry, a combination thereof, etc. that is capable of performing or facilitating performance of flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings. Circuitry <b>508</b> may comprise hardware, software, firmware, discrete/fixed logic circuitry, a combination thereof, etc. that is capable of performing or facilitating performance of flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings, wherein circuitry <b>508</b> comprises at least one physical or hardware component or aspect.
0073For certain example embodiments, one or more communication interfaces <b>510</b> may provide one or more interfaces between server device <b>112</b> and another device or a person/operator/entity directly or indirectly. A wireless communication interface <b>510</b><i>a </i>or a wired communication interface <b>510</b><i>b </i>may also or alternatively include, by way of example but not limitation, a transceiver (e.g., a transmitter or a receiver), a radio, an antenna, a wired interface connector or other similar apparatus (e.g., a network connector, a universal serial bus (USB) connector, a proprietary connector, a Thunderbolt® or Light Peak® connector, a gateway, a combination thereof, etc.), a physical or logical network adapter or port, a frequency converter, a baseband processor, an Internet or telecommunications backbone connector, a fiber optic connector, a storage area network (SAN) connector, a combination thereof, etc. to communicate wireless signals or wired signals via one or more wireless communication links or wired communication links, respectively, such as over one or more channels <b>108</b> (e.g., of <figref idref="DRAWINGS">FIGS. 1 and 2A</figref>). Communications with at least one communication interface <b>510</b> may enable transmitting, receiving, or initiating of transmissions, just to name a few examples.
0074For certain example embodiments, at least one interconnect <b>512</b> may enable signal communication between or among components of server device <b>112</b>. Interconnect <b>512</b> may comprise, by way of example but not limitation, one or more buses, channels, switching fabrics, local area networks (LANs), storage area networks (SANs), some combination thereof, or so forth. Although not explicitly illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, one or more components of server device <b>112</b> may be coupled to interconnect <b>512</b> via a discrete or integrated interface. By way of example only, one or more interfaces may couple a processor <b>502</b> or a medium <b>504</b> to at least one interconnect <b>512</b>. For certain example embodiments, at least one power source <b>514</b> may provide power to one or more components of server device <b>112</b>. Power source <b>514</b> may comprise, by way of example but not limitation, a power connector for accessing an electrical grid, a fuel cell, a solar power source, some combination thereof, or so forth.
0075For certain example embodiments, an entity interface <b>516</b> may enable one or more entities (e.g., another device, a person, a group, a robotic entity, a combination thereof, etc.) to provide input to or receive output from server device <b>112</b>. Interactions between an entity and a device may relate, by way of example but not limitation, to inputting or outputting instructions, commands, settings, parameters, indications, some combination thereof, or so forth. Certain entity interfaces <b>516</b> may enable both entity input and entity output at server device <b>112</b> or over at least one network link, such as one or more channels <b>108</b> (e.g., of <figref idref="DRAWINGS">FIGS. 1 and 2A</figref>).
0076However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, or so forth. For instance, it should be understood that for certain example implementations components that are illustrated separately in <figref idref="DRAWINGS">FIG. 5</figref> need not necessarily be separate or mutually exclusive. For example, a given component may provide multiple functionalities. By way of example only, hard-wired logic <b>506</b> may form circuitry <b>508</b>. Additionally or alternatively, a single component such as a connector may function as a communication interface <b>510</b> or as an entity interface <b>516</b>. Additionally or alternatively, one or more instructions <b>518</b> may function to realize at least one setting or parameter <b>520</b>.
0077It should also be understood that for certain example implementations components that are illustrated in schematic diagram <b>500</b> or described herein may not be integral or integrated with a server device <b>112</b>. For example, a component may be removably connected to a server device <b>112</b>, a component may be wirelessly coupled to a server device <b>112</b>, one or more components of a server device <b>112</b> may be geographically distributed or separated from one another, some combination thereof, or so forth. By way of example only, instructions <b>518</b> may be stored on one medium <b>504</b>, and settings/parameters <b>520</b> (or another portion of instructions <b>518</b>) may be stored on a different medium <b>504</b>, which may comprise a same server or a part of a different server of, e.g., a server farm. Additionally or alternatively, respective processor-media sets may be physically realized on different or respective server blades or server containers. Multiple server blades, for instance, may be linked or interlinked to realize at least one server device <b>112</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0078<figref idref="DRAWINGS">FIGS. 6A and 6B</figref> are schematic diagrams <b>600</b>A and <b>600</b>B of an example user device and an example server device, respectively, that have one or more functional units in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIGS. 6A and 6B</figref>, by way of example but not limitation, schematic diagrams <b>600</b>A and <b>600</b>B may comprise a user device <b>102</b> and a server device <b>112</b>, respectively. As illustrated in schematic diagrams <b>600</b>A and <b>600</b>B, a user device <b>102</b> or a server device <b>112</b> may include, but are not limited to, at least one authentication unit <b>602</b>, at least one authorization unit <b>604</b>, at least one behavioral fingerprint unit <b>606</b>, a combination thereof, or so forth. However, a user device <b>102</b> or a server device <b>112</b> may alternatively include more, fewer, or different unit(s) from those that are illustrated without departing from claimed subject matter.
0079For certain example embodiments, a unit may be comprised of at least one processor (e.g., a processor <b>402</b> of <figref idref="DRAWINGS">FIG. 4</figref>, a processor <b>502</b> of <figref idref="DRAWINGS">FIG. 5</figref>, a combination thereof, etc.), one or more media (e.g., a medium <b>404</b> of <figref idref="DRAWINGS">FIG. 4</figref>, a media medium <b>504</b> of <figref idref="DRAWINGS">FIG. 5</figref>, a combination thereof, etc.), instructions (e.g., processor-executable instructions, instructions <b>420</b> of <figref idref="DRAWINGS">FIG. 4</figref>, instructions <b>518</b> of <figref idref="DRAWINGS">FIG. 5</figref>, computer-implementable instructions, a combination thereof, etc.), logic (e.g., logic <b>406</b> of <figref idref="DRAWINGS">FIG. 4</figref>, logic <b>506</b> of <figref idref="DRAWINGS">FIG. 5</figref>, a combination thereof, etc.), circuitry (e.g., circuitry <b>408</b> of <figref idref="DRAWINGS">FIG. 4</figref>, circuitry <b>508</b> of <figref idref="DRAWINGS">FIG. 5</figref>, a combination thereof, etc.), other described or illustrated component(s), some combination thereof, or so forth. For certain example implementations, one or more units (e.g., an authentication unit <b>602</b>, an authorization unit <b>604</b>, a behavioral fingerprint unit <b>606</b>, a combination thereof, etc.) of at least one user device <b>102</b> may function or interoperate with one or more units of at least one server device <b>112</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0080For certain example embodiments, an authentication unit <b>602</b> may operate to authenticate a user of a device. For certain example implementations, a user of a device may be authenticated by determining to some (e.g., reasonable, acceptable, measurable, quantifiable, a combination thereof, etc.) degree an identity of a user. By way of example but not limitation, an authentication unit <b>602</b> may enable implementation of multiple degrees of authentication, with different degrees of authentication corresponding to different levels of certainty of an identity of a user. Example aspects related to authentication are described further herein (e.g., at least herein above with particular reference to <figref idref="DRAWINGS">FIG. 1</figref>). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0081For certain example embodiments, an authorization unit <b>604</b> may operate to permit or enable full or at least partial access to, use of, implementation of, execution of, a combination thereof, etc. one or more features, applications, accounts, profiles, data, capabilities, a combination thereof, etc. of at least one device, such as a user device <b>102</b> or a server device <b>112</b>. For certain example implementations, authorization may be fully or at least partially granted, denied, withheld, a combination thereof, etc. based at least partially on an authentication determination, a result from an authentication unit <b>602</b>, some combination thereof, or so forth. By way of example but not limitation, an authorization unit <b>604</b> may provide for different levels of authorization, including but not limited to for a given authorized user, that correspond to different degrees of authentication, that correspond to different user identities, some combination thereof, or so forth. Example aspects related to authorization are described further herein (e.g., at least herein above with particular reference to <figref idref="DRAWINGS">FIG. 1</figref>). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0082For certain example embodiments, a behavioral fingerprint unit <b>606</b> may operate to implement, perform, facilitate performance of, a combination thereof, etc. one or more flow diagrams, methods, processes, procedures, operations, functionality, technology, mechanisms, a combination thereof, etc. that are described herein or illustrated in the accompanying drawings or that relate to at least one behavioral fingerprint. For certain example implementations, a behavioral fingerprint unit <b>606</b> may provide information, monitored acts, likelihood values, determinations, comparisons, analyses, indications, predicted acts, a combination thereof, etc. to an authentication unit <b>602</b> on which it may at least partially base an authentication determination. Example aspects related to behavioral fingerprinting are described further herein above and below. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0083<figref idref="DRAWINGS">FIG. 7A</figref> is a schematic diagram <b>700</b>A that includes at least one example device that is capable of handling scenarios for behavioral fingerprinting via social networking interaction in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIG. 7A</figref>, by way of example but not limitation, schematic diagram <b>700</b>A includes at least one device that may comprise a family relation indication obtainment unit <b>702</b> or a behavioral fingerprint incorporation unit <b>704</b>. More specifically, schematic diagram <b>700</b>A may include a user device <b>102</b> or a server device <b>112</b>. By way of example but not limitation, a family relation indication obtainment unit <b>702</b> or a behavioral fingerprint incorporation unit <b>704</b> may comprise one or more modules, hardware, software, firmware, logic, circuitry, some combination thereof, or so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0084For certain example embodiments, a family relation indication obtainment unit <b>702</b> or a behavioral fingerprint incorporation unit <b>704</b> may be implemented separately or at least partially jointly or in combination. A family relation indication obtainment unit <b>702</b> may be configured to obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction. A behavioral fingerprint incorporation unit <b>704</b> may be configured to incorporate the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0085<figref idref="DRAWINGS">FIGS. 7B-7C</figref> are schematic diagrams <b>700</b>B-<b>700</b>C that include at least one example device and that depict example scenarios for implementing behavioral fingerprinting via social networking interaction in accordance with certain example embodiments. As shown in <figref idref="DRAWINGS">FIGS. 7B-7C</figref>, by way of example but not limitation, one or more of schematic diagrams <b>700</b>B-<b>700</b>C may include at least one user device <b>102</b>, at least one user <b>104</b>, at least one behavioral fingerprint <b>110</b>, at least one server device <b>112</b>, at least one family relation indication <b>706</b>, at least one utilization indicator <b>708</b>, at least one social networking interaction <b>710</b>, at least one incorporation <b>712</b>, at least one other device <b>714</b>, or at least one cloud <b>716</b>. Each of schematic diagrams <b>700</b>B-<b>700</b>C may include alternative or additional depictions, which may relate to behavioral fingerprinting via social networking interaction, as described herein below. In addition to or in alternative to description herein below with specific reference to <figref idref="DRAWINGS">FIGS. 7B-7C</figref>, illustrated aspects of schematic diagrams <b>700</b>B-<b>700</b>C may be relevant to example description with reference to <figref idref="DRAWINGS">FIGS. 8A-8M or 9A-9G</figref>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0086As shown in <figref idref="DRAWINGS">FIG. 7B</figref>, by way of example but not limitation, schematic diagram <b>700</b>B may include at least one user device <b>102</b>, at least one user <b>104</b>, at least one behavioral fingerprint <b>110</b>, at least one server device <b>112</b>, at least one family relation indication <b>706</b>, at least one utilization indicator <b>708</b>, at least one social networking interaction <b>710</b>, at least one incorporation <b>712</b>, at least one other device <b>714</b>, or at least one cloud <b>716</b>. More specifically, schematic diagram <b>700</b>B may include a user device <b>102</b> that may correspond to a user <b>104</b>, which user may comprise an authorized user; a server <b>112</b>(<b>1</b>) or a server <b>112</b>(<b>2</b>); an indication of family relation <b>706</b>; an indicator of utilization <b>708</b> of one or more user devices, such as a user device <b>102</b>; or at least one social networking interaction <b>710</b>, which may facilitate obtainment of at least one family relation indication <b>706</b>. For certain example embodiments, at least one family relation indication <b>706</b> may include an indication of if, whether, how, a combination thereof, etc. a particular individual is related from a family perspective to a user <b>104</b>. An indication of family relation <b>706</b> (or family relation indication <b>706</b>) may comprise, by way of example but not limitation, at least one other indication <b>324</b> (e.g., of <figref idref="DRAWINGS">FIG. 3</figref>) or at least one utilization indicator <b>708</b>. For certain example embodiments, a social networking interaction <b>710</b> may include a passive, an active, a receptive, an initiated, a monitoring, a participating, a combination thereof, etc. type of interaction with a social network. For certain example implementations, an incorporation <b>712</b> may include incorporating at least a portion of a family relation indication <b>706</b> into at least one behavioral fingerprint <b>110</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0087For certain example embodiments, at least one utilization indicator <b>708</b> may correspond to (e.g., be monitored, detected, observed, a combination thereof, etc. at or by) a user device <b>102</b>. An indicator of utilization <b>708</b> (or utilization indicator <b>708</b>) may comprise, by way of example but not limitation, at least one indicator of any of indicators <b>302</b>-<b>322</b> (e.g., of <figref idref="DRAWINGS">FIG. 3</figref>). An indication of family relation <b>706</b> (or family relation indication <b>706</b>) may comprise, by way of example but not limitation, at least one other indication <b>324</b> (e.g., of <figref idref="DRAWINGS">FIG. 3</figref>). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0088For certain example embodiments, a server device <b>112</b>(<b>1</b>) may be operated by or for a social network. A social network may include, by way of example but not imitation, a network, a service, a website, a computing infrastructure, an application, an interface, cloud computing, a combination thereof, etc. that enables or facilitates interaction (e.g., via text, images, audio, video, a combination thereof, etc.) between or among two or more members of the social network. The term “social” in social networks should not be interpreted to exclude networks designed or intended for professional or specific purposes. Social networks may include, but are not limited to, Facebook, Google+, Twitter, LinkedIn, Myspace, Pinterest, Classmates[dot]com, Flickr, Foursquare, Friendster, Netlog, Orkut, Sina Weibo, Qzone, Habbo, Instagram, and so forth. For certain example embodiments, a server device <b>112</b>(<b>2</b>) may be operated by or for another entity, such as a third party. For certain example implementations, another entity that is affiliated with a server device <b>112</b>(<b>2</b>) may comprise a provider or utilizer of a cloud service or cloud computing, as represented by cloud <b>716</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0089For certain example embodiments, an other device <b>714</b> may be operated or owned by a user <b>104</b>, may be operated or owned by a third party, may be operated by one and owned by the other, and so forth. For certain example implementations, other device <b>714</b> may be communicatively coupled to user device <b>102</b>. By way of example but not limitation, other device <b>714</b>: may be integrated with user device <b>102</b>, may be physically connected to user device <b>102</b>, may be wirelessly coupled to user device <b>102</b>, may be coupled by wire to user device <b>102</b>, a combination thereof, and so forth. Other device <b>714</b> may be capable of bidirectional or unidirectional communication with a server <b>112</b>(<b>1</b>) or a server <b>112</b>(<b>2</b>) (e.g., via one or more channels <b>108</b> (e.g., of <figref idref="DRAWINGS">FIGS. 1 and 2A</figref>), which channel(s) may include at least one network, such as an internet). Other device <b>714</b> may comprise, by way of example but not limitation, a point-of-sale (POS) terminal, such as a register; an attachment augmenting a POS terminal; an attachment to a user device <b>102</b>; a device that accepts credit, debit, or other payment cards and is coupled to a user device <b>102</b>; a combination thereof; and so forth. Data (e.g., relating to behavioral fingerprinting, social networking, family relations, a combination thereof, etc.) may be collected at or by other device <b>714</b> or funneled through other device <b>714</b> between or among at least one user device <b>102</b> and one or more server devices <b>112</b>. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc. Additional or alternative description that may be relevant to schematic diagram <b>700</b>B is provided herein below with particular reference to one or more of any of <figref idref="DRAWINGS">FIGS. 8A-8M</figref> or <figref idref="DRAWINGS">FIGS. 9A-9G</figref>.
0090As shown in <figref idref="DRAWINGS">FIG. 7C</figref>, by way of example but not limitation, schematic diagram <b>700</b>C may include at least one user device <b>102</b>, at least one user <b>104</b>, at least one behavioral fingerprint <b>110</b>, at least one server device <b>112</b>, at least one family relation indication <b>706</b>, at least one utilization indicator <b>708</b>, at least one social networking interaction <b>710</b>, at least one incorporation <b>712</b>, at least one other device <b>714</b>, at least one social network <b>718</b>, at least some profile data <b>720</b>, at least one social network app <b>722</b>, or at least one social network communication <b>724</b>. Additional or alternative description that may be relevant to schematic diagram <b>700</b>C is provided herein below with particular reference to one or more of any of <figref idref="DRAWINGS">FIGS. 8A-8M</figref> or <figref idref="DRAWINGS">FIGS. 9A-9G</figref>.
0091Following are a series of flowcharts depicting implementations. For ease of understanding, the flowcharts are organized such that the initial flowcharts present implementations via an example implementation and thereafter the following flowcharts present alternate implementations and/or expansions of the initial flowchart(s) as either sub-component operations or additional component operations building on one or more earlier-presented flowcharts. Those having skill in the art will appreciate that the style of presentation utilized herein (e.g., beginning with a presentation of a flowchart(s) presenting an example implementation and thereafter providing additions to and/or further details in subsequent flowcharts) generally allows for a rapid and easy understanding of the various process implementations. In addition, those skilled in the art will further appreciate that the style of presentation used herein also lends itself well to modular and/or object-oriented program design paradigms.
0092<figref idref="DRAWINGS">FIG. 8A</figref> is a flow diagram <b>800</b>A illustrating an example method for at least one device with regard to behavioral fingerprinting via social networking interaction in accordance with certain example embodiments. As illustrated, flow diagram <b>800</b>A may include any of operations <b>802</b>-<b>804</b>. Although operations <b>802</b>-<b>804</b> are shown or described in a particular order, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations. Also, at least some operation(s) of flow diagram <b>800</b>A may be performed so as to be fully or partially overlapping with other operation(s). For certain example embodiments, one or more operations of flow diagram <b>800</b>A may be performed by at least one user device (e.g., a user device <b>102</b>) or at least one server device (e.g., a server device <b>112</b>).
0093For certain example embodiments, a method for behavioral fingerprinting via social networking interaction, which method may be at least partially implemented using hardware (e.g., circuitry, at least one processor, processor-accessible memory, a combination thereof, etc.) such as that of at least one of a user device or a server device, may comprise an operation <b>802</b> or an operation <b>804</b>. An operation <b>802</b> may be directed at least partially to obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction. For certain example implementations, at least one device <b>102</b> or <b>112</b> (e.g., a user device <b>102</b>, a server device <b>112</b>, multiple ones thereof, etc.) may obtain (e.g., acquire, ascertain, receive, retrieve, accept, load, extract, determine, a combination thereof, etc. from the at least one device itself, from at least one memory, from another device, from a program or data structure, from a message or other communication, from another location, a combination thereof, etc.) at least one indication of family relation <b>706</b> (e.g., one or more indications representing one or more familial relations (e.g., legal, biological, marital, family-in-law such as mother-in-law, parent-child, natural parent-child, adopted parent-child, daughter, uncle, a combination thereof, etc.) between at least one authorized user and one or more individuals) for at least one authorized user (e.g., a user <b>104</b> that is authorized to use a given user device <b>102</b> to at least some extent, a user <b>104</b> that is associated with a behavioral fingerprint corresponding to a given user device <b>102</b>, a combination thereof, etc.) via at least one social networking interaction <b>710</b> (e.g., an interaction with infrastructure of a social network such as a server device thereof, an interaction with another entity using a social network, an interaction with a social network web site, an interaction with a social network app, an interaction with an outgoing communication for a social network, an interaction with an incoming communication for a social network, an interaction with a propagating communication for a social network, an interaction with a user profile of a social network, a combination thereof, etc.). By way of example but not limitation, a service provider (e.g., an authentication service provider operating at least partially via a cloud computing service or a web infrastructure, such as Apple's iCloud or ebay's PayPal) may obtain (e.g., acquire in response to an inquiry or inspection) at least one indication (e.g., a label, a categorization, a code, one or more words, a combination thereof, etc.) of family relation (e.g., a parent-child or spousal family relationship) for at least one authorized user (e.g., an owner or permitted operator of an Apple iPhone) via at least one social networking interaction (e.g., a message that is received via Facebook or a post that is uploaded to Facebook). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0094For certain example embodiments, an operation <b>804</b> may be directed at least partially to incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user. For certain example implementations, at least one device <b>102</b> or <b>112</b> (e.g., a user device <b>102</b>, a server device <b>112</b>, multiple ones thereof, etc.) may incorporate <b>712</b> (e.g., add, integrate, supplement with, establish links between or among individuals reflecting familial relations thereof, update using, augment with, replace with, modify using, adapt using, change statistics using, create at least one new predicted act based at least partially on, alter at least one existing predicted act based at least partially on, a combination thereof, etc.) at least one indication (e.g., a family status designation in a social network account profile, an explicit textual designation in a description of a photo posting, an implicit textual implication in a direct message posting, a family status designation from a social network grouping, a combination thereof, etc.) of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with the at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>302</b>-<b>322</b> (e.g., one or more of any of indicators <b>302</b>-<b>322</b> of <figref idref="DRAWINGS">FIG. 3</figref> as described herein above, including but not limited to predicted acts <b>322</b>) of utilization <b>708</b> (e.g., accessing, using, interacting with, carrying, moving from place to place, providing input to, receiving output from, communicating with, running apps on, requesting or completing or effecting transactions via, directing operation of, a combination thereof, etc.) of one or more user devices <b>102</b> by at least one authorized user <b>104</b>. By way of example but not limitation, a service provider (e.g., an authentication service provider operating at least partially via the Internet or a mobile device operating system, such as a Google web service or a Google Android OS) may incorporate (e.g., add at least one piece of datum of) at least one indication of family relation into at least one behavioral fingerprint (e.g., a collection of acts or characteristics) that is associated with (e.g., that are derived or attributable to) at least one authorized user (e.g., an owner or registered user of an Android-based smart phone), with the at least one behavioral fingerprint including one or more indicators of utilization (e.g., one or more stored representations of how a user operates a user interface of an Android device, an identification of one or more entities interacted with via the Android device, or a listing of one or more locations visited using the Android device) of one or more user devices (e.g., an Android-based smart phone such as a Samsung Galaxy) by the at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0095<figref idref="DRAWINGS">FIGS. 8B-8M</figref> depict example additions or alternatives for a flow diagram of <figref idref="DRAWINGS">FIG. 8A</figref> in accordance with certain example embodiments. As illustrated, flow diagrams of <figref idref="DRAWINGS">FIGS. 8B-8M</figref> may include any of the illustrated or described operations. Although operations are shown or described in a particular order or with a particular relationship to one or more other operations, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations (e.g., operations that are illustrated as nested blocks are not necessarily subsidiary operations and may instead be performed independently). Also, at least some operation(s) of flow diagrams of <figref idref="DRAWINGS">FIGS. 8B-8M</figref> may be performed so as to be fully or partially overlapping with other operation(s).
0096<figref idref="DRAWINGS">FIG. 8B</figref> illustrates a flow diagram <b>800</b>B having example operations <b>808</b>, <b>810</b>, <b>812</b>, or <b>814</b>. For certain example embodiments, an operation <b>808</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining at least one indication of a legal family relation for the at least one authorized user via the at least one social network interaction. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of a legal family relation (e.g., a familial relation that is created, recognized, regulated, a combination thereof, etc. by common or statutory law, including but not limited to, domestic partners, spouses, marriages, adoptions, etc.) for at least one authorized user (e.g., a user <b>104</b> that is authorized to use a given user device <b>102</b> to at least some extent, a user <b>104</b> that is associated with a behavioral fingerprint corresponding to a given user device <b>102</b>, a combination thereof, etc.) via at least one social network interaction <b>710</b> (e.g., establishing or reading a user account profile). By way of example but not limitation, an app that is local to a device may obtain at least one indication of a legal family relation (e.g., a marriage or domestic partnership between two people) for the at least one authorized user via at least one social network interaction (e.g., a creation or instance of a user profile). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0097For certain example embodiments, an operation <b>810</b> may be directed at least partially to wherein the obtaining at least one indication of a legal family relation for the at least one authorized user via the at least one social network interaction (of operation <b>808</b>) comprises obtaining at least one indication of a spousal family relationship for the at least one authorized user via the at least one social network interaction. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of a spousal family relationship (e.g., a married relationship, a husband and wife relationship, a combination thereof, etc.) for at least one authorized user via at least one social network interaction <b>710</b> (e.g., a social network posting). By way of example but not limitation, a web app or server may obtain (e.g., via scraping of a web site or web page) at least one indication of a spousal family relationship (e.g., that two people are spouses, such as a husband and a wife) for the at least one authorized user via at least one social network interaction (e.g., writing on a user's Facebook wall that indicates that he or she has a spouse named “Margaret” or “Robert”). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0098For certain example embodiments, an operation <b>812</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining at least one indication of a biological family relation for the at least one authorized user via the at least one social network interaction. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of a biological family relation (e.g., blood, genetic, mother, son, paternal grandmother, niece, great aunt, second cousin, a combination thereof, etc.) for at least one authorized user via at least one social network interaction <b>710</b>. By way of example but not limitation, a social network (e.g., Google+) may obtain at least one indication of a biological family relation (e.g., a parent-child relationship) for at least one authorized user via at least one social network interaction (e.g., speech converted to text from a Google+ hangout). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0099For certain example embodiments, an operation <b>814</b> may be directed at least partially to wherein the obtaining at least one indication of a biological family relation for the at least one authorized user via the at least one social network interaction (of operation <b>812</b>) comprises obtaining at least one indication of a parent-child family relationship for the at least one authorized user via the at least one social network interaction. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of a parent-child family relationship for at least one authorized user via at least one social network interaction <b>710</b> (e.g., a social network message that is sent or received). By way of example but not limitation, a network-based service (e.g., operated by Visa, MasterCard, American Express, Diner's Card, etc.) may obtain (e.g., infer) at least one indication of a parent-child family relationship (e.g., a father-son or father-daughter relationship) for at least one authorized user (e.g., a son or daughter, respectively) via at least one social network interaction (e.g., a private Tweet sent via Twitter that reads “Dad, please check out my grades”). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0100<figref idref="DRAWINGS">FIG. 8C</figref> illustrates a flow diagram <b>800</b>C having example operations <b>816</b>, <b>818</b>, <b>820</b>, or <b>822</b>. For certain example embodiments, an operation <b>816</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network <b>718</b> (e.g., a network, a service, a website, a computing infrastructure, an application, an interface, cloud computing, a combination thereof, etc. that enables or facilitates interaction (e.g., via text, images, audio, video, a combination thereof, etc.) between or among two or more members). By way of example but not limitation, a cloud-based service (e.g., a service from a debit card provider such as Bank of America) may obtain at least one indication of family relation (e.g., an indication of the existence of an aunt) for at least one authorized user via at least one social networking interaction (e.g., a message sent between or among at least two friends) from at least one social network (e.g., from Facebook or Myspace). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0101For certain example embodiments, an operation <b>818</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user from the at least one social network from profile data that is associated with an account for the at least one authorized user with the at least one social network. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user from at least one social network <b>718</b> from profile data <b>720</b> that is associated with an account for the at least one authorized user with the at least one social network. By way of example but not limitation, a web-based service (e.g., a service such as PayPal that may offer payment authentication services) may obtain at least one indication of family relation (e.g., a spouse, a first child's name, a second child's name, etc.) for at least one authorized user from at least one social network (e.g., Facebook) from profile data (e.g., demographic or other data that may be provided if the authorized user establishes a Facebook account) that is associated with an account (e.g., identifiable by a username such as an email or phone number) for the at least one authorized user with the at least one social network. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0102For certain example embodiments, an operation <b>820</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user from the at least one social network from profile data that is associated with an account for the at least one authorized user with the at least one social network (of operation <b>818</b>) comprises retrieving at least a portion of the profile data that is associated with the account for the at least one authorized user with the at least one social network via submission of at least one credential of the authorized user. For certain example implementations, at least one device may retrieve (e.g., acquire in response to a contemporaneous, previous, standing, a combination thereof, etc. request) at least a portion of profile data <b>720</b> that is associated with an account for at least one authorized user with at least one social network <b>718</b> via submission of (e.g., transmission to, entry of, reference to, a combination thereof, etc.) at least one credential (e.g., a username, an email address, a phone number, a password, a biometric input, a set of actions forming a pass pattern, answers to challenge questions, a combination thereof, etc.) of the authorized user. By way of example but not limitation, a server (e.g., that is operated by or for a retail company such as Starbucks) may retrieve at least a portion of profile data (e.g., family indications thereof) that is associated with an account for at least one authorized user with at least one social network (e.g., Facebook) via submission of at least one credential (e.g., a username, an email address, a phone number, a password, a code for a two-factor authentication process, a combination thereof, etc.) of the authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0103For certain example embodiments, an operation <b>822</b> may be directed at least partially to wherein the retrieving at least a portion of the profile data that is associated with the account for the at least one authorized user with the at least one social network via submission of at least one credential of the authorized user (of operation <b>820</b>) comprises submitting to the at least one social network at least one of a user name or a password of the authorized user. For certain example implementations, at least one device may submit (e.g., enter via a webpage, provide via a social network interoperability protocol, send via an encrypted package, a combination thereof, etc.) to at least one social network <b>718</b> at least one of a user name (e.g., text, an image, an email address, a physical address, a combination thereof, etc.) or a password (e.g., alphanumeric characters, a user interface input or pass pattern, a code, a biometric input, a token, a combination thereof, etc.) of an authorized user. By way of example but not limitation, a web presence of a social network (e.g., a server of Google+ or another Google service) may submit to at least one social network (e.g., Facebook) at least one of a user name (e.g., an email address or a phone number) or a password (e.g., an alphanumeric character string) of the authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0104<figref idref="DRAWINGS">FIG. 8D</figref> illustrates a flow diagram <b>800</b>D having example operations <b>824</b>, <b>826</b>, <b>828</b>, or <b>830</b>. For certain example embodiments, an operation <b>824</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user from the at least one social network via an application programming interface (API) that is exposed by the at least one social network to enable retrieval of family relation indications. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user from at least one social network <b>718</b> via an API that is exposed (e.g., hardware, software, or firmware infrastructure is provided to make an API available for calling, accessing, or using; an API is documented publicly; a combination thereof; etc.) by at least one social network <b>718</b> to enable retrieval (e.g., extracting, pulling, ascertaining, accessing, a combination thereof, etc.) of family relation indications. By way of example but not limitation, an application on a user device (e.g., an app that enables purchasing such as an Amazon app) may obtain at least one indication of family relation (e.g., children's names) for at least one authorized user (e.g., a parent) from at least one social network (e.g., Facebook) via an API that is exposed (e.g., documented in a software development/developer's kit) by the at least one social network to enable retrieval of family relation indications. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0105For certain example embodiments, an operation <b>826</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises retrieving the at least one indication of family relation for the at least one authorized user from at least a portion of one or more servers operated by or for the at least one social network. For certain example implementations, at least one device (e.g., at least one server <b>112</b>(<b>2</b>)) may retrieve at least one indication <b>706</b> of family relation for at least one authorized user from at least a portion (e.g., from a single physical or virtual server, from a distributed server, from a part of a server farm, from multiple servers, a combination thereof, etc.) of one or more servers (e.g., at least one server <b>112</b>(<b>1</b>)) operated by or for at least one social network <b>718</b>. By way of example but not limitation, at least one server device (e.g., an actual or virtual server of a cloud service such as Apple's iCloud) may retrieve at least one indication of family relation for at least one authorized user from at least a portion of one or more servers operated by or for at least one social network (e.g., from one or more servers operated for or by Classmates[dot]com). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0106For certain example embodiments, an operation <b>828</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user from the at least one social network using at least a portion of login data associated with the at least one authorized user. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user from at least one social network <b>718</b> using at least a portion of login data (e.g., a username, text, an image, an email address, a physical address, a phone number, a password, alphanumeric characters, a user interface input or pass pattern, a code, a biometric input, a token, a combination thereof, etc.) associated with the at least one authorized user. By way of example but not limitation, a cloud service (e.g., that authorizes payments electronically such as that of Google Wallet) may obtain at least one indication of family relation for at least one authorized user from at least one social network (e.g., LinkedIn) using at least a portion of login data (e.g., email or password) associated with the at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0107For certain example embodiments, an operation <b>830</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user from the at least one social network using at least a portion of login data associated with the at least one authorized user (of operation <b>828</b>) comprises submitting to the at least one social network at least a portion of biometric data associated with the at least one authorized user. For certain example implementations, at least one device may submit (e.g., send, input, transmit, enter, apply, a combination thereof, etc.) to at least one social network <b>718</b> at least a portion of biometric data (e.g., data representing or derived from an iris scan, a voice sample, a fingerprint image, a combination thereof, etc.) associated with at least one authorized user. By way of example but not limitation, a user-device-resident app (e.g., an app associated with a fast food chain such as McDonald's that is executable on a user device) may submit to at least one social network (e.g., Google+) at least a portion of biometric data (e.g., data representing a fingerprint image that is obtained from a user device's memory or a user device's fingerprint scanner) associated with at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0108<figref idref="DRAWINGS">FIG. 8E</figref> illustrates a flow diagram <b>800</b>E having example operations <b>832</b>, <b>834</b><i>a</i>, <b>834</b><i>b</i>, or <b>836</b>. For certain example embodiments, an operation <b>832</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises obtaining permission from the at least one authorized user to access at least a portion of a profile that is marked private via the at least one social network. For certain example implementations, at least one device may obtain permission (e.g., approval, capability, resources to effectuate, a link or code to pursue, a combination thereof, etc.) from at least one authorized user to access at least a portion (e.g., one or more fields but not necessarily all fields) of a profile <b>720</b> (e.g., social network member information associated with a social network account) that is marked private (e.g., that is opaque to one or more or certain other social network members, to partners of a social network entity, to programmers utilizing an API of a social network, a combination thereof, etc.) via at least one social network <b>718</b>. By way of example but not limitation, an-internet-enabled payment service (e.g., from a banking institution such as Chase or Capital One) may obtain permission (e.g., one or more access credentials, a one-time code, a direct link, a general password, a profile-accessing-specific password—such as one that enables access to at least a portion of a profile but not to other aspects of a social network member's account, a combination thereof, etc.) from at least one authorized user (e.g., a customer of Chase or Capital One and a Google+ member) to access at least a portion of a profile (e.g., account information) that is marked private via the at least one social network (e.g., Google+). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0109For certain example embodiments, an operation <b>834</b><i>a </i>and operation <b>834</b><i>b </i>may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises obtaining permission from the at least one authorized user to access at least a portion of a profile that is marked private via the at least one social network (for operation <b>834</b><i>a</i>) and retrieving the at least one indication of family relation from the at least a portion of the profile that is marked private utilizing a limited-use access code with the at least one social network (for operation <b>834</b><i>b</i>). For certain example implementations, at least one device may obtain permission from at least one authorized user to access at least a portion of a profile <b>720</b> that is marked private via at least one social network <b>718</b> and retrieve at least one indication <b>706</b> of family relation from the at least a portion of the profile that is marked private utilizing a limited-use (e.g., limited in duration of usability until an expiration of time, limited in number of uses, limited in what fields of a profile may be accessed, a combination thereof, etc.) access code (e.g., an alphanumeric code, a URL or other hyper-link-type code, a macro or multi-step processing code, a combination thereof, etc.) with the at least one social network. By way of example but not limitation, an authentication or authorization-oriented app (e.g., that stores or manages passwords, such as one by Norton Security or Passpack) on a user device may obtain permission from at least one authorized user to access at least a portion of a profile that is marked private via at least one social network (e.g., Facebook) and retrieve the at least one indication of family relation from the at least a portion of the profile (e.g., from a listing of name(s) in a field or fields labeled “children”) that is marked private (e.g., “do not share”, “not public”, “private”, etc.) utilizing a limited-use access code (e.g., a one-time use password that expires within 24 hours of its generation) with the at least one social network (e.g., Facebook). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0110For certain example embodiments, an operation <b>836</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network (of operation <b>816</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user from the at least one social network via an interoperability protocol for social networking. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user from at least one social network <b>718</b> via an interoperability protocol for social networking (e.g., a protocol designed to enable social networks to exchange data with each other, a protocol intended for social network members to share data between or among accounts of different social networks, a protocol that enables a third party to access different social networks using one or more common procedures or data formats, a combination thereof, etc.). By way of example but not limitation, a cloud-based service (e.g., one or more of Amazon Cloud Services) may obtain at least one indication of family relation (e.g., an indication of a grandparent relationship) for at least one authorized user from at least one social network (e.g., Orkut) via an interoperability protocol for social networking (e.g., OpenID or OpenSocial). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0111<figref idref="DRAWINGS">FIG. 8F</figref> illustrates a flow diagram <b>800</b>F having example operations <b>838</b>, <b>840</b>, <b>842</b>, <b>844</b>, <b>846</b>, or <b>847</b>. For certain example embodiments, an operation <b>838</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network application. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network application <b>722</b> (e.g., an application stored at, executing on, a combination thereof, etc. a user device <b>102</b> or an application that is separate from or at least partially integrated with an OS of a user device <b>102</b>). By way of example but not limitation, code executing on a server (e.g., a server device <b>112</b>(<b>2</b>) of <figref idref="DRAWINGS">FIG. 7B</figref>) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction (e.g., a message sent via Facebook) from at least one social network application (e.g., a Facebook application). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0112For certain example embodiments, an operation <b>840</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network application (of operation <b>838</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network mobile application. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network mobile application <b>722</b>. By way of example but not limitation, a module of a mobile device operating system (e.g., at least a portion of an Android OS on an HTC smart phone) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction (e.g., a message received via Facebook) from at least one social network mobile application (e.g., a Facebook iOS application optimized for Apple's iPad). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0113For certain example embodiments, an operation <b>842</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network application (of operation <b>838</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network desktop application. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network desktop application <b>722</b>. By way of example but not limitation, a desktop security program (e.g., a module of a Microsoft Windows OS or a Symantec program) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction (e.g., an incoming tweet for a Twitter account) from at least one social network desktop application (e.g., a Twitter application executing on or in conjunction with a Microsoft Windows OS on a desktop machine). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0114For certain example embodiments, an operation <b>844</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network application (of operation <b>838</b>) comprises retrieving the at least one indication of family relation for the at least one authorized user from one or more storage locations used by the at least one social network application. For certain example implementations, at least one device may retrieve at least one indication of family relation <b>706</b> for at least one authorized user from one or more storage locations (e.g., of a user device <b>102</b>) used by (e.g., a memory segment allocated to, a memory block reserved for, one or more memory locations accessible to, a combination thereof, etc.) at least one social network application <b>722</b>. By way of example but not limitation, an application on a user device that is in communication with a cloud service (e.g., an Amazon store app for Android) may retrieve at least one indication of family relation (e.g., an indication that an addressee of an Amazon address book is a nephew) for at least one authorized user from one or more storage locations (e.g., a portion of integrated or removable or expandable memory on a tablet computing device) used by at least one social network application (e.g., a Google+ application on a Samsung Galaxy Tab). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0115For certain example embodiments, an operation <b>846</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network application (of operation <b>838</b>) comprises querying the at least one social network application to obtain the at least one indication of family relation for the at least one authorized user from the at least one social network application. For certain example implementations, at least one device may query (e.g., ask, interrogate, access an API of, poll, a combination thereof, etc.) at least one social network application <b>722</b> to obtain at least one indication of family relation <b>706</b> for at least one authorized user from at least one social network application <b>722</b>. By way of example but not limitation, a cloud service such as a storage provider (e.g., Dropbox) may query at least one social network application (e.g., a Google+ application running on an Apple iPhone) to obtain at least one indication of family relation (e.g., an identification of a spouse) for at least one authorized user from the at least one social network application. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0116For certain example embodiments, an operation <b>847</b> may be directed at least partially to wherein the querying the at least one social network application to obtain the at least one indication of family relation for the at least one authorized user from the at least one social network application (of operation <b>846</b>) comprises sending a query from at least one server to the at least one social network application to obtain the at least one indication of family relation for the at least one authorized user from the at least one social network application. For certain example implementations, at least one device may send a query (e.g., a request, an inquiry, a poll, a combination thereof, etc.) from at least one server <b>112</b>(<b>2</b>) to at least one social network application <b>722</b> (e.g., executing on a user device <b>102</b>) to obtain at least one indication <b>706</b> of family relation for at least one authorized user from at least one social network application <b>722</b>. By way of example but not limitation, a server that is part of a cloud computing service or system (e.g., a server device operated by or for Amazon Cloud Player) may send a query from at least one server to at least one social network application (e.g., an application executing for or associated with Classmates[dot]com) to obtain at least one indication of family relation (e.g., a list of sibling names or children names for fraud-detection purposes) for at least one authorized user from the at least one social network application. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0117<figref idref="DRAWINGS">FIG. 8G</figref> illustrates a flow diagram <b>800</b>G having example operations <b>848</b>, <b>850</b>, <b>852</b>, <b>854</b>, or <b>856</b>. For certain example embodiments, an operation <b>848</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one browser-based interaction. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one browser-based interaction (e.g., text, images, videos, files, etc. downloaded via a browser; text, images, videos, files, etc. uploaded via a browser, such as a web browser; data stored by (e.g., in or under the direction of) a browser, such as a web browser; a combination thereof; etc.). By way of example but not limitation, a web browser plug-in (e.g., a Yahoo! toolbar) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction (e.g., checking for Facebook news feed updates) from at least one browser-based interaction (e.g., an interaction with Safari, Internet Explorer, Chrome, Opera, Firefox, Silk, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0118For certain example embodiments, an operation <b>850</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one browser-based interaction (of operation <b>848</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via at least one of an incoming communication or an outgoing communication for a browser that is facilitating the at least one browser-based interaction. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one of an incoming communication (e.g., data received at a user device and processed—such as presented to a user or manipulated—at least partially with a browser) or an outgoing communication (e.g. data transmitted from a user device that is processed—such as accepted from a user or manipulated—at least partially with a browser) for a browser that is facilitating the at least one browser-based interaction. By way of example but not limitation, a server that is monitoring browser communications (e.g., a server that is providing accelerated page processing for an Amazon Silk browser) may obtain at least one indication of family relation for at least one authorized user via at least one of an incoming communication (e.g., a LinkedIn update) or an outgoing communication (e.g., a captioned picture being uploaded) for a browser (e.g., Silk) that is facilitating the at least one browser-based interaction (e.g., an interaction with a social network via browser functionality). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0119For certain example embodiments, an operation <b>852</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one browser-based interaction (of operation <b>848</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via at least one browser module for a browser that is facilitating the at least one browser-based interaction. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one browser module (e.g., a plug-in, an add-in, an extension, a combination thereof, etc.) for a browser that is facilitating at least one browser-based interaction. By way of example but not limitation, a security-based browser module (e.g., a Kaspersky safe browsing extension) may obtain at least one indication of family relation for at least one authorized user for a browser (e.g., Chrome) that is facilitating at least one browser-based interaction. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0120For certain example embodiments, an operation <b>854</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via at least one browser module for a browser that is facilitating the at least one browser-based interaction (of operation <b>852</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via at least one browser plug-in for the browser that is facilitating the at least one browser-based interaction. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one browser plug-in (e.g., a plug-in for Internet Explorer or Firefox) for a browser that is facilitating at least one browser-based interaction. By way of example but not limitation, at least one browser plug-in (e.g., a search toolbar such as a Bing toolbar for Internet Explorer) may obtain at least one indication of family relation for at least one authorized user for a browser that is facilitating the at least one browser-based interaction. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0121For certain example embodiments, an operation <b>856</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one browser-based interaction (of operation <b>848</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via at least one cookie stored by a browser that is facilitating the at least one browser-based interaction. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one cookie (e.g., a Hypertext Transfer Protocol (HTTP) cookie, a piece of data saved on a user device by a website via a browser function or capability, a storage location associated with a website as allotted by a browser, a combination thereof, etc.) stored by a browser (e.g., stored in a browser; stored under the direction of a browser; stored into a block of memory allocated to a browser; stored in response to a command initiated at, authorized by, or routed through a browser; a combination thereof; etc.) that is facilitating at least one browser-based interaction. By way of example but not limitation, a cloud-based service (e.g., Apple's iCloud) may obtain at least one indication of family relation for at least one authorized user via at least one cookie (e.g., by reading data saved by Ancestry[dot]com or another website and) stored by a browser (e.g., stored by Safari on an iMac) that is facilitating at least one browser-based interaction. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0122<figref idref="DRAWINGS">FIG. 8H</figref> illustrates a flow diagram <b>800</b>H having example operations <b>858</b>, <b>860</b>, <b>862</b>, or <b>864</b>. For certain example embodiments, an operation <b>858</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation (e.g., a listing of in-laws living in the same state) for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network communication <b>724</b> (e.g., a message, a tweet, a post, a pin, a picture, a video, wall writing, streamed items, news items, a combination thereof, etc.). By way of example but not limitation, a cloud-based payment authorization service (e.g., Google Wallet) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one social network communication (e.g., a Twitter tweet). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0123For certain example embodiments, an operation <b>860</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication flow. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network communication flow (e.g., a continuous or intermittent or ongoing flow of information from or to a social network). By way of example but not limitation, a cloud-based payment authorization service (e.g., PayPal) may obtain at least one indication of family relation (e.g., a new addition to a family) for at least one authorized user via at least one social networking interaction from at least one social network communication flow (e.g., a news feed, an update stream, an activity stream, a Twitter stream, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0124For certain example embodiments, an operation <b>862</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication flow (of operation <b>860</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network stream. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network stream. By way of example but not limitation, a local security app (e.g., from Symantec) running on a user device may obtain at least one indication of family relation (e.g., a father's name) for at least one authorized user via at least one social networking interaction from at least one social network stream (e.g., a Google+ Stream). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0125For certain example embodiments, an operation <b>864</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication flow (of operation <b>860</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network news feed. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network news feed. By way of example but not limitation, a security service that is at least partially cloud-based (e.g., a TrendMicro computing-device-monitoring service) may obtain at least one indication of family relation (e.g., a picture caption indicating a person's status as a brother) for at least one authorized user via at least one social networking interaction from at least one social network news feed (e.g., Facebook's News Feed). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0126<figref idref="DRAWINGS">FIG. 8I</figref> illustrates a flow diagram <b>800</b>I having example operations <b>866</b>, <b>868</b>, <b>870</b>, or <b>872</b>. For certain example embodiments, an operation <b>866</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one message sent to one or more followers. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one message (e.g., a post, a tweet, a combination thereof, etc.) sent to one or more followers (e.g., other social network members, social network members that subscribe to a particular social network member's social network communications, social network members that affirmatively agree to receive messages from an identified social network member, a combination thereof, etc.). By way of example but not limitation, a web-based service (e.g., provided by a home security company such as ADT) may obtain at least one indication of family relation (e.g., a cousin that is coming to visit) for at least one authorized user via at least one social networking interaction from at least one message (e.g., a tweet) sent to one or more followers (e.g., Twitter followers). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0127For certain example embodiments, an operation <b>868</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one posting to one or more social network members. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one posting (e.g., an image, a picture, a video, text, a message, a tweet, a pin, a combination thereof, etc.) to one or more social network members (e.g., Facebook friends, people included in a Google+ circle, Twitter followers, people included in a Pinterest Group, a combination thereof, etc.). By way of example but not limitation, an operating system (OS) feature or function (e.g., a capability of a Microsoft Windows 8 OS) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one posting (e.g., a message or notice submitted to a Google+ stream) to one or more social network members (e.g., Google+ members within a particular circle). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0128For certain example embodiments, an operation <b>870</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication having at least one explicit statement of family relationship. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network communication <b>724</b> having at least one explicit statement of family relationship (e.g., a statement that presents a family relationship as existing or being in effect). By way of example but not limitation, an operating system feature or function (e.g., an Apple iOS capability) may obtain at least one indication of family relation (e.g., that an iTunes or Apple ID account holder has an aunt) for at least one authorized user via at least one social networking interaction from at least one social network communication (e.g., an incoming or outgoing textual message) having at least one explicit statement of family relationship (e.g., a message that reads, “My Aunt is Samantha Villanova.”). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0129For certain example embodiments, an operation <b>872</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication having at least one implicit statement of family relationship. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network communication <b>724</b> having at least one implicit statement of family relationship (e.g., a statement that implies a family relationship is extant). By way of example but not limitation, a credit card company may establish a cloud service to monitor accounts for suspicious or legitimate-appearing charges (e.g., a Visa service that balances questionable charge requests against actual or likely family relations) and may obtain at least one indication of family relation (e.g., an indication that Mathew's father is William) for at least one authorized user via at least one social networking interaction from at least one social network communication (e.g., from a Twitter tweet) having at least one implicit statement of family relationship (e.g., an incoming tweet from Mathew's Twitter account to William's Twitter account that reads, “Dad, please retweet this.”). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0130<figref idref="DRAWINGS">FIG. 8J</figref> illustrates a flow diagram <b>800</b>J having example operations <b>874</b> or <b>876</b>. For certain example embodiments, an operation <b>874</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication that includes text associated with an image. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network communication <b>724</b> that includes text (e.g., a caption, metadata, Twitter handle, account name, post description, title of a picture or video, description of a video, a combination thereof, etc.) associated with an image (e.g., at least one static image such as a snapshot or one or more moving images such as a video). By way of example but not limitation, a company-specific app on a user device (e.g., a rewards or payment app from Target) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one social network communication (e.g., a photo tweeted via Twitter) that includes text (e.g., up to 140 characters entered by a user) that is associated with an image (e.g., a snapshot picture taken by an iPhone and tweeted via Twitter). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0131For certain example embodiments, an operation <b>876</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication that includes text associated with an image (of operation <b>874</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication that includes a textual caption for a photograph. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one social network communication <b>724</b> that includes a textual caption (e.g., alphanumeric characters describing the picture or representing an account owner) for a photograph (e.g., a still image captured by a mobile device or camera). By way of example but not limitation, a security feature of a mobile device (e.g., an authorization or authentication component of an Android OS) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one social network communication that includes a textual caption for a photograph (e.g., a picture posted to a Google+ stream that includes or is associated with text entered by a posting party). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0132<figref idref="DRAWINGS">FIG. 8K</figref> illustrates a flow diagram <b>800</b>K having example operations <b>878</b>, <b>880</b>, or <b>882</b>. For certain example embodiments, an operation <b>878</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one textual message communicated at least partially using at least one social network. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one textual message (e.g., a message including alphanumeric characters or ideograms) communicated at least partially using at least one social network (e.g., communicated using a social network app, communicated using a social network website, communicated using a social network service, communicated using infrastructure of a social network, a combination thereof, etc.). By way of example but not limitation, a server of a social network service (e.g., a server operated by or for Facebook) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one textual message (e.g., a public posting to a News Feed or a private message) communicated at least partially using at least one social network (e.g., transmitted using a Facebook interface on a device or over at least one Facebook server). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0133For certain example embodiments, an operation <b>880</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one textual message communicated at least partially using at least one social network (of operation <b>878</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one textual message that is at least one of initiated or terminated at least partially using at least one social network interface of the at least one social network. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one textual message (e.g., a post, communication, email, or other message that includes text) that is at least one of initiated (e.g., composed, sent, addressed, a combination thereof, etc.) or terminated (e.g., viewed, heard, received, a combination thereof, etc.) at least partially using at least one social network interface (e.g., a browser-based social network interface, an app-based social network interface, a combination thereof, etc.) of at least one social network. By way of example but not limitation, a cloud service that is monitoring social network messages (e.g., a security service that is determining long-term or short-term characteristics of a security-conscious subscriber to the security service) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one textual message (e.g., a post to a Facebook News Feed) that is at least one of initiated or terminated (e.g., received or processed using HTML protocols appropriate for a webpage) at least partially using at least one social network interface of the at least one social network (e.g., with the webpage being served up by Facebook). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0134For certain example embodiments, an operation <b>882</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one textual message communicated at least partially using at least one social network (of operation <b>878</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one textual message that is propagated at least partially using at least one server operated by or for the at least one social network. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one textual message that is propagated (e.g., received, sent, transmitted, buffered, a combination thereof, etc.) at least partially using at least one server <b>112</b>(<b>1</b>) operated by or for at least one social network. By way of example but not limitation, a security-monitoring service from a credit card company (e.g., a fraud alert or avoidance program from Visa that is operating using at least one server owned by or a virtual-server-processing-allotment allocated to Visa card services from a server farm) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one textual message (e.g., a Twitter tweet that reads, “My brother's band is playing at Shangri-La tonight.”—e.g., in conjunction with a link to a webpage advertising Shrangi-La's upcoming musical performance groups and the band members thereof) that is propagated at least partially using at least one server operated by or for the at least one social network (e.g., a server owned by or a virtual-server-processing-allotment allocated to Twitter from a server farm). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0135<figref idref="DRAWINGS">FIG. 8L</figref> illustrates a flow diagram <b>800</b>L having example operations <b>884</b> or <b>885</b>. For certain example embodiments, an operation <b>884</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one social network communication (of operation <b>858</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from voice data derived from at least one of an audio call or a video call communicated at least partially using at least one social network. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from voice data (e.g., bytes representing a digitized voice, bytes representing text resulting from speech recognition being applied to a digitized voice, a combination thereof, etc.) derived from at least one of an audio call (e.g., a phone call, a voice-only call, a combination thereof, etc.) or a video call (e.g., a call including both voice and moving images) communicated at least partially using at least one social network (e.g., at least partially using servers or other infrastructure of a social network, at least partially using a social-network interface, at least partially using social network contact information, a combination thereof, etc.). By way of example but not limitation, a local authentication or authorization app (e.g., that is downloadable from an app store) on a user device may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from voice data derived from at least one of an audio call (e.g., a Skype call initiated or otherwise effectuated via Facebook) or a video call (e.g., a Google+ Hangout) communicated at least partially using at least one social network (e.g., Facebook or Google+, respectively). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0136For certain example embodiments, an operation <b>885</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one other device that is communicatively coupled to the one or more user devices. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one other device <b>714</b> (e.g., a security dongle, a credit card reader, a quick response (QR) code reader, a point-of-sale terminal, an accessory to a point-of-sale terminal, a combination thereof, etc.) that is communicatively coupled (e.g., wirelessly, by wire, connected thereto, integrated therewith, a combination thereof, etc.) to one or more user devices <b>102</b>. By way of example but not limitation, a cloud service that is to authorize purchases of authenticated users (e.g., iCloud in conjunction with an Apple ID) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one other device (e.g., a Square credit card reader for an iPhone) that is communicatively coupled to one or more user devices (e.g., that is inserted to a connector of an iPhone). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0137<figref idref="DRAWINGS">FIG. 8M</figref> illustrates a flow diagram <b>800</b>M having example operations <b>886</b>, <b>888</b>, or <b>890</b>. For certain example embodiments, an operation <b>886</b> may be directed at least partially to wherein the obtaining at least one indication of family relation for at least one authorized user via at least one social networking interaction (of operation <b>802</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one membership grouping of at least one social network. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one membership grouping (e.g., a set or list of social network members that are publicly or privately identified by at least one social network member as being related, as having something in common, as being addressable together for incoming or outgoing communications, as being appropriate for joint handling of associated social network communications, a combination thereof, etc.) of at least one social network. By way of example but not limitation, an internet or cloud-based payment service (e.g., an Intuit payment service) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one membership grouping (e.g., a Facebook grouping that is labeled, tagged, or otherwise indicated to be related to a family unit or familial relations) of at least one social network (e.g., Facebook). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0138For certain example embodiments, an operation <b>888</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one membership grouping of at least one social network (of operation <b>886</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one circle of social network members that is designated to relate to family. For certain example implementations, at least one device may obtain at least one indication of family relation <b>706</b> for at least one authorized user via at least one social networking interaction <b>710</b> from at least one circle (e.g., defined, identified, a combination thereof, etc. set) of social network members (e.g., entities that have joined or have an account with a social network) that is designated to relate to family. By way of example but not limitation, an app executing on a user device (e.g., a Lookout security app for Android OS) may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction from at least one circle of social network members (e.g., a Google+ Circle) that is designated to relate to family (e.g., one that is titled “immediate family”, described as “extended family” or “kids” or “parents”, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0139For certain example embodiments, an operation <b>890</b> may be directed at least partially to wherein the obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one membership grouping of at least one social network (of operation <b>886</b>) comprises obtaining the at least one indication of family relation for the at least one authorized user via the at least one social networking interaction from at least one posting group that is designated to relate to family. For certain example implementations, at least one device may obtain at least one indication <b>706</b> of family relation for at least one authorized user via at least one social networking interaction <b>710</b> from at least one posting group (e.g., a group of social network members that may be a joint recipient of a post) that is designated to relate to family. By way of example but not limitation, a server device that is part of a cloud service may obtain at least one indication of family relation for at least one authorized user via at least one social networking interaction (e.g., a pinned posting) from at least one posting group (e.g., a Pinterest group) that is designated to relate to family (e.g., a group entitled “Vanderbilt Family Retreat”). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0140<figref idref="DRAWINGS">FIGS. 9A-9G</figref> depict example additions or alternatives for a flow diagram of <figref idref="DRAWINGS">FIG. 8A</figref> in accordance with certain example embodiments. As illustrated, flow diagrams of <figref idref="DRAWINGS">FIGS. 9A-9G</figref> may include any of the illustrated or described operations. Although operations are shown or described in a particular order or with a particular relationship to one or more other operations, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations (e.g., operations that are illustrated as nested blocks are not necessarily subsidiary operations and may instead be performed independently). Also, at least some operation(s) of flow diagrams of <figref idref="DRAWINGS">FIGS. 9A-9G</figref> may be performed so as to be fully or partially overlapping with other operation(s).
0141<figref idref="DRAWINGS">FIG. 9A</figref> illustrates a flow diagram <b>900</b>A having example operations <b>908</b>, <b>910</b>, <b>912</b>, or <b>914</b>. For certain example embodiments, an operation <b>908</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises adding the at least one indication of family relation to the at least one behavioral fingerprint that is associated with the at least one authorized user. For certain example implementations, at least one device may add (e.g., augment, insert, include, supplement, append, join together, a combination thereof, etc.) at least one indication of family relation <b>706</b> to at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user. By way of example but not limitation, an internet or cloud-based security service may add at least one indication of family relation (e.g., an Apple iCloud server may insert an identification of a child) to at least one behavioral fingerprint that is associated with at least one authorized user (e.g., a behavioral fingerprint portion of an Apple ID profile stored at an Apple server farm). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0142For certain example embodiments, an operation <b>910</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises updating the at least one behavioral fingerprint that is associated with the at least one authorized user with the at least one indication of family relation. For certain example implementations, at least one device may update (e.g., replace a previous entry, modify a previous entry, remove at least part of a previous entry, connect, affix, a combination thereof, etc.) at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user with at least one indication <b>706</b> of family relation. By way of example but not limitation, an internet or cloud-based security service may update (e.g., an Apple iCloud server may change a child named “Pat” from being designated a son to being designated a daughter) at least one behavioral fingerprint that is associated with at least one authorized user (e.g., a behavioral fingerprint portion of an Apple ID profile stored at a user's iPhone) with at least one indication of family relation (e.g., an indication that a user's child named “Pat” has just joined “Curves”). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0143For certain example embodiments, an operation <b>911</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises deleting at least a portion of the at least one behavioral fingerprint that is associated with the at least one authorized user based at least partially on the at least one indication of family relation. For certain example implementations, at least one device may delete (e.g., remove, excise, write over, replace with something new, a combination thereof, etc.) at least a portion of at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user based at least partially on at least one indication of family relation <b>706</b>. By way of example but not limitation, an internet or cloud-based service may delete (e.g., a Microsoft-Azure based cloud service may remove) at least a portion of at least one behavioral fingerprint that is associated with at least one authorized user based at least partially on the at least one indication of family relation (e.g., may remove a spousal family relationship from a behavioral fingerprint based at least partially on a Facebook post indicating that a divorce has occurred). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0144For certain example embodiments, an operation <b>912</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises confirming that the at least one behavioral fingerprint that is associated with the at least one authorized user includes the at least one indication of family relation. For certain example implementations, at least one device may confirm (e.g., compare at least one newly-received family relation indication to one or more existing family relation designations) that at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user includes at least one indication of family relation <b>706</b>. By way of example but not limitation, a cloud-type service (e.g., a Google service such as Google Wallet) may confirm that at least one behavioral fingerprint that is associated with at least one authorized user includes at least one indication of family relation (e.g., verify that an obtained indication of sibling status exists or matches a current family relation designation in a Google Wallet security profile). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0145For certain example embodiments, an operation <b>914</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises establishing between or among one or more individuals at least one linkage that reflects at least one familial relation in the at least one behavioral fingerprint that is associated with the at least one authorized user based, at least partially, on the at least one indication of family relation. For certain example implementations, at least one device may establish (e.g., set-up, create, organize, provide, set-forth, a combination thereof, etc.) between or among one or more individuals (e.g., people, persons, social network members, other entities, a combination thereof, etc.) at least one linkage (e.g., a reference, a vector, an arrow, a family tree indicator, a pointer, a combination thereof, etc.) that reflects (e.g., represents, indicates, defines, explains, a combination thereof, etc.) at least one familial relation in at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user based, at least partially, on at least one indication of family relation <b>706</b>. By way of example but not limitation, an operating system feature (e.g., a function of a Google Android OS of an HTC smartphone) may establish between or among one or more individuals at least one linkage that reflects at least one familial relation (e.g., may create a reference between a user and another individual with the reference representing a parental relationship) in at least one behavioral fingerprint (e.g., in a security or other user-related file on the HTC smartphone) that is associated with at least one authorized user based, at least partially, on at least one indication of family relation. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0146<figref idref="DRAWINGS">FIG. 9B</figref> illustrates a flow diagram <b>900</b>B having example operations <b>918</b>, <b>920</b>, or <b>922</b>. For certain example embodiments, an operation <b>918</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of accessing one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of accessing (e.g., changing settings, entering a password, executing apps, using OS features, communicating with, a combination thereof, etc.) one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, an app on a user device (e.g., an app on a RIM Blackberry) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of accessing one or more user devices by the at least one authorized user (e.g., indicator(s) that a particular user has executed a particular app or has regularly changed brightness settings). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0147For certain example embodiments, an operation <b>920</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of interacting with one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication <b>706</b> of family relation into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of interacting with (e.g., manipulating, controlling I/O functions, working a user interface (UI), playing games, creating files, producing documents, a combination thereof, etc.) one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a shell on a smartphone (e.g., an HTC Sense UI or Touch Sense UI) may incorporate at least one indication of family relation (e.g., an indication that another user of a device is a spouse) into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of interacting with one or more user devices by the at least one authorized user (e.g., one or more indicators that a user has played certain games on a user device). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0148For certain example embodiments, an operation <b>922</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of movement of one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of movement (e.g., shaking movements, movements resulting from being carried from place to place, movements while being carried from place to place, movements while a person walks or runs, movement while a person rides on a form of transportation, a combination thereof, etc.) of one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, an app that enables point of sale purchases (e.g., a Dunkin Donuts app) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of movement of one or more user devices by the at least one authorized user (e.g., a Dunkin Donuts app can include indicators of which Dunkin Donut locations a user patronizes or what form of transportation—such as on foot or on a train—a user relies on to reach a given location). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0149<figref idref="DRAWINGS">FIG. 9C</figref> illustrates a flow diagram <b>900</b>C having example operations <b>924</b>, <b>926</b>, or <b>928</b>. For certain example embodiments, an operation <b>924</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of providing input to one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of providing input (e.g., controlling a device via a UI, speaking into a microphone, touching a screen with at least one finger, swiping a screen with one or more fingers, pressing buttons, a combination thereof etc.) to one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a retailer with a web presence (e.g., Walmart) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of providing input to one or more user devices by the at least one authorized user (e.g., a Walmart server—such as after an app from Walmart on a user device sends at least one family relation indication to the Walmart server—may incorporate the at least one family relation indication into a behavioral fingerprint that includes at least one user input characteristic, such as an indication of how a user swipes between pages or other visual screens on a user device). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0150For certain example embodiments, an operation <b>926</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of receiving output from one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of receiving output from (e.g., images displayed on a device screen, sounds played from a speaker, a combination thereof, etc.) one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a cloud server (e.g., a virtual server of a payment services company that leases server resources from a computing resources wholesaler, such as Amazon's Elastic Compute Cloud (ECC)) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of receiving output from one or more user devices by the at least one authorized user (e.g., a virtual server of a payment services company may incorporate at least one family relation indication into a behavioral fingerprint that includes at least one user output characteristic, such as volume levels used for phone calls and internet videos by a user). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0151For certain example embodiments, an operation <b>928</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of communicating via one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication <b>706</b> of family relation into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of communicating (e.g., indicators of how a user communicates—such as via text messaging, phone, email, a special app such as iMessage or Facetime, or video calling; indicators of to whom a user communicates—such as people or groups; indicators of when a user communicates; a combination thereof; etc.) via one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a cloud security service that monitors a user device (e.g., a Trend Micro security suite that monitors device usage at least partially from a location remote from the user device) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of communicating via one or more user devices by the at least one authorized user (e.g., a Trend Micro server may incorporate at least one family relation indication into a behavioral fingerprint that includes an indicator of what times and days of week a user calls his mother). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0152<figref idref="DRAWINGS">FIG. 9D</figref> illustrates a flow diagram <b>900</b>D having example operations <b>930</b> or <b>932</b>. For certain example embodiments, an operation <b>930</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of app execution on one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of app (e.g., software application) execution (e.g., at least one indicator of which apps are launched or run, how long apps are interacted with, a placement of app windows on a display screen, when apps are launched, a combination thereof, etc.) on one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, an app or feature with near-field communication (NFC) capabilities (e.g., an app or iOS feature on an Apple iPhone) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of app execution on one or more user devices by the at least one authorized user (e.g., an app or iOS feature of an iPhone may incorporate at least one family relation indication into a behavioral fingerprint that includes at least one app execution characteristic, such as how often a user accesses a Safari browser). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0153For certain example embodiments, an operation <b>932</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of effecting at least one transaction via one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of effecting at least one transaction (e.g., conducting, initiating, concluding, providing authorization, providing a source of funds, a combination thereof, etc. at least one purchase, order, procurement, exchange of consideration, a combination thereof, etc.) via one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a cloud component of a payment service (e.g., at least one server operated by or for PayPal) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of effecting at least one transaction via one or more user devices (e.g., a server of PayPal may incorporate at least one family relation indication into a behavioral fingerprint that includes at least one transaction characteristic, such as a vendor—e.g., Staples—that has been used before or an item category—e.g., ski equipment—that has been purchased from before) by the at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0154<figref idref="DRAWINGS">FIG. 9E</figref> illustrates a flow diagram <b>900</b>E having example operations <b>938</b> or <b>940</b>. For certain example embodiments, an operation <b>938</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of at least one user habit with respect to one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of at least one user habit (e.g., at least one act that is repeated at certain times of the day, on certain days of the week, in a certain manner, at a certain location, a combination thereof, etc.) with respect to one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a retail app (e.g., an app by McDonald's) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of at least one user habit (e.g., an app executing on a user device may incorporate at least one family relation indication into a behavioral fingerprint—which behavioral fingerprint may be located on a user device or at a remote server device—that includes at least one indicator of (i) an act—e.g., a purchase of a Big Mac with cheese and a small fry and soft drink—that occurs every Tuesday and Thursday or (ii) an act—e.g., texting a spouse—that occurs every weekday between 10 and 10:30 am) with respect to one or more user devices (e.g., a Nokia Lumia phone is executing an app that enables purchases at McDonald's using the phone) by the at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0155For certain example embodiments, an operation <b>940</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of at least one user habit with respect to one or more user devices by the at least one authorized user, (of operation <b>938</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of at least one user act that is repeated with respect to one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication <b>706</b> of family relation into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of at least one user act (e.g., viewing a series of three websites every Saturday and Sunday starting between 9:00 and 9:30 am) that is repeated with respect to one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, an OS of a mobile device (e.g., an Apple iOS) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of at least one user act (e.g., an iPhone or iPad may incorporate at least one family relation indication into a behavioral fingerprint that includes at least one repeated user act, such as using an iOS device to navigate to a lunch location each weekday starting at 11:00 am) that is repeated with respect to one or more user devices by the at least one authorized user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0156<figref idref="DRAWINGS">FIG. 9F</figref> illustrates a flow diagram <b>900</b>F having example operations <b>944</b>, <b>946</b>, <b>948</b>, or <b>950</b>. For certain example embodiments, an operation <b>944</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of observed usage of one or more user devices by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of observed usage (e.g., user interaction with, communication modes employed, apps employed, transactions conducted, social network interactions carried out, a combination thereof, etc.) of one or more user devices <b>102</b> by the at least one authorized user. By way of example but not limitation, a security app on a user device (e.g., a Symantec mobile security app) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of observed usage of one or more user devices by the at least one authorized user (e.g., a mobile device executing a Symantec mobile security app may incorporate at least one family relation indication into a behavioral fingerprint that includes at least one user act, such as a list of social network members contacted via at least one social network with the mobile device). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0157For certain example embodiments, an operation <b>946</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of observed usage of one or more user devices by the at least one authorized user, (of operation <b>944</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that includes one or more indicators of apps employed by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that includes one or more indicators <b>708</b> of apps employed (e.g., an identification of an app, a chronological listing of apps used each day, a duration of interaction for each app, a number of uses per day for a number of apps, a quality of play for a given app, features utilized for a particular app, a list of people contacted with a particular app, a combination thereof, etc.) by at least one authorized user. By way of example but not limitation, a desktop user device (e.g., an Apple iMac or an HP personal computer (PC)) may incorporate at least one indication of family relation into at least one behavioral fingerprint that includes one or more indicators of apps employed by at least one authorized user (e.g., an OS feature of an iMac, such as a feature of OS X, or of an HP PC, such as a feature of Microsoft Windows 8, may incorporate at least one family relation indication into a behavioral fingerprint that indicates that Microsoft Office is open or running each day from about 8:00 am to 3:00 pm). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0158For certain example embodiments, an operation <b>948</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of observed usage of one or more user devices by the at least one authorized user, (of operation <b>944</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that includes one or more indicators of transactions conducted by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that includes one or more indicators <b>708</b> of transactions conducted (e.g., a purchase, an order, a procurement, an exchange of consideration, a combination thereof, etc. that is initiated, concluded, authorized, financed, consummated, a combination thereof, etc.) by at least one authorized user. By way of example but not limitation, a payment authorization cloud service (e.g., an Amazon cloud service for authorizing payments for purchases made through Amazon via a user device) may incorporate at least one indication of family relation into at least one behavioral fingerprint that includes one or more indicators of transactions conducted by the at least one authorized user (e.g., an Android user device that is in communication with an Amazon server may incorporate at least one family relation indication into a behavioral fingerprint that includes a list of previous transactions made through Amazon or made with the Android user device). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0159For certain example embodiments, an operation <b>950</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of observed usage of one or more user devices by the at least one authorized user, (of operation <b>944</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that includes one or more indicators of social network interactions by the at least one authorized user. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that includes one or more indicators <b>708</b> of social network interactions (e.g., social networks logged into or otherwise accessed, social network members contacted, types of social network communication modes employed, times of social network use, social network apps used, games played via a social network, a combination thereof, etc.) by at least one authorized user. By way of example but not limitation, a payment authorization service (e.g., a bank debit card service) that is realized at least partially in a cloud environment may incorporate at least one indication of family relation into at least one behavioral fingerprint that includes one or more indicators of social network interactions by at least one authorized user (e.g., a Bank of America service that monitors social network interactions of an authorized user may incorporate at least one family relation indication into a behavioral fingerprint that indicates that the authorized user frequently posts to a particular neighbor's Facebook wall each day between lunch and dinner). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0160<figref idref="DRAWINGS">FIG. 9G</figref> illustrates a flow diagram <b>900</b>G having example operations <b>954</b> or <b>956</b>. For certain example embodiments, an operation <b>954</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of utilization of one or more user devices by the at least one authorized user, (of operation <b>804</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of at least one observed action by the at least one authorized user with regard to one or more user devices. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of at least one observed action by the at least one authorized user (e.g., a UI action, a user movement, a location visited by a user, a user status alert, a combination thereof, etc.) with regard to one or more user devices <b>102</b>. By way of example but not limitation, an app for a user device that enables at least semi-automatic unlocking of real-world objects (e.g., a car or house door based at least partially on proximity of the user device) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of at least one observed action by the at least one authorized user with regard to one or more user devices (e.g., one or more of the user devices may be executing a locking/unlocking app that may incorporate at least one family relation indication into a behavioral fingerprint that includes at least one indicator of how a user navigates between apps or at least one indicator of how long a user keeps a user device in motion before a particular door is to be unlocked). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0161For certain example embodiments, an operation <b>956</b> may be directed at least partially to wherein the incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of at least one observed action by the at least one authorized user with regard to one or more user devices, (of operation <b>954</b>) comprises incorporating the at least one indication of family relation into at least one behavioral fingerprint that is associated with the at least one authorized user, the at least one behavioral fingerprint including one or more indicators of at least one location visited by the at least one authorized user with regard to one or more user devices. For certain example implementations, at least one device may incorporate at least one indication of family relation <b>706</b> into at least one behavioral fingerprint <b>110</b> that is associated with at least one authorized user, with at least one behavioral fingerprint <b>110</b> including one or more indicators <b>708</b> of at least one location visited (e.g., a virtual location—such as a website or virtual world or location thereof; a physical location—such as an address, coordinates, or an identifiable place like a neighborhood or friend's home; a combination thereof; etc.) by the at least one authorized user with regard to one or more user devices. By way of example but not limitation, an OS of a Sony PC (e.g., Microsoft's Windows 8 of a Sony Vaio) may incorporate at least one indication of family relation into at least one behavioral fingerprint that is associated with at least one authorized user, with the at least one behavioral fingerprint including one or more indicators of at least one location visited by the at least one authorized user with regard to one or more user devices (e.g., an OS having security features, which may expose an authentication API to an app, may incorporate at least one family relation indication into a behavioral fingerprint that includes a list of a person's daily destinations to which a user device is carried). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.
0162Those skilled in the art will appreciate that the foregoing specific exemplary processes and/or devices and/or technologies are representative of more general processes and/or devices and/or technologies taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.
0163Those 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, software, and/or firmware implementations of aspects of systems; the use of hardware, software, and/or firmware 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), 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; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. 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.
0164In some implementations described herein, logic and similar implementations may include software or other control structures. Electronic circuitry, for example, may have one or more paths of electrical current constructed and arranged to implement various functions as described herein. In some implementations, one or more media may be configured to bear a device-detectable implementation when such media hold or transmit device detectable instructions operable to perform as described herein. In some variants, for example, implementations may include an update or modification of existing software or firmware, or of gate arrays or programmable hardware, such as by performing a reception of or a transmission of one or more instructions in relation to one or more operations described herein. Alternatively or additionally, in some variants, an implementation may include special-purpose hardware, software, firmware components, and/or general-purpose components executing or otherwise invoking special-purpose components. Specifications or other implementations may be transmitted by one or more instances of tangible transmission media as described herein, optionally by packet transmission or otherwise by passing through distributed media at various times.
0165Alternatively or additionally, implementations may include executing a special-purpose instruction sequence or invoking circuitry for enabling, triggering, coordinating, requesting, or otherwise causing one or more occurrences of virtually any functional operations described herein. In some variants, operational or other logical descriptions herein may be expressed as source code and compiled or otherwise invoked as an executable instruction sequence. In some contexts, for example, implementations may be provided, in whole or in part, by source code, such as C++, or other code sequences. In other implementations, source or other code implementation, using commercially available and/or techniques in the art, may be compiled/ /implemented/translated/converted into a high-level descriptor language (e.g., initially implementing described technologies in C or C++ programming language and thereafter converting the programming language implementation into a logic-synthesizable language implementation, a hardware description language implementation, a hardware design simulation implementation, and/or other such similar mode(s) of expression). For example, some or all of a logical expression (e.g., computer programming language implementation) may be manifested as a Verilog-type hardware description (e.g., via Hardware Description Language (HDL) and/or Very High Speed Integrated Circuit Hardware Descriptor Language (VHDL)) or other circuitry model which may then be used to create a physical implementation having hardware (e.g., an Application Specific Integrated Circuit). Those skilled in the art will recognize how to obtain, configure, and optimize suitable transmission or computational elements, material supplies, actuators, or other structures in light of these teachings.
0166The 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 Circuits (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 circuits, 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 (e.g., transmitter, receiver, transmission logic, reception logic, etc.), etc.).
0167In 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, and/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 memory (e.g., random access, flash, read only, etc.)), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, optical-electrical equipment, etc.). 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.
0168Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into a data processing system. Those having skill in the art will recognize that a data processing system generally includes one or more of a system unit housing, a video display device, memory such as volatile or non-volatile memory, processors such as microprocessors or digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices (e.g., a touch pad, a touch screen, an antenna, etc.), 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 data processing system may be implemented utilizing suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
0169For the purposes of this application, “cloud” computing may be understood as described in the cloud computing literature. For example, cloud computing may be methods and/or systems for the delivery of computational capacity and/or storage capacity as a service. The “cloud” may refer to one or more hardware and/or software components that deliver or assist in the delivery of computational and/or storage capacity, including, but not limited to, one or more of a client, an application, a platform, an infrastructure, and/or a server The cloud may refer to any of the hardware and/or software associated with a client, an application, a platform, an infrastructure, and/or a server. For example, cloud and cloud computing may refer to one or more of a computer, a processor, a storage medium, a router, a switch, a modem, a virtual machine (e.g., a virtual server), a data center, an operating system, a middleware, a firmware, a hardware back-end, a software back-end, and/or a software application. A cloud may refer to a private cloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloud may be a shared pool of configurable computing resources, which may be public, private, semi-private, distributable, scaleable, flexible, temporary, virtual, and/or physical. A cloud or cloud service may be delivered over one or more types of network, e.g., a mobile communication network, and the Internet.
0170As used in this application, a cloud or a cloud service may include one or more of infrastructure-as-a-service (“IaaS”), platform-as-a-service (“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service (“DaaS”). As a non-exclusive example, IaaS may include, e.g., one or more virtual server instantiations that may start, stop, access, and/or configure virtual servers and/or storage centers (e.g., providing one or more processors, storage space, and/or network resources on-demand, e.g., EMC and Rackspace). PaaS may include, e.g., one or more software and/or development tools hosted on an infrastructure (e.g., a computing platform and/or a solution stack from which the client can create software interfaces and applications, e.g., Microsoft Azure). SaaS may include, e.g., software hosted by a service provider and accessible over a network (e.g., the software for the application and/or the data associated with that software application may be kept on the network, e.g., Google Apps, SalesForce). DaaS may include, e.g., providing desktop, applications, data, and/or services for the user over a network (e.g., providing a multi-application framework, the applications in the framework, the data associated with the applications, and/or services related to the applications and/or the data over the network, e.g., Citrix). The foregoing is intended to be exemplary of the types of systems and/or methods referred to in this application as “cloud” or “cloud computing” and should not be considered complete or exhaustive.
0171Those skilled in the art will recognize that it is common within the art to implement devices and/or processes and/or systems, and thereafter use engineering and/or other practices to integrate such implemented devices and/or processes and/or systems into more comprehensive devices and/or processes and/or systems. That is, at least a portion of the devices and/or processes and/or systems described herein can be integrated into other devices and/or processes and/or systems via a reasonable amount of experimentation. Those having skill in the art will recognize that examples of such other devices and/or processes and/or systems might include—as appropriate to context and application—all or part of devices and/or processes and/or systems of (a) an air conveyance (e.g., an airplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., a car, truck, locomotive, tank, armored personnel carrier, etc.), (c) a building (e.g., a home, warehouse, office, etc.), (d) an appliance (e.g., a refrigerator, a washing machine, a dryer, etc.), (e) a communications system (e.g., a networked system, a telephone system, a Voice over IP system, etc.), (f) a business entity (e.g., an Internet Service Provider (ISP) entity such as Comcast Cable, Qwest, Southwestern Bell, etc.), or (g) a wired/wireless services entity (e.g., Sprint, Cingular, Nextel, etc.), etc.
0172In certain cases, use of a system or method may occur in a territory even if components are located outside the territory. For example, in a distributed computing context, use of a distributed computing system may occur in a territory even though parts of the system may be located outside of the territory (e.g., relay, server, processor, signal-bearing medium, transmitting computer, receiving computer, etc. located outside the territory). A sale of a system or method may likewise occur in a territory even if components of the system or method are located and/or used outside the territory. Further, implementation of at least part of a system for performing a method in one territory does not preclude use of the system in another territory.
0173One skilled in the art will recognize that the herein described components (e.g., operations), devices, objects, and the discussion accompanying them are used as examples for the sake of conceptual clarity and that various configuration modifications are contemplated. Consequently, as used herein, the specific exemplars set forth and the accompanying discussion are intended to be representative of their more general classes. In general, use of any specific exemplar is intended to be representative of its class, and the non-inclusion of specific components (e.g., operations), devices, and objects should not be taken limiting.
0174With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations are not expressly set forth herein for sake of clarity.
0175The 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 may 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.
0176In some instances, one or more components may be referred to herein as “configured to,” “configured by,” “configurable to,” “operable/operative to,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc. Those skilled in the art will recognize that such terms (e.g. “configured to”) can generally encompass active-state components and/or inactive-state components and/or standby-state components, unless context requires otherwise.
0177This application may make reference to one or more trademarks, e.g., a word, letter, symbol, or device adopted by one manufacturer or merchant and used to identify and distinguish his or her product from those of others. Trademark names used herein are set forth in such language that makes clear their identity, that distinguishes them from common descriptive nouns, that have fixed and definite meanings, and, in many if not all cases, are accompanied by other specific identification using terms not covered by trademark. In addition, trademark names used herein have meanings that are well-known and defined in the literature, and do not refer to products or compounds protected by trade secrets in order to divine their meaning. All trademarks referenced in this application are the property of their respective owners, and the appearance of one or more trademarks in this application does not diminish or otherwise adversely affect the validity of the one or more trademarks. All trademarks, registered or unregistered, that appear in this application are assumed to include a proper trademark symbol, e.g., the circle R or [trade], even when such trademark symbol does not explicitly appear next to the trademark. To the extent a trademark is used in a descriptive manner to refer to a product or process, that trademark should be interpreted to represent the corresponding product or process as of the date of the filing of this patent application.
0178While 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. 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 claims 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 typically a 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 unless context dictates otherwise. For example, the phrase “A or B” will be typically understood to include the possibilities of “A” or “B” or “A and B.”
0179With respect to the appended claims, those skilled in the art will appreciate that recited operations therein may generally be performed in any order. Also, although various operational flows are presented in a sequence(s), it should be understood that the various operations may be performed in other orders than those which are illustrated, or may be performed concurrently. Examples of such alternate orderings may include overlapping, interleaved, interrupted, reordered, incremental, preparatory, supplemental, simultaneous, reverse, or other variant orderings, unless context dictates otherwise. Furthermore, terms like “responsive to,” “related to,” or other past-tense adjectives are generally not intended to exclude such variants, unless context dictates otherwise.
0180While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Contents5
32 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2016267586A1 | Cited by | United States of America | Search report |
| US11789735B2 | Cited by | United States of America | Applicant |
| US2016267586A1 | Cited by | United States of America | Search report |
| US10783275B1 | Cited by | United States of America | Search report |
| US2016267586A1 | Cited by | United States of America | Search report |
| US10225261B2 | Cited by | United States of America | Search report |
| US2016267586A1 | Cited by | United States of America | Pre-grant |
| US2002025803A1 | Cites | United States of America | Search report |
| US2002046105A1 | Cites | United States of America | Applicant |
| US2002073046A1 | Cites | United States of America | Applicant |
| US2003063730A1 | Cites | United States of America | Applicant |
| US2003220980A1 | Cites | United States of America | Applicant |
| US2004002329A1 | Cites | United States of America | Applicant |
| US2004005051A1 | Cites | United States of America | Applicant |
| US2004193892A1 | Cites | United States of America | Applicant |
| US2005071643A1 | Cites | United States of America | Applicant |
| US2005100198A1 | Cites | United States of America | Applicant |
| US2005171832A1 | Cites | United States of America | Applicant |
| US2005246771A1 | Cites | United States of America | Applicant |
| US2005268107A1 | Cites | United States of America | Applicant |
| US2006020814A1 | Cites | United States of America | Applicant |
| US2006020816A1 | Cites | United States of America | Applicant |
| US2006020876A1 | Cites | United States of America | Applicant |
| US2006074769A1 | Cites | United States of America | Applicant |
| US2006133651A1 | Cites | United States of America | Applicant |
| US2006161553A1 | Cites | United States of America | Applicant |
| US2006218153A1 | Cites | United States of America | Applicant |
| US2006224898A1 | Cites | United States of America | Applicant |
| US2006250578A1 | Cites | United States of America | Search report |
| US2006288234A1 | Cites | United States of America | Applicant |
| US2007067853A1 | Cites | United States of America | Applicant |
| US2007084913A1 | Cites | United States of America | Search report |
| US2007218900A1 | Cites | United States of America | Search report |
| US2007226248A1 | Cites | United States of America | Applicant |
| US2007240203A1 | Cites | United States of America | Applicant |
| US2007245157A1 | Cites | United States of America | Applicant |
| US2007245158A1 | Cites | United States of America | Applicant |
| US2007250550A1 | Cites | United States of America | Applicant |
| US2008033941A1 | Cites | United States of America | Applicant |
| US2008091453A1 | Cites | United States of America | Applicant |
| US2008092209A1 | Cites | United States of America | Applicant |
| US2008098456A1 | Cites | United States of America | Applicant |
| US2008102766A1 | Cites | United States of America | Applicant |
| US2008126255A1 | Cites | United States of America | Applicant |
| US2008138472A1 | Cites | United States of America | Applicant |
| US2008146193A1 | Cites | United States of America | Applicant |
| US2008167002A1 | Cites | United States of America | Applicant |
| US2008172461A1 | Cites | United States of America | Applicant |
| US2008235614A1 | Cites | United States of America | Applicant |
| US2008281668A1 | Cites | United States of America | Applicant |
| US2009006846A1 | Cites | United States of America | Applicant |
| US2009025081A1 | Cites | United States of America | Applicant |
| US2009030985A1 | Cites | United States of America | Search report |
| US2009037285A1 | Cites | United States of America | Applicant |
| US2009060517A1 | Cites | United States of America | Applicant |
| US2009070435A1 | Cites | United States of America | Applicant |
| US2009093235A1 | Cites | United States of America | Applicant |
| US2009111491A1 | Cites | United States of America | Applicant |
| US2009113040A1 | Cites | United States of America | Applicant |
| US2009150507A1 | Cites | United States of America | Search report |
| US2009152343A1 | Cites | United States of America | Search report |
| US2009169062A1 | Cites | United States of America | Applicant |
| US2009210494A1 | Cites | United States of America | Applicant |
| US2009220653A1 | Cites | United States of America | Applicant |
| US2009228509A1 | Cites | United States of America | Applicant |
| US2009254975A1 | Cites | United States of America | Applicant |
| US2009292010A1 | Cites | United States of America | Applicant |
| US2009298514A1 | Cites | United States of America | Applicant |
| US2010073202A1 | Cites | United States of America | Applicant |
| US2010088157A1 | Cites | United States of America | Applicant |
| US2010115592A1 | Cites | United States of America | Applicant |
| US2010115610A1 | Cites | United States of America | Applicant |
| US2010130165A1 | Cites | United States of America | Applicant |
| US2010161544A1 | Cites | United States of America | Applicant |
| US2010169343A1 | Cites | United States of America | Applicant |
| US2010174709A1 | Cites | United States of America | Applicant |
| US2010177938A1 | Cites | United States of America | Search report |
| US2010179856A1 | Cites | United States of America | Applicant |
| US2010179857A1 | Cites | United States of America | Applicant |
| US2010185518A1 | Cites | United States of America | Applicant |
| US2010186066A1 | Cites | United States of America | Applicant |
| US2010241964A1 | Cites | United States of America | Search report |
| US2010250676A1 | Cites | United States of America | Applicant |
| US2010255172A1 | Cites | United States of America | Applicant |
| US2010274815A1 | Cites | United States of America | Applicant |
| US2010293094A1 | Cites | United States of America | Applicant |
| US2010299292A1 | Cites | United States of America | Applicant |
| US2010299757A1 | Cites | United States of America | Applicant |
| US2010306099A1 | Cites | United States of America | Applicant |
| US2010306828A1 | Cites | United States of America | Applicant |
| US2010319053A1 | Cites | United States of America | Applicant |
| US2010323730A1 | Cites | United States of America | Applicant |
| US2011016534A1 | Cites | United States of America | Applicant |
| US2011029887A1 | Cites | United States of America | Search report |
| US2011066615A1 | Cites | United States of America | Applicant |
| US2011070898A1 | Cites | United States of America | Applicant |
| US2011072487A1 | Cites | United States of America | Applicant |
| US2011112898A1 | Cites | United States of America | Applicant |
| WO2011119273A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2011131122A1 | Cites | United States of America | Applicant |
65 members in 3 offices; this record represents the family
Priority claims11
| Document | Office | Kind | Date |
|---|---|---|---|
| 201161632836 | United States of America | P | |
| 201161572309 | United States of America | P | |
| 201113373685 | United States of America | A | |
| 201113373684 | United States of America | A | |
| 201113373680 | United States of America | A | |
| 201113373677 | United States of America | A | |
| 201113373682 | United States of America | A | |
| 201213475564 | United States of America | A | |
| 201213538385 | United States of America | A | |
| 201213552502 | United States of America | A | |
| 201213563599 | United States of America | A |
Members65
| Document | Office | Kind | |
|---|---|---|---|
| US2013022201A1 | United States of America | A1 | |
| US2013024676A1 | United States of America | A1 | |
| US2013024867A1 | United States of America | A1 | |
| US2013024937A1 | United States of America | A1 | |
| US2013024939A1 | United States of America | A1 | |
| US2013031364A1 | United States of America | A1 | |
| US2013036314A1 | United States of America | A1 | |
| US2013036464A1 | United States of America | A1 | |
| US2013081039A1 | United States of America | A1 | |
| US2013081043A1 | United States of America | A1 | |
| US2013081134A1 | United States of America | A1 | |
| US2013097669A1 | United States of America | A1 | |
| US2013097683A1 | United States of America | A1 | |
| US2013104203A1 | United States of America | A1 | |
| US2013111489A1 | United States of America | A1 | |
| US2013111491A1 | United States of America | A1 | |
| US2013117214A1 | United States of America | A1 | |
| US2013133033A1 | United States of America | A1 | |
| US2013133052A1 | United States of America | A1 | |
| US2013133054A1 | United States of America | A1 | |
| US2013139262A1 | United States of America | A1 | |
| US2013151515A1 | United States of America | A1 | |
| US2013151617A1 | United States of America | A1 | |
| US2013159217A1 | United States of America | A1 | |
| US2013159413A1 | United States of America | A1 | |
| US2013160087A1 | United States of America | A1 | |
| US2013167207A1 | United States of America | A1 | |
| US2013191887A1 | United States of America | A1 | |
| US2013197968A1 | United States of America | A1 | |
| US8555077B2 | United States of America | B2 | |
| WO2014005067A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2014040989A1 | United States of America | A1 | |
| US8688980B2 | United States of America | B2 | |
| US8689350B2 | United States of America | B2 | |
| US8713704B2 | United States of America | B2 | |
| US2014123249A1 | United States of America | A1 | |
| US2014123253A1 | United States of America | A1 | |
| US8813085B2 | United States of America | B2 | |
| US8869241B2 | United States of America | B2 | |
| US8930714B2 | United States of America | B2 | |
| US2015020075A1 | United States of America | A1 | |
| US8943313B2 | United States of America | B2 | |
| US8955111B2 | United States of America | B2 | |
| US9015860B2 | United States of America | B2 | |
| EP2867843A1 | European Patent Office (EPO) | A1 | |
| US2015128262A1 | United States of America | A1 | |
| US9083687B2 | United States of America | B2 | |
| US9098608B2 | United States of America | B2 | |
| US9170843B2 | United States of America | B2 | |
| EP2867843A4 | European Patent Office (EPO) | A4 | |
| US9298900B2 | United States of America | B2 | |
| US9298918B2 | United States of America | B2 | |
| US9348985B2 | United States of America | B2 | |
| US9443085B2 | United States of America | B2 | |
| US2016277441A1 | United States of America | A1 | |
| US9460290B2 | United States of America | B2 | |
| US9465657B2 | United States of America | B2 | |
| US9471373B2 | United States of America | B2 | |
| US9558034B2 | United States of America | B2 | |
| US9575903B2 | United States of America | B2 | |
| US9621404B2 | United States of America | B2 | |
| US9729549B2 | United States of America | B2 | |
| US9798873B2 | United States of America | B2 | |
| US9813445B2 | United States of America | B2 | |
| US9825967B2This record | United States of America | B2 |
192 transactions on the USPTO file
Allowed after 3 non-final rejections, 3 final rejections and 3 RCEs.
- Non-final rejections
- 3
- Final rejections
- 3
- RCEs
- 3
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Response to Amendment under Rule 312N271 | N271 | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Interview Summary - Examiner Initiated - TelephonicMEXET | MEXET | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Response after Non-Final ActionA... | A... | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Interview Request CorrectionINCOR | INCOR | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Response after Non-Final ActionA... | A... | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Notice of Informal or Non-Responsive RCE AmendmentMCPA-AMD | MCPA-AMD | |
| RCE Amendment Informal or Non-ResponsiveCPA-AMD | CPA-AMD | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Letter Requesting Interview with ExaminerM865 | M865 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC |
16 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Certificate of correctionCC | CC | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 9825967
- Application
- 13602061
Titles
- English
- Behavioral fingerprinting via social networking interaction
Patent term adjustment
- A delay
- +323 daysthe office missed an examination deadline
- Applicant delay
- −450 days
- Net adjustment
- 0 days
Classification
- CPC, 6
- H04L63/107
- G06Q10/40
- G06F16/284
- G06Q20/3224
- G06Q20/4016
- G06Q50/01
- IPC, 4
- H04L29 06
- G06Q20 40
- G06Q20 32
- G06Q50 00