US20130144919A1 - Template development based on reported aspects of a plurality of source users - Google Patents

Template development based on reported aspects of a plurality of source users Download PDF

Info

Publication number
US20130144919A1
US20130144919A1 US13/656,288 US201213656288A US2013144919A1 US 20130144919 A1 US20130144919 A1 US 20130144919A1 US 201213656288 A US201213656288 A US 201213656288A US 2013144919 A1 US2013144919 A1 US 2013144919A1
Authority
US
United States
Prior art keywords
aspects
relevant
reported
operation
reported aspects
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/656,288
Inventor
Shawn P. Firminger
Jason Garms
Roderick A. Hyde
Edward K. Y. Jung
Chris D. Karkanias
Eric C. Leuthardt
Royce A. Levien
Richard T. Lord
Robert W. Lord
Mark A. Malamud
John D. Rinaldo, Jr.
Clarence T. Tegreene
Kristin M. Tolle
Lowell L. Wood, JR.
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Invention Science Fund I LLC
Original Assignee
Searete LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US12/584,489 priority Critical patent/US8265943B2/en
Priority to US12/584,653 priority patent/US8280746B2/en
Priority to US12/587,018 priority patent/US8260624B2/en
Priority to US12/587,127 priority patent/US8229756B2/en
Priority to US12/590,027 priority patent/US8275628B2/en
Priority to US12/590,039 priority patent/US8392205B2/en
Priority to US12/590,600 priority patent/US8234123B2/en
Priority to US12/590,841 priority patent/US8249887B2/en
Priority to US12/592,075 priority patent/US8255400B2/en
Priority to US12/592,161 priority patent/US8249888B2/en
Priority to US12/592,544 priority patent/US8260807B2/en
Priority to US12/592,548 priority patent/US8271524B2/en
Priority to US12/592,944 priority patent/US8244552B2/en
Priority to US12/592,946 priority patent/US8244553B2/en
Priority to US12/653,117 priority patent/US8255236B2/en
Priority to US12/653,180 priority patent/US8255237B2/en
Priority to US12/653,387 priority patent/US8311846B2/en
Priority to US12/653,386 priority patent/US8260625B2/en
Priority to US12/653,972 priority patent/US8260626B2/en
Priority to US12/655,075 priority patent/US8265944B2/en
Priority to US12/655,250 priority patent/US8265945B2/en
Priority to US12/655,365 priority patent/US8265946B2/en
Priority to US12/655,582 priority patent/US8321233B2/en
Application filed by Searete LLC filed Critical Searete LLC
Priority to US13/656,288 priority patent/US20130144919A1/en
Assigned to SEARETE LLC reassignment SEARETE LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GARMS, JASON, LEVIEN, ROYCE A., MALAMUD, MARK A., TEGREENE, CLARENCE T., RINALDO, JOHN D., JR., LORD, RICHARD T., LORD, ROBERT W., TOLLE, KRISTIN M., FIRMINGER, SHAWN P., WOOD, LOWELL L., JR, JUNG, EDWARD K.Y., LEUTHARDT, ERIC C., HYDE, RODERICK A., KARKANIAS, CHRIS D.
Publication of US20130144919A1 publication Critical patent/US20130144919A1/en
Assigned to THE INVENTION SCIENCE FUND I, LLC reassignment THE INVENTION SCIENCE FUND I, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SEARETE LLC
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • G06F17/30091
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/13File access structures, e.g. distributed indices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

A computationally implemented method includes, but is not limited to: providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • The 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
  • For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation of U.S. patent application Ser. No. 12/655,582, entitled TEMPLATE DEVELOPMENT BASED ON REPORTED ASPECTS OF A PLURALITY OF SOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 30 Dec. 2009, 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. This application claims priority to the following applications, which are currently co-pending or applications of which a currently co-pending application is entitled to the benefit of the filing date.
  • RELATED APPLICATIONS
      • U.S. patent application Ser. No. 12/584,489, entitled PERSONALIZED PLAN DEVELOPMENT, U.S. Pat. No. 8,265,943, filed 3 Sep. 2009.
      • U.S. patent application Ser. No. 12/584,653, entitled PERSONALIZED PLAN DEVELOPMENT, U.S. Pat. No. 8,280,746, filed 8 Sep. 2009.
      • U.S. patent application Ser. No. 12/587,018, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON OUTCOME IDENTIFICATION, U.S. Pat. No. 8,260,624, filed 29 Sep. 2009.
      • U.S. patent application Ser. No. 12/587,127, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON OUTCOME IDENTIFICATION, U.S. Pat. No. 8,229,756, filed 30 Sep. 2009.
      • U.S. patent application Ser. No. 12/590,027, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORE SOURCE USERS, U.S. Pat. No. 8,275,628, filed 29 Oct. 2009.
      • U.S. patent application Ser. No. 12/590,039, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORE SOURCE USERS, filed 30 Oct. 2009.
      • U.S. patent application Ser. No. 12/590,600, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, U.S. Pat. No. 8,234,123, filed 10 Nov. 2009.
      • U.S. patent application Ser. No. 12/590,841, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, U.S. Pat. No. 8,249,887, filed 12 Nov. 2009.
      • U.S. patent application Ser. No. 12/592,075, entitled DEVELOPMENT OF PERSONALIZED PLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, U.S. Pat. No. 8,255,400, filed 17 Nov. 2009.
      • U.S. patent application Ser. No. 12/592,161, entitled DEVELOPMENT OF PERSONALIZED PLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, U.S. Pat. No. 8,249,888, filed 18 Nov. 2009.
      • U.S. patent application Ser. No. 12/592,544, entitled IDENTIFICATION AND PROVISION OF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OF TARGET OUTCOMES, U.S. Pat. No. 8,260,807, filed 24 Nov. 2009.
      • U.S. patent application Ser. No. 12/592,548, entitled IDENTIFICATION AND PROVISION OF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OF TARGET OUTCOMES, U.S. Pat. No. 8,271,524, filed 25 Nov. 2009.
      • U.S. patent application Ser. No. 12/592,944, entitled TEMPLATE DEVELOPMENT BASED ON SENSOR ORIGINATED REPORTED ASPECTS, U.S. Pat. No. 8,244,552, filed 3 Dec. 2009.
      • U.S. patent application Ser. No. 12/592,946, entitled TEMPLATE DEVELOPMENT BASED ON SENSOR ORIGINATED REPORTED ASPECTS, U.S. Pat. No. 8,244,553, filed 4 Dec. 2009.
      • U.S. patent application Ser. No. 12/653,117, entitled SOURCE USER BASED PROVISION OF ONE OR MORE TEMPLATES, U.S. Pat. No. 8,255,236, filed 7 Dec. 2009.
      • U.S. patent application Ser. No. 12/653,180, entitled SOURCE USER BASED PROVISION OF ONE OR MORE TEMPLATES, U.S. Pat. No. 8,255,237, filed 8 Dec. 2009.
      • U.S. patent application Ser. No. 12/653,387, entitled TARGET OUTCOME BASED PROVISION OF ONE OR MORE TEMPLATES, filed 10 Dec. 2009.
      • U.S. patent application Ser. No. 12/653,386, entitled TARGET OUTCOME BASED PROVISION OF ONE OR MORE TEMPLATES, U.S. Pat. No. 8,260,625, filed 11 Dec. 2009.
      • U.S. patent application Ser. No. 12/653,972, entitled DETECTING DEVIATION FROM COMPLIANT EXECUTION OF A TEMPLATE, U.S. Pat. No. 8,260,626, filed 17 Dec. 2009.
      • U.S. patent application Ser. No. 12/655,075, entitled DETECTING DEVIATION FROM COMPLIANT EXECUTION OF A TEMPLATE, U.S. Pat. No. 8,265,944, filed 21 Dec. 2009.
      • U.S. patent application Ser. No. 12/655,250, entitled TEMPLATE MODIFICATION BASED ON DEVIATION FROM COMPLIANT EXECUTION OF THE TEMPLATE, U.S. Pat. No. 8,265,945, filed 23 Dec. 2009.
      • U.S. patent application Ser. No. 12/655,365, entitled TEMPLATE MODIFICATION BASED ON DEVIATION FROM COMPLIANT EXECUTION OF THE TEMPLATE, U.S. Pat. No. 8,265,946, filed 28 Dec. 2009.
  • The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation, continuation-in-part, or divisional of a parent application. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTO Official Gazette Mar. 18, 2003. The 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 designation(s) are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).
  • If 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.
  • All 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.
  • SUMMARY
  • A computationally implemented method includes, but is not limited to providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and means for developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and circuitry for developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and one or more instructions for developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for developing a template based, at least in part, on a plurality of relevant reported aspects associated with a plurality of source users, the method includes providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and developing, using a processor, a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to receiving a request for a personalized plan designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least a source user; acquiring source user data indicating a plurality of reported aspects associated with at least the source user in response to receiving the request; and developing the personalized plan by at least determining which of the plurality of reported aspects associated with the source user are relevant to the achievement of the one or more target outcomes. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least a source user; means for acquiring source user data indicating a plurality of reported aspects associated with at least the source user in response to receiving the request; and means for developing the personalized plan by at least determining which of the plurality of reported aspects associated with the source user are relevant to the achievement of the one or more target outcomes. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least a source user; circuitry for acquiring source user data indicating a plurality of reported aspects associated with at least the source user in response to receiving the request and circuitry for developing the personalized plan by at least determining which of the plurality of reported aspects associated with the source user are relevant to the achievement of the one or more target outcomes. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least a source user; one or more instructions for acquiring source user data indicating a plurality of reported aspects associated with at least the source user in response to receiving the request; and one or more instructions for developing the personalized plan by at least determining which of the plurality of reported aspects associated with the source user are relevant to the achievement of the one or more target outcomes. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to receiving a request for one or more personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the request identifying the one or more target outcomes; seeking one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request; and developing the one or more personalized plans based, at least in part, on the seeking. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for receiving a request for one or more personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the request identifying the one or more target outcomes; means for seeking one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request; and means for developing the one or more personalized plans based, at least in part, on the seeking. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for receiving a request for one or more personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the request identifying the one or more target outcomes; circuitry for seeking one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request and circuitry for developing the one or more personalized plans based, at least in part, on the seeking. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for receiving a request for one or more personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the request identifying the one or more target outcomes; one or more instructions for seeking one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request; and one or more instructions for developing the one or more personalized plans based, at least in part, on the seeking. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for developing one or more personalized plans that includes receiving a request for one or more personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the request identifying the one or more target outcomes; seeking, using a microprocessor, one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request; and developing the one or more personalized plans based, at least in part, on the seeking.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to providing one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the providing of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' association with the one or more source users; and developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the providing. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for providing one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the providing of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' association with the one or more source users; and means for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the providing. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for providing one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the providing of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' association with the one or more source users; and circuitry for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the providing. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for providing one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the providing of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' association with the one or more source users; and one or more instructions for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the providing. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for developing one or more personalized plans that includes providing, using a microprocessor, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the providing of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' association with the one or more source users; and developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the providing.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to identifying one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identifying of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes; and developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the identifying. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for identifying one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identifying of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes; and means for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the identifying. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for identifying one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identifying of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes; and circuitry for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the identifying. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for identifying one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identifying of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes; and one or more instructions for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the identifying. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for developing one or more personalized plans that includes identifying, using a processor, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identifying of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes; and developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the identifying.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to acquiring one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to the achievement of the one or more target outcomes; and developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the acquiring. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for acquiring one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to the achievement of the one or more target outcomes; and means for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the acquiring. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for acquiring one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to the achievement of the one or more target outcomes; and circuitry for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the acquiring. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for acquiring one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to the achievement of the one or more target outcomes; and one or more instructions for developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the acquiring. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for developing one or more personalized plans that includes acquiring, using a processor, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects being based, at least in part, on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes; and developing one or more personalized plans designed to facilitate an end user to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the development of the one or more personalized plans being based, at least in part, on the acquiring.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to identifying, in response to reception of one or more solicitations, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes; and providing the one or more relevant reported aspects. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for identifying, in response to reception of one or more solicitations, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes; and means for providing the one or more relevant reported aspects. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for identifying, in response to reception of one or more solicitations, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes; and circuitry for providing the one or more relevant reported aspects. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for identifying, in response to reception of one or more solicitations, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes; and one or more instructions for providing the one or more relevant reported aspects. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for providing relevant reported aspects that are relevant to achieving one or more target outcomes, the method includes identifying, using a processor one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects in response to reception of one or more solicitations and being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes; and providing the one or more relevant reported aspects.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to providing one or more reported aspects associated with one or more source users that were originally reported by one or more sensors; and developing one or more templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates are emulated, the development of the one or more templates being based at least on a portion of the one or more reported aspects. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for providing one or more reported aspects associated with one or more source users that were originally reported by one or more sensors; and means for developing one or more templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates are emulated, the development of the one or more templates being based at least on a portion of the one or more reported aspects. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for providing one or more reported aspects associated with one or more source users that were originally reported by one or more sensors; and circuitry for developing one or more templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates are emulated, the development of the one or more templates being based at least on a portion of the one or more reported aspects. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for providing one or more reported aspects associated with one or more source users that were originally reported by one or more sensors; and one or more instructions for developing one or more templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates are emulated, the development of the one or more templates being based at least on a portion of the one or more reported aspects. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for providing relevant reported aspects that are relevant to achieving one or more target outcomes, the method includes providing, using a processor, one or more reported aspects associated with one or more source users that were originally reported by one or more sensors; and developing one or more templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates are emulated, the development of the one or more templates being based at least on a portion of the one or more reported aspects.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to receiving one or more requests for one or more particular templates that are associated with one or more source users, the one or more particular templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and providing from a plurality of templates the one or more particular templates, the providing being based at least on the association of the one or more particular templates with the one or more source users, the one or more particular templates developed based on one or more reported aspects associated with the one or more source users. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for receiving one or more requests for one or more particular templates that are associated with one or more source users, the one or more particular templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and means for providing from a plurality of templates the one or more particular templates, the providing being based at least on the association of the one or more particular templates with the one or more source users, the one or more particular templates developed based on one or more reported aspects associated with the one or more source users. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for receiving one or more requests for one or more particular templates that are associated with one or more source users, the one or more particular templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and circuitry for providing from a plurality of templates the one or more particular templates, the providing being based at least on the association of the one or more particular templates with the one or more source users, the one or more particular templates developed based on one or more reported aspects associated with the one or more source users. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for receiving one or more requests for one or more particular templates that are associated with one or more source users, the one or more particular templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and one or more instructions for providing from a plurality of templates the one or more particular templates, the providing being based at least on the association of the one or more particular templates with the one or more source users, the one or more particular templates developed based on one or more reported aspects associated with the one or more source users. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for providing one or more templates that are associated with one or more source users from a plurality of templates, the method includes receiving one or more requests for one or more particular templates that are associated with one or more source users, the one or more particular templates designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and providing from a plurality of templates, using a processor, the one or more particular templates, the providing being based at least on the association of the one or more particular templates with the one or more source users, the one or more particular templates developed based on one or more reported aspects associated with the one or more source users.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to receiving one or more requests indicating at least one or more target outcomes of one or more particular templates, the one or more particular templates designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and providing from a plurality of templates the one or more particular templates, the providing being based at least on the one or more particular templates' association with the one or more target outcomes, the one or more particular templates developed based on one or more reported aspects of one or more source users. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for receiving one or more requests indicating at least one or more target outcomes of one or more particular templates, the one or more particular templates designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and means for providing from a plurality of templates the one or more particular templates, the providing being based at least on the one or more particular templates' association with the one or more target outcomes, the one or more particular templates developed based on one or more reported aspects of one or more source users. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for receiving one or more requests indicating at least one or more target outcomes of one or more particular templates, the one or more particular templates designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and circuitry for providing from a plurality of templates the one or more particular templates, the providing being based at least on the one or more particular templates' association with the one or more target outcomes, the one or more particular templates developed based on one or more reported aspects of one or more source users. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for receiving one or more requests indicating at least one or more target outcomes of one or more particular templates, the one or more particular templates designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and one or more instructions for providing from a plurality of templates the one or more particular templates, the providing being based at least on the one or more particular templates' association with the one or more target outcomes, the one or more particular templates developed based on one or more reported aspects of one or more source users. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for providing one or more templates that are associated with one or more source users from a plurality of templates, the method includes receiving one or more requests indicating at least one or more target outcomes of one or more particular templates, the one or more particular templates designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more particular templates are emulated; and providing from a plurality of templates, using a processor, the one or more particular templates, the providing being based at least on the one or more particular templates' association with the one or more target outcomes, the one or more particular templates developed based on one or more reported aspects of one or more source users.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to detecting deviation from a compliant execution of a template by an end user, the template designed to facilitate the end user to achieve one or more target outcomes when one or more emulatable aspects included in the template are emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that are relevant to achieving the one or more target outcomes; and executing one or more actions in response to the detecting of the deviation. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for detecting deviation from a compliant execution of a template by an end user, the template designed to facilitate the end user to achieve one or more target outcomes when one or more emulatable aspects included in the template are emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that are relevant to achieving the one or more target outcomes; and means for executing one or more actions in response to the detecting of the deviation. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for detecting deviation from a compliant execution of a template by an end user, the template designed to facilitate the end user to achieve one or more target outcomes when one or more emulatable aspects included in the template are emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that are relevant to achieving the one or more target outcomes; and circuitry for executing one or more actions in response to the detecting of the deviation. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for detecting deviation from a compliant execution of a template by an end user, the template designed to facilitate the end user to achieve one or more target outcomes when one or more emulatable aspects included in the template are emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that are relevant to achieving the one or more target outcomes; and one or more instructions for executing one or more actions in response to the detecting of the deviation. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for executing one or more actions in response to detecting deviation from a compliant execution of a template, the method includes detecting, using a processor, deviation from a compliant execution of a template by an end user, the template designed to facilitate the end user to achieve one or more target outcomes when one or more emulatable aspects included in the template are compliantly emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that are relevant to achieving the one or more target outcomes; and executing one or more actions in response to the detecting of the deviation.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • A computationally implemented method includes, but is not limited to determining whether a plurality of end users deviated from compliantly executing a template designed to facilitate the plurality of end users in achieving one or more target outcomes when one or more emulatable aspects included in the template are emulated by the plurality of end users, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that were deemed to have been relevant to achieving the one or more target outcomes; and modifying the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
  • A computationally implemented system includes, but is not limited to: means for determining whether a plurality of end users deviated from compliantly executing a template designed to facilitate the plurality of end users in achieving one or more target outcomes when one or more emulatable aspects included in the template are emulated by the plurality of end users, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that were deemed to have been relevant to achieving the one or more target outcomes; and means for modifying the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computationally implemented system includes, but is not limited to: circuitry for determining whether a plurality of end users deviated from compliantly executing a template designed to facilitate the plurality of end users in achieving one or more target outcomes when one or more emulatable aspects included in the template are emulated by the plurality of end users, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that were deemed to have been relevant to achieving the one or more target outcomes; and circuitry for modifying the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A computer program product including a signal-bearing medium bearing one or more instructions for determining whether a plurality of end users deviated from compliantly executing a template designed to facilitate the plurality of end users in achieving one or more target outcomes when one or more emulatable aspects included in the template are emulated by the plurality of end users, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that were deemed to have been relevant to achieving the one or more target outcomes; and one or more instructions for modifying the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
  • A method for modifying a template based, at least in part, on determining whether a plurality of end users deviated from compliantly executing the template, the method includes determining whether a plurality of end users deviated from compliantly executing a template designed to facilitate the plurality of end users in achieving one or more target outcomes when one or more emulatable aspects included in the template are emulated by the plurality of end users, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that were deemed to have been relevant to achieving the one or more target outcomes; and modifying, using a processor, the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template.
  • The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
  • BRIEF DESCRIPTION OF THE FIGURES
  • FIGS. 1 a and 1 b show a high-level block diagram of a Computing Device 10 operating in a network environment.
  • FIG. 2 a shows another perspective of the Relevant Reported Aspect Providing module 102 of the Computing Device 10 of FIG. 1 b.
  • FIG. 2 b shows another perspective of the Template Developing Module 104 of the Computing Device 10 of FIG. 1 b.
  • FIG. 3 is a high-level logic flowchart of a process.
  • FIG. 4 a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 302 of FIG. 3.
  • FIG. 4 b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 302 of FIG. 3.
  • FIG. 4 c is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 302 of FIG. 3.
  • FIG. 4 d is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 302 of FIG. 3.
  • FIG. 4 e is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 302 of FIG. 3.
  • FIG. 5 a is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 304 of FIG. 3.
  • FIG. 5 b is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 304 of FIG. 3.
  • FIG. 5 c is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 304 of FIG. 3.
  • FIG. 5 d is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 304 of FIG. 3.
  • FIG. 5 e is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 304 of FIG. 3.
  • FIG. 6 is a high-level logic flowchart of another process.
  • FIG. 7 is a high-level logic flowchart of a process depicting alternate implementations of the template presenting operation 606 of FIG. 6.
  • FIG. 8 is another high-level block diagram showing one implementation of the computing device 10 of FIG. 1 b.
  • FIGS. 1-1 a and 1-1 b show a high-level block diagram of a server 1-10 operating in a network environment.
  • FIGS. 1-1 c and 1-1 d show a high-level block diagram of a local source user device 1-20′ operating in a network environment.
  • FIGS. 1-1 e and 1-1 f show a high-level block diagram of a local end user device 1-30″ operating in a network environment.
  • FIG. 1-2 shows another perspective of the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, of the local source user device 1-20′ of FIG. 1-1 d, and of the local end user device 1-30″ of FIG. 1-1 f.
  • FIG. 1-3 is a high-level logic flowchart of a process.
  • FIG. 1-4 a is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 1-302 of FIG. 1-3.
  • FIG. 1-4 b is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 1-302 of FIG. 1-3.
  • FIG. 1-4 c is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 1-302 of FIG. 1-3.
  • FIG. 1-4 d is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 1-302 of FIG. 1-3.
  • FIG. 1-4 e is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 1-302 of FIG. 1-3.
  • FIG. 1-5 a is a high-level logic flowchart of a process depicting alternate implementations of the acquisition operation 1-304 of FIG. 1-3.
  • FIG. 1-5 b is a high-level logic flowchart of a process depicting alternate implementations of the acquisition operation 1-304 of FIG. 1-3.
  • FIG. 1-5 c is a high-level logic flowchart of a process depicting alternate implementations of the acquisition operation 1-304 of FIG. 1-3.
  • FIG. 1-5 d is a high-level logic flowchart of a process depicting alternate implementations of the acquisition operation 1-304 of FIG. 1-3.
  • FIG. 1-5 e is a high-level logic flowchart of a process depicting alternate implementations of the acquisition operation 1-304 of FIG. 1-3.
  • FIG. 1-5 f is a high-level logic flowchart of a process depicting alternate implementations of the acquisition operation 1-304 of FIG. 1-3.
  • FIG. 1-6 a is a high-level logic flowchart of a process depicting alternate implementations of the development operation 1-306 of FIG. 1-3.
  • FIG. 1-6 b is a high-level logic flowchart of a process depicting alternate implementations of the development operation 1-306 of FIG. 1-3.
  • FIG. 1-6 c is a high-level logic flowchart of a process depicting alternate implementations of the development operation 1-306 of FIG. 1-3.
  • FIG. 1-6 d is a high-level logic flowchart of a process depicting alternate implementations of the development operation 1-306 of FIG. 1-3.
  • FIG. 1-7 is a high-level logic flowchart of another process.
  • FIG. 1-8 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 1-708 of FIG. 1-7.
  • FIGS. 2-1 a and 2-1 b show a high-level block diagram of a server 2-10 operating in a network environment.
  • FIGS. 2-2 a and 2-2 b show a high-level block diagram of a local source user device 2-20′ operating in a network environment.
  • FIGS. 2-3 a and 2-3 b show a high-level block diagram of a local end user device 2-30″ operating in a network environment.
  • FIG. 2-4 a shows another perspective of the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, of the local source user device 2-20′ of FIG. 2-2 b, and of the local end user device 2-30″ of FIG. 2-3 b.
  • FIG. 2-4 b shows another perspective of the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1 b, of the local source user device 2-20′ of FIG. 2-2 b, and of the local end user device 2-30″ of FIG. 2-3 b.
  • FIG. 2-5 is a high-level logic flowchart of a process.
  • FIG. 2-6 a is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 2-502 of FIG. 2-5.
  • FIG. 2-6 b is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 2-502 of FIG. 2-5.
  • FIG. 2-6 c is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 2-502 of FIG. 2-5.
  • FIG. 2-6 d is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 2-502 of FIG. 2-5.
  • FIG. 2-6 e is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 2-502 of FIG. 2-5.
  • FIG. 2-6 f is a high-level logic flowchart of a process depicting alternate implementations of the reception operation 2-502 of FIG. 2-5.
  • FIG. 2-7 a is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 b is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 c is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 d is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 e is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 f is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 g is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 h is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 i is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 j is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 k is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 l is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-7 m is a high-level logic flowchart of a process depicting alternate implementations of the seeking operation 2-504 of FIG. 2-5.
  • FIG. 2-8 a is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 b is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 c is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 d is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 e is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 f is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 g is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 h is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 i is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-8 j is a high-level logic flowchart of a process depicting alternate implementations of the development operation 2-506 of FIG. 2-5.
  • FIG. 2-9 is a high-level logic flowchart of another process.
  • FIG. 2-10 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 2-908 of FIG. 2-9.
  • FIG. 2-11 is a high-level block diagram of a computing device.
  • FIGS. 3-1 a and 3-1 b show a high-level block diagram of a server 3-10 operating in a network environment.
  • FIGS. 3-2 a and 3-2 b show a high-level block diagram of a local source user device 3-20′ operating in a network environment.
  • FIGS. 3-3 a and 3-3 b show a high-level block diagram of a local end user device 3-30″ operating in a network environment.
  • FIG. 3-4 a shows another perspective of the relevant reported aspect provision module 3-102* of the server 3-10 of FIG. 3-1 b, of the local source user device 3-20′ of FIG. 3-2 b, and of the local end user device 3-30″ of FIG. 3-3 b.
  • FIG. 3-4 b shows another perspective of the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1 b, of the local source user device 3-20′ of FIG. 3-2 b, and of the local end user device 3-30″ of FIG. 3-3 b.
  • FIG. 3-4 c shows one perspective of one of the sensing devices 3-40* of the first exemplary environment of FIGS. 3-1 a and 3-1 b, of the second exemplary environment of FIGS. 3-2 a and 3-2 b, and of the third exemplary environment of FIGS. 3-3 a and 3-3 b.
  • FIG. 3-5 is a high-level logic flowchart of a process.
  • FIG. 3-6 a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 c is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 d is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 e is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 f is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 g is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 h is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 i is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 j is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 k is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 l is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 m is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 n is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 o is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 p is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 q is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 r is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-6 s is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 3-502 of FIG. 3-5.
  • FIG. 3-7 a is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 b is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 c is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 d is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 e is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 f is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 g is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 h is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-7 i is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan development operation 3-504 of FIG. 3-5.
  • FIG. 3-8 is a high-level logic flowchart of another process.
  • FIG. 3-9 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 3-806 of FIG. 3-8.
  • FIG. 3-10 is a high-level block diagram of a computing device.
  • FIGS. 4-1 a and 4-1 b show a high-level block diagram of a computing device 4-10 operating in a network environment.
  • FIG. 4-2 a shows another perspective of the relevant reported aspect identification module 4-102 of the computing device 4-10 of FIG. 4-1 b.
  • FIG. 4-2 b shows another perspective of the personalized plan development module 4-104 of the computing device 4-10 of FIG. 4-1 b.
  • FIG. 4-2 c shows one perspective of one of the sensing devices 4-40 of the environment of FIGS. 4-1 a and 4-1 b.
  • FIG. 4-3 is a high-level logic flowchart of a process.
  • FIG. 4-4 a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 c is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 d is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 e is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 f is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 g is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-4 h is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 4-302 of FIG. 4-3.
  • FIG. 4-5 a is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 4-304 of FIG. 4-3.
  • FIG. 4-5 b is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 4-304 of FIG. 4-3.
  • FIG. 4-5 c is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 4-304 of FIG. 4-3.
  • FIG. 4-5 d is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 4-304 of FIG. 4-3.
  • FIG. 4-6 is a high-level logic flowchart of another process.
  • FIG. 4-7 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 4-606 of FIG. 4-6.
  • FIG. 4-8 is another high-level block diagram showing another perspective of the computing device 4-10 of FIG. 4-1 b.
  • FIGS. 5-1 a and 5-1 b show a high-level block diagram of a computing device 5-10 operating in a network environment.
  • FIG. 5-2 a shows another perspective of the relevant reported aspect acquisition module 5-102 of the computing device 5-10 of FIG. 5-1 b.
  • FIG. 5-2 b shows another perspective of the personalized plan development module 5-104 of the computing device 5-10 of FIG. 5-1 b.
  • FIG. 5-2 c shows one perspective of one of the sensing devices 5-40 of the environment of FIGS. 5-1 a and 5-1 b.
  • FIG. 5-3 is a high-level logic flowchart of a process.
  • FIG. 5-4 a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 c is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 d is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 e is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 f is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 g is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-4 h is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect acquiring operation 5-302 of FIG. 5-3.
  • FIG. 5-5 a is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 5-304 of FIG. 5-3.
  • FIG. 5-5 b is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 5-304 of FIG. 5-3.
  • FIG. 5-5 c is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 5-304 of FIG. 5-3.
  • FIG. 5-5 d is a high-level logic flowchart of a process depicting alternate implementations of the personalized plan developing operation 5-304 of FIG. 5-3.
  • FIG. 5-6 is a high-level logic flowchart of another process.
  • FIG. 5-7 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 5-606 of FIG. 5-6.
  • FIG. 5-8 is another high-level block diagram showing another perspective of the computing device 5-10 of FIG. 5-1 b.
  • FIGS. 6-1 a and 6-1 b show a high-level block diagram of a computing device 6-10 operating in a network environment.
  • FIG. 6-2 a shows another perspective of the relevant reported aspect identification module 6-102 of the computing device 6-10 of FIG. 6-1 b.
  • FIG. 6-2 b shows another perspective of the relevant reported aspect providing module 6-104 of the computing device 6-10 of FIG. 6-1 b.
  • FIG. 6-2 c shows one perspective of one of the sensing devices 6-40 of the environment of FIGS. 6-1 a and 6-1 b.
  • FIG. 6-3 is a high-level logic flowchart of a process.
  • FIG. 6-4 a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 c is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 d is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 e is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 f is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 g is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-4 h is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 6-302 of FIG. 6-3.
  • FIG. 6-5 a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 6-304 of FIG. 6-3.
  • FIG. 6-5 b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 6-304 of FIG. 6-3.
  • FIG. 6-6 is another high-level block diagram showing one implementation of the computing device 6-10 of FIG. 6-1 b.
  • FIGS. 7-1 a and 7-1 b show a high-level block diagram of a computing device 7-10 operating in a network environment.
  • FIG. 7-2 a shows another perspective of the sensor originated reported aspect providing module 7-102 of the computing device 7-10 of FIG. 7-1 b.
  • FIG. 7-2 b shows another perspective of the template development module 7-104 of the computing device 7-10 of FIG. 7-1 b.
  • FIG. 7-2 c shows one perspective of one of the sensor integrated devices 7-40 of the exemplary environment 7-100 of FIGS. 7-1 a and 7-1 b.
  • FIG. 7-2 d shows one perspective of the one or more sensors 7-240*(e.g., one or more sensors 7-240 a, one or more sensors 7-240 b, or one or more sensors 7-240 c) of the exemplary environment 7-100 of FIGS. 7-1 a and 7-1 b.
  • FIG. 7-3 is a high-level logic flowchart of a process.
  • FIG. 7-4 a is a high-level logic flowchart of a process depicting alternate implementations of the sensor originated reported aspect providing operation 7-302 of FIG. 7-3.
  • FIG. 7-4 b is a high-level logic flowchart of a process depicting alternate implementations of the sensor originated reported aspect providing operation 7-302 of FIG. 7-3.
  • FIG. 7-4 c is a high-level logic flowchart of a process depicting alternate implementations of the sensor originated reported aspect providing operation 7-302 of FIG. 7-3.
  • FIG. 7-4 d is a high-level logic flowchart of a process depicting alternate implementations of the sensor originated reported aspect providing operation 7-302 of FIG. 7-3.
  • FIG. 7-4 e is a high-level logic flowchart of a process depicting alternate implementations of the sensor originated reported aspect providing operation 7-302 of FIG. 7-3.
  • FIG. 7-4 f is a high-level logic flowchart of a process depicting alternate implementations of the sensor originated reported aspect providing operation 7-302 of FIG. 7-3.
  • FIG. 7-5 a is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 7-304 of FIG. 7-3.
  • FIG. 7-5 b is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 7-304 of FIG. 7-3.
  • FIG. 7-5 c is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 7-304 of FIG. 7-3.
  • FIG. 7-5 d is a high-level logic flowchart of a process depicting alternate implementations of the template developing operation 7-304 of FIG. 7-3.
  • FIG. 7-6 is a high-level logic flowchart of another process.
  • FIG. 7-7 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 7-606 of FIG. 7-6.
  • FIG. 7-8 is another high-level block diagram showing one implementation of the computing device 7-10 of FIG. 7-1 b.
  • FIGS. 8-1 a and 8-1 b show a high-level block diagram of a computing device 8-10 operating in a network environment.
  • FIG. 8-2 a shows another perspective of the particular template providing module 8-104 of the computing device 8-10 of FIG. 8-1 b.
  • FIG. 8-2 b shows one perspective of a particular template.
  • FIG. 8-3 is a high-level logic flowchart of a process.
  • FIG. 8-4 a is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 8-302 of FIG. 8-3.
  • FIG. 8-4 b is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 8-302 of FIG. 8-3.
  • FIG. 8-4 c is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 8-302 of FIG. 8-3.
  • FIG. 8-5 a is a high-level logic flowchart of a process depicting alternate implementations of the template providing operation 8-304 of FIG. 8-3.
  • FIG. 8-5 b is a high-level logic flowchart of a process depicting alternate implementations of the template providing operation 8-304 of FIG. 8-3.
  • FIG. 8-5 c is a high-level logic flowchart of a process depicting alternate implementations of the template providing operation 8-304 of FIG. 8-3.
  • FIG. 8-5 d is a high-level logic flowchart of a process depicting alternate implementations of the template providing operation 8-304 of FIG. 8-3.
  • FIG. 8-6 is a high-level logic flowchart of another process.
  • FIG. 8-7 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 8-606 of FIG. 8-6.
  • FIG. 8-8 is another high-level block diagram showing one implementation of the computing device 8-10 of FIG. 8-1 b.
  • FIGS. 9-1 a and 9-1 b show a high-level block diagram of a computing device 9-10 operating in a network environment.
  • FIG. 9-2 a shows another perspective of the particular template providing module 9-104 of the computing device 9-10 of FIG. 9-1 b.
  • FIG. 9-2 b shows one perspective of a particular template.
  • FIG. 9-3 is a high-level logic flowchart of a process.
  • FIG. 9-4 a is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 9-302 of FIG. 9-3.
  • FIG. 9-4 b is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 9-302 of FIG. 9-3.
  • FIG. 9-4 c is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 9-302 of FIG. 9-3.
  • FIG. 9-5 a is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 9-304 of FIG. 9-3.
  • FIG. 9-5 b is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 9-304 of FIG. 9-3.
  • FIG. 9-5 c is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 9-304 of FIG. 9-3.
  • FIG. 9-5 d is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 9-304 of FIG. 9-3.
  • FIG. 9-5 e is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 9-304 of FIG. 9-3.
  • FIG. 9-5 f is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 9-304 of FIG. 9-3.
  • FIG. 9-6 is a high-level logic flowchart of another process.
  • FIG. 9-7 is a high-level logic flowchart of a process depicting alternate implementations of the presentation operation 9-606 of FIG. 6.
  • FIG. 9-8 is another high-level block diagram showing one implementation of the computing device 9-10 of FIG. 9-1 b.
  • FIGS. 10-1 a and 10-1 b show a high-level block diagram of a Computing Device 10-10 operating in a network environment.
  • FIG. 10-2 a shows another perspective of the Deviation Detecting Module 10-102 of the Computing Device 10-10 of FIG. 10-1 b.
  • FIG. 10-2 b shows another perspective of the Action Executing Module 10-104 of the Computing Device 10-10 of FIG. 10-1 b.
  • FIG. 10-3 is a high-level logic flowchart of a process.
  • FIG. 10-4 a is a high-level logic flowchart of a process depicting alternate implementations of the deviation detecting operation 10-302 of FIG. 10-3.
  • FIG. 10-4 b is a high-level logic flowchart of a process depicting alternate implementations of the deviation detecting operation 10-302 of FIG. 10-3.
  • FIG. 10-4 c is a high-level logic flowchart of a process depicting alternate implementations of the deviation detecting operation 10-302 of FIG. 10-3.
  • FIG. 10-4 d is a high-level logic flowchart of a process depicting alternate implementations of the deviation detecting operation 10-302 of FIG. 10-3
  • FIG. 10-5 a is a high-level logic flowchart of a process depicting alternate implementations of the particular action executing operation 10-304 of FIG. 10-3.
  • FIG. 10-5 b is a high-level logic flowchart of a process depicting alternate implementations of the particular action executing operation 10-304 of FIG. 10-3.
  • FIG. 10-5 c is a high-level logic flowchart of a process depicting alternate implementations of the particular action executing operation 10-304 of FIG. 10-3.
  • FIG. 10-5 d is a high-level logic flowchart of a process depicting alternate implementations of the particular action executing operation 10-304 of FIG. 10-3.
  • FIG. 10-6 is another high-level block diagram showing one implementation of the computing device 10-10 of FIG. 10-1 b.
  • FIGS. 11-1 a and 11-1 b show a high-level block diagram of a Computing Device 11-10 operating in a network environment.
  • FIG. 11-2 a shows another perspective of the Deviation Determining Module 11-102 of the Computing Device 11-10 of FIG. 11-1 b.
  • FIG. 11-2 b shows another perspective of the Template Modifying Module 11-104 of the Computing Device 11-10 of FIG. 11-1 b.
  • FIG. 11-3 is a high-level logic flowchart of a process.
  • FIG. 11-4 a is a high-level logic flowchart of a process depicting alternate implementations of the deviation determining operation 11-302 of FIG. 11-3.
  • FIG. 11-4 b is a high-level logic flowchart of a process depicting alternate implementations of the deviation determining operation 11-302 of FIG. 11-3.
  • FIG. 11-4 c is a high-level logic flowchart of a process depicting alternate implementations of the deviation determining operation 11-302 of FIG. 11-3.
  • FIG. 11-5 a is a high-level logic flowchart of a process depicting alternate implementations of the particular template modifying operation 11-304 of FIG. 11-3.
  • FIG. 11-5 b is a high-level logic flowchart of a process depicting alternate implementations of the particular template modifying operation 11-304 of FIG. 11-3.
  • FIG. 11-5 c is a high-level logic flowchart of a process depicting alternate implementations of the particular template modifying operation 11-304 of FIG. 11-3.
  • FIG. 11-6 is a high-level logic flowchart of another process.
  • FIG. 11-7 is a high-level logic flowchart of a process depicting alternate implementations of the modified template presenting operation 11-606 of FIG. 11-6.
  • FIG. 11-8 is another high-level block diagram showing one implementation of the computing Device 11-10 of FIG. 11-1 b.
  • DETAILED DESCRIPTION
  • In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
  • A recent trend that has enjoyed explosive popularity in the computing/communication field is to electronically record one's daily activities, behaviors, thoughts, beliefs, traits, physical or mental states, physical characteristics, and other aspects of the person's everyday life onto an open diary. One place where such open diaries are maintained is at social networking sites commonly known as “blogs” where one or more users may report or post every aspect of their daily lives. In brief, an “aspect,” as will be referred to herein, may be in reference to any act, behavior, characteristic, user state or status, belief, external events, and so forth, that may be associated with a user (e.g., a person including, for example, a network user such as a blogger or a social networking user). The process of reporting or posting blog entries is commonly referred to as “blogging.” A newer type of blogging that has quickly become ubiquitous in the social networking fabric is “microblogging,” colloquially referred to as “twittering” or “tweeting.” In microblogging, each of the microblogs that are posted are typically relatively short posts or entries, usually not more than 140 characters long.
  • Other types of social networking sites may also allow users to maintain open diaries and to allow users to easily update their personal information in real time. Such updates are typically made via, for example, social networking status reports otherwise known simply as “status reports.” These social networking sites allow a user to report or post for others to view the latest status or other aspects related to the user.
  • Another recent tread in social networking is to employ one or more sensors to detect and report on a wide variety of user aspects (i.e., aspects of a user). Examples of sensors that may be used for such purposes vary widely, ranging from well-known devices that can detect and report on various physiological parameters such as heart rate or blood pressure, to sensors that can detect certain user behaviors or activities such as toilet usage. Examples of sensors that may be employed in order to monitor or detect user activities include, for example, accelerometers, pedometers, global positioning systems or GPSs, and so forth. Such devices are already, in fact, being integrated into mobile computing/communication devices such as cellular telephones and smart phones, and even into functional devices such as automobiles, exercise machines, household appliances, and so forth.
  • Other types of sensors are also being integrated into mobile computing/communication devices such as those that monitor environmental conditions. Examples of such sensors include, for example, those that can measure atmospheric conditions such as air quality levels. In some cases, sensors may be integrated into functional devices such as automobiles, exercise machines, household appliances, and so forth in order to detect and monitor, for example, their usage as well as, in some cases certain physical or physiological characteristics of the device operators. There are also sensors that are currently available that can even monitor bathroom or toilet usage. All the above described sensors may be configured to provide their collected data through log entries such as entries made through social networking channels (e.g., microblogs, blogs, social networking internet sites, and so forth).
  • Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, and so forth) are now available through such social networking internet sites (or simply “social networking sites”), it is only recently has there been any effort to exploit such potentially useful data. As blogs, microblogs, and various social networking sites become increasingly popular, personal data collected through such means may be spread across multiple network locations.
  • One possible way to exploit such personal data is to use such data to develop templates for achieving a variety of target outcomes (e.g., goals) based on the personal data. In brief, a template may be a plan, a program, or a schedule that is designed to facilitate one or more end users to achieve one or more target outcomes when one or more events (i.e., in the following descriptions, these events will be referred to as “emulatable aspects”) that may be included with the template are emulated. In other words, to use personal data of those (e.g., source users) who have already achieved desirable goals (e.g., target outcomes) to develop templates for others (e.g., end users) to emulate in order to facilitate them in achieving those goals.
  • Each of the one or more emulatable aspects that may be included in a template may be based on and correspond to one or more reported aspects of one or more source users that may have been reported through, for example, social networking channels (e.g., microblogs, social networking sites, and so forth). An “aspect,” in brief may be any behavior, act, mental state, physical state, and so forth that may be associated with a source user. A “reported aspect” is any aspect associated with a source user that may have been reported via, for example, one or more social networking channels or by other means.
  • There are at least two types of templates that could be developed from personal data obtained through, for example, social networking channels. One type of templates that can be developed is generic templates that may be designed to be used generically by any random user in order to achieve one or more target outcomes. The second type of templates, which may be referred to as personalized templates or personalized plans, include those templates that have been personalized for use by a particular end user or users (e.g., a modified version of a generic template that has been modified in order to accommodate the end user's limitations and/or preferences). For purposes of this description, references to a “template” in the following will be in reference to either the first or the second type of templates.
  • In various embodiments, methods, systems, circuitry, and computer program products are provided that are designed to develop a template that is designed to facilitate one or more end users to achieve one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on relevant reported aspects of a plurality of source users, the relevant reported aspects being relevant to achieving the one or more target outcomes. In some embodiments, the relevant reported aspects of the plurality of source users may have been originally reported via log entries such as microblog entries and status reports. More generally, the methods, systems, circuitry, and computer program products to be provided are designed to facilitate the development of a template based on reported aspects of multiple source users. These methods, systems, circuitry, and computer program products being very dynamic and are able to facilitate in the development of almost any type of template to achieve almost any type of target outcomes.
  • As previously described a “template” may be any type of plan, program, or schedule that is designed to facilitate achievement of one or more target outcomes when one or more emulatable aspects included in the template are emulated. Each of the one or more emulatable aspects that may be included in the template may have been developed based on a plurality of relevant reported aspects that are each associated with a different source user. In various embodiments, each of the associated source users may or may not have originally reported the associated relevant reported aspect. That is, a reported aspect (e.g., a relevant or non-relevant reported aspect) of a source user may be reported by any one of a number of different sources including, for example, by the source user (e.g., a microblogger or a social networking user) who is the basis for the reported aspect, by a sensor, or by a third party (e.g., such as another source user).
  • As briefly described earlier, a template may comprise of one or more emulatable aspects that may be based on reported aspects of, for example, one or more source users. Note that the word “emulatable” as will be repeatedly used herein has no significant meaning other than to be used in the following description to merely distinguish those aspects (emulatable aspects) that are indicated in a template from other types of aspects (e.g., reported aspects of source users). In accordance with various embodiments, a template may be developed for achieving almost any type of desired outcome (e.g., target outcome) so long as the appropriate data, such as log entry data of source users who have achieved the desired outcome, are available. Examples of the types of templates that could be developed based on log entry data include, for example, those that are designed to facilitate achievement of medical or health related outcomes, those that are designed to facilitate achievement of athletic or gaming outcomes, those that are designed to facilitate achievement of particular user states such as mental or social states, those that are designed to facilitate achievement of intellectual or academic outcomes, and so forth.
  • In some cases, a template may merely indicate or be a collection of one or more emulatable aspects that end users may emulate in order to achieve one or more target outcomes. In other instances, however, a template may indicate a plurality of emulatable aspects and may define their relationships (e.g., temporal or specific time relationship) with respect to each other. Such a template will be very similar to a schedule or program that indicates when each of the emulatable aspects included in the template should be emulated by end users with respect to the other emulatable aspects included in the template. For example, if a template is designed to facilitate end users to shed a certain amount of body weight, it may include a schedule of when and what activities (e.g., go jogging for 30 minutes on day 1, go swimming for 40 minutes on day 2, and so forth) end users may need to execute in order to achieve the weight loss. Similarly, if the template is designed to, for example, facilitate end users to achieve a high score for the scholastic aptitude test (SAT), the template may be a schedule of when and what activities (e.g., read a particular book on day 1, work on math problems from a particular math book on day 2, and so forth) end users may need to execute in order to achieve the high test score for the SAT.
  • In some instances a template may include one or more emulatable intermediate outcomes that are related to the one or more target outcomes associated with the template. For example, in the above weight loss example, the template may indicate the amount of weight loss end users should have achieved (e.g., in order to achieve the target outcome) after emulating, for example, one week, two weeks, or a month of emulatable aspects indicated by the template.
  • In still other cases, a template may merely be a collection of emulatable aspects that does not define the relationships between the emulatable aspects. For example, a template designed to facilitate an end user to achieve relaxed state of mind may indicate two unlinked emulatable aspects, “get 8 hours of sleep each night,” and “avoid caffeine beverages.” Such a template would not necessarily have any indication of relationship between the two emulatable aspects indicated by the template. It should be noted here that an emulatable aspect that may be included into a template may not only be an act or a behavior, but may be a physiological characteristic, a mental state, or any other aspect that may be emulated. For example, a template that is designed to facilitate reducing backaches may include as one of its aspects, a requirement to keep blood pressure below a certain level, which is a physiological state. An emulatable aspect may even be an external event, such as environmental conditions, that an end user may have some control over.
  • In some embodiments, a template may include or be linked to other information other than emulatable aspects. For example, in some instances, a template may include or be associated with a particular source user and/or with a particular target outcome. Other information may also be included with or be associated with a template as will be further described herein.
  • In order to facilitate understanding of the various concepts to be described herein, an introduction to the meaning of certain words and phrases to be used in the following discussion will now be provided. As described earlier, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, user state or status, external event, or any other facet associated with a source user or a group of source users. A “source user” may be any person, such as a microblogger or a social networking user, who may be the basis for one or more reported aspects. Note that a source user may not necessarily have to be the source for the one or more reported aspects that are related to the source user since reported aspects that are associated with a particular source user may be provided by other source users or by sensors.
  • A “reported aspect” may be any aspect associated with or related to a source user or an end user that has been reported by, for example, the source user, the end user, one or more sensors, or one or more third parties (e.g., other source users or end users). In some instances, such a reported aspect may be reported in the form of a log entry such as a microblog entry, a status report, or a journal entry.
  • A “target outcome” may be any type of desirable goal or result that may be sought by, for example, end users. Examples of target outcomes include, for example, health-related outcomes such as weight loss or improved cardiovascular conditioning, athletic outcomes such as developing a particular athletic skill including being able to pitch a curve ball or achieving a particular golf handicap, physiological outcomes such as reduced blood pressure or blood glucose levels, social outcomes such as obtaining membership into an elite social club or attaining a particular social status, mental state outcomes such as achieving certain level of calmness or happiness, interpersonal or relational outcomes such as having lots of friends or developing skill to make friends, employment outcomes such as being promoted or developing certain work skills, academic or intellectual outcomes, and so forth.
  • An “end user” may be any person, for example, who executes a template in order to achieve one or more target outcomes. As briefly described above, a “source user” may be any person who may be the basis for one or more reported aspects. Note that although in most cases, a source user will be an actual (real) person who may be the basis for one or more reported aspects, in other cases, however, a source user may be a fictional person such as a composite of multiple “actual” source users. For example, reported aspects indicating actual aspects of a plurality of actual source users may be compiled and processed (e.g., normalized or averaged out) in order to create a fictional source user.
  • Turning now to FIGS. 1 a, and 1 b illustrating an example environment in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented by a computing device 10. In particular, the methods, systems, circuitry, and computer program products may be implemented at any network device including at a peer-to-peer network component device. In some embodiments, the computing device 10 may be a server such as one of the one or more network servers 60 illustrated in FIG. 1 a. Alternatively, the computing device 10 may be a source user device such as one of the local source user devices 20* illustrated in FIG. 1 a. In still other embodiments, the computing device 10 may be an end user device such as one of the local end user devices 30* illustrated in FIG. 1 a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 2*” may be in reference to a source user 2 a, a source user 2 b, a source user 2 c, and so forth, or a combination thereof.
  • Note further that for ease of understanding and explanation, the computing device 10 of the exemplary environment 100 of FIGS. 1 a and 1 b in the following discussion will be generally described operating as a server (e.g., server embodiment) rather than as an end user device or as a source user device. Further, although the following discussion related to the exemplary environment 100 of FIGS. 1 a and 1 b assumes that the computing device 10 is a server, the following discussion will, for the most part, be applicable even if the computing device 10 were operating as an end user device (e.g., local end user device 30*) or as a source user device (e.g., local source user device 20*) with certain obvious exceptions (e.g., if the computing device 10 is an end user device or a source user device rather than a server, the computing device 10 may communicate with an end user 4* or a source user 2* directly through a user interface 120 rather than indirectly through one or more communication networks 50 as may be the case when the computing device 10 is a server). In some embodiments, the computing device 10 may operate via a web 1.0 or web 2.0 construct.
  • Referring back to FIGS. 1 a and 1 b, and as previously indicated, the computing device 10 may be a network device such as a server (e.g., a network server 60) that is designed to communicate with other network devices. For example, the computing device 10 may communicate with one or more source users 2*(e.g., source user 2 a, source user 2 b, source user 2 c, source user 2 d, and so forth) through one or more local source user devices 20*(e.g., local source user device 20 a, local source user device 20 b, and so forth), with a plurality of end users 4*(e.g., end user 4 a, end user 4 b, and so forth) through a plurality of local end user devices 30*(e.g., local end user device 30 a, local end user device 30 b, and so forth), with one or more sensor integrated devices 40 (e.g., a transportation vehicle such as a car, an exercise machine, or any other type of functional device that may have an integrated sensor designed to sense, for example, their usage or some aspect of the device operator), with one or more network servers 60, and/or with one or more third parties 6 (e.g., one or more content providers, one or more network service providers, and/or one or more potential future end users 4*) via one or more communication networks 50. In some implementations, the one or more communication networks 50 may include one or more wireless networks and/or one or more wired networks including, for example, at least one of a local area network (LAN), a wireless local area network (WLAN), personal area network (PAN), Worldwide Interoperability for Microwave Access (WiMAX), public switched telephone network (PTSN), general packet radio service (GPRS), cellular networks, and/or other types of wireless and/or wired networks.
  • In some implementations, the computing device 10 may be designed to develop at least one template 16 that is designed to facilitate one or more end users 4* to achieve one or more target outcomes when one or more emulatable aspects included in the template 16 are emulated. The development of the template 16 may be based on a plurality of relevant reported aspects 14 associated with a plurality of source users 2* that are determined to be relevant to achieving the one or more target outcomes. In some cases, the relevant reported aspects 14 may have been originally reported via log entries such as microblog entries and/or status reports. A log entry may be any entry that indicates any aspect of, for example, a source user 2* that may be entered continuously, regularly, semi-regularly, randomly, or on a one-time basis.
  • In some cases, the computing device 10 may have previously received a number of reported aspects 13 that include the relevant reported aspects 14 (e.g., the reported aspects 13 may include both relevant reported aspects 14 and non-relevant reported aspects). After receiving the reported aspects 13 including the relevant reported aspects 14, the reported aspects 13 including the relevant reported aspects 14 may be stored in a memory 116. In various embodiments, the reported aspects 13 as well as the relevant reported aspects 14 may be obtained from a variety of sources including for example, one or more network servers 60, local source user devices 20*, one or more sensor integrated devices 40, and/or one or more third parties 6.
  • Alternatively, the plurality of relevant reported aspects 14 may be selectively acquired by the computing device 10 as a result of the computing device 10 transmitting one or more solicitations 12 that solicits for the relevant reported aspects 14. Such solicitations 12 may be sent to a variety of network devices including, for example, to one or more network servers 60, one or more sensor integrated devices 40, local source user devices 20*, and so forth. Note that in embodiments where the computing device 10 receives a plurality of reported aspects 13 including a plurality of relevant reported aspects 14, the computing device 10 may, after receiving the plurality of reported aspects 13, store the reported aspects 13 (as well as the relevant reported aspects 14 in a memory 116). After acquiring the relevant reported aspects 14, a template 16 may be developed based, at least in part, on the identification of the relevant reported aspects 14 (associated with multiple source users 2*) from a plurality of reported aspects 13. In some cases, the template 16 may be developed by including into the template 16 one or more emulatable aspects that are each developed based on relevant reported aspects 14 of multiple source users 2*.
  • In embodiments where the template 16 includes a plurality of emulatable aspects the development of the template 16 may further include defining in the template 16 the relationships (e.g., temporal or specific time relationships) between the plurality of emulatable aspects that may be included in the template 16. Such relationships may also be based, at least in part, on the plurality of relevant reported aspects 14 of the plurality of source users 2*.
  • After developing the template 16, the template 16 may be presented to at least one end user 4*, to one or more network servers 60, to one or more third parties 6, or to one or more source users 2* via one or more communication networks 50. In embodiments in which the computing device 10 is a local client device such as local end user device 30* or a local source user device 20*, the template 16 may be presented via a user interface 120.
  • In various embodiments, the computing device 10 may be a server (e.g., one of the one or more network servers 60) that may be located at a single network site, located across multiple network sites, or may be a conglomeration of servers located at multiple network sites. In embodiments in which the computing device 10 is a source user device (e.g., local source user device 20*) or an end user device (e.g., local end user device 30*) rather than a network server 60, the computing device 10 may be any one of a wide range of mobile or stationary computing/communication devices including, for example, a laptop, a desktop, a workstation, a cellular telephone, a personal digital assistant (PDA), a Smartphone, a web tablet such as a Netbook, and so forth.
  • Referring back to the exemplary environment 100 of FIGS. 1 a and 1 b, in various embodiments the one or more sensor integrated devices 40 of the exemplary environment 100 of FIGS. 1 a and 1 b may directly communicate with the one or more communication networks 50. Alternatively, the one or more sensor integrated devices 40 may indirectly communicate with the one or more communication networks 50 via the one or more local source user devices 20*(e.g., via, for example, a personal area network or PAN). In various alternative embodiments, a sensor integrated device 40 may be a variety of functional devices that may comprise of one or more sensors 240 and that may be operated or used by a source user 2*. Examples of such devices include, for example, a transportation vehicle (e.g., automobile, a motorcycle, a boat, a plane, and so forth), an exercise machine (e.g., a treadmill), a household appliance (e.g., television set), and so forth.
  • As will be further described herein, the one or more sensors 240, which may also be included in the local source user devices 20*, the one or more local end user devices 30*, and/or the computing device 10, may include any type of sensors 240 that can sense one or more aspects of a source user 2* or, in some cases, an end user 4*. Examples of such sensors 240 include, for example, sensing devices that can sense various physical characteristics of a source user 2* or an end user 4*(e.g., heart rate sensor or blood pressure sensor), sensing devices that can sense activities of a source user 2* or an end user 4*(e.g., a pedometer, an accelerometer, and so forth), sensing devices that can sense environment conditions (e.g., air quality sensors), sensing devices that can sense the location of a source user 2* or an end user 4*(e.g., global positioning system or GPS), sensing devices that can provide physiological data that may be processed in order to determine inferred mental states of source users 2* or end users 4*, and so forth.
  • Each of the one or more local source user devices 20* and the local end user devices 30*(as well as the computing device 10 in embodiments in which the computing device 10 is an end user device or a source user device) may be any one of a variety of computing/communication devices including, for example, a cellular phone, a personal digital assistant (PDA), a laptop, a desktop, or other types of computing/communication devices. In some embodiments, the one or more local source user devices 20* and/or the local end user devices 30*(as well as the computing device 10 in some embodiments) may be a handheld device such as a cellular telephone, a Smartphone, a Mobile Internet Device (MID), an Ultra Mobile Personal Computer (UMPC), a convergent device such as a personal digital assistant (PDA), and so forth. Alternatively, such local client devices (e.g., local source user device 20* and/or local end user devices 30*) may be a laptop, a desktop, a workstation, a web tablet such as a Netbook, or other types of devices that may not be a handheld device in various alternative implementations.
  • The computing device 10 as illustrated in FIG. 1 b may include one or more modules, sub-modules, and various other components. As shown, the computing device 10 may include at least a relevant reported aspect providing module 102 (which may further include one or more sub-modules as illustrated in FIG. 2 a) and a template developing module 104 (which may also include one or more sub-modules as illustrated in FIG. 2 b). The relevant reported aspect providing module 102 may be particularly configured to, among other things, provide a plurality of relevant reported aspects 14 associated with a plurality of source users 2* that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects 14 being based, at least in part, on relevancy of the plurality of relevant reported aspects 14 with respect to the one or more target outcomes. In contrast, the template developing module 104 may be particularly configured to, among other things, develop a template 16 designed to facilitate one or more end users 4* to achieve the one or more target outcomes when one or more emulatable aspects included in the template 16 are emulated, the development of the template 16 being based, at least in part, on the providing of the plurality of relevant reported aspects 14 associated with the plurality of source users 2*.
  • In various implementations, the computing device 10 may further include a template presenting module 106 and a memory 116. The template presenting module 106 may be particularly configured to present the template 16 to, for example, one or more end users 4*, to one or more network servers 60, or to one or more third parties 6. In some implementations, the template presenting module 106 may further include a template transmitting module 150 (e.g., configured to transmit, via the one or more communication networks 50, the template 16) and/or a template indicating module 152 (e.g., configured to indicate, via the user interface 120, the template 16).
  • The memory 116, in various implementations, may store a plurality of reported aspects 13 that are associated with the plurality of source users 2*. Among the plurality of reported aspects 13 stored in memory 116 may be a plurality of relevant reported aspects 14 that may be determined to be relevant to achieving the one or more target outcomes of the template 16 that is developed by the template developing module 104. Other types of data may also be stored in the memory 116 in various alternative implementations. For example, in various implementations, the memory 116 may store one or more of end user relevancy indications 142 (e.g., one or more indications that indicate the types of reported or emulatable aspects that one or more end users 4* have an interest in or believes are relevant to achieving one or more target outcomes), one or more end user limitations 143 (e.g., limitations such as contextual limitations, physical limitations, personal limitations, and so forth, associated with one or more end users 4* that prevent one or more emulatable aspects of the template 16 from being emulated by the one or more end users 4*), and/or one or more source user relevancy indications 144 (e.g., one or more indications provided by one or more source users 2* that indicate at least which types of reported aspects 13 are relevant to achieving one or more target outcomes).
  • In some cases, the memory 116 may also include, for example, one or more third party source relevancy indications 145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 6 that indicate at least which types of reported aspects 13 are relevant to achieving one or more target outcomes), and/or one or more predefined time period indications 146 (e.g., one or more indications that indicate at least one time period such as a time increment or window that may be used to determine whether, for example, a reported aspect 13 is relevant for achieving at least one target outcome only if the reported aspect 13 indicates an aspect that occurred within the at least one time period from an occurrence of the target outcome as successfully achieved by, for example, a source user 2*).
  • In some implementations, the memory 116 may store one or more applications 140 (e.g., a text messaging application, an instant messaging application, an email application, a social networking application, a voice recognition system, a Web 1.0 application, and/or Web 2.0 application to facilitate in communicating via, for example, the World Wide Web). The memory 116 may comprise of one or more of a mass storage device, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a cache memory such as random access memory (RAM), a flash memory, a synchronous random access memory (SRAM), a dynamic random access memory (DRAM), and/or other types of memory devices.
  • The computing device 10 may also include, in various implementations, a network interface 118 (e.g., a network interface card or NIC), a user interface 120 (e.g., a display monitor, a touchscreen, a microphone, a speaker, a mouse, and so forth), and/or one or more sensors 240 that are designed to measure or sense one or more user aspects. Examples of sensors 240 include, for example, devices that are designed to sense user activities such as pedometers and accelerometers, devices that are designed to sense physiological characteristics such as heart rate monitors or blood glucose monitors, devices that are designed to sense environmental conditions such as devices for measuring air quality, devices that are designed to detect user location such as GPS, and so forth. In some cases, the presence or absence of some of these modules and components of computing device 10 may depend on, for example, whether the computing device 10 is a server, an end user device, or a source user device. For example, if the computing device 10 is a server, then the computing device 10 may not include a user interface 120.
  • In various implementations, the computing device 10 may include a log entry receiving module 108 that is particularly configured to receive log entries associated with a plurality of source users 2*. In some implementations, the log entry receiving module 108 may further include one or more additional sub-modules. For example, in some instances, the log entry receiving module 108 may include a social networking entry receiving module 110 that is configured to receive social networking entries (e.g., log entries provided through social networking channels such as social networking sites). The social networking entry receiving module 110 may further include a blog entry receiving module 111 (e.g., configured to receive blog entries) and/or a status report receiving module 112 (e.g., configured to receive social networking status reports). In the same or different implementations, the log entry receiving module 108 may further include a journal entry receiving module 114 (e.g., configured to receive journal or diary entries) and/or sensor entry receiving module 115 (e.g., configured to receive log entries provided by sensors 240).
  • FIG. 2 a illustrates particular implementations of the relevant reported aspect providing module 102 of FIG. 1 b. The relevant reported aspect providing module 102 in various implementations may include, among other things, a memory acquiring module 202 that is configured to, among other things, acquire one or more of the plurality of relevant reported aspects 14 that are relevant to achieving one or more target outcomes from a memory 116 and/or a network acquiring module 204 that is configured to acquire one or more of the plurality of relevant reported aspects 14 via one or more communication networks 50 and that may include a solicitation transmitting module 206 that is configured to transmit one or more solicitations 12 for the one or more relevant reported aspects 14 via the one or more communication networks 50.
  • In the same or different implementations, the relevant reported aspect providing module 102 may include a “target outcome corresponding reported aspect” identifying module 208, a source user identifying module 210, an identified source user associated reported aspect providing module 212, and/or a “relevancy factor relevant reported aspect” providing module 214. A more detailed discussion regarding these sub-modules of the relevant reported aspect providing module 102 will be provided with respect to the processes and operations to be described herein.
  • FIG. 2 b illustrates particular implementations of the template developing module 104 of the computing device 10 of FIG. 1 b. In various implementations, the template developing module 104 may include at least an emulatable aspect including module 216 that may be particularly configured to include into a template 16 one or more emulatable aspects. Each of the one or more emulatable aspects to be included in the template 16 by the emulatable aspect including module 216 may have been developed based on a plurality of relevant reported aspects 14 of a plurality of source users 2*. The emulatable aspect including module 216 may further include an emulatable aspect deriving module 218 that may be particularly configured to derive the one or more emulatable aspects to be included in the template 16. The emulatable aspect deriving module 218 may, in turn, further include a commonly reported aspect determining module 220, a deviation determining module 222 (which may further include a mean value determining module 224 and/or an average value determining module 226), a compliant determining module 228, and/or a plausible emulatable aspect determining module 230. These modules and sub-modules of the template developing module 104 will be discussed in greater detail below with respect to the processes and operation to be described herein.
  • In some implementations, the template developing module 104 may further include an emulatable aspect relationship defining module 232 that is configured to define one or more relationships (e.g., temporal or specific time relationships) between emulatable aspects in a template 16 when the template 16 includes a plurality of emulatable aspects. Such relationships may be based, at least in part, on the relevant reported aspects 14 provided by the relevant reported aspect providing module 102. In some cases, such relationships may also be provided by using techniques similar to the techniques that will be described herein that may be used in order to derive the emulatable aspects to be included in the template 16. In other cases, such relationships may be determined by determining trends that may be detected with respect to how relevant reported aspects 14 were executed by the source users 2*. In still other cases, more sophisticated analysis may be performed in order to determine the relationships between the emulatable aspects that may be included in a template 16.
  • Referring back to the computing device 10 of FIG. 1 b, the various modules (e.g., the relevant reported aspect providing module 102, the template developing module 104, and so forth) along with their sub-modules included in the computing device 10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the relevant reported aspect providing module 102 and/or the template developing module 104 may be implemented with a processor 802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 804 (e.g., computer program product) stored in a storage medium 806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 10 of FIG. 8. Alternatively, hardware such as application specific integrated circuit (ASIC) may be employed in order to implement such modules in some alternative implementations.
  • A more detailed description of the computing device 10 of FIG. 1 b and its components will now be provided with respect to the processes and operations to be described herein. FIG. 3 illustrates an operational flow 300 representing example operations directed to, among other things, development of a template 16 that is designed to facilitate one or more end users 4* to achieve the one or more target outcomes when one or more emulatable aspects included in the template 16 are emulated, the development of the template 16 being based, at least in part, on relevant reported aspects 14 of a plurality of source users 2* that are relevant to achieving the one or more target outcomes.
  • In FIG. 3 and in the following figures that include various examples of operational flows, discussions and explanations of the operational flows will be provided with respect to the exemplary environment 100 described above as illustrated in FIGS. 1 a and 1 b, and/or with respect to other examples (e.g., as provided in FIGS. 2 a and 2 b) and contexts. However, it should be understood that the operational flows may be executed in a number of other environments and contexts, and/or in modified versions of FIGS. 1 a, 1 b, 2 a, and 2 b. Also, although the various operational flows are presented in the sequence(s) illustrated, it should be understood that the various operations may be performed in other orders other than those which are illustrated, or may be performed concurrently.
  • Further, in FIG. 3 and in the figures to follow thereafter, various operations may be depicted in a box-within-a-box manner. Such depictions may indicate that an operation in an internal box may comprise an optional example embodiment of the operational step illustrated in one or more external boxes. However, it should be understood that internal box operations may be viewed as independent operations separate from any associated external boxes and may be performed in any sequence with respect to all other illustrated operations, or may be performed concurrently.
  • In any event, after a start operation, the operational flow 300 may move to a relevant reported aspect providing operation 302 for providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes. For instance, and as an illustration, the relevant reported aspect providing module 102 of the computing device 10 of FIG. 1 b providing (e.g., acquiring, retrieving, identifying, finding, locating, accessing, and so forth) a plurality of relevant reported aspects 14 associated with a plurality of source users 2* that are relevant to achieving one or more target outcomes (e.g., health or medical outcomes, athletic or fitness outcomes, user state outcomes such as subjective mental state outcomes, spiritual outcomes, and so forth), the providing of the plurality of relevant reported aspects 14 being based, at least in part, on relevancy of the plurality of relevant reported aspects 14 with respect to the one or more target outcomes.
  • In addition to the relevant reported aspect providing operation 302, operational flow 300 may also include a template developing operation 304 for developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users. For instance, the template developing module 104 of the computing device 10 developing a template 16 that is designed to facilitate one or more end users 4* to achieve the one or more target outcomes when one or more emulatable aspects included in the template 16 are emulated, the development of the template 16 being based, at least in part, on the providing of the plurality of relevant reported aspects 14 associated with the plurality of source users 2*. Note that in various implementations, the relevant reported aspect providing operation 302 and the template developing operation 304 of FIG. 3 may be implemented in a variety of different ways.
  • For example, FIGS. 4 a, 4 b, 4 c, 4 d, and 4 e illustrate various ways that the relevant reported aspect providing operation 302 of FIG. 3 may be executed in various alternative implementations. For instance, the relevant reported aspects 14 provided through operation 302 may be provided from various sources in various alternative implementations. In some implementations, for example, the relevant reported aspect providing operation 302 may include an operation 402 for acquiring the relevant reported aspects from a memory as depicted in FIG. 4 a. For instance, the memory acquiring module 202 (see FIG. 2 a) of the computing device 10 acquiring (e.g., locating, finding, retrieving, identifying, and so forth) the relevant reported aspects 14 from a memory 116 (e.g., volatile or non-volatile memory including, for example, cache memory).
  • In some implementations, the relevant reported aspect providing operation 302 may include an operation 403 for acquiring the relevant reported aspects via one or more communication networks as depicted in FIG. 4 a. For instance, the network acquiring module 204 (see FIG. 2 a) of the computing device 10 acquiring (e.g., soliciting, querying, retrieving, receiving, and so forth) the relevant reported aspects 14 via one or more communication networks 50 (e.g., a wireless network and/or a wired network).
  • In some cases, operation 403 may, in turn, include an operation 404 for acquiring the relevant reported aspects via the one or more communication networks by transmitting one or more solicitations for the one or more relevant reported aspects via the one or more communication networks as depicted in FIG. 4 a. For instance, the network acquiring module 204 of the computing device 10 acquiring the relevant reported aspects 14 via the one or more communication networks 50 by having the solicitation transmitting module 206 (see FIG. 2 a) transmitting one or more solicitations 12 (e.g., requests, queries, and so forth) for the one or more relevant reported aspects 14 via the one or more communication networks 50.
  • In the same or different implementations, the relevant reported aspect providing operation 302 of FIG. 3 may include one or more operations to determine or identify the plurality of relevant reported aspects 14. For example, in some implementations, the relevant reported aspect providing operation 302 of FIG. 3 may include an operation 405 for providing the plurality of relevant reported aspects by at least identifying reported aspects that correspond to the one or more target outcomes as depicted in FIG. 4 b. For instance, the relevant reported aspect providing module 102 including the “target outcome corresponding reported aspect identifying” module 208 of the computing device 10 providing the plurality of relevant reported aspects 14 by at least identifying reported aspects 13 (which may be stored in a memory 116 and/or located at one or more network sites such as at the one or more local source user devices 20* or at the one or more network servers 60) that correspond (e.g., equivalent or substantially equivalent) to the one or more target outcomes.
  • Operation 405, in turn, may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 405 may include an operation 406 for identifying the source users based on the source users association with the reported aspects that corresponds to the one or more target outcomes as depicted in FIG. 4 b. For instance, the source user identifying module 210 (see FIG. 2 a) of the computing device 10 identifying the source users 2* based on the source users 2*association with the reported aspects (e.g., source users 2* reporting that they had achieved an A1C score, an indication of blood glucose level, of 6.2 or 6.0) that corresponds to the one or more target outcomes (e.g., A1C score of 6.2 or lower).
  • In some implementations, operation 406 may further include an operation 407 for providing reported aspects that are at least associated with the identified source users as depicted in FIG. 4 b. For instance, the “identified source user associated reported aspect providing” module 212 (see FIG. 2 a) of the computing device 10 providing reported aspects 13 that are at least associated with the identified source users 2*. In other words, providing reported aspects 13 that indicate specific aspects of the identified source users 2*.
  • In some implementations, operation 407 may further include an operation 408 for providing, from the reported aspects that are at least associated with the identified source users, reported aspects that are relevant with respect to one or more relevancy factors as depicted in FIG. 4 b. For instance, the relevancy factor relevant reported aspect providing module 214 (see FIG. 2 a) of the computing device 10 providing, from the reported aspects 13 that are at least associated with the identified source users 2*, reported aspects 13 (e.g., relevant reported aspects 14) that are relevant with respect to one or more relevancy factors.
  • In various implementations, operation 408 may further include one or more additional operations including, for example, an operation 409 for providing the reported aspects that are relevant with respect to the one or more relevancy factors by providing reported aspects that are at least associated with the identified source users and that belong to one or more aspect types that are of interest to one or more end users as depicted in FIG. 4 b. For instance, the relevancy factor relevant reported aspect providing module 214 of the computing device 10 providing the reported aspects 13 that are relevant with respect to the one or more relevancy factors by providing reported aspects 13 (e.g., relevant reported aspects 14) that are at least associated with the identified source users 2* and that belong to one or more aspect types that are of interest to one or more end users 4*.
  • In the same or different implementations, operation 408 may include an operation 410 for providing the reported aspects that are relevant with respect to the one or more relevancy factors by providing reported aspects that are at least associated with the identified source users and that belong to one or more aspect types that have been indicated by at least one source user as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 4 b. For instance, the relevancy factor relevant reported aspect providing module 214 of the computing device 10 providing the reported aspects 13 that are relevant with respect to the one or more relevancy factors by providing reported aspects 13 (e.g., relevant reported aspects 14) that are at least associated with the identified source users 2* and that belong to one or more aspect types that have been indicated by at least one source user 2* as being relevant to the achievement of the one or more target outcomes.
  • In the same or different implementations, operation 408 may include an operation 411 for providing the reported aspects that are relevant with respect to the one or more relevancy factors by providing reported aspects that are at least associated with the identified source users and that belong to one or more aspect types that have been indicated by at least one third party source as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 4 b. For instance, the relevancy factor relevant reported aspect providing module 214 of the computing device 10 providing the reported aspects 13 that are relevant with respect to the one or more relevancy factors by providing reported aspects 13 (e.g., relevant reported aspects 14) that are at least associated with the identified source users 2* and that belong to one or more aspect types that have been indicated by at least one third party source (e.g., a publication, a peer-reviewed research publication, a third party 6, and so forth) as being relevant to the achievement of the one or more target outcomes.
  • In the same or different implementations, operation 408 may include an operation 412 for providing the reported aspects that are relevant with respect to the one or more relevancy factors by providing reported aspects that are at least associated with the identified source users and that indicate aspects of the identified source users that occurred within one or more predefined time periods, respectively, from occurrences of the reported aspects that were identified as corresponding to the one or more target outcomes as depicted in FIG. 4 b. For instance, the relevancy factor relevant reported aspect providing module 214 of the computing device 10 providing the reported aspects 13 that are relevant with respect to the one or more relevancy factors by providing reported aspects 13 (e.g., cease consuming caffeine and increase exercise activities) that are at least associated with the identified source users 2* and that indicate aspects of the identified source users 2* that occurred within one or more predefined time periods (e.g., two months), respectively, from occurrences of the reported aspects 13 (e.g., lowering blood pressure) that were identified as corresponding to the one or more target outcomes (e.g., lowering blood pressure). The purpose here is to, for example, exclude from consideration those reported aspects 13 that indicate aspects of the identified source users 2* that occurred well before or well after the achievement of the one or more target outcomes by the identified source user 2*. In various implementations, the predefined time periods may be set by a source user 2*, by an end user 4*, or by a third party 6 (e.g., a physician, a content provider, a network service provider, and so forth).
  • In various implementations, operation 412 may include an operation 413 for providing the reported aspects that are relevant with respect to the one or more relevancy factors by providing reported aspects that are at least associated with the identified source users and that indicate aspects of the identified source users that occurred prior to and within one or more predefined time periods, respectively, from occurrences of the reported aspects that were identified as corresponding to the one or more target outcomes as depicted in FIG. 4 b. For instance, the relevancy factor relevant reported aspect providing module 214 of the computing device 10 providing the reported aspects 13 that are relevant with respect to the one or more relevancy factors by providing reported aspects 13 (e.g., jogging) that are at least associated with the identified source users 2* and that indicate aspects of the identified source users 2* that occurred prior to and within one or more predefined time periods (e.g., 2 weeks), respectively, from occurrences of the reported aspects 13 (e.g., getting 8 hours of continuous and restful sleep) that were identified as corresponding to the one or more target outcomes (e.g., 8 hours of continuous and restful sleep).
  • The plurality of relevant reported aspects 14 that may be provided through the relevant reported aspect providing operation 302 of FIG. 3 may have been originally reported by a variety of different ways. For example, in some implementations, the relevant reported aspect providing operation 302 of FIG. 3 may include an operation 414 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported via one or more log entries as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported via one or more log entries (e.g., as received by, for example, the log entry receiving module 108 of the computing device 10).
  • In various implementations, operation 414 may include one or more additional operations. For example, in some cases, operation 414 may further include an operation 415 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported via one or more social networking entries as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported via one or more social networking entries (e.g., as received by, for example, the social networking entry receiving module 110 of the computing device 10).
  • In various implementations, operation 415 may further include an operation 416 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported via one or more blog entries as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported via one or more blog entries such as one or more microblog entries (e.g., as received by, for example, the blog entry receiving module 111 of the computing device 10).
  • In the same or different implementations, operation 415 may include an operation 417 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported via one or more status reports as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported via one or more status reports such as one or more social networking status reports (e.g., as received by, for example, the status report receiving module 112 of the computing device 10).
  • In some implementations, operation 414 may include an operation 418 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported via one or more journal entries as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported via one or more journal entries (e.g., as received by, for example, the journal entry receiving module 114 of the computing device 10).
  • In the same or different implementations, operation 414 may include an operation 419 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported by one or more of the source users as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported by one or more of the source users 2*.
  • In the same or different implementations, operation 414 may further include an operation 420 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported by one or more third parties as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported by one or more third parties 6.
  • In some implementations, operation 414 may include an operation 421 for providing the plurality of relevant reported aspects associated with the plurality of source users that are relevant to achieving one or more target outcomes including one or more relevant reported aspects that were at least originally reported by one or more sensors as depicted in FIG. 4 c. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 associated with the plurality of source users 2* that are relevant to achieving one or more target outcomes including one or more relevant reported aspects 14 that were at least originally reported by one or more sensors 240 (which may be located at one or more local source user devices 20*, at one or more sensor integrated devices 40, and/or at the computing device 10).
  • In various implementations, the relevant reported aspect providing operation 302 of FIG. 3 may include an operation 422 for providing the plurality of relevant reported aspects including providing a first one or more reported aspects that are associated with a first source user and that are relevant to achieving at least one of the one or more target outcomes and providing a second one or more reported aspects that are associated with a second source user and that are relevant to achieving the at least one of the one or more target outcomes, the providing of the first one or more reported aspects and the second one or more reported aspects being based on the first one or more reported aspects' and the second one or more reported aspects' relevancy with respect to the at least one of the one or more target outcomes as depicted in FIG. 4 d. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a first one or more reported aspects 13 that are associated with a first source user 2 a and that are relevant to achieving at least one of the one or more target outcomes and providing a second one or more reported aspects 13 that are associated with a second source user 2 b and that are relevant to achieving the at least one of the one or more target outcomes, the providing of the first one or more reported aspects 13 and the second one or more reported aspects 13 being based on relevancy of the first one or more reported aspects 13 and the second one or more reported aspects 13 with respect to the at least one of the one or more target outcomes.
  • The plurality of relevant reported aspects 14 that may be provided through the relevant reported aspect providing operation 302 of FIG. 3 may include a variety of aspects related to the plurality of source users 2*. For example, in some implementations, relevant reported aspect providing operation 302 may include an operation 423 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of behavior incidences associated with the plurality of source users as depicted in FIG. 4 d. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of behavior incidences (e.g., dietary activities, exercise activities, social behavior, and so forth) associated with the plurality of source users 2*.
  • In some implementations, operation 423 may further include an operation 424 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user activities associated with the plurality of source users as depicted in FIG. 4 d. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user activities (e.g., consuming a particular medication or food, sleeping in a particular type of bed, reading a particular book, and so forth) associated with the plurality of source users 2*.
  • In the same or different implementations, operation 423 may include an operation 425 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user attitudes associated with the plurality of source users as depicted in FIG. 4 d. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user attitudes (e.g., disdain, loving or caring, and so forth) associated with the plurality of source users 2*.
  • In the same or different implementations, operation 423 may include an operation 426 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user conduct associated with the plurality of source users as depicted in FIG. 4 d. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user conduct (e.g., treating subordinates as equal, driving a friend's car carefully, and so forth) associated with the plurality of source users 2*.
  • In some implementations, the relevant reported aspect providing operation 302 of FIG. 3 may include an operation 427 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user beliefs associated with the plurality of source users as depicted in FIG. 4 e. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user beliefs (e.g., dietary beliefs, social or religious beliefs, superstitious beliefs, and so forth) associated with the plurality of source users 2*.
  • In the same or different implementations, the relevant reported aspect providing operation 302 may include an operation 428 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user states associated with the plurality of source users as depicted in FIG. 4 e. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user states (e.g., marital state, academic state, social state, health or fitness state, mental state, physical state, and so forth) associated with the plurality of source users 2*.
  • In the same or different implementations, the relevant reported aspect providing operation 302 may include an operation 429 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user physical characteristics associated with the plurality of source users as depicted in FIG. 4 e. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user physical characteristics (e.g., body fat level, hair color, and so forth) associated with the plurality of source users 2*.
  • In the same or different implementations, the relevant reported aspect providing operation 302 may include an operation 430 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of user locations associated with the plurality of source users as depicted in FIG. 4 e. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of user locations associated with the plurality of source users 2*.
  • In the same or different implementations, the relevant reported aspect providing operation 302 may include an operation 431 for providing the plurality of relevant reported aspects including providing a plurality of relevant reported aspects related to a plurality of incidences of external events associated with the plurality of source users as depicted in FIG. 4 e. For instance, the relevant reported aspect providing module 102 of the computing device 10 providing the plurality of relevant reported aspects 14 including providing a plurality of relevant reported aspects 14 related to a plurality of incidences of external events (e.g., external environmental or atmospheric conditions) associated with the plurality of source users 2*.
  • Referring back to FIG. 3, the template developing operation 304 may be implemented in a number of different ways in various alternative implementations. For example, in some implementations, the template developing operation 304 may include an operation 532 for developing the template by including into the template one or more emulatable aspects that were derived based, at least in part, on the plurality of relevant reported aspects that are associated with the plurality of source users and that are relevant to achieving the one or more target outcomes as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 (see FIG. 2 b) include into the template 16 one or more emulatable aspects that were derived (e.g., as derived by, for example, the emulatable aspect deriving module 218) based, at least in part, on the plurality of relevant reported aspects 14 that are associated with the plurality of source users 2* and that are relevant to achieving one or more target outcomes.
  • In various implementations, operation 532 may further include an operation 533 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on a plurality of relevant reported aspects that are each associated with different source users as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived (e.g., as derived by, for example, the emulatable aspect deriving module 218) based, at least in part, on a plurality of relevant reported aspects 14 that are each associated with different source users 2*.
  • In some cases, operation 533 may further include an operation 534 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on a first relevant reported aspect that is associated with a first source user and a second relevant reported aspect that is associated with a second source user as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 (see FIG. 2 b) include into the template 16 at least one emulatable aspect (e.g., jogging for 45 minutes) that was derived (e.g., as derived by, for example, the emulatable aspect deriving module 218) based, at least in part, on a first relevant reported aspect (e.g., jogging for 55 minutes) that is associated with a first source user 2 a and a second relevant reported aspect (e.g., jogging for 35 minutes) that is associated with a second source user 2 b.
  • In some implementations, operation 534 may further include one or more additional operations including, for example, an operation 535 for developing the template by including into the template a second emulatable aspect that was derived based, at least in part, on a third relevant reported aspect that is associated with the first source user and a fourth relevant reported aspect that is associated with the second source user as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 a second emulatable aspect (e.g., jogging at a moderate pace) that was derived (e.g., as derived by, for example, the emulatable aspect deriving module 218) based, at least in part, on a third relevant reported aspect (e.g., jogging at a very quick pace) that is associated with the first source user 2 a and a fourth relevant reported aspect (e.g., jogging at a very slow pace) that is associated with the second source user 2 b.
  • In the same or different implementations, operation 534 may include an operation 536 for developing the template by including into the template a second emulatable aspect that was derived based, at least in part, on a third relevant reported aspect that is associated with a third source user and a fourth relevant reported aspect that is associated with a fourth source user as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 a second emulatable aspect (e.g., rowing for one hour) that was derived (e.g., as derived by, for example, the emulatable aspect deriving module 218) based, at least in part, on a third relevant reported aspect (e.g., rowing for one hour) that is associated with a third source user 2 c and a fourth relevant reported aspect (e.g., swimming for one hour) that is associated with a fourth source user 2 d.
  • Note that in this example, the second emulatable aspect that was included into the template 16 was the same as the third relevant reported aspect (of the third source user 2 c) completely different from the fourth relevant reported aspect (of the fourth source user 2 d). In cases like this, certain factors or rules may be considered in resolving conflicts between relevant reported aspects in order to, for example, determine the second emulatable aspect. For example, there may be a rule that says that the most commonly executed reported aspect be used in order to determine an emulatable aspect (e.g., in the above example, the first source user 2 a and the second source user 2 b may also have reported rowing for one hour). In another example, relevant reported aspects of, for example, a first group of source users 2* may be given more weight than the relevant reported aspects of a second group of source users 2* because the first group of source users 2* may have similar traits (e.g., physical traits, health traits, intellectual traits, and so forth) as the end users 4*. Of course, those skilled in the art will recognize that there are many other tie breaker rules that may be used in order to resolve conflicts between relevant reported aspects.
  • In various implementations, operation 533 for developing a template 16 by including into the template 16 at least one emulatable aspect may include an operation 537 for developing the template by including into the template at least one emulatable aspect that corresponds to a commonly reported aspect that is determined to be associated with two or more of the plurality of source users as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that corresponds to a commonly reported aspect (e.g., a source user aspect that is reported by, for example, more than one source user 2*) that is determined to be associated with two or more of the plurality of source users 2*(e.g., as determined by the commonly reported aspect determining module 220).
  • In some implementations, operation 537 may further include an operation 538 for developing the template by including into the template at least one emulatable aspect that corresponds to a commonly reported aspect that is determined to be associated with a majority of the plurality of source users as depicted in FIG. 5 a. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that corresponds to a commonly reported aspect that is determined to be associated with a majority of the plurality of source users 2*(e.g., as determined by the commonly reported aspect determining module 220).
  • In various implementations, the operation 533 for developing a template 16 by including into the template 16 at least one emulatable aspect may include an operation 539 for developing the template by including into the template at least one emulatable aspect that includes at least a portion that was derived based, at least in part, on deviations of the plurality of relevant reported aspects with respect to each other as depicted in FIG. 5 b. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect (e.g., swimming for 30 minutes) that includes at least a portion (e.g., 30 minutes) that was derived based, at least in part, on deviations of the plurality of relevant reported aspects 14 with respect to each other (e.g., as determined by, for example, the deviation determining module 222).
  • In some implementations, operation 539 may further include an operation 540 for developing the template by including into the template at least one mean value emulatable aspect that was at least partially developed by determining a mean value for the plurality of relevant reported aspects as depicted in FIG. 5 b. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one mean value emulatable aspect that was at least partially developed by determining a mean value for the plurality of relevant reported aspects 14 (e.g., as determined by, for example, the mean value determining module 224). For example, in the above swimming example, determining the mean value for the amount of time that the source users 2* reported swimming. Note that in some cases it may also be possible to obtain a mean value for variables that may not be considered quantifiable variables such as, for example, “jogging” (e.g., a mean value can be obtained from, for example, jogging at a fast pace, jogging at a moderate pace, or jogging at a slow pace).
  • In the same or different implementations, operation 539 may include an operation 541 for developing the template by including into the template at least one average value emulatable aspect that was at least partially developed by determining an average value for the plurality of relevant reported aspects as depicted in FIG. 5 b. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one average value emulatable aspect that was at least partially developed by determining an average value for the plurality of relevant reported aspects 14 (e.g., as determined by, for example, the average value determining module 226).
  • In some cases, operation 533 for developing a template 16 by including into the template 16 at least one emulatable aspect may include an operation 542 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more limitations associated with at least one of the one or more end users as depicted in FIG. 5 b. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with (e.g., not violating) one or more limitations associated with at least one of the one or more end users 4*.
  • In some implementations, operation 542 may further include an operation 543 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more contextual limitations associated with at least one of the one or more end users as depicted in FIG. 5 b. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more contextual limitations (e.g., logistical limitations such as no or limited access to a swimming pool, a car, or a particular text book) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 542 may include an operation 544 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more personal limitations associated with at least one of the one or more end users as depicted in FIG. 5 b. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more personal limitations (e.g., dietary or religious limitations) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 542 may include an operation 545 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more physical limitations associated with at least one of the one or more end users as depicted in FIG. 5 c. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more physical limitations (e.g., having severe arthritis) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 542 may include an operation 546 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more medical or health limitations associated with at least one of the one or more end users as depicted in FIG. 5 c. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more medical or health limitations (e.g., being lactose intolerant, being diabetic, or being in poor physical shape) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 542 may include an operation 547 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more user state limitations associated with at least one of the one or more end users as depicted in FIG. 5 c. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more user state limitations (e.g., being married, being unemployed, or being mentally or physically fatigued) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 542 may include an operation 548 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more legal or regulatory limitations associated with at least one of the one or more end users as depicted in FIG. 5 c. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more legal or regulatory limitations (e.g., local drug regulations) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 542 may include an operation 549 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with a different source user, the at least one emulatable aspect being determined to be compliant with one or more academic or intellectual limitations associated with at least one of the one or more end users as depicted in FIG. 5 d. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with a different source user 2*, the at least one emulatable aspect being determined (e.g., as determined by the compliant determining module 228) to be compliant with one or more academic or intellectual limitations (e.g., lacks particular educational or training background) associated with at least one of the one or more end users 4*.
  • In the same or different implementations, operation 533 may include an operation 550 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with different source users, the at least one emulatable aspect being determined to be at least one plausible emulatable aspect that has been successfully emulated by one or more third parties who share at least one common trait with the one or more end users as depicted in FIG. 5 d. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with different source users 2*, the at least one emulatable aspect being determined (e.g., as determined by the plausible emulatable aspect determining module 230) to be at least one plausible emulatable aspect that has been successfully emulated by one or more third parties 6 who share at least one common trait (e.g., ethnicity or illness) with the one or more end users 4*.
  • In the same or different implementations, operation 533 may include an operation 551 for developing the template by including into the template at least one emulatable aspect that was derived based, at least in part, on the plurality of relevant reported aspects that are each associated with different source users, the at least one emulatable aspect being determined to be at least one plausible emulatable aspect that has been successfully emulated by one or more third parties in order to achieve the one or more target outcomes as depicted in FIG. 5 d. For instance, the template developing module 104 of the computing device 10 developing the template 16 by having the emulatable aspect including module 216 include into the template 16 at least one emulatable aspect that was derived by the emulatable aspect deriving module 218 based, at least in part, on the plurality of relevant reported aspects 14* that are each associated with different source users 2*, the at least one emulatable aspect being determined (e.g., as determined by the plausible emulatable aspect determining module 230) to be at least one plausible emulatable aspect that has been successfully emulated by one or more third parties 6 in order to achieve the one or more target outcomes.
  • In various implementations, the template 16 that is developed through the template developing operation 304 of FIG. 3 may be designed to facilitate achievement of any one or more of a variety of target outcomes. For example, in some implementations, the template developing operation 304 may include an operation 552 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more health or medical outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more health or medical outcomes (e.g., losing weight, improve results of a medical treatment, reduce pain, reduce stress, reduce blood pressure or blood glucose levels, and so forth).
  • In the same or different implementations, the template developing operation 304 may include an operation 553 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more athletic or gaming outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more athletic or gaming outcomes (e.g., win a tennis tournament, lower golf handicap, improve scores on an electronic game, and so forth).
  • In the same or different implementations, the template developing operation 304 may include an operation 554 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more occupational outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more occupational outcomes (e.g., complete a work project, getting a new client, obtaining a promotion, and so forth).
  • In the same or different implementations, the template developing operation 304 may include an operation 555 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more social or leisure outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more social or leisure outcomes (e.g., invited to be a member of an elite social organization, acquiring new friends, and so forth).
  • In the same or different implementations, the template developing operation 304 may include an operation 556 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more sexual intimacy outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more sexual intimacy outcomes (e.g., increase the frequency of sexual encounters).
  • In the same or different implementations, the template developing operation 304 may include an operation 557 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more academic or intellectual outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more academic or intellectual outcomes (e.g., understanding particular concepts introduced in a book, accepted for enrollment at a particular University, and so forth).
  • In the same or different implementations, the template developing operation 304 may include an operation 558 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more spiritual or religious outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more spiritual or religious outcomes (e.g., achieve spiritual harmony, acceptance to a particular church or religion, and so forth).
  • In the same or different implementations, the template developing operation 304 may include an operation 559 for developing the template designed to facilitate the one or more end users to achieve the one or more target outcomes including one or more user state outcomes as depicted in FIG. 5 e. For instance, the template developing module 104 of the computing device 10 developing the template 16 designed to facilitate the one or more end users 4* to achieve the one or more target outcomes including one or more user state outcomes (e.g., achieve certain subjective user states such as being “happy” or “content,” achieve certain social states such as being married, and so forth).
  • Referring to FIG. 6 illustrating another operational flow 600 in accordance with various embodiments. Operational flow 600 includes certain operations that mirror the operations included in the operational flow 300 of FIG. 3. These operations include a relevant reported aspect providing operation 602 and a template developing operation 604 that corresponds to and mirror the relevant reported aspect providing operation 302 and the template developing operation 304, respectively, of FIG. 3.
  • In addition, operational flow 600 includes a template presenting operation 606 for presenting the template as depicted in FIG. 6. For instance, the template presenting module 106 of the computing device 10 presenting the template 16 resulting from the template developing operation 604.
  • In some implementations, the template presenting operation 606 of FIG. 6 may include an operation 761 for transmitting the template via one or more communication networks as depicted in FIG. 7. For instance, the template transmitting module 150 (see FIG. 1 b) of the computing device 10 transmitting the template 16 via one or more communication networks 50.
  • In the same or different implementations, the template presenting operation 606 may include an operation 762 for indicating the template via a user interface as depicted in FIG. 7. For instance, the template indicating module 152 of the computing device 10 indicating the template 16 via a user interface 120 (e.g., a display monitor, a touch screen, one or more speakers, and so forth).
  • In the same or different implementations, the template presenting operation 606 may include an operation 763 for presenting the template to the one or more end users as depicted in FIG. 7. For instance, the template presenting module 106 of the computing device 10 presenting the template 16 to the one or more end users 4*.
  • In the same or different implementations, the template presenting operation 606 may include an operation 764 for presenting the template to one or more third parties as depicted in FIG. 7. For instance, the template presenting module 106 of the computing device 10 presenting the template 16 to one or more third parties 6 (e.g., health or medical entities such as a doctor's office, a future end user 4*, and so forth).
  • Turning now to FIG. 8, which is a high-level block diagram illustrating a particular implementation of the computing device 10 of FIG. 1 b. As illustrated, the computing device 10 may include a processor 802 (e.g., microprocessor, controller, and so forth) coupled to a storage medium 806 (e.g., volatile or non-volatile memory). The storage medium 806 may store computer readable instructions 804 (e.g., computer program product). The processor 802, in various implementations, may execute the computer readable instructions 804 in order to execute one or more operations described above and as illustrated in FIGS. 3, 4 a, 4 b, 4 c, 4 d, 4 e, 5 a, 5 b, 5 c, 5 d, 5 e, 6, and 7.
  • For example, the processor 802 may execute the computer readable instructions 804 in order to provide a plurality of relevant reported aspects 14 associated with a plurality of source users 2* that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects 14 being based, at least in part, on relevancy of the plurality of relevant reported aspects 14 with respect to the one or more target outcomes; and/or to develop a template 16 designed to facilitate one or more end users 4* to achieve the one or more target outcomes when one or more emulatable aspects included in the template 16 are emulated, the development of the template 16 being based, at least in part, on the providing of the plurality of relevant reported aspects 14 associated with the plurality of source users 2* as illustrated by the operational flow 300 of FIG. 3.
  • Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems and/or other technologies described herein can be effected (e.g., hardware, software, and/or firmware), 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.
  • The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuitry (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuitry, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • In a general sense, those skilled in the art will recognize that the various aspects described herein which can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof can be viewed as being composed of various types of “electrical circuitry.” Consequently, as used herein “electrical circuitry” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment). Those having skill in the art will recognize that the subject matter described herein may be implemented in an analog or digital fashion or some combination thereof.
  • Those having skill in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system generally includes one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
  • The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
  • While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. Furthermore, it is to be understood that the invention is defined by the appended claims.
  • It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.).
  • It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations.
  • In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).
  • In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
  • II. Personalized Plan Development
  • In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
  • A recent trend that has enjoyed explosive popularity in the computing/communication field is to electronically record one's daily activities, behaviors, thoughts, beliefs, traits, physical or mental states, physical characteristics, and other aspects of the person's everyday life onto an open diary. One place where such open diaries are maintained is at social networking sites commonly known as “blogs” where one or more users may report or post every aspect of their lives. The process of reporting or posting blog entries is commonly referred to as blogging. Newer types of blogs that are also becoming increasingly popular are known as microblogging or “twittering,” whereby each of the microblogs that are posted are typically relatively short posts or entries, usually not more than 140 characters long.
  • Other social networking sites may allow users to update their personal information via, for example, social networking status reports in which a user may report or post for others to view the latest status or other aspects of the user. Although a wealth of personal information in the form of, for example, log data are now available through such social networking sites, it is only recently has there been any effort to exploit such useful data.
  • In particular embodiments, robust methods, systems, circuitry, and computer program products are provided that may facilitate in the development of a plan that when executed by, for example, an end user may result in the achievement of one or more target outcomes. In order to develop the plan, a model (e.g., a source user), who may be associated with the one or more outcomes, may be initially identified. The plan may then be developed by at least determining from a plurality of reported events or aspects associated with the model those reported aspects that may be relevant to the achievement of the one or more target outcomes. In some cases, the plurality of reported aspects may be indicated by, for example, log data such as data that may have been at least originally acquired through social networking entries (e.g., microblog entries and/or status reports), diary entries, and/or sensor readings.
  • More generally, and in accordance with various embodiments, the robust methods, systems, circuitry, and computer program products may facilitate in the development of a personalized plan designed to assist an end user in achieving one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated. In some implementations, a personalized plan may merely indicate a collection of one or more “emulatable aspects.” An emulatable aspect may be any behavior, act, trait, physical state, mental state, social state, declaration, belief, or any other facet that may be emulated in order to achieve one or more target outcomes. In cases where the personalized plan includes multiple emulatable aspects, the personalized plan may or may not define a relationship or relationships (e.g., temporal, specific time, or spatial relationships) between the emulatable aspects.
  • A target outcome may be any type of goal or desired result that may be sought by an end user or by a third party. Examples of target outcomes include, for example, health-related outcomes such as weight loss or improved cardiovascular conditioning, athletic outcomes such as developing a particular athletic skill including being able to pitch a curve ball or achieving a particular golf handicap, physiological outcomes such as reduced blood pressure or blood glucose levels, social outcomes such as obtaining membership into an elite social club or attaining a particular social status, mental state outcomes such as achieving certain level of calmness or happiness, interpersonal or relational outcomes such as having lots of friends or developing skill to make friends, employment outcomes such as being promoted or developing certain work skills, and so forth.
  • In various implementations, the robust methods, systems, circuitry, and computer program products may begin developing the personalized plan when a request for the personalized plan designed to achieve the one or more target outcomes is initially received. Such a request may at least identify a source user who may be the model for achieving the one or more target outcomes. In other words, the source user may at least be perceived by, for example, an end user as having achieved the at least one or more target outcomes. In some cases, the source user may be an actual or “real” person. While in other cases, the source user may be a “fictional” person (e.g., an alter ego created by someone's imagination) that is associated with the one or more target outcomes. In still other cases, a source user may be a composite person created from data provided by a plurality of “real” persons.
  • In some cases where the source user is an actual or “real” person, the end user may have become aware of the source user when the end user accidently or randomly encountered the source user at some locale such as the gym, at school, at the doctor's office, on the street, or at some other locale. Upon encountering the source user, the end user may perceive that the source user is associated with some admirable quality (e.g., target outcome) and would like to have such a quality. For these cases, the end user may obtain the identity of the source user by a variety of alternative means. For instance, in situations where the end user randomly encounters the source user, the identity of the source user may be obtained by using some sort of sensing device that may be employed to unobtrusively acquire the identity of the source user. Example of such devices include, for example, a radio frequency identification (RFID) reader device (e.g., source user may carry an RFID), a facial recognition device, a device that determine the geographical location of a source user such as certain types of cellular telephones, and so forth.
  • Alternatively, a source user (e.g., actual, composite, or fictional person) may be listed at a website such as a social networking site. Such a website may allow an end user to access the identity of the source user as well as provide indications of one or more desirable qualities (e.g., target outcomes) associated with the source user.
  • In any event, in response to receiving the request for the personalized plan, “source user data” indicating one or more reported aspects associated with source user may be acquired (e.g., retrieved). In some implementations, the acquired source user data may be in the form of log data associated with the source user that may have been originally been obtained via social networking entries such as microblog entries or status reports, via diary entries, and/or via data entries provided by one or more sensors. Alternatively, such source user data may at least be partially fictional or fabricated.
  • After acquiring the source user data, the methods, systems, circuitry, and computer program products may develop the personalized plan by at least determining which of the one or more reported aspects associated with the source user and indicated by the source user data may be relevant to the achievement of the one or more target outcomes. After determining those reported aspects that are relevant to the achievement of the one or more target outcomes, the personalized plan may be developed by including into the personalized plan one or more emulatable aspects that corresponds to one or more identified reported aspects that are relevant to the achievement of the one or more target outcomes. In certain implementations, where the personalized plan includes a plurality of emulatable aspects, the personalized plan may define the relationships (e.g., temporal, specific time, and/or spatial relationships) between the emulatable aspects.
  • Turning now to FIGS. 1-1 a, 1-1 b, 1-1 c, 1-1 d, 1-1 e, and 1-1 f, illustrating three example environments in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented by a computing device such as a server or a local user device. In particular, FIGS. 1-1 a and 1-1 b illustrates a first example environment in which the methods, systems, circuitry, and computer program products in accordance with some embodiments may be implemented at a server 1-10. FIGS. 1-1 c and 1-1 d illustrates a second example environment in which the methods, systems, circuitry, and computer program products in accordance with some embodiments may be implemented at a local source user device 1-20′. FIGS. 1-1 e and 1-1 f illustrate a third example environment in which the methods, systems, circuitry, and computer program products in accordance with some embodiments may be implemented at a local end user device 1-30″. Note that in the following, “*” represents a wildcard. Thus, “server 1-10*” in the following description may be in reference to server 1-10 of the first example environment of FIGS. 1-1 a and 1-1 b, to server 1-10′ of the second example environment of FIGS. 1-1 c and 1-1 d, or to server 1-10″ of the third example environment of FIGS. 1-1 e and 1-1 f.
  • In various embodiments, the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, and the local end user device 1-30″ of FIG. 1-1 f may be designed to, among other things, receive a request 1-12* for a personalized plan 1-16* that is designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* identifying at least a source user 1-2*. In response to the receiving the request 1-12*, the server 1-10, the local source user device 1-20′, and the local end user device 1-30″ may be designed to acquire source user data 1-14* that may indicate a plurality of reported aspects associated with the source user 1-2*.
  • After acquiring the source user data 1-14*, the server 1-10, the local source user device 1-20′, and the local end user device 1-30″ may be designed to develop the personalized plan 1-16* by at least determining which of the plurality of reported aspects associated with the source user 1-2*are relevant to the achievement of the one or more target outcomes. In some implementations, the server 1-10, the local source user device 1-20′, and the local end user device 1-30″ may be further designed to present the resulting personalized plan 1-16*.
  • Referring particularly now to FIGS. 1-1 a and 1-1 b illustrated the first example environment in accordance with various embodiments. Included in the illustrated first environment of FIGS. 1-1 a and 1-1 b is a first exemplary system 1-100, which includes at least a server 1-10 (see FIG. 1-1 b) that may be designed to communicate with at least a source user 1-2 (via a local source user device 1-20) and an end user 1-4 (via a local end user device 1-30) through a wireless network and/or wired network 1-50. In some implementations, the server 1-10 may further communicate with, via the wireless network and/or wired network 1-50, one or more third parties 1-6 such as one or more other source users, one or more other end users, one or more content providers, one or more network service providers, and/or one or more other third parties. The server 1-10 may also communicate with, via the wireless network and/or wired network 1-50, one or more sensors 1-40.
  • In various implementations, the server 1-10 of FIG. 1-1 b (as well as the server 1-10′ of FIG. 1-1 c and the server 1-10″ of FIG. 1-1 e) may be a network server that is designed to interface with a wireless network and/or wired network 1-50*. A network server, as will be described herein, may be in reference to a server located at a single network site or located across multiple network sites or a conglomeration of servers located at multiple network sites.
  • The local source user device 1-20 (as well as the local source user device 1-20′ of FIG. 1-1 d and the local source user device 1-20″ of FIG. 1-1 e) and the local end user device 1-30 (as well as the local end user device 1-30′ of FIG. 1-1 c and the local end user device 1-30″ of FIG. 1-10 may be a variety of computing/computing devices including, for example, a cellular phone, a personal digital assistant (PDA), a laptop, a desktop, or other types of computing/communication devices that can communicate with the computing device 1-10. In some embodiments, the local source user device 1-20 (as well as the local source user device 1-20′ of FIG. 1-1 d and the local source user device 1-20″ of FIG. 1-1 e) and/or the local end user device 1-30 (as well as the local end user device 1-30′ of FIG. 1-1 c and the local end user device 1-30″ of FIG. 1-10 may be a handheld device such as a cellular telephone, a smartphone, a Mobile Internet Device (MID), an Ultra Mobile Personal Computer (UMPC), a convergent device such as a personal digital assistant (PDA), and so forth.
  • In various embodiments, the one or more sensors 1-40 (as well as the one or more sensors 1-40′ of FIG. 1-1 c and the one or more sensors 1-40″ of FIG. 1-1 e) a wide range of devices that can monitor various aspects or events associated with a source user 1-2*. For example, in some implementations, the one or more sensors 140* may include devices that can monitor a user's physiological characteristics such as blood pressure sensors, heart rate monitors, glucometers, and so forth. In some implementations, the one or more sensors 140* may include devices that can monitor activities of a user (e.g., source user 1-2*) such as a pedometer, a toilet monitoring system (e.g., to monitor bowel movements), exercise machine sensors, an accelerometer to measure a person's movements which may indicate specific activities, and so forth. The one or more sensors 1-40* may also include other types of sensor/monitoring devices such as video or digital camera, global positioning system (GPS) to provide data that may be related to a user (e.g., locations of the source user 1-2*), and so forth.
  • Referring back to the first exemplary environment of FIGS. 1-1 a and 1-1 b, the server 1-10 may receive a request 1-12 for a personalized plan 1-16 from the end user 1-4 via the local end user device 1-30. The request 1-12 may identify at least a source user 1-2. The requested personalized plan 1-16 may be designed to facilitate the end user 1-4 to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16 are emulated. In response to receiving the request 1-12, the server 1-10 may acquire source user data 1-14 that may indicate a plurality of reported aspects associated with at least the source user 1-2. The source user data 1-14 may be acquired from a variety of sources. For example, in some implementations, at least a portion of the source user data 1-14 may be acquired from a memory 1-116. In some implementations, at least a portion of the source user data 1-14 may be acquired from the local source user device 1-20. In some implementations, at least a portion of the source user data 1-14 may be acquired from the one or more third parties. In some implementations, at least a portion of the source user data 1-14 may be acquired from one or more sensors 1-40.
  • After acquiring the source user data 1-14, the server 1-10 may develop the personalized plan 1-16 by at least determining which of the plurality of reported aspects associated with the source user 1-2 are relevant to the achievement of the one or more target outcomes. In some implementations, the server 1-10 may then present the developed personalized plan 1-16 to the end user 1-4 (via the local end user device 1-30) and/or to one or more third parties 1-6.
  • The server 1-10 as illustrated in FIG. 1-1 b may include a variety of modules, sub-modules, and components. As shown, the server 1-10 may include a request reception module 1-102 (which may further include a network interface reception module 1-202, a source user data acquisition module 1-104 (which may further include a request transmission module 1-204 and/or source user data reception module 1-206), a personalized plan development module 1-106, a presentation module 1-108 (which may further include a transmission module 1-228), a memory 1-116 (which may store source user data 1-14 and/or one or more applications 1-140), and/or a network interface 1-118 (e.g., a network interface card or NIC). The server 1-10, in various implementations, may further include a social networking entry reception module 1-110 (which may further include a blog entry reception module 1-111 and/or status report reception module 1-112), a diary entry reception module 1-114, and/or a sensor data reception module 1-115.
  • The request reception module 1-102 may be configured to, among other things, receive a request 1-12 for a personalized plan 1-16 that is designed to facilitate an end user 1-4 to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16 are emulated. The request 1-12 to be received by the request reception module 1-102 may at least identify a source user 1-2. In some implementations, the request 1-12 to be received by the request reception module 1-102 may further include information that may facilitate in the development of the personalized plan 1-16 as will be further described herein. In order to facilitate reception of a request 1-12 from, for example, a network device (e.g., local end user device 1-30 or another server), the request reception module 1-102 may include a network interface reception module 1-202 designed to receive the request 1-12 via a wireless network and/or wired network 1-50.
  • The source user data acquisition module 1-104 may be configured to acquire, in response to the request reception module 1-102 receiving the request 1-12, source user data 1-14 indicating a plurality of reported aspects associated with at least the source user 1-2. In various implementations, the source user data acquisition module 1-104 may further include a request transmission module 1-204 designed to transmit (e.g., via the wireless network and/or wired network 1-50) a request for the source user data 1-14, and a source user data reception module 1-206 designed to receive the source user data 1-14. The source user data 1-14 acquired by the source user data acquisition module 1-104 may indicate, in various implementations, at least a first one or more reported aspects that may be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16, and a second one or more reported aspects that may not be relevant to the achievement of the one or more target outcomes.
  • The personalized plan development module 1-106 may be configured to, among other things, develop a personalized plan 1-16 by at least determining which of the plurality of reported aspects associated with the source user 1-2 as indicated by the source user data 1-14 are relevant to the achievement of the one or more target outcomes of the personalized plan 1-16. For example, filtering the source user data 1-14 to determine or distinguish those reported aspects (e.g., first one or more reported aspects) that are relevant to the achievement of the one or more target outcomes from those reported aspects (e.g., second one or more reported aspects) that are not relevant to the achievement of the one or more target outcomes. After determining which of the reported aspects associated with the source user 1-2 are relevant to the achievement of the one or more target outcomes, the personalized plan development module 1-106 may develop the personalized plan 1-16 by including into the personalized plan 1-16 one or more emulatable aspects that corresponds to one or more reported aspects that have been determined to be relevant to the achievement of the one or more target outcomes. As will be further described herein, the personalized plan development module 1-106 in various implementations may further include one or more sub-modules as will be further described herein and as illustrated in FIG. 1-2.
  • The presentation module 1-108 may be configured to present the personalized plan 1-16 developed by the personalized plan development module 1-106 to the end user 1-4, the source user 1-2, and/or one or more third parties 1-6. In some implementations, presentation module 1-108 may further include a transmission module 1-228 that is configured to transmit the personalized plan 1-16 via, for example, the wireless network and/or wired network 1-50.
  • A more detailed discussion relating to the request reception module 1-102, the source user data acquisition module 1-104, the personalized plan development module 1-106, the presentation module 1-108, and their sub-modules, will be provided below with respect to the various operational flows to be described herein. The social networking entry reception module 1-110 may be configured to receive social networking entries from various sources including, for example, the source user 1-2, the end user 1-4, and/or one or more third parties 1-6. The social networking entry reception module 1-110 may further include a blog entry reception module 1-111 that is configured to receive blog or microblog entries and/or a status report reception module 1-112 configured to receive status reports. Similarly, the diary entry reception module 1-114 may be configured to receive diary entries from, for example, the source user 1-2, the end user 1-4, and/or from one or more third parties 1-6.
  • The sensor data reception module 1-115 may be configured to receive sensing data from one or more sensors 1-40. The memory 1-116 may comprise one or more volatile and/or non-volatile devices that may be used to store data. In various implementations, the memory 1-116 may include, for example, a mass storage device, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), cache memory such as random access memory (RAM), flash memory, synchronous random access memory (SRAM), dynamic random access memory (DRAM), and/or other memory devices. The one or more applications 1-140 that may be included in the memory 1-116 may comprise of, for example, one or more communication applications (e.g., text messaging application, instant messaging application, email application, voice recognition system, and so forth), Web 1.0 application, and/or Web 2.0 application to facilitate in communicating via, for example, the World Wide Web.
  • Referring now to FIGS. 1-1 c and 1-1 d, which as previously indicated, illustrates a second example environment in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented at a local source user device 1-20′ rather than at a server 1-10′ as was the case in the first example environment of FIGS. 1-1 a and 1-1 b. As illustrated, the second example environment of FIGS. 1-1 c and 1-1 d is similar to the first example environment of FIGS. 1-1 a and 1-1 b.
  • In general, the second example environment of FIGS. 1-1 c and 1-1 d may include a second exemplary system 1-100′, which includes at least a local source user device 1-20′ (see FIG. 1-1 d). In various implementations, the local source user device 1-20′ as was the case for server 1-10 of FIGS. 1-1 a and 1-1 b may be designed to receive a request 1-12′ for a personalized plan 1-16′ designed to facilitate an end user 1-4′ to achieve one or more target outcomes via a wireless network and/or wired network 1-50′. In some implementations, the request 1-12′ may be received from an end user 1-4′. Alternatively, and although not depicted, the request 1-12′ may be received from a server 1-10′ or from one or more third parties 1-6′. Note that server 1-10 of the first example environment of FIGS. 1-1 a and 1-1 b may also receive the request 1-12 from other sources (e.g., another server or one or more third parties 1-6) other than from an end user 1-4.
  • In any event, in response to receiving the request 1-12′, the local source user device 1-20′ may be designed to acquire source user data 1-14′ indicating a plurality of reported aspects associated with a source user 1-2′ from one or more sources including, for example, a memory 1-116′, a server 1-10′, one or more sensors 1-40′, and/or one or more third parties 1-6′. The source user data 1-14′ acquired by the local source user device 1-20′ may indicate, in various implementations, at least a first one or more reported aspects that may be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16′, and a second one or more reported aspects that may not be relevant to the achievement of the one or more target outcomes. The local source user device 1-20′ may be further designed to develop a personalized plan 1-16′ by at least determining which of the reported aspects associated with the source user 1-2′ may be relevant to the achievement of the one or more target outcomes. For example, the local source user device 1-20′ may be designed to filter the source user data 1-14′ to determine or distinguish those reported aspects (e.g., first one or more reported aspects) that are relevant to the achievement of the one or more target outcomes from those reported aspects (e.g., second one or more reported aspects) that are not relevant to the achievement of the one or more target outcomes. In some implementations, the local source user device 1-20′ may be further designed to present the developed personalized plan 1-16′ to the end user 1-4′, one or more third parties 1-6′, and/or a server 1-10′.
  • The local source user device 1-20′, as illustrated in FIG. 1-1 d, may include the same or similar modules, sub-modules, and components included in the server 1-10 of FIG. 1-1 b. As illustrated, the local source user device 1-20′ may include a request reception module 1-102′ (which may further include a network interface reception module 1-202′, a source user data acquisition module 1-104′ (which may further include a request transmission module 1-204′ and a source user data reception module 1-206′), a personalized plan development module 1-106′, a presentation module 1-108′ (which may further include a transmission module 1-228′), a memory 1-116′ (which may store source user data 1-14′ and/or one or more applications 1-140′), and/or a network interface 1-118′, similar to the server 1-10 of FIG. 1-1 b.
  • Also similar to server 1-10 of FIG. 1-1 b, the local source user device 1-20′ may also include a social networking entry reception module 1-110′ (which may further include a blog entry reception module 1-111′ and/or a status report reception module 1-112′), a diary entry reception module 1-114′, and/or a sensor data reception module 1-115′. All of these modules, sub-modules, and components of the local source user device 1-20′ may perform the same or similar functions as their counterparts that may be included in the server 1-10 of FIG. 1-1 b. In addition to these modules, sub-modules, and components, the local source user device 1-20′ may include a user interface 1-120′ and a user interface indication module 1-229′ (which may be included with the presentation module 1-108′). The user interface indication module 1-229′ may be designed to indicate, for example, the personalized plan 1-16′ via the user interface 1-120′. The user interface 1-120′ may include one or more of, for example, a display monitor, a touchscreen, a keyboard, a keypad, a mouse, an audio system including one or more speakers, a microphone, an image capturing device such as a digital camera, and so forth.
  • Turning now to FIGS. 1-1 e and 1-1 f, which as previously indicated, illustrates a third example environment in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented at a local end user device 1-30″ rather than at a server 1-10″ or at a local source user device 1-20″ as was the case in the first and second example environments of FIGS. 1-1 a and 1-1 b and FIGS. 1-1 c and 1-1 d. The third example environment of FIGS. 1-1 e and 1-1 f is similar to the first example environment of FIGS. 1-1 a and 1-1 b and the second example environment of FIGS. 1-1 c and 1-1 d with few minor differences. For example, in the third example environment, the local end user device 1-30″ may receive a request 1-12″ for a personalized plan 1-16″ directly from an end user 1-4* via a user interface 1-120″ rather than from the wireless network and/or wired network 1-50″ as was the case for the server 1-10 of the first example environment of FIGS. 1-1 a and 1-1 b and as was the case for the local source user device 1-20′ of the second example environment of FIGS. 1-1 c and 1-1 d. However, and as with the server 1-10 and the local source user device 1-20′ of FIGS. 1-1 b and 1-1 d, the local end user device 1-30″ may also alternatively receive a request 1-12″ via the wireless network and/or wired network 1-50″ from other sources such as from one or more third parties 1-6″ or from a server 1-10″.
  • As illustrated, the third example environment of FIGS. 1-1 e and 1-1 f may include a third exemplary system 1-100″, which includes at least a local end user device 1-30″ (see FIG. 1-1 f). In general, the local end user device 1-30″ may be designed to receive a request 1-12″ for a personalized plan 1-16″ for facilitating an end user 1-4″ in achieving one or more target outcomes. In some implementations, the request 1-12″ may be received directly from the end user 1-4″ via a user interface 1-120″. Alternatively, and although not depicted, the request 1-12″ may be received via wireless network and/or wired network 1-50″ from, for example, one or more third parties 1-6″ or from a server 1-10″.
  • In response to receiving the request 1-12″, the local end user device 1-30″ may be designed to acquire source user data 1-14″ indicating a plurality of reported aspects associated with a source user 1-2″ from one or more sources including, for example, a memory 1-116″, a server 1-10″, one or more sensors 1-40″, and/or one or more third parties 1-6″. The source user data 1-14″ acquired by the local end user device 1-30″ may indicate, in various implementations, at least a first one or more reported aspects that may be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16″, and a second one or more reported aspects that may not be relevant to the achievement of the one or more target outcomes. The local end user device 1-30″ may be further designed to develop a personalized plan 1-16″ by at least determining which of the reported aspects associated with the source user 1-2″ may be relevant to the achievement of the one or more target outcomes. For example, the local end user device 1-30″ may be designed to filter the source user data 1-14″ to determine or distinguish those reported aspects (e.g., first one or more reported aspects) that are relevant to the achievement of the one or more target outcomes from those reported aspects (e.g., second one or more reported aspects) that are not relevant to the achievement of the one or more target outcomes. In various implementations, the local end user device 1-30″ may be further designed to present the developed personalized plan 1-16″ to the end user 1-4″ (e.g., via the user interface 1-120″), to one or more third parties 1-6″ (e.g., via wireless network and/or wired network 1-50″), and/or to a server 1-10″ (e.g., via wireless network and/or wired network 1-50″).
  • In various implementations, the local end user device 1-30″ may include the same or similar modules, sub-modules, and components included in the local source user device 1-20′ of FIG. 1-1 d. For example, the local end user device 1-30″ may include a request reception module 1-102″, a source user data acquisition module 1-104″ (which may further include a request transmission module 1-204″ and a source user data reception module 1-206″), a personalized plan development module 1-106″, a presentation module 1-108″ (which may further include a transmission module 1-228″ and a user interface indication module 1-229″), a memory 1-116″ (which may store source user data 1-14″ and/or one or more applications 1-140″), a user interface 1-120″, and/or a network interface 1-118″, similar to the local source user device 1-20′ of FIG. 1-1 d. Also similar to the local source user device 1-20′ of FIG. 1-1 d, the local end user device 1-30″ may also include a social networking entry reception module 1-110″ (which may further include a blog entry reception module 1-111″ and/or a status report reception module 1-112″), a diary entry reception module 1-114″, and/or a sensor data reception module 1-115″. All of these modules, sub-modules, and components of the local end user device 1-30″ may perform the same or similar functions as their counterparts that may be included in the local source user device 1-20′ of FIG. 1-1 d. In addition to these modules, sub-modules, and components, the local end user device 1-30″ may include a user interface reception module 1-203″ (which may be included in the request reception module 1-102″) for receiving the request 1-12″ via a user interface 1-120″. The user interface 1-120″ may include one or more of, for example, a display monitor, a touchscreen, a keyboard, a keypad, a mouse, an audio system including one or more speakers, a microphone, an image capturing device such as a digital camera, and so forth.
  • FIG. 1-2 illustrates the personalized plan development module 1-106* (e.g., personalized plan development module 1-106, personalized plan development module 1-106′, and personalized plan development module 1-106″) of FIGS. 1-1 b, 1-1 d, and 1-1 f. As illustrated, the personalized plan development module 1-106* may include a relevant reported aspect determination module 1-208* that is configured to, among other things, determine which of a plurality of reported aspects associated with a source user 1-2*, as indicated by source user data 1-14*, are relevant to the achievement of one or more target outcomes of a personalized plan 1-16*. In various implementations, the relevant reported aspect determination module 1-208* may be further configured to, among other things, determine which of the plurality of the reported aspects, as indicated by the source user data 1-14*, occurred within a predefined time period from occurrence of one or more reported outcomes associated with the source user 1-2* that corresponds to the one or more target outcomes of the personalized plan 1-16*. In the same or different implementations, the relevant reported aspect determination module 1-208* may be configured to determine which of the reported aspects as indicated by the source user data 1-14* are relevant to the achievement of the one or more target outcomes based, at least in part, on indications provided by the source user 1-2*, by the end user 1-4*, and/or by one or more third party sources.
  • The relevant reported aspect determination module 1-208* may further include one or more sub-modules in various alternative implementations. For example, in various implementations, the relevant reported aspect determination module 1-208* may include one or more of a reported aspect relevancy requesting module 1-212*, a reported aspect non-relevancy requesting module 1-214*, an aspect type relevancy requesting module 1-216*, an aspect type non-relevancy requesting module 1-218*, a relevancy reception module 1-220*, and/or a non-relevancy reception module 1-221*. In brief, the reported aspect relevancy requesting module 1-212* may be configured to, among other things, request the source user 1-2* or the end user 1-4* to provide one or more indications of which of the reported aspects (as indicated by the source user data 1-14*) are relevant to the achievement of one or more reported outcomes (as may be indicated by the source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*.
  • In contrast, the reported aspect non-relevancy requesting module 1-214 may be configured to, among other things, request the source user 1-2* or the end user 1-4* to provide one or more indications of which of the reported aspects (as indicated by source user data 1-14*) are not relevant to the achievement of one or more reported outcomes (as may be indicated by the source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*. The aspect type relevancy requesting module 1-216* may be configured to, among other things, request the end user 1-4* or the source user 1-2* to provide one or more indications of what types of aspects are relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*. In contrast, the aspect type non-relevancy requesting module 1-218* may be configured to, among other things, request the end user 1-4* or the source user 1-2* to provide one or more indications of what types of aspects are relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • The relevancy reception module 1-220* may be configured to receive (e.g., receive from a source user 1-2*, an end user 1-4*, or one or more third parties 1-6*) indications as to which reported aspects or which types of reported aspects are relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*. In contrast, the non-relevancy reception module 1-221* may be configured to receive (e.g., receive from a source user 1-2*, an end user 1-4*, or one or more third parties 1-6*) indications as to which reported aspects or which types of reported aspects are not relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In various alternative implementations, the personalized plan development module 1-106* may further include one or more of an emulatable aspect inclusion module 1-222*, an intermediate outcome inclusion module 1-224*, a relationship defining module 1-226*, and/or a plausible emulatable aspect inclusion module 1-228*. The emulatable aspect inclusion module 1-222* may be configured to, among other things, facilitate the development of the personalized plan 1-16* by including into the personalized plan 1-16 at least one emulatable aspect that corresponds to at least one reported aspect associated with the source user 1-2* that is determined to be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*. The intermediate outcome inclusion module 1-224* may be configured to, among other things, facilitate the development of the personalized plan 1-16* by including into the personalized plan 1-16* at least one intermediate outcome that corresponds to one or more reported intermediate outcomes as indicated by the source user data 1-14*. The relationship defining module 1-226* may be configured to, among other things, facilitate the development of the personalized plan 1-16* by defining in the personalized plan 1-16* a relationship or relationships (e.g., temporal, specific time, or spatial relationships) between a plurality of emulatable aspects that may be included in the personalized plan 1-16*. The plausible emulatable aspect inclusion module 1-228 may be configured to, among other things, facilitate the development of the personalized plan 1-16* by including into the personalized plan 1-16* at least one plausible emulatable aspect, the at least one plausible emulatable aspect being at least one emulatable aspect that has been successfully emulated by one or more other end users (e.g., one or more third parties 1-6*).
  • A more detailed discussion related to the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, and the local end user device 1-30″ of FIG. 1-1 f will now be provided with respect to the processes and operations to be described herein.
  • FIG. 1-3 illustrates an operational flow 1-300 representing example operations related to, among other things, development of a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes by at least determining which of a plurality of reported aspects associated with a source user 1-2* are relevant to the achievement of the one or more target outcomes. In some embodiments, the operational flow 1-300 may be executed by, for example, the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f.
  • In FIG. 1-3 and in the following figures that include various examples of operational flows, discussions and explanations may be provided with respect to the three exemplary environments described above as illustrated in FIGS. 1-1 a and 1-1 b, FIGS. 1-1 e and 1-1 d, and FIGS. 1-1 e and 1-1 f, and/or with respect to other examples (e.g., as provided in FIG. 1-2) and contexts. However, it should be understood that the operational flows may be executed in a number of other environments and contexts, and/or in modified versions of FIGS. 1-1 a to 1-1 f, and 1-2. Also, although the various operational flows are presented in the sequence(s) illustrated, it should be understood that the various operations may be performed in other orders than those which are illustrated, or may be performed concurrently.
  • Further, in FIG. 1-3 and in following figures, various operations may be depicted in a box-within-a-box manner. Such depictions may indicate that an operation in an internal box may comprise an optional example embodiment of the operational step illustrated in one or more external boxes. However, it should be understood that internal box operations may be viewed as independent operations separate from any associated external boxes and may be performed in any sequence with respect to all other illustrated operations, or may be performed concurrently.
  • In any event, after a start operation, the operational flow 1-300 may move to a reception operation 1-302 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least a source user. For instance, and as an illustration, the request reception module 1-102*(e.g., the request reception module 1-102, the request reception module 1-102′, or the request reception module 1-102″) of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12*(e.g., via a wireless network and/or wired network 1-50* or via a user interface 1-120*) for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes (e.g., weight loss, development or improvement of user skills such as work skills, athletic or game skills, or social skills, developing or having particular subjective user states such as well-rested and/or well-being, and so forth) when one or more emulatable aspects (e.g., one or more behaviors, one or more acts, one or more beliefs, one or more traits, and/or other types of characteristics or traits) indicated by the personalized plan 1-16* are emulated, the request identifying at least a source user 1-2*. Note that in various implementations the request 1-12* does not need to specify the one or more target outcomes associated with the requested personalized plan 1-16*. Instead, the request 1-12* may merely identify a particular source user 1-2*. The identification of the source user 1-2* in the request 1-12* may be made by various means including, for example, by actual name (e.g., “John Doe”), by a user name (e.g., “jdoe”), by a facial image of the source user, by RFID identification, by voice identification, by location identification, by title identification, and so forth.
  • Operational flow 1-300 may also include an acquisition operation 1-304 for acquiring source user data indicating a plurality of reported aspects associated with at least the source user in response to receiving the request. For instance, and as an illustration, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, of the local source user device 1-20′ of FIG. 1-1 d, or of the local end user device 1-30″ of FIG. 1-1 f acquiring (e.g., acquiring from a memory 1-116* and/or from a wireless network and/or wired network 1-50*) source user data 1-14* indicating a plurality of reported aspects (e.g., reported acts, behavior, beliefs, and so forth) associated with at least the source user 1-2* in response to receiving the request 1-12*.
  • Finally, operational flow 1-300 may include a development operation 1-306 for developing the personalized plan by at least determining which of the plurality of reported aspects associated with the source user are relevant to the achievement of the one or more target outcomes. For instance, and as an illustration, the personalized plan development module 1-106* including the relevant reported aspect determination module 1-208* of the server 1-10 of FIG. 1-1 b, of the local source user device 1-20′ of FIG. 1-1 d, or of the local end user device 1-30″ of FIG. 1-1 f developing (e.g., creating) the personalized plan 1-16* by having the relevant reported aspect determination module 1-208* at least determining which of the plurality of reported aspects associated with the source user 1-2* are relevant to the achievement of the one or more target outcomes.
  • In various implementations, the reception operation 1-302 of FIG. 1-3 may be performed in various alternative ways as illustrated in FIGS. 1-4 a, 1-4 b, 1-4 c, 1-4 d, and 1-4 e. For example, the request 1-12* received through the reception operation 1-302 may be received by various means depending upon, for example, whether the operation is being implemented at a server 1-10 (e.g., as in the embodiment depicted in FIGS. 1-1 a and 1-1 b), at a local source user device 1-20′ (e.g., as in the embodiment depicted in FIGS. 1-1 c and 1-1 d), or at a local end user device 1-30″ (e.g., as in the embodiment depicted in FIGS. 1-1 e and 1-1 f). For example, in some implementations the reception operation 1-302 may include an operation 1-402 for receiving the request via a user interface as depicted in FIG. 1-4 a. For instance, the user interface reception module 1-203″ of the local end user device 1-30″ receiving the request 1-12″ via a user interface 1-120″ (e.g., an audio system including a microphone, a keypad, a touchscreen, a mouse, and so forth).
  • In some alternative implementations, however, the reception operation 1-302 may include an operation 1-403 for receiving the request via at least one of a wireless network and a wired network as depicted in FIG. 1-4 a. For instance, the network interface reception module 1-202*(e.g., network interface reception module 1-202 or network interface reception module 1-202′) of the server 1-10 of FIG. 1-1 b or the local source user device 1-20′ of FIG. 1-1 d receiving the request 1-12*(e.g., request 1-12 or request 1-12′) via at least one of wireless network and a wired network 1-50*.
  • Various types of personalized plan 1-16* may be requested via the reception operation 1-302 of FIG. 1-3 in various alternative implementations. For example, in some implementations, the reception operation 1-302 may include an operation 1-404 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more outcomes related to athletics as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more outcomes related to athletics (e.g., an athletic skill or result such as being able to pitch a curve ball or running a mile under 6 minutes) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated. Note again that in various alternative implementations, the request 1-12* may not specifically identify the one or more outcomes, but instead, may merely identify a source user 1-2*.
  • In some implementations, the reception operation 1-302 may include an operation 1-405 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more outcomes relating to games as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more outcomes related to games (e.g., a gaming skill or result relating to playing chess or a video/electronic game) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-406 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more work related outcomes as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more work-related outcomes (e.g., obtaining a promotion, work related skills such as computer skills, interpersonal skills, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-407 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more social related outcomes as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more social related outcomes (e.g., having many friends, participating in many social activities, interpersonal skills such as public speaking, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-408 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more leisure related outcomes as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more leisure related outcomes (e.g., going on a vacation or being available to take a vacation, having or setting aside time to read a novel, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-409 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more health or medical related outcomes as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more health or medical related outcomes (e.g., reducing blood pressure or blood glucose levels, weight loss, increase red blood cell count, improve recovery from an illness such as cancer, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-410 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more sexual intimacy outcomes as depicted in FIG. 1-4 a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more sexual intimacy outcomes (e.g., increased sexual activities, increased sexual performance, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-411 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more psychological related outcomes as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more psychological related outcomes (e.g., easing of a phobia, hostile feeling towards a person or a group, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-412 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more subjective user states as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more subjective user states when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated. A subjective user state may be any user state that may generally only be subjectively indicated by a user. The requested personalized plan 1-16* may be designed to facilitate an end user 1-4* to achieve various types of subjective user states.
  • For example, in some implementations, operation 1-412 may further include an operation 1-413 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more subjective user mental states as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more subjective user mental states (e.g., happiness, calmness, alertness, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, operation 1-412 may include an operation 1-414 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more subjective user physical states as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more subjective user physical states (e.g., feeling energized, being pain-free, being able to see and/or hear well, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, operation 1-412 may include an operation 1-415 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more subjective user overall states as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more subjective user overall states (e.g., “good,” “bad,” “well,” “available,” “busy,” and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-416 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more user social states as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more social states (e.g., being available for marriage, belonging to a higher social class, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In some implementations, the reception operation 1-302 may include an operation 1-417 for receiving a request for a personalized plan designed to facilitate an end user to achieve one or more user employment states as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving a request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more user employment states (e.g., being employed, having or obtaining an employment position such as a management position, having or developing a particular reputation at work, and so forth) when, for example, one or more emulatable aspects of the personalized plan 1-16* are emulated.
  • In order to identify the source user 1-2*, in some implementations, the request 1-12* received through the reception operation 1-302 of FIG. 1-3 may include an identifier for the source user 1-2*. For example, in some implementations, the reception operation 1-302 may include an operation 1-418 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request including an identifier associated with at least the source user as depicted in FIG. 1-4 b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for the personalized plan 1-16* designed to facilitate the end user 1-4* to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* including an identifier (e.g., an “actual” name, a user name, a title or position such as CEO or administrative assistant, accomplishment such as “winner,” class such as professional football player, an image of the source user's face, an RFID identity, an avatar identity, voice recognition identification, retinal scan identification, digital fingerprint identification, credit card, social security number, and so forth) associated with at least the source user 1-2*.
  • In some cases, the request 1-12* received through the reception operation 1-302 of FIG. 1-3 may identify at least one of the target outcomes of the personalized plan 1-16*. For example, in some implementations, the reception operation 1-302 may include an operation 1-419 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least one of the one or more target outcomes as depicted in FIG. 1-4 c. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for the personalized plan 1-16* designed to facilitate the end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* identifying at least one of the one or more target outcomes.
  • In some cases, operation 1-419 may further include an operation 1-420 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request including an identifier associated with at least one of the one or more target outcomes as depicted in FIG. 1-4 c. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for the personalized plan 1-16* designed to facilitate the end user 1-4* to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* including an identifier (e.g., a description, a name, a symbolic representation, an image of the outcome as physically displayed by, for example, the source user 1-2* or a third party 1-6*, and so forth) associated with at least one of the one or more target outcomes.
  • The request 1-12* received through the reception operation 1-302 of FIG. 1-3 may indicate other types of information in various alternative implementations. For example, in some implementations, operation 1-302 may include an operation 1-421 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more preferences of the end user as depicted in FIG. 1-4 c. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more preferences (e.g., prefer not to jog, prefer not to wake-up early, prefer not to consume certain items, and so forth) of the end user 1-4*.
  • In some implementations, the reception operation 1-302 may include an operation 1-322 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more limitations associated with the end user as depicted by FIG. 1-4 d. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more limitations (e.g., physical or mental handicaps, scheduling limitations, logistical limitations, and so forth) associated with the end user 1-4*.
  • Operation 1-422, in turn, may further include an operation 1-423 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more physical limitations associated with the end user as depicted in FIG. 1-4 d. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more physical limitations (e.g., visual or hearing limitations, physical movement limitations such as those related to a paraplegic, physical characteristic limitations such as height, weight, and so forth, related to the end user 1-4*, physiological limitations such as cholesterol levels, and so forth) associated with the end user 1-4*.
  • In the same or different implementations, operation 1-422 may include an operation 1-424 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more contextual limitations associated with the end user as depicted in FIG. 1-4 d. For instance, the request reception module 1-102* of the server 1-10 (of FIG. 1-1 b), the local source user device 1-20′ (of FIG. 1-1 d), or the local end user device 1-30″ (of FIG. 1-1 f) receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more contextual limitations (e.g., scheduling limitations, geographical limitations, asset limitations such as lack of particular equipment or facilities, and so forth) associated with the end user 1-4*.
  • In the same or different implementations, operation 1-422 may include an operation 1-425 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more personal limitations associated with the end user as depicted in FIG. 1-4 d. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more personal limitations (e.g., religious beliefs, dietary beliefs, phobias, personal prejudices, limitations related to personal experiences, personal work schedule, family dynamics or circumstances, and so forth) associated with the end user 1-4*.
  • In the same or different implementations, operation 1-422 may include an operation 1-426 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more medical or health limitations associated with the end user as depicted in FIG. 1-4 e. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more medical or health limitations (e.g., medical limitations as limitations resulting from an illness or treatment of the illness including physical limitations due to cancer or treatment thereof, health limitations related to the physical conditioning of the end user 1-4*, genetic limitations, and so forth) associated with the end user 1-4*.
  • In the same or different implementations, operation 1-422 may include an operation 1-427 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more user state limitations associated with the end user as depicted in FIG. 1-4 e. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more user state limitations (e.g., end user 1-4* is married, end user 1-4* is in mourning, end user 1-4* is unemployed, end user 1-4* is a vegan, and so forth) associated with the end user 1-4*.
  • In the same or different implementations, operation 1-422 may include an operation 1-428 for receiving the request for the personalized plan designed to facilitate the end user to achieve the one or more target outcomes when the one or more emulatable aspects indicated by the personalized plan are emulated, the request indicating one or more legal or regulatory limitations associated with the end user as depicted in FIG. 1-4 e. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f receiving the request 1-12* for a personalized plan 1-16* designed to facilitate an end user 1-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 1-16* are emulated, the request 1-12* indicating one or more legal or regulatory limitations (e.g., drug regulations, laws related to conduct, and so forth) associated with the end user 1-4*. Note that the legal or regulatory limitations between where the source user 1-2* resides and where the end user 1-4* resides may differ, and therefore, such information may be useful in developing a personalized plan 1-16*.
  • Referring back to FIG. 1-3, the acquisition operation 1-304 may be executed in a variety of different manners in various alternative implementations. For instance, the source user data 1-14* acquired through the acquisition operation 1-304 may be acquired from different sources and/or may have at least originated from different sources. For example, in some implementations, the acquisition operation 1-304 may include an operation 1-529 for acquiring at least a portion of the source user data from a remote network device as depicted in FIG. 1-5 a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20 ′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring at least a portion of the source user data 1-14*(e.g., log data such as social networking entry data or diary data) from a remote network device (e.g., in embodiments in which operational flow 1-300 is implemented at a server 1-10 as depicted in FIGS. 1-1 a and 1-1 b, at least a portion of the source user data 1-14 may be acquired from a local source user device 1-20, from one or more third party devices such as other source user devices, and/or from one or more sensors 1-40).
  • In some implementations, operation 1-529 may, in turn, include an operation 1-530 for transmitting a request to the remote network device for the at least a portion of the source user data, the request identifying at least the source user as depicted in FIG. 1-5 a. For instance, the request transmission module 1-204* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f transmitting (e.g., via wireless network and/or wired network 1-50) a request to the remote network device for the at least a portion of the source user data 1-14*, the request identifying at least the source user 1-2*. For example, in embodiments in which the operational flow 1-300 is being executed at a local end user device 1-30″ (e.g., FIGS. 1-1 e and 1-1 f), the request transmission module 1-204″ of the local end user device 1-30″ may transmit to the server 1-10″, the local source user device 1-20″, and/or one or more sensors 1-40″ a request for at least a portion of the source user data 1-14″, the request identifying at least the source user 1-2″. In various implementations, the source user data reception module 1-206* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f may then receive the requested source user data 1-14*.
  • In the same or different implementations, operation 1-529 may include an operation 1-531 for transmitting a request to the remote network device for the at least a portion of the source user data, the request identifying at least one of the one or more target outcomes as depicted in FIG. 1-5 a. For instance, the request transmission module 1-204* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f transmitting (e.g., via wireless network and/or wired network 1-50) a request to the remote network device for the at least a portion of the source user data 1-14*, the request identifying at least one of the one or more target outcomes. For example, in embodiments in which the operational flow 1-300 is being executed at a local source user device 1-20′ (e.g., FIGS. 1-1 c and 1-1 d), the request transmission module 1-204′ of the local source user device 1-20′ may transmit to the server 1-10′ and/or one or more sensors 1-40′ a request for at least a portion of the source user data 1-14″, the request identifying at least one of the one or more target outcomes of the personalized plan 1-16′.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-532 for acquiring at least a portion of the source user data from a memory as depicted in FIG. 1-5 a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b or the local source user device 1-20′ of FIG. 1-1 d acquiring at least a portion of the source user data 1-14* from a memory 1-116*(e.g., flash memory, volatile memory, non-volatile memory, cache memory, and so forth).
  • In some implementations, the acquisition operation 1-304 may include an operation 1-533 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported by the source user as depicted in FIG. 1-5 a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data indicating one or more reported aspects as at least originally reported by the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-534 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported by one or more sensors as depicted in FIG. 1-5 a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data indicating one or more reported aspects as at least originally reported by one or more sensors 1-40*(e.g., physiological sensing devices such as blood pressure or blood glucose sensors, sensors to sense activities of a subject such as pedometers, GPSs, exercise machine sensors, and accelerometers, sensors to measure environmental conditions such as thermometers or air quality sensors, and so forth).
  • In some implementations, the acquisition operation 1-304 may include an operation 1-535 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported by one or more third parties as depicted in FIG. 1-5 a. For instance, the source user data acquisition module 1-104* of the server 1-10 (of FIG. 1-1 b), the local source user device 1-20′ (of FIG. 1-1 d), or the local end user device 1-30″ (of FIG. 1-1 f) acquiring the source user data 1-14* including data indicating one or more reported aspects as at least originally reported by one or more third parties 1-6*(e.g., other end users, spouses, friends, employers, and so forth).
  • In some implementations, the acquisition operation 1-304 may include an operation 1-536 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported via one or more social networking entries as depicted in FIG. 1-5 b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data (e.g., log data) indicating one or more reported aspects as at least originally reported via one or more social networking entries.
  • In various implementations, operation 1-536 may further include an operation 1-537 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported via one or more blog entries as depicted in FIG. 1-5 b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data (e.g., log data) indicating one or more reported aspects as at least originally reported via one or more blog (e.g., microblog) entries (e.g., as entered by the source user 1-2* or by a third party 1-6*).
  • In some implementations, operation 1-536 may further include an operation 1-538 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported via one or more status reports as depicted in FIG. 1-5 b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data (e.g., log data) indicating one or more reported aspects as at least originally reported via one or more status reports (e.g., as reported by the source user 1-2* or by a third party 1-6*).
  • In various implementations, the acquisition operation 1-304 may include an operation 1-539 for acquiring the source user data including data indicating one or more reported aspects as at least originally reported via one or more diary entries as depicted in FIG. 1-5 b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data (e.g., log data) indicating one or more reported aspects as at least originally reported via one or more diary entries (e.g., as entered by the source user 1-2* or by a third party 1-6*). Note that in some cases, diary entries may also include data provided by one or more sensors 1-40*.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-540 for acquiring the source user data including log data indicating one or more reported factual aspects associated with at least the source user in response to receiving the request as depicted in FIG. 1-5 b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including log data indicating one or more reported factual aspects (e.g., rather than fictional or imaginary aspects) associated with at least the source user 1-2* in response to receiving the request 1-12*.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-541 for acquiring the source user data including data indicating one or more reported fictional or fabricated aspects associated with at least the source user in response to receiving the request as depicted in FIG. 1-5 b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* including data indicating one or more reported fictional or fabricated aspects associated with at least the source user 1-2* in response to receiving the request 1-12*.
  • Various types of reported aspects associated with a source user 1-2* may be indicated by the source user data 1-14* acquired through the acquisition operation 1-304 of FIG. 1-3. For example, in some implementations, the acquisition operation 1-304 may include an operation 1-542 for acquiring the source user data indicating the plurality of reported aspects including one or more user behavior incidences associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more user behavior incidences (e.g., dietary behavior, exercise or athletic behavior, social behavior, work behavior, sexual behavior, and so forth) associated with the source user 1-2*.
  • Operation 1-542, in turn, may include one or more additional operations in various alternative implementations. For example, in some implementations, operation 1-542 may include an operation 1-543 for acquiring the source user data indicating the plurality of reported aspects including one or more acts that were executed by the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more acts (e.g., exercising, eating, driving, sleeping, waking-up early, reading, studying, and so forth) that were executed by the source user 1-2*.
  • In the same or different implementations, operation 1-542 may include an operation 1-544 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of user attitudes associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of user attitudes (e.g., anger, happiness, skeptical, alert, hostile, accepting, indifference, and so forth) associated with the source user 1-2*.
  • In the same or different implementations, operation 1-542 may include an operation 1-545 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of user conduct associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 (of FIG. 1-1 b), the local source user device 1-20′ (of FIG. 1-1 d), or the local end user device 1-30″ (of FIG. 1-1 f) acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of user conduct (e.g., how a source user 1-2* interacts with others, how a source user 1-2* reacts to external events, and so forth) associated with the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-546 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of belief or beliefs associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of belief or beliefs (e.g., religious beliefs, spiritual beliefs, dietary beliefs, and so forth) associated with the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-547 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of subjective user states associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of subjective user states (e.g., “rested,” “well,” “alert,” “occupied,” “relaxed,” and so forth) associated with the source user 1-2*. For these implementations, incidences of various types of subjective user states may be indicated by the acquired source user data 1-14*.
  • For example, in some implementations, operation 1-547 may include an operation 1-548 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of subjective mental states associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of subjective mental states (e.g., happy, relaxed, calm, awake or alert, and so forth) associated with the source user 1-2*.
  • In the same or different implementations, operation 1-547 may include an operation 1-549 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of subjective physical states associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of subjective physical states (e.g., being fit, having endurance, being pain free, and so forth) associated with the source user 1-2*.
  • In the same or different implementations, operation 1-547 may include an operation 1-550 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of subjective overall user states associated with the source user as depicted in FIG. 1-5 c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of subjective overall user states (e.g., “good,” “well,” “available,” and so forth) associated with the source user 1-2*.
  • Incidences of other types of aspects associated with a source user 1-2* may also be indicated by the source user data 1-14* acquired through the acquisition operation 1-304 in various alternative implementations. For example, in some implementations, the acquisition operation 1-304 may include an operation 1-551 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of user physical characteristics associated with the source user as depicted in FIG. 1-5 d. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of user physical characteristics (e.g., hair color, hair length, weight loss, nail color or length, and so forth) associated with the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-552 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of user locations associated with the source user as depicted in FIG. 1-5 d. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of user locations (e.g., home, workplace, Hawaii, the gym, and so forth) associated with the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 may include an operation 1-553 for acquiring the source user data indicating the plurality of reported aspects including one or more incidences of external events associated with the source user as depicted in FIG. 1-5 d. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported aspects including one or more incidences of external events (e.g., weather, drinking water quality, work environment, and so forth) associated with the source user 1-2*.
  • In addition to acquiring source user data that indicates a plurality of reported aspects associated with a source user 1-2*, the acquisition operation 1-304 of FIG. 1-3 may involve the acquisition of source user data that indicates other types of events. For example, in some implementations, the acquisition operation 1-304 may include an operation 1-554 for acquiring source user data indicating one or more reported outcomes associated with the source user as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes (e.g., at least one intermediate outcome related to the final or target outcome) associated with the source user 1-2*.
  • Note that a “reported outcome” may be viewed, in some cases, as merely one type of reported aspect associated with a source user 1-2*. For example, the weight loss of a source user 1-2* at different points in time may represent reported outcomes but may also be considered reported aspects associated with the source user 1-2* in some cases. For these cases, the distinction with respect to a reported outcome as opposed to, for example, other types of reported aspects are that a reported outcome may be the result of or is dependent on the occurrence of other reported aspects, while other types of reported aspects may not be dependent on the occurrence of other reported aspects.
  • In various implementations, operation 1-554 may include one or more operations. For example, in some implementations, operation 1-554 may include an operation 1-555 for acquiring source user data indicating a plurality of reported outcomes associated with the source user as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating a plurality of reported outcomes (e.g., blood pressure levels or bowling scores over the course of several months) associated with the source user 1-2*.
  • In some implementations, operation 1-555 may further include an operation 1-556 for acquiring the source user data indicating the plurality of reported outcomes associated with the source user, at least a first one of the reported outcomes indicated by the source user data being a reported outcome that occurred during a first point or interval of time and at least a second one of the reported outcomes being a reported outcome that occurred during a second point or interval of time, the second point or interval of time being a later point or interval of time than the first point or interval of time as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring the source user data 1-14* indicating the plurality of reported outcomes associated with the source user 1-2*, at least a first one of the reported outcomes (e.g., a bowling average of 98) indicated by the source user data 1-14* being a reported outcome that occurred during a first point or interval of time and at least a second one of the reported outcomes (e.g., a bowling average of 156) being a reported outcome that occurred during a second point or interval of time, the second point or interval of time (e.g., May 9, 2011) being a later point or interval of time than the first point or interval of time (e.g., Mar. 2, 2011).
  • Operation 1-556, in turn, may further include an operation 1-557 for acquiring the source user data indicating the plurality of reported outcomes associated with the source user, at least the first one of the reported outcomes and the second one of the reported outcomes being related outcomes as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating the plurality of reported outcomes associated with the source user 1-2*, at least the first one of the reported outcomes and the second one of the reported outcomes being related outcomes (e.g., same types of outcomes such as outcomes related to weight loss, outcomes related to a particular work skill such as word processing skills, outcomes related to a particular interpersonal skill such as developing new friendships, and so forth).
  • In various implementations, the operation 1-554 for acquiring source user data indicating one or more reported outcomes associated with the source user, may further include an operation 1-558 for acquiring source user data indicating one or more reported outcomes associated with the source user that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes (e.g., a final reported outcome such as weight loss) associated with the source user 1-2* that corresponds to the one or more target outcomes (e.g., a target weight loss) of the personalized plan 1-16*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-559 for acquiring source user data indicating one or more reported outcomes including one or more reported physical characteristics of the source user as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported physical characteristics (e.g., weight, hair color, physiological characteristic such as hormone level or heart rate at rest, skin tone, hearing characteristic, vision characteristic, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-560 for acquiring source user data indicating one or more reported outcomes including one or more reported medical or health characteristics of the source user as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported medical or health characteristics (e.g., reduction in tumor size, absence of a malignant tumor, improved cardiovascular performance, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-561 for acquiring source user data indicating one or more reported outcomes including one or more reported traits of the source user as depicted in FIG. 1-5 e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported traits (e.g., mannerisms, alertness, affect, charisma, demeanor, style, number of friends, wealth, happiness, sadness, order in life, organization, control, well being, spirituality, improved communication, better personal or professional relationships, better anger management, better cognitive skills, improved vocabulary, improved problem solving skills, improved coping mechanisms, better math skills, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-562 for acquiring source user data indicating one or more reported outcomes including one or more reported statuses of the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported statuses (e.g., availability, wellness, employment, marital, physical or mental states, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-563 for acquiring source user data indicating one or more reported outcomes including one or more reported athletic outcomes or skills of the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported athletic outcomes or skills (e.g., reducing golf handicap, swimming one mile, developing a curveball patch, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-564 for acquiring source user data indicating one or more reported outcomes including one or more reported gaming outcomes or skills of the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported gaming outcomes or skills (e.g., chess playing results, video/electronic gaming skills, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-565 for acquiring source user data indicating one or more reported outcomes including one or more reported work outcomes or skills of the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported work outcomes or skills (e.g., successful completion of a project, computer skills, managerial skills, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-566 for acquiring source user data indicating one or more reported outcomes including one or more reported leisure outcomes or skills of the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported leisure outcomes or skills (e.g., having lots of friends, going away on a vacation, having extra time to spend with children, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-567 for acquiring source user data indicating one or more reported outcomes including one or more reported intellectual or academic outcomes or skills of the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported intellectual or academic outcomes or skills (e.g., achieving a certain grade point average or score on a test, increased IQ, comprehension of technically complex subject, and so forth) of the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-568 for acquiring source user data indicating one or more reported outcomes including one or more reported sexual intimacy outcomes associated with the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported sexual intimacy outcomes (e.g., number of or quality of sexual encounters) associated with the source user 1-2*.
  • In some implementations, the acquisition operation 1-304 of FIG. 1-3 may include an operation 1-569 for acquiring source user data indicating one or more reported outcomes including one or more reported external outcomes associated with the source user as depicted in FIG. 1-5 f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f acquiring source user data 1-14* indicating one or more reported outcomes including one or more reported external outcomes (e.g., subordinates' work production, behavior of others towards the source user 1-2*, and so forth) associated with the source user 1-2*.
  • Referring back to the development operation 1-306 of FIG. 1-3, in various implementations, the development operation 1-306 may be implemented in a variety of different ways. For example, in some implementations, the development operation 1-306 may include an operation 1-670 for developing the personalized plan by at least determining which of the plurality of reported aspects occurred within a predefined time period from occurrence of one or more reported outcomes associated with the source user that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 a. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* based on the relevant reported aspect determination module 1-208* at least determining which of the plurality of reported aspects (e.g., as indicated by the source user data 1-14*) occurred within a predefined time period from occurrence of one or more reported outcomes (e.g., weight loss of 20 pounds) associated with the source user 1-2*(e.g., as indicated by the source user data 1-14*) that corresponds to the one or more target outcomes (e.g., weight loss 20 pounds) of the personalized plan 1-16*.
  • Operation 1-670 may, in certain implementations, include an operation 1-671 for developing the personalized plan by at least determining which of the plurality of reported aspects occurred within a predefined time period and preceded occurrence of the one or more reported outcomes associated with the source user that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 a. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* based on the relevant reported aspect determination module 1-208*at least determining which of the plurality of reported aspects (e.g., as indicated by the source user data 1-14*) occurred within a predefined time period and preceded occurrence of the one or more reported outcomes associated with the source user 1-2*(e.g., as indicated by the source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*.
  • In some implementations, the development operation 1-306 of FIG. 1-3 may include an operation 1-672 for developing the personalized plan by at least determining which of the plurality of reported aspects are relevant to the achievement of the one or more target outcomes based on one or more indications provided by the source user as depicted in FIG. 1-6 a. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* based on the relevant reported aspect determination module 1-208* at least determining which of the plurality of reported aspects (e.g., as indicated by the source user data 1-14*) are relevant to the achievement of the one or more target outcomes based on one or more indications provided by the source user 1-2*. In other words, the source user 1-2* may provide an indication as to which of the reported aspects may be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In some cases, operation 1-672 may further include one or more additional operations. For example, in some implementations, operation 1-672 may include an operation 1-673 for requesting the source user to provide one or more indications of which of the reported aspects are relevant to achievement of one or more reported outcomes that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 a. For example, the reported aspect relevancy requesting module 1-212* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f requesting the source user 1-2*(e.g., transmitting a request 1-12* via a wireless network and/or wired network 1-50* or indicating a request 1-12* via a user interface 1-120′) to provide one or more indications of which of the reported aspects (e.g., as indicated by the acquired source user data 1-14*) are relevant to achievement of one or more reported outcomes (e.g., as indicated by, for example, the acquired source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*. For these implementations, the source user 1-2* may be requested to merely indicate what type or types of reported aspects (e.g., reduced carbohydrate intake) may be relevant to the achievement of the one or more reported outcomes (e.g., weight loss of 30 pounds).
  • In some implementations, operation 1-672 may include an operation 1-674 for requesting the source user to provide one or more indications of which of the reported aspects are not relevant to achievement of one or more reported outcomes that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 a. For instance, the reported aspect non-relevancy requesting module 1-214* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f requesting the source user 1-2*(e.g., transmitting a request 1-12* via a wireless network and/or wired network 1-50* or indicating a request 1-12* via a user interface 1-120′) to provide one or more indications of which of the reported aspects (e.g., as indicated by the acquired source user data 1-14*) are not relevant to achievement of one or more reported outcomes (e.g., as indicated by the acquired source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*. For these implementations, the source user 1-2* may be requested to merely indicate what type or types of reported aspects (e.g., getting 8 hours of sleep) may not be relevant to the achievement of the one or more reported outcomes (e.g., weight loss of 30 pounds).
  • In various implementations, the development of a personalized plan 1-16* through the development operation 1-306 of FIG. 1-3 may be based, at least in part, on input provided by an end user 1-4*. For example, the development operation 1-306 in various implementations may include an operation 1-675 for developing the personalized plan by at least determining which of the plurality of reported aspects are relevant to the achievement of the one or more target outcomes based on one or more indications provided by the end user as depicted in FIG. 1-6 b. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* as a result of the relevant reported aspect determination module 1-208*at least determining which of the plurality of reported aspects (e.g., as indicated by the acquired source user data 1-14*) are relevant to the achievement of the one or more target outcomes based on one or more indications provided by the end user 1-4*.
  • In various alternative implementations, operation 1-675 may further include one or more additional operations. For example, in some implementations, operation 1-675 may include an operation 1-676 for requesting the end user to provide one or more indications of which of the reported aspects are relevant to achievement of one or more reported outcomes that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 b. For example, the reported aspect relevancy requesting module 1-212* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f requesting the end user 1-4*(e.g., transmitting a request 1-12* via a wireless network and/or wired network 1-50* or indicating a request 1-12* via a user interface 1-120″) to provide one or more indications of which of the reported aspects (e.g., as indicated by the acquired source user data 1-14*) are relevant to achievement of one or more reported outcomes (e.g., as indicated by, for example, the acquired source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*.
  • In some implementations, operation 1-675 may include an operation 1-677 for requesting the end user to provide one or more indications of which of the reported aspects are not relevant to achievement of one or more reported outcomes that corresponds to the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 b. For instance, the reported aspect non-relevancy requesting module 1-214* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f requesting the end user 1-4*(e.g., transmitting a request 1-12* via a wireless network and/or wired network 1-50* or indicating a request 1-12* via a user interface 1-120″) to provide one or more indications of which of the reported aspects (e.g., as indicated by the acquired source user data 1-14*) are not relevant to achievement of one or more reported outcomes (e.g., as indicated by, for example, the acquired source user data 1-14*) that corresponds to the one or more target outcomes of the personalized plan 1-16*.
  • In various implementations, operation 1-675 may include an operation 1-678 for requesting the end user to provide one or more indications of what types of aspects are relevant to the achievement of the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 b. For instance, the aspect type relevancy requesting module 1-216* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f requesting the end user 1-4*(e.g., transmitting a request 1-12* via a wireless network and/or wired network 1-50* or indicating a request 1-12* via a user interface 1-120″) to provide one or more indications of what types of aspects (e.g., what types of books should be read) are relevant to the achievement of the one or more target outcomes (e.g., improve reading test score) of the personalized plan 1-16*.
  • In some implementations, operation 1-678 may further include an operation 1-679 for determining which of the plurality of reported aspects belong to one or more types of aspects, as indicated by the end user, as being relevant to the achievement of the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 b. For instance, the relevant reported aspect determination module 1-208* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f determining which of the plurality of reported aspects (e.g., as indicated by the acquired source user data 1-14*) belong to one or more types of aspects, as indicated by the end user 1-4*, as being relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In various implementations, operation 1-675 may include an operation 1-680 for requesting the end user to provide indications of what types of aspects are not relevant to the achievement of the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 b. For instance, the aspect type non-relevancy requesting module 1-218* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f requesting the end user 1-4*(e.g., transmitting a request 1-12* via a wireless network and/or wired network 1-50* or indicating a request 1-12* via a user interface 1-120″) to provide one or more indications of what types of aspects are relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In some implementations, operation 1-680 may further include an operation 1-681 for determining which of the plurality of reported aspects does not belong to one or more types of aspects, as indicated by the end user, as being not relevant to the achievement of the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 b. For instance, the relevant reported aspect determination module 1-208* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f determining which of the plurality of reported aspects (e.g., as indicated by the acquired source user data 1-14*) does not belong to one or more types of aspects, as indicated by the end user 1-4*, as being not relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In various implementations, the development operation 1-306 of FIG. 1-3 may include an operation 1-682 for developing the personalized plan by at least determining which of the plurality of reported aspects are relevant to the achievement of the one or more target outcomes based, at least in part, on data provided by one or more third party sources that indicates one or more types of aspects that are relevant to the achievement of the one or more target outcomes of the personalized plan as depicted in FIG. 1-6 c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* as a result of the relevant reported aspect determination module 1-208* at least determining which of the plurality of reported aspects (e.g., as indicated by the acquired source user data 1-14*) are relevant to the achievement of the one or more target outcomes based, at least in part, on data provided by one or more third party sources (e.g., other source or end users 1-4*, publications, research papers, medical research, and so forth) that indicates one or more types of aspects that are relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In various embodiments, the development operation 1-306 may include an operation 1-683 for developing the personalized plan by including into the personalized plan at least one emulatable aspect that corresponds to at least one reported aspect associated with the source user that is determined to be relevant to the achievement of the one or more target outcomes as depicted in FIG. 1-6 c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the emulatable aspect inclusion module 1-222* include into the personalized plan 1-16* at least one emulatable aspect that corresponds to at least one reported aspect associated with the source user 1-2* that is determined to be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • In some implementations, the development operation 1-306 may include, in various alternative implementations, an operation 1-684 for developing the personalized plan by including into the personalized plan at least one intermediate outcome that corresponds to one or more reported intermediate outcomes as indicated by the source user data as depicted in FIG. 1-6 c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the intermediate outcome inclusion module 1-224* include into the personalized plan 1-16* at least one intermediate outcome that corresponds to one or more reported intermediate outcomes as indicated by the source user data 1-14*. Note that an intermediate outcome is an outcome that may precede the final reported outcome (e.g., target outcome associated with a personalized plan 1-16*). The intermediate outcome may be used in order to track, for example, the progress of an end user 1-4* in achieving a target outcome associated with a personalized plan 1-16*.
  • In some implementations, the development operation 1-306 may include an operation 1-685 for developing the personalized plan by including into the personalized plan a plurality of emulatable aspects that corresponds to the plurality of reported aspects associated with the source user that are determined to be relevant to the achievement of the one or more target outcomes as depicted in FIG. 1-6 c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the emulatable aspect inclusion module 1-222* include into the personalized plan 1-16* a plurality of emulatable aspects that corresponds to the plurality of reported aspects (e.g., as indicated by the acquired source user data 1-14*) associated with the source user 1-2* that are determined to be relevant to the achievement of the one or more target outcomes of the personalized plan 1-16*.
  • Operation 1-685, in turn, may further include one or more additional operations as illustrated in FIG. 1-6 d. For example, in some implementations, operation 1-685 may include an operation 1-686 for developing the personalized plan by defining in the personalized plan a relationship or relationships between the plurality of emulatable aspects included in the personalized plan. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the relationship defining module 1-226* define in the personalized plan 1-16* a relationship or relationships (e.g., temporal relationships, specific time relationships, or spatial relationships) between the plurality of emulatable aspects included in the personalized plan 1-16. Note that in some implementations, the personalized plan 1-16* may not indicate the relationships between the plurality of emulatable aspects included in the personalized plan 1-16*. Instead, such a personalized plan 1-16* may simply be a collection of emulatable aspects (as well as in some cases a collection of one or more outcomes).
  • In various implementations, operation 1-686 may further include an operation 1-687 for developing the personalized plan by defining in the personalized plan a temporal relationship or relationships between the plurality of emulatable aspects included in the personalized plan as depicted in FIG. 1-6 d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the relationship defining module 1-226* define in the personalized plan 1-16* a temporal relationship or relationships between the plurality of emulatable aspects included in the personalized plan 1-16*.
  • In some implementations, operation 1-686 may include an operation 1-688 for developing the personalized plan by defining in the personalized plan a specific time relationship or relationships between the plurality of emulatable aspects included in the personalized plan as depicted in FIG. 1-6 d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the relationship defining module 1-226* define in the personalized plan 1-16* a specific time relationship or relationships between the plurality of emulatable aspects included in the personalized plan 1-16*.
  • In various implementations, operation 1-686 may further include an operation 1-689 for developing the personalized plan by defining in the personalized plan a spatial relationship or relationships between the plurality of emulatable aspects included in the personalized plan as depicted in FIG. 1-6 d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the relationship defining module 1-226* define in the personalized plan 1-16* a spatial relationship or relationships between the plurality of emulatable aspects included in the personalized plan 1-16*.
  • In various implementations, operation 1-306 of FIG. 1-3 may include an operation 1-690 for developing the personalized plan by including into the personalized plan at least one plausible emulatable aspect, the at least one plausible emulatable aspect being at least one emulatable aspect that has been successfully emulated by one or more other end users as depicted in FIG. 1-6 d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the plausible emulatable aspect inclusion module 1-228* include into the personalized plan 1-16* at least one plausible emulatable aspect, the at least one plausible emulatable aspect being at least one emulatable aspect that has been successfully emulated by one or more other end users 1-4*(e.g., one or more third parties 1-6*).
  • Operation 1-690 may, in turn, include an operation 1-691 for developing the personalized plan by including into the personalized plan at least one plausible emulatable aspect, the at least one plausible emulatable aspect being at least one emulatable aspect that has been successfully emulated by the one or more other end users in order to achieve at least one of the one or more target outcomes as depicted in FIG. 1-6 d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f developing the personalized plan 1-16* by having the plausible emulatable aspect inclusion module 1-228 include into the personalized plan 1-16* at least one plausible emulatable aspect, the at least one plausible emulatable aspect being at least one emulatable aspect that has been successfully emulated by one or more other end users in order to achieve at least one of the one or more target outcomes of the personalized plan 1-16*.
  • Referring to FIG. 1-7 illustrating another operational flow 1-700 in accordance with various embodiments. Operational flow 1-700 includes certain operations that mirror the operations included in the operational flow 1-300 of FIG. 1-3. These operations include a reception operation 1-702, an acquisition operation 1-704 and a development operation 1-706 that corresponds to and mirror the reception operation 1-302, the acquisition operation 1-304 and the development operation 1-306, respectively, of FIG. 1-3.
  • In addition, operational flow 1-700 includes a presentation operation 1-708 for presenting the personalized plan as depicted in FIG. 1-7. For instance, the presentation module 1-108* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f presenting (e.g., transmitting via the wireless network and/or wired network 1-50 or indicating via a user interface 1-120*) the personalized plan 1-16*.
  • In various alternative implementations, the presentation operation 1-708 may include one or more additional operations. For example, in some implementations, the presentation operation 1-708 may include an operation 1-893 for transmitting the personalized plan via at least one of wireless network and a wired network as depicted in FIG. 1-8. For instance, the transmission module 1-228* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f transmitting the personalized plan 1-16* via at least one of wireless network and a wired network 1-50*.
  • In the same or different implementations, the presentation operation 1-708 may include an operation 1-894 for indicating the personalized plan via a user interface as depicted in FIG. 1-8. For instance, the user interface indication module 1-229* of the local source user device 1-20′ of FIG. 1-1 d or the local end user device 1-30″ of FIG. 1-1 f audibly or visually indicating the personalized plan 1-16* via a user interface 1-120* (e.g., a display monitor, a touchscreen, an audio system including one or more speakers, and so forth).
  • In the same or different implementations, the presentation operation 1-708 may include an operation 1-895 for presenting the personalized plan to the end user as depicted in FIG. 1-8. For instance, the presentation module 1-108* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f presenting the personalized plan 1-16* to the end user 1-4*.
  • In the same or different implementations, the presentation operation 1-708 may include an operation 1-896 for presenting the personalized plan to one or more third parties as depicted in FIG. 1-8. For instance, the presentation module 1-108* of the server 1-10 of FIG. 1-1 b, the local source user device 1-20′ of FIG. 1-1 d, or the local end user device 1-30″ of FIG. 1-1 f presenting the personalized plan 1-16* to one or more third parties 1-6*.
  • III. Personalized Plan Development Based on Outcome Identification
  • In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
  • A recent trend that has enjoyed explosive popularity in the computing/communication field is to electronically record one's daily activities, behaviors, thoughts, beliefs, traits, physical or mental states, physical characteristics, and other aspects of the person's everyday life onto an open diary. One place where such open diaries are maintained is at social networking sites commonly known as “blogs” where one or more users may report or post every aspect of their daily lives. The process of reporting or posting blog entries is commonly referred to as blogging. A newer type of blogging that has become very popular is microblogging, otherwise known as “twittering” or “tweeting.” In microblogging, each of the microblogs that are posted are typically relatively short posts or entries, usually not more than 140 characters long.
  • Other types of social networking sites may also allow users to maintain open diaries and to allow users to easily update their personal information. Such updates are typically made via, for example, social networking status reports. These social networking sites allow a user to report or post for others to view the latest status or other aspects related to the user. Although a wealth of personal information in the form of, for example, log data are now available through these social networking sites, it is only recently has there been any effort to exploit such potentially useful data.
  • In various embodiments, robust methods, systems, circuitry, and computer program products are provided that may facilitate in the development of one or personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated. The methods, systems, circuitry, and computer program products may be implemented in a variety of computing/communication devices including in a network device such as a server (e.g., network servers) or a local client device. In various embodiments, the development of the one or more personalized plans may be prompted when, for example, a request is received that identifies at least the one or more target outcomes.
  • In response to receiving the request, the methods, systems, circuitry, and computer program products may be designed to cause at least the execution of an operation to seek one or more reported aspects that are determined to be relevant to achieving the one or more target outcomes. A reported aspect may be any indication (e.g., in the form of electronic data such as text data, numerical data, image data, digital data, analog data, etc.) that indicates a reported occurrence of an aspect (e.g., behavior, act, trait, physical state, mental state, social state, declaration, belief, or any other facet) that may be associated with one or more source users. In some cases, the one or more relevant reported aspects to be found may be found from a plurality of reported aspects that may include both relevant and not relevant reported aspects for achieving the one or more target outcomes. Various locations or sources may be searched in order to find the one or more reported aspects that are relevant to achieving the one or more targeted outcomes in various embodiments. For example, in some embodiments, a memory (e.g., mass storage, volatile memory, non-volatile memory, and so forth) and/or a wireless and/or wired network may be searched for the one or more reported aspects that are relevant to achieving the one or more target outcomes.
  • Each reported aspect that is found to be relevant to achieving the one or more target outcomes may be associated with one or more source users and may have been at least originally reported by, for example, the one or more source users, one or more sensors, and/or one or more third parties. In some embodiments, a reported aspect may also be associated with a particular point or interval in time and/or associated with a particular location or locations. In certain cases, at least a portion of the one or more reported aspects that have been found to be relevant to the achievement of the one or more target outcomes may have been reported through social networking entries (e.g., microblog entry or status report).
  • Note that although the request for the one or more personalized plans may indicate the one or more target outcomes, in some embodiments, the request may not indicate any source user. In other embodiments, however, the request for the one or more personalized plans may, in addition to identifying the one or more target outcomes, may identify at least a source user or a group of source users.
  • Based at least in part on the seeking operations for the one or more reported aspects, the one or more personalized plans may be developed. The development of the one or more personalized plans may be by, for example, including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that have been determined to be relevant to the achievement of the one or more target outcomes. As will be further described, other types of information may also be included into the one or more personalized plans to be developed in various alternative embodiments.
  • A number of different approaches may be employed in various embodiments in order to determine whether a reported aspect is relevant to the achievement of one or more target outcomes. For example, in some embodiments, the operation to seek the one or more reported aspects that are relevant to achieving the one or more target outcomes may involve initially seeking one or more reported outcomes (e.g., final outcomes that have been reported) that corresponds to the one or more target outcomes. Note that in some cases a reported outcome may merely be a particular type of reported aspect. For example, if a request has been received for a personalized plan for losing 20 pounds of body weight (e.g., target outcome), a seeking operation may be executed that includes initially searching for one or more reported outcomes or aspects that indicates 20 pounds of body weight loss by one or more source users.
  • Once the one or more reported outcomes are found that corresponds to the one or more target outcomes, one or more source users may be identified that are associated with the one or more reported outcomes, which corresponds to the one or more target outcomes. By identifying those source users who have achieved the one or more target outcomes (e.g., reported outcomes that corresponds to the target outcomes), the search for the one or more reported aspects that are relevant to achieving the one or more target outcomes may be narrowly focused. The seeking operation may then exam only those reported aspects that are associated with the one or more source users who have been identified as having achieved the one or more target outcomes in order to find the one or more reported aspects that are relevant to achieving the one or more target outcomes.
  • The seeking operation to seek one or more reported aspects that are relevant to achieving the one or more target outcomes may be further narrowed by seeking or identifying only those reported aspects associated with the one or more identified source users (e.g., source users who have achieved the target outcomes) and that occurred within one or more predefined time periods from the one or more occurrences of the one or more reported outcomes. That is, not all reported aspects associated with the one or more source users previously identified as having achieved the one or more target outcomes may be relevant to the achievement of the one or more target outcomes. This may be particularly true with reported aspects that may have occurred well before (or well after) the achievement of the one or more target outcomes (e.g., as represented by the one or more reported outcomes that have been found to be corresponding to the one or more target outcomes) by the one or more identified source users. Thus, a reported aspect may only be relevant to the achievement of the one or more target outcomes if it falls within some time period (e.g., predefined time period) from the one or more occurrences of the one or more reported outcomes that have been found to be corresponding to the one or more target outcomes. The amount of time period or predefined time period described above may, of course, vary depending on a number of factors.
  • For example, in some embodiments, the one or more predefined time periods (e.g., each of the one or more target outcomes as represented by the one or more reported outcomes may be associated with a different predefined time period) may be set based on the types of the one or more personalized plans being requested and/or may be provided by the end user, a source user, or some third party. For example, in the above weight loss example, the end user may only be interested in reported aspects (e.g., dietary and/or exercise behaviors) that occurred within one month of the one or more occurrences of the one or more reported outcomes (e.g., body weight loss of 20 pounds).
  • Based on this criteria, only those reported aspects that occurred within one month of the occurrence of the reported target outcome (e.g., 20 pounds of body weight loss) and that are associated with the same one or more source users that were identified as achieving the target outcome may qualify as being relevant to the achievement of the one or more target outcomes. As will be further described herein, other factors (e.g., types of reported aspects that the end user may be interested in or indications provided by one or more third party sources such as publications or research advisories that indicate what types of reported aspects may be relevant to achieving the types of target outcomes being sought) may also determine which reported aspects are “relevant” to achieving the one or more target outcomes.
  • In some cases, the one or more reported aspects that are found to be relevant to achieving the one or more target outcomes may have been originally acquired in the form of, for example, log data. In some embodiments, such log data may have been at least originally received via social networking entries (e.g., microblog entries and/or status reports), diary entries, sensor readings and/or other means of obtaining log data. Upon finding the one or more reported aspects that are determined to be relevant to achieving the one or more target outcomes, the one or more personalized plans may be developed by including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that have been found to be relevant to achieving the one or more target outcomes. As will be further described herein, other types of information such as “emulatable intermediate outcomes” may also be included in the one or more personalized plans in various alternative embodiments. After developing the one or more personalized plans, the personalized plans may be presented to the end user or to one or more third parties in various embodiments.
  • In some embodiments, a personalized plan may merely be a collection of one or more emulatable aspects. An emulatable aspect may be any behavior, act, trait, physical state, mental state, social state, declaration, belief, or any other facet that may be emulated in order to achieve one or more target outcomes. In cases where a personalized plan includes multiple emulatable aspects, the personalized plan may or may not define a relationship or relationships (e.g., temporal, specific time, or spatial relationships) between the emulatable aspects included in the personalized plan. In some cases, a personalized plan may also indicate one or more emulatable intermediate outcomes that may be associated with the target outcomes. For example, if a personalized plan includes a plurality of emulatable aspects, one or more emulatable intermediate outcomes may also be included in the personalized plan that may represent one or more outcomes that preferably or ideally occurs before the target outcome is achieved. In some cases, the emulatable intermediate outcomes that may be included in a personalized plan may be based on, for example, one or more reported intermediate outcomes (e.g., intermediate outcomes that have been reported). By including one or more emulatable intermediate outcomes into a personalized plan, an end user may be able to better monitor his/her progress towards reaching the one or more target outcomes by comparing his/her actual intermediate results with the one or more emulatable intermediate outcomes that may be included in a personalized plan,
  • A “target outcome” may be any type of goal or desired result that may be sought by an end user or by a third party. Examples of target outcomes include, for example, health-related outcomes such as weight loss or improved cardiovascular conditioning, athletic outcomes such as developing a particular athletic skill including being able to pitch a curve ball or achieving a particular golf handicap, physiological outcomes such as reduced blood pressure or blood glucose levels, social outcomes such as obtaining membership into an elite social club or attaining a particular social status, mental state outcomes such as achieving certain level of calmness or happiness, interpersonal or relational outcomes such as having lots of friends or developing skill to make friends, employment outcomes such as being promoted or developing certain work skills, academic or intellectual outcomes, and so forth.
  • A source user may be any real or fictitious person who may be associated with one or more reported aspects. In some cases, a source user may be an actual person who may be the source or is associated with one or more reported aspects. In other cases, a source user may be a fictional person such as a composite of multiple actual source users. For example, reported aspects of actual aspects associated with a plurality of source user may be compiled and processed (e.g., normalized or averaged out) in order to create such a fictional source user.
  • Turning now to FIGS. 2-1 a, 2-1 b, 2-2 a, 2-2 b, 2-3 a, and 2-3 b, illustrating three example environments in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented by a computing device such as a server or a local client device. In particular, FIGS. 2-1 a and 2-1 b illustrates a first example environment in which the methods, systems, circuitry, and computer program products in accordance with some embodiments may be implemented at a server 2-10. FIGS. 2-2 a and 2-2 b illustrate a second example environment in which the methods, systems, circuitry, and computer program products in accordance with some embodiments may be implemented at a local source user device 2-20 a′. FIGS. 2-3 a and 2-3 b illustrate a third example environment in which the methods, systems, circuitry, and computer program products in accordance with some embodiments may be implemented at a local end user device 2-30″.
  • Note that in the following, “*” represents a wildcard. Thus, references in the following description to “one or more source users 2-2*” is in reference to the one or more source users 2-2 of the first example environment of FIGS. 2-1 a and 2-1 b, to the one or more source users 2-2′ of the second example environment of FIGS. 2-2 a and 2-2 b, or to the one or more source users 2-2″ of the third example environment of FIGS. 2-3 a and 2-3 b. Further, references in the following to “a source user 2-2**” is in reference to any one of the source users (e.g., source user 2-2 a, source user 2-2 b, source user 2-2 a′, source user 2-2 b′, source user 2-3 a″, source user 2-3 b″, and so forth) depicted in the three example environments of FIGS. 2-1 a, 2-1 b, 2-2 a, 2-2 b, 2-3 a, and 2-3 b.
  • In various embodiments, the server 2-10 of FIG. 2-1 b, the local source user device 2-20 a′ of FIG. 2-1 d, and the local end user device 2-30″ of FIG. 2-1 f may be designed to, among other things, receive a request 2-12* for one or more personalized plans 2-16* that are designed to facilitate an end user 24* to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 2-16* are emulated, the request 2-12* identifying at least the one or more target outcomes. In some implementations, the request 2-12* may identify the one or more target outcomes without identifying any source user 2-2**. In response to the receiving the request 2-12*, the server 2-10, the local source user device 2-20′, and the local end user device 2-30″ may be designed to seek (e.g., search or identify) one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes. In various implementations, the one or more reported aspects 2-14* that are found to be relevant to the achievement of the one or more target outcomes may be associated with one or more source users 2-2* who have achieved the one or more target outcomes.
  • After seeking for (and finding) the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes, the server 2-10, the local source user device 2-20 a′, and the local end user device 2-30″ may be designed to develop the one or more personalized plans 2-16* by, for example, including into the one or more personalized plans 2-16* at least one or more emulatable aspects that corresponds to the one or more reported aspects that were found to be relevant to the achievement of the one or more target outcomes. In some implementations, the server 2-10, the local source user device 2-20 a′, and the local end user device 2-30″ may be further designed to present the resulting one or more personalized plans 2-16*.
  • Referring particularly now to FIGS. 2-1 a and 2-1 b illustrated the first example environment in accordance with various embodiments. Included in the illustrated first environment of FIGS. 2-1 a and 2-1 b is a first exemplary system 2-100, which includes at least a server 2-10 (see FIG. 2-1 b) that may be designed to communicate with one or more source users 2-2 (via one or more local source user devices 2-20) and an end user 2-4 (via a local end user device 2-30) through a wireless network and/or wired network 2-50. In some implementations, the server 2-10 may further communicate with, via the wireless network and/or wired network 2-50, one or more third parties 2-6 (e.g., one or more other end users, one or more content providers, one or more network service providers, and/or one or more other parties), one or more other servers (illustrated as one or more network servers 2-60), and/or one or more sensors 2-40.
  • In various implementations, the server 2-10 of FIG. 2-1 b (as well as the one or more network servers 2-60* of FIGS. 2-1 a, 2-2 a, and 2-3 b) may be a computing/communication device that is designed to interface with a wireless network and/or wired network 2-50. Further, the server 2-10 of FIG. 2-1 b, as will be described herein, may be in reference to a network server that may be located at a single network site or located across multiple network sites or a conglomeration of servers located at multiple network sites.
  • The one or more source users 2-2 may include a first source user 2-2 a, a second source user 2-2 b, a third source user 2-2 c, a fourth source user 2-2 d, and so forth. The one or more local source user devices 2-20 may include a first local source user device 2-20 a (e.g., to be used by the first source user 2-2 a to communicate via wireless network and/or wired network 2-50), a second local source user device 2-20 b (e.g., to be used by the second source user 2-2 b to communicate via wireless network and/or wired network 2-50), and so forth. The one or more local source user devices 2-20 (as well as the local source user devices 2-20** of FIGS. 2-2 a and 2-2 b and the one or more local source user devices 2-20″ of FIG. 2-3 a) and the local end user device 2-30 (as well as the local end user device 2-30′ of FIG. 2-2 a and the local end user device 2-30″ of FIG. 2-3 b) may be any one of a variety of computing/computing devices including, for example, a cellular phone, a personal digital assistant (PDA), a laptop, a desktop, or other types of computing/communication devices. In some embodiments, the one or more local source user devices 2-20 (as well as the local source user devices 2-20** of FIGS. 2-2 a and 2-2 b and the one or more local source user devices 2-20″ of FIG. 2-3 a) and/or the local end user device 2-30 (as well as the local end user device 2-30′ of FIG. 2-2 a and the local end user device 2-30″ of FIG. 2-2 b) may be a handheld device such as a cellular telephone, a smartphone, a Mobile Internet Device (MID), an Ultra Mobile Personal Computer (UMPC), a convergent device such as a personal digital assistant (PDA), and so forth.
  • In various embodiments, the one or more sensors 2-40 (as well as the one or more sensors 2-40′ of FIG. 2-2 a and the one or more sensors 2-40″ of FIG. 2-3 a) may include one or more of a wide range of sensing devices that can monitor various aspects or events associated with one or more source users 2-2. For example, in some implementations, the one or more sensors 2-40* may include devices that can monitor a user's physiological characteristics such as blood pressure sensors, heart rate monitors, glucometers, and so forth. In some implementations, the one or more sensors 2-40* may include devices that can monitor activities of a user (e.g., a source user 2-2*) such as a pedometer, a toilet monitoring system (e.g., to monitor bowel movements), exercise machine sensors, an accelerometer to measure a person's movements which may indicate specific activities, and so forth. The one or more sensors 2-40* may also include other types of sensor/monitoring devices such as video or digital camera to provide electronic images of, for example, the one or more target outcomes as displayed by a source user 2-20*, global positioning system (GPS) to provide location data related to a user (e.g., locations of the source user 2-2*), and so forth. In various implementations, the one or more sensors 2-40 may be designed to communicate directly with the wireless network and/or wired network 2-50 or indirectly with the wireless network and/or wired network 2-50 via the one or more local source user devices 2-20.
  • Referring back to the first exemplary environment of FIGS. 2-1 a and 2-1 b, the server 2-10 may receive a request 2-12 for one or more personalized plans 2-16 designed to facilitate an end user 2-4 to achieve one or more target outcomes from, for example, the end user 2-4 (e.g., via the local end user device 2-30), from one or more third parties 2-6, or from one or more network servers 2-60. The request 2-12 may identify at least the one or more target outcomes. In various implementations, the requested one or more personalized plans 2-16 may be designed to facilitate the end user 2-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 2-16 are emulated.
  • In response to receiving the request 2-12, the server 2-10 may execute an operation to seek (e.g., identify or search) one or more reported aspects 2-14 that are relevant to achieving the one or more target outcomes. This may involve searching for the relevant reported aspects 2-14 at a number of different locations via a wireless network and/or a wired network 2-50. For example, in some implementations, a solicitation 2-13 for the one or more reported aspects 2-14 may be transmitted to one or more local source user devices 2-20, to one or more third parties 2-6, to one or more sensors 2-40, and/or to one or more network servers 2-60. In alternative or in the same implementations, a memory 2-116 may be searched for the one or more reported aspects 2-14. The determination of whether a reported aspect 2-14 is relevant to the achievement of the one or more target outcomes may be based on a number of factors as will be further described in greater detail herein.
  • Once the one or more reported aspects 2-14 relevant to the achievement of the one or more target outcomes have been found, the server 2-10 may develop the one or more personalized plans 2-16 by, for example, including into the one or more personalized plans 2-16, one or more emulatable aspects that corresponds to the reported aspects 2-14 that have been found to be relevant to the achievement of the one or more target outcomes. In some implementations, a personalized plan 2-16 may merely be a collection of one or more emulatable aspects, while in other implementations, a personalized plan 2-16 may define the specific relationships (e.g. spatial or time relationships) between emulatable aspects. In some implementations, a personalized plan 2-16 may include other information such as emulatable intermediate outcomes to determine, for example, how well an end user 2-4 when following a personalized plan 2-16 is progressing towards achieving a target outcome. In some implementations, the server 2-10 may then be designed to present the developed one or more personalized plans 2-16 to the end user 2-4 (via the local end user device 2-30) and/or to one or more third parties 2-6.
  • The server 2-10 as illustrated in FIG. 2-1 b may include a variety of modules, sub-modules, and other components. As shown, the server 2-10 may include a request reception module 2-102 (which may further include a network interface reception module 2-202), a reported aspect seeking module 2-104 (which may further include one or more sub-modules as illustrated in FIG. 2-4 a), a personalized plan development module 2-106 (which may further include one or more sub-modules as illustrated in FIG. 2-4 b), a presentation module 2-108 (which may further include a transmission module 2-224), a memory 2-116 (which may store a plurality of reported aspects 2-15, one or more applications 2-140, one or more end user preferences 2-142, one or more end user limitations 2-144, and/or one or more third party sources 2-146), and/or a network interface 2-118 (e.g., a network interface card or NIC). The server 2-10, in various implementations, may further include a social networking entry reception module 2-110 (which may further include a blog entry reception module 2-111 and/or status report reception module 2-112), a diary entry reception module 2-114, and/or a sensor data reception module 2-115.
  • The request reception module 2-102 may be configured to, among other things, receive a request 2-12 for one or more personalized plans 2-16 that are designed to facilitate an end user 2-4 to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan 2-16 are emulated. The request 2-12 to be received by the request reception module 2-102 may at least identify the one or more target outcomes. In some implementations, the request 2-12 to be received by the request reception module 2-102 may further include other information that may facilitate in the development of the one or more personalized plans 2-16 as will be further described herein. In order to facilitate reception of a request 2-12 from, for example, a network device (e.g., local end user device 2-30 or a network server 2-60), the request reception module 2-102 may include a network interface reception module 2-202 configured to receive the request 2-12 via a wireless network and/or wired network 2-50.
  • The reported aspect seeking module 2-104 may be configured to seek (e.g., search or identify), in response to the request reception module 2-102 receiving the request 2-12, one or more reported aspects 2-14 that are determined to be relevant to achieving the one or more target outcomes. In various implementations, the reported aspect seeking module 2-104 may be configured to seek the one or more reported aspects 2-14 that are relevant to achieving the one or more reported outcomes by transmitting a solicitation for the one or more reported aspects 2-14 to one or more potential sources (e.g., one or more network servers 2-60 and/or one or more local source user devices 2-20) via a wireless network and/or wired network 2-50. In the same or different implementations, the reported aspect seeking module 2-104 may be designed to search a memory 2-116 for the one or more reported aspects 2-14 that are relevant to achieving the one or more target outcomes. In various implementations, memory 2-116 may store a plurality of reported aspects 2-15 that may include both reported aspects 2-14 that are relevant to the achievement of the one or more target outcomes and reported aspects that are not relevant to achieving the one or more target outcomes. Thus, the reported aspect seeking module 2-104 may be designed to search or filter through a plurality of reported aspects (e.g., plurality of reported aspects 2-15 that may be found throughout the wireless network and/or wired network 2-50 or the plurality of reported aspects 2-15 that may be included in memory 2-116) to find the one or more reported aspects 2-14 that are relevant to the achieving of the one or more target outcomes.
  • The personalized plan development module 2-106 may be configured to, among other things, develop one or more personalized plans 2-16 by, for example, including into the one or more personalized plans 2-16 at least one or more emulatable aspects that corresponds to the one or more reported aspects 2-14 found by the reported aspect seeking module 2-104 that have been determined to be relevant to the achievement of the one or more target outcomes. The personalized plan development module 2-106 may also be configured to include into the one or more personalized plans 2-16 other types of information in various alternative implementations. For example, in some implementations, the personalized plan development module 2-106 may be designed to define in a personalized plan 2-16 one or more spatial, temporal, or specific time relationships between a plurality of emulatable aspects that may be included in the personalized plan 2-16. In the same or different implementations, the personalized plan development module 2-106 may be configured to include into a personalized plan 2-16 one or more emulatable intermediate outcomes. As will be further described herein, the personalized plan development module 2-106, in various implementations, may further include one or more sub-modules as will be further described herein and as illustrated in FIG. 2-4 b.
  • The presentation module 2-108 may be configured to present the personalized plan 2-16 developed by the personalized plan development module 2-106 to the end user 2-4, one or more source users 2-2, one or more third parties 2-6, and/or one or more network servers 2-60. In some implementations, the presentation module 2-108 may further include a transmission module 2-224 that is configured to transmit the one or more personalized plans 2-16 via, for example, the wireless network and/or wired network 2-50.
  • A more detailed discussion relating to the request reception module 2-102, the reported aspect seeking module 2-104, the personalized plan development module 2-106, the presentation module 2-108, and their sub-modules, will be provided below with respect to the various operational flows to be described herein. The social networking entry reception module 2-110 may be configured to receive social networking entries from various sources including, for example, one or more source users 2-2, an end user 2-4, and/or one or more third parties 2-6. The social networking entry reception module 2-110 may further include a blog entry reception module 2-111 that is configured to receive blog entries (e.g. microblog entries) and/or a status report reception module 2-112 configured to receive social networking status reports. Similarly, the diary entry reception module 2-114 may be configured to receive diary entries from, for example, the one or more source users 2-2, the end user 2-4, and/or from the one or more third parties 2-6.
  • The sensor data reception module 2-115 may be configured to receive sensing data from one or more sensors 2-40. The memory 2-116 may comprise one or more volatile and/or non-volatile devices that may be used to store data. In various implementations, the memory 2-116 may include, for example, a mass storage device, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), cache memory such as random access memory (RAM), flash memory, synchronous random access memory (SRAM), dynamic random access memory (DRAM), and/or other types of memory devices.
  • In various implementations, memory 2-116 may store a plurality of reported aspects 2-15, one or more applications 2-140, one or more end user preferences 2-142 (e.g., preferences indicating the types of reported or emulatable aspects that an end user 2-4 is interested in), one or more end user limitations 2-144 (e.g., contextual limitations, physical limitations, personal limitations, and so forth that may prevent certain types of aspects from being emulated by, for example, an end user 2-4), and/or one or more third party sources 2-146 (e.g., publications, research advisories, and so forth that may indicate the types of reported aspects that may be relevant to achieving one or more target outcomes). The plurality of reported aspects 2-15 may be associated with one or more source users 2-2 and may include different types of reported aspects 2-14 (e.g., behaviors, traits, beliefs, and so forth associated with one or more source users 2-2). The one or more applications 2-140 that may be included in the memory 2-116 may comprise of, for example, one or more communication applications (e.g., text messaging application, instant messaging application, email application, voice recognition system, and so forth), Web 1.0 application, and/or Web 2.0 application to facilitate in communicating via, for example, the World Wide Web.
  • Referring now to FIGS. 2-2 a and 2-2 b, which as previously indicated, illustrates a second example environment in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented at a local source user device 2-20′ rather than at a server 2-10′ as was the case in the first example environment of FIGS. 2-1 a and 2-1 b. As illustrated, the second example environment of FIGS. 2-2 a and 2-2 b is similar to the first example environment of FIGS. 2-1 a and 2-1 b.
  • In general, the second example environment of FIGS. 2-2 a and 2-2 b may include a second exemplary system 2-100′, which includes at least a local source user device 2-20 a′ (see FIG. 2-2 b). In various implementations, the local source user device 2-20 a′, as was the case for server 2-10 of FIGS. 2-1 a and 2-1 b, may be designed to receive a request 2-12′ for one or more personalized plans 2-16′ that are designed to facilitate an end user 2-4′ to achieve one or more target outcomes. In some implementations, the request 2-12′ may be received from an end user 2-4′ via a wireless network and/or wired network 2-50′. Alternatively, the request 2-12′ may be received from a network server 2-60′ or from one or more third parties 2-6′. As before in the first exemplary environment, the request 2-12′ may identify one or more target outcomes in various implementations. Also as before, in some implementations, the request 2-12′ may not identify any source user 2-2*′.
  • In response to receiving the request 2-12′, the local source user device 2-20 a′ may be designed to execute an operation to seek (e.g., identify or search) one or more reported aspects 2-14′ that are relevant to achieving the one or more target outcomes. Such an operation may involve searching for the relevant one or more reported aspects 2-14′ at a number of different locations via, for example, a wireless network and/or a wired network 2-50′. For example, such searching may be accomplished by transmitting a solicitation 2-13′ for the one or more reported aspects 2-14′ that are relevant to achieving the one or more target outcomes to one or more network servers 2-60′, to one or more sensors 2-40′, to one or more third parties 2-6′, and/or to other one or more local source user devices 2-20′. In alternative or in the same implementations, a memory 2-116′ may be searched for the one or more reported aspects 2-14′.
  • Once the one or more reported aspects 2-14′ relevant to the achievement of the one or more target outcomes have been found, the local source user device 2-20 a′ may develop the one or more personalized plans 2-16′ by, for example, including into the one or more personalized plans 2-16′, one or more emulatable aspects that corresponds to one or more reported aspects 2-14′ that have been found to be relevant to the achievement of the one or more target outcomes. As in the case of the first exemplary environment of FIGS. 2-1 a and 2-1 b, a personalized plan 2-16′ may, in some cases, merely be a collection of one or more emulatable aspects. In other cases, however, a personalized plan 2-16′ may define the specific relationships (e.g., spatial, temporal, or specific time relationships) between multiple emulatable aspects. And as in the case of the first exemplary environment, a personalized plan 2-16′ may include other information such as emulatable intermediate outcomes. After developing the one or more personalized plans 2-16′, the local source user device 2-20 a′ may then be designed to present the developed one or more personalized plans 2-16′ to, for example, an end user 2-4′ (via the local end user device 2-30), one or more network servers 2-60, a source user 2-2 a′ (e.g., via user interface 2-120′), and/or one or more third parties 2-6′.
  • The local source user device 2-20 a′, as illustrated in FIG. 2-2 b, may include the same or similar modules, sub-modules, and other components included in the server 2-10 of FIG. 2-1 b. As illustrated, the local source user device 2-20 a′ may include a request reception module 2-102′ (which may further include a network interface reception module 2-202′, a reported aspect seeking module 2-104′, a personalized plan development module 2-106′, a presentation module 2-108′ (which may further include a transmission module 2-224′), a memory 2-116′ (which may store a plurality of reported aspects 2-15′, one or more applications 2-140′, one or more end user preferences 2-142′, one or more end user limitations 2-144′, and/or one or more third party sources 2-146′), and/or a network interface 2-118′, similar to the server 2-10 of FIG. 2-1 b.
  • Also similar to server 2-10 of FIG. 2-1 b, the local source user device 2-20 a′ may also include a social networking entry reception module 2-110′ (which may further include a blog entry reception module 2-111′ and/or a status report reception module 2-112′), a diary entry reception module 2-114′, and/or a sensor data reception module 2-115′. All of these modules, sub-modules, and other components of the local source user device 2-20 a′ may perform the same or similar functions as their counterparts that may be included in the server 2-10 of FIG. 2-1 b. In addition to these modules, sub-modules, and other components, the local source user device 2-20′ may include a user interface 2-120′ and a user interface indication module 2-226′ (which may be included with the presentation module 2-108′). The user interface indication module 2-226′ may be designed to indicate, for example, the one or more personalized plans 2-16′ via the user interface 2-120′. The user interface 2-120′ may include one or more of, for example, a display monitor, a touchscreen, a keyboard, a keypad, a mouse, an audio system including one or more speakers, a microphone, an image capturing device such as a digital camera, and so forth.
  • Turning now to FIGS. 2-3 a and 2-3 b, which as previously indicated, illustrates a third example environment in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented at a local end user device 2-30″ rather than at a server 2-10″ or at a local source user device 2-20 a″ as was the case in the first and second example environments of FIGS. 2-1 a and 2-1 b and FIGS. 2-2 a and 2-2 b. The third example environment of FIGS. 2-3 a and 2-3 b is similar to the first example environment of FIGS. 2-1 a and 2-1 b and the second example environment of FIGS. 2-2 a and 2-2 b with few minor differences. For example, in the third example environment, the local end user device 2-30″ may receive a request 2-12″ for the one or more personalized plans 2-16″ directly from an end user 2-4″ via a user interface 2-120″ rather than via the wireless network and/or wired network 2-50″ as was the case for the server 2-10 of the first example environment of FIGS. 2-1 a and 2-1 b and as was the case for the local source user device 2-20 a′ of the second example environment of FIGS. 2-2 a and 2-2 b. However, and as with the server 2-10 and the local source user device 2-20 a′ of FIGS. 2-1 b and 2-2 b, the local end user device 2-30″ may also alternatively receive a request 2-12″ via the wireless network and/or wired network 2-50″ from other sources such as from one or more third parties 2-6″ or from a network server 2-60″.
  • As illustrated, the third example environment of FIGS. 2-3 a and 2-3 b may include a third exemplary system 2-100″, which includes at least a local end user device 2-30″ (see FIG. 2-3 b). In general, the local end user device 2-30″ may be designed to receive a request 2-12″ for one or more personalized plans 2-16″ that are designed to facilitate an end user 2-4″ to achieve one or more target outcomes. In some implementations, the request 2-12″ may be received directly from the end user 2-4″ via a user interface 2-120″. Alternatively, and although not depicted, the request 2-12″ may be received via wireless network and/or wired network 2-50″ from, for example, one or more third parties 2-6″ or from a network server 2-60″. As before in the first and second exemplary environments, the request 2-12″ may identify one or more target outcomes in various implementations. Also as before, in some implementations, the request 2-12″ may not identify any source user 2-2*″.
  • In response to receiving the request 2-12″, the local end user device 2-30″ may be designed to execute an operation to seek (e.g., identify or search) one or more reported aspects 2-14″ that are relevant to achieving the one or more target outcomes. Such an operation may involve, in some cases, searching for the relevant one or more reported aspects 2-14″ at a number of different locations via, for example, a wireless network and/or a wired network 2-50″. For example, such searching may be accomplished by transmitting a solicitation 2-13″ for the one or more reported aspects 2-14″ that are relevant to achieving the one or more target outcomes to one or more network servers 2-60″, to one or more sensors 2-40″, to one or more third parties 2-6″, and/or to one or more local source user devices 2-20″. In alternative or in the same implementations, a memory 2-116″ may be searched for the one or more reported aspects 2-14″ that are relevant to achieving the one or more target outcomes.
  • Once the one or more reported aspects 2-14″ relevant to the achievement of the one or more target outcomes have been found, the local end user device 2-30″ may develop the one or more personalized plans 2-16″ by, for example, including into the one or more personalized plans 2-16″, at least one or more emulatable aspects that corresponds to one or more reported aspects 2-14″ that have been found to be relevant to the achievement of the one or more target outcomes. As in the case of the first exemplary environment of FIGS. 2-1 a and 2-1 b and the second exemplary environment of FIGS. 2-2 a and 2-2 b, a personalized plan 2-16″ may, in some cases, merely be a collection of one or more emulatable aspects. In other cases, however, a personalized plan 2-16″ may define the specific relationships (e.g., spatial, temporal, or specific time relationships) between multiple emulatable aspects. And as in the case of the first and second exemplary environments, a personalized plan 2-16″ may include other information such as emulatable intermediate outcomes. After developing the one or more personalized plans 2-16″, the local end user device 2-30″ may then be designed to present the developed one or more personalized plans 2-16″ to, for example, an end user 2-4″ (via the user interface 2-120″), one or more network servers 2-60″, and/or one or more third parties 2-6″.
  • In various implementations, the local end user device 2-30″ may include the same or similar modules, sub-modules, and other components included in the local source user device 2-20 a′ of FIG. 2-2 b. For example, the local end user device 2-30″ may include a request reception module 2-102″, a reported aspect seeking module 2-104″, a personalized plan development module 2-106″, a presentation module 2-108″ (which may further include a transmission module 2-224″ and a user interface indication module 2-226″), a memory 2-116″ (which may store a plurality of reported aspects 2-15″, one or more applications 2-140″, one or more end user preferences 2-142″, one or more end user limitations 2-144″, and/or one or more third party sources 2-146″), a user interface 2-120″, and/or a network interface 2-118″, similar to the local source user device 2-20 a′ of FIG. 2-2 b.
  • Also similar to the local source user device 2-20 a′ of FIG. 2-2 b, the local end user device 2-30″ may also include a social networking entry reception module 2-110″ (which may further include a blog entry reception module 2-111″ and/or a status report reception module 2-112″), a diary entry reception module 2-114″, and/or a sensor data reception module 2-115″. All of these modules, sub-modules, and components of the local end user device 2-30″ may perform the same or similar functions as their counterparts that may be included in the local source user device 2-20 a′ of FIG. 2-2 b. In addition to these modules, sub-modules, and components, the local end user device 2-30″ may include a user interface reception module 2-203″ (which may be included in the request reception module 2-102″) for receiving the request 2-12″ via a user interface 2-120″. The user interface 2-120″ may include one or more of, for example, a display monitor, a touchscreen, a keyboard, a keypad, a mouse, an audio system including one or more speakers, a microphone, an image capturing device such as a digital camera, and so forth.
  • FIG. 2-4 a illustrates particular implementations of the reported aspect seeking module 2-104*(e.g., the reported aspect seeking module 2-104, the reported aspect seeking module 2-104′, and the reported aspect seeking module 2-104″) of FIGS. 2-1 b, 2-2 b, and 2-3 b. As illustrated, the reported aspect seeking module 2-104* may include a network searching module 2-204* that is configured to, among other things, search for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes via at least one of a wireless network and a wired network 2-50. In various implementations, the network searching module 2-204* may further include a solicitation transmission module 2-206* configured to, among other things, transmit a solicitation 2-13* for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes to one or more remote network devices (e.g., in the embodiment depicted in FIGS. 2-1 a and 2-1 b, transmitting the solicitation 2-13 to one or more local source user devices 2-20, to one or more sensors 2-40, or to one or more network servers 2-60).
  • In various implementations, the reported aspect seeking module 2-104* may include a memory searching module 2-208*, a reported outcome identification module 2-210*, a reported aspect identification module 2-212*, a preference compliant reported aspect identification module 2-213*, a limitation compliant reported aspect identification module 2-214*, a reported plausible aspect identification module 2-216*, and/or a reported aspect reception module 2-218*. The memory searching module 2-208* may be configured to search a memory 2-116* for the one or more reported aspects 2-14* associated with at least the one or more target outcomes. The reported outcome identification module 2-210* may be configured to identify one or more reported outcomes that correspond to the one or more target outcomes to, for example, facilitate the seeking of the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes. The reported aspect identification module 2-212* may be configured to, among other things, identify the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of the one or more reported outcomes (e.g. as identified by the reported outcome identification module 2-210*).
  • The preference compliant reported aspect identification module 2-213* may be configured to, among other things, identify one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14* that complies with one or more preferences of an end user 2-4* and that are associated with the one or more reported outcomes (e.g., as identified by the reported outcome identification module 2-210*). The limitation compliant reported aspect identification module 2-214* may be configured to, among other things, identify one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14* that complies with one or more limitations associated with an end user 2-4* and that are associated with the one or more reported outcomes (e.g., as identified by the reported outcome identification module 2-210*). The reported plausible aspect identification module 2-216* may be configured to, among other things, identify one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported plausible aspects that are associated with the one or more reported outcomes (e.g., as identified by the reported outcome identification module 2-210*) that corresponds to the one or more target outcomes, the one or more reported plausible aspects being aspects that have been successfully emulated by one or more third parties 2-6*. The reported aspect reception module 2-218* may be configured to receive one or more reported aspects 2-14* that are found by the reported aspect seeking module 2-104 to be relevant to achieving the one or more target outcomes.
  • FIG. 2-4 b illustrates particular implementations of the personalized plan development module 2-106*(e.g., the personalized plan development module 2-106, the personalized plan development module 2-106′, and the personalized plan development module 2-106″) of FIGS. 2-1 b, 2-2 b, and 2-3 b. In various implementations, the personalized plan development module 2-106* may include an emulatable aspect inclusion module 2-218*, a relationship defining module 2-220*, and/or an emulatable intermediate outcome inclusion module 2-222*. The emulatable aspect inclusion module 2-218* may be configured to, among other things, include into each of one or more personalized plans 2-16* to be developed one or more emulatable aspects that corresponds to one or more reported aspects that have been found to be relevant to achieving the one or more target outcomes of the one or more personalized plans 2-16*. The relationship defining module 2-220* may be configured to, among other things, define in each of the one or more personalized plans 2-16* to be developed one or more relationships (e.g., spatial, temporal, and/or specific time relationships) between the plurality of emulatable aspects included in each of the one or more personalized plans 2-16*. The emulatable intermediate outcome inclusion module 2-222* may be configured to, among other things, include into at least one of the one or more personalized plans 2-16* to be developed one or more emulatable intermediate outcomes related to the one or more target outcomes of the at least one of the one or more personalized plans 2-16*.
  • Referring back to the server 2-10 of FIG. 2-1 b, the local source user device 2-20 a′ of FIG. 2-2 b, and the local end user device 2-30″, the various modules (e.g., the request reception module 2-102*, the reported aspect seeking module 2-104*, the personalized plan development module 2-106*, the presentation module 2-108*, and so forth) along with their sub-modules included in the server 2-10, the local source user device 2-20 a′, and the local end user device 2-30″ may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations the request reception module 2-102*, the reported aspect seeking module 2-104*, the personalized plan development module 2-106*, and/or the presentation module 2-108* may be implemented with a processor 2-1102 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 2-1104 (e.g., computer program product) stored in a storage medium 2-1106 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 2-1100 of FIG. 2-11. Alternatively, hardware such as application specific integrated circuit (ASIC) may be employed in order to implement such modules in some alternative implementations.
  • A more detailed discussion related to the server 2-10 of FIG. 2-1 b, the local source user device 2-20 a′ of FIG. 2-2 b, and the local end user device 2-30″ of FIG. 2-3 b will now be provided with respect to the processes and operations to be described herein. FIG. 2-5 illustrates an operational flow 2-500 representing example operations related to, among other things, development of one or more personalized plans 2-16 designed to facilitate an end user 2-4 to achieve one or more target outcomes, the development of the one or more personalized plans 2-16 being in response to a reception of a request 2-12 that at least identifies the one or more target outcomes. In some embodiments, the operational flow 2-500 may be executed by, for example, the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b.
  • In FIG. 2-5 and in the following figures that include various examples of operational flows, discussions and explanations may be provided with respect to the three exemplary environments described above as illustrated in FIGS. 2-1 a and 2-1 b, FIGS. 2-2 a and 2-2 b, and FIGS. 2-3 a and 2-3 b, and/or with respect to other examples (e.g., as provided in FIGS. 2-4 a and 2-4 b) and contexts. However, it should be understood that the operational flows may be executed in a number of other environments and contexts, and/or in modified versions of FIGS. 2-1 a, 2-1 b, 2-2 a, 2-2 b, 2-3 a, 2-3 b, 2-4 a and 2-4 b. Also, although the various operational flows are presented in the sequence(s) illustrated, it should be understood that the various operations may be performed in other orders than those which are illustrated, or may be performed concurrently.
  • Further, in FIG. 2-5 and in the figures to follow thereafter, various operations may be depicted in a box-within-a-box manner. Such depictions may indicate that an operation in an internal box may comprise an optional example embodiment of the operational step illustrated in one or more external boxes. However, it should be understood that internal box operations may be viewed as independent operations separate from any associated external boxes and may be performed in any sequence with respect to all other illustrated operations, or may be performed concurrently.
  • In any event, after a start operation, the operational flow 2-500 may move to a reception operation 2-502 for receiving a request for one or more personalized plans designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans are emulated, the request identifying the one or more target outcomes. For instance, and as an illustration, the request reception module 2-102*(e.g., the request reception module 2-102, the request reception module 2-102′, or the request reception module 2-102″) of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving a request 2-12*(e.g., via a wireless network and/or wired network 2-50* or via a user interface 2-120*) for one or more personalized plans 2-16* designed to facilitate an end user 2-4* to achieve one or more target outcomes when one or more emulatable aspects (e.g., one or more behaviors, one or more acts, one or more beliefs, one or more traits, and/or other types of characteristics or traits) indicated by the one or more personalized plans 2-16* are emulated, the request 2-12* identifying the one or more target outcomes (e.g., weight loss, development or improvement of user skills such as work skills, athletic or game skills, or social skills, developing or having particular subjective user states such as well-rested and/or well-being, and so forth). Note that in various implementations, the request 2-12* may not specify or identify any source user 2-2** (e.g., source user 2-2 a, source user 2-2 b, source user 2-2 a′, source user 2-2 b′, and so forth). Instead, the development of the one or more personalized plans 2-16* may at least be prompted by the identification of the one or more target outcomes by the request 2-12*. The identification of the one or more target outcomes may be made by various means including, for example, textual or audio descriptions of the one or more target outcomes, textual or audio names of the one or more target outcomes, images such as digital images of the target outcomes as displayed by a source user 2-2**, and so forth.
  • Operational flow 2-500 may also include a seeking operation 2-504 for seeking one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, of the local source user device 2-20′ of FIG. 2-2 b, or of the local end user device 2-30″ of FIG. 2-3 b seeking (e.g., searching in a memory 2-116* and/or searching through a wireless network and/or wired network 2-50*) one or more reported aspects 2-14 that are relevant (e.g., as indicated by a source user 2-2**, an end user 24*, a third party 2-6*, one or more third party sources such as a publication or research, or based on other factors) to achieving the one or more target outcomes in response to receiving the request 2-12*.
  • Finally, operational flow 2-500 may include a development operation 2-506 for developing the one or more personalized plans based, at least in part, on the seeking. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1 b, of the local source user device 2-20′ of FIG. 2-2 b, or of the local end user device 2-30″ of FIG. 2-3 b developing (e.g., creating) the one or more personalized plans 2-16* based, at least in part, on the seeking
  • In various implementations, the reception operation 2-502 of FIG. 2-5 may be executed in a number of different ways as illustrated in FIGS. 2-6 a, 2-6 b, 2-6 c, 2-6 d, 2-6 e, and 2-6 f. For example, the request 2-12* received through the reception operation 2-502 may be received by various means depending upon, for example, whether the operation is being implemented at a server 2-10 (e.g., as in the embodiment depicted in FIGS. 2-1 a and 2-1 b), at a local source user device 2-20′ (e.g., as in the embodiment depicted in FIGS. 2-2 a and 2-2 b), or at a local end user device 2-30″ (e.g., as in the embodiment depicted in FIGS. 2-3 a and 2-3 b). For example, in some implementations the reception operation 2-502 may include an operation 2-602 for receiving the request via a user interface as depicted in FIG. 2-6 a. For instance, the user interface reception module 2-203″ of the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12″ via a user interface 2-120″ (e.g., an audio system including a microphone, a keypad, a touchscreen, a mouse, and so forth).
  • Alternatively, the reception operation 2-502 may include an operation 2-603 for receiving the request via at least one of a wireless network and a wired network as depicted in FIG. 2-6 a. For instance, the network interface reception module 2-202* (e.g., network interface reception module 2-202 or network interface reception module 2-202′) of the server 2-10 of FIG. 2-1 b or the local source user device 2-20′ of FIG. 2-2 b receiving the request 2-12*(e.g., request 2-12 or request 2-12′) via at least one of wireless network and a wired network 2-50*.
  • The request 2-12* may be received from a variety of sources in various alternative implementations. For example, in some implementations the reception operation 2-502 may include an operation 2-604 for receiving the request from the end user as depicted in FIG. 2-6 a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* from the end user 2-4*. For example, in the embodiment depicted in FIGS. 2-1 a and 2-1 b the request reception module 2-102 of the server 2-10 receiving the request 2-12 from the end user 2-4 via a wireless network and/or wired network 2-50. In the embodiment depicted in FIGS. 2-3 a and 2-3 b the request reception module 2-102″ of the local end user device 2-30″ receiving the request 2-12″ from the end user 2-4″ via a user interface 2-120″. Note that in various alternative implementations, the request 2-12* may not specifically identify a source user 2-2**, but instead may merely identify one or more target outcomes.
  • In some implementations, the reception operation 2-502 may include an operation 2-605 for receiving the request from one or more third parties as depicted in FIG. 2-6 a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* from one or more third parties 2-6*(e.g., network service provider, content provider, social networking sites, other end users, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-606 for receiving the request from one or more remote network devices as depicted in FIG. 2-6 a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* from one or more remote network devices. For example, in the case of the request reception module 2-102 of the server 2-10 of FIGS. 2-1 a and 2-1 b receiving the request 2-12 from a local end user device 2-30 or from a network server 2-60.
  • In some implementations, operation 2-606 may include an operation 2-607 for receiving the request from one or more network servers as depicted in FIG. 2-6 a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* from one or more network servers 2-60*.
  • The one or more personalized plans 2-16* that may be requested may be designed to achieve one or more of a wide variety of target outcomes. For example, in some implementations, the reception operation 2-502 may include an operation 2-608 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more health or medical outcomes as depicted in FIG. 2-6 b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 24* to achieve the one or more target outcomes including one or more health or medical outcomes (e.g., recovery time or recovery success related to an illness, weight loss, blood pressure reduction, blood glucose level reduction, lifespan, and so forth).
  • Operation 2-608 may in turn include one or more additional operations in various implementations. For example, in some implementations, operation 2-608 may include an operation 2-609 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more physiological outcomes as depicted in FIG. 2-6 b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 24* to achieve the one or more target outcomes including one or more physiological outcomes (e.g., reducing blood pressure or blood glucose levels, increase red blood cell count, improve and so forth).
  • In the same or different implementations, operation 2-608 may include an operation 2-610 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more physical fitness outcomes as depicted in FIG. 2-6 b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more physical fitness outcomes (e.g., reduced body fat level, increased lung air capacity, reduce time it takes to run a mile, increase amount of sit-ups or push-ups, and so forth).
  • In the same or different implementations, operation 2-608 may include an operation 2-611 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more medical treatment outcomes as depicted in FIG. 2-6 b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more medical treatment outcomes (e.g., improved recovery from stroke or other types of disease, reduction of side-effects from a medical treatment such as chemotherapy, and so forth).
  • In the same or different implementations, operation 2-608 may include an operation 2-612 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more physical fitness training outcomes as depicted in FIG. 2-6 b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more physical fitness training outcomes (e.g., reduce soreness from exercising, improve results of a training program, and so forth).
  • In the same or different implementations, operation 2-608 may include an operation 2-613 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more fitness life style outcomes as depicted in FIG. 2-6 b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more fitness life style outcomes (e.g., quit smoking, getting regular eight hours of nightly sleep, sticking with a vegan or low carbohydrate diet, and so forth).
  • In some implementations, the reception operation 2-502 of FIG. 2-5 may include an operation 2-614 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more athletic outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more athletic outcomes (e.g., improve golf scores, win a bicycle or swimming race, develop a curve ball pitch, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-615 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more gaming outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes related to one or more gaming outcomes (e.g., winning a chest tournament or improve video gaming skills).
  • In some implementations, the reception operation 2-502 may include an operation 2-616 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more work outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more work outcomes (e.g., a job promotion, finish a project on time, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-617 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more social outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more social outcomes (e.g., attaining a certain social class, having a dinner date with a particular person, developing a particular reputation, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-618 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more leisure outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more leisure outcomes (e.g., learn how to knit, finding time to go on vacation, finish reading a book, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-619 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more sexual intimacy outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more sexual intimacy outcomes (e.g., increased sexual activities, increased sexual performance, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-620 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more psychological outcomes as depicted in FIG. 2-6 c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more psychological outcomes (e.g., overcoming a phobia, overcoming certain addictive behavior such as compulsion to be clean, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-621 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user states as depicted in FIG. 2-6 d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 24* to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user states. A subjective user state may be any user state or status associated with a user that may generally only be subjectively indicated by the user. The one or more personalized plans 2-16* that may be requested may be designed to facilitate the end user 2-4* to achieve various types of subjective user states in various alternative implementations.
  • For example, in some implementations, operation 2-621 may include an operation 2-622 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user mental states as depicted by FIG. 2-6 d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-2* for the one or more personalized plans 2-16* designed to facilitate the end user 24* to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user mental states (e.g., happiness, alertness, clarity of thinking, calmness, and so forth). A subjective user mental state is any subjective user state related to any mental aspect of a subject (e.g., user).
  • In the same or different implementations, operation 2-621 may include an operation 2-623 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user physical states as depicted in FIG. 2-6 d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user physical states (e.g., physical fatigue, pain, blurry vision, and so forth). A subjective user physical state is any subjective user state related to any physical aspect of a subject (e.g., user).
  • In the same or different implementations, operation 2-621 may include an operation 2-624 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user overall states as depicted in FIG. 2-6 d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 24* to achieve the one or more target outcomes including one or more outcomes related to one or more subjective user overall states (e.g., “good,” “bad.” “well,” “tired,” “available,” “busy,” and so forth). A subjective user overall state is any subjective user state related to a subject and is not a subjective user mental state or a subjective user physical state.
  • In some implementations, the reception operation 2-502 of FIG. 2-5 may include an operation 2-625 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more outcomes related to one or more user social states as depicted in FIG. 2-6 d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more outcomes related to one or more user social states (e.g., membership to a social group, being married, being single and so forth).
  • In some implementations, the reception operation 2-502 of FIG. 2-5 may include an operation 2-626 for receiving the request for the one or more personalized plans designed to facilitate the end user to achieve the one or more target outcomes including one or more outcomes related to one or more user employment states as depicted in FIG. 2-6 d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16* designed to facilitate the end user 2-4* to achieve the one or more target outcomes including one or more outcomes related to one or more user employment states (e.g., being employed, attaining a particular employment position, attaining managerial authority, and so forth).
  • In some implementations, the reception operation 2-502 of FIG. 2-5 may include an operation 2-627 for receiving the request for the one or more personalized plans, the request including one or more identifiers associated with the one or more target outcomes as depicted in FIG. 2-6 e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* including one or more identifiers (e.g., one or more images of a source user 2-2* showing the one or more desired or target outcomes, textual or audio indications of the one or more target outcomes, and so forth) associated with the one or more target outcomes.
  • In some implementations, the reception operation 2-502 of FIG. 2-5 may include an operation 2-628 for receiving the request for the one or more personalized plans, the request not identifying any source user as depicted in FIG. 2-6 e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* not identifying any source user 2-2**. For these implementations, the development of the one or more personalized plans 2-16* may be based primarily on the identification of the one or more target outcomes (e.g., as identified in the request 2-12*) and may not rely on any identification of any source user 2-2**.
  • In alternative implementations, however, the request 2-12* received through the reception operation 2-502 of FIG. 2-5 may identify one or more source users 2-2*. For example, in some implementations, the reception operation 2-502 may include an operation 2-629 for receiving the request for the one or more personalized plans, the request identifying one or more source users as depicted in FIG. 2-6 e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* identifying one or more source users 2-2*.
  • In some implementations, operation 2-629 may, in turn, include an operation 2-630 for receiving the request for the one or more personalized plans, the request including one or more identifiers associated with the one or more source users as depicted in FIG. 2-6 e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* including one or more identifiers associated with the one or more source users 2-2*(e.g., one or more images of the one or more source users 2-2*, voice identifications of the one or more source users 2-2*, user names of the one or more source users 2-2*, actual names of the one or more source users 2-2*, locational identification of the one or more source users 2-2*, radio frequency identifications (RFIDs) of the one or more source users 2-2*, and so forth).
  • In some implementations, the reception operation 2-502 may include an operation 2-631 for receiving the request for the one or more personalized plans, the request identifying one or more source user groups as depicted in FIG. 2-6 e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* identifying one or more source user groups (e.g., one or more social networking groups, one or more ethnic or cultural groups, a gender group, one or more business groups, one or more medical patient groups, and so forth).
  • Operation 2-631, in turn, may further include an operation 2-632 for receiving the request for the one or more personalized plans, the request identifying one or more source user groups that share at least one common trait with the end user as depicted in FIG. 2-6 e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* identifying one or more source user groups that share at least one common trait (e.g., one or more physical characteristics, one or more ailments or illnesses, one or more handicaps, one or more social or employment status, belonging to the same social networking groups, and so forth) with the end user 2-4*.
  • Various other types of information may be indicated by the request 2-12* received through the reception operation 2-502 of FIG. 2-5 in various alternative implementations. For example, in some implementations, the reception operation 2-502 may include an operation 2-633 for receiving the request for the one or more personalized plans, the request indicating one or more preferences of the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more preferences (e.g., preference not to eat meats, preference not to exercise on Mondays, preference to sleep late on Fridays, and so forth) of the end user 2-4*.
  • In the same or different implementations, the reception operation 2-502 of FIG. 2-5 may include an operation 2-634 for receiving the request for the one or more personalized plans, the request indicating one or more limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more limitations (e.g., physical limitations, logistical limitations, asset limitations, and so forth) associated with the end user 2-4*.
  • Operation 2-634 may, in turn, further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 2-634 may include an operation 2-635 for receiving the request for the one or more personalized plans, the request indicating one or more physical limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more physical limitations (e.g., visual or hearing limitations, physical movement limitations such as those related to a paraplegic, physical characteristic limitations such as height, weight, and so forth, related to the end user 2-4*, physiological limitations such as cholesterol levels, and so forth) associated with the end user 2-4*.
  • In the same or different implementations, operation 2-634 may include an operation 2-636 for receiving the request for the one or more personalized plans, the request indicating one or more contextual limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more contextual limitations (e.g., scheduling limitations, geographical limitations, asset limitations such as lack of particular equipment or facilities, and so forth) associated with the end user 2-4*.
  • In the same or different implementations, operation 2-634 may include an operation 2-637 for receiving the request for the one or more personalized plans, the request indicating one or more personal limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more personal limitations (e.g., religious beliefs, dietary beliefs, phobias, personal prejudices, limitations related to personal experiences, personal work schedule obligations, family dynamics or circumstances, and so forth) associated with the end user 2-4*.
  • In the same or different implementations, operation 2-634 may include an operation 2-638 for receiving the request for the one or more personalized plans, the request indicating one or more medical or health limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more medical or health limitations (e.g., medical limitations such as limitations resulting from an illness or treatment of an illness including physical limitations due to cancer or treatment of cancer, health limitations related to the physical conditioning of the end user 2-4*, genetic limitations, and so forth) associated with the end user 2-4*.
  • In the same or different implementations, operation 2-634 may include an operation 2-639 for receiving the request for the one or more personalized plans, the request indicating one or more user state limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more user state limitations associated with the end user 2-4*(e.g., end user 2-4* is married, end user 2-4* is in mourning, end user 2-4* is unemployed, end user 2-4* is a vegan, and so forth).
  • In the same or different implementations, operation 2-634 may include an operation 2-640 for receiving the request for the one or more personalized plans, the request indicating one or more legal or regulatory limitations associated with the end user as depicted in FIG. 2-6 f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b receiving the request 2-12* for the one or more personalized plans 2-16*, the request 2-12* indicating one or more legal or regulatory limitations associated with the end user 2-4*(e.g., drug regulations or laws, laws related to conduct or behavior in the jurisdiction of the end user 2-4*, and so forth).
  • Referring back to the seeking operation 2-504 of FIG. 2-5, the seeking operation 2-504 may be executed in a variety of different ways in various alternative implementations. For example, in some implementations, the seeking operation 2-504 may include an operation 2-741 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes from a plurality of reported aspects as depicted in FIG. 2-7 a. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes from a plurality of reported aspects 2-15. For these implementations, the plurality of reported aspects 2-15 to be searched, which may include reported aspects associated with one or more source users 2-2* and which may include both reported aspects that may be relevant to achieving the one or more target outcomes and reported aspects that may not be relevant to achieving the one or more target outcomes, may be in memory 2-116* and/or at one or more remote network sites (e.g., in the case of the first exemplary environment of FIGS. 2-1 a and 2-1 b, one or more network servers 2-60 or one or more local source user devices 2-20).
  • In some implementations, operation 2-741 may include an operation 2-742 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes from a plurality of reported aspects that includes at least a first one or more reported aspects that are relevant to achieving the one or more target outcomes and a second one or more reported aspects that are not relevant to achieving the one or more target outcomes as depicted in FIG. 2-7 a. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes from a plurality of reported aspects that includes at least a first one or more reported aspects that are relevant to achieving the one or more target outcomes and a second one or more reported aspects that are not relevant to achieving the one or more target outcomes.
  • In some implementations, operation 2-741 may include an operation 2-743 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking a first one or more reported aspects associated with a first source user and a second one or more reported aspects associated with a second source user from the plurality of reported aspects, the first one or more reported aspects and the second one or more reported aspects being relevant to achieving the one or more target outcomes as depicted in FIG. 2-7 a. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking a first one or more reported aspects associated with a first source user 2-2 a* and a second one or more reported aspects associated with a second source user 2-2 b* from the plurality of reported aspects 2-15, the first one or more reported aspects and the second one or more reported aspects being relevant to achieving the one or more target outcomes. Thus, in operation 2-743 multiple reported aspects may be found that are associated with multiple source users.
  • In some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-744 for searching for the one or more reported aspects that are relevant to achieving the one or more target outcomes via at least one of a wireless network and a wired network as depicted in FIG. 2-7 b. For instance, the network searching module 2-204* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b searching (e.g., transmitting an inquiry or a solicitation) for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes via at least one of a wireless network and a wired network 2-50*.
  • Operation 2-744 may in turn include one or more additional operations in various alternative implementations. For example, in some implementations, operation 2-744 may include an operation 2-745 for transmitting a solicitation for the one or more reported aspects that are relevant to achieving the one or more target outcomes via the at least one of a wireless network and a wired network as depicted in FIG. 2-7 b. For instance, the solicitation transmission module 2-206*(see FIG. 2-4 a) of the server 2-10 (of FIG. 2-1 b), the local source user device 2-20′ (of FIG. 2-2 b), or the local end user device 2-30″ (of FIG. 2-3 b) transmitting a solicitation 2-13* for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes via the at least one of a wireless network and a wired network 2-50*.
  • In the same or different implementations, operation 2-744 may include an operation 2-746 for transmitting a solicitation for the one or more reported aspects that are relevant to achieving the one or more target outcomes to one or more remote network devices as depicted in FIG. 2-7 b. For instance, the solicitation transmission module 2-206* of the server 2-10 (of FIG. 2-1 b), the local source user device 2-20′ (of FIG. 2-2 b), or the local end user device 2-30″ (of FIG. 2-3 b) transmitting a solicitation 2-13* for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes to one or more remote network devices (e.g., in the embodiment depicted in FIGS. 2-1 a and 2-1 b, transmitting the solicitation 2-13 to one or more local source user devices 2-20, to one or more sensors 2-40, or to one or more network servers 2-60).
  • Operation 2-746 may, in turn, include an operation 2-747 for transmitting the solicitation for the one or more reported aspects that are relevant to achieving the one or more target outcomes to one or more local source user devices as depicted in FIG. 2-7 b. For instance, the solicitation transmission module 2-206* of the server 2-10 (of FIG. 2-1 b), the local source user device 2-20′ (of FIG. 2-2 b), or the local end user device 2-30″ (of FIG. 2-3 b) transmitting the solicitation 2-13* for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes to one or more local source user devices 2-20*(e.g., in the embodiment depicted in FIGS. 2-1 a and 2-1 b, the server 2-10 transmitting the solicitation 2-13 to one or more local source user devices 2-20).
  • In the same or different implementations, operation 2-746 may include an operation 2-748 for transmitting the solicitation for the one or more reported aspects that are relevant to achieving the one or more target outcomes to one or more network servers as depicted in FIG. 2-7 b. For instance, the solicitation transmission module 2-206* of the server 2-10 (of FIG. 2-1 b), the local source user device 2-20′ (of FIG. 2-2 b), or the local end user device 2-30″ (of FIG. 2-3 b) transmitting the solicitation 2-13* for the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes to one or more network servers 2-60*(e.g., in the embodiment depicted in FIGS. 2-3 a and 2-3 b, the local end user device 2-30″ transmitting the solicitation 2-13″ to one or more network servers 2-60″).
  • In various implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-749 for searching a memory for the one or more reported aspects associated with at least the one or more target outcomes as depicted in FIG. 2-7 b. For instance, the memory searching module 2-208* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b searching a memory 2-116* for the one or more reported aspects 2-14* associated with at least the one or more target outcomes.
  • One or more reported aspects 2-14* may be deemed to be relevant to the achievement of the one or more target outcomes based on a number of different factors including, for example, whether the one or more reported aspects 2-14* are associated with a specific source user 2-2* or a group of source users 2-2*. Such a source user 2-2* or group of source users 2-2* may have been identified by, for example, the end user 2-4* or by one or more third parties 2-6*, or may be further associated with, for example, one or more reported outcomes that corresponds to the one or more target outcomes (e.g., in other words, whether the reported aspects 2-14* are associated with a specific user or a group of source users who have reported (e.g., via reported outcomes) that they have achieved the one or more target outcomes).
  • For example, in some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-750 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that are particularly associated with a particular source user as depicted in FIG. 2-7 c. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that are particularly associated with a particular source user (e.g., source user 2-2 a* or source user 2-2 b*).
  • In various implementations, the seeking operation 2-504 may include an operation 2-751 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that are particularly associated with a plurality of particular source users as depicted in FIG. 2-7 c. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that are particularly associated with a plurality of particular source users (e.g., source users 2-2*).
  • In some implementations, operation 2-751 may further include an operation 2-752 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that are particularly associated with a plurality of particular source users that share at least one common trait with the end user as depicted in FIG. 2-7 c. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that are particularly associated with a plurality of particular source users (e.g., source users 2-2*) that share at least one common trait (e.g., physical characteristic, physical handicap, illness, ethnic, religious, or cultural belief, and so forth) with the end user 24*.
  • The one or more reported aspects 2-14 to be found through the seeking operation 2-504 of FIG. 2-5 may have been at least originally reported via various means. For example, in some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-753 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that were at least originally reported through one or more log entries as depicted in FIG. 2-7 d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that were at least originally reported through one or more log entries (e.g., electronic log entries as entered by, for example, a source user 2-2* or a sensor 2-40*).
  • In various implementations, operation 2-753 may further include one or more additional operations. For example, in some implementations, operation 2-753 may include an operation 2-754 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that were at least originally reported through one or more social networking entries as depicted in FIG. 2-7 d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that were at least originally reported through one or more social networking entries.
  • The one or more reported aspects 2-14* to be found through operation 2-754 may have been originally reported via various social networking means. For example, in some implementations, operation 2-754 may include an operation 2-755 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that were at least originally reported through one or more blog entries as depicted in FIG. 2-7 d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that were at least originally reported through one or more blog entries (e.g., microblog entries).
  • In some implementations, operation 2-754 may include an operation 2-756 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that were at least originally reported through one or more status reports as depicted in FIG. 2-7 d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that were at least originally reported through one or more status reports.
  • In various implementations, operation 2-753 may include an operation 2-757 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that were at least originally reported through one or more diary entries as depicted in FIG. 2-7 d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that were at least originally reported through one or more diary entries, which in some cases may be stored in a memory 2-116*.
  • In some implementations, operation 2-753 may include an operation 2-758 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects that were at least originally reported through one or more log entries as provided by one or more sensors as depicted in FIG. 2-7 d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes by seeking one or more reported aspects 2-14* that were at least originally reported through one or more log entries as provided by one or more sensors 2-40*(e.g., physiological sensors such as heart rate monitors or blood glucose meter, user activity sensors such as those that detect a user's toilet use or sensors that detects exercise activities of a user such as a pedometer, and so forth).
  • In order to seek the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes, one or more reported outcomes that corresponds to the one or more target outcomes may be initially identified. For example, in some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-759 for identifying one or more reported outcomes that correspond to the one or more target outcomes to facilitate the seeking as depicted in FIG. 2-7 e. For instance, the reported outcome identification module 2-210*(see FIG. 2-4 a) of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying one or more reported outcomes that correspond to the one or more target outcomes to facilitate the seeking
  • In various implementations, once the one or more reported outcomes that correspond to the one or more target outcomes have been identified, other operations may be executed. For example, in some implementations, operation 2-759 may further include an operation 2-760 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying the one or more reported aspects that indicates one or more aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of the one or more reported outcomes as depicted in FIG. 2-7 e. For instance, the reported aspect identification module 2-212*(see FIG. 2-4 a) of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14*(e.g., dietary behavior) that are relevant to achieving the one or more target outcomes (e.g., losing 20 pounds of weight) including identifying one or more reported aspects 2-14* that indicates one or more aspects that occurred within one or more predefined time periods (e.g., two months), respectively, from one or more occurrences of the one or more reported outcomes. As a further example, the reported aspect identification module 2-212* identifying one or more reported aspects 2-14* related to the dietary behavior (e.g., eating behavior) of one or more source users 2-2* and that occurred within two months of occurrences of 20 pounds of weight loss (e.g., reported outcomes or target outcomes) reported by the one or more source users 2-2*.
  • In some implementations, operation 2-760 may further include an operation 2-761 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying the one or more reported aspects that indicates one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of the one or more reported outcomes as depicted in FIG. 2-7 e. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14* that indicates one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of the one or more reported outcomes. As a further example, suppose an end user 2-4* is interested in the dietary behaviors of those who have lost a total of 20 pounds of weight loss during the two months preceding the weight loss. The reported aspect identification module 2-212* may then identify one or more reported aspects 2-14* that are related to the dietary behavior (e.g., eating behavior) of one or more source users 2-2* that occurred prior to and within two months of occurrences of 20 pounds of weight loss (e.g., reported outcomes or target outcomes) reported by the one or more source users 2-2*.
  • In some implementations, operation 2-759 may include an operation 2-762 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with a source user who is also associated with the one or more reported outcomes as depicted in FIG. 2-7 e. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14* that are particularly associated with a source user 2-2* who is also associated with the one or more reported outcomes. As a further example, the reported aspect identification module 2-212* identifying one or more reported aspects 2-14* that are particularly associated with a source user 2-2 a* (e.g., reading one book per week by the source user 2-2 a*) who is also associated with the one or more reported outcomes (e.g., improve SAT reading score).
  • In various alternative implementations, operation 2-759 for identifying one or more reported outcomes may further include one or more operations to identify one or more reported aspects 2-14 that are associated with one or more members of a source user group. For example, in various implementations, operation 2-759 may include an operation 2-763 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a source user group, the one or more members of the source user group having at least one common trait and being further associated with the one or more reported outcomes as depicted in FIG. 2-7 f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14* that are particularly associated with one or more members of a source user group (e.g., social networking group, ethnic, cultural, or religious groups, health group, belief groups, and so forth), the one or more members of the source user group having at least one common trait and being further associated with the one or more reported outcomes.
  • In some implementations, operation 2-763 may include an operation 2-764 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a social networking group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14* that are particularly associated with one or more members of a social networking group, the one or more members being further associated with the one or more reported outcomes. As a further illustration, the reported aspect identification module 2-212* identifying reported aspects (e.g., study habits) that are particularly associated with members of a social networking group (e.g., classmates), the members being further associated with the one or more reported outcomes (e.g., passing a calculus exam) that corresponds to the one or more target outcomes.
  • In some implementations, operation 2-763 may include an operation 2-765 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of an ethnic, religious, or social group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., relatively low white rice consumption) that are particularly associated with one or more members of an ethnic, religious, or social group (e.g., Asian ancestry), the one or more members being further associated with the one or more reported outcomes (e.g., low blood glucose levels).
  • In some implementations, operation 2-763 may include an operation 2-766 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a gender or age group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., Omega-3 consumption) that are particularly associated with one or more members of a gender or age group (e.g., over 65 years of age), the one or more members being further associated with the one or more reported outcomes (e.g., reduced arthritic conditions).
  • In some implementations, operation 2-763 may include an operation 2-767 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a health-related group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., marijuana usage) that are particularly associated with one or more members of a health-related group (e.g., cancer patients being treated by chemotherapy), the one or more members being further associated with the one or more reported outcomes (e.g., reduction in nausea).
  • In some implementations, operation 2-763 may include an operation 2-768 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of an educational or academic group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., being tutored by a particular tutor) that are particularly associated with one or more members of an educational or academic group (e.g., students at a particular engineering school) the one or more members being further associated with the one or more reported outcomes (e.g., understanding thermodynamics).
  • In some implementations, operation 2-763 may include an operation 2-769 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a fitness or athletic group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., amount of sit-ups done daily) that are particularly associated with one or more members of a fitness or athletic group (e.g., members of a particular gym), the one or more members being further associated with the one or more reported outcomes (e.g., 28 inch waist).
  • In some implementations, operation 2-763 may include an operation 2-770 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a social status group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., behavior towards a boyfriend) that are particularly associated with one or more members of a social status group (e.g., single women), the one or more members being further associated with the one or more reported outcomes (e.g., diamond ring).
  • In some implementations, operation 2-763 may include an operation 2-771 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects that are particularly associated with one or more members of a work or employment group, the one or more members being further associated with the one or more reported outcomes as depicted in FIG. 2-7 g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1 b, the local source user device 2-20′ of FIG. 2-2 b, or the local end user device 2-30″ of FIG. 2-3 b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying one or more reported aspects 2-14*(e.g., attendance at company functions) that are particularly associated with one or more members of a work or employment group (e.g., employees at the