TEMPLATE DEVELOPMENT BASED ON REPORTED ASPECTS OF A PLURALITY OF SOURCE USERS

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

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 1b 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. 1b.

FIG. 2 b shows another perspective of the Template Developing Module 104 of the Computing Device 10 of FIG. 1b.

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. 1b.

FIGS. 1-1 a and 1-1b show a high-level block diagram of a server 1-10 operating in a network environment.

FIGS. 1-1 c and 1-1d 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-1f 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-1b, of the local source user device 1-20′ of FIG. 1-1d, and of the local end user device 1-30″ of FIG. 1-1f.

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-1b show a high-level block diagram of a server 2-10 operating in a network environment.

FIGS. 2-2 a and 2-2b 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-3b 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-1b, of the local source user device 2-20′ of FIG. 2-2b, and of the local end user device 2-30″ of FIG. 2-3b.

FIG. 2-4 b shows another perspective of the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, of the local source user device 2-20′ of FIG. 2-2b, and of the local end user device 2-30″ of FIG. 2-3b.

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-1b show a high-level block diagram of a server 3-10 operating in a network environment.

FIGS. 3-2 a and 3-2b 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-3b 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-1b, of the local source user device 3-20′ of FIG. 3-2b, and of the local end user device 3-30″ of FIG. 3-3b.

FIG. 3-4 b shows another perspective of the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, of the local source user device 3-20′ of FIG. 3-2b, and of the local end user device 3-30″ of FIG. 3-3b.

FIG. 3-4 c shows one perspective of one of the sensing devices 3-40* of the first exemplary environment of FIGS. 3-1a and 3-1b, of the second exemplary environment of FIGS. 3-2a and 3-2b, and of the third exemplary environment of FIGS. 3-3a and 3-3b.

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-1b 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-1b.

FIG. 4-2 b shows another perspective of the personalized plan development module 4-104 of the computing device 4-10 of FIG. 4-1b.

FIG. 4-2 c shows one perspective of one of the sensing devices 4-40 of the environment of FIGS. 4-1a and 4-1b.

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-1b.

FIGS. 5-1 a and 5-1b 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-1b.

FIG. 5-2 b shows another perspective of the personalized plan development module 5-104 of the computing device 5-10 of FIG. 5-1b.

FIG. 5-2 c shows one perspective of one of the sensing devices 5-40 of the environment of FIGS. 5-1a and 5-1b.

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-1b.

FIGS. 6-1 a and 6-1b 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-1b.

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-1b.

FIG. 6-2 c shows one perspective of one of the sensing devices 6-40 of the environment of FIGS. 6-1a and 6-1b.

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-1b.

FIGS. 7-1 a and 7-1b 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-1b.

FIG. 7-2 b shows another perspective of the template development module 7-104 of the computing device 7-10 of FIG. 7-1b.

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-1a and 7-1b.

FIG. 7-2 d shows one perspective of the one or more sensors 7-240*(e.g., one or more sensors 7-240a, one or more sensors 7-240b, or one or more sensors 7-240c) of the exemplary environment 7-100 of FIGS. 7-1a and 7-1b.

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-1b.

FIGS. 8-1 a and 8-1b 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-1b.

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-1b.

FIGS. 9-1 a and 9-1b 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-1b.

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-1b.

FIGS. 10-1 a and 10-1b 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-1b.

FIG. 10-2 b shows another perspective of the Action Executing Module 10-104 of the Computing Device 10-10 of FIG. 10-1b.

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-1b.

FIGS. 11-1 a and 11-1b 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-1b.

FIG. 11-2 b shows another perspective of the Template Modifying Module 11-104 of the Computing Device 11-10 of FIG. 11-1b.

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-1b.

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. 1a, and 1b 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. 1a. Alternatively, the computing device 10 may be a source user device such as one of the local source user devices 20* illustrated in FIG. 1a. 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. 1a. 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 2a, a source user 2b, a source user 2c, 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. 1a and 1b 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. 1a and 1b 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. 1a and 1b, 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 2a, source user 2b, source user 2c, source user 2d, and so forth) through one or more local source user devices 20*(e.g., local source user device 20a, local source user device 20b, and so forth), with a plurality of end users 4*(e.g., end user 4a, end user 4b, and so forth) through a plurality of local end user devices 30*(e.g., local end user device 30a, local end user device 30b, 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. 1a and 1b, in various embodiments the one or more sensor integrated devices 40 of the exemplary environment 100 of FIGS. 1a and 1b 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. 1b 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. 2a) and a template developing module 104 (which may also include one or more sub-modules as illustrated in FIG. 2b). 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. 1b. 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. 1b. 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. 1b, 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. 1b 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. 1a and 1b, and/or with respect to other examples (e.g., as provided in FIGS. 2a and 2b) 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. 1a, 1b, 2a, and 2b. 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. 1b 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. 4a, 4b, 4c, 4d, and 4e 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. 4a. For instance, the memory acquiring module 202 (see FIG. 2a) 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. 4a. For instance, the network acquiring module 204 (see FIG. 2a) 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. 4a. 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. 2a) 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. 4b. 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. 4b. For instance, the source user identifying module 210 (see FIG. 2a) 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. 4b. For instance, the “identified source user associated reported aspect providing” module 212 (see FIG. 2a) 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. 4b. For instance, the relevancy factor relevant reported aspect providing module 214 (see FIG. 2a) 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. 4b. 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. 4b. 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. 4b. 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. 4b. 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. 4b. 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. 4c. 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. 4c. 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. 4c. 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. 4c. 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. 4c. 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. 4c. 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. 4c. 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. 4c. 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. 4d. 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 2a 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 2b 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. 4d. 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. 4d. 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. 4d. 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. 4d. 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. 4e. 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. 4e. 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. 4e. 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. 4e. 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. 4e. 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. 5a. 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. 2b) 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. 5a. 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. 5a. 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. 2b) 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 2a and a second relevant reported aspect (e.g., jogging for 35 minutes) that is associated with a second source user 2b.

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. 5a. 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 2a and a fourth relevant reported aspect (e.g., jogging at a very slow pace) that is associated with the second source user 2b.

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. 5a. 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 2c and a fourth relevant reported aspect (e.g., swimming for one hour) that is associated with a fourth source user 2d.

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 2c) completely different from the fourth relevant reported aspect (of the fourth source user 2d). 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 2a and the second source user 2b 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. 5a. 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. 5a. 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. 5b. 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. 5b. 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. 5b. 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. 5b. 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. 5b. 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. 5b. 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. 5c. 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. 5c. 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. 5c. 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. 5c. 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. 5d. 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. 5d. 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. 5d. 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. 5e. 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. 5e. 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. 5e. 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. 5e. 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. 5e. 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. 5e. 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. 5e. 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. 5e. 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. 1b) 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. 1b. 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, 4a, 4b, 4c, 4d, 4e, 5a, 5b, 5c, 5d, 5e, 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-1a, 1-1b, 1-1c, 1-1d, 1-1e, and 1-1f, 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-1a and 1-1b 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-1c and 1-1d 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-1e and 1-1f 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-1a and 1-1b, to server 1-10′ of the second example environment of FIGS. 1-1c and 1-1d, or to server 1-10″ of the third example environment of FIGS. 1-1e and 1-1f.

In various embodiments, the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, and the local end user device 1-30″ of FIG. 1-1f 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-1a and 1-1b illustrated the first example environment in accordance with various embodiments. Included in the illustrated first environment of FIGS. 1-1a and 1-1b is a first exemplary system 1-100, which includes at least a server 1-10 (see FIG. 1-1b) 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-1b (as well as the server 1-10′ of FIG. 1-1c and the server 1-10″ of FIG. 1-1e) 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-1d and the local source user device 1-20″ of FIG. 1-1e) and the local end user device 1-30 (as well as the local end user device 1-30′ of FIG. 1-1c 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-1d and the local source user device 1-20″ of FIG. 1-1e) and/or the local end user device 1-30 (as well as the local end user device 1-30′ of FIG. 1-1c 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-1c and the one or more sensors 1-40″ of FIG. 1-1e) 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-1a and 1-1b, 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-1b 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-1c and 1-1d, 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-1a and 1-1b. As illustrated, the second example environment of FIGS. 1-1c and 1-1d is similar to the first example environment of FIGS. 1-1a and 1-1b.

In general, the second example environment of FIGS. 1-1c and 1-1d may include a second exemplary system 1-100′, which includes at least a local source user device 1-20′ (see FIG. 1-1d). In various implementations, the local source user device 1-20′ as was the case for server 1-10 of FIGS. 1-1a and 1-1b 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-1a and 1-1b 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-1d, may include the same or similar modules, sub-modules, and components included in the server 1-10 of FIG. 1-1b. 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-1b.

Also similar to server 1-10 of FIG. 1-1b, 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-1b. 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-1e and 1-1f, 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-1a and 1-1b and FIGS. 1-1c and 1-1d. The third example environment of FIGS. 1-1e and 1-1f is similar to the first example environment of FIGS. 1-1a and 1-1b and the second example environment of FIGS. 1-1c and 1-1d 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-1a and 1-1b and as was the case for the local source user device 1-20′ of the second example environment of FIGS. 1-1c and 1-1d. However, and as with the server 1-10 and the local source user device 1-20′ of FIGS. 1-1b and 1-1d, 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-1e and 1-1f may include a third exemplary system 1-100″, which includes at least a local end user device 1-30″ (see FIG. 1-1f). 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-1d. 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-1d. Also similar to the local source user device 1-20′ of FIG. 1-1d, 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-1d. 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-1b, 1-1d, and 1-1f. 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-1b, the local source user device 1-20′ of FIG. 1-1d, and the local end user device 1-30″ of FIG. 1-1f 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f.

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-1a and 1-1b, FIGS. 1-1e and 1-1d, and FIGS. 1-1e and 1-1f, 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-1a to 1-1f, 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1b, of the local source user device 1-20′ of FIG. 1-1d, or of the local end user device 1-30″ of FIG. 1-1f 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-1b, of the local source user device 1-20′ of FIG. 1-1d, or of the local end user device 1-30″ of FIG. 1-1f 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-4a, 1-4b, 1-4c, 1-4d, and 1-4e. 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-1a and 1-1b), at a local source user device 1-20′ (e.g., as in the embodiment depicted in FIGS. 1-1c and 1-1d), or at a local end user device 1-30″ (e.g., as in the embodiment depicted in FIGS. 1-1e and 1-1f). 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-4a. 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-4a. 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-1b or the local source user device 1-20′ of FIG. 1-1d 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4a. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4b. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4c. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4c. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4c. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4d. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4d. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4d. For instance, the request reception module 1-102* of the server 1-10 (of FIG. 1-1b), the local source user device 1-20′ (of FIG. 1-1d), or the local end user device 1-30″ (of FIG. 1-1f) 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-4d. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4e. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4e. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-4e. For instance, the request reception module 1-102* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20 ′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1a and 1-1b, 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-5a. For instance, the request transmission module 1-204* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1e and 1-1f), 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5a. For instance, the request transmission module 1-204* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1c and 1-1d), 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-5a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b or the local source user device 1-20′ of FIG. 1-1d 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-5a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5a. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5a. For instance, the source user data acquisition module 1-104* of the server 1-10 (of FIG. 1-1b), the local source user device 1-20′ (of FIG. 1-1d), or the local end user device 1-30″ (of FIG. 1-1f) 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-5b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5b. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 (of FIG. 1-1b), the local source user device 1-20′ (of FIG. 1-1d), or the local end user device 1-30″ (of FIG. 1-1f) 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5c. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5d. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5d. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5d. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5e. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-5f. For instance, the source user data acquisition module 1-104* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6a. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6a. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6a. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6a. For example, the reported aspect relevancy requesting module 1-212* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6a. For instance, the reported aspect non-relevancy requesting module 1-214* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For example, the reported aspect relevancy requesting module 1-212* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For instance, the reported aspect non-relevancy requesting module 1-214* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For instance, the aspect type relevancy requesting module 1-216* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For instance, the relevant reported aspect determination module 1-208* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For instance, the aspect type non-relevancy requesting module 1-218* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6b. For instance, the relevant reported aspect determination module 1-208* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6c. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6d. 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-6d. For instance, the personalized plan development module 1-106* of the server 1-10 of FIG. 1-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1d or the local end user device 1-30″ of FIG. 1-1f 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1b, the local source user device 1-20′ of FIG. 1-1d, or the local end user device 1-30″ of FIG. 1-1f 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-1a, 2-1b, 2-2a, 2-2b, 2-3a, and 2-3b, 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-1a and 2-1b 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-2a and 2-2b 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-20a′. FIGS. 2-3a and 2-3b 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-1a and 2-1b, to the one or more source users 2-2′ of the second example environment of FIGS. 2-2a and 2-2b, or to the one or more source users 2-2″ of the third example environment of FIGS. 2-3a and 2-3b. 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-2a, source user 2-2b, source user 2-2a′, source user 2-2b′, source user 2-3a″, source user 2-3b″, and so forth) depicted in the three example environments of FIGS. 2-1a, 2-1b, 2-2a, 2-2b, 2-3a, and 2-3b.

In various embodiments, the server 2-10 of FIG. 2-1b, the local source user device 2-20a′ of FIG. 2-1d, and the local end user device 2-30″ of FIG. 2-1f 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-20a′, 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-20a′, 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-1a and 2-1b illustrated the first example environment in accordance with various embodiments. Included in the illustrated first environment of FIGS. 2-1a and 2-1b is a first exemplary system 2-100, which includes at least a server 2-10 (see FIG. 2-1b) 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-1b (as well as the one or more network servers 2-60* of FIGS. 2-1a, 2-2a, and 2-3b) 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-1b, 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-2a, a second source user 2-2b, a third source user 2-2c, a fourth source user 2-2d, and so forth. The one or more local source user devices 2-20 may include a first local source user device 2-20a (e.g., to be used by the first source user 2-2a to communicate via wireless network and/or wired network 2-50), a second local source user device 2-20b (e.g., to be used by the second source user 2-2b 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-2a and 2-2b and the one or more local source user devices 2-20″ of FIG. 2-3a) and the local end user device 2-30 (as well as the local end user device 2-30′ of FIG. 2-2a and the local end user device 2-30″ of FIG. 2-3b) 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-2a and 2-2b and the one or more local source user devices 2-20″ of FIG. 2-3a) and/or the local end user device 2-30 (as well as the local end user device 2-30′ of FIG. 2-2a and the local end user device 2-30″ of FIG. 2-2b) 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-2a and the one or more sensors 2-40″ of FIG. 2-3a) 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-1a and 2-1b, 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-1b 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-4a), a personalized plan development module 2-106 (which may further include one or more sub-modules as illustrated in FIG. 2-4b), 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-4b.

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-2a and 2-2b, 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-1a and 2-1b. As illustrated, the second example environment of FIGS. 2-2a and 2-2b is similar to the first example environment of FIGS. 2-1a and 2-1b.

In general, the second example environment of FIGS. 2-2a and 2-2b may include a second exemplary system 2-100′, which includes at least a local source user device 2-20a′ (see FIG. 2-2b). In various implementations, the local source user device 2-20a′, as was the case for server 2-10 of FIGS. 2-1a and 2-1b, 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-20a′ 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-20a′ 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-1a and 2-1b, 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-20a′ 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-2a′ (e.g., via user interface 2-120′), and/or one or more third parties 2-6′.

The local source user device 2-20a′, as illustrated in FIG. 2-2b, may include the same or similar modules, sub-modules, and other components included in the server 2-10 of FIG. 2-1b. As illustrated, the local source user device 2-20a′ 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-1b.

Also similar to server 2-10 of FIG. 2-1b, the local source user device 2-20a′ 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-20a′ may perform the same or similar functions as their counterparts that may be included in the server 2-10 of FIG. 2-1b. 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-3a and 2-3b, 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-20a″ as was the case in the first and second example environments of FIGS. 2-1a and 2-1b and FIGS. 2-2a and 2-2b. The third example environment of FIGS. 2-3a and 2-3b is similar to the first example environment of FIGS. 2-1a and 2-1b and the second example environment of FIGS. 2-2a and 2-2b 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-1a and 2-1b and as was the case for the local source user device 2-20a′ of the second example environment of FIGS. 2-2a and 2-2b. However, and as with the server 2-10 and the local source user device 2-20a′ of FIGS. 2-1b and 2-2b, 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-3a and 2-3b may include a third exemplary system 2-100″, which includes at least a local end user device 2-30″ (see FIG. 2-3b). 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-1a and 2-1b and the second exemplary environment of FIGS. 2-2a and 2-2b, 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-20a′ of FIG. 2-2b. 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-20a′ of FIG. 2-2b.

Also similar to the local source user device 2-20a′ of FIG. 2-2b, 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-20a′ of FIG. 2-2b. 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-1b, 2-2b, and 2-3b. 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-1a and 2-1b, 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-1b, 2-2b, and 2-3b. 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-1b, the local source user device 2-20a′ of FIG. 2-2b, 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-20a′, 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-1b, the local source user device 2-20a′ of FIG. 2-2b, and the local end user device 2-30″ of FIG. 2-3b 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-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b.

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-1a and 2-1b, FIGS. 2-2a and 2-2b, and FIGS. 2-3a and 2-3b, and/or with respect to other examples (e.g., as provided in FIGS. 2-4a and 2-4b) 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-1a, 2-1b, 2-2a, 2-2b, 2-3a, 2-3b, 2-4a and 2-4b. 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-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-2a, source user 2-2b, source user 2-2a′, source user 2-2b′, 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-1b, of the local source user device 2-20′ of FIG. 2-2b, or of the local end user device 2-30″ of FIG. 2-3b 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-1b, of the local source user device 2-20′ of FIG. 2-2b, or of the local end user device 2-30″ of FIG. 2-3b 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-6a, 2-6b, 2-6c, 2-6d, 2-6e, and 2-6f. 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-1a and 2-1b), at a local source user device 2-20′ (e.g., as in the embodiment depicted in FIGS. 2-2a and 2-2b), or at a local end user device 2-30″ (e.g., as in the embodiment depicted in FIGS. 2-3a and 2-3b). 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-6a. For instance, the user interface reception module 2-203″ of the local end user device 2-30″ of FIG. 2-3b 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-6a. 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-1b or the local source user device 2-20′ of FIG. 2-2b 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-6a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b receiving the request 2-12* from the end user 2-4*. For example, in the embodiment depicted in FIGS. 2-1a and 2-1b 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-3a and 2-3b 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-6a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-1a and 2-1b 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-6a. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6b. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6c. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6d. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6e. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-6f. For instance, the request reception module 2-102* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7a. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-1a and 2-1b, 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-7a. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7a. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-2a* and a second one or more reported aspects associated with a second source user 2-2b* 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-7b. For instance, the network searching module 2-204* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7b. For instance, the solicitation transmission module 2-206*(see FIG. 2-4a) of the server 2-10 (of FIG. 2-1b), the local source user device 2-20′ (of FIG. 2-2b), or the local end user device 2-30″ (of FIG. 2-3b) 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-7b. For instance, the solicitation transmission module 2-206* of the server 2-10 (of FIG. 2-1b), the local source user device 2-20′ (of FIG. 2-2b), or the local end user device 2-30″ (of FIG. 2-3b) 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-1a and 2-1b, 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-7b. For instance, the solicitation transmission module 2-206* of the server 2-10 (of FIG. 2-1b), the local source user device 2-20′ (of FIG. 2-2b), or the local end user device 2-30″ (of FIG. 2-3b) 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-1a and 2-1b, 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-7b. For instance, the solicitation transmission module 2-206* of the server 2-10 (of FIG. 2-1b), the local source user device 2-20′ (of FIG. 2-2b), or the local end user device 2-30″ (of FIG. 2-3b) 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-3a and 2-3b, 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-7b. For instance, the memory searching module 2-208* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7c. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-2a* or source user 2-2b*).

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-7c. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7c. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7d. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7e. For instance, the reported outcome identification module 2-210*(see FIG. 2-4a) of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7e. For instance, the reported aspect identification module 2-212*(see FIG. 2-4a) of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7e. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7e. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-2a* (e.g., reading one book per week by the source user 2-2a*) 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-7f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7f. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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-7g. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 same company), the one or more members being further associated with the one or more reported outcomes (e.g., promotion to managerial position).

In various implementations, operation 2-759 of FIGS. 2-7e, 2-7f, and 2-7g may include an operation 2-772 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 specific source user, the specific source user being further associated with the one or more reported outcomes as depicted in FIG. 2-7h. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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., sleep behavior) that are particularly associated with a specific source user 2-2a*, the specific source user 2-2a* being further associated with the one or more reported outcomes (e.g., feeling alert and energetic).

In some implementations, operation 2-759 may include an operation 2-773 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes including identifying a plurality of reported aspects that are particularly associated with specific source users, the specific source users being further associated with the one or more reported outcomes as depicted in FIG. 2-7h. For instance, the reported aspect identification module 2-212* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b identifying the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including identifying a plurality of reported aspects 2-14*(e.g., positive outlook) that are particularly associated with specific source users 2-2*(e.g., formerly unemployed workers), the specific source users 2-2* being further associated with the one or more reported outcomes (e.g., getting a job or having a successful job interview).

In various implementations, the one or more reported aspects 2-14* to be found through the seeking operation 2-504 of FIG. 2-5 may include one or more reported aspects 2-14* that may comply with one or more preferences and/or limitations of the end user 2-4*. For example, in some implementations, operation 2-759 may include an operation 2-774 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 complies with one or more preferences of the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7h. For instance, the preference compliant reported aspect identification module 2-213* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b identifying the one or more reported aspects 2-4* 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 (e.g., types of reported aspects that are of interest) of the end user 2-4* and that are associated with the one or more reported outcomes. For example, the end user 2-4* may only be interested in the sleep patterns of source users 2-2* who have lost 30 pounds of weight (e.g., target outcome). Under such circumstances, the preference compliant reported aspect identification module 2-213* may only be configured to identify those reported aspects 2-14* that relate to sleep activities. Thus, for these implementations, the preference compliant reported aspect identification module 2-213* may be designed to only identify the types of reported aspects that the end user 2-4* may have an interest in with respect to the achievement of the one or more target outcomes.

Alternatively or in the same implementations, operation 2-759 may include an operation 2-775 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 complies with one or more limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7i. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with (e.g., does not violate) one or more limitations associated with the end user 2-4*(e.g., end user 2-4* is a vegan, end user 2-4* has a physical handicap that prevents her from participating in certain activities, end user 2-4* lives in Singapore so does not have access to chewing gum, and so forth) and that are associated with the one or more reported outcomes.

Operation 2-775 may, in turn, include one or more additional operations in various alternative implementations. For example, in some implementations, operation 2-775 may include an operation 2-776 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 complies with one or more physical limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7i. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more physical limitations (e.g., visual handicap, hearing handicap, missing limbs or paralysis, and so forth) associated with the end user 2-4* and that are associated with the one or more reported outcomes.

In some implementations, operation 2-775 may include an operation 2-777 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 complies with one or more contextual limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7i. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more contextual limitations (e.g., logistical limitations such as the geographical location of the end user 2-4* that prevents the end user 2-4* from participating in certain activities or work or family situations that prevents the end user 2-4* from participating in certain activities) associated with the end user 2-4* and that are associated with the one or more reported outcomes.

In some implementations, operation 2-775 may include an operation 2-778 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 complies with one or more personal limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7i. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more personal limitations (e.g., limitations related to religious beliefs, spiritual beliefs, phobias, personal beliefs such as avoidance of fluoride, and so forth) associated with the end user 2-4* and that are associated with the one or more reported outcomes.

In some implementations, operation 2-775 may include an operation 2-779 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 complies with one or more medical or health limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7i. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more medical or health limitations (e.g., limitations related to arthritis, diabetes, cardiovascular conditions, and so forth) associated with the end user 2-4* and that are associated with the one or more reported outcomes.

In some implementations, operation 2-775 may further include an operation 2-780 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 complies with one or more user state limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7j. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more user state limitations (e.g., marital status, employment status, mental state, and so forth) associated with the end user 2-4* and that are associated with the one or more reported outcomes.

In some implementations, operation 2-775 may further include an operation 2-781 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 complies with one or more legal or regulatory limitations associated with the end user and that are associated with the one or more reported outcomes as depicted in FIG. 2-7j. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more legal or regulatory limitations associated with the end user 2-4*(e.g., drug or food regulations related to the place of domicile of the end user 2-4*) and that are associated with the one or more reported outcomes.

In some instances, the one or more reported aspects 2-14* to be found through the seeking operation 2-504 may be identified as being compliant with one or more limitations as set forth by one or more third parties 2-6*. For example, in various implementations, operation 2-759 may include an operation 2-782 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 complies with one or more limitations indicated by one or more third party sources and that are associated with the one or more reported outcomes as depicted in FIG. 2-7j. For instance, the limitation compliant reported aspect identification module 2-214* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 complies with one or more limitations indicated by one or more third party sources (e.g., publications, research results, medical advisories, and so forth) and that are associated with the one or more reported outcomes.

In some cases, the one or more reported aspects 2-14* to be sought may be identified as being one or more reported plausible aspects. For example, in some embodiments, operation 2-759 may include an operation 2-783 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 plausible aspects that are associated with the one or more reported outcomes 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 as depicted in FIG. 2-7k. For instance, the reported plausible aspect identification module 2-216* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 plausible aspects (e.g., walking 1 mile per day) that are associated with the one or more reported outcomes (e.g., reduce blood pressure) that corresponds to the one or more target outcomes, the one or more reported plausible aspects (e.g., walking 1 mile per day) being aspects that have been successfully emulated by one or more third parties 2-6*.

In turn, operation 2-783 may further include an operation 2-784 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 plausible aspects that are associated with the one or more reported outcomes that corresponds to the one or more target outcomes, the one or more reported plausible aspects being aspects that have been successfully emulated by the one or more third parties in order to achieve at least one of the one or more target outcomes as depicted in FIG. 2-7k. For instance, the reported plausible aspect identification module 2-216* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b 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 plausible aspects that are associated with the one or more reported outcomes and that corresponds to the one or more target outcomes, the one or more reported plausible aspects (e.g., reduced daily meat consumption) being aspects that have been successfully emulated by one or more third parties (e.g., third parties 2-6* such as other end users who may or may not have same traits as the end user 2-4*) in order to achieve at least one of the one or more target outcomes (e.g., lower cholesterol level).

In various implementations, the seeking operation 2-504 of FIG. 2-5 may include one or more operations for identifying one or more reported intermediate outcomes. For example, in some implementations, operation 2-759 may include an operation 2-785 for identifying one or more reported intermediate outcomes that are associated with the one or more reported outcomes as depicted in FIG. 2-7k. For instance, the reported outcome identification module 2-210* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b identifying one or more reported intermediate outcomes (e.g., a weight loss of 5 pounds, 8 pounds, 15 pounds, and so forth) that are associated with the one or more reported outcomes (e.g., a target outcome such as a total weight loss of 30 pounds).

In turn, operation 2-785 may further include, in some implementations, an operation 2-786 for identifying the one or more reported intermediate outcomes that are associated with the one or more reported outcomes including identifying one or more reported intermediate outcomes that occurred prior to one or more occurrences of the one or more reported outcomes as depicted in FIG. 2-7k. For instance, the reported outcome identification module 2-210* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b identifying the one or more reported intermediate outcomes that are associated with the one or more reported outcomes including identifying one or more reported intermediate outcomes (e.g., increased reading skills score by 10 points) that occurred prior to one or more occurrences of the one or more reported outcomes (e.g., target outcome such as increased reading skills score by 50 points).

In some implementations, operation 2-785 may include an operation 2-787 for identifying the one or more reported intermediate outcomes that are associated with the one or more reported outcomes including identifying one or more reported intermediate outcomes that are associated with one or more source users that the one or more reported aspects are associated with as depicted in FIG. 2-7k. For instance, the reported outcome identification module 2-210* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b identifying the one or more reported intermediate outcomes that are associated with the one or more reported outcomes (e.g., lower blood pressure level by 30 mmHg) including identifying one or more reported intermediate outcomes (e.g., lower blood pressure level by 10 mmHg) that are associated with one or more source users 2-2* that the one or more reported aspects 2-14*(e.g., sleep 8 hours per day) are associated with.

Various types of reported aspects 2-14* may be sought through the seeking operation 2-504 of FIG. 2-5 in various alternative implementations. For example, in some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-788 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to one or more incidences of source user behavior associated with one or more source users as depicted in FIG. 2-7l. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to one or more incidences of source user behavior (e.g., dietary behavior, physical activity behavior, behavior towards others, mental or physical acts, and so forth) associated with one or more source users 2-2*.

In various implementations, operation 2-788 may include one or more additional operations. For example, in some implementations, operation 2-788 may further include an operation 2-789 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to one or more incidences of physical acts executed by one or more source users as depicted in FIG. 2-7l. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to one or more incidences of physical acts (e.g., consume a food item or a medicine, attend class, read, exercise, and so forth) executed by one or more source users 2-2*.

In the same or different implementations, operation 2-788 may include an operation 2-790 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to one or more incidences of user attitudes associated with one or more source users as depicted in FIG. 2-7l. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to one or more incidences of user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with one or more source users 2-2*.

In the same or different implementations, operation 2-788 may include an operation 2-791 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to one or more incidences of user conduct associated with one or more source users as depicted in FIG. 2-7l. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to one or more incidences of user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with one or more source users 2-2 (does it need a *).

In some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-792 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to incidences of one or more user beliefs associated with one or more source users as depicted in FIG. 2-7m. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, and so forth) associated with one or more source users 2-2*.

In some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-793 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to incidences of one or more user states associated with one or more source users as depicted in FIG. 2-7m. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to incidences of one or more user states (e.g., mental states, marital states, employment state, physical state, availability state, and so forth) associated with one or more source users 2-2*.

In some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-794 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to incidences of one or more physical characteristics associated with one or more source users as depicted in FIG. 2-7m. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to incidences of one or more physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with one or more source users 2-2*

In some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-795 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to incidences of one or more user locations associated with one or more source users as depicted in FIG. 2-7m. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to incidences of one or more user locations (e.g., home, workplace, New York City, beach, and so forth) associated with one or more source users 2-2*.

In some implementations, the seeking operation 2-504 of FIG. 2-5 may include an operation 2-796 for seeking the one or more reported aspects that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects relating to incidences of one or more external events associated with one or more source users as depicted in FIG. 2-7m. For instance, the reported aspect seeking module 2-104* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b seeking the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including seeking one or more reported aspects 2-14* relating to incidences of one or more external events (e.g., hot or cold weather, heavy or no auto traffic, and so forth) associated with one or more source users 2-2*.

The development operation 2-506 of FIG. 2-5 may be executed in a variety of different ways in various alternative implementations. For example, in various implementations, the development operation 2-506 may include an operation 2-897 for developing at least one of the one or more personalized plans based, at least in part, on the one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a source user as depicted in FIG. 2-8a. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one of the one or more personalized plans 2-16* based, at least in part, on the one or more reported aspects 2-14* that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a source user 2-2a*. Thus, in these implementations, the execution of operation 2-897 may result in the development of at least one personalized plan 2-16* based on one or more reported aspects 124* that are related to a particular source user (e.g., source user 2-2a*).

Other personalized plans 2-16* may also be developed based on reported aspects associated with other source users (e.g., source user 2-2b*) in various alternative implementations. For example, in some implementations, operation 2-897 may include an operation 2-898 for developing at least a second one of the one or more personalized plans based, at least in part, on a second one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a second source user as depicted in FIG. 2-8a. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least a second one of the one or more personalized plans 2-16* based, at least in part, on a second one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a second source user 2-2b*. Thus, the execution of operation 2-898 may result in the development of a second personalized plan 2-16* based on a second one or more reported aspects that are related to a second source user (e.g., source user 2-2b*).

Operation 2-898 may in turn further include, in various implementations, an operation 2-899 for developing a third one of the one or more personalized plans based, at least in part, on a third one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a third source user, and a fourth one of the one or more personalized plans based, at least in part, on a fourth one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a fourth source user as depicted in FIG. 2-8a. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing a third one of the one or more personalized plans 2-16* based, at least in part, on a third one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a third source user (e.g., source user 2-2c*), and a fourth one of the one or more personalized plans 2-16* based, at least in part, on a fourth one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with a fourth source user (e.g., source user 2-2d*).

In various implementations, the development operation 2-506 may include an operation 2-800 for developing the one or more personalized plans based, at least in part, on the one or more reported aspects that are relevant to achieving at least one of the one or more target outcomes and that are particularly associated with one or more members of a source user group as depicted in FIG. 2-8a. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing the one or more personalized plans 2-16* based, at least in part, on the one or more reported aspects 2-14* that are relevant to achieving at least one of the one or more target outcomes (e.g., one or more reported outcomes that corresponds to the one or more target outcomes) and that are particularly associated with one or more members of a source user group (e.g., a social group such as a social networking group, a medical patient group, an employee group, a religious group, and so forth).

The one or more personalized plans 2-16* developed through the development operation 2-506 of FIG. 2-5 may be developed, at least in part, by including into the one or more personalized plans 2-16* emulatable aspects. For example, in various implementations, the development operation 2-506 may include an operation 2-801 for including into each of the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to the achievement of the one or more target outcomes as depicted in FIG. 2-8b. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into each of the one or more personalized plans 2-16* one or more emulatable aspects (e.g., indications of one or more aspects that may be emulated) that corresponds to the one or more reported aspects that are relevant to the achievement of the one or more target outcomes associated with the one or more personalized plans 2-16*. Note that in some situations a personalized plan 2-16* may include only a single emulatable aspect such as “being a vegan.”

In other cases, however, multiple emulatable aspects may be included in a personalized plan 2-16* to be developed. For example, in some implementations, operation 2-801 may include an operation 2-802 for including into each of the one or more personalized plans a plurality of emulatable aspects that corresponds to a plurality of reported aspects that are relevant to the achievement of the one or more target outcomes as depicted in FIG. 2-8b. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into each of the one or more personalized plans 2-16* a plurality of emulatable aspects (e.g., eat only fruits on day one, eat only vegetables on day two, and so forth) that corresponds to a plurality of reported aspects 2-14* that are relevant to the achievement of the one or more target outcomes (e.g., lose 20 pounds in a month).

When multiple emulatable aspects are to be included in a personalized plan 2-16* other types of information may also be included in the personalized plan 2-16* to be developed. For example, in some implementations, operation 2-802 may include an operation 2-803 for defining in each of the one or more personalized plans one or more relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 2-8b. For instance, the relationship defining module 2-220* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b defining (e.g., indicating) in each of the one or more personalized plans 2-16* one or more relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 2-16*. Various types of relationships may be defined in various alternative implementations.

For example, in some implementations, operation 2-803 may include an operation 2-804 for defining in each of the one or more personalized plans one or more temporal relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 2-8b. For instance, the relationship defining module 2-220* of the server 2-0 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b defining in each of the one or more personalized plans 2-16* one or more temporal relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 2-16*. For example, in the above example indicating that only fruits should be eaten on the day before the day that only vegetables are consumed.

In some implementations, operation 2-803 may include an operation 2-805 for defining in each of the one or more personalized plans one or more specific time relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 2-8b. For instance, the relationship defining module 2-220* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b defining in each of the one or more personalized plans 2-16* one or more specific time relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 2-16*. As an illustration, suppose a personalized plan 2-16* to be developed is for reducing migraine headaches (e.g., target outcome), and the personalized plan 2-16* indicates that the end user 2-4* should consume three specific types of vegetables (e.g., veg1, veg2, and veg3) a day. The personalized plan 2-16* may then be developed to indicate at what times should veg1 be consumed, what time should veg2 be consumed with respect to the time that veg1 was consumed, and what time should veg3 be consumed with respect to the times that veg1 and veg2 were consumed.

In some implementations, operation 2-803 may include an operation 2-806 for defining in each of the one or more personalized plans one or more spatial relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 2-8b. For instance, the relationship defining module 2-220* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b defining in each of the one or more personalized plans 2-16* one or more spatial relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 2-16*. As an illustration, suppose a personalized plan 2-16* to be developed is for reducing stress, and that the personalized plan 2-16* indicates that the end user 2-4* in order to reduce stress should break his daily work routine into two portions, a first work portion and a second work portion. The personalized plan 2-16* may be developed by indicating that the first work portion should be done at the end user's work place, while the second portion should be done at home.

Other types of information may also be included into a personalized plan 2-16* when, for example, multiple emulatable aspects are included into a personalized plan 2-16*. For example, in various implementations, operation 2-802 may include an operation 2-807 for including into at least one of the one or more personalized plans one or more emulatable intermediate outcomes related to the one or more target outcomes as depicted in FIG. 2-8b. For instance, the emulatable intermediate outcome inclusion module 2-222* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* one or more emulatable intermediate outcomes related to the one or more target outcomes. As an illustration, suppose a personalized plan 2-16* is to be developed for losing a body weight of 20 pounds (e.g., target outcome). The personalized plan 2-16* may be developed to include intermediate outcomes (e.g., 5 pound weight loss after two weeks, 8 pound of weight loss after four weeks, and so forth) to facilitate in determining whether the end user 2-4* in following the personalized plan 2-16* is on track to achieve the target outcome (e.g., 20 pound weight loss).

In some implementations, operation 2-807 may include an operation 2-808 for including into at least one of the one or more personalized plans one or more emulatable intermediate outcomes related to the one or more target outcomes, the one or more emulatable intermediate outcomes being identified in the one or more personalized plans as occurring prior to occurrence of the one or more target outcomes, the one or more emulatable intermediate outcomes corresponding to one or more reported intermediate outcomes as depicted in FIG. 2-8b. For instance, the emulatable intermediate outcome inclusion module 2-222* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* one or more emulatable intermediate outcomes related to the one or more target outcomes, the one or more emulatable intermediate outcomes being identified in the one or more personalized plans 2-16* as occurring prior to occurrence of the one or more target outcomes (e.g., final reported outcomes), the one or more emulatable intermediate outcomes corresponding to one or more reported intermediate outcomes.

The one or more emulatable aspects that may be included into a personalized plan 2-6* developed through the development operation 2-506 of FIG. 2-5 may correspond to one or more reported aspects 2-14* that have been determined to be relevant to the achievement of one or more reported outcomes, which may further correspond to the one or more target outcomes. For example, in some implementations, the development operation 2-506 may include an operation 2-809 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes including one or more reported aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of one or more reported outcomes that corresponds to the one or more target outcomes as depicted in FIG. 2-8c. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including one or more reported aspects 2-14* that occurred within one or more predefined time periods (e.g., one day, 48 hours, one month, one year, or other time periods), respectively, from one or more occurrences of one or more reported outcomes that corresponds to the one or more target outcomes.

As a further illustration, suppose a first personalized plan 2-16* is to be developed that may be based on initially seeking or identifying at least a first reported outcome that corresponds to at least a first target outcome. A first one or more reported aspects may then be identified that occurred within a predefined time period from the occurrence of the first reported outcome. By doing so, reported aspects that occurred well before or well after (e.g., outside the predefined time period) the occurrence of the first reported outcome (e.g. target outcome) may be ignored since they are not likely to be relevant to the occurrence of the first reported outcome. Note that in this example, the first one or more reported aspects and the first reported outcome that are identified may all be associated with a first source user (e.g., source user 2-2a*). Similarly, a second personalized plan 2-16* may be developed by identifying a second one or more reported aspects that occurred within a predefined time period from occurrence of a second reported outcome that corresponds to the first target outcome or a second target outcome. In some cases, the second one or more reported aspects and the second reported outcome may all be associated with a second source user (e.g., source user 2-2b*). In this illustration, the predefined time period described above may depend upon the type of personalized plan 2-16* being developed or may be set by a source user (e.g., a source user 2-2a*), an end user 2-4*, or by a third party 2-6*.

In some implementations, the 2-809 may further include an operation 2-810 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes including one or more reported aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported outcomes that corresponds to the one or more target outcomes as depicted in FIG. 2-8c. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes including one or more reported aspects 2-14* that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported outcomes that corresponds to the one or more target outcomes. Note that the difference between operation 2-809 and operation 2-810 is the inclusion of the phase “prior to” in operation 2-810.

In various implementations, one or more emulatable aspects may be included into a personalized plan 2-16* that complies with one or more preferences and/or one or more limitations. For example, in some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-811 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more preferences of the end user as depicted in FIG. 2-8c. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14*(e.g., as found through the seeking operation 2-504 of FIG. 2-5) that are relevant to achieving the one or more target outcomes and that complies with one or more preferences (e.g., interests) of the end user 2-4*. For example, the end user 2-4* may only be interested in reported aspects that relate to dietary activities or sleep activities.

In the same or different implementations, the development operation 2-506 may include an operation 2-812 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with (e.g., does not violate) one or more limitations (e.g., personal or physical limitations) associated with the end user 2-4*. The one or more reported aspects 2-14* that corresponds to the one or more emulatable aspects that may be included into the one or more personalized plans 2-16* may comply with a variety of different limitations in various alternative implementations.

For example, in some implementations, operation 2-812 may include an operation 2-813 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more physical limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with one or more physical limitations (e.g., missing limb, paralysis, visual or hearing impediment, and so forth) associated with the end user 2-4*.

In the same or different implementations, operation 2-812 may include an operation 2-814 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more contextual limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with one or more contextual limitations (e.g., logistical limitations such as scheduling limitations, geographical limitations, asset limitations, and so forth) associated with the end user 2-4*.

In the same or different implementations, operation 2-812 may include an operation 2-815 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more personal limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with 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-812 may include an operation 2-816 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more medical or health limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with 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-812 may include an operation 2-817 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more user state limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with one or more user state limitations (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) associated with the end user 2-4*.

In the same or different implementations, operation 2-812 may include an operation 2-818 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more legal or regulatory limitations associated with the end user as depicted in FIG. 2-8d. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with one or more legal or regulatory limitations (e.g., drug regulations, laws related to conduct or behavior in the jurisdiction of the end user 2-4*, and so forth) associated with the end user 2-4*.

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-819 for including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more reported aspects that are relevant to achieving the one or more target outcomes and that complies with one or more limitations indicated by one or more third party sources as depicted in FIG. 2-8e. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into the one or more personalized plans 2-16* one or more emulatable aspects that corresponds to the one or more reported aspects 2-14* that are relevant to achieving the one or more target outcomes and that complies with one or more limitations indicated by one or more third party sources (e.g., publications, research results, medical advisories, and so forth).

In various implementations, the one or more emulatable aspects that may be included into a personalized plan 2-16* may be based on one or more reported plausible aspects that have been successfully emulated by one or more third parties 2-6*. For example, in some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-820 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one reported plausible aspect that is relevant to achieving the one or more target outcomes, the at least one reported plausible aspect being an aspect that has been successfully emulated by one or more third parties as depicted in FIG. 2-8e. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one reported plausible aspect that is relevant to achieving the one or more target outcomes, the at least one reported plausible aspect being an aspect that has been determined to have been successfully emulated by one or more third parties 2-6*(e.g., other end users).

Operation 2-820, in turn, may further include an operation 2-821 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one reported plausible aspect that is relevant to achieving the one or more target outcomes, the at least one reported plausible aspect being an aspect that has been successfully emulated by one or more third parties in order to achieve at least one of the one or more target outcomes as depicted in FIG. 2-8e. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one reported plausible aspect that is relevant to achieving the one or more target outcomes, the at least one reported plausible aspect being an aspect that has been successfully emulated by one or more third parties 2-6*(e.g., other end users) in order to achieve at least one of the one or more target outcomes.

In various alternative implementations, the one or more emulatable aspects that may be included into a personalized plan 2-16* may correspond to any one or more of a variety of different reported aspect types. For example, in various implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-822 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more source user behaviors associated with a source user as depicted in FIG. 2-8f. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more source user behaviors (e.g., dietary behavior, physical activity behavior, behavior towards others, mental or physical acts, and so forth) associated with a source user (e.g., source user 2-2a*).

Operation 2-822 in turn may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 2-822 may include an operation 2-823 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more physical acts executed by a source user as depicted in FIG. 2-8f. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more physical acts (e.g., consume a food item or a medicine, attend class, read, exercise, and so forth) executed by a source user (e.g., source user 2-2a*).

In the same or different implementations, operation 2-822 may include an operation 2-824 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user attitudes associated with a source user as depicted in FIG. 2-8f. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with a source user (e.g., source user 2-2a*).

In the same or different implementations, operation 2-822 may include an operation 2-825 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user conduct associated with a source user as depicted in FIG. 2-8f. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with a source user (e.g., source user 2-2a*).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-826 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user beliefs associated with a source user as depicted in FIG. 2-8g. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, and so forth) associated with a source user (e.g., source user 2-2a*).

In some implementations, the development operation 2-506 may include an operation 2-827 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user states associated with a source user as depicted in FIG. 2-8g. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more user states (e.g., mental states, marital states, employment state, physical state, availability state, and so forth) associated with a source user (e.g., source user 2-2a*).

In some implementations, the development operation 2-506 may include an operation 2-828 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more physical characteristics associated with a source user as depicted in FIG. 2-8g. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with a source user (e.g., source user 2-2a*).

In some implementations, the development operation 2-506 may include an operation 2-829 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user locations associated with a source user as depicted in FIG. 2-8g. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more user locations (e.g., home, workplace, New York City, beach, and so forth) associated with a source user (e.g., source user 2-2a*).

In some implementations, the development operation 2-506 may include an operation 2-830 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more reported aspects that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more external events associated with a source user as depicted in FIG. 2-8g. For instance, the emulatable aspect inclusion module 2-218* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b including into at least one of the one or more personalized plans 2-16* at least one emulatable aspect that corresponds to at least one of the one or more reported aspects 2-14* that is relevant to achieving at least one of the one or more target outcomes, the at least one of the one or more reported aspects 2-14* being related to one or more incidences of one or more external events (e.g., hot or cold weather, heavy or no auto traffic, and so forth) associated with a source user (e.g., source user 2-2a*).

The one or more personalized plans 2-16* to be developed through the development operation 2-506 of FIG. 2-5 may be designed to facilitate an end user 2-4* to achieve any one or more of a variety of different outcomes. For example, in some implementations, the development operation 2-506 may include an operation 2-831 for developing at least one personalized plan to facilitate the end user to achieve one or more health or medical outcomes based, at least in part, on the seeking as depicted in FIG. 2-8h. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing (e.g., creating) at least one personalized plan 2-16* to facilitate the end user 24* to achieve 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) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

The at least one personalized plan 2-16* to be developed through operation 2-831 may be to facilitate the end user 24* in achieving a variety of specific health or medical outcomes. For example, in some implementations, operation 2-831 may include an operation 2-832 for developing at least one personalized plan to facilitate the end user to achieve one or more physiological outcomes based, at least in part, on the seeking as depicted in FIG. 2-8h. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more physiological outcomes (e.g., reducing blood pressure or blood glucose levels, increase red blood cell count, improve and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In the same or different implementations, operation 2-831 may include an operation 2-833 for developing at least one personalized plan to facilitate the end user to achieve one or more physical fitness outcomes based, at least in part, on the seeking as depicted in FIG. 2-8h. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve 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) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In the same or different implementations, operation 2-831 may include an operation 2-834 for developing at least one personalized plan to facilitate the end user to achieve one or more medical treatment outcomes based, at least in part, on the seeking as depicted in FIG. 2-8h. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve 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) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In the same or different implementations, operation 2-831 may include an operation 2-835 for developing at least one personalized plan to facilitate the end user to achieve one or more physical fitness training outcomes based, at least in part, on the seeking as depicted in FIG. 2-8h. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 24* to achieve one or more physical fitness training outcomes (e.g., reduce soreness from exercising, improve results of a training program, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In the same or different implementations, operation 2-831 may include an operation 2-836 for developing at least one personalized plan to facilitate the end user to achieve one or more fitness life style outcomes based, at least in part, on the seeking as depicted in FIG. 2-8h. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve 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) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-837 for developing at least one personalized plan to facilitate the end user to achieve one or more athletic outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more athletic outcomes (e.g., improve golf scores, win a bicycle or swimming race, develop a curve ball pitch, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-838 for developing at least one personalized plan to facilitate the end user to achieve one or more gaming outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more gaming outcomes (e.g., winning a chest tournament or improve video gaming skills) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-839 for developing at least one personalized plan to facilitate the end user to achieve one or more work outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 24* to achieve one or more work outcomes (e.g., a job promotion, finish a project on time, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-840 for developing at least one personalized plan to facilitate the end user to achieve one or more social outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve 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) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-841 for developing at least one personalized plan to facilitate the end user to achieve one or more leisure outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more leisure outcomes (e.g., learn how to knit, seeking time to go on vacation, finish reading a book, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-842 for developing at least one personalized plan to facilitate the end user to achieve one or more sexual intimacy outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more sexual intimacy outcomes (e.g., increased sexual activities, increased sexual performance, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-843 for developing at least one personalized plan to facilitate the end user to achieve one or more psychological outcomes based, at least in part, on the seeking as depicted in FIG. 2-8i. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more psychological outcomes (e.g., overcoming a phobia, overcoming certain addictive behavior such as compulsion to be clean, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-844 for developing at least one personalized plan to facilitate the end user to achieve one or more subjective user states based, at least in part, on the seeking as depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more subjective user states (e.g., overcoming a phobia, overcoming certain addictive behavior such as compulsion to be clean, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

Operation 2-844 may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 2-844 may include an operation 2-845 for developing at least one personalized plan to facilitate the end user to achieve one or more subjective user mental states based, at least in part, on the seeking depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more subjective user mental states (e.g., happiness, alertness, clarity of thinking, calmness, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, operation 2-844 may include an operation 2-846 for developing at least one personalized plan to facilitate the end user to achieve one or more subjective user physical states based, at least in part, on the seeking depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more subjective user physical states (e.g., physical fatigue, pain, blurry vision, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In some implementations, operation 2-844 may include an operation 2-847 for developing at least one personalized plan to facilitate the end user to achieve one or more subjective user overall states based, at least in part, on the seeking depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more subjective user overall states (e.g., “good,” “bad.” “well,” “tired,” “available,” “busy,” and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In various implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-848 for developing at least one personalized plan to facilitate the end user to achieve one or more user social states based, at least in part, on the seeking as depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 24* to achieve one or more user social states (e.g., membership to a social group, being married, being single and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In various implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-849 for developing at least one personalized plan to facilitate the end user to achieve one or more user employment states based, at least in part, on the seeking as depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more user employment states (e.g., being employed, attaining a particular employment position, attaining managerial authority, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

In various implementations, the development operation 2-506 of FIG. 2-5 may include an operation 2-850 for developing at least one personalized plan to facilitate the end user to achieve one or more intellectual or academic outcomes based, at least in part, on the seeking as depicted in FIG. 2-8j. For instance, the personalized plan development module 2-106* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b developing at least one personalized plan 2-16* to facilitate the end user 2-4* to achieve one or more intellectual or academic outcomes (e.g., passing a particular exam or class, obtaining a certain degree or academic award, being accepted into a particular program or school, attaining a particular scholarship, understanding a complex concept, acquiring particular knowledge, and so forth) based, at least in part, on the seeking (e.g., seeking operation 2-504 of FIG. 2-5).

Referring to FIG. 2-9 illustrating another operational flow 2-900 in accordance with various embodiments. Operational flow 2-900 includes certain operations that mirror the operations included in the operational flow 2-500 of FIG. 2-5. These operations include a reception operation 2-902, a seeking operation 2-904 and a development operation 2-906 that corresponds to and mirror the reception operation 2-502, the seeking operation 2-504 and the development operation 2-506, respectively, of FIG. 2-5.

In addition, operational flow 2-900 includes a presentation operation 2-908 for presenting the one or more personalized plans as depicted in FIG. 2-9. For instance, the presentation module 2-108* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b presenting (e.g., transmitting via the wireless network and/or wired network 2-50* or indicating via a user interface 2-120*) the one or more personalized plans 2-16*.

In various alternative implementations, the presentation operation 2-908 may include one or more additional operations. For example, in some implementations, the presentation operation 2-908 may include an operation 2-1052 for transmitting the one or more personalized plans via at least one of wireless network and a wired network as depicted in FIG. 2-10. For instance, the transmission module 2-224* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b transmitting the one or more personalized plans 2-16* via at least one of wireless network and a wired network 2-50*.

In the same or different implementations, the presentation operation 2-908 may include an operation 2-1053 for indicating the one or more personalized plans via user interface as depicted in FIG. 2-10. For instance, the user interface indication module 2-226* of the local source user device 2-20′ of FIG. 2-2b or the local end user device 2-30″ of FIG. 2-3b audibly or visually indicating the one or more personalized plans 2-16* via a user interface 2-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 2-908 may include an operation 2-1054 for presenting the one or more personalized plans to the end user as depicted in FIG. 2-10. For instance, the presentation module 2-108* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b presenting the one or more personalized plans 2-16* to the end user 2-4*.

In the same or different implementations, the presentation operation 2-908 may include an operation 2-1055 for presenting the one or more personalized plans to one or more third parties as depicted in FIG. 2-10. For instance, the presentation module 2-108* of the server 2-10 of FIG. 2-1b, the local source user device 2-20′ of FIG. 2-2b, or the local end user device 2-30″ of FIG. 2-3b presenting the one or more personalized plans 2-16* to one or more third parties 2-6*.

Turning now to FIG. 2-11 illustrating a computing device 2-1100 designed to implement one or more of the operations of the operational flows described above (e.g., as illustrated in FIGS. 2-5, 2-6a, 2-6b, 2-6c, 2-6d, 2-6e, 2-6f, 2-7a, 2-7b, 2-7c, 2-7d, 2-7e, 2-7f, 2-7g, 2-7h, 2-7i, 2-7j, 2-7k, 2-7l, 2-7m, 2-8a, 2-8b, 2-8c, 2-8d, 2-8e, 2-8f, 2-8g, 2-8h, 2-8i, 2-8j, 2-9, and 2-10). In various implementations, the computing device 2-1100 may be a server such as the server 2-10 of FIG. 2-1b or a local client device such as the local source user device 2-20a′ of FIG. 2-2b or the local end user device 2-30″ of FIG. 2-3b.

As illustrated, the computing device 2-1100 may include a processor 2-1102 (e.g., microprocessor, controller, and so forth) coupled to storage medium 2-1106 (e.g., volatile or non-volatile memory). The storage medium 2-1106 may store computer readable instructions 2-1104 (e.g., computer program product). The processor 2-1102, in various implementations, may execute the computer readable instructions 2-1104 in order to execute one or more operations described above and as illustrated in FIGS. 2-5, 2-6a, 2-6b, 2-6c, 2-6d, 2-6e, 2-6f, 2-7a, 2-7b, 2-7c, 2-7d, 2-7e, 2-7f, 2-7g, 2-7h, 2-7i, 2-7j, 2-7k, 2-7l, 2-7m, 2-8a, 2-8b, 2-8c, 2-8d, 2-8e, 2-8f, 2-8g, 2-8h, 2-8i, 2-8j, 2-9, and 2-10.

For example, the processor 2-1102 may execute the computer readable instructions 2-1104 in order to receive 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; seek one or more reported aspects that are relevant to achieving the one or more target outcomes in response to receiving the request; and/or develop the one or more personalized plans based, at least in part, on the seeking as depicted in the operational flow 2-500 of FIG. 2-5.

IV. Personalized Plan Development Based on One or More Reported Aspects' Association with One or More Source Users

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 particular act, behavior, characteristic, user state or status, belief, and so forth, 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 become very popular in recent times 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 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 aspects associated with a user. Examples of sensors that may be used for such purposes vary widely, ranging from traditional devices that can detect and report on physiological parameters such as heart rate or blood pressure, to sensors that can detect certain user behaviors or activities such as toilet usage. Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, sensor data, and so forth) 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, methods, systems, circuitry, and computer program products are provided that may facilitate in the development of 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 development of the one or more personalized plans may be by initially providing one or more relevant reported aspects that have been determined to be associated with one or more source users (e.g., model subjects who may have been previously identified) and that have been determined to be relevant to achieving the one or more target outcomes. The one or more personalized plans may then be developed by including into the one or more personalized plans one or more emulatable aspects that corresponds to the one or more relevant reported aspects. The methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, by a network device such as a server (e.g., network servers) or a local client device.

In some cases, the development of the one or more personalized plans may be prompted when, for example, a request is received that at least identifies the one or more source users. For example, suppose an end user (or a third party) observes that a particular source user (or a group of source users) has certain desirable traits or characteristics (e.g., target outcomes) that the end user would like to have. In order to acquire such desirable characteristics or target outcomes, the end user may submit a request for a personalized plan to achieve such outcomes. In some cases, the request may only include data that identifies the source user having the desired traits and without identifying the desired traits (e.g., without indicating the target outcomes). As will be further discussed below, various techniques may be employed in order to provide the identity of the source user who may be a complete stranger to the end user (e.g., the end user may have only noticed or come across the source user at a gym or at a doctor's office) without being intrusive. Upon obtaining the identity of the source user, one or more relevant reported aspects that have been determined to be associated with the identified source user and that are determined to be relevant to achieving the target outcomes are provided.

In some embodiments, the one or more relevant reported aspects may be provided by, for example, identifying or finding the one or more relevant reported aspects from a plurality of reported aspects that may or may not include both relevant and non-relevant reported aspects that may or may not be associated with the identified source user. Note that 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 an occurrence of an aspect (e.g., behavior, act, trait, physical state, mental state, social state, declaration, belief, or any other facet) associated with a particular source user and that has been reported. Various sources may be searched in order to find the one or more relevant reported aspects. For example, 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 target outcomes and that are associated with the identified source user.

Each reported aspect that is determined to be associated with the identified source user and that have been determined to be relevant to achieving the target outcomes may have been at least originally reported by, for example, one or more source users, by one or more sensing devices, and/or by one or more third parties. In some cases, at least a portion of the one or more relevant reported aspects that are found to be associated with the identified source user and that are found to be relevant to the achievement of the target outcomes may have been reported through social networking entries (e.g., microblog entry or status report).

A number of different approaches may be employed in order to provide the one or more relevant reported aspects (e.g., reported aspects that are associated with the identified source user and that are relevant to achieving the one or more target outcomes). For example, in some cases, an operation to provide the one or more relevant reported aspects may involve initially finding or identifying reported aspects that are determined to be at least associated with the identified source user. Once, one or more reported aspects that are determined to be at least associated with at least the one or more source users have been found or identified, one or more reported aspects that are relevant to achieving the one or more target outcomes may be identified from the one or more reported aspects that have been determined to be at least associated with the identified source user.

The “relevancy” of a reported aspect with respect to achieving the target outcomes may be based on one or more factors, which for purposes of this discussion, will be referred to as “relevancy factors.” Some relevancy factors that may be determinative in determining whether a reported aspect is relevant includes, for example, whether the reported aspect is a type of aspect that has been indicated by, for example, the end user, a source user, or a third party as being relevant (e.g., cause) for achieving the desired one or more target outcomes. For example, if an end user is interested as to how a particular source user was able to have a very calm temperament, and the end user believes that the source user's calm temperament (e.g., target outcome) is the result of the source user's dietary behavior, then only reported aspects relating to the dietary behaviors of the identified source user may be considered “relevant.”

Other relevancy factors may also be factors in determining whether a reported aspect is relevant to the achievement of a target outcome. For example, determining whether a reported aspect indicates an aspect that occurred proximate to the occurrence of a reported aspect that corresponds to a target outcome. Note that when the identified source user has achieved the particular target outcome, the achievement of the target outcome may be indicated in the form of a reported aspect. As an illustration, suppose a source user has lost 30 pounds of body weight, then the weight loss, which may be the target outcome of an end user, may be reported in the form of a reported aspect. The end user, upon observing the weight loss of the source user, may indicate that she is only interested in the exercise activities of the source user because the end user believes that the weight loss was due to the source user's exercise activities. Thus, under this criteria, all reported aspects that are related to exercise activities of the source user may be deemed relevant.

However, not all reported aspects associated with the source user and that are related to exercise activities may be relevant to the achievement of the target outcome if they occurred well before (or after) the occurrence (achievement) of the target outcome. Thus, in some embodiments, a determination may be made as to whether an aspect indicated by a potentially relevant reported aspect occurred within some predefined time period from the occurrence of a reported aspect that corresponds to the target outcome. The predefined time period described above may be based upon the type of target outcome being sought and/or may be provided by the end user, the source user, or by a third party source.

For example, in the above weight loss example, the end user may only be interested in reported aspect (e.g., dietary and/or exercise behaviors) that occurred within one month (e.g., predefined time period) of the occurrences of the reported aspect that corresponds to the target outcome (e.g., body weight loss of 30 pounds). Based on this criteria, only those reported aspects that occurred within one month of the occurrence of the reported aspect (e.g., 30 pounds of body weight loss) that corresponds to the target outcome and that are associated with the identified source user may qualify as being relevant to the achievement of the one or more target outcomes. Of course, and alternatively, third party sources (e.g., content provider or a publication such as research article) may provide the predefined time period based on the type of personalized plan being developed.

Note that a reported aspect that is found to be associated with the source user of interest (e.g., the source user who has been identified by, for example, the end user as having achieved a particular target outcome) and that is found to satisfy a particular relevancy factor may not necessary be a “relevant reported aspect” for achieving the target outcome. That is, there may be several relevancy factors that may need to be satisfied in order for a reported aspect to be determined as a “relevant reported aspect” that is associated with one or more particular source users and that are relevant for achieving one or more target outcomes.

In some embodiments, a personalized plan may merely be a collection of one or more emulatable aspects. An emulatable aspect may be an indication of 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 multiple 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 are preferably or ideally achieved 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 aspects (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 achieving 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 (real) 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 indicating actual aspects of a plurality of real source users may be compiled and processed (e.g., normalized or averaged out) in order to create such a fictional source user.

Turning now to FIGS. 3-1a, 3-1b, 3-2a, 3-2b, 3-3a, and 3-3b, 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. 3-1a and 3-1b 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 3-10. FIGS. 3-2a and 3-2b 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 3-20a′. FIGS. 3-3a and 3-3b 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 3-30″.

Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, a “local end user device 3-30*” may be in reference to the local end user device 3-30 of the first example environment of FIGS. 3-1a and 3-1b, the local end user device 3-30′ of the second example environment of FIGS. 3-2a and 3-2b, or the local end user device 3-30″ of the third example environment of FIGS. 3-3a and 3-3b. Similarly, references in the following to a “source user 3-2**” may be in reference to any one of the one or more source users (e.g., source user 3-2a, 3-2b, and so forth) of the first example environment of FIGS. 3-1a and 3-1b, to any one of the one or more source users (e.g., source user 3-2a′, 3-2b′, and so forth) of the second example environment of FIGS. 3-2a and 3-2b, or to any one of the one or more source users (e.g., 3-2a″, 3-2b″, and so forth) of the third example environment of FIGS. 3-3a and 3-3b. In still other cases, references in the following to “a source user 3-2a*” may be in reference to the source user 3-2a of FIG. 3-1a, to the source user 3-2a′ of FIG. 3-2a, or to the source user 3-2a″ of FIG. 3-3b.

In various embodiments, the server 3-10 of FIG. 3-1b, the local source user device 3-20a′ of FIG. 3-2b, and the local end user device 3-30″ of FIG. 3-3b may be designed to, among other things, provide one or more relevant reported aspects associated with one or more source users 3-2** 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 3-2**. After providing the one or more relevant reported aspects, the server 3-10, the local source user device 3-20a′, and the local end user device 3-30″ may be designed to, among other things, develop one or more personalized plans 3-16* designed to facilitate an end user 3-4* to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16* are emulated, the development of the one or more personalized plans 3-16* being based, at least in part, on the providing of the one or more relevant reported aspects.

As illustrated, in various embodiments the server 3-10 of FIG. 3-1b, the local end user device 3-20a′ of FIG. 3-3b, and the local end user device 3-30 may be employed in a network environment. For example, the server 3-10 of the first example environment of FIGS. 3-1a and 3-1b, the local source user device 3-20a* of the second example environment of FIGS. 3-2a and 3-2b, and the local end user device 3-30″ of the third example environment of FIGS. 3-3a and 3-3b may communicate with other network devices via a wireless network and/or wired network 3-50*(e.g., at least one of a wireless network and a wired network 3-50*). In various implementations, the wireless and/or wired network 3-50 may include 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 3-50*.

Referring particularly now to FIGS. 3-1a and 3-1b, which illustrates the first example environment in accordance with various embodiments. Included in the illustrated first environment of FIGS. 3-1a and 3-1b is a first exemplary system 3-100, which includes at least a server 3-10 (a network server) that may be designed to communicate with one or more source users 3-2*(via one or more local source user devices 3-20*) and an end user 3-4 (via a local end user device 3-30) through a wireless network and/or wired network 3-50. In some implementations, the server 3-10 may further communicate with, via the wireless network and/or wired network 3-50, one or more third parties 3-6 (e.g., one or more other end users 3-4*, 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 3-60), and/or one or more sensing devices 3-40. As will be further described herein with respect to FIG. 3-4c, each of the one or more sensing devices 3-40 may include one or more sensors 3-240 (one or more sensors 3-240* of FIG. 3-4c) that can detect or sense one or more aspects associated with one or more source users 3-2*(e.g., source user 3-2a, source user 3-2b, and so forth), a network interface 3-242 (e.g., see network interface 3-242* of FIG. 3-4c) and/or a memory 3-244 (see memory 3-244 of FIG. 3-4c).

In various implementations, the server 3-10 of FIG. 3-1b (as well as the one or more network servers 3-60* of FIGS. 3-1a, 3-2a, and 3-3b) may be a computing/communication device that is designed to interface with a wireless network and/or wired network 3-50. Further, the server 3-10 of FIG. 3-1b, 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 3-2* may include a first source user 3-2a, a second source user 3-2b, a third source user 3-2c, a fourth source user 3-2d, and so forth. The one or more local source user devices 3-20* may include a first local source user device 3-20a (e.g., to be used by the first source user 3-2a to communicate via wireless network and/or wired network 3-50), a second local source user device 3-20b (e.g., to be used by the second source user 3-2b to communicate via wireless network and/or wired network 3-50), and so forth. The one or more local source user devices 3-20*(as well as the one or more local source user devices 3-20*′ of FIGS. 3-2a and 3-2b and the one or more local source user devices 3-20*″ of FIGS. 3-3a and 3-3b) and the local end user device 3-30 (as well as the local end user device 3-30′ of FIGS. 3-2a and 3-2b and the local end user device 3-30″ of FIGS. 3-3a and 3-3b) 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 3-20 (as well as the local source user devices 3-20*′ of FIGS. 3-2a and 3-2b and the one or more local source user devices 3-20*″ of FIG. 3-3a) and/or the local end user device 3-30 (as well as the local end user device 3-30′ of FIG. 3-2a and the local end user device 3-30″ of FIG. 3-2b) 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 3-20** and/or local end user device 3-30*) may be a laptop, a desktop, a workstation, a web tablet, or other types of devices that may not be a handheld device in various alternative implementations.

Referring back to the first exemplary environment of FIGS. 3-1a and 3-1b, the server 3-10 may be designed to receive a request 3-12 for one or more personalized plans 3-16 for achieving one or more target outcomes. The one or more requests 3-12 may be received from an end user 3-4, from a third party 3-6, from a source user 3-2*, or from a network server 3-60. In various embodiments, the request 3-12 may at least identify one or more source users 3-2*, and in some cases, may not identify any of the target outcomes that are associated with the one or more personalized plans 3-16.

In some embodiments, in response to receiving the request 3-12, the server 3-10 may provide one or more relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving one or more target outcomes associated with the one or more personalized plans 3-16, 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 3-2*. There are at least four ways or paths that the server 3-10 may follow in various alternative embodiments in order to provide the one or more relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving one or more target outcomes associated with the one or more personalized plans 3-16.

In the first path, the server 3-10 may provide the one or more relevant reported aspects by selectively acquiring (e.g., via the wireless network and/or wired network 3-50) reported aspects 3-15 that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors (e.g., relevant with respect to satisfying one or more relevancy factors). In other words, selectively acquiring the relevant reported aspects rather than, for example, acquiring randomly reported aspects that may or may not be relevant to achieving the one or more target outcomes.

In the second path, the server 3-10 may first selectively acquire (e.g., via the wireless network and/or wired network 3-50) one or more reported aspects 3-14 that are at least associated with the one or more source users 3-2*. After acquiring the one or more reported aspects 3-14 that are at least associated with the one or more source users 3-2*, the one or more relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes (e.g., relevant with respect to one or more relevancy factors) may be identified (e.g., finding or determining) from the one or more reported aspects 3-14 that have been acquired.

In the third path, the server 3-10 may first selectively acquire (e.g., via the wireless network and/or wired network 3-50) one or more reported aspects 3-15 that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes based on (e.g., with respect to) one or more relevancy factors. After acquiring the one or more reported aspects 3-15, the one or more relevant reported aspects may be provided by identifying from the one or more reported aspects 3-15, one or more reported aspects that are relevant to achieving the one or more target outcomes based (e.g., with respect to) on a second one or more relevancy factors.

In the fourth path, it is presumed that a plurality of reported aspects 3-17 is already in the possession of or is available to the server 3-10, where the plurality of reported aspects 3-17 may or may not include both relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes, and reported aspects that may not be associated with the one or more source users 3-2* and/or that are not relevant to achieving the one or more target outcomes. Under such circumstances, the server 3-10 may be designed to provide the one or more relevant reported aspects by identifying from the plurality of reported aspects 3-17 one or more reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes (e.g., relevant with respect to one or more relevancy factors). In some embodiments, the plurality of reported aspects 3-17 may be stored in a memory 3-116.

Note that in some embodiments, the providing of the one or more relevant reported aspects by the server 3-10 may include the server 3-10 both identifying the one or more relevant reported aspects in memory 3-116 and searching for the one or more relevant reported aspects via the wireless network and/or wired network 3-50. That is, reported aspects (both relevant reported aspects and not relevant aspects) may be found throughout the wireless network and/or wired network 3-50 and may, in some cases, be found in a memory 3-116.

If the one or more reported aspects 3-14 or the one or more reported aspects 3-15 are to be acquired by the server 3-10, such as when the server 3-10 follows the first, the second, or the third path, then the server 3-10 may be designed to transmit one or more solicitations 3-13 that may be designed to solicit for the one or more reported aspects 3-14 or solicit for the one or more reported aspects 3-15. In some embodiments, the one or more solicitations 3-13 may be transmitted to one or more local source user devices 3-20*, one or more third parties 3-6, one or more sensing devices 3-40, and/or one or more network servers 3-60 via the wireless network and/or wired network 3-50. After transmitting the one or more solicitations 3-13, the server 3-10 may be designed to receive the one or more reported aspects 3-14 that are at least associated with the one or more source users 3-2* or the one or more reported aspects 3-15 that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors.

After receiving the one or more reported aspects 3-14 or the one or more reported aspects 3-15, the server 3-10 may be designed to identify from the one or more reported aspects 3-14 or from the one or more reported aspects 3-15, one or more reported aspects that are relevant for achieving the one or more target outcomes with respect to one or more relevancy factors (e.g., such as the case when the server 3-10 follows the third path, and the server 3-10 identifies the one or more reported aspects that are relevant with respect to a second one or more relevancy factors)

In some alternative embodiments, the relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes may be part of a plurality of reported aspects 3-17 that are already in the possession of or already accessible to the server 3-10 (e.g., such as the case in the fourth path). In such cases, the plurality of reported aspects 3-17 may or may not include both reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes (e.g., relevant reported aspects), and reported aspects that may not be associated with the one or more source users 3-2* and/or that are not relevant to achieving the one or more target outcomes. In some cases, the plurality of reported aspects 3-17 may be stored in a memory 3-116.

Once the one or more relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes have been provided (e.g., as acquired and/or identified via the first, the second, the third, or the fourth path), the server 3-10 may be designed to develop one or more personalized plans 3-16 that are designed to facilitate an end user 3-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16 are emulated, the development of the one or more personalized plans 3-16 being based, at least in part, on the providing of the one or more relevant reported aspects.

In some implementations, a personalized plan 3-16 may merely be a collection of one or more emulatable aspects, while in other implementations, a personalized plan 3-16 may define the specific relationships (e.g. spatial or time relationships) between emulatable aspects. In some implementations, a personalized plan 3-16 may include other information such as emulatable intermediate outcomes to facilitate determining, for example, how well an end user 3-4 is progressing towards achieving one or more target outcomes of the personalized plan 3-16 when the one or more emulatable aspects included in the personalized plan 3-16 are being emulated. In some implementations, the server 3-10 may then be designed to present the developed one or more personalized plans 3-16 to the end user 3-4 (via the local end user device 3-30), to one or more network servers 3-60, and/or to one or more third parties 3-6.

The server 3-10 as illustrated in FIG. 3-1b may include a variety of modules, sub-modules, and various other components. As shown, the server 3-10 may include a relevant reported aspect provision module 3-102 (which may further include one or more sub-modules as illustrated in FIG. 3-4a), a personalized plan development module 3-104 (which may further include one or more sub-modules as illustrated in FIG. 3-4b), a presentation module 3-106 (which may further include a transmission module 3-224), a memory 3-116 (which may store a plurality of reported aspects 3-17, one or more end user relevancy indications 3-142, one or more end user limitations 3-143, one or more source user relevancy indications 3-144, one or more third party source relevancy indications 3-145, one or more predefined time period indications 3-146, and one or more applications 3-140), and/or a network interface 3-118 (e.g., network interface card or NIC). In various embodiments, the server 3-10 may further include a social networking entry reception module 3-110 (which may further include a blog entry reception module 3-111 and/or a status report reception module 3-112), a diary entry reception module 3-114, and/or a sensor data reception module 3-115.

The relevant reported aspect provision module 3-102 may be configured to, among other things, provide one or more relevant reported aspects based, at least in part, on the one or more relevant reported aspects' association with one or more source users 3-2*, the one or more relevant reported aspects to be provided being relevant to achieving one or more target outcomes. The personalized plan development module 3-104 may be configured to, among other things, develop one or more personalized plans 3-16 based, at least in part, on the one or more relevant reported aspects, the one or more personalized plans 3-16 to be developed being designed to facilitate an end user 3-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16 are emulated. The presentation module 3-106 may be designed to present (e.g., transmit via the wireless network and/or wired network 3-50 to the local end user device 3-30, to one or more local source user devices 3-20*, to one or more network servers 3-60, and/or to one or more third parties 3-6) the one or more personalized plans 3-16 that are developed. A more detailed discussion relating to the relevant reported aspect provision module 3-102, the personalized plan development module 3-104, the presentation module 3-106, and their sub-modules, will be provided below with respect to the various operational flows to be described herein.

The memory 3-116 may be designed to store various data including a plurality of reported aspects 3-17 that may include one or more reported aspects that are relevant to achieving the one or more target outcomes and/or that are associated with the one or more source users 3-2*. In some cases, the reported aspects 3-17 stored in memory 3-116 may include reported aspects that are not relevant to achieving the one or more target outcomes and/or that are not associated with the one or more source users 3-2*. Other types of data may be stored in the memory 3-116 including, for example, one or more end user relevancy indications 3-142 (e.g., one or more indications that indicate the types of reported or emulatable aspects that an end user 3-4 has an interest in or believes is relevant to achieving the one or more target outcomes), one or more end user limitations 3-143 (e.g., limitations such as contextual limitations, physical limitations, personal limitations, and so forth, associated with the end user 3-4 that prevent one or more emulatable aspects from being emulated), and/or one or more source user relevancy indications 3-144 (e.g., one or more indications provided by a source user 3-2* that indicate at least which types of reported aspects are relevant to achieving the one or more target outcomes).

In some cases, the memory 3-116 may also include, for example, one or more third party source relevancy indications 3-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 3-6 that indicate at least which types of reported aspects are relevant to achieving the one or more target outcomes), one or more predefined time period indications 3-146 (e.g., one or more indications that indicate at least one time period such as a time increment or window, a reported aspect being relevant for achieving at least one target outcome only if the reported aspect indicate 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 3-2*), and/or one or more applications 3-140 (e.g., a text messaging application, an instant messaging application, an email 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). In various implementations, the memory 3-116 comprises 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 social networking entry reception module 3-110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 3-2*, an end user 3-4, one or more third parties 3-6, and/or one or more network servers 3-60. The social networking entry reception module 3-110 may further include a blog entry reception module 3-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 3-112 for receiving social networking status reports. The diary entry reception module 3-114 may be configured to receive diary entries from, for example, the one or more source users 3-2*, the end user 3-4, and/or from the one or more third parties 3-6 (e.g., a non-user). The sensor data reception module 3-115 may be configured to receive sensing data from one or more sensing devices 3-40.

Referring now to FIGS. 3-2a and 3-2b, 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 3-20′ rather than at a server 3-10 as was the case in the first example environment of FIGS. 3-1a and 3-1b. As illustrated, the second example environment of FIGS. 3-2a and 3-2b is similar to the first example environment of FIGS. 3-1a and 3-1b.

In general, the second example environment of FIGS. 3-2a and 3-2b may include a second exemplary system 3-100′, which includes at least a local source user device 3-20a′ (see FIG. 3-2b). In various implementations, the local source user device 3-20a′, as was the case for server 3-10 of FIGS. 3-1a and 3-1b, may be designed to receive a request 3-12′ for one or more personalized plans 3-16′ that are designed to facilitate an end user 3-4′ to achieve one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans 3-16′ are emulated. The one or more requests 3-12′ may be received from an end user 3-4′, from a third party 3-6′, from a network server 3-60′, or from a source user 3-2a′ (e.g., via user interface 3-120′). In various embodiments, the request 3-12′ may at least identify one or more source users 3-2*′, and in some cases, may not identify any target outcomes associated with the one or more personalized plans 3-16′.

In response to receiving the request 3-12′ the local source user device 3-20′ may be designed to provide one or more relevant reported aspects that are associated with the one or more source users 3-2*′ and 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 3-2*′. Similar to the server 3-10 of FIG. 3-1b, the local source user device 3-20a′ may follow any one of four alternative paths in various alternative embodiments in order to provide the one or more relevant reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving one or more target outcomes associated with the one or more personalized plans 3-16′.

As was the case with the server 3-10 of FIG. 3-1b, in the first path, the local source user device 3-20a′ may provide the one or more relevant reported aspects by selectively acquiring (e.g., via the wireless network and/or wired network 3-50′) reported aspects 3-15′ that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors (e.g., relevant with respect to satisfying one or more relevancy factors).

In the second path, the local source user device 3-20a′ may initially selectively acquire (e.g., via the wireless network and/or wired network 3-50′) one or more reported aspects 3-14′ that are at least associated with the one or more source users 3-2*′. After acquiring the one or more reported aspects 3-14′ that are at least associated with the one or more source users 3-2*′, the one or more relevant reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes (e.g., relevant with respect to one or more relevancy factors) may be identified (e.g., finding or determining) from the one or more reported aspects 3-14′ that have been acquired.

In the third path, the local source user device 3-20a′ may first selectively acquire (e.g., via the wireless network and/or wired network 3-50′) one or more reported aspects 3-15′ that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes based on (e.g., with respect to) one or more relevancy factors. After acquiring the one or more reported aspects 3-15′, the one or more relevant reported aspects may be provided by identifying from the one or more reported aspects 3-15′, one or more reported aspects that are relevant to achieving the one or more target outcomes based (e.g., with respect to) on a second one or more relevancy factors.

In the fourth path, it is presumed that a plurality of reported aspects 3-17′ may already be in the possession of or may already be available to the local source user device 3-20a′, where the plurality of reported aspects 3-17′ may include both relevant reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes, and reported aspects that may not be associated with the one or more source users 3-2*′ and/or that are not relevant to achieving the one or more target outcomes. Under such circumstances, the local source user device 3-20a′ may be designed to provide the one or more relevant reported aspects by identifying from the plurality of reported aspects 3-17′ one or more reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes (e.g., relevant with respect to one or more relevancy factors). In some embodiments, the plurality of reported aspects 3-17′ may be stored in a memory 3-116′.

As with the server 3-10 of FIG. 3-1b, the providing of the one or more relevant reported aspects by the local source user device 3-20a′ may include the local source user device 3-20a′ both identifying the one or more relevant reported aspects in memory 3-116′ and searching for the one or more relevant reported aspects via the wireless network and/or wired network 3-50′.

If the one or more reported aspects 3-14′ or the one or more reported aspects 3-15′ are to be acquired by the local source user device 3-20a′, such as when the local source user device 3-20a′ follows the first, the second, or the third path, then the local source user device 3-20a′ may be designed to transmit one or more solicitations 3-13′ that may be designed to solicit for the one or more reported aspects 3-14′ or for the one or more reported aspects 3-15′. In some embodiments, the one or more solicitations 3-13′ may be transmitted to one or more other local source user devices 3-20*′ (e.g., local source user device 3-20b′, local source user device 3-20c′, and so forth), one or more third parties 3-6′, one or more sensing devices 3-40′, and/or one or more network servers 3-60′ via the wireless network and/or wired network 3-50′. After transmitting the one or more solicitations 3-13′, the local source user device 3-20a′ may be designed to receive the one or more reported aspects 3-14′ that are at least associated with the one or more source users 3-2*′ or the one or more reported aspects 3-15′ that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors.

After receiving the one or more reported aspects 3-14′ or the one or more reported aspects 3-15′, the local source user device 3-20a′ may be designed to identify from the one or more reported aspects 3-14′ or from the one or more reported aspects 3-15′, one or more reported aspects that are relevant for achieving the one or more target outcomes with respect to one or more relevancy factors (e.g., in the case where the local source user device 3-20a′ follows the third path, the local source user device 3-20a′ identifying the one or more reported aspects that are relevant with respect to a second one or more relevancy factors).

In the case where the relevant reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes are already in the possession of or are already readily accessible to the local source user device 3-20a′ (e.g., such as the case when the local source user device 3-20a′ follows the fourth path), the one or more relevant reported aspects may be part of a plurality of reported aspect 3-17′ that may already be in the possession (e.g., stored in the memory 3-116′) of the local source user device 3-20a′. In various embodiments, the plurality of reported aspects 3-17′ may include both reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes (e.g., relevant reported aspects), and reported aspects that may not be associated with the one or more source users 3-2*′ and/or that are not relevant to achieving the one or more target outcomes. In some cases, the plurality of reported aspects 3-17′ may be stored in a memory 3-116′.

Once the one or more relevant reported aspects that are associated with the one or more source users 3-2*′ and that are relevant to achieving the one or more target outcomes have been provided (e.g., as acquired and/or identified via the first, the second, the third, or the fourth path), the local source user device 3-20a′ may be designed to develop one or more personalized plans 3-16′ that are designed to facilitate an end user 3-4′ to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16′ are emulated, the development of the one or more personalized plans 3-16′ being based, at least in part, on the providing of the one or more relevant reported aspects.

The local source user device 3-20a′, as illustrated in FIG. 3-2b, may include the same or similar modules, sub-modules, and components included in the server 3-10 of FIG. 3-1b. As illustrated, the local source user device 3-20a′ may include a relevant reported aspect provision module 3-102′ (which may further include one or more sub-modules as illustrated in FIG. 3-4a), a personalized plan development module 3-104′ (which may further include one or more sub-modules as illustrated in FIG. 3-4b), a presentation module 3-106′ (which may further include a transmission module 3-224′), a memory 3-116′ (which may store a plurality of reported aspects 3-17′, one or more end user relevancy indications 3-142′, one or more end user limitations 3-143′, one or more source user relevancy indications 3-144′, one or more third party source relevancy indications 3-145′, one or more predefined time period indications 3-146′, and one or more applications 3-140′), and/or a network interface 3-118′ (e.g., NIC), similar to the server 3-10 of FIG. 3-1b.

Also similar to server 3-10 of FIG. 3-1b, the local source user device 3-20a′ may also include a social networking entry reception module 3-110′ (which may further include a blog entry reception module 3-111′ and/or a status report reception module 3-112′), a diary entry reception module 3-114′, and/or a sensor data reception module 3-115′. All of these modules, sub-modules, and other components of the local source user device 3-20a′ may perform the same or similar functions as their counterparts that may be included in the server 3-10 of FIG. 3-1b. In addition to these modules, sub-modules, and components, the local source user device 3-20′ may include a user interface 3-120′ and a user interface indication module 3-226′ (which may be included with the presentation module 3-108′). The user interface indication module 3-226′ may be designed to indicate, for example, the one or more personalized plans 3-16′ via the user interface 3-120′. The user interface 3-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. 3-3a and 3-3b, 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 3-30″ rather than at a server 3-10″ or at a local source user device 3-20a″ as was the case in the first and second example environments of FIGS. 3-1a and 3-1b and FIGS. 3-2a and 3-2b. The third example environment of FIGS. 3-3a and 3-3b is similar to the first example environment of FIGS. 3-1a and 3-1b and the second example environment of FIGS. 3-2a and 3-2b with few minor differences.

For example, in the third example environment, the local end user device 3-30″ may receive a request 3-12″ for the one or more personalized plans 3-16″ directly from an end user 3-4″ via a user interface 3-120″ rather than via the wireless network and/or wired network 3-50″ as was the case for the server 3-10 of the first example environment of FIGS. 3-1a and 3-1b and as was the case for the local source user device 3-20a′ of the second example environment of FIGS. 3-2a and 3-2b. However, and as with the server 3-10 and the local source user device 3-20a′ of FIGS. 3-1b and 3-2b, the local end user device 3-30″ may also alternatively receive a request 3-12″ from other sources such as from one or more third parties 3-6″ or from a network server 3-60″ via the wireless network and/or wired network 3-50″.

As illustrated, the third example environment of FIGS. 3-3a and 3-3b may include a third exemplary system 3-100″, which includes at least a local end user device 3-30″ (see FIG. 3-3b). In general, the local end user device 3-30″ may be designed to receive a request 3-12″ for one or more personalized plans 3-16″ that are designed to facilitate an end user 3-4″ to achieve one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans 3-16″ are emulated. In some implementations, the request 3-12″ may be received directly from the end user 3-4″ via a user interface 3-120″. Alternatively, and although not depicted, the request 3-12″ may be received via wireless network and/or wired network 3-50″ from, for example, one or more third parties 3-6″ or from a network server 3-60″. As before in the first and second exemplary environments, the request 3-12″ may identify one or more source users 3-2*″ in various implementations. Also as before, in some implementations, the request 3-12″ may not identify any target outcomes.

In response to receiving the request 3-12″, the local end user device 3-30″ may be designed to provide one or more relevant reported aspects that are associated with the one or more source users 3-2*″ and 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 3-2*″. Similar to the server 3-10 of FIG. 3-1b and the local source user device 3-20a′ of FIG. 3-2b, the local end user device 3-30″ may follow any one of four alternative paths in various alternative implementations in order to provide for the one or more relevant reported aspects that are associated with the one or more source users 3-2*″ and that are relevant to achieving one or more target outcomes associated with the one or more personalized plans 3-16″.

As was the case with the server 3-10 of FIG. 3-1b and with the local source user device 3-20a′ of FIG. 3-2b, in the first path, the local end user device 3-30″ may provide the one or more relevant reported aspects by selectively acquiring (e.g., via the wireless network and/or wired network 3-50″) reported aspects 3-15″ that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors (e.g., relevant with respect to satisfying one or more relevancy factors).

In the second path, the local end user device 3-30″ may initially selectively acquire (e.g., via the wireless network and/or wired network 3-50″) one or more reported aspects 3-14″ that are at least associated with the one or more source users 3-2*″. After acquiring the one or more reported aspects 3-14″ that are at least associated with the one or more source users 3-2*″, the one or more relevant reported aspects that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes (e.g., relevant with respect to one or more relevancy factors) may be identified (e.g., finding or determining) from the one or more reported aspects 3-14″ that have been acquired.

In the third path, the local end user device 3-30″ may first selectively acquire (e.g., via the wireless network and/or wired network 3-50″) one or more reported aspects 3-15″ that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes based on (e.g., with respect to) one or more relevancy factors. After acquiring the one or more reported aspects 3-15″, the one or more relevant reported aspects may be provided by identifying from the one or more reported aspects 3-15″, one or more reported aspects that are relevant to achieving the one or more target outcomes based (e.g., with respect to) on a second one or more relevancy factors.

In the fourth path, it is presumed that a plurality of reported aspects 3-17″ may already be in the possession of or may already be available to the local end user device 3-30″, where the plurality of reported aspects 3-17″ may include both relevant reported aspects that are associated with the one or more source users 3-2* and that are relevant to achieving the one or more target outcomes, and reported aspects that may not be associated with the one or more source users 3-2*″ and/or that are not relevant to achieving the one or more target outcomes. Under such circumstances, the local end user device 3-30″ may be designed to provide the one or more relevant reported aspects by identifying from the plurality of reported aspects 3-17″ one or more reported aspects that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes (e.g., relevant with respect to one or more relevancy factors). In some embodiments, the plurality of reported aspects 3-17″ may be stored in a memory 3-116″.

As with the server 3-10 of FIG. 3-1b and the local source user device 3-20a′ of FIG. 3-2b, the providing of the one or more relevant reported aspects by the local end user device 3-30″ may include the local end user device 3-30″ both identifying the one or more relevant reported aspects in memory 3-116″ and searching for the one or more relevant reported aspects via the wireless network and/or wired network 3-50″.

If the one or more reported aspects 3-14″ or the one or more reported aspects 3-15″ are to be acquired by the local end user device 3-30″, such as when the local end user device 3-30″ follows the first, the second, or the third path, then the local end user device 3-30″ may be designed to transmit one or more solicitations 3-13″ that may be designed to solicit for the one or more reported aspects 3-14″ or for the one or more reported aspects 3-15″. In some embodiments, the one or more solicitations 3-13″ may be transmitted to one or more local source user devices 3-20*″, one or more third parties 3-6″, one or more sensing devices 3-40″, and/or one or more network servers 3-60″ via the wireless network and/or wired network 3-50″. After transmitting the one or more solicitations 3-13″, the local end user device 3-30″ may be designed to receive the one or more reported aspects 3-14″ that are at least associated with the one or more source users 3-2*″ or the one or more reported aspects 3-15″ that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors.

After receiving the one or more reported aspects 3-14″ or the one or more reported aspects 3-15″, the local end user device 3-30″ may be designed to identify from the one or more reported aspects 3-14″ or from the one or more reported aspects 3-15″, one or more reported aspects that are relevant for achieving the one or more target outcomes with respect to one or more relevancy factors (in the case where the local end user device 3-30″ follows the third path, the local end user device 3-30″ identifying the one or more reported aspects that are relevant with respect to a second one or more relevancy factors).

In the case where the relevant reported aspects that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes are already in the possession of or are already readily accessible to the local end user device 3-30″ (e.g., such as the case when the local end user device 3-30″ follows the fourth path), the one or more relevant reported aspects may be part of a plurality of reported aspect 3-17″ that may already be in the possession (e.g., stored in the memory 3-116″) of the local end user device 3-30″. In various embodiments, the plurality of reported aspects 3-17″ may include both reported aspects that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes (e.g., relevant reported aspects), and reported aspects that may not be associated with the one or more source users 3-2*″ and/or that are not relevant to achieving the one or more target outcomes. In some cases, the plurality of reported aspects 3-17″ may be stored in a memory 3-116″.

Once the one or more relevant reported aspects that are associated with the one or more source users 3-2*″ and that are relevant to achieving the one or more target outcomes have been provided (e.g., as acquired and/or identified via the first, the second, the third, or the fourth path), the local end user device 3-30″ may be designed to develop one or more personalized plans 3-16″ that are designed to facilitate an end user 3-4″ to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16″ are emulated, the development of the one or more personalized plans 3-16″ being based, at least in part, on the providing of the one or more relevant reported aspects.

In various implementations, the local end user device 3-30″ as illustrated in FIG. 3-3b may include the same or similar modules, sub-modules, and components included in the local source user device 3-20a′ of FIG. 3-2b. For example, the local end user device 3-30″ may include a relevant reported aspect provision module 3-102″ (which may further include one or more sub-modules as illustrated in FIG. 3-4a), a personalized plan development module 3-104″ (which may further include one or more sub-modules as illustrated in FIG. 3-4b), a presentation module 3-106″ (which may further include a transmission module 3-224″ and a user interface indication module 3-226″), a memory 3-116″ (which may store a plurality of reported aspects 3-17″, one or more end user relevancy indications 3-142″, one or more end user limitations 3-143″, one or more source user relevancy indications 3-144″, one or more third party source relevancy indications 3-145″, one or more predefined time period indications 3-146″, and one or more applications 3-140″), and/or a network interface 3-118″ (e.g., NIC), similar to the local source user device 3-20a′ of FIG. 3-2b.

Also similar to the local source user device 3-20a′ of FIG. 3-2b, the local end user device 3-30″ may also include a social networking entry reception module 3-110″ (which may further include a blog entry reception module 3-111″ and/or a status report reception module 3-112″), a diary entry reception module 3-114″, and/or a sensor data reception module 3-115″. All of these modules, sub-modules, and components of the local end user device 3-30″ may perform the same or similar functions as their counterparts that may be included in the local source user device 3-20a′ of FIG. 3-2b. In addition to these modules, sub-modules, and components, the local end user device 3-30″ may include an identification device 3-122″ for providing data to identify one or more source users 3-2*″. Such data may be in the form of, for example, audio data, image data, RFID data, text or numerical data, or other types of identification data that facilitate in the identification of the one or more source users 3-2*″. The user interface 3-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. 3-4 a illustrates particular implementations of the relevant reported aspect provision module 3-102*(e.g., the relevant reported aspect provision module 3-102, the relevant reported aspect provision module 3-102′, and the relevant reported aspect provision module 3-102″) of FIGS. 3-1b, 3-2b, and 3-3b. As illustrated, the relevant reported aspect provision module 3-102* may include, in various implementations, one or more sub-modules. For example, in some implementations, the relevant reported aspect provision module 3-102* may include a relevant reported aspect identification module 3-202* that is configured to, among other things, identify (e.g., from a plurality of reported aspects 3-17*) one or more reported aspects 3-14* that are at least associated with one or more source users 3-2**, the identification being based, at least in part, on the one or more source users 3-2** association with the one or more reported aspects. Alternatively, or in the same implementations, the relevant reported aspect identification module 3-202* may be configured to identify one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving one or more target outcomes, the one or more reported aspects 3-15* being relevant based on, or with respect to, one or more relevancy factors (e.g., the one or more reported aspects 3-15* indicate one or more aspects that occurred proximate or within one or more predefined time periods from the one or more occurrences of one or more target outcomes as achieved by, for example, the one or more source users 3-2**).

In the same implementations or different implementations, the relevant reported aspect provision module 3-102* may include a relevant aspect acquisition module 3-204*that is configured to, among other things, acquire one or more reported aspects 3-14* that are at least associated with one or more source users 3-2** who may have been previously identified or specified. In the same or different implementations, the relevant reported aspect acquisition module 3-204* may be configured to acquire one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving one or more target outcomes based on (e.g., with respect to) one or more relevancy factors (e.g., relevancy based on indications provided by the end user 3-4*, one or more source users 3-2**, and/or one or more third party sources).

The reported aspect acquisition module 3-204* may further include one or more sub-modules in various alternative implementations. For example, in some implementations, the reported aspect acquisition module 3-204* may include a memory searching module 3-206* that is configured to, among other things, search a memory 3-116* for one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** or for one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving one or more target outcomes based on (e.g., with respect to) one or more relevancy factors.

In the same or different implementations, the reported aspect acquisition module 3-204* may include a network searching module 3-208* that is configured to, among other things, search for the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** or for the one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving one or more target outcomes based on one or more relevancy factors via at least one of a wireless network and a wired network 3-50*. The network searching module 3-208*, in turn, may further include one or more additional sub-modules.

For example, in some implementations, the network searching module 3-208* may include a solicitation transmission module 3-210* for transmitting, via the at least one of the wireless network and the wired network 3-50, one or more solicitations 3-13* for the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** or for the one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving one or more target outcomes based on one or more relevancy factors. The solicitations 3-13* may be transmitted to a variety of network devices including, for example, one or more local source user devices 3-20*, one or more network servers 3-60*, one or more sensing devices 3-40*, one or more third parties 3-6*, and so forth. In the same or different implementations, the network searching module 3-208* may include a reported aspect reception module 3-212* that is configured to receive, for example, the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** and/or the one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving one or more target outcomes based on one or more relevancy factors.

FIG. 3-4 b illustrates particular implementations of the personalized plan development module 3-104*(e.g., the personalized plan development module 3-104, the personalized plan development module 3-104′, and the personalized plan development module 3-104″) of FIGS. 3-1b, 3-2b, and 3-3b. As previously indicated, the personalized plan development module 3-104* may be configured to develop one or more personalized plans 3-16* that are designed to facilitate an end user 3-4* to achieve one or more target outcomes when one or more emulated aspects included in the one or more personalized plans 3-16* are emulated, the development of the one or more personalized plans 3-16* being based on one or more relevant reported aspects that are provided by the relevant reported aspect provision module 3-102*.

In various implementations, the personalized plan development module 3-104* may include one or more of an emulatable aspect inclusion module 3-220*, a relationship defining module 3-222*, an emulatable intermediate outcome inclusion module 3-223*, a limitation compliance determination module 3-224*(which may further include a non-compliance notification module 3-226* and/or a personalized plan modification module 3-228*), and/or a plausible determination module 3-230*(which may further include an action module 3-232* that may further include a not plausible notification module 3-234* and/or personalized plan modification module 3-236*).

The emulatable aspect inclusion module 3-220* may be configured to include into each of the one or more personalized plans 3-16* to be developed one or more emulatable aspects that correspond to the one or more relevant reported aspects provided by the relevant reported aspect provision module 3-102*. The relationship defining module 3-222* may be configured to define in each of the one or more personalized plans 3-16* to be developed one or more relationships (e.g., spatial, temporal, and/or specific time relationships) between the plurality of emulatable aspects that may be included in each of the one or more personalized plans 3-16*. The emulatable intermediate outcome inclusion module 3-223* may be configured to, among other things, include into at least one of the one or more personalized plans 3-16* to be developed one or more emulatable intermediate outcomes (e.g., lower systolic BP pressure by 10 mmHg) related to the one or more target outcomes (e.g., lower systolic BP pressure by 20 mmHg) of the at least one of the one or more personalized plans 3-16*.

The limitation compliance determination module 3-224* may be configured to determine whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16 complies with one or more limitations associated with the end user 3-4*, and if not compliant, execute one or more actions. Various types of actions may be executed if a determination is made of non-compliance. For example, in some implementations, the limitation compliance determination module 3-224* may include a non-compliance notification module 3-226* that is configured to notify (e.g., notifying by transmitting a notification or by indicating via a user interface 3-120*) at least one of the end user 3-4* and a third party 3-6* regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user 3-4*. Other types of actions may also be executed. For example, in some implementations, the limitation compliance determination module 3-224* may include a personalized plan modification module 3-228* that is configured to modify the one or more personalized plans 3-16* including replacing one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 3-4* with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user 3-4*.

The plausible determination module 3-230*, in contrast to the limitation compliance determination module 3-224*, may be configured to determine whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is a plausible aspect that has been successfully emulated by one or more third parties 3-6*(e.g., other end users), and if not plausible, execute one or more actions. Various types of actions may be executed if a determination is made of non-compliance.

For example, in some implementations, the plausible determination module 3-230* may include a not plausible notification module 3-234* that is configured to notify, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is not a plausible aspect, at least one of the end user 3-4* and a third party 3-6* regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is not a plausible aspect. Note that a plausible aspect is an aspect that has been successfully emulated by one or more third parties 3-6* in order to, for example in some cases, achieve the one or more target outcomes.

Other types of actions may also be executed when one or more emulatable aspects that may be included in the one or more personalized plans 3-16* have been determined to be not plausible. For example, in some implementations, the plausible determination module 3-230* may include a personalized plan modification module 3-236* that is configured to modify, in response to a determination that at least one of the one or more emulatable aspects included in the one or more personalized plans 3-16* is not a plausible aspect, at least one of the one or more personalized plans 3-16* by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 3-6*.

Referring now to FIG. 3-4c illustrating one of the sensing devices 3-40* of FIGS. 3-1a, 3-2a, and 3-3a. The sensing device 3-40*, in various embodiments, may include at least one or more sensors 3-240*. The one or more sensors 3-240* that may be included in a sensing device 3-40* may be designed to sense or detect one or more aspects associated with a source user 3-2**. For example, in various implementations, the one or more sensors 3-240* may include one or more 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 3-240* may include devices that can detect activities of a user (e.g., a source user 3-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 3-240* may include, in various implementations, 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 3-20*, global positioning system (GPS) to provide location data related to a user (e.g., locations of the source user 3-2*), and so forth. In various implementations, a sensing device 3-40* may further include a network interface 3-242* and/or a memory 3-244* to store, for example, sensing data provided by the one or more sensors 3-240*.

Referring back to the server 3-10 of FIG. 3-1b, the local source user device 3-20a′ of FIG. 3-2b, and the local end user device 3-30″, the various modules (e.g., the relevant reported aspect provision module 3-102*, the personalized plan development module 3-104*, the presentation module 3-106*, and so forth) along with their sub-modules included in the server 3-10, the local source user device 3-20a′, and the local end user device 3-30″ may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the relevant reported aspect provision module 3-102*, the personalized plan development module 3-104*, and/or the presentations module 3-106* may be implemented with a processor 3-1002 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 3-1004 (e.g., computer program product) stored in a storage medium 3-1006 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 3-1000 of FIG. 3-10. 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 3-10 of FIG. 3-1b, the local source user device 3-20a′ of FIG. 3-2b, and the local end user device 3-30″ of FIG. 3-3b will now be provided with respect to the processes and operations to be described herein. FIG. 3-5 illustrates an operational flow 3-500 representing example operations related to, among other things, providing of one or more relevant reported aspects that are associated with one or more source users 3-2** and that are relevant to achieving one or target outcomes, and the development of one or more personalized plans 3-16* based on the one or more relevant reported aspects that are provided.

In FIG. 3-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. 3-1a and 3-1b, FIGS. 3-2a and 3-2b, and FIGS. 3-3a and 3-3b, and/or with respect to other examples (e.g., as provided in FIGS. 3-4a, 3-4b, and 3-4c) 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. 3-1a, 3-1b, 3-2a, 3-2b, 3-3a, 3-3b, 3-4a, 3-4b, and 3-4c. 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. 3-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 3-500 may move to a relevant reported aspect providing operation 3-502 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. For instance, and as an illustration, the relevant reported aspect provision module 3-102*(e.g., the relevant reported aspect provision module 3-102, the relevant reported aspect provision module 3-102′, or the relevant reported aspect provision module 3-102″) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b providing one or more relevant reported aspects associated with one or more source users 3-2** 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 3-2**. In some cases, the relevant reported aspect providing operation 3-502 (as well as the operational flow 3-500) may be prompted to be executed as a result of the server 3-10, the local source user device 3-20′, or the local end user device 3-30″ receiving a request 3-12* for the one or more personalized plans 3-16* that are designed to facilitate the end user 3-4* in achieving one or more target outcomes. The request 3-12* may have originated from various sources including, for example, the end user 3-4*, a network server 3-60*, or a third party 3-6*. In some embodiments, the request 3-12* may merely identify the one or more source users 3-2** without, for example, identifying any of the one or more target outcomes.

Note that in various implementations, provision of the one or more relevant reported aspects may not depend on the association of the one or more relevant reported aspects with the one or more target outcomes. Rather, such an operation for providing the one or more relevant reported aspects may only depend on the association of the one or more relevant reported aspects with the one or more source users 3-2** who may be identified by, for example, the end user 3-4* or by a third party 3-6*. In various implementations, and as will be further described herein, the one or more source users 3-2** may be identified by various means including by name, user name, biometrics data, image data, audio data, location data, and so forth.

Operational flow 3-500 may also include a personalized plan development operation 3-504 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. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, of the local source user device 3-20′ of FIG. 3-2b, or of the local end user device 3-30″ of FIG. 3-3b developing (e.g., creating) one or more personalized plans 3-16* designed to facilitate an end user 3-4* to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16* are emulated, the development of the one or more personalized plans 3-16* being based, at least in part, on the providing of the one or more relevant reported aspects.

In various implementations, the relevant reported aspect providing operation 3-502 of FIG. 3-5 may be executed in a number of different ways as will be illustrated in FIGS. 3-6a, 3-6b, 3-6c, 3-6d, 3-6e, 3-6f, 3-6g, 3-6h, 3-6i, 3-6j, 3-6k, 3-61, 3-6m, 3-6n, 3-6o, 3-6p, 3-6q, 3-6r, and 3-6s. In some cases, for example, the relevant reported aspect providing operation 3-502 may simply involve identifying (e.g., finding, determining, or locating) the one or more relevant reported aspects that are associated with one or more source users 3-2** and that are relevant to achieving one or more target outcomes. In particular, in some implementations the relevant reported aspect providing operation 3-502 may include an operation 3-602 for identifying one or more reported aspects that are at least associated with the one or more source users from a plurality of reported aspects as depicted in FIG. 3-6a. For instance, the relevant reported aspect identification module 3-202*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying (e.g., locating or finding from a plurality of reported aspects 3-17* stored in a memory 3-116*) one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** from a plurality of reported aspects 3-17* that may or may not be associated with the one or more source users 3-2**. The identification of the one or more reported aspects 3-14* may be based, at least in part, on the one or more reported aspects 3-14* associated with the one or more source users 3-2**.

Operation 3-602 may, in turn, include an operation 3-603 for identifying one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users in various implementations. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**.

Note that the one or more reported aspects 3-14* that are at least associated with the one or more source user 3-2** (e.g., the one or more reported aspects that the one or more reported aspects that are relevant to achieving the one or more target outcomes are identified from) may include both reported aspects that are relevant to achieving the one or more target outcomes and reported aspects that are not relevant to achieving the one or more target outcomes. Thus, in some implementations operation 3-603 may include an operation 3-604 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from 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. 3-6a. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from 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.

The identification of the one or more reported aspects (i.e., relevant reported aspects) that are relevant to achieving the one or more target outcome from the one or more reported aspects that are at least associated with the one or more source users 3-2** may involve determining which of the one or more reported aspects that are at least associated with the one or more source users 3-2** are relevant with respect to one or more relevancy factors. As will be referred to herein, a relevancy factor may be any basis for determining whether a reported aspect is relevant to achieving one or more target outcomes. For example, in some implementations, the operation 3-603 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes may include an operation 3-605 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users based, at least in part, on one or more relevancy factors that at least identifies one or more aspect types that are relevant to achieving the one or more target outcomes as depicted in FIG. 3-6a. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** based, at least in part, on one or more relevancy factors that at least identifies one or more aspect types that are relevant to achieving the one or more target outcomes.

The identification of the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users 3-2** may be based on a variety of relevancy factors. For example, in some implementations, the operation 3-605 for identifying the one or more reported aspects based on one or more relevancy factors may include an operation 3-606 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that belong to one or more aspect types that are of interest to the end user as depicted in FIG. 3-6a. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that belong to one or more aspect types that are of interest to the end user 3-4* (e.g., the end user 3-4* may have indicated an interest in the dietary or sleep habits of the one or more source users 3-2**).

In the same or different implementations, operation 3-605 may include an operation 3-607 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that belong to one or more aspect types that have been indicated by the one or more source users as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6a. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that belong to one or more aspect types that have been indicated by the one or more source users 3-2** as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 3-605 may include an operation 3-608 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that belong to one or more aspect types that have been indicated by one or more third party sources as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6b. For instance, the relevant reported aspect identification 3-202* of the of the server 3-10 of FIG. 3-1b, the local end user device 3-20′, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that belong to one or more aspect types that have been indicated by one or more third party sources (e.g., publications, research articles, government or scientific advisories, content provider, and so forth) as being relevant to the achievement of the one or more target outcomes. For example, published research indicating that sleep habits may affect ability to lose body weight (e.g., target outcome). Thus, reported aspects relating to the sleep habits or behavior associated with the one or more source users 3-2** may be identified.

In the same or different implementations, operation 3-605 may include an operation 3-609 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that indicate one or more aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 3-6b. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that indicate one or more aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes.

That is, not all reported aspects associated with the one or more source users 3-2** and that may be relevant with respect to at least certain relevancy factors may actually be relevant to achieving the one or more target outcomes if the reported aspects indicate aspects that, time-wise, occurred remotely from occurrence of the one or more target outcomes as successfully achieved by the one or more source users 3-2**. For example, reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant based on certain relevancy factors may, nevertheless, not be relevant to achieving the one or more target outcomes if they occurred well before (or well after) the achievement of the one or more target outcomes (e.g., as represented by one or more reported aspects that corresponds to the one or more target outcomes) by the one or more source users 3-2**. Thus, a reported aspect may, in some cases, be relevant to the achievement of the one or more target outcomes only if it falls within some time period (e.g., a predefined time period) from the one or more occurrences of the one or more reported aspects that correspond to the one or more target outcomes. The amount of time period (i.e., “predefined time period”) described above may, of course, depend 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 may be associated with a different predefined time period) may be set based on the type of personalized plans 3-16* being developed. Alternatively, the one or more predefined time periods may be provided by the end user 3-4*, a source user, or some third party. As an illustration, suppose an end user 3-4* observes that a source user 3-2** has lost considerable amount of weight during the previous two months. The end user 3-4* may then indicate that he is only interested in reported aspects that indicate aspects associated with the source user 3-2** and that have occurred during the past two months.

In some implementations, operation 3-609 may further include an operation 3-610 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that indicate one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 3-6b. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that indicate one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes. That is, generally most (but not all) reported aspects that are relevant to achieving a particular target outcome will typically occur prior to the target outcome being achieved.

Various types of aspects may be indicated by the one or more reported aspects that are identified as being relevant to achieving the one or more target outcomes in various alternative implementations. For example, in some implementations, the operation 3-603 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users may include an operation 3-611 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more behavior incidences associated with the one or more source users as depicted in FIG. 3-6c. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more behavior incidences associated with the one or more source users 3-2**.

A behavior incidence may be related to any act, conduct, manner, and so forth that may be exhibited by, for example, a source user 3-2**. For example, in some implementations, operation 3-611 may include an operation 3-612 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more activities executed by the one or more source users as depicted in FIG. 3-6c. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more activities (e.g., dietary or nutritional activities, exercise activities, leisure activities, sleeping or resting activities, and so forth) executed by the one or more source users 3-2*.

In the same or different implementations, operation 3-611 may include an operation 3-613 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user attitudes associated with the one or more source users as depicted in FIG. 3-6c. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-611 may include an operation 3-614 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user conduct associated with the one or more source users as depicted in FIG. 3-6c. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with the one or more source users 3-2**.

In some implementations, the operation 3-603 for identifying one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users may include an operation 3-615 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user beliefs associated with the one or more source users as depicted in FIG. 3-6d. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, political beliefs, and so forth) associated with the one or more source users 3-2**. As a further illustration, such user beliefs, which may be user professed beliefs or apparent beliefs, may be reported by the one or more source users 3-2** or by one or more third parties 3-6*(e.g., other end users 3-4*) via log entries (e.g., microblog entries or status reports). Note that in the case where one or more third parties 3-6* are reporting the specific incidences of beliefs associated with the one or more source users 3-2**, the reported beliefs may be obtained from the one or more source users 3-2** when the source users 3-2** expresses such beliefs.

In the same or different implementations, operation 3-603 may include an operation 3-616 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more subjective user states associated with the one or more source users as depicted in FIG. 3-6d. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more subjective user states associated with the one or more source users 3-2*. A subjective user state may be any state or status associated with a source user 3-2* that can typically only be indicated by the source user 3-2*. Examples of subjective user states include, for example, subjective user mental states (e.g., sadness, happiness, mental exhaustion, alertness, and so forth), subjective user physical states (e.g., sore back, blurred vision, overall physical exhaustion, and so forth), and subjective user overall states (e.g., any other subjective user states that are neither a subjective user mental state or a subjective user physical state including, for example, “feeling good,” “feeling bad,” “feeling alive,” and so forth).

In the same or different implementations, operation 3-603 may include an operation 3-617 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 3-6d. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-603 may include an operation 3-618 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of user locations associated with the one or more source users as depicted in FIG. 3-6d. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of user locations (e.g., home, workplace, New York City, beach, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-603 may include an operation 3-619 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of external events associated with the one or more source users as depicted in FIG. 3-6e. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of external events (e.g., weather conditions, heavy or no road traffic, stock market performance, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-603 may include an operation 3-620 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that corresponds to the one or more target outcomes as depicted in FIG. 3-6e. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that corresponds to the one or more target outcomes. For example, if the one or more target outcomes includes a target outcome for achieving an A1C score of 6 percent or lower (e.g., a test score that indicate average blood glucose level for previous three months) then identifying one or more reported aspects that corresponds to achieving an AIC score of 6 percent or lower.

In the same or different implementations, operation 3-603 may include an operation 3-621 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are reported intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 3-6e. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects (e.g., total body weight loss of 3-10 pounds) that are reported intermediate outcomes associated with the one or more target outcomes (e.g., total body weight loss of 30 pounds). By identifying such reported aspects or reported intermediate outcomes, a personalized plan 3-16* may be developed that may include at least one emulatable intermediate outcome (which corresponds to the reported intermediate outcome) that may facilitate the end user 3-4* in determining whether the end user 3-4* is on track to achieve the target outcome when the one or more personalized plans 3-16* are being executed.

In the same or different implementations, operation 3-603 may include an operation 3-622 for identifying from the one or more reported aspects that are at least associated with the one or more source users a first one or more reported aspects that are associated with a first source user and that are relevant to achieving a first one or more target outcomes and a second one or more reported aspects that are associated with a second source user and that are relevant to achieving a second one or more target outcomes as depicted by FIG. 3-6e. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** a first one or more reported aspects that are associated with a first source user 3-2a* and that are relevant to achieving a first one or more target outcomes and a second one or more reported aspects that are associated with a second source user 3-2b* and that are relevant to achieving a second one or more target outcomes. Thus, in various implementations, multiple reported aspects that are associated with multiple source users 3-2** may be identified for achieving at least two target outcomes.

In the same or different implementations, operation 3-603 may include an operation 3-623 for identifying from the one or more reported aspects that are at least associated with the one or more source users a first one or more reported aspects that are associated with a first source user and that are relevant to achieving at least one target outcome and 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 target outcome as depicted in FIG. 3-6e. For instance, the relevant reported aspect identification 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** a first one or more reported aspects that are associated with a first source user 3-2a* and that are relevant to achieving at least one target outcome and a second one or more reported aspects that are associated with a second source user 3-2b* and that are relevant to achieving the at least one target outcome. Thus, in various implementations, multiple reported aspects that are associated with multiple source users 3-2** may be identified for achieving the same target outcome.

In various implementations, the relevant reported aspect providing operation 3-502 of FIG. 3-5 may be performed by acquiring one or more reported aspects. For example, in some implementations, the relevant reported aspect providing operation 3-502 may include an acquisition operation 3-624 for acquiring one or more reported aspects that are at least associated with the one or more source users as depicted in FIG. 3-6f. For instance, the reported aspect acquisition module 3-204*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b acquiring (e.g., obtaining or retrieving from a memory 3-116* or via at least one of a wireless network and a wired network 3-50) one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**.

The acquisition of the one or more reported aspects that are at least associated with the one or more source users 3-2** may be accomplished in a variety of different ways in various alternative implementations. For example, in some implementations, the acquisition operation 3-624 may include a memory searching operation 3-625 for searching a memory for the one or more reported aspects that are at least associated with the one or more source users as depicted in FIG. 3-6f. For instance, the memory searching module 3-206*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b searching a memory 3-116* for the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**. Note that in various implementations the searching operation 3-625 may include one or more of the identification operations (e.g., operations 3-602 to 3-623) previously described above. For example, and similar to operation 3-602 of FIG. 3-6a, the memory searching operation 3-625 may include an operation for identifying (e.g., in memory 3-116) one or more reported aspects that are at least associated with the one or more source users 3-2** from a plurality of reported aspects 3-17*.

In some implementations, the acquisition operation 3-624 may include an operation 3-626 for searching, via at least one of a wireless network and a wired network, for the one or more reported aspects that are at least associated with the one or more source users as depicted in FIG. 3-6f. For instance, the network searching module 3-208*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b searching (e.g., querying), via at least one of a wireless network and a wired network 3-50*, for the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**.

In order to search for the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** via the wireless network and/or the wired network 3-50*, one or more solicitations 3-13* may be transmitted via the wireless network and/or the wired network 3-50*. For example, in some implementations, operation 3-626 may include an operation 3-627 for transmitting, via the at least one of the wireless network and the wired network, one or more solicitations for the one or more reported aspects that are at least associated with the one or more source users, the one or more solicitations identifying at least one of the one or more source users as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting, via the at least one of the wireless network and the wired network 3-50*, one or more solicitations 3-13* (e.g., queries or requests) for the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**, the one or more solicitations 3-13* identifying at least one of the one or more source users 3-2**.

Operation 3-627, in turn, may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 3-627 may include an operation 3-628 for transmitting at least one of the one or more solicitations to one or more local source user devices as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting at least one of the one or more solicitations 3-13* to one or more local source user devices 3-20**.

In the same or different implementations, operation 3-627 may include an operation 3-629 for transmitting at least one of the one or more solicitations to one or more network servers as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting at least one of the one or more solicitations 3-13* to one or more network servers 3-60*.

In the same or different implementations, operation 3-627 may include an operation 3-630 for transmitting at least one of the one or more solicitations to one or more sensing devices as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting at least one of the one or more solicitations 3-13* to one or more sensing devices 340**.

In the same or different implementations, operation 3-627 may include an operation 3-631 for transmitting the one or more solicitations including one or more solicitations that does not identify any of the one or more target outcomes as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations that does not identify any of the one or more target outcomes.

Various types of data may be included in the one or more solicitations 3-13* in order to identify the one or more source users 3-2**. For example, in some implementations, operation 3-627 may include an operation 3-632 for transmitting the one or more solicitations including one or more solicitations that include one or more electronic images that identify at least one of the one or more source users as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more electronic images that identify (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-627 may include an operation 3-633 for transmitting the one or more solicitations including one or more solicitations that include one or more electronic audio data that identify at least one of the one or more source users as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more electronic audio data that identify (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-627 may include an operation 3-634 for transmitting the one or more solicitations including one or more solicitations that include one or more location data that identify at least one of the one or more source users as depicted in FIG. 3-6f. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more location data that identify (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-627 may include an operation 3-635 for transmitting the one or more solicitations including one or more solicitations that include one or more radio frequency identification (RFID) data that identify at least one of the one or more source users as depicted in FIG. 3-6g. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more radio frequency identification (RFID) data that identify (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**. Such an operation may be implemented in some cases when the one or more source users 3-2** are carrying RFID tags, and an end user 3-4*, for example, wishes to identify the one or more source users 3-2** without being intrusive by using an RFID reader to read the RFID tags being carried by one or more source users 3-2**.

In the same or different implementations, operation 3-627 may include an operation 3-636 for transmitting the one or more solicitations including one or more solicitations that include one or more user names that identify at least one of the one or more source users as depicted in FIG. 3-6g. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more user names (e.g., actual user name, network username, and so forth) that identify at least one of the one or more source users 3-2**.

As a way of identifying the one or more source users 3-2**, the one or more solicitations 3-13* to be transmitted in operation 3-627 may include data that identifies one or more source user groups. For example, in some implementations, operation 3-627 may include an operation 3-637 for transmitting the one or more solicitations including one or more solicitations that identify one or more source user groups as depicted in FIG. 3-6g. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that identify one or more source user groups (e.g., social networking groups, medical patient groups, employment groups, religious groups, athletic groups or clubs, ethnic or gender groups, and so forth).

Operation 3-637 may, in turn, include an operation 3-638 for transmitting the one or more solicitations including one or more solicitations that identify one or more source user groups that share at least one common trait with the end user in various implementations as depicted in FIG. 3-6g. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that identify one or more source user groups that share at least one common trait (e.g., members of the same social networking group, common ethnicity, common illness, common medical treatment, common physical characteristics, common school or class, common field of study, and so forth) with the end user 3-4*.

As a result of transmitting the one or more solicitations 3-13** in operation 3-627, one or more reported aspects may be received. For example, in some, operation 3-627 may include an operation 3-639 for receiving the one or more reported aspects that are at least associated with the one or more source users as depicted in FIG. 3-6g. For instance, the reported aspect reception module 3-212*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b receiving the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**.

After acquiring the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2*, one or more operations may be further executed in order to identify one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more acquired reported aspects in various alternative implementations. For example, in some implementations, the acquisition operation 3-624 for acquiring the one or more reported aspects that are at least associated with the one or more source users may further include an operation 3-640 for identifying one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users as depicted in FIG. 3-6h. For instance, the relevant reported aspect identification module 3-202*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2**.

As will be further described herein, operation 3-640 may be implemented in a number of different ways in various alternative implementations. For example, in some implementations, operation 3-640 may include an operation 3-641 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users including identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from 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. 3-6h. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** including identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from 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. This may be the case, for example, when the one or more reported aspects 3-14* that were acquired and that are at least associated with the one or more source users 3-2** include both reported aspects that are relevant and reported aspects that are not relevant (e.g., relevant to achieving the one or more target outcomes).

In the same or different implementations, operation 3-640 may include an operation 3-642 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users based, at least in part, on one or more relevancy factors that at least identifies one or more aspect types that are relevant to achieving the one or more target outcomes as depicted in FIG. 3-6h. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** based, at least in part, on one or more relevancy factors that at least identifies one or more aspect types (e.g., physical activities, user states such as mental states, beliefs, and so forth) that are relevant to achieving the one or more target outcomes.

In some implementations, operation 3-642 may further include an operation 3-643 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that belong to one or more aspect types that are of interest to the end user as depicted in FIG. 3-6h. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that belong to one or more aspect types that are of interest to the end user 3-4*.

In the same or different implementations, operation 3-642 may include an operation 3-644 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that belong to one or more aspect types that have been indicated by the one or more source users as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6h. For instance, the relevant reported aspect identification module 3-202*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that belong to one or more aspect types that have been indicated by the one or more source users 3-2** as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 3-642 may include an operation 3-645 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that belong to one or more aspect types that have been indicated by one or more third party sources as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6h. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that belong to one or more aspect types that have been indicated by one or more third party sources (e.g., one or more third parties 3-6* or one or more third party source relevancy indications 3-145*) as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 3-642 may include an operation 3-646 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that indicate one or more aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 3-6i. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that indicate one or more aspects (e.g., sleep activities) that occurred within one or more predefined time periods (e.g., 24 hours), respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes (e.g., being alert and active).

In various implementations, operation 3-646 may, in turn, include an operation 3-647 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that indicate one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 3-6i. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that indicate one or more aspects (e.g., study activities) that occurred prior to and within one or more predefined time periods (e.g., two months), respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes (e.g., obtaining a particular test score for a particular test).

Various types of reported aspects may be identified by the operation 3-640 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users. For example, in some implementations, operation 3-640 may include an operation 3-648 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more behavior incidences associated with the one or more source users as depicted in FIG. 3-6j. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more behavior incidences associated with the one or more source users 3-2**.

Operation 3-648 may, in turn, include one or more additional operations. For example, in some implementations, operation 3-648 may include an operation 3-649 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more activities executed by the one or more source users as depicted in FIG. 3-6j. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more activities (e.g., dietary activities, educational or study activities, social activities, and so forth) executed by the one or more source users 3-2**.

In the same or different implementations, operation 3-648 may include an operation 3-650 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user attitudes associated with the one or more source users as depicted in FIG. 3-6j. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-648 may include an operation 3-651 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user conduct associated with the one or more source users as depicted in FIG. 3-6j. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with the one or more source users 3-2*.

In some implementations, the operation 3-640 for identifying the one or more reported aspects that are relevant to achieving the one or more target outcomes from the one or more reported aspects that are at least associated with the one or more source users may include an operation 3-652 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user beliefs associated with the one or more source users as depicted in FIG. 3-6j. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, political beliefs, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-640 may include an operation 3-653 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more subjective user states associated with the one or more source users as depicted in FIG. 3-6j. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more subjective user states (e.g., subjective user mental states, subjective user physical states, and/or subjective user overall states) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-640 may include an operation 3-654 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 3-6k. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of one or more user physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-640 may include an operation 3-655 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of user locations associated with the one or more source users as depicted in FIG. 3-6k. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of user locations (e.g., workplace, relatives' home, Los Angeles, Jamaica, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-640 may include an operation 3-656 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are related to one or more incidences of external events associated with the one or more source users as depicted in FIG. 3-6k. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are related to one or more incidences of external events (e.g., boss going on vacation, spouse visiting a relative, rainy weather, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-640 may include an operation 3-657 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that corresponds to the one or more target outcomes as depicted in FIG. 3-6k. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that corresponds to the one or more target outcomes.

In the same or different implementations, operation 3-640 may include an operation 3-658 for identifying from the one or more reported aspects that are at least associated with the one or more source users one or more reported aspects that are reported intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 3-6l. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** one or more reported aspects that are reported intermediate outcomes (e.g., typing 80 words per minute) associated with the one or more target outcomes (e.g., typing 120 words per minute).

In the same or different implementations, operation 3-640 may include an operation 3-659 for identifying from the one or more reported aspects that are at least associated with the one or more source users a first one or more reported aspects that are associated with a first source user and that are relevant to achieving a first one or more target outcomes and a second one or more reported aspects that are associated with a second source user and that are relevant to achieving a second one or more target outcomes as depicted in FIG. 3-6l. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** a first one or more reported aspects (e.g., exercising) that are associated with a first source user 3-2a* and that are relevant to achieving a first one or more target outcomes (e.g., alertness and stamina) and a second one or more reported aspects (e.g., small portion meals) that are associated with a second source user 3-2b* and that are relevant to achieving a second one or more target outcomes (e.g. weight loss).

In the same or different implementations, operation 3-640 may include an operation 3-660 for identifying from the one or more reported aspects that are at least associated with the one or more source users a first one or more reported aspects that are associated with a first source user and that are relevant to achieving at least one target outcome and 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 target outcome as depicted in FIG. 3-6l. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the one or more reported aspects 3-14* that are at least associated with the one or more source users 3-2** a first one or more reported aspects (e.g., hypnosis treatment) that are associated with a first source user 3-2a* and that are relevant to achieving at least one target outcome (e.g., self-confidence) and a second one or more reported aspects (e.g., hypnosis treatment) that are associated with a second source user 3-2b* and that are relevant to achieving the at least one target outcome (e.g., self-confidence).

In some cases, the relevant reported aspect providing operation 3-502 of FIG. 3-5 may include one or more operations for acquiring one or more reported aspects that are both associated with one or more source users and that are relevant to achieving one or more target outcomes with respect to one or more relevancy factors. For example, in some implementations, the relevant reported aspect providing operation 3-502 may include an acquisition operation 3-661 for acquiring one or more reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors that identifies one or more aspect types that are relevant for achieving at least one of the one or more target outcomes as depicted in FIG. 3-6m. Note that such an acquisition operation 3-661 is slightly different from the previously described acquisition operation 3-624 (see FIG. 3-6f), which involves acquiring one or more reported aspects that are merely associated with the one or more source users rather than acquiring one or more reported aspects that are associated with the one or more source users and that are relevant (e.g., at least based on one or more relevancy factors) to achieving one or more target outcomes. For instance, and as an illustration, the reported aspect acquisition module 3-204*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b acquiring (e.g., retrieving, soliciting, finding, and so forth) one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes based on one or more relevancy factors that identifies one or more aspect types that are relevant for achieving at least one of the one or more target outcomes.

Operation 3-661 may, in turn, include one or more additional operations in various alternative implementations. For example, in some implementations, the acquisition operation 3-661 may include an operation 3-662 for searching in a memory for the one or more reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes based on the one or more relevancy factors as depicted in FIG. 3-6m. For instance, the memory searching module 3-206*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b searching in a memory 3-116* for the one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes based on the one or more relevancy factors (e.g., one or more indications provided by the end user 3-4* or by one or more source users 3-2** as to what types of reported aspects are relevant).

In the same or different implementations, the acquisition operation 3-661 may include an operation 3-663 for searching, via at least one of a wireless network and a wired network, for the one or more reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes based on the one or more relevancy factors as depicted in FIG. 3-6m. For instance, the network searching module 3-208*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b searching, via at least one of a wireless network and a wired network 3-50*, for the one or more reported aspects 3-15* that are associated with the one or more source users 3-2**and that are relevant to achieving the one or more target outcomes, the searching being based on the one or more relevancy factors.

In order to search for the one or more reported aspects via the at least one of the wireless network and the wired network 3-50*, one or more operations for transmitting one or more solicitations 3-13* may be executed in various alternative implementations. For example, in some implementations, operation 3-663 may include an operation 3-664 for transmitting, via the at least one of the wireless network and the wired network, one or more solicitations for the one or more reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes based on the one or more relevancy factors, the one or more solicitations identifying at least one of the one or more source users as depicted in FIG. 3-6m. For instance, the solicitation transmission module 3-10*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting, via the at least one of the wireless network and the wired network 3-50*, one or more solicitations 3-13* for the one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes based on the one or more relevancy factors, the one or more solicitations 3-13* identifying at least one of the one or more source users 3-2**.

In various implementations, operation 3-664 may be executed in a variety of different ways as will be further described herein. For example, in some implementations, operation 3-664 may include an operation 3-665 for transmitting at least one of the one or more solicitations to one or more local source user devices as depicted in FIG. 3-6m. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting (e.g., via at the wireless network and/or wired network 3-50*) at least one of the one or more solicitations 3-13* to one or more local source user devices 3-20**.

In the same or different implementations, operation 3-664 may include an operation 3-666 for transmitting at least one of the one or more solicitations to one or more network servers as depicted in FIG. 3-6m. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting at least one of the one or more solicitations 3-13* to one or more network servers 3-60*.

In the same or different implementations, operation 3-664 may include an operation 3-667 for transmitting at least one of the one or more solicitations to one or more sensing devices as depicted in FIG. 3-6m. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting at least one of the one or more solicitations 3-13* to one or more sensing devices 3-40*.

In the same or different implementations, operation 3-664 may include an operation 3-668 for transmitting the one or more solicitations including one or more solicitations that does not identify any of the one or more target outcomes as depicted in FIG. 3-6m. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that does not identify any of the one or more target outcomes.

In the same or different implementations, operation 3-664 may include an operation 3-669 for transmitting the one or more solicitations including one or more solicitations that include one or more electronic images that identifies at least one of the one or more source users as depicted in FIG. 3-6m. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13** including one or more solicitations 3-13* that include one or more electronic images that identifies (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-664 may include an operation 3-670 for transmitting the one or more solicitations including one or more solicitations that include one or more audio data that identifies at least one of the one or more source users as depicted in FIG. 3-6n. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more audio data that identifies (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-664 may include an operation 3-671 for transmitting the one or more solicitations including one or more solicitations that include one or more location data that identifies at least one of the one or more source users as depicted in FIG. 3-6n. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13** including one or more solicitations 3-13* that include one or more location data that identifies (e.g., facilitates in the identification of) at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-664 may include an operation 3-672 for transmitting the one or more solicitations including one or more solicitations that include one or more radio frequency identification (RFID) data that identifies at least one of the one or more source users as depicted in FIG. 3-6n. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more radio frequency identification (RFID) data that identifies at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-664 may include an operation 3-673 for transmitting the one or more solicitations including one or more solicitations that include one or more user names that identifies at least one of the one or more source users as depicted in FIG. 3-6n. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that include one or more user names that identifies at least one of the one or more source users 3-2**.

In the same or different implementations, operation 3-664 may include an operation 3-674 for transmitting the one or more solicitations including one or more solicitations that identifies one or more source user groups as depicted in FIG. 3-6o. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that identifies one or more source user groups.

In some cases, operation 3-674 may further include an operation 3-675 for transmitting the one or more solicitations including one or more solicitations that identifies one or more source user groups that share at least one common trait with the end user as depicted in FIG. 3-6o. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that identifies one or more source user groups that share at least one common trait with the end user 3-4*.

In the same or different implementations, operation 3-664 may include an operation 3-676 for transmitting the one or more solicitations including one or more solicitations that indicate the one or more relevancy factors as depicted in FIG. 3-6o. For instance, the solicitation transmission module 3-210*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that indicate the one or more relevancy factors.

Various types of relevancy factors may be indicated by the one or more solicitations 3-13* in various alternative implementations. For example, in some implementations, operation 3-676 may include an operation 3-677 for transmitting the one or more solicitations including one or more solicitations that indicate one or more aspect types that are of interest to the end user as depicted in FIG. 3-6o. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that indicate one or more aspect types (e.g., the local weather associated with the one or more source users 3-2**, what brand or types of toiletries is being used by the one or more source users 3-2**, and so forth) that are of interest to the end user 3-4*.

In the same or different implementations, operation 3-676 may include an operation 3-678 for transmitting the one or more solicitations including one or more solicitations that indicate one or more aspect types that have been indicated by the one or more source users as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6o. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that indicate one or more aspect types (e.g., working out on exercise machines) that have been indicated by the one or more source users 3-2** as being relevant to the achievement of the one or more target outcomes (e.g., being alert at work).

In the same or different implementations, operation 3-676 may include an operation 3-679 for transmitting the one or more solicitations including one or more solicitations that indicate one or more aspect types that have been indicated by one or more third party sources as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6o. For instance, the solicitation transmission module 3-210* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more solicitations 3-13* including one or more solicitations 3-13* that indicate one or more aspect types (e.g., sleep or rest activities) that have been indicated by one or more third party sources (e.g., research publication) as being relevant to the achievement of the one or more target outcomes (e.g., body weight loss).

In some implementations, operation 3-664 may include an operation 3-680 for receiving the one or more reported aspects that are associated with the one or more source users and that are relevant with respect to the one or more relevancy factors as depicted in FIG. 3-6o. For instance, the reported aspect reception module 3-212*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b receiving the one or more reported aspects 3-15* that are associated with the one or more source users 3-2** and that are relevant with respect to the one or more relevancy factors.

In various implementations, the acquisition operation 3-661 for acquiring the one or more reported aspects that are associated with the one or more source users and that are relevant for achieving the one or more target outcomes based on one or more relevancy factors may further include one or more operations for identifying from the one or more acquired reported aspects one or more reported aspects that are relevant to achieving the one or more target outcomes based on a second one or more relevancy factors. For example, in some implementations, the acquisition operation 3-661 may include an operation 3-681 for identifying from the acquired one or more reported aspects one or more reported aspects that are relevant to achieving the one or more target outcomes based on a second one or more relevancy factors that identifies a second one or more aspect types that are relevant to achieving at least one of the one or more target outcomes as depicted in FIG. 3-6p. For instance, the relevant reported aspect identification module 3-202*(see FIG. 3-4a) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are relevant to achieving the one or more target outcomes based on a second one or more relevancy factors that identifies a second one or more aspect types that are relevant to achieving at least one of the one or more target outcomes.

Various types of relevancy factors may be involved in identifying the one or more reported aspects that are relevant from the one or more acquired reported aspects in various alternative implementations. For example, in some implementations, operation 3-681 may include an operation 3-682 for identifying from the acquired one or more reported aspects one or more reported aspects that belong to one or more aspect types that are of interest to the end user as depicted in FIG. 3-6p. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that belong to one or more aspect types that are of interest to the end user 3-4*.

In the same or different implementations, operation 3-681 may include an operation 3-683 for identifying from the acquired one or more reported aspects one or more reported aspects that belong to one or more aspect types that have been indicated by the one or more source users as being relevant to the achievement of at least one of the one or more target outcomes as depicted in FIG. 3-6p. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that belong to one or more aspect types that have been indicated by the one or more source users 3-2** as being relevant to the achievement of at least one of the one or more target outcomes.

In the same or different implementations, operation 3-681 may include an operation 3-684 for identifying from the acquired one or more reported aspects one or more reported aspects that belong to one or more aspect types that have been indicated by one or more third party sources as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 3-6p. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that belong to one or more aspect types that have been indicated by one or more third party sources (e.g., one or more third parties 3-6*) as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 3-681 may include an operation 3-685 for identifying from the acquired one or more reported aspects one or more reported aspects that indicate one or more aspects that occurred within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 3-6p. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects (e.g., reading particular books) that indicate one or more aspects that occurred within one or more predefined time periods (e.g., two months), respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes (e.g., improved or high exam score).

In some cases, operation 3-685 may further include an operation 686 for identifying from the acquired one or more reported aspects one or more reported aspects that indicate one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 3-6p. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that indicate one or more aspects that occurred prior to and within one or more predefined time periods, respectively, from one or more occurrences of one or more reported aspects that correspond to the one or more target outcomes. Note that in some cases, it may be possible for a reported aspect that is relevant to achieving a target outcome to have occurred after the occurrence of the target outcome (e.g., as indicated by a corresponding reported aspect). However, the more general case may be the case where a reported aspect that is associated with a source user 3-2** and that is relevant to achieving one or more target outcomes will also indicate an aspect that occurred prior to the achievement of the target outcome by the source user 3-2**.

Various types of reported aspects may be identified through operation 3-681 in various alternative implementations. For example, in some implementations, operation 3-681 may include an operation 3-687 for identifying from the acquired one or more reported aspects one or more relevant reported aspects that are related to one or more behavior incidences associated with the one or more source users as depicted in FIG. 3-6q. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more relevant reported aspects that are related to one or more behavior incidences associated with the one or more source users 3-2**.

Various types of behavior incidences may be indicated by the one or more relevant reported aspects identified through operation 3-687 in various alternative implementations. For example, in some implementations, operation 3-687 may include an operation 3-688 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more activities executed by the one or more source users as depicted in FIG. 3-6q. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more activities (e.g., dietary activities, exercise activities, leisure activities, social activities, employment activities, and so forth) executed by the one or more source users 3-2**.

In the same or different implementations, operation 3-687 may include an operation 3-689 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of one or more user attitudes associated with the one or more source users as depicted in FIG. 3-6q. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of one or more user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-687 may include an operation 3-690 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of one or more user conduct associated with the one or more source users as depicted in FIG. 3-6q. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of one or more user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with the one or more source users 3-2**.

Other types of reported aspects may also be identified by operation 3-681 in various implementations. For example, in some implementations, operation 3-681 may include an operation 3-691 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of one or more user beliefs associated with the one or more source users as depicted in FIG. 3-6q. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, political beliefs, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-681 may include an operation 3-692 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of one or more subjective user states associated with the one or more source users as depicted in FIG. 3-6q. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of one or more subjective user states (e.g., subjective user mental states, subjective user physical states, and/or subjective user overall states) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-681 may include an operation 3-693 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 3-6r. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of one or more user physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-681 may include an operation 3-694 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of user locations associated with the one or more source users as depicted in FIG. 3-6r. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of user locations (e.g., home, workplace, New York City, beach, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-681 may include an operation 3-695 for identifying from the acquired one or more reported aspects one or more reported aspects that are related to one or more incidences of external events associated with the one or more source users as depicted in FIG. 3-6r. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are related to one or more incidences of external events (e.g., weather conditions, heavy or no road traffic, stock market performance, and so forth) associated with the one or more source users 3-2**.

In the same or different implementations, operation 3-681 may include an operation 3-696 for identifying from the acquired one or more reported aspects one or more reported aspects that corresponds to the one or more target outcomes as depicted in FIG. 3-6r. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that corresponds to the one or more target outcomes.

In the same or different implementations, operation 3-681 may include an operation 3-697 for identifying from the acquired one or more reported aspects one or more reported aspects that are reported intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 3-6r. For instance, the relevant reported aspect identification module 3-202* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b identifying from the acquired one or more reported aspects 3-15* one or more reported aspects that are reported intermediate outcomes (e.g. running a mile in 6 minutes) associated with the one or more target outcomes (e.g., running a mile in 5 minutes).

The one or more relevant reported aspects to be provided by the relevant reported aspect providing operation 3-502 of FIG. 3-5 may have been originally obtained by various alternative means. For example, in some implementations, the relevant reported aspect providing operation 3-502 may include an operation 3-698 for providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more log entries as depicted in FIG. 3-6s. For instance, the relevant reported aspect provision module 3-102* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more log entries.

The one or more “log entries” referred to above may be in reference to any type of electronic entries that may be regularly or randomly entered electronically and that may indicate one or more aspects associated with one or more source users 3-2**. For example, in some implementations, operation 3-698 may include an operation 3-699 for providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more blog entries as depicted in FIG. 3-6s. For instance, the relevant reported aspect provision module 3-102* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more blog entries (e.g., microblog entries).

In the same or different implementations, operation 3-698 may include an operation 3-700 for providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more status reports as depicted in FIG. 3-6s. For instance, the relevant reported aspect provision module 3-102* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more status reports (e.g., social networking status reports).

In the same or different implementations, operation 3-698 may include an operation 3-701 for providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more journal entries as depicted in FIG. 3-6s. For instance, the relevant reported aspect provision module 3-102* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via one or more journal entries (e.g., diary entries).

In the same or different implementations, operation 3-698 may include an operation 3-702 for providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via log entries as provided by one or more sensing devices as depicted in FIG. 3-6s. For instance, the relevant reported aspect provision module 3-102* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b providing the one or more relevant reported aspects including providing one or more relevant reported aspects that were at least originally reported via log entries as provided by one or more sensing devices 3-40*.

Referring back to the development operation 3-504 of FIG. 3-5 and as will be further described herein, the development operation 3-504 may include one or more additional operations in various implementations. For example, in some implementations, the development operation 3-504 may include an operation 3-703 for including into each of the one or more personalized plans one or more emulatable aspects that correspond to the one or more relevant reported aspects that are associated with one or more source users and that are relevant to achieving one or more target outcomes as depicted in FIG. 3-7a. For instance, the emulatable aspect inclusion module 3-220*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into each of the one or more personalized plans 3-16* one or more emulatable aspects that correspond to the one or more relevant reported aspects (e.g., as provided through the relevant reported aspect providing operation 3-502) that are associated with one or more source users 3-2** and that are relevant to achieving one or target outcomes.

In some cases, operation 3-703 may further include an operation 3-704 for including into each of the one or more personalized plans a plurality of emulatable aspects that corresponds to a plurality of relevant reported aspects that are associated with one or more source users and that are relevant to achieving the one or more target outcomes as depicted in FIG. 3-7a. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into each of the one or more personalized plans 3-16* a plurality of emulatable aspects that corresponds to a plurality of relevant reported aspects that are associated with one or more source users 3-2** and that are relevant to achieving the one or more target outcomes.

In turn, operation 3-704 may include, in various implementations, an operation 3-705 for defining in each of the one or more personalized plans one or more relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 3-7a. For instance, the relationship defining module 3-222*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b defining in each of the one or more personalized plans 3-16* one or more relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 3-16*.

Various types of relationships may be defined in the one or more personalized plans 3-16* to be developed in various alternative implementations. For example, in some implementations, operation 3-705 may include an operation 3-706 for defining in each of the one or more personalized plans one or more temporal relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 3-7a. For instance, the relationship defining module 3-222* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b defining in each of the one or more personalized plans 3-16* one or more temporal relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 3-16*. As a further illustration, for example, indicating in a personalized plan 3-16* to read a particular book first (e.g., a first emulatable aspect) before reading a second book (e.g., a second emulatable event) without providing a specific indication of the specific time relationship between the first and second emulatable aspects.

In the same or different implementations, operation 3-705 may include an operation 3-707 for defining in each of the one or more personalized plans one or more specific time relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 3-7a. For instance, the relationship defining module 3-222* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b defining each of the one or more personalized plans 3-16* one or more specific time relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 3-16*. As a further illustration, for example, indicating in a personalized plan 3-16* to walk for one hour (e.g., a first emulatable aspect) on a first day, and jogging for 30 minutes (e.g., a second emulatable aspect) two days later (e.g., specific time relationship).

In the same or different implementations, operation 3-705 may include an operation 3-708 for defining in each of the one or more personalized plans one or more spatial relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 3-7a. For instance, the relationship defining module 3-222* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b defining each of the one or more personalized plans 3-16* one or more spatial relationships between the plurality of emulatable aspects included in each of the one or more personalized plans 3-16*. As a further illustration, for example, indicating in a personalized plan 3-16* to drink coffee (e.g., a first emulatable aspect) at home, and to drink tea (e.g., a second emulatable aspect) at work.

In the same or different implementations, the operation 3-704 for including into each of the one or more personalized plans a plurality of emulatable aspects may include an operation 3-709 for including into at least one of the one or more personalized plans one or more emulatable intermediate outcomes related to the one or more target outcomes as depicted in FIG. 3-7a. For instance, the emulatable intermediate outcome inclusion module 3-223 (see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into at least one of the one or more personalized plans 3-16* one or more emulatable intermediate outcomes related to the one or more target outcomes. As a further illustration, for example, including into a personalized plan 3-16* for losing 30 pounds (e.g., target outcome) an emulatable intermediate outcome of 20 pounds at some point during the execution of the personalized plan 3-16*.

In various implementations, the operation 3-703 for including into each of the one or more personalized plans one or more emulatable aspects that correspond to the one or more relevant reported aspects may include an operation 3-710 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7b. For instance, the limitation compliance determination module 3-224*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with (e.g., does not violate) one or more limitations associated with the end user 3-4*(e.g., limitations that prevent or make it impractical for the one or more emulatable aspects to be successfully emulated), and if not, execute one or more actions.

In various implementations, operation 3-710 may further include one or more additional operations. For example, in some implementations, operation 3-710 may include an operation 3-711 for notifying at least one of the end user and a third party regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user as depicted in FIG. 3-7b. For instance, the non-compliance notification module 3-226*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b notifying at least one of the end user 3-4* and a third party 3-6* regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user 3-4*.

In the same or different implementations, operation 3-710 may include an operation 3-712 for modifying the one or more personalized plans including replacing one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user as depicted in FIG. 3-7b. For instance, the personalized plan modification module 3-228*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b modifying the one or more personalized plans 3-16* including replacing one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 3-4* with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user 3-4*. As a further illustration, if an emulatable aspect such as swimming for 40 minutes is determined to be non-compliant, than replacing the non-compliant emulatable aspect with a complaint emulatable aspect (e.g., jogging for 1 hour that results in the same amount of calories being burned) that is at least proximately equivalent, at least in substance, to the non-compliant emulatable aspect. Of course, what is “proximately equivalent” will depend on the type of emulatable aspect being replaced and the type of personalized plan 3-16* being developed.

In the same or different implementations, operation 3-710 may include an operation 3-713 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more physical limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7b. For instance, the limitation compliance determination module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with one or more physical limitations (e.g., missing limb, paralysis, visual or hearing impediment, and so forth) associated with the end user 3-4*, and if not, execute one or more actions.

In the same or different implementations, operation 3-710 may include an operation 3-714 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more contextual limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7b. For instance, the limitation compliance determination module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with one or more contextual limitations (e.g., logistical limitations such as scheduling limitations, geographical limitations, asset limitations, and so forth) associated with the end user 3-4*, and if not, execute one or more actions.

In the same or different implementations, operation 3-710 may include an operation 3-715 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more personal limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7c. For instance, the limitation compliance determination module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with 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 3-4*, and if not, execute one or more actions.

In the same or different implementations, operation 3-710 may include an operation 3-716 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more medical or health limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7c. For instance, the limitation compliance determination module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with one or more medical or health limitations (e.g., medical limitations such as limitations resulting from an illness or treatment of an illness including limitations due to cancer or treatment of the cancer, health limitations related to the physical conditioning of the end user 3-4*, genetic limitations, and so forth) associated with the end user 3-4*, and if not, execute one or more actions.

In the same or different implementations, operation 3-710 may include an operation 3-717 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more user state limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7c. For instance, the limitation compliance determination module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with one or more user state limitations (e.g., end user 3-4* is married, end user 3-4* is in mourning, end user 3-4* is unemployed, end user 3-4* is a vegan, and so forth) associated with the end user 3-4*, and if not, execute one or more actions.

In the same or different implementations, operation 3-710 may include an operation 3-718 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more legal or regulatory limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 3-7c. For instance, the limitation compliance determination module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether the one or more emulatable aspects to be included in the one or more personalized plans 3-16* complies with one or more legal or regulatory limitations (e.g., drug regulations, laws related to conduct or behavior in the jurisdiction of the end user 3-4*, and so forth) associated with the end user 3-4*, and if not, execute one or more actions.

In various implementations, the operation 3-703 for including into each of the one or more personalized plans one or more emulatable aspects may include an operation 3-719 for determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans is a plausible aspect that has been successfully emulated by one or more third parties, and if not, execute one or more actions as depicted in FIG. 3-7d. For instance, the plausible determination module 3-230*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is a plausible aspect that has been successfully emulated by one or more third parties 3-6*(e.g., other end users), and if not, execute one or more actions.

In various alternative implementations, operation 3-719 may include one or more additional operations. For example, in some implementations, operation 3-719 may include an operation 3-720 for notifying, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans is not a plausible aspect, at least one of the end user and a third party regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans is not a plausible aspect as depicted in FIG. 3-7d. For instance, the not plausible notification module 3-234*(see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b notifying in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is not a plausible aspect, at least one of the end user 3-4* and a third party 3-6* regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is not a plausible aspect.

In the same or different implementations, operation 3-719 may include an operation 3-721 for modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more personalized plans by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties as depicted in FIG. 3-7d. For instance, the personalized plan modification module 3-236* (see FIG. 3-4b) of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more personalized plans 3-16* by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 3-6*.

In the same or different implementations, operation 3-719 may include an operation 3-722 for determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans is a plausible aspect that has been successfully emulated by one or more third parties in order to achieve at least one of the one or more target outcomes, and if not, execute one or more actions as depicted in FIG. 3-7d. For instance, the plausible determination module 3-230* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 3-16* is a plausible aspect that has been successfully emulated by one or more third parties 3-6* in order to achieve at least one of the one or more target outcomes, and if not, execute one or more actions.

In certain implementations, the operation 3-703 for including into each of the one or more personalized plans one or more emulatable aspects may include an operation 3-723 for including into at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more source user behaviors associated with a source user as depicted in FIG. 3-7e. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more source user behaviors (e.g., dietary behavior, physical activity behavior, behavior towards others, mental or physical acts, and so forth) associated with a source user 3-2a*.

In various implementations, operation 3-723 may include one or more additional operations. For example, in some implementations, operation 3-723 may include an operation 3-724 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more physical acts executed by a source user as depicted in FIG. 3-7e. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more physical acts (e.g., consume a food item or a medicine, attend class, read, exercise, and so forth) executed by a source user 3-2a*.

In the same or different implementations, operation 3-723 may include an operation 3-725 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user attitudes associated with a source user as depicted in FIG. 3-7e. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with a source user 3-2a*.

In the same or different implementations, operation 3-723 may include an operation 3-726 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user conduct associated with a source user as depicted in FIG. 3-7e. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with a source user 3-2a*.

In various implementations, the operation 3-703 for including into each of the one or more personalized plans one or more emulatable aspects may include an operation 3-727 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user beliefs associated with a source user as depicted in FIG. 3-7f. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, and so forth) associated with a source user 3-2a*.

In the same or different implementations, operation 3-703 may include an operation 3-728 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user states associated with a source user as depicted in FIG. 3-7f. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user states (e.g., subjective user states, marital states, employment state, physical state, availability state, and so forth) associated with a source user 3-2**.

In the same or different implementations, operation 3-703 may include an operation 3-729 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more physical characteristics associated with a source user as depicted in FIG. 3-7f. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with a source user 3-2a*.

In the same or different implementations, operation 3-703 may include an operation 3-730 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user locations associated with a source user as depicted in FIG. 3-7f. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more user locations (e.g., home, workplace, New York City, beach, and so forth) associated with a source user 3-2a*.

In the same or different implementations, operation 3-703 may include an operation 3-731 for including into the at least one of the one or more personalized plans at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more external events associated with a source user as depicted in FIG. 3-7f. For instance, the emulatable aspect inclusion module 3-220* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b including into the at least one of the one or more personalized plans 3-16* at least one emulatable aspect that corresponds to at least one of the one or more relevant reported aspects that are associated with the one or more source users 3-2** and that are relevant to achieving the one or more target outcomes, the at least one of the one or more reported aspects being related to one or more incidences of one or more external events (e.g., hot or cold weather, heavy or no auto traffic, stock market performance, visit by a relative, and so forth) associated with a source user 3-2a*.

In various implementations, the personalized plan development operation 3-504 of FIG. 3-5 may include an operation 3-732 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more health or medical outcomes as depicted in FIG. 3-7g. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan that is designed to facilitate the end user 3-4* to achieve 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 3-732 may include, in various implementations, one or more additional operations as will be further described herein. For example, in some implementations, operation 3-732 may include an operation 3-733 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more physiological outcomes as depicted in FIG. 3-7g. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more physiological outcomes (e.g., reducing blood pressure or blood glucose levels, increase red blood cell count, improve blood circulation, and so forth).

In the same or different implementations, operation 3-732 may include an operation 3-734 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more physical fitness outcomes as depicted in FIG. 3-7g. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16 including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve 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 3-732 may include an operation 3-735 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more physical fitness training outcomes as depicted in FIG. 3-7g. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more physical fitness training outcomes (e.g., shorter time to recover from vigorous exercise, increase stamina during fitness training, reduce water loss during vigorous exercise, and so forth).

In the same or different implementations, operation 3-732 may include an operation 3-736 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more medical treatment outcomes as depicted in FIG. 3-7g. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve 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 3-732 may include an operation 3-737 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more fitness lifestyle outcomes as depicted in FIG. 3-7g. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more fitness lifestyle outcomes (e.g., improved exercise activities, improved dietary activities such as reduced calorie or cholesterol consumption, and so forth).

In some implementations, the personalized plan development operation 3-504 of FIG. 3-5 may include an operation 3-738 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more athletic outcomes as depicted in FIG. 3-7h. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve 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 the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-739 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more gaming outcomes as depicted in FIG. 3-7h. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more gaming outcomes (e.g., winning a chest tournament or improve video gaming skills).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-740 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more occupational outcomes as depicted in FIG. 3-7h. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more occupational outcomes (e.g., a job promotion, complete a work project on time, develop new occupational relationships, and so forth).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-741 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more social outcomes as depicted in FIG. 3-7h. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more social outcomes (e.g., attaining a certain social class, having a dinner date with a particular person, developing a particular reputation, develop or expand social networks, and so forth).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-742 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more leisure outcomes as depicted in FIG. 3-7h. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan that is designed to facilitate the end user 3-4* to achieve 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 the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-743 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more sexual intimacy outcomes as depicted in FIG. 3-7h. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more sexual intimacy outcomes (e.g., increased sexual activities, increased sexual performance, and so forth).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-744 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more psychological outcomes as depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more psychological outcomes (e.g., overcoming a phobia, overcoming certain addictive behavior such as compulsion to be clean, and so forth).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-745 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more intellectual or academic outcomes depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more intellectual or academic outcomes (e.g., passing a particular exam or class, obtaining a certain degree or academic award, being accepted into a particular program or school, attaining a particular scholarship, understanding a complex concept, acquiring particular knowledge, and so forth).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-746 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more user states depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more user states (e.g., mental states, marital states, employment state, physical state, availability state, and so forth).

In turn, operation 3-746 may further include one or more additional operations. For example, in some implementations, operation 3-746 may include an operation 3-747 for developing the one or more personalized plans including the at least one personalized plan that is designed to facilitate the end user to achieve one or more subjective user states depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including the at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more subjective user states (e.g., subjective user mental states, subjective user physical states, and/or subjective user overall states).

In the same or different implementations, operation 3-746 may include an operation 3-748 for developing the one or more personalized plans including the at least one personalized plan that is designed to facilitate the end user to achieve one or more user social states as depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including the at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more user social states (e.g., membership to a social group, being married, being single and so forth).

In the same or different implementations, operation 3-746 may include an operation 3-749 for developing the one or more personalized plans including the at least one personalized plan that is designed to facilitate the end user to achieve one or more users employment states as depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including the at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more users employment states (e.g., being employed, attaining a particular employment position, attaining managerial authority, and so forth).

In the same or different implementations, the personalized plan development operation 3-504 may include an operation 3-750 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more spiritual or faith-based outcomes as depicted in FIG. 3-7i. For instance, the personalized plan development module 3-104* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b developing the one or more personalized plans 3-16* including at least one personalized plan 3-16* that is designed to facilitate the end user 3-4* to achieve one or more spiritual or faith-based outcomes (e.g., greater self-awareness or satisfaction, greater tolerance of the difference of others, and so forth).

Referring to FIG. 3-8 illustrating another operational flow 3-800 in accordance with various embodiments. Operational flow 3-800 includes certain operations that mirror the operations included in the operational flow 3-500 of FIG. 3-5. These operations include a relevant reported aspect providing operation 3-802 and a personalized plan development operation 3-804 that corresponds to and mirror the relevant reported aspect providing operation 3-502 and the personalized plan development operation 3-504, respectively, of FIG. 3-5.

In addition, operational flow 3-800 includes a presentation operation 3-806 for presenting the one or more personalized plans as depicted in FIG. 3-8. For instance, the presentation module 3-106* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b presenting (e.g., transmitting via the wireless network and/or wired network 3-50* or indicating via a user interface 3-120*) the one or more personalized plans 3-16*.

In various alternative implementations, the presentation operation 3-806 may include one or more additional operations. For example, in some implementations, the presentation operation 3-806 may include an operation 3-952 for transmitting the one or more personalized plans via at least one of wireless network and a wired network as depicted in FIG. 3-9. For instance, the transmission module 3-224* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b transmitting the one or more personalized plans 3-16* via at least one of wireless network and a wired network 3-50*.

In the same or different implementations, the presentation operation 3-806 may include an operation 3-953 for indicating the one or more personalized plans via user interface as depicted in FIG. 3-9. For instance, the user interface indication module 3-226* of the local source user device 3-20′ of FIG. 3-2b or the local end user device 3-30″ of FIG. 3-3b audibly or visually indicating the one or more personalized plans 3-16* via a user interface 3-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 3-806 may include an operation 3-954 for presenting the one or more personalized plans to the end user as depicted in FIG. 3-9. For instance, the presentation module 3-106* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b presenting the one or more personalized plans 3-16* to the end user 3-4*.

In the same or different implementations, the presentation operation 3-806 may include an operation 3-955 for presenting the one or more personalized plans to one or more third parties as depicted in FIG. 3-9. For instance, the presentation module 3-106* of the server 3-10 of FIG. 3-1b, the local source user device 3-20′ of FIG. 3-2b, or the local end user device 3-30″ of FIG. 3-3b presenting the one or more personalized plans 3-16* to one or more third parties 3-6*.

Turning now to FIG. 3-10 illustrating a computing device 3-1000 designed to implement one or more of the operations of the operational flows described above (e.g., as illustrated in FIGS. 3-5, 3-6a, 3-6b, 3-6c, 3-6d, 3-6e, 3-6f, 3-6g, 3-6h, 3-6i, 3-6j, 3-6k, 3-6l, 3-6m, 3-6n, 3-6o, 3-6p, 3-6q, 3-6r, 3-6s, 3-7a, 3-7b, 3-7c, 3-7d, 3-7e, 3-7f, 3-7g, 3-7h, 3-7i, 3-8, and 3-9). In various implementations, the computing device 3-1000 may be a server such as the server 3-10 of FIG. 3-1b or a local client device such as the local source user device 3-20a′ of FIG. 3-2b or the local end user device 3-30″ of FIG. 3-3b.

As illustrated, the computing device 3-1000 may include a processor 3-1002 (e.g., microprocessor, controller, and so forth) coupled to storage medium 3-1006 (e.g., volatile or non-volatile memory). The storage medium 3-1006 may store computer readable instructions 3-1004 (e.g., computer program product). The processor 3-1002, in various implementations, may execute the computer readable instructions 3-1004 in order to execute one or more operations described above and as illustrated in FIGS. 3-5, 3-6a, 3-6b, 3-6c, 3-6d, 3-6e, 3-6f, 3-6g, 3-6h, 3-6i, 3-6j, 3-6k, 3-6l, 3-6m, 3-6n, 3-6o, 3-6p, 3-6q, 3-6r, 3-6s, 3-7a, 3-7b, 3-7c, 3-7d, 3-7e, 3-7f, 3-7g, 3-7h, 3-7i, 3-8, and 3-9.

For example, the processor 3-1002 may execute the computer readable instructions 3-1004 in order to provide one or more relevant reported aspects associated with one or more source users 3-2* 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 3-2*; and/or to develop one or more personalized plans 3-16* designed to facilitate an end user 3-4* to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 3-16* are emulated, the development of the one or more personalized plans 3-16* being based, at least in part, on the providing as depicted in the operational flow 3-500 of FIG. 3-5.

V. Personalized Plan Development Based on Identification of One or More Relevant Reported Aspects

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 journal. One place where such open journals 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 particular act, behavior, characteristic, user state or status, belief, 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 become very popular in recent times 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 journals and to allow users to easily update their personal information. 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 aspects associated with users. Examples of sensors that may be used for such purposes vary widely, ranging from traditional devices that can detect and report on physiological parameters such as heart rate or blood pressure, to sensors that can detect certain user behaviors or activities such as toilet usage. Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, sensor data, and so forth) 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, methods, systems, circuitry, and computer program products are provided for developing, among other things, 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. In particular, the methods, systems, circuitry, and computer program products may be designed to identify (e.g., determine or find) one or more relevant reported aspects associated with one or more source users that are relevant to achieving the one or more target outcomes, the identification based at least in part on the one or more relevant reported aspects' relevancy with respect to the one or more target outcomes. Based on the identification of the one or more relevant reported aspects, the one or more personalized plans may then be developed by including into the one or more personalized plans the one or more emulatable aspects that may correspond to the one or more relevant reported aspects. The methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, by a network device such as a server (e.g., network servers) or a local client device.

In some embodiments, the methods, systems, circuitry, and computer program products may be employed in order to, for example, identify from a large (or small) quantity of data that may indicate a plurality of reported aspects associated with one or more source users one or more reported aspects that may be relevant to achieving one or more target outcomes. For these embodiments, the large quantity of data to be examined may include data that indicate both relevant and non-relevant reported aspects (e.g., not relevant to achieving the one or more target outcomes) that are associated with one, few, or many source users.

As will be described herein, an “aspect” may be any behavior, act, belief, characteristic, state, and so forth associated with a particular person (i.e., a source user). A “reported aspect” may be any aspect associated with the person that has been reported. In some embodiments, a reported aspect may have been originally reported via log entries such as blog or microblog entries, status reports, journal entries, sensing device entries, and so forth. In some cases, a reported aspect may be at least originally reported by the source user that the reported aspect is associated with, by a sensing device that detects the aspect to be reported, or by a third party (e.g., another source user who may be reporting on an aspect of the first source user).

The determination of whether a reported aspect is relevant for achieving a particular target outcome (e.g., goal) may be based on one or more factors including one or more “relevancy factors.” For example, in some embodiments, a reported aspect may only be relevant for achieving a particular target outcome only if the reported aspect is associated with a source user who has achieved the target outcome. That is, reported aspects that are associated with a source user who has not achieved the target outcome will most likely not be relevant to the achievement of the target outcome. Instead, only reported aspects that are associated with a “successful” source user (e.g., a source user who has achieved the target outcome) may be relevant to the achievement of the target outcome. And even if a reported aspect is determined to be associated with a source user who has achieved the target outcome, such a reported aspect may not necessarily be relevant as many, if not most, reported aspects that are associated with the source user may be completely immaterial to the achievement of the target outcome.

Thus, other factors such as “relevancy factors” may be considered when determining whether a particular reported aspect that is associated with a source user who has achieved the target outcome is actually relevant to the achievement of the target outcomes. Such relevancy factors may include, for example, whether the reported aspect associated with the successful source user indicates an aspect that occurred proximate to the achievement of the target outcome by the successful source user. That is, reported aspects associated with the successful source user that indicate aspects that occurred well before or well after the achievement of the target outcome by the successful source user may not have any bearing or relationship (e.g., causal relationship) with respect to the achievement of the target outcome.

For example, suppose an end user is interested in losing at least 20 pounds of body weight in two months (e.g., target outcome). Suppose further that a particular source user such as a microblogger has been determined to have lost 25 pounds of body weight in two months. In determining which reported aspects (e.g., dietary behavior, exercise activities, sleep activities, study activities, and so forth) associated with the source user may be relevant to achieving the target outcome, those reported aspects that indicate aspects (e.g., exercise activities) of the source user that occurred well before (e.g., one year before) the occurrence or achievement of the target outcome (e.g., 25 pound body weight loss in two months) by the source user will likely be considered not relevant.

Other relevancy factors may also be considered in determining whether a reported aspect is relevant to the achievement of the target outcome. For example, determining whether the reported aspect belong to an aspect type that is of interest to the end user. Suppose, for example, the end user in the above example believes that the key to losing weight is to have a good night's sleep. In that case, only reported aspects that relate to, for example, the sleep activities of the successful source user may be considered as being relevant. In some cases, the successful source user may also indicate what aspects or types of aspects associated with the source user may have contributed to his achievement of the target outcome. In such cases, only those reported aspects associated with the successful source user and that belong to the types of aspects that the successful source user considers relevant to achieving the target outcome may be considered as a relevant reported aspect. In still other cases, the relevancy of a reported aspect may be based on indications provided by one or more third party sources such as other source users (e.g., those who may not have achieved the target outcome), other end users, publications, medical research, and so forth, that may indicate the types of aspects that may be relevant to achieving the target outcome.

In any event, based at least in part on the identification of the one or more relevant reported aspects, one or more personalized plans may be developed that are designed to facilitate the end user to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans are emulated. In some embodiments, the development of the one or more personalized plans may be prompted when, for example, a request (e.g., a query, a command, a solicitation, and so forth) is received that may identify at least one of the one or more target outcomes. For these embodiments, the request may originate from an end user, a source user, a third party (e.g., a network service provider, a content provider, and so forth), or from some other origin.

A personalized plan may merely be a collection of one or more emulatable aspects. An emulatable aspect may be an indication of any behavior, act, trait, physical state, mental state, social state, declaration, belief, or any other facet of a person (i.e., source user) that may be emulated in order to achieve one or more target outcomes. In some cases, a personalized plan may include only a single emulatable aspect. For example, a personalized plan for reducing cavities (e.g., target outcome) may include a single emulatable aspect (e.g., avoid sweet desserts). In other cases, a personalized plan may include multiple emulatable aspects. For example, a personalized plan to lose 20 pounds of body weight (e.g., target outcome) may include multiple emulatable aspects (e.g., the personalized plan includes a schedule of swimming and jogging activities where each activity is an emulatable aspect). 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 multiple emulatable aspects included in the personalized plan. For instance, in the above weight loss example, the personalized plan may indicate when certain activities should be executed with respect to other activities (e.g., swimming on day one, jogging on day two, and so forth).

In some cases, a personalized plan may also indicate one or more emulatable intermediate outcomes that may be associated with one or more target outcomes of the personalized plan. For example, if a personalized plan includes a plurality of emulatable aspects, then one or more emulatable intermediate outcomes may also be included in the personalized plan that may represent one or more outcomes that are preferably or ideally achieved while the personalized plan is being executed and 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 one or more reported aspects (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 achieving 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 (real) 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 indicating actual aspects of a plurality of real source users may be compiled and processed (e.g., normalized or averaged out) in order to create such a fictional source user.

Turning now to FIGS. 4-1a, and 4-1b 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 4-10. In various embodiments, the computing device 4-10 may be a server such as one of the one or more network servers 4-60, a source user device such as one of the local source user devices 4-20*, or an end user device such as the local end user device 4-30. More particularly, the methods, systems, circuitry, and computer program products may be implemented at any network device including a peer-to-peer network component device. In some embodiments, the computing device 4-10 may operate via a web 1.0 or web 2.0 construct. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 4-2*” may be in reference to a source user 4-2a, a source user 4-2b, and so forth.

In various embodiments, the computing device 4-10 may be designed to, among other things, identify one or more relevant reported aspects associated with one or more source users 4-2* 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. After identifying the one or more relevant reported aspects, the computing device 4-10, may be designed to, among other things, develop one or more personalized plans 4-16 designed to facilitate an end user 4-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 4-16 are emulated, the development of the one or more personalized plans 4-16 being based, at least in part, on the identifying of the one or more relevant reported aspects.

In some implementations, the operation to identify the one or more relevant aspects may be prompted when the computing device 4-10, for example, receives a request 4-12 (e.g., a solicitation, a query, and so forth) from an end user 4-4 (e.g., via a local end user device 4-30), from a source user 4-2*(e.g., via a local source user device 4-20*), from a network server 4-60, or from a third party 4-6 (e.g., a network service provider, a content provider, and so forth). For these implementations, the request 4-12 may at least indicate one of the one or more target outcomes, and in some cases, may request for the one or more personalized plans 4-16. In some implementations, the request 4-12 may not indicate a source user 4-2*, and in particular, may not indicate any source user 4-2* who may have successfully achieved the one or more target outcomes.

As illustrated, in various embodiments the computing device 4-10 may be employed in a network environment. For example, the computing device 4-10 may communicate with other network devices (e.g., a local end user device 4-30, one or more network servers 4-60, one or more local source user devices 4-20*, one or more sensing devices 4-40, and so forth) via a wireless network and/or wired network 4-50 (e.g., at least one of a wireless network and a wired network 4-50). In various implementations, the wireless and/or wired network 4-50 may include 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 4-50.

Note again that in various alternative implementations the computing device 4-10 may be a server, a source user device (e.g., local source user device 4-20*), or an end user device (e.g., local end user device 4-30). However, for ease of explanation and understanding, the following description of the exemplary environment of FIGS. 4-1a and 4-1b will be from a perspective in which the computing device 4-10 is operating as a server rather than as an end user device or as a source user device. And although the computing device 4-10 in the following will be described from a server perspective (e.g., server embodiment), the following description of the functionalities of the computing device 4-10 will generally hold true even if the computing device 4-10 were operating as a source user device (e.g., source user embodiment) or as an end user device (e.g., end user embodiment) with a few minor exceptions.

For example, if the computing device 4-10 is a source user device such as a local source user device 4-20*, then the computing device 4-10 may directly communicate with a source user 4-2* via a user interface 4-120 rather through a wireless network and/or a wired network 4-50 as is the case when the computing device 4-10 is a server. Similarly, if the computing device 4-10 is an end user device such as a local end user device 4-30, then the computing device 4-10 may directly communicate with an end user 4-4 via the user interface 4-120 instead of through the wireless network and/or the wired network 4-50.

Referring particularly now to FIGS. 4-1a and 4-1b, which illustrates an example environment in accordance with various embodiments. Included in the illustrated environment of FIGS. 4-1a and 4-1b is an exemplary system 4-100, which includes at least a computing device 4-10 that may be designed to communicate with one or more source users 4-2*(via one or more local source user devices 4-20*) and an end user 4-4 (via a local end user device 4-30) through a wireless network and/or wired network 4-50. In some implementations, the computing device 4-10 may further communicate with, via the wireless network and/or wired network 4-50, one or more third parties 4-6 (e.g., one or more other end users 4-4, one or more content providers, one or more network service providers, and/or one or more other parties), one or more other network servers 4-60, and/or one or more sensing devices 4-40.

With respect to the one or more sensing devices 4-40, the one or more sensing devices 4-40 may communicate with the wireless network and/or the wired network 4-50 directly or indirectly via the one or more local source user devices 4-20*. As will be further described herein with respect to FIG. 4-2c, each of the one or more sensing devices 4-40 (see FIG. 4-2c) may include one or more sensors 4-240, a network interface 4-242, and/or a memory 4-244. The one or more sensors 4-240 may be designed to detect or sense one or more aspects associated with one or more source users 4-2*. Examples of sensors 4-240 include, for example, devices that can detect physical or physiological characteristics of one or more source users 4-2*, devices that can detect activities of the one or more source users 4-2*, devices that can detect external events (e.g., environmental conditions including the weather, pollution levels, performance of the stock market, and so forth), image capturing device such as a digital camera or camcorder, and/or devices that can detect the location of the one or more source users 4-2* such as a global positioning system or GPS. Examples of devices that can detect physical or physiological characteristics include, for example, a heart rate monitor, a blood pressure sensor, a glucose sensor, and so forth. Examples of devices that can detect activities of the one or more source users 4-2* including, for example, 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.

In various implementations, the computing device 4-10 may be a computing/communication device that is designed to interface with a wireless network and/or wired network 4-50. In some embodiments, the computing device 4-10 may be a network server 4-60 that may be located at a single network site, located across multiple network sites, or a conglomeration of servers located at multiple network sites. In embodiments in which the computing device 4-10 is a source user device (e.g., local source user device 4-20*) or an end user device (e.g., local end user device 4-30*), the computing device 4-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.

The one or more source users 4-2* may comprise a first source user 4-2a, a second source user 4-2b, a third source user 4-2c, a fourth source user 4-2d, and so forth. The one or more local source user devices 4-20* may include a first local source user device 4-20a (e.g., to be used by the first source user 4-2a to communicate via wireless network and/or wired network 4-50), a second local source user device 4-20b (e.g., to be used by the second source user 4-2b to communicate via wireless network and/or wired network 4-50), and so forth. The one or more local source user devices 4-20* and the local end user device 4-30 (as well as the computing device 4-10 in embodiments in which the computing device 4-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 4-20 and/or the local end user device 4-30 (as well as the computing device 4-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 4-20 and/or local end user device 4-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.

Referring back to the exemplary environment of FIGS. 4-1a and 4-1b, the computing device 4-10 in various implementations may be designed to collect one or more reported aspects 4-14 (e.g., in the form of data) from one or more sources including, for example, one or more local source user devices 4-20*, one or more sensing devices 4-40, one or more network servers 4-60, and/or one or more third parties 4-6. In some implementations, the one or more reported aspects 4-14 to be collected may indicate one or more aspects associated with one or more source users 4-2*. The reported aspects 4-14 may be received in a variety of forms including, for example, log entries such as blog entries, status reports, journal entries, entries provided by sensing devices 4-40, and/or other types of entries. In embodiments where the computing device 4-10 is a source user device (e.g., local source user device 4-20*), the computing device 4-10 may receive reported aspects 4-14 through a user interface 4-120. In some cases, after collecting the reported aspects 4-14, the reported aspects 4-14 may be stored in a memory 4-116.

In some implementations, the computing device 4-10 may be designed to receive a request 4-12 (e.g., a solicitation for one or more personalized plans 4-16) from a variety of different sources. For example, the request 4-12 may be received from an end user 4-4, from a third party 4-6, from a source user 4-2*, or from a network server 4-60. For these embodiments, the request 4-12 may at least identify one or more target outcomes of one or more personalized plans 4-16, and in some cases, may not identify any source users 4-2* who may have achieved the one or more target outcomes. In embodiments where the computing device 4-10 is a source user device or an end user device, the computing device 4-10 may receive the request 4-12 via a user interface 4-120.

In response to receiving the request 4-12, the computing device 4-10 may identify one or more relevant reported aspects associated with the one or more source users 4-2* 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. The identification of the one or more relevant reported aspects may be based on one or more factors including relevancy factors as will be further described herein. Further, the identification of the one or more relevant reported aspects may be from a plurality of reported aspects that include both reported aspects that may be relevant for achieving the one or more target outcomes and reported aspects that may not be relevant for achieving the one or more target outcomes. In any event, based on the identification of the one or more relevant reported aspects, the computing device 4-10 may be designed to develop one or more personalized plans 4-16 designed to facilitate an end user 4-4 to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans 4-16 are emulated.

The computing device 4-10 as illustrated in FIG. 4-1b may include a variety of modules, sub-modules, and various other components. As shown, the computing device 4-10 may include a relevant reported aspect identification module 4-102 (which may further include one or more sub-modules as illustrated in FIG. 4-2a), a personalized plan development module 4-104 (which may further include one or more sub-modules as illustrated in FIG. 4-2b), a presentation module 4-106 (which may further include a transmission module 4-224 and/or a user interface indication module 4-226), a memory 4-116 (which may store a plurality of reported aspects 4-14, one or more end user relevancy indications 4-142, one or more end user limitations 4-143, one or more source user relevancy indications 4-144, one or more third party source relevancy indications 4-145, one or more predefined time period indications 4-146, and/or one or more applications 4-140), a network interface 4-118 (e.g., network interface card or NIC), and/or a user interface 4-120. In various embodiments, the computing device 4-10 may further include a social networking entry reception module 4-110 (which may further include a blog entry reception module 4-111 and/or a status report reception module 4-112), a journal entry reception module 4-114, and/or a sensor data reception module 4-115. In various implementations, the computing device 4-10 may include a request reception module 4-122 designed to receive one or more requests 4-12 via, for example, a wireless network and/or wired network 4-50. For these implementations, the one or more requests 4-12 to be received may be for one or more personalized plans 4-16.

The relevant reported aspect identification module 4-102 may be configured to, among other things, identify one or more relevant reported aspects based, at least in part, on the one or more relevant reported aspects' relevancy with respect to one or more target outcomes, the one or more relevant reported aspects to be identified being associated with one or more source users 4-2* and being relevant to achieving the one or more target outcomes. The personalized plan development module 4-104 may be configured to, among other things, develop one or more personalized plans 4-16 based, at least in part, on the one or more relevant reported aspects, the one or more personalized plans 4-16 to be developed being designed to facilitate an end user 4-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 4-16 are emulated. The presentation module 4-106 may be designed to present (e.g., transmit via the wireless network and/or wired network 4-50 to the local end user device 4-30, to one or more local source user devices 4-20, to one or more network servers 4-60, and/or to one or more third parties 4-6) the one or more personalized plans 4-16 that are developed. A more detailed discussion relating to the relevant reported aspect identification module 4-102, the personalized plan development module 4-104, the presentation module 4-106, and their sub-modules, will be provided below with respect to the various operational flows to be described herein.

The memory 4-116 may be designed to store various data including a plurality of reported aspects 4-14 that may include one or more reported aspects associated with one or more source users 4-2* and that may or may not be relevant to achieving the one or more target outcomes (e.g., the plurality of reported aspects 4-14 may include both reported aspects that are relevant to achieving one or more target outcomes and reported aspects that may not be relevant to achieving the one or more target outcomes). Other types of data may be stored in the memory 4-116 including, for example, one or more end user relevancy indications 4-142 (e.g., one or more indications that indicate the types of reported or emulatable aspects that an end user 4-4 has an interest in or believes is relevant to achieving one or more target outcomes), one or more end user limitations 4-143 (e.g., limitations such as contextual limitations, physical limitations, personal limitations, and so forth, associated with the end user 4-4 that prevent one or more emulatable aspects from being emulated), and/or one or more source user relevancy indications 4-144 (e.g., one or more indications provided by a source user 4-2* that indicate at least which types of reported aspects are relevant to achieving one or more target outcomes).

In some cases, the memory 4-116 may also include, for example, one or more third party source relevancy indications 4-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 4-6 that indicate at least which types of reported aspects are relevant to achieving one or more target outcomes), one or more predefined time period indications 4-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 is relevant for achieving at least one target outcome only if the reported aspect indicate 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 4-2*), and/or one or more applications 4-140 (e.g., a text messaging application, an instant messaging application, an email 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). In various implementations, the memory 4-116 comprises 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 social networking entry reception module 4-110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 4-2*, an end user 4-4, one or more third parties 4-6, and/or one or more network servers 4-60. The social networking entry reception module 4-110 may further include a blog entry reception module 4-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 4-112 for receiving social networking status reports. The journal entry reception module 4-114 may be configured to receive journal entries from, for example, the one or more source users 4-2, the end user 4-4, and/or from the one or more third parties 4-6 (e.g., a non-user). The sensor data reception module 4-115 may be configured to receive sensing data from one or more sensing devices 4-40. The user interface 4-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. 4-2 a illustrates particular implementations of the relevant reported aspect identification module 4-102 of the computing device 4-10 of FIG. 4-1b. As illustrated, the relevant reported aspect identification module 4-102 may include, in various implementations, one or more sub-modules. For example, in some implementations, the relevant reported aspect identification module 4-102 may include a source user associated reported aspect identification module 4-202 that is configured to, among other things, identify from a plurality of reported aspects 4-14 one or more reported aspects 4-14 that are associated with one or more source users 4-2*, the one or more source users 4-2* having achieved one or more target outcomes. The identification of one or more relevant reported aspects that are relevant to achieving the one or more target outcomes by the relevant reported aspect identification module 4-102 may be facilitated by at least identifying those reported aspects 4-14 that are associated with source users 4-2* who have been determined to have achieved the one or more target outcomes.

In order to facilitate the source user associated reported aspect identification module 4-202 identify the one or more reported aspects 4-14 that are associated with the one or more source users 4-2* who have achieved the one or more target outcomes, the source user associated reported aspect identification module 4-202 may further include a target outcome corresponding reported aspect identification module 4-204 and/or an associated source user determination module 4-206. The target outcome corresponding reported aspect identification module 4-204 may be configured to identify from the plurality of reported aspects 4-14 one or more reported aspects 4-14 that corresponds to the one or more target outcomes. In contrast, the associated source user determination module 4-206 may be configured to determine one or more source users 4-2* who are associated with the one or more reported aspects 4-14 that correspond to the one or more target outcomes (e.g., determine the one or more source users 4-2* who have achieved the one or more target outcomes).

In various implementations, the relevant reported aspect identification module 4-102 may further include a relevancy factor relevant reported aspect identification module 4-208 that is configured to at least identify one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors. Various types of relevancy factors may be considered as previously described including, for example, whether the one or more reported aspects 4-14 belong to the types of aspects that is of interest to the end user 4-4* or are considered as relevant to achieving the one or more target outcomes by a source user 4-2* or by a third party source.

FIG. 4-2 b illustrates particular implementations of the personalized plan development module 4-104 of FIG. 4-1b. As previously indicated, the personalized plan development module 4-104 may be configured to develop one or more personalized plans 4-16 that are designed to facilitate an end user 4-4 to achieve one or more target outcomes when one or more emulated aspects included in the one or more personalized plans 4-16 are emulated, the development of the one or more personalized plans 4-16 being based on one or more relevant reported aspects that are identified by the relevant reported aspect identification module 4-102.

In various implementations, the personalized plan development module 4-104 may include one or more of an emulatable aspect inclusion module 4-220, a relationship defining module 4-222, an emulatable intermediate outcome inclusion module 4-223, a limitation compliance determination module 4-224 (which may include an action module 4-225 that may further include a non-compliance notification module 4-226 and/or a personalized plan modification module 4-228), and/or a plausible determination module 4-230 (which may include an action module 4-232 that may further include a not plausible notification module 4-234 and/or personalized plan modification module 4-236).

The emulatable aspect inclusion module 4-220 may be configured to include into each of the one or more personalized plans 4-16 to be developed one or more emulatable aspects that correspond to the one or more relevant reported aspects identified by the relevant reported aspect identification module 4-102. The relationship defining module 4-222 may be configured to define in each of the one or more personalized plans 4-16 to be developed one or more relationships (e.g., spatial, temporal, and/or specific time relationships) between a plurality of emulatable aspects that may be included in each of the one or more personalized plans 4-16. The emulatable intermediate outcome inclusion module 4-223 may be configured to include into at least one of the one or more personalized plans 4-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 4-16.

The limitation compliance determination module 4-224 may be configured to determine whether the one or more emulatable aspects to be included in the one or more personalized plans 4-16 complies with one or more limitations associated with the end user 4-4, and if not compliant, execute one or more actions (e.g., as executed by the action module 4-225). Various types of actions may be executed by the action module 4-225 if a determination is made of non-compliance. For example, in some implementations, the action module 4-225 may include a non-compliance notification module 4-226 that is configured to notify (e.g., notifying by transmitting a notification or by indicating via a user interface 4-120) at least one of the end user 4-4 and a third party 4-6 regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user 4-4. Other types of actions by the action module 4-225 may also be executed in various implementations. For example, in some implementations, the action module 4-225 may include a personalized plan modification module 4-228 that is configured to modify the one or more personalized plans 4-16 including replacing one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 4-4 with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user 4-4.

The plausible determination module 4-230, in contrast to the limitation compliance determination module 4-224, may be configured to determine whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is a plausible aspect that has been successfully emulated by one or more third parties 4-6 (e.g., other end users 4-4), and if not plausible, execute one or more actions (e.g., as executed by the action module 4-232). Various types of actions may be executed by the action module 4-232 if a determination is made of non-compliance.

For example, in some implementations, the action module 4-232 may include a not plausible notification module 4-234 that is configured to notify, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is not a plausible aspect, at least one of the end user 4-4 and a third party 4-6 regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is not a plausible aspect. Note that in some implementations, a “plausible aspect” may be an aspect that has been successfully emulated by one or more third parties 4-6 in order to, for example, achieve the one or more target outcomes.

Other types of actions may also be executed by the action module 4-232 when one or more emulatable aspects that may be included in the one or more personalized plans 4-16 have been determined to be not plausible. For example, in some implementations, the action module 4-232 may include a personalized plan modification module 4-236 that is configured to modify, in response to a determination that at least one of the one or more emulatable aspects included in the one or more personalized plans 4-16 is not a plausible aspect, at least one of the one or more personalized plans 4-16 by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 4-6.

Referring now to FIG. 4-2c illustrating one of the sensing devices 4-40 of FIGS. 4-1a and 4-1b. The sensing device 4-40, in various embodiments, may include at least one or more sensors 4-240. The one or more sensors 4-240 that may be included in a sensing device 4-40 may be designed to sense or detect one or more aspects associated with a source user 4-2*. For example, in various implementations, the one or more sensors 4-240 may include one or more devices that can monitor a user's physiological characteristics such as blood pressure sensors, heart rate monitors, glucometers (e.g., glucose meters), and so forth.

In some implementations, the one or more sensors 4-240 may include devices that can detect activities of a user (e.g., a source user 4-2*). Examples of such devices include, for example, 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 4-240 may include, in various implementations, 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 4-2*, global positioning system (GPS) to provide location data related to a user (e.g., locations of the source user 4-2*), and so forth. In various implementations, a sensing device 4-40 may further include a network interface 4-242 and/or a memory 4-244 to store, for example, sensing data provided by the one or more sensors 4-240.

Referring back to the computing device 4-10 of FIG. 4-1b, the various modules (e.g., the relevant reported aspect identification module 4-102, the personalized plan development module 4-104, the presentation module 4-106, and so forth) along with their sub-modules included in the computing device 4-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the relevant reported aspect identification module 4-102, the personalized plan development module 4-104, and/or the presentations module 4-106 may be implemented with a processor 4-802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 4-804 (e.g., computer program product) stored in a storage medium 4-806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 4-800 of FIG. 4-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 discussion related to the computing device 4-10 of FIG. 4-1b will now be provided with respect to the processes and operations to be described herein. FIG. 4-3 illustrates an operational flow 4-300 representing example operations related to, among other things, identification of one or more relevant reported aspects associated with one or more source users 4-2* that are relevant to achieving one or more target outcomes, the identification being based on the relevancy of the one or more relevant reported aspects with respect to the one or more target outcomes, and the development of one or more personalized plans 4-16 based on the one or more relevant reported aspects that are identified.

In FIG. 4-3 and in the following figures that include various examples of operational flows, discussions and explanations may be provided with respect to the exemplary environments described above as illustrated in FIGS. 4-1a and 4-1b, and/or with respect to other examples (e.g., as provided in FIGS. 4-2a, 4-2b, and 4-2c) 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. 4-1a, 4-1b, 4-2a, 4-2b, and 4-2c. 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. 4-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 4-300 may move to a relevant reported aspect identifying operation 4-302 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. For instance, and as an illustration, the relevant reported aspect identification module 4-102 of the computing device 4-10 of FIG. 4-1b identifying (e.g., determining, ascertaining, finding, locating, and so forth) one or more relevant reported aspects associated with one or more source users 4-2 and 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.

Note that in various implementations, the identification of the one or more relevant reported aspects may not depend on the identification (e.g., by an end user 4-4 or by a third party 4-6), at least initially, of the one or more source users 4-2* who have achieved the one or more target outcomes. Rather, such identification operation may depend, at least initially, only on the relevancy of the one or more relevant reported aspects with respect to the one or more target outcomes in order to identify the one or more relevant reported aspects.

In addition to the relevant reported aspect identifying operation 4-302, operational flow 4-300 may also include a personalized plan developing operation 4-304 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. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing (e.g., creating) one or more personalized plans 4-16 designed to facilitate an end user 4-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 4-16 are emulated, the development of the one or more personalized plans 4-16 being based, at least in part, on the identifying of the one or more relevant reported aspects. As will be described herein, the relevant reported aspect identifying operation 4-302 as well as the personalized plan developing operation 4-304 may be implemented in a number of different ways in various alternative implementations.

For example the relevant reported aspect identifying operation 4-302 of FIG. 4-3 in various implementations may be executed in various alternative ways as will be illustrated in FIGS. 4-4a, 4-4b, 4-4c, 4-4d, 4-4e, 4-4f, 4-4g, and 4-4h. In some implementations, for example, the relevant reported aspect identifying operation 4-302 may include an operation 4-402 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that are at least relevant for achieving the one or more target outcomes from a plurality of reported aspects as depicted in FIG. 4-4a. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 of FIG. 4-1b identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 (e.g., aspects of the one or more source users 4-2* that have been reported and that may indicate, for example, the behaviors or acts of the one or more source users 4-2*) that are at least relevant for achieving the one or more target outcomes from a plurality of reported aspects 4-14.

In some implementations, operation 4-402 may further include an operation 4-403 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that are relevant for achieving the one or more target outcomes from a plurality of reported aspects stored in memory as depicted in FIG. 4-4a. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that are relevant for achieving the target outcomes from a plurality of reported aspects 4-14 stored in memory 4-116 (e.g., volatile memory, non-volatile memory, cache memory, and so forth).

In the same or different implementations, operation 4-402 may include an operation 4-404 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that are relevant for 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 further depicted in FIG. 4-4a. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that are relevant for achieving the one or more target outcomes from a plurality of reported aspects 4-14 that includes at least a first one or more reported aspects 4-14 that are relevant to achieving the one or more target outcomes and a second one or more reported aspects 4-14 that are not relevant to achieving the one or more target outcomes.

Various techniques may be employed in order to identify reported aspects 4-14 that may be relevant for achieving a particular target outcome or outcomes. In some cases, this may involve at least identifying reported aspects 4-14 that are associated with one or more source users 4-2* who have been determined to have achieved the target outcome or outcomes. For example, in some implementations, operation 4-402 may include an operation 4-405 for identifying from the plurality of reported aspects one or more reported aspects that are associated with the one or more source users, the one or more source users having achieved the one or more target outcomes as depicted in FIG. 4-4b. For instance, the source user associated reported aspect identification module 4-202 (see FIG. 4-2a) of the computing device 4-10 identifying from the plurality of reported aspects 4-14 one or more reported aspects that are associated with the one or more source users 4-2*, the one or more source users 4-2* having achieved the one or more target outcomes.

In order to determine whether the one or more source users 4-2* have achieved the one or more target outcomes, operation 4-405 may further include one or more additional operations. For example, in some implementations, operation 4-405 may include an operation 4-406 for identifying from the plurality of reported aspects the one or more reported aspects that are associated with the one or more source users by at least identifying from the plurality of reported aspects one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4b. For instance, the target outcome corresponding reported aspect identification module 4-204 (see FIG. 4-2a) of the computing device 4-10 identifying from the plurality of reported aspects 4-14 the one or more reported aspects 4-14 that are associated with the one or more source users 4-2* by at least identifying from the plurality of reported aspects 4-14 one or more reported aspects 4-14 that corresponds (e.g., equivalent or substantially equivalent) to the one or more target outcomes.

Operation 4-406, in turn, may further include an operation 4-407 for determining one or more source users who are associated with the one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4b. For instance, the associated source user determination module 4-206 (see FIG. 4-2a) of the computing device 4-10 determining one or more source users 4-2*(e.g., Matthew and Leslie) who are associated with the one or more reported aspects 4-14 (e.g., Matthew and Leslie getting a 92 percent and 95 percent test scores, respectively, on a particular calculus test) that correspond to the one or more target outcomes (e.g., achieving at least a 90 percent test score on the calculus test).

For these implementations, once the one or more source users 4-2* who have achieved the one or more target outcomes have been identified, reported aspects that are associated with the source users 4-2** may be identified. For example, in some implementations, operation 4-407 may further include an operation 4-408 for identifying, from the plurality of reported aspects, one or more reported aspects that are associated with the one or more source users who have been determined to be associated with the one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4b. For instance, the source user associated reported aspect identification module 4-202 of the computing device 4-10 identifying, from the plurality of reported aspects 4-14, one or more reported aspects 4-14 that are associated with the one or more source users 4-2* who have been determined to be associated with the one or more reported aspects 4-14 that correspond to the one or more target outcomes. In other words, the source user associated reported aspect identification module 4-202 identifying one or more reported aspects 4-14 that are associated with source users 4-2* who have been determined to have achieved the one or more target outcomes.

Note that not all reported aspects 4-14 that are associated with the source users 4-2* who have been determined to have achieved the one or more target outcomes may actually be relevant to achieving the one or more target outcomes. Thus, operation 4-408 may further include one or more additional operations in order to identify reported aspects 4-14 that are relevant to achieving the one or more target outcomes. For example, in some implementations, operation 4-408 may further include an operation 4-409 for identifying, from the one or more reported aspects that are associated with the one or more source users who have been determined to be associated with the one or more reported aspects that correspond to the one or more target outcomes, one or more reported aspects that are relevant with respect to one or more relevancy factors as depicted in FIG. 4-4b. For instance, the relevancy factor relevant reported aspect identification module 4-208 (see FIG. 4-2a) of the computing device 4-10 identifying, from the one or more reported aspects 4-14 that are associated with the one or more source users 4-2* who have been determined to be associated with the one or more reported aspects that correspond to the one or more target outcomes, one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors.

Various types of relevancy factors may be considered when determining whether a reported aspect is relevant to the achievement of a particular target outcome or outcomes. For example, in some implementations, operation 4-409 may include an operation 4-410 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that belong to one or more aspect types that are of interest to the end user as depicted in FIG. 4-4b. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 4-14 that belong to one or more aspect types (e.g., sleep or rest activities) that are of interest to the end user 4-4.

In the same or different implementations, operation 4-409 may include an operation 4-411 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 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-4b. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that belong to one or more aspect types (e.g., reading activities) that have been indicated by at least one source user 4-2* as being relevant to the achievement of the one or more target outcomes (e.g., improve verbal test score on the scholastic amplitude test).

In the same or different implementations, operation 4-409 may include an operation 4-412 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 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-4b. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 4-14 that belong to one or more aspect types (e.g., exercise activities or dietary activities) that have been indicated by at least one third party source (e.g., published medical research) as being relevant to the achievement of the one or more target outcomes (e.g., mental well-being).

In the same or different implementations, operation 4-409 may include an operation 4-413 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that indicate 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 aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4c. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 4-14 that indicate 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 aspects 4-14 that correspond to the one or more target outcomes.

That is, not all reported aspects 4-14 that are associated with the one or more source users 4-2* who have achieved the one or more target outcomes and that are relevant with respect to at least certain relevancy factors may actually be relevant to achieving the one or more target outcomes if the reported aspects 4-14 indicate aspects that, time-wise, occurred remotely from occurrence of the one or more target outcomes as successfully achieved by the one or more source users 4-2*. For example, reported aspects 4-14 that are associated with the one or more source users 4-2* who have achieved the one or more target outcomes and that are relevant based on certain relevancy factors (e.g., belonging to a type of aspect that is of interest to the end user 4-4) may, nevertheless, not be relevant to achieving the one or more target outcomes if they occurred well before (or well after) the achievement of the one or more target outcomes (e.g., as represented by one or more reported aspects that correspond to the one or more target outcomes) by the one or more source users 4-2*. Thus, a reported aspect 4-14 may, in some cases, be relevant to the achievement of the one or more target outcomes only if it falls within some time period (e.g., “predefined time period”) from the one or more occurrences of the one or more reported aspects that correspond to the one or more target outcomes. The length of the predefined time periods to be considered in determining relevancy may depend 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 may be associated with a different predefined time period) may be set based on the type of personalized plans 4-16 being developed. Alternatively, the one or more predefined time periods may be set by the end user 4-4, by one or more source users 4-2*, or by one or more third parties 4-6. As an illustration, suppose an end user 4-4 is interested in finding out what type of reading activities could help improve his verbal score on the SAT in six months. The end user 4-4 may then indicate that he is only interested in reported aspects 4-14 that indicate reading activities that have occurred during the six months prior to the taking of an SAT exam.

In some implementations, operation 4-413 may further include an operation 4-414 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that indicate 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 aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4c. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 4-14 that indicate one or more aspects (e.g., exercise activities) that occurred prior to and within one or more predefined time periods (e.g., one month), respectively, from one or more occurrences of the one or more reported aspects 4-14 that correspond to the one or more target outcomes (e.g., 20 pound body weight loss). That is, generally in most (but not all) cases, reported aspects 4-14 that indicate aspects that are deemed to be relevant to achieving a particular target outcome will typically occur prior to the target outcome being achieved.

In some implementations, the relevant reported aspect identifying operation 4-302 may not include a determination for the one or more source users 4-2* who may have achieved the one or more target outcomes. For these implementations, the relevant reported aspect identifying operation 4-302 may, nevertheless, include an operation 4-415 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that are relevant with respect to one or more relevancy factors as depicted in FIG. 4-4d. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that are relevant with respect to one or more relevancy factors.

Operation 4-415 may in turn include one or more additional operations in various alternative implementations. For example, in some implementations, operation 4-415 may include an operation 4-416 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that belong to one or more aspect types that are of interest to the end user as depicted in FIG. 4-4d. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that belong to one or more aspect types (e.g., conduct at workplace) that are of interest to the end user 4-4.

In the same or different implementations, operation 4-415 may include an operation 4-417 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 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-4d. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that belong to one or more aspect types (e.g., caffeine consumption) that have been indicated by at least one source user 4-2* as being relevant to the achievement of the one or more target outcomes (e.g., having a relaxed temperament).

In the same or different implementations, operation 4-415 may include an operation 4-418 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 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-4d. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that belong to one or more aspect types (e.g., social activities) that have been indicated by at least one third party source (e.g., a third party 4-6, a publication, a content provider, and so forth) as being relevant to the achievement of the one or more target outcomes (e.g., having many friends).

In the same or different implementations, operation 4-415 may include an operation 4-419 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that indicate 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 aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4d. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that indicate one or more aspects (e.g., caffeine consumption) that occurred within one or more predefined time periods (e.g., 24 hours), respectively, from one or more occurrences of the one or more reported aspects 4-14 that correspond to the one or more target outcomes (e.g., being alert at work).

In some implementations, operation 4-419 may further include an operation 4-420 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that indicate 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 aspects that correspond to the one or more target outcomes as depicted in FIG. 4-4d. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects by at least identifying one or more reported aspects 4-14 that indicate 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 aspects 4-14 that correspond to the one or more target outcomes.

The one or more relevant reported aspects to be identified via the relevant reported aspect identifying operation 4-302 of FIG. 4-3 may have been originally reported in a number of different ways. For example, in some implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-421 for identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more log entries as depicted in FIG. 4-4e. For instance, the relevancy factor relevant reported aspect identification module 4-208 of the computing device 4-10 identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more log entries. A log entry, as described here, may be any type of, for example, electronic entry that may be regularly, semi-regularly, or randomly entered by, for example, a source user 4-2*, a sensing device 4-40, or by a third party 4-6. A log entry, as will be further described herein, may come in a variety of different forms.

For example, in some implementations, operation 4-421 may include an operation 4-422 for identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more blog entries as depicted by FIG. 4-4e. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more blog entries (e.g., microblog entries).

In the same or different implementations, operation 4-421 may include an operation 4-423 for identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more status reports as depicted in FIG. 4-4e. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more status reports (e.g., social networking status reports).

In the same or different implementations, operation 4-421 may include an operation 4-424 for identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more journal entries as depicted in FIG. 4-4e. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via one or more journal entries.

In the same or different implementations, operation 4-421 may include an operation 4-425 for identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via log entries as provided by one or more sensing devices as depicted in FIG. 4-4e. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including one or more relevant reported aspects that were at least originally reported via log entries as provided by one or more sensing devices 4-40 (e.g., sensing devices that can detect or sense source user activities or physiological characteristics of one or more source users 4-2*).

In some implementations, the relevant reported aspect identifying operation 4-302 of FIG. 4-3 may include an operation 4-426 for identifying the one or more relevant reported aspects including one or more relevant reported aspects that are reported intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 4-4e. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including one or more relevant reported aspects that are reported intermediate outcomes (e.g., losing 10 pounds of body weight) associated with the one or more target outcomes (e.g., losing 20 pounds of body weight).

In order to execute such an operation, operation 4-426 for identifying the one or more relevant reported aspects that are reported intermediate outcomes may include one or more additional operations such as initially identifying the one or more source users 4-2* who have achieved the one or more target outcomes, and identifying reported aspects 4-14 associated with the one or more source users 4-2* who have achieved the one or more target outcomes and that may be intermediate reported outcomes associated with the one or more target outcomes. Note that when developing the one or more personalized plans 4-16, one or more emulatable intermediate outcomes that correspond to the reported intermediate outcomes may be included into the one or more personalized plans 4-16. In doing so, the end user 4-4 may be better facilitated in tracking his/her progress towards achieving, for example, the desired target outcomes.

In some cases, the relevant reported aspect identifying operation 4-302 of FIG. 4-3 may involve identifying relevant reported aspects that are associated with multiple source users 4-2*. For example, in some implementations, the relevant reported aspect identifying operation 4-302 of FIG. 4-3 may include an operation 4-427 for identifying the one or more relevant reported aspects including identifying a first one or more reported aspects that are associated with a first source user and that are relevant to achieving a first one or more target outcomes and identifying a second one or more reported aspects that are associated with a second source user and that are relevant to achieving a second one or more target outcomes, the identifying of the first one or more reported aspects being based on the first one or more reported aspects' relevancy with respect to the first one or more target outcomes and the identifying of the second one or more reported aspects being based on the second one or more reported aspects' relevancy with respect to the second one or more target outcomes as depicted in FIG. 4-4f. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying a first one or more reported aspects 4-14 that are associated with a first source user 4-2a and that are relevant to achieving a first one or more target outcomes and identifying a second one or more reported aspects 4-14 that are associated with a second source user 4-2b and that are relevant to achieving a second one or more target outcomes, the identifying of the first one or more reported aspects 4-14 being based on the first one or more reported aspects' relevancy with respect to the first one or more target outcomes and the identifying of the second one or more reported aspects 4-14 being based on the second one or more reported aspects' relevancy with respect to the second one or more target outcomes.

In the same or different implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-428 for identifying the one or more relevant reported aspects including identifying a first one or more reported aspects that are associated with a first source user and that are relevant to achieving at least one target outcome and identifying 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 target outcome, the identifying 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 target outcome as depicted in FIG. 4-4f. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying a first one or more reported aspects 4-14 that are associated with a first source user 4-2a and that are relevant to achieving at least one target outcome and identifying a second one or more reported aspects 4-14 that are associated with a second source user 4-2b and that are relevant to achieving the at least one target outcome, the identifying of the first one or more reported aspects 4-14 and the second one or more reported aspects 4-14 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 target outcome.

Various types of aspects may be indicated by the one or more relevant reported aspects identified by the relevant reported aspect identifying operation 4-302 of FIG. 4-3 in various alternative implementations. For example, in some implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-429 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more behavior incidences associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more behavior incidences associated with the one or more source users 4-2*.

Various types of behavior incidences may be indicated by the one or more relevant reported aspects identified by operation 4-429. For example, in some implementations, operation 4-429 may include an operation 4-430 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more activities executed by the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more activities (e.g., food or medicine ingestion activities, rest activities, occupational activities, exercise activities, social activities, and so forth) executed by the one or more source users 4-2*.

In the same or different implementations, operation 4-429 may include an operation 4-431 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user attitudes associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user attitudes (e.g., being indifferent, feeling critical, feeling skeptical, feeling optimistic, and so forth) associated with the one or more source users 4-2*.

In the same or different implementations, operation 4-429 may include an operation 4-432 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user conduct associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user conduct (e.g., behavior towards others, treatment of others, manner in which acts are executed, and so forth) associated with the one or more source users 4-2*.

Other types of relevant reported aspects other than those that indicate behavior incidences may be identified through the relevant reported aspect identifying operation 4-302 of FIG. 4-3 in various alternative implementations. For example, in some implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-433 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user beliefs associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user beliefs (e.g., religious beliefs, spiritual beliefs, prejudicial beliefs, political beliefs, and so forth) associated with the one or more source users 4-2*.

In the same or different implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-434 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more subjective user states associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more subjective user states associated with the one or more source users 4-2*.

A subjective user state may be any state or status associated with a source user 4-2* that can typically only be indicated by the source user 4-2*. Examples of subjective user states include, for example, subjective user mental states (e.g., sadness, happiness, mental exhaustion, alertness, and so forth), subjective user physical states (e.g., sore back, blurred vision, overall physical exhaustion, and so forth), and subjective user overall states (e.g., any other subjective user states that are neither a subjective user mental state or a subjective user physical state including, for example, “feeling good,” “feeling bad,” “feeling alive,” and so forth).

In the same or different implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-435 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of one or more user physical characteristics (e.g., hair or eye color, hair length, hair style, facial hair characteristics, overall body figure, body weight, and so forth) associated with the one or more source users 4-2*.

In the same or different implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-436 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of user locations associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of user locations (e.g., nightclub, football stadium, home residence, workplace, and so forth) associated with the one or more source users 4-2*.

In the same or different implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-437 for identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of external events associated with the one or more source users as depicted in FIG. 4-4g. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects including identifying one or more relevant reported aspects that are related to one or more incidences of external events (e.g., weather conditions, heavy or no road traffic, performance of one or more investment stocks that are of interest to the one or more source users 4-2*, and so forth) associated with the one or more source users 4-2*.

In various implementations, the relevant reported aspect identifying operation 4-302 (as well as the operational flow 4-300) of FIG. 4-3 may be prompted when, for example, a request 4-12 is received. For example, in some implementations, the relevant reported aspect identifying operation 4-302 may include an operation 4-438 for identifying the one or more relevant reported aspects in response to receiving a request as depicted in FIG. 4-4h. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects in response to receiving a request 4-12 (e.g., a request 4-12 for the one or more personalized plans 4-16 as made by the end user 4-4 or by a third party 4-6). In the case where the computing device 4-10 is an end user device (e.g., local end user device 4-30) or a source user device (e.g., local source user device 4-20), the request 4-12 may be received through a user interface 4-120 or through a network interface 4-118. In the case where the computing device 4-10 is a server (e.g., network server 4-60), the request 4-12 may be received through the network interface 4-118.

In some implementations, operation 4-438 may further include an operation 4-439 for identifying the one or more relevant reported aspects in response to receiving the request, the request identifying at least one of the one or more target outcomes as depicted in FIG. 4-4h. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects in response to receiving the request 4-12, the request 4-12 identifying at least one of the one or more target outcomes.

In some cases, operation 4-439 may further include an operation 4-440 for identifying the one or more relevant reported aspects in response to receiving the request, the request not identifying any of the one or more source users as depicted in FIG. 4-4h. For instance, the relevant reported aspect identification module 4-102 of the computing device 4-10 identifying the one or more relevant reported aspects in response to receiving the request 4-12, the request 4-12 not identifying any of the one or more source users 4-2*. For example, if the requester (e.g., end user 4-4) is unaware of which user (e.g., source user 4-2*) may have achieved the one or more target outcomes, than the request 4-12 may not identify the one or more source users 4-2*.

Referring back to the personalized plan developing operation 4-304 of FIG. 4-3, the personalized plan developing operation 4-304 may include one or more additional operations in various implementations. For example, in some implementations, the personalized plan developing operation 4-304 may include an operation 4-541 for including into each of the one or more personalized plans one or more emulatable aspects that correspond to the one or more relevant reported aspects as depicted in FIG. 4-5a. For instance, the emulatable aspect inclusion module 4-220 (see FIG. 4-2b) of the computing device 4-10 including into each of the one or more personalized plans 4-16 one or more emulatable aspects that correspond to the one or more relevant reported aspects (e.g., as identified through the relevant reported aspect identifying operation 4-302).

In some cases, operation 4-541 may further include an operation 4-542 for including into each of the one or more personalized plans a plurality of emulatable aspects that corresponds to a plurality of relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes as depicted in FIG. 4-5a. For instance, the emulatable aspect inclusion module 4-220 of the computing device 4-10 including into each of the one or more personalized plans 4-16 a plurality of emulatable aspects that corresponds to a plurality of relevant reported aspects that are associated with the one or more source users 4-2* and that are relevant to achieving the one or more target outcomes.

In turn, operation 4-542 may include, in various implementations, an operation 4-543 for defining in each of the one or more personalized plans one or more relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 4-5a. For instance, the relationship defining module 4-222 (see FIG. 4-2b) of the computing device 4-10 defining in each of the one or more personalized plans 4-16 one or more relationships (e.g., temporal relationships, specific time relationships, and/or spatial relationships) between the plurality of emulatable aspects included in each of the one or more personalized plans 4-16.

In various implementations, the operation 4-541 for including into each of the one or more personalized plans one or more emulatable aspects that correspond to the one or more relevant reported aspects may include an operation 4-544 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with one or more limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 4-5a. For instance, the limitation compliance determination module 4-224 (see FIG. 4-2b) of the computing device 4-10 determining whether the one or more emulatable aspects to be included in the one or more personalized plans 4-16 complies with (e.g., does not violate) one or more limitations associated with the end user 4-4 (e.g., limitations that prevent or make it impractical for the one or more emulatable aspects to be successfully emulated), and if not compliant, execute one or more actions.

In various implementations, operation 4-544 may further include one or more additional operations. For example, in some implementations, operation 4-544 may include an operation 4-545 for notifying at least one of the end user and a third party regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user as depicted in FIG. 4-5a. For instance, the non-compliance notification module 4-226 (see FIG. 4-2b) of the computing device 4-10 notifying at least one of the end user 4-4 and a third party 4-6 regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user 4-4.

In the same or different implementations, operation 4-544 may include an operation 4-546 for modifying the one or more personalized plans including revising one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user or replacing the one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user as depicted in FIG. 4-5a. For instance, the personalized plan modification module 4-228 (see FIG. 4-2b) of the computing device 4-10 modifying the one or more personalized plans 4-16 including revising one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 4-4 or replacing the one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 4-4 with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user 4-4. As a further illustration, if an emulatable aspect such as “swimming for 40 minutes” is determined to be non-compliant, than replacing the non-compliant emulatable aspect with a complaint emulatable aspect (e.g., “jogging for one hour” that results in the same amount of calories being burned) that is at least proximately equivalent to the non-compliant emulatable aspect. Of course, what is “at least proximately equivalent” will depend on the type of emulatable aspect being replaced and the type of personalized plan 4-16 being developed.

In the same or different implementations, operation 4-544 may include an operation 4-547 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans complies with at least one of a contextual, physical, personal, health, medical, user state, or legal limitations associated with the end user as depicted in FIG. 4-5a. For instance, the limitation compliance determination module 4-224 of the computing device 4-10 determining whether the one or more emulatable aspects to be included in the one or more personalized plans 4-16 complies with at least one of a contextual (e.g., logistical limitations such as scheduling limitations, geographical limitations, asset limitations, and so forth), physical (e.g., missing limb, paralysis, visual or hearing impediment, and so forth), personal (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), health or medical (e.g., medical limitations such as limitations resulting from an illness or treatment of an illness including limitations due to cancer or treatment of the cancer, health limitations related to the physical conditioning of the end user 4-4, genetic limitations, and so forth), user state (e.g., end user 4-4 is married, end user 4-4 is in mourning, end user 4-4 is unemployed, end user 4-4 is a vegan, and so forth), or legal limitations (e.g., drug regulations, laws related to conduct or behavior in the jurisdiction of the end user 4-4, and so forth) associated with the end user 4-4, and if not, execute one or more actions.

In various implementations, the operation 4-541 for including one or more emulatable aspects into each of the one or more personalized plans may include an operation 4-548 for determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans is a plausible aspect that has been successfully emulated by one or more third parties, and if not, execute one or more actions as depicted in FIG. 4-5b. For instance, the plausible determination module 4-230 (see FIG. 4-2b) of the computing device 4-10 determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is a plausible aspect that has been successfully emulated by one or more third parties 4-6 (e.g., other end users 4-4* or disinterested parties), and if not plausible, execute one or more actions.

In various alternative implementations, operation 4-548 may include one or more additional operations. For example, in some implementations, operation 4-548 may include an operation 4-549 for notifying, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans is not a plausible aspect, at least one of the end user and a third party regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans is not a plausible aspect as depicted in FIG. 4-5b. For instance, the not plausible notification module 4-234 (see FIG. 4-2b) of computing device 4-10 notifying, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is not a plausible aspect, at least one of the end user 4-4 and a third party 4-6 regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is not a plausible aspect.

In the same or different implementations, operation 4-548 may include an operation 4-550 for modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more personalized plans by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by the one or more third parties as depicted in FIG. 4-5b. For instance, the personalized plan modification module 4-236 (see FIG. 4-2b) of the computing device 4-10 modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more personalized plans 4-16 by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 4-6 (e.g., other end users 4-4* or disinterested parties).

In the same or different implementations, operation 4-548 may include an operation 4-551 for determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans is a plausible aspect that has been successfully emulated by the one or more third parties in order to achieve at least one of the one or more target outcomes, and if not, execute the one or more actions as depicted in FIG. 4-5b. For instance, the plausible determination module 4-230 of the computing device 4-10 determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 4-16 is a plausible aspect that has been successfully emulated by one or more third parties 4-6 in order to achieve at least one of the one or more target outcomes, and if not plausible, execute one or more actions.

Various types of personalized plans 4-16 may be developed through the personalized plan developing operation 4-304 of FIG. 4-3. For example, in some implementations, the personalized plan developing operation 4-304 may include an operation 4-552 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more health or medical outcomes as depicted in FIG. 4-5c. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more health or medical outcomes (e.g., recovery time or recovery success related to an illness, weight loss, improve lifespan, physiological outcomes such as reducing blood pressure or blood glucose levels, increase red blood cell count, improve blood circulation, and so forth).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-553 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more athletic outcomes as depicted in FIG. 4-5c. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve 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 the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-554 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more gaming outcomes as depicted in FIG. 4-5c. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more gaming outcomes (e.g., winning a chest tournament or improve video gaming skills).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-555 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more occupational outcomes as depicted in FIG. 4-5c. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more occupational outcomes (e.g., a job promotion, complete a work project on time, develop new occupational relationships, and so forth).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-556 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more social outcomes as depicted in FIG. 4-5c. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more social outcomes (e.g., attaining a certain social class, having a dinner date with a particular person, developing a particular reputation, develop or expand social networks, and so forth).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-557 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more leisure outcomes as depicted in FIG. 4-5d. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan that is designed to facilitate the end user 4-4 to achieve 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 the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-558 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more sexual intimacy outcomes as depicted in FIG. 4-5d. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more sexual intimacy outcomes (e.g., increased sexual activities, increased sexual performance, and so forth).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-559 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more psychological outcomes as depicted in FIG. 4-5d. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more psychological outcomes (e.g., overcoming a phobia, overcoming certain addictive behavior such as compulsion to be clean, and so forth).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-560 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more intellectual or academic outcomes as depicted in FIG. 4-5d. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more intellectual or academic outcomes (e.g., passing a particular exam or class, obtaining a certain degree or academic award, being accepted into a particular program or school, attaining a particular scholarship, understanding a complex concept, acquiring particular knowledge, and so forth).

In the same or different implementations, the personalized plan developing operation 4-304 may include an operation 4-561 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more user states as depicted in FIG. 4-5d. For instance, the personalized plan development module 4-104 of the computing device 4-10 developing the one or more personalized plans 4-16 including at least one personalized plan 4-16 that is designed to facilitate the end user 4-4 to achieve one or more user states (e.g., subjective user states such as subjective mental, physical, and/or overall states, marital states, occupational states, physical states, availability states, social states, spiritual or faith-based states, academic states, and so forth).

Referring to FIG. 4-6 illustrating another operational flow 4-600 in accordance with various embodiments. Operational flow 4-600 includes certain operations that mirror the operations included in the operational flow 4-300 of FIG. 4-3. These operations include a relevant reported aspect identifying operation 4-602 and a personalized plan developing operation 4-604 that corresponds to and mirror the relevant reported aspect identifying operation 4-302 and the personalized plan developing operation 4-304, respectively, of FIG. 4-3.

In addition, operational flow 4-300 includes a personalized plan presenting operation 4-606 for presenting the one or more personalized plans as depicted in FIG. 4-6. For instance, the presentation module 4-106 of the computing device 4-10 presenting (e.g., transmitting via the wireless network and/or wired network 4-50 or indicating via a user interface 4-120) the one or more personalized plans 4-16.

In various alternative implementations, the personalized plan presenting operation 4-606 may include one or more additional operations. For example, in some implementations, the personalized plan presenting operation 4-606 may include an operation 4-763 for transmitting the one or more personalized plans via at least one of wireless network and a wired network as depicted in FIG. 4-7. For instance, the transmission module 4-224 of the computing device 4-10 transmitting the one or more personalized plans 4-16 via at least one of wireless network and a wired network 4-50.

In the same or different implementations, the personalized plan presenting operation 4-606 may include an operation 4-764 for indicating the one or more personalized plans via a user interface as depicted in FIG. 4-7. For instance, the user interface indication module 4-226 of the computing device 4-10 audibly and/or visually indicating the one or more personalized plans 4-16 via a user interface 4-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 personalized plan presenting operation 4-606 may include an operation 4-765 for presenting the one or more personalized plans to the end user as depicted in FIG. 4-7. For instance, the presentation module 4-106 of the computing device 4-10 presenting the one or more personalized plans 4-16 to the end user 4-4.

In the same or different implementations, the personalized plan presenting operation 4-606 may include an operation 4-766 for presenting the one or more personalized plans to at least one of a third party, a source user, and a network server as depicted in FIG. 4-7. For instance, the presentation module 4-106 of the computing device 4-10 presenting the one or more personalized plans 4-16 to at least one of a third party 4-6, a source user 4-2*, and a network server 4-60.

Turning now to FIG. 4-8, which is a high-level block diagram illustrating another perspective of the computing device 4-10 of FIG. 4-1b. As illustrated, the computing device 4-10 may include a processor 4-802 (e.g., microprocessor, controller, and so forth) coupled to storage medium 4-806 (e.g., volatile or non-volatile memory). The storage medium 4-806 may store computer readable instructions 4-804 (e.g., computer program product). The processor 4-802, in various implementations, may execute the computer readable instructions 4-804 in order to execute one or more operations described above and as illustrated in FIGS. 4-3, 4-4a, 4-4b, 4-4c, 4-4d, 4-4e, 4-4f, 4-4g, 4-4h, 4-5a, 4-5b, 4-5c, 4-5d, 4-6, and 4-7.

For example, the processor 4-802 may execute the computer readable instructions 4-804 in order to identify one or more relevant reported aspects associated with one or more source users 4-2 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/or to develop one or more personalized plans 4-16 designed to facilitate an end user 4-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 4-16 are emulated, the development of the one or more personalized plans 4-16 being based, at least in part, on the identifying of the one or more relevant reported aspects as depicted in the operational flow 4-300 of FIG. 4-3.

VI. Development of Personalized Plans Based on Acquisition of Relevant Reported Aspects

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 journal. One place where such open journals 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 particular act, behavior, characteristic, user state or status, belief, 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 become very popular in recent times 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 journals and to allow users to easily update their personal information. 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 aspects associated with users. 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. Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, sensor data, and so forth) are now available through these 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 sites making it even more difficult to exploit such potentially useful data.

In various embodiments, methods, systems, circuitry, and computer program products are provided for developing 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. More particularly, the methods, systems, circuitry, and computer program products may be designed to acquire (e.g., solicit, request, retrieve, and so forth) one or more relevant reported aspects associated with one or more “source users” that are relevant to achieving the one or more target outcomes, the acquisition being based, at least in part, on the relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes. Based on the acquisition of the one or more relevant reported aspects, the one or more personalized plans may then be developed by including into the one or more personalized plans one or more emulatable aspects that may correspond to the one or more relevant reported aspects that have been acquired. In various embodiments, the one or more relevant reported aspects may be acquired from one or more network sites (e.g., network servers and/or local client devices). The methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, by a network device such as a server (e.g., network servers) or a local client device.

As will be described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, and so forth, associated with a particular person (i.e., a source user). A “reported aspect,” in contrast, may be any aspect associated with the person that has been reported. In some embodiments, a reported aspect may have been originally reported via log entries such as blog or microblog entries, status reports, journal entries, sensing device entries, and so forth. In some cases, a reported aspect may be at least originally reported by the source user that the reported aspect is associated with, by a sensing device that detects the aspect to be reported, or by a third party (e.g., another source user who may be reporting on an aspect of the first source user).

In accordance with various embodiments, in order to acquire one or more relevant reported aspects that may be relevant to achieving one or more target outcomes, certain information may be provided to, for example, one or more network devices (e.g., network servers, client devices, and so forth). For example, in some cases, the one or more target outcomes may at least be initially indicated to the one or more network devices. In some cases, by indicating the one or more target outcomes, source users who have achieved the one or more target outcomes may be ascertained by, for example, looking for reported aspects that corresponds to the one or more target outcomes, and then determining source users who are associated with the reported aspects that corresponds to the one or more target outcomes.

After those source users who have achieved the one or more target outcomes have been ascertained, it becomes much simpler to find those reported aspects that are actually relevant to achieving the one or more target outcomes. That is, reported aspects that are relevant to achieving the one or more target outcomes will generally be associated with source users (i.e., “successful” source users) who have actually achieved the one or more target outcomes. Thus, those reported aspects that are associated with source users who may not have achieved the one or more target outcomes can quickly be eliminated as being relevant reported aspects.

Since both relevant and non-relevant reported aspects may be associated with a successful source user, other information may be provided to the one or more network devices in order to acquire relevant reported aspects. For example, in some embodiments certain “relevancy factors” may be provided to the one or more network devices. Such relevancy factors may be considered when determining whether a particular reported aspect is actually relevant to the achievement of one or more target outcomes. Such relevancy factors may include, for example, whether a reported aspect source user indicates an aspect that occurred proximate to the achievement of the target outcome by a successful source user. That is, those reported aspects that are associated with the successful source user and that indicate aspects that occurred well before or well after the achievement of the target outcome by the successful source user may not have any bearing or relationship (e.g., causal relationship) with respect to the achievement of the target outcome.

For example, suppose an end user is interested in losing at least 20 pounds of body weight in two months (e.g., target outcome). Suppose further that a particular source user such as a microblogger has been determined to have lost 25 pounds of body weight in two months. In determining which reported aspects (e.g., dietary behavior, exercise activities, sleep activities, study activities, and so forth) associated with the source user may be relevant to achieving the target outcome, those reported aspects that indicate aspects (e.g., exercise activities) of the source user that occurred well before (e.g., one year before) the occurrence or achievement of the target outcome (e.g., 25 pound body weight loss in two months) by the source user will likely be considered not relevant.

Other relevancy factors may also be provided and considered in determining whether a reported aspect is relevant to the achievement of the target outcome. For example, determining whether the reported aspect is an aspect type that is of interest to the end user. For instance, suppose the end user in the above example believes that the key to losing weight is to have a good night's sleep. In that case, only reported aspects that relate to, for example, the sleep activities of a successful source user (e.g., a source user who has achieved the target outcome) may be considered as being relevant.

In some cases, a successful source user may also indicate what aspects or types of aspects associated with the source user may have contributed to his achievement of the target outcome. In such cases, only those reported aspects associated with the source user and that belong to the types of aspects that the successful source user considers relevant to achieving the target outcome may be considered as a relevant reported aspect.

In still other cases, the relevancy of a reported aspect may be based on indications provided by one or more third party sources such as other source users (e.g., those who may not have achieved the target outcome), other end users, publications, medical research, and so forth, that may indicate the types of aspects that may be relevant to achieving the target outcome. Thus, by providing indications of one or more target outcomes (as well as, in some cases, indications of relevancy factors) to one or more network devices (e.g., servers or client devices used by source users), one or more relevant reported aspects that may be relevant to achieving one or more target outcomes may be acquired.

Based, at least in part, on the acquisition of the one or more relevant reported aspects, one or more personalized plans may be developed that are designed to facilitate the end user to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans are emulated. In some embodiments, the acquisition of the relevant reported aspects as well as the development of the one or more personalized plans may be prompted when, for example, a request (e.g., a query, a command, a solicitation, and so forth) is received that may identify at least one of the one or more target outcomes. For these embodiments, the request may originate from an end user, a source user, a third party (e.g., a network service provider, a content provider, and so forth), or from some other source.

In various embodiments, a personalized plan may merely be a collection of one or more emulatable aspects. An emulatable aspect may be an indication of any behavior, act, trait, physical state, mental state, social state, declaration, belief, or any other facet of a person (i.e., source user) that may be emulated in order to achieve one or more target outcomes. In some cases, a personalized plan may include only a single emulatable aspect. For example, a personalized plan for reducing cavities (e.g., target outcome) may include a single emulatable aspect (e.g., avoid sweet desserts). In other cases, a personalized plan may include multiple emulatable aspects. For example, a personalized plan to lose 20 pounds of body weight (e.g., target outcome) may include multiple emulatable aspects (e.g., the personalized plan includes a schedule of swimming and jogging activities where each activity is an emulatable aspect). 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 multiple emulatable aspects included in the personalized plan. For instance, in the above weight loss example, the personalized plan may indicate when certain activities should be executed with respect to other activities (e.g., swimming on day one, jogging on day two, and so forth).

In some cases, a personalized plan may indicate one or more emulatable intermediate outcomes that may be associated with one or more target outcomes of the personalized plan. For example, if a personalized plan includes a plurality of emulatable aspects, then one or more emulatable intermediate outcomes may also be included in the personalized plan that may represent one or more outcomes that are preferably or ideally achieved while the personalized plan is being executed and before the target outcome is achieved. The one or more emulatable intermediate outcomes that may be included in a personalized plan may be based on one or more reported aspects (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 achieving 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 (real) 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 indicating actual aspects of a plurality of real source users may be compiled and processed (e.g., normalized or averaged out) in order to create such a fictional source user.

Turning now to FIGS. 5-1a, and 5-1b 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 5-10. In various embodiments, the computing device 5-10 may be a server such as one of the one or more network servers 5-60 depicted in FIG. 5-1a. Alternatively, the computing device 5-10 may be a source user device such as one of the local source user devices 5-20* depicted in FIG. 5-1a. In still other embodiments, the computing device 5-10 may be an end user device such as the local end user device 5-30 depicted in FIG. 5-1a.

In particular, the methods, systems, circuitry, and computer program products may be implemented at any network device including a peer-to-peer network component device. Note that for ease of understanding and explanation, the following description of the exemplary environment of FIGS. 5-1a and 5-1b assumes that the computing 5-10 is a server rather than an end user device or a source user device. However, the following description of the exemplary environment of FIG. 5-1a and 5-1b will generally hold true even in embodiments where the computing device 5-10 is an end user device or a source user device with certain obvious exceptions (e.g., if the computing device 5-10 is an end user device or a source user device rather than a server, the computing device 5-10 may communicate with an end user 5-4 or a source user 5-2* directly through a user interface 5-120 rather than indirectly through a wireless network and/or wired network 5-50 as may be the case when the computing device 5-10 is a server).

In some embodiments, the computing device 5-10 may operate via a web 1.0 or web 2.0 construct. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 5-2*” may be in reference to a source user 5-2a, a source user 5-2b, and so forth.

In various embodiments, the computing device 5-10 may be designed to, among other things, acquire one or more relevant reported aspects 5-14 associated with one or more source users 5-2* that are relevant to achieving one or more target outcomes, the acquiring of the one or more relevant reported aspects 5-14 being based, at least in part, on relevancy of the one or more relevant reported aspects 5-14 with respect to the one or more target outcomes. The acquisition of the one or more relevant reported aspects 5-14 may, in some cases, be in response to receiving a request 5-12 from an end user 5-4 or from other parties. After acquiring the one or more relevant reported aspects 5-14, the computing device 5-10, may be configured to, among other things, develop one or more personalized plans 5-16 designed to facilitate the end user 5-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 5-16 are emulated, the development of the one or more personalized plans 5-16 being based, at least in part, on the acquisition of the one or more relevant reported aspects 5-14.

As briefly described earlier, in some implementations, the operation to acquire the one or more relevant reported aspects 5-14 by the computing device 5-10 may be prompted when the computing device 5-10 receives a request 5-12 (e.g., a solicitation, a query, and so forth) from an end user 5-4 (e.g., via a local end user device 5-30), from a source user 5-2*(e.g., via a local source user device 5-20*), from a network server 5-60, or from a third party 5-6 (e.g., a network service provider, a content provider, and so forth). For these implementations, the request 5-12 may at least indicate one of the one or more target outcomes, and in some cases, may solicit for the one or more personalized plans 5-16. Note that in embodiments where the computing device 5-10 is an end user device (e.g., local end user device 5-30) or a source user device (e.g., local source user device 5-20) the request 5-12 may be directly received from an end user 5-4 or from a source user 5-2* via a user interface 5-120.

As illustrated in FIGS. 5-1a and 5-1b, the computing device 5-10 may be employed in a network environment. For example, the computing device 5-10 may communicate with other network devices (e.g., a local end user device 5-30, one or more network servers 5-60, one or more local source user devices 5-20*, one or more sensing devices 5-40, and so forth) via a wireless network and/or wired network 5-50 (e.g., at least one of a wireless network and a wired network 5-50). In various implementations, the wireless and/or wired network 5-50 may include 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 5-50.

The computing device 5-10 may be designed to communicate with one or more source users 5-2*(via one or more local source user devices 5-20*) and an end user 5-4 (via a local end user device 5-30) through the wireless network and/or wired network 5-50. In some implementations, the computing device 5-10 may further communicate with, via the wireless network and/or wired network 5-50, one or more third parties 5-6 (e.g., one or more other end users 5-4, one or more content providers, one or more network service providers, and/or one or more other parties), one or more other network servers 5-60, and/or one or more sensing devices 5-40.

The computing device 5-10 as previously indicated may be a server (e.g., one of the one or more network servers 5-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 5-10 is a source user device (e.g., local source user device 5-20*) or an end user device (e.g., local end user device 5-30*) rather than a network server, the computing device 5-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.

With respect to the one or more sensing devices 5-40 of the exemplary environment of FIGS. 5-1a and 5-1b, the one or more sensing devices 5-40 may communicate with the wireless network and/or the wired network 5-50 directly or indirectly via the one or more local source user devices 5-20*. As will be further described herein with respect to FIG. 5-2c, each of the one or more sensing devices 5-40 (see FIG. 5-2c) may include one or more sensors 5-240, a network interface 5-242, and/or a memory 5-244. The one or more sensors 5-240 may be designed to detect or sense one or more aspects associated with one or more source users 5-2*.

Examples of sensors 5-240 include, for example, devices that can detect physical or physiological characteristics of one or more source users 5-2*, devices that can detect activities of the one or more source users 5-2*, devices that can detect external events (e.g., environmental conditions including the weather, pollution levels, performance of the stock market, and so forth), image capturing device such as a digital camera or camcorder, and/or devices that can detect the location of the one or more source users 5-2* such as a global positioning system or GPS. Examples of devices that can detect physical or physiological characteristics include, for example, a heart rate monitor, a blood pressure sensor, a glucose sensor, and so forth. Examples of devices that can detect activities of the one or more source users 5-2* including, for example, 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 source users 5-2* may comprise a first source user 5-2a, a second source user 5-2b, a third source user 5-2c, a fourth source user 5-2d, and so forth. The one or more local source user devices 5-20* may include a first local source user device 5-20a (e.g., to be used by the first source user 5-2a to communicate via wireless network and/or wired network 5-50), a second local source user device 5-20b (e.g., to be used by the second source user 5-2b to communicate via wireless network and/or wired network 5-50), and so forth. The one or more local source user devices 5-20* and the local end user device 5-30 (as well as the computing device 5-10 in embodiments in which the computing device 5-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 5-20 and/or the local end user device 5-30 (as well as the computing device 5-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 5-20 and/or local end user device 5-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.

Functionally, the computing device 5-10 may be designed to acquire one or more relevant reported aspects 5-14 (e.g., in the form of data) that may be relevant for achieving one or more target outcomes from one or more network sources including, for example, one or more local source user devices 5-20*, one or more sensing devices 5-40, one or more network servers 5-60, and/or one or more third parties 5-6. In some implementations, the one or more relevant reported aspects 5-14 may be acquired by transmitting one or more solicitations 5-13 for the one or more relevant reported aspects 5-14 to one or more potential sources (e.g., one or more local source user devices 5-20*, one or more sensing devices 5-40, one or more network servers 5-60, and so forth). In some implementations, the relevant reported aspects 5-14 to be acquired may have been originally reported via log entries such as blog entries, status reports, journal entries, entries provided by sensing devices 5-40, and/or other types of entries.

The acquisition of the one or more relevant reported aspects 5-14 may be based, at least in part, on the relevancy of the one or more relevant reported aspects 5-14 with respect to the one or more target outcomes. In particular, if one or more solicitations 5-13 are to be transmitting in order to acquire the one or more relevant reported aspects 5-14, then the one or more solicitations 5-13 may indicate at least one of the one or more target outcomes. The one or more solicitations 5-13 may also include other information such as relevancy factors in order to facilitate the receiving network device (e.g., local source user device 5-20* or a network server 5-60) in identifying the relevant reported aspects 5-14 from the many relevant and non-relevant reported aspects that the network device may be in possession of

After transmitting the one or more solicitations 5-13, the computing device 5-10 may receive the one or more relevant reported aspects 5-14 from one or more network sources (e.g., local source user device 5-20, one or more network servers 5-60, and so forth) in response to the solicitations 5-13. In some cases, the one or more relevant reported aspects 5-14 that may be received may be stored in memory 5-116. Based on the acquisition of the one or more relevant reported aspects 5-14, the computing device 5-10 may be designed to develop one or more personalized plans 5-16 designed to facilitate an end user 5-4 to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans 5-16 are emulated. In some embodiments, the computing device 5-10 after developing the one or more personalized plans 5-16, may present the one or more personalized plans 5-16 to the end user 5-4, to one or more source users 5-2*, to one or more network servers 5-60, or to one or more third parties 5-6.

The computing device 5-10 as illustrated in FIG. 5-1b may include a variety of modules, sub-modules, and various other components. As shown, the computing device 5-10 may include a relevant reported aspect acquisition module 5-102 (which may further include one or more sub-modules as illustrated in FIG. 5-2a), a personalized plan development module 5-104 (which may further include one or more sub-modules as illustrated in FIG. 5-2b), a presentation module 5-106 (which may further include a transmission module 5-224 and/or a user interface indication module 5-226), a memory 5-116 (which may store a plurality of reported aspects 5-15, one or more end user relevancy indications 5-142, one or more end user limitations 5-143, one or more source user relevancy indications 5-144, one or more third party source relevancy indications 5-145, one or more predefined time increment indications 5-146, and/or one or more applications 5-140), a network interface 5-118 (e.g., network interface card or NIC), and/or a user interface 5-120.

In various embodiments, the computing device 5-10 may further include a social networking entry reception module 5-110 (which may further include a blog entry reception module 5-111 and/or a status report reception module 5-112), a journal entry reception module 5-114, and/or a sensor data reception module 5-115. In various implementations, the computing device 5-10 may include a request reception module 5-122 designed to receive one or more requests 5-12 via, for example, a wireless network and/or wired network 5-50. For these implementations, the one or more requests 5-12 to be received by the request reception module 5-122 may indicate at least one target outcome and may request for one or more personalized plans 5-16 for achieving the at least one target outcome.

The relevant reported aspect acquisition module 5-102 may be configured to, among other things, acquire one or more relevant reported aspects 5-14 based, at least in part, on relevancy of the one or more relevant reported aspects 5-14 with respect to achievement of one or more target outcomes, the one or more relevant reported aspects 5-14 to be acquired being associated with one or more source users 5-2* and being relevant to achieving the one or more target outcomes. The personalized plan development module 5-104 may be configured to, among other things, develop one or more personalized plans 5-16 based, at least in part, on the acquisition of the one or more relevant reported aspects 5-14, the one or more personalized plans 5-16 being designed to facilitate an end user 5-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 5-16 are emulated.

The presentation module 5-106 may be designed to present (e.g., transmit via the wireless network and/or wired network 5-50 to the local end user device 5-30, to one or more local source user devices 5-20, to one or more network servers 5-60, and/or to one or more third parties 5-6) the one or more personalized plans 5-16 that are developed. A more detailed discussion relating to the relevant reported aspect acquisition module 5-102, the personalized plan development module 5-104, the presentation module 5-106, and their sub-modules, will be provided below with respect to the various operational flows to be described herein.

The memory 5-116 may be designed to store various data including a plurality of reported aspects 5-15 associated with one or more source user 5-2*. The plurality of reported aspects 5-15 stored in the memory 5-116 may include both reported aspects 5-15 that are relevant to achieving one or more target outcomes (e.g., relevant reported aspects 5-14) and reported aspects 5-14 that may not be relevant to achieving any target outcome. Other types of data may be stored in the memory 5-116 including, for example, one or more end user relevancy indications 5-142 (e.g., one or more indications that indicate the types of reported or emulatable aspects that an end user 5-4 has an interest in or believes is relevant to achieving one or more target outcomes), one or more end user limitations 5-143 (e.g., limitations such as contextual limitations, physical limitations, personal limitations, and so forth, associated with the end user 5-4 that prevent one or more emulatable aspects from being emulated), and/or one or more source user relevancy indications 5-144 (e.g., one or more indications provided by a source user 5-2* that indicate at least which types of reported aspects are relevant to achieving one or more target outcomes).

In some cases, the memory 5-116 may also include, for example, one or more third party source relevancy indications 5-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 5-6 that indicate at least which types of reported aspects are relevant to achieving one or more target outcomes), one or more predefined time increment indications 5-146 (e.g., one or more indications that indicate at least one time increment such as a time increment or window that may be used in order to conclude whether, for example, a reported aspect is relevant for achieving at least one target outcome only if the reported aspect indicate an aspect that occurred within the at least one time increment from an occurrence of the target outcome as successfully achieved by, for example, a source user 5-2*), and/or one or more applications 5-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). In various implementations, the memory 5-116 comprises 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 social networking entry reception module 5-110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 5-2*, an end user 5-4, one or more third parties 5-6, and/or one or more network servers 5-60. The social networking entry reception module 5-110 may further include a blog entry reception module 5-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 5-112 for receiving social networking status reports. The journal entry reception module 5-114 may be configured to receive journal entries from, for example, the one or more source users 5-2, the end user 5-4, and/or from the one or more third parties 5-6 (e.g., a non-user). The sensor data reception module 5-115 may be configured to receive sensing data from one or more sensing devices 5-40. The user interface 5-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. 5-2 a illustrates particular implementations of the relevant reported aspect acquisition module 5-102 of the computing device 5-10 of FIG. 5-1b. As illustrated, the relevant reported aspect acquisition module 5-102 may include, in various implementations, one or more sub-modules. For example, in some implementations, the relevant reported aspect acquisition module 5-102 may include a network searching module 5-200 that is configured to search for one or more relevant reported aspects 5-14 via a wireless network and/or wired network 5-50.

In order to facilitate the network searching module 5-200 to search for the one or more relevant reported aspects 5-14, the network searching module 5-200 may include a solicitation transmission module 5-202 and/or a relevant reported aspect reception module 5-204. The solicitation transmission module 5-202 may be configured to, among other things, transmit via the wireless network and/or wired network 5-50 one or more solicitations 5-13 for the one or more relevant reported aspects 5-14. As will be further described herein, various types of information may be indicated by the one or more solicitations 5-13 to be transmitted. In contrast, the relevant reported aspect reception module 5-204 may be configured to receive the solicited one or more relevant reported aspects 5-14.

FIG. 5-2 b illustrates particular implementations of the personalized plan development module 5-104 of FIG. 5-1b. As previously indicated, the personalized plan development module 5-104 may be configured to develop one or more personalized plans 5-16 that are designed to facilitate an end user 5-4 to achieve one or more target outcomes when one or more emulated aspects included in the one or more personalized plans 5-16 are emulated, the development of the one or more personalized plans 5-16 being based on one or more relevant reported aspects 5-14 that are acquired by the relevant reported aspect acquisition module 5-102.

In various implementations, the personalized plan development module 5-104 may include one or more of an emulatable aspect inclusion module 5-220, a relationship defining module 5-222, an emulatable intermediate outcome inclusion module 5-223, a limitation compliance determination module 5-224 (which may include an action module 5-225 that may further include a non-compliance notification module 5-226 and/or a personalized plan modification module 5-228), and/or a plausible determination module 5-230 (which may include an action module 5-232 that may further include a not plausible notification module 5-234 and/or a personalized plan modification module 5-236).

The emulatable aspect inclusion module 5-220 may be configured to include into each of the one or more personalized plans 5-16 to be developed one or more emulatable aspects that correspond to the one or more relevant reported aspects acquired by the relevant reported aspect acquisition module 5-102. The relationship defining module 5-222 may be configured to define in each of the one or more personalized plans 5-16 to be developed one or more relationships (e.g., spatial, temporal, and/or specific time relationships) between a plurality of emulatable aspects that may be included in each of the one or more personalized plans 5-16. The emulatable intermediate outcome inclusion module 5-223 may be configured to include into at least one of the one or more personalized plans 5-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 5-16.

The limitation compliance determination module 5-224 may be configured to determine whether the one or more emulatable aspects to be included in the one or more personalized plans 5-16 complies with one or more limitations associated with the end user 5-4, and if not compliant, execute one or more actions (e.g., as executed by the action module 5-225). Various types of actions may be executed by the action module 5-225 if a determination is made of non-compliance. For example, in some implementations, the action module 5-225 may include a non-compliance notification module 5-226 that is configured to notify (e.g., notifying by transmitting a notification or by indicating via a user interface 5-120) at least one of the end user 5-4 and a third party 5-6 regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user 5-4. Other types of actions may be executed by the action module 5-225 in various implementations. For example, in some implementations, the action module 5-225 may include a personalized plan modification module 5-228 that is configured to modify the one or more personalized plans 5-16 including revising one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 5-4 or replacing one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 5-4 with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user 5-4.

The plausible determination module 5-230, in contrast to the limitation compliance determination module 5-224, may be configured to determine whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is a plausible aspect that has been successfully emulated by one or more third parties 5-6 (e.g., other end users 5-4), and if not plausible, execute one or more actions (e.g., as executed by the action module 5-232). Various types of actions may be executed by the action module 5-232 if a determination is made of non-compliance.

For example, in some implementations, the action module 5-232 may include a not plausible notification module 5-234 that is configured to notify, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is not a plausible aspect, at least one of the end user 5-4 and a third party 5-6 regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is not a plausible aspect. Note that in some implementations, a “plausible aspect” may be an aspect that has been successfully emulated by one or more third parties 5-6 in order to, for example, achieve the one or more target outcomes.

Other types of actions may also be executed by the action module 5-232 when one or more emulatable aspects that may be included in the one or more personalized plans 5-16 have been determined to be not plausible. For example, in some implementations, the action module 5-232 may include a personalized plan modification module 5-236 that is configured to modify, in response to a determination that at least one of the one or more emulatable aspects included in the one or more personalized plans 5-16 is not a plausible aspect, at least one of the one or more personalized plans 5-16 by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 5-6.

Referring now to FIG. 5-2c illustrating one of the sensing devices 5-40 of FIGS. 5-1a and 5-1b. The sensing device 5-40, in various implementations, may include at least one or more sensors 5-240. The one or more sensors 5-240 that may be included in a sensing device 5-40 may be designed to sense or detect one or more aspects associated with a source user 5-2*. For example, in various implementations, the one or more sensors 5-240 may include one or more devices that can monitor a user's physiological characteristics such as blood pressure sensors, heart rate monitors, glucometers (e.g., blood glucose meter), and so forth.

In some implementations, the one or more sensors 5-240 may include devices that can detect activities of a user (e.g., a source user 5-2*). Examples of such devices include, for example, 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 5-240 may include, in various implementations, 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 5-2*, global positioning system (GPS) to provide location data related to a user (e.g., locations of the source user 5-2*), and so forth. In various implementations, a sensing device 5-40 may further include a network interface 5-242 and/or a memory 5-244 to store, for example, sensing data provided by the one or more sensors 5-240.

Referring back to the computing device 5-10 of FIG. 5-1b, the various modules (e.g., the relevant reported aspect acquisition module 5-102, the personalized plan development module 5-104, the presentation module 5-106, and so forth) along with their sub-modules included in the computing device 5-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the relevant reported aspect identification module 5-102, the personalized plan development module 5-104, and/or the presentations module 5-106 may be implemented with a processor 5-802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 5-804 (e.g., computer program product) stored in a storage medium 5-806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 5-800 of FIG. 5-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 discussion related to the computing device 5-10 of FIG. 5-1b will now be provided with respect to the processes and operations to be described herein. FIG. 5-3 illustrates an operational flow 5-300 representing example operations related to, among other things, acquisition of one or more relevant reported aspects 5-14 associated with one or more source users 5-2* that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects 5-14 being based, at least in part, on relevancy of the one or more relevant reported aspects 5-14 with respect to the one or more target outcomes, and development of one or more personalized plans 5-16 designed to facilitate an end user 5-4 to achieve the one or more target outcomes when one or more emulatable aspects included in the one or more personalized plans 5-16 are emulated, the development of the one or more personalized plans 5-16 being based on the acquisition of the one or more relevant reported aspects 5-14.

In FIG. 5-3 and in the following figures that include various examples of operational flows, discussions and explanations may be provided with respect to the exemplary environment described above as illustrated in FIGS. 5-1a and 5-1b, and/or with respect to other examples (e.g., as provided in FIGS. 5-2a, 5-2b, and 5-2c) 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. 5-1a, 5-1b, 5-2a, 5-2b, and 5-2c. 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. 5-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 5-300 may move to a relevant reported aspect acquiring operation 5-302 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. For instance, and as an illustration, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 of FIG. 5-1b acquiring (e.g., receiving, searching, retrieving, obtaining, and so forth) one or more relevant reported aspects associated with one or more source users 5-2* and that are relevant to achieving one or more target outcomes, the acquisition of the one or more relevant reported aspects 5-14 being based, at least in part, on relevancy of the one or more relevant reported aspects 5-14 with respect to the achievement of the one or more target outcomes.

Note that in various implementations, the acquisition of the one or more relevant reported aspects 5-14 may not depend on the identification, at least initially, of the one or more source users 5-2* who may have achieved the one or more target outcomes. Rather, the acquisition of the one or more relevant reported aspects 5-14 may be based on the relevancy of the one or more relevant reported aspects 5-14 with respect to achieving the one or more target outcomes.

In addition to the relevant reported aspect acquiring operation 5-302, operational flow 5-300 may also include a personalized plan developing operation 5-304 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. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing (e.g., creating) one or more personalized plans 5-16 designed to facilitate an end user 5-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 5-16 are emulated, the development of the one or more personalized plans 5-16 being based, at least in part, on the acquisition of the one or more relevant reported aspects 5-14. As will be described herein, the relevant reported aspect acquiring operation 5-302 as well as the personalized plan developing operation 5-304 may be implemented in a number of different ways in various alternative implementations as will be described herein.

For example, FIGS. 5-4a, 5-4b, 5-4c, 5-4d, 5-4e, 5-4f, 5-4g, and 5-4h illustrate the various ways that the relevant reported aspect acquiring operation 5-302 of FIG. 5-3 may be implemented in various alternative implementations. In some implementations, for example, the relevant reported aspect acquiring operation 5-302 may include an operation 5-402 for acquiring the one or more relevant reported aspects via at least one of a wireless network and a wired network as depicted in FIG. 5-4a. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 of FIG. 5-1b acquiring the one or more relevant reported aspects 5-14 by at least acquiring the one or more relevant reported aspects 5-14 (e.g., aspects of the one or more source users 5-2* that have been reported and that may indicate, for example, the behaviors or acts of the one or more source users 5-2*) via at least one of a wireless network and a wired network 5-50.

In some implementations, operation 5-402 may further include an operation 5-403 for searching for the one or more relevant reported aspects via at least one of a wireless network and a wired network as depicted in FIG. 5-4a. For instance, the network searching module 5-200 (see FIG. 5-2a) of the computing device 5-10 searching (e.g., seeking, querying, and so forth) for the one or more relevant reported aspects 5-14 via at least one of a wireless network and a wired network 5-50.

Operation 5-403, in turn, may include an operation 5-404 for transmitting one or more solicitations for the one or more relevant reported aspects via at least one of the wireless network and the wired network as further depicted in FIG. 5-4a. For instance, the solicitation transmission module 5-202 (see FIG. 5-2a) of the computing device 5-10 transmitting one or more solicitations 5-13 (e.g., requests, queries, and so forth) for the one or more relevant reported aspects 5-14 via at least one of the wireless network and the wired network 5-50.

In some implementations, operation 5-404 may include an operation 5-405 for transmitting the one or more solicitations for the one or more relevant reported aspects including one or more solicitations that indicate the one or more target outcomes as depicted in FIG. 5-4a. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for the one or more relevant reported aspects 5-14 including one or more solicitations 5-13 that indicate the one or more target outcomes. By merely indicating at least the one or more target outcomes in the one or more solicitations 5-13, one or more relevant reported aspects 5-14 may be selectively acquired even if the one or more solicitations 5-13 does not identify those source users 5-2* who have achieved the one or more target outcomes.

For example, in some implementations, operation 5-405 may include an operation 5-406 for transmitting the one or more solicitations that indicate the one or more target outcomes including one or more solicitations that does not indicate any of the one or more source users as depicted in FIG. 5-4a. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate the one or more target outcomes including one or more solicitations 5-13 that does not indicate any of the one or more source users 5-2*.

In the same or different implementations, operation 5-405 may include an operation 5-407 for transmitting the one or more solicitations that indicate the one or more target outcomes including one or more solicitations that solicit for one or more reported aspects that are associated with one or more source users who have achieved the one or more target outcomes as depicted in FIG. 5-4a. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate the one or more target outcomes including one or more solicitations 5-13 that solicit for one or more reported aspects 5-14 that are associated with one or more source users 5-2* who have achieved the one or more target outcomes.

Operation 5-407 in turn may further include an operation 5-408 for transmitting the one or more solicitations that solicit for one or more reported aspects that are associated with one or more source users who have achieved the one or more target outcomes including one or more solicitations that does not indicate any of the one or more source users who have achieved the one or more target outcomes as depicted in FIG. 5-4a. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that solicit for one or more reported aspects 5-14 that are associated with one or more source users 5-2* who have achieved the one or more target outcomes including one or more solicitations 5-13 that does not indicate any of the one or more source users 5-2* who have achieved the one or more target outcomes.

In some implementations, operation 5-405 may include an operation 5-409 for transmitting the one or more solicitations that indicate the one or more target outcomes including one or more solicitations that indicate one or more relevancy factors as depicted in FIG. 5-4b. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate the one or more target outcomes including one or more solicitations 5-13 that indicate one or more relevancy factors (e.g., bases for determining whether a reported aspect is relevant to achieving one or more target outcomes).

Various types of relevancy factors may be indicated by the one or more solicitations 5-13 to be transmitted in various alternative implementations. For example, in some implementations, operation 5-409 may include an operation 5-410 for transmitting the one or more solicitations that indicate one or more relevancy factors including one or more solicitations that indicate one or more aspect types that are of interest to the end user as depicted in FIG. 5-4b. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13* that indicate one or more relevancy factors including one or more solicitations 5-13 that indicate one or more aspect types (e.g., dietary activities, sleep or rest activities, reading activities, user locations, mental states, and so forth) that are of interest to the end user 5-4.

In the same or different implementations, operation 5-409 may include an operation 5-411 for transmitting the one or more solicitations that indicate one or more relevancy factors including one or more solicitations that indicate one or more aspect types indicated by at least one source user as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 5-4b. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more relevancy factors including one or more solicitations 5-13 that indicate one or more aspect types (e.g., exercise activities, medication usage, mental attitudes, social or employment activities, and so forth) indicated by at least one source user 5-2* as being relevant to the achievement of the one or more target outcomes (e.g., losing weight, feeling more alert, reduce pain, increase sexual intimacy activities, and so forth).

In the same or different implementations, operation 5-409 may include an operation 5-412 for transmitting the one or more solicitations that indicate one or more relevancy factors including one or more solicitations that indicate one or more aspect types 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. 5-4b. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more relevancy factors including one or more solicitations 5-13 that indicate one or more aspect types indicated by at least one third party source (e.g., third party 5-6) as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 5-409 may include an operation 5-413 for transmitting the one or more solicitations that indicate one or more relevancy factors including one or more solicitations that indicate one or more aspect types including one or more solicitations that indicate one or more predefined time increments, the one or more predefined time increments to be considered in order to determine relevancy of one or more reported aspects with respect to achieving the one or more target outcomes as depicted in FIG. 5-4b. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more relevancy factors including one or more solicitations 5-13 that indicate one or more aspect types including one or more solicitations 5-13 that indicate one or more predefined time increments, the one or more predefined time increments (e.g., one day, one week, three months, one year, five years, and so forth) to be considered in order to determine relevancy of one or more reported aspects with respect to achieving the one or more target outcomes.

That is, not all relevant reported aspects 5-14 that may be relevant with respect to certain relevancy factors may actually be relevant to achieving the one or more target outcomes if the relevant reported aspects 5-14 indicate aspects that, time-wise, occurred remotely from occurrence of the one or more target outcomes as successfully achieved by the one or more source users 5-2*. For example, reported aspects that are associated with source users 5-2* who have achieved the one or more target outcomes and that are relevant based on certain relevancy factors (e.g., belong to a type of aspect that is of interest to the end user 5-4) may, nevertheless, not be relevant to achieving the one or more target outcomes if they occurred well before (or well after) the achievement of the one or more target outcomes (e.g., as represented by one or more reported aspects that corresponds to the one or more target outcomes) by the one or more source users 5-2*. Thus, a reported aspect may, in some cases, be relevant to the achievement of the one or more target outcomes only if it falls within some time increment (e.g., “predefined time increment”) from the one or more occurrences of the one or more reported aspects that correspond to the one or more target outcomes. The length of the predefined time increments to be considered in determining relevancy may depend on a number of factors.

For example, in some embodiments, the lengths of the one or more predefined time increments (e.g., each of the one or more target outcomes may be associated with a different predefined time increment) may be based on the type of personalized plans 5-16 being developed. Alternatively, the one or more predefined time increments may be set by the end user 5-4, by one or more source users 5-2*, or by one or more third parties 5-6. As an illustration, suppose an end user 5-4 is interested in finding out what type of reading activities could help improve his verbal score on the SAT in six months. The end user 5-4 may then indicate that he is only interested in reported aspects 5-14 that indicate reading activities that have occurred during the six months prior to the taking of an SAT exam.

Other types of relevancy factors may also be indicated by the one or more solicitations 5-13 to be transmitted in various alternative implementations. For example, in the same or different implementations, operation 5-409 may include an operation 5-414 for transmitting the one or more solicitations that indicate one or more relevancy factors including one or more solicitations that indicate one or more traits associated with the end user as depicted in FIG. 5-4c. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more relevancy factors including one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4. That is, in some cases, a reported aspect may be deemed relevant only if, for example, the reported aspect is associated with a source user 5-2* who has achieved a target outcome and who has the same specific traits of the end user 5-4 (e.g., same type of jobs or same marital status).

Various types of traits associated with the end user 5-4 may be indicated by the one or more solicitations 5-13 in various alternative implementations. For example, in some implementations, operation 5-414 may include an operation 5-415 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate one or more social networking groups associated with the end user as depicted in FIG. 5-4c. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate one or more social networking groups (e.g., groups that include members that have common interests and/or common traits) associated with the end user 5-4.

In the same or different implementations, operation 5-414 may include an operation 5-416 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate at least one of an ethnic and a religious group associated with the end user as depicted in FIG. 5-4c. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate at least one of an ethnic and a religious group (e.g., Irish ancestry, Hispanic ancestry, Buddhist, Christian, and so forth) associated with the end user 5-4.

In the same or different implementations, operation 5-414 may include an operation 5-417 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate at least one of a gender and an age group associated with the end user as depicted in FIG. 5-4c. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate at least one of a gender and an age group (e.g., male, female, 18 years old, over 65 years of age, and so forth) associated with the end user 5-4.

In the same or different implementations, operation 5-414 may include an operation 5-418 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate one or more physical or mental handicap associated with the end user as depicted in FIG. 5-4c. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate one or more physical or mental handicap (e.g., blindness, phobic, missing a particular limb, diabetes, and so forth) associated with the end user 5-4.

In the same or different implementations, operation 5-414 may include an operation 5-419 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate one or more health or medical states associated with the end user as depicted in FIG. 5-4d. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate one or more health or medical states (e.g., in top physical shape, in-patient, being treated for a particular illness, and so forth) associated with the end user 5-4.

In the same or different implementations, operation 5-414 may include an operation 5-420 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate one or more intellectual or academic states associated with the end user as depicted in FIG. 5-4d. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate one or more intellectual or academic states (e.g., college senior, in a particular field of study, a PhD, and so forth) associated with the end user 5-4.

In the same or different implementations, operation 5-414 may include an operation 5-421 for transmitting the one or more solicitations that indicate one or more traits associated with the end user including one or more solicitations that indicate one or more social states associated with the end user as depicted in FIG. 5-4d. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 that indicate one or more traits associated with the end user 5-4 including one or more solicitations 5-13 that indicate one or more social states (e.g., membership in a social group, having many or few friends, and so forth) associated with the end user 5-4.

The one or more relevant reported aspects 5-14 to be solicited through the solicitation transmission operation 5-404 may have been originally reported in a variety of different forms. For example, in some implementations, operation 5-404 may include an operation 5-422 for transmitting the one or more solicitations for the one or more relevant reported aspects including one or more solicitations for one or more relevant reported aspects that were originally reported through log entries as depicted by FIG. 5-4e. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for the one or more relevant reported aspects 5-14 including one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through log entries (e.g., electronic entries that are continuously, regularly, semi-regularly, or randomly entered).

In some implementations, operation 5-422 may include an operation 5-423 for transmitting the one or more solicitations for one or more relevant reported aspects that were originally reported through log entries including one or more solicitations for one or more relevant reported aspects that were originally reported through blog entries as depicted in FIG. 5-4e. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through log entries including one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through blog entries (e.g., microblog entries).

In the same or different implementations, operation 5-422 may include an operation 5-424 for transmitting the one or more solicitations for one or more relevant reported aspects that were originally reported through log entries including one or more solicitations for one or more relevant reported aspects that were originally reported through status reports as depicted in FIG. 5-4e. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through log entries including one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through status reports (e.g., social networking status reports).

In the same or different implementations, operation 5-422 may include an operation 5-425 for transmitting the one or more solicitations for one or more relevant reported aspects that were originally reported through log entries including one or more solicitations for one or more relevant reported aspects that were originally reported through journal entries as depicted in FIG. 5-4e. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through log entries including one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through journal entries (e.g., diary entries).

In the same or different implementations, operation 5-422 may include an operation 5-426 for transmitting the one or more solicitations for one or more relevant reported aspects that were originally reported through log entries including one or more solicitations for one or more relevant reported aspects that were originally reported through sensing device entries as depicted in FIG. 5-4e. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through log entries including one or more solicitations 5-13 for one or more relevant reported aspects 5-14 that were originally reported through sensing device entries (e.g., data providing by one or more sensing devices 5-40).

In some cases, operation 5-404 for transmitting the one or more solicitations for the one or more relevant reported aspects may include an operation 5-427 for transmitting the one or more solicitations for the one or more relevant reported aspects to one or more local source user devices as depicted in FIG. 5-4f. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for the one or more relevant reported aspects 5-14 to one or more local source user devices 5-20*.

In the same or different implementations, operation 5-404 may include an operation 5-428 for transmitting the one or more solicitations for the one or more relevant reported aspects to one or more network servers as depicted in FIG. 5-4f. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for the one or more relevant reported aspects 5-14 to one or more network servers 5-60.

In the same or different implementations, operation 5-404 may include an operation 5-429 for transmitting the one or more solicitations for the one or more relevant reported aspects to one or more third parties as depicted in FIG. 5-4f. For instance, the solicitation transmission module 5-202 of the computing device 5-10 transmitting the one or more solicitations 5-13 for the one or more relevant reported aspects 5-14 to one or more third parties 5-6 (e.g., content providers, network service providers, other end users 5-4, and so forth).

In the same or different implementations, operation 5-404 may include an operation 5-430 for receiving the one or more relevant reported aspects as depicted in FIG. 5-4f. For instance, the relevant reported aspect reception module 5-204 (see FIG. 5-2a) of the computing device 5-10 receiving the one or more relevant reported aspects 5-14 that were solicited.

In various implementations, the relevant reported aspect acquiring operation 5-302 of FIG. 5-3 may acquire various types of relevant reported aspects 5-14 that may indicate a variety of aspects associated with the one or more source users 5-2*. For example, in some implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-431 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects associated with two or more source users as depicted in FIG. 5-4g. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 associated with two or more source users 5-2*(e.g., source user 5-2a and source user 5-2b of FIG. 5-1a).

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-432 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 5-4g. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more intermediate outcomes (e.g., running a mile in 10 minutes) associated with the one or more target outcomes (e.g., running a mile in 7 minutes).

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-433 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more behavior incidences associated with the one or more source users as depicted in FIG. 5-4g. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more behavior incidences (e.g., activities such as dietary activities or social manners) associated with the one or more source users 5-2*.

In some cases, operation 5-433 may further include an operation 5-434 for acquiring the one or more relevant reported aspects indicating one or more behavior incidences associated with the one or more source users including one or more relevant reported aspects indicating one or more incidences of activities executed by the one or more source users as depicted in FIG. 5-4g. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 indicating one or more behavior incidences associated with the one or more source users 5-2* including one or more relevant reported aspects 5-14 indicating one or more incidences of activities (e.g., leisure activities, sleep or rest activities, employment activities, exercise activities, and so forth) executed by the one or more source users 5-2*.

In the same or different implementations, operation 5-433 may include an operation 5-435 for acquiring the one or more relevant reported aspects indicating one or more behavior incidences associated with the one or more source users including one or more relevant reported aspects indicating one or more user attitudes or conduct associated with the one or more source users as depicted in FIG. 5-4g. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 indicating one or more behavior incidences associated with the one or more source users 5-2* including one or more relevant reported aspects indicating one or more user attitudes or conduct associated with the one or more source users 5-2*.

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-436 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more incidences of one or more user beliefs associated with the one or more source users as depicted in FIG. 5-4h. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more incidences of one or more user beliefs (e.g., religious or spiritual beliefs, dietary beliefs, superstitious beliefs, and so forth) associated with the one or more source users 5-2*.

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-437 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more incidences of one or more subjective user states associated with the one or more source users as depicted in FIG. 5-4h. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more incidences of one or more subjective user states associated with the one or more source users 5-2*.

A subjective user state may be any state or status associated with a source user 5-2* that can typically only be indicated by the source user 5-2*. Examples of subjective user states include, for example, subjective user mental states (e.g., sadness, happiness, mental exhaustion, alertness, and so forth), subjective user physical states (e.g., sore back, blurred vision, overall physical exhaustion, and so forth), and subjective user overall states (e.g., any other subjective user states that are neither a subjective user mental state or a subjective user physical state including, for example, “feeling good,” “feeling bad,” “feeling alive,” and so forth).

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-438 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 5-4h. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more incidences of one or more user physical characteristics (e.g., hair color, skin color, overall physical shape, and so forth) associated with the one or more source users 5-2*.

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-439 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more incidences of user locations associated with the one or more source users as depicted in FIG. 5-4h. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more incidences of user locations (e.g., New York City, Hawaii, home, workplace, and so forth) associated with the one or more source users 5-2*.

In the same or different implementations, the relevant reported aspect acquiring operation 5-302 may include an operation 5-440 for acquiring the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more incidences of external events associated with the one or more source users as depicted in FIG. 5-4h. For instance, the relevant reported aspect acquisition module 5-102 of the computing device 5-10 acquiring the one or more relevant reported aspects 5-14 including one or more relevant reported aspects 5-14 indicating one or more incidences of external events associated with the one or more source users 5-2*.

Referring back to the personalized plan developing operation 5-304 of FIG. 5-3, the personalized plan developing operation 5-304 may be executed in a number of different ways in various alternative implementations. For example, in some implementations, the personalized plan developing operation 5-304 may include an operation 5-541 for including into each of the one or more personalized plans one or more emulatable aspects that correspond to the one or more relevant reported aspects as depicted in FIG. 5-5a. For instance, the emulatable aspect inclusion module 5-220 (see FIG. 5-2b) of the computing device 5-10 including into each of the one or more personalized plans 5-16 one or more emulatable aspects (e.g., data indicating the one or more emulatable aspects) that correspond to the one or more relevant reported aspects 5-14 (e.g., as acquired through the relevant reported aspect acquiring operation 5-302).

As will be further described, operation 5-541 for including the one or more emulatable aspects into the one or more personalized plans 5-16 may include one or more additional operations in various alternative implementations. For example, in some cases, operation 5-541 may further include an operation 5-542 for including into each of the one or more personalized plans a plurality of emulatable aspects that correspond to a plurality of relevant reported aspects that are associated with the one or more source users and that are relevant to achieving the one or more target outcomes as depicted in FIG. 5-5a. For instance, the emulatable aspect inclusion module 5-220 of the computing device 5-10 including into each of the one or more personalized plans 5-16 a plurality of emulatable aspects that corresponds to a plurality of relevant reported aspects 5-14 that are associated with the one or more source users 5-2* and that are relevant to achieving the one or more target outcomes.

Operation 5-542, in turn, may include an operation 5-543 for defining in each of the one or more personalized plans one or more relationships between the plurality of emulatable aspects included in each of the one or more personalized plans as depicted in FIG. 5-5a. For instance, the relationship defining module 5-222 (see FIG. 5-2b) of the computing device 5-10 defining in each of the one or more personalized plans 5-16 one or more relationships (e.g., temporal relationships, specific time relationships, and/or spatial relationships) between the plurality of emulatable aspects included in each of the one or more personalized plans 5-16.

In various implementations, the operation 5-541 for including into each of the one or more personalized plans 5-16 one or more emulatable aspects that correspond to the one or more relevant reported aspects may include an operation 5-544 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans comply with one or more limitations associated with the end user, and if not, execute one or more actions as depicted in FIG. 5-5a. For instance, the limitation compliance determination module 5-224 (see FIG. 5-2b) of the computing device 5-10 determining whether the one or more emulatable aspects to be included in the one or more personalized plans 5-16 complies with (e.g., does not violate) one or more limitations associated with the end user 5-4 (e.g., limitations that prevent or make it impractical for the one or more emulatable aspects to be successfully emulated by the end user 5-4), and if not compliant, execute one or more actions.

In various implementations, operation 5-544 may further include one or more additional operations. For example, in some implementations, operation 5-544 may include an operation 5-545 for notifying at least one of the end user and a third party regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user as depicted in FIG. 5-5a. For instance, the non-compliance notification module 5-226 (see FIG. 5-2b) of the computing device 5-10 notifying at least one of the end user 5-4 and a third party 5-6 regarding non-compliance of the one or more emulatable aspects in response to a determination of non-compliance with the one or more limitations associated with the end user 5-4.

In the same or different implementations, operation 5-544 may include an operation 5-546 for modifying the one or more personalized plans including revising one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user or replacing the one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user as depicted in FIG. 5-5a. For instance, the personalized plan modification module 5-228 (see FIG. 5-2b) of the computing device 5-10 modifying the one or more personalized plans 5-16 including revising one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 5-4 or replacing the one or more emulatable aspects that have been determined not to be in compliance with the one or more limitations associated with the end user 5-4 with one or more replacement emulatable aspects that does comply with the one or more limitations associated with the end user 5-4.

As a further illustration, if an emulatable aspect such as “swimming for 40 minutes” is determined to be non-compliant, than revising the non-compliant aspect (e.g., “swimming for 20 minutes”) or replacing the non-compliant emulatable aspect with a complaint emulatable aspect (e.g., “jogging for one hour” that results in the same amount of calories being burned) that is at least proximately equivalent to the non-compliant emulatable aspect. Of course, what is “at least proximately equivalent” will depend on the type of emulatable aspect being replaced and the type of personalized plan 5-16 being developed.

In the same or different implementations, operation 5-544 may include an operation 5-547 for determining whether the one or more emulatable aspects to be included in the one or more personalized plans comply with at least one of a contextual limitation, a physical limitation, a personal limitation, a health limitation, a medical limitation, a user state limitation, and a legal limitation associated with the end user as depicted in FIG. 5-5a. For instance, the limitation compliance determination module 5-224 of the computing device 5-10 determining whether the one or more emulatable aspects to be included in the one or more personalized plans 5-16 complies with at least one of a contextual limitation (e.g., a logistical limitation such as a scheduling limitation, a geographical limitation, an asset limitation, and so forth), a physical limitation (e.g., missing limb, paralysis, visual or hearing impediment, and so forth), a personal limitation (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), a health limitation (e.g., health limitations related to the physical conditioning of the end user 5-4, genetic limitations, and so forth), a medical limitation (e.g., medical limitations such as limitations resulting from an illness or treatment of an illness including limitations due to cancer or treatment for the cancer, and so forth), a user state limitation (e.g., end user 5-4 is married, end user 5-4 is in mourning, end user 5-4 is unemployed, end user 5-4 is a vegan, and so forth), or a legal limitation (e.g., drug regulations, laws related to conduct or behavior in the jurisdiction of the end user 5-4, and so forth) associated with the end user 5-4, and if not, execute one or more actions.

In various implementations, the operation 5-541 for including one or more emulatable aspects into each of the one or more personalized plans may include an operation 5-548 for determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans is a plausible aspect that has been successfully emulated by one or more third parties, and if not, execute one or more actions as depicted in FIG. 5-5b. For instance, the plausible determination module 5-230 (see FIG. 5-2b) of the computing device 5-10 determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is a plausible aspect that has been successfully emulated by one or more third parties 5-6 (e.g., other end users 5-4* or disinterested parties), and if not plausible, execute one or more actions.

In various implementations, operation 5-548 may include one or more additional operations. For example, in some implementations, operation 5-548 may include an operation 5-549 for notifying, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans is not a plausible aspect, at least one of the end user and a third party regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans is not a plausible aspect as depicted in FIG. 5-5b. For instance, the not plausible notification module 5-234 (see FIG. 5-2b) of computing device 5-10 notifying, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is not a plausible aspect, at least one of the end user 5-4 and a third party 5-6 regarding the determination that the at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is not a plausible aspect.

In the same or different implementations, operation 5-548 may include an operation 5-550 for modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more personalized plans by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties as depicted in FIG. 5-5b. For instance, the personalized plan modification module 5-236 (see FIG. 5-2b) of the computing device 5-10 modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more personalized plans 5-16 by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 5-6 (e.g., other end users 5-4* or disinterested parties).

In the same or different implementations, operation 5-548 may include an operation 5-551 for determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans is a plausible aspect that has been successfully emulated by the one or more third parties in order to achieve at least one of the one or more target outcomes, and if not, execute the one or more actions as depicted in FIG. 5-5b. For instance, the plausible determination module 5-230 of the computing device 5-10 determining whether at least one of the one or more emulatable aspects to be included in the one or more personalized plans 5-16 is a plausible aspect that has been successfully emulated by one or more third parties 5-6 in order to achieve at least one of the one or more target outcomes, and if not plausible, execute one or more actions.

Various types of personalized plans 5-16 may be developed through the personalized plan developing operation 5-304 of FIG. 5-3. For example, in some implementations, the personalized plan developing operation 5-304 may include an operation 5-552 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more health or medical outcomes as depicted in FIG. 5-5c. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more health or medical outcomes (e.g., recovery time or recovery success related to an illness, weight loss, improve lifespan, physiological outcomes such as reducing blood pressure or blood glucose levels, increase red blood cell count, improve blood circulation, and so forth).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-553 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more athletic outcomes as depicted in FIG. 5-5c. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve 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 the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-554 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more gaming outcomes as depicted in FIG. 5-5c. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more gaming outcomes (e.g., winning a chest tournament or improve video gaming skills).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-555 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more occupational outcomes as depicted in FIG. 5-5c. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more occupational outcomes (e.g., a job promotion, complete a work project on time, develop new occupational relationships, and so forth).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-556 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more social outcomes as depicted in FIG. 5-5c. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more social outcomes (e.g., attaining a certain social class, having a dinner date with a particular person, developing a particular reputation, develop or expand social networks, and so forth).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-557 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more leisure outcomes as depicted in FIG. 5-5d. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan that is designed to facilitate the end user 5-4 to achieve 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 the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-558 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more sexual intimacy outcomes as depicted in FIG. 5-5d. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more sexual intimacy outcomes (e.g., increased sexual activities, increased sexual performance, and so forth).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-559 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more psychological outcomes as depicted in FIG. 5-5d. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more psychological outcomes (e.g., overcoming a phobia, overcoming certain addictive behavior such as compulsion to be clean, and so forth).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-560 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more intellectual or academic outcomes as depicted in FIG. 5-5d. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more intellectual or academic outcomes (e.g., passing a particular exam or class, obtaining a certain degree or academic award, being accepted into a particular program or school, attaining a particular scholarship, understanding a complex concept, acquiring particular knowledge, and so forth).

In the same or different implementations, the personalized plan developing operation 5-304 may include an operation 5-561 for developing the one or more personalized plans including at least one personalized plan that is designed to facilitate the end user to achieve one or more user states as depicted in FIG. 5-5d. For instance, the personalized plan development module 5-104 of the computing device 5-10 developing the one or more personalized plans 5-16 including at least one personalized plan 5-16 that is designed to facilitate the end user 5-4 to achieve one or more user states (e.g., subjective user states such as subjective mental, physical, and/or overall states, marital states, occupational states, physical states, availability states, social states, spiritual or faith-based states, academic states, and so forth).

Referring to FIG. 5-6 illustrating another operational flow 5-600 in accordance with various embodiments. Operational flow 5-600 includes certain operations that mirror the operations included in the operational flow 5-300 of FIG. 5-3. These operations include a relevant reported aspect acquiring operation 5-602 and a personalized plan developing operation 5-604 that corresponds to and mirror the relevant reported aspect acquiring operation 5-302 and the personalized plan developing operation 5-304, respectively, of FIG. 5-3.

In addition, operational flow 5-300 includes a personalized plan presenting operation 5-606 for presenting the one or more personalized plans as depicted in FIG. 5-6. For instance, the presentation module 5-106 of the computing device 5-10 presenting (e.g., transmitting via the wireless network and/or wired network 5-50 or indicating via a user interface 5-120) the one or more personalized plans 5-16.

In various alternative implementations, the personalized plan presenting operation 5-606 may include one or more additional operations. For example, in some implementations, the personalized plan presenting operation 5-606 may include an operation 5-763 for transmitting the one or more personalized plans via at least one of wireless network and a wired network as depicted in FIG. 5-7. For instance, the transmission module 5-224 of the computing device 5-10 transmitting the one or more personalized plans 5-16 via at least one of wireless network and a wired network 5-50.

In the same or different implementations, the personalized plan presenting operation 5-606 may include an operation 5-764 for indicating the one or more personalized plans via a user interface as depicted in FIG. 5-7. For instance, the user interface indication module 5-226 of the computing device 5-10 audibly and/or visually indicating the one or more personalized plans 5-16 via a user interface 5-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 personalized plan presenting operation 5-606 may include an operation 5-765 for presenting the one or more personalized plans to the end user as depicted in FIG. 5-7. For instance, the presentation module 5-106 of the computing device 5-10 presenting the one or more personalized plans 5-16 to the end user 5-4.

In the same or different implementations, the personalized plan presenting operation 5-606 may include an operation 5-766 for presenting the one or more personalized plans to at least one of a third party, a source user, and a network server as depicted in FIG. 5-7. For instance, the presentation module 5-106 of the computing device 5-10 presenting the one or more personalized plans 5-16 to at least one of a third party 5-6, a source user 5-2*, and a network server 5-60.

Turning now to FIG. 5-8, which is a high-level block diagram illustrating another perspective of the computing device 5-10 of FIG. 5-1b. As illustrated, the computing device 5-10 may include a processor 5-802 (e.g., microprocessor, controller, and so forth) coupled to storage medium 5-806 (e.g., volatile or non-volatile memory). The storage medium 5-806 may store computer readable instructions 5-804 (e.g., computer program product). The processor 5-802, in various implementations, may execute the computer readable instructions 5-804 in order to execute one or more operations described above and as illustrated in FIGS. 5-3, 5-4a, 5-4b, 5-4c, 5-4d, 5-4e, 5-4f, 5-4g, 5-4h, 5-5a, 5-5b, 5-5c, 5-5d, 5-6, and 5-7.

For example, the processor 5-802 may execute the computer readable instructions 5-804 in order to acquire one or more relevant reported aspects associated with one or more source users 5-2 that are relevant to achieving one or more target outcomes, the acquiring 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/or to develop one or more personalized plans 5-16 designed to facilitate an end user 5-4 to achieve the one or more target outcomes when one or more emulatable aspects indicated by the one or more personalized plans 5-16 are emulated, the development of the one or more personalized plans 5-16 being based, at least in part, on the acquiring of the one or more relevant reported aspects as depicted by the operational flow 5-300 of FIG. 5-3 and by the operational flow 5-600 of FIG. 5-6.

VII. Identification and Provision of Reported Aspects that Are Relevant with Respect to Achievement of Target Outcomes

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 journal. One place where such open journals 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, 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 become very popular in recent times 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 journals 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. Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, sensor data, and so forth) are now available through these 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 sites making it even more difficult to exploit such potentially useful data.

In various embodiments, methods, systems, circuitry, and computer program products are provided for providing one or more reported aspects of one or more users that are relevant for achieving one or more target outcomes. More particularly, the methods, systems, circuitry, and computer program products may be designed to identify selectively, 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 selective 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.

Based on the identification of the one or more relevant reported aspects, the one or more identified relevant reported aspects may then be provided. In some cases, the providing of the one or more relevant reported aspects may involve transmission of, displaying of, allowing access to, and/or distribution of such data to one or more computing/communication devices such as network devices. In various embodiments, the methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, a network device such as a server (e.g., network servers) or a local client device.

In various embodiments, the one or more relevant reported aspects that are provided by the methods, systems, circuitry, and computer program products may be used directly by an end user in order to achieve the one or more target outcomes when the one or more relevant reported aspects are emulated by the end user. Alternatively, the one or more relevant reported aspects that are provided may be used in order to develop one or more templates and/or one or more personalized plans, which may then be used by an end user in order to achieve the one or more target outcomes. A “template” is a generic plan designed to facilitate the achievement of one or more target outcomes when one or more emulatable aspects included in the template are emulated. The one or more emulatable aspects that may be included in the template may correspond to the one or more relevant reported aspects that were provided and that are relevant for achieving the one or more target outcomes.

In contrast, a “personalized plan” may merely be a template that has personalized for a particular end user. For example, by taking a generic template and modifying the generic template (e.g., modifying or replacing the emulatable aspects that may be included in the generic template) such that the modified generic template (e.g., personalized plan) meets or satisfies logistical or physical limitations of the end user. An example of a personalized plan (or a template) is a personalized plan (or a template) that was developed based on relevant reported aspects of a source user that facilitates an end user to achieve a desired outcome such as weight loss or getting a high score on the scholastic aptitude test (SAT).

Such a personalized plan (or template) may be embodied by a schedule of activities (e.g., emulatable aspects) that an end user may need to emulate in order to achieve the target outcome. For example, if the personalized plan is designed to facilitate an end user to lose 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) the end user may need to execute in order to achieve the weight loss. Similarly, if the personalized plan is designed to facilitate an end user to achieve a high score for the SAT, the personalized plan 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) the end user may need to execute in order to achieve the high test score for the SAT.

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 is now provided. In brief, and as will be further described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, 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, 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 sensing devices. Note that in some cases, a template or a personalized plan does not have to be a schedule of activities, but may merely be a collection of one or more emulatable aspects. For example, a template may be developed (based on relevant reported aspects) for achieving lower blood pressure that may indicate a single emulatable aspect (e.g., be spiritual or religious all the time).

A “reported aspect” may be any aspect associated with a source user that has been reported by various means (e.g., microblog entries, status reports, sensing device entries, and so forth). A “relevant reported aspect” is a reported aspect that is relevant to achieving one or more target outcomes (e.g., sought-after goals or desired outcomes). In some embodiments, what constitutes “relevant” with respect to achieving one or more target outcomes may depend on one or more “relevancy factors” that may be considered in determining, for example, whether a reported aspect is relevant to achieving one or more target outcomes as will be further described herein. Note that references in the following to “reported aspects” and “relevant reported aspects” will actually be in reference to data that indicate such information (e.g., data that indicate reported aspects and data that indicate relevant reported aspects) unless indicated otherwise.

In some embodiments, a reported aspect may have been originally reported via log entry such as a blog or microblog entry, a status report, a journal entry, a sensing device entry, or other types of entry. Such a log entry may be provided by the source user that the reported aspect is associated with, by another source user, by a third party (e.g., network service provider), or by a sensing device that can detect the aspect being reported.

A “target outcome” may be any type of desirable goal or result that may be sought by, for example, an end user. 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 who is a direct or indirect beneficiary of one or more relevant reported aspects that may be provided and that are relevant to achieving one or more target outcomes. In some cases, an end user may be a direct beneficiary of the one or more relevant reported aspects by, for example, directly using (e.g., emulating) the one or more relevant reported aspects in order to achieve the one or more target outcomes. Alternatively, an end user may be an indirect beneficiary of the one or more relevant reported aspects by being the beneficiary of a template or a personalized plan developed based on the one or more relevant reported aspects.

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. 6-1a, and 6-1b illustrating an example environment 6-100 in which the methods, systems, circuitry, and computer program products in accordance with various embodiments may be implemented by a computing device 6-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 various embodiments, the computing device 6-10 may be a server such as one of the one or more network servers 6-60 illustrated in FIG. 6-1a. Alternatively, the computing device 6-10 may be a source user device such as one of the local source user devices 6-20* illustrated in FIG. 6-1a. In still other embodiments, the computing device 6-10 may be an end user device such as one of the local end user device 6-30* illustrated in FIG. 6-1a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 6-2*” may be in reference to a source user 6-2a, a source user 6-2b, and so forth.

Note that for ease of understanding and explanation, the computing device 6-10 of the exemplary environment 6-100 of FIGS. 6-1a and 6-1b will be generally described in the following discussion as being a server (e.g., server embodiment) rather than an end user device or a source user device. Further, although the following discussion related to the exemplary environment 6-100 of FIG. 6-1a and 6-1b assumes that the computing device 6-10 is a server, the following discussion will, for the most part, be applicable even if the computing device 6-10 were an end user device (e.g., local end user device 6-30*) or a source user device (e.g., local source user device 6-20*) with certain obvious exceptions (e.g., if the computing device 6-10 is an end user device or a source user device rather than a server, the computing device 6-10 may communicate with an end user 6-4 or a source user 6-2* directly through a user interface 6-120 rather than indirectly through a wireless network and/or wired network 6-50 as may be the case when the computing device 6-10 is a server). In some embodiments, the computing device 6-10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 6-1a and 6-1b, and as previously indicated, the computing device 6-10 may be a network device such as a server (e.g., network server 6-60) that is designed to communicate with other network devices. For example, the computing device 6-10 may communicate with one or more source users 6-2*(e.g., source user 6-2a, source user 6-2b, and so forth) through one or more local source user devices 6-20*(e.g., local source user device 6-20a, local source user device 6-20b, and so forth), with one or more end users 6-4*(e.g., end user 6-4a, end user 6-4b, and so forth) through one or more local end user devices 6-30*(e.g., local end user device 6-30a, local end user device 6-30b, and so forth), with one or more sensing devices 6-40, with one or more network servers 6-60, and/or with one or more third parties 6-6 (e.g., one or more content providers, one or more network service providers, and/or one or more other parties) via a wireless network and/or wired network 6-50. In various implementations, the wireless and/or wired network 6-50 may include 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 6-50.

In various embodiments, the computing device 6-10 may be designed to, among other things, identify (e.g., selectively identify, locate, find, search, distinguish, and so forth) one or more relevant reported aspects 6-14 associated with one or more source users 6-2* that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects 6-14 being based, at least in part, on relevancy of the one or more relevant reported aspects 6-14 with respect to achieving the one or more target outcomes. The identification of the one or more relevant reported aspects 6-14 may, in some cases, be in response to reception of one or more solicitations 6-13 from one or more end users 6-4*(e.g., via one or more local end user devices 6-30*), from one or more source users 6-2*(e.g., via one or more local source user devices 6-20*), from one or more network servers 6-60, or from other parties (e.g., one or more third parties 6-6). Note that in embodiments where the computing device 6-10 is an end user device or a source user device, the one or more solicitations 6-13 may be directly received from an end user 6-4* or a source user 6-2* via a user interface 6-120.

In various embodiments, the identification of the one or more relevant reported aspects 6-14 may be by identifying the one or more relevant reported aspects 6-14 from a plurality of reported aspects 6-15, which may, in some embodiments, be stored in memory 6-116. The plurality of reported aspects 6-15 may include both relevant reported aspects 6-14 that are relevant to achieving one or more target outcomes, and non-relevant reported aspects 6-16 that are not relevant to achieving the one or more target outcomes. In some implementations, the plurality of reported aspects 6-15 may be associated with a single source user 6-2*. In other implementations, however, the plurality of reported aspects 6-15 may be associated with a plurality of source users 6-2*.

The plurality of reported aspects 6-15, which may be associated with one or more source users 6-2*, may be acquired from a variety of different sources. For example, in some implementations, one or more of the plurality of reported aspects 6-15 may be acquired from one or more local source user devices 6-20*, from one or more network servers 6-60, from one or more sensing devices 6-40, and/or one or more third parties 6-6.

Note that in embodiments where the computing device 6-10 is a source user device, one or more of the plurality of reported aspects 6-15 may be acquired directly from one or more sensing devices 6-40 or directly from a source user 6-2* via a user interface 6-120. Further, in embodiments where the computing device 6-10 is a source user device, the computing device 6-10 may include one or more integrated sensors 6-240 that may be employed in order to directly sense or detect one or more aspects associated with a source user 6-2*. As will be further described, a sensor 6-240 may be any type of sensor including, for example, sensors that can sense various physical characteristics of a source user 6-2*(e.g., heart rate sensor or blood pressure sensor), sensors that can sense activities of a source user 6-2*(e.g., a pedometer), sensors that can sense environment conditions (e.g., air quality sensors), sensors that can sense the location of a source user 6-2*(e.g., global positioning system or GPS), and so forth.

In any event, after identifying the one or more relevant reported aspects 6-14, the computing device 6-10, may be configured to, among other things, provide the one or more relevant reported aspects 6-14 to one or more entities. In this context, the providing of the one or more relevant reported aspects 6-14 may involve transmitting, via the wireless network and/or the wired network 6-50, the one or more relevant reported aspects 6-14 to one or more network entities such as local source user devices 6-20*, network servers 6-60, local end user devices 6-30*, and/or third parties 6-6. The one or more relevant reported aspects 6-14 may also be provided by displaying or indicating the one or more relevant reported aspects 6-14 through a user interface 6-120 (e.g., a display monitor and/or speakers) in embodiments where, for example, the computing device 6-10 is a source user device or an end user device.

As briefly described earlier, in some implementations, the operation to identify the one or more relevant reported aspects 6-14 by the computing device 6-10 may be in response to the computing device 6-10 receiving, via the wireless network and/or the wired network 6-50, one or more solicitations 6-13 from, for example, one or more end users 6-4*(e.g., via one or more local end user devices 6-30*), from one or more source users 6-2*(e.g., via one or more local source user devices 6-20*), from one or more network servers 6-60, or from one or more third parties 6-6 (e.g., a network service provider, a content provider, and so forth). The one or more solicitations 6-13 may be, in various implementations, one or more requests, queries, and so forth. In some embodiments, the one or more solicitations 6-13 may indicate at least one or more target outcomes. In other embodiments, however, the one or more solicitations 6-13 may indicate one or more source users 6-2* who have achieved the one or more target outcomes. In embodiments where the computing device 6-10 is a source user device or an end user device, the one or more solicitations 6-13 may be received through the user interface 6-120.

The computing device 6-10 as previously indicated may be a server (e.g., one of the one or more network servers 6-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 6-10 is a source user device (e.g., local source user device 6-20*) or an end user device (e.g., local end user device 6-30*) rather than a network server, the computing device 6-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.

With respect to the one or more sensing devices 6-40 of the exemplary environment 6-100 of FIGS. 6-1a and 6-1b, the one or more sensing devices 6-40 may communicate with the wireless network and/or the wired network 6-50 directly or indirectly via the one or more local source user devices 6-20*. As will be further described herein with respect to FIG. 6-2c, each of the one or more sensing devices 6-40 (see FIG. 6-2c) may include one or more sensors 6-240, a network interface 6-242, and/or a memory 6-244. The one or more sensors 6-240 may be designed to detect or sense one or more aspects associated with one or more source users 6-2*.

Examples of sensors 6-240 include, for example, devices that can detect physical or physiological characteristics of one or more source users 6-2*, devices that can detect activities of the one or more source users 6-2*, devices that can detect external events (e.g., environmental conditions including the weather, pollution levels, performance of the stock market, and so forth), image capturing device such as a digital camera or camcorder, and/or devices that can detect the location of the one or more source users 6-2* such as a global positioning system or GPS. Examples of devices that can detect physical or physiological characteristics include, for example, a heart rate monitor, a blood pressure sensor, a glucose sensor, and so forth. Examples of devices that can detect activities of the one or more source users 6-2* including, for example, 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.

Each of the one or more local source user devices 6-20* and each of the one or more local end user devices 6-30*(as well as the computing device 6-10 in embodiments in which the computing device 6-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 6-20* and/or the one or more local end user devices 6-30*(as well as the computing device 6-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 6-20* and/or local end user device 6-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 6-10 as illustrated in FIG. 6-1b may include a variety of modules, sub-modules, and various other components. As shown, the computing device 6-10 may include at least a relevant reported aspect identification module 6-102 (which may further include one or more sub-modules as illustrated in FIG. 6-2a) and a relevant reported aspect providing module 6-104 (which may further include one or more sub-modules as illustrated in FIG. 6-2b). In various embodiments, the computing device 6-10 may further include a memory 6-116 (which may store a plurality of reported aspects 6-15 that may further include one or more relevant reported aspects 6-14 and one or more non-relevant reported aspects 6-16, one or more end user relevancy indications 6-142, one or more source user relevancy indications 6-144, one or more third party source relevancy indications 6-145, one or more predefined time increment indications 6-146, and/or one or more applications 6-140), a network interface 6-118 (e.g., network interface card or NIC), a user interface 6-120, a social networking entry reception module 6-110 (which may further include a blog entry reception module 6-111 and/or a status report reception module 6-112), a journal entry reception module 6-114, a sensor data reception module 6-115, and/or a solicitation reception module 6-122 that is designed to receive one or more solicitations 6-13 via, for example, a wireless network and/or wired network 6-50 or via user interface 6-120. In embodiments where the computing device 6-10 is a source user device, the computing device 6-10 may include one or more integrated sensors 6-240 that are designed to sense or detect one or more aspects associated with one or more source users 6-2*.

Referring to the relevant reported aspect identification module 6-102, the relevant reported aspect identification module 6-102 may be configured to, among other things, identify one or more relevant reported aspects 6-14 based, at least in part, on relevancy of the one or more relevant reported aspects 6-14 with respect to achievement of one or more target outcomes, the one or more relevant reported aspects 6-14 to be identified being associated with one or more source users 6-2* and being relevant to achieving the one or more target outcomes, and the identification of the one or more relevant reported aspects being in response to reception of one or more solicitations 6-13. In contrast, the relevant reported aspect providing module 6-104 may be configured to, among other things, provide the identified one or more relevant reported aspects 6-14.

The memory 6-116 may be designed to store various data including a plurality of reported aspects 6-15 associated with one or more source user 6-2*. The plurality of reported aspects 6-15 stored in the memory 6-116 may include both relevant reported aspects 6-14 that are relevant to achieving one or more target outcomes and non-relevant reported aspects 6-16 that may not be relevant to achieving any of the one or more target outcomes. Other types of data may be stored in the memory 6-116 in various implementations including, for example, one or more end user relevancy indications 6-142 (e.g., one or more indications that indicate the types of reported aspects that an end user 6-4 has an interest in or believes is relevant to achieving one or more target outcomes) and/or one or more source user relevancy indications 6-144 (e.g., one or more indications provided by a source user 6-2* that indicate at least which types of reported aspects are relevant to achieving one or more target outcomes).

In some cases, the memory 6-116 may also include, for example, one or more third party source relevancy indications 6-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 6-6 that indicate at least which types of reported aspects are relevant to achieving one or more target outcomes), one or more predefined time increment indications 6-146 (e.g., one or more indications that indicate at least one time increment, such as a time interval or window, that may be considered in order to determine whether, for example, a reported aspect is relevant for achieving a target outcome if the reported aspect indicate an aspect that occurred within the time increment from an occurrence of the target outcome as successfully achieved by, for example, a source user 6-2*), and/or one or more applications 6-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). In various implementations, the memory 6-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 social networking entry reception module 6-110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 6-2*, from one or more end users 6-4*, from one or more third parties 6-6, from one or more sensing devices 6-40, and/or from one or more network servers 6-60. The social networking entry reception module 6-110 may further include a blog entry reception module 6-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 6-112 for receiving social networking status reports. The journal entry reception module 6-114 may be configured to receive journal entries from, for example, one or more source users 6-2*, one or more end users 6-4*, and/or one or more third parties 6-6 (e.g., a non-user). The sensor data reception module 6-115 may be configured to receive sensing data that indicate one or more reported aspects 6-15 associated with one or more source users 6-2* from one or more sensing devices 6-40 or one or more integrated sensors 6-240. The user interface 6-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. 6-2 a illustrates particular implementations of the relevant reported aspect identification module 6-102 of the computing device 6-10 of FIG. 6-1b. As illustrated, the relevant reported aspect identification module 6-102 may include, in various implementations, one or more sub-modules. For example, in some implementations, the relevant reported aspect identification module 6-102 may include a source user associated reported aspect identification module 6-202 that is configured to identify the one or more relevant reported aspects 6-14 that are associated with one or more source users 6-2* and that are relevant to achieving the one or more target outcomes by at least identifying one or more reported aspects 6-15 that are associated with the one or more source users 6-2*, the one or more source users 6-2* having achieved the one or more target outcomes.

The source user associated reported aspect identification module 6-202 may further include a target outcome corresponding reported aspect identification module 6-204 and/or an associated source user determination module 6-206. The target outcome corresponding reported aspect identification module 6-204 may be configured to identify the one or more relevant reported aspects 6-14 by at least identifying one or more reported aspects 6-15 that correspond to the one or more target outcomes. In contrast, the associated source user determination module 6-206 may be configured to determine one or more source users 6-2* who are associated with the one or more reported aspects 6-15 that correspond to the one or more target outcomes. In doing so, the one or more source users 6-2* who have achieved the one or more target outcomes may be identified or determined. Based on the determination of the one or more source users 6-2* who have achieved the one or more target outcomes, the relevant reported aspect identification module 6-102 may identify one or more reported aspects 6-15 that are associated with the one or more source users 6-2* who have achieved the target outcomes.

In some implementations, the relevant reported aspect identification module 6-102 may include a relevancy factor relevant reported aspect identification module 6-208 and/or a log entry originated relevant reported aspect identification module 6-212. In brief, the relevancy factor relevant reported aspect identification module 6-208 may be configured to identify one or more reported aspects 6-14 that are relevant for achieving one or more target outcomes with respect to one or more relevancy factors (e.g., the one or more reported aspects 6-14 belonging to a type or types of aspects that are of interest to an end user 6-4*). In contrast, the log entry originated relevant reported aspect identification module 6-212 may be configured to identify the one or more relevant reported aspects 6-14 by identifying one or more reported aspects 6-15 that were originally reported through log entries (e.g., microblog entries, status reports, and so forth).

FIG. 6-2 b illustrates particular implementations of the relevant reported aspect providing module 6-104 of FIG. 6-1b. The relevant reported aspect providing module 6-104, as illustrated, may include one or more sub-modules. For example, in various implementations, the relevant reported aspect providing module 6-104 may include a network transmission module 6-220 that is configured to transmit the one or more relevant reported aspects 6-14 via a wireless network and/or a wired network 6-50 (e.g., via at least one of a wireless network and a wired network 6-50). In some implementations, the network transmission module 6-220 may further include a network device transmission module 6-222 configured to transmit the one or more relevant reported aspects 6-14 to one or more network devices (e.g., network servers 6-60, local source user devices 6-20*, local end user devices 6-30, and/or other network devices).

In various implementations, the relevant reported aspect providing module 6-104 may include a link indication providing module 6-224 that is configured to provide one or more indications that links (e.g., associates) two or more relevant reported aspects 6-14 together. In some implementations, development of a template or a personalized plan designed to achieve one or more target outcomes and that is developed based on the two or more relevant reported aspects 6-14 may be facilitated by indicating the link between the two or more relevant reported aspects 6-14. In some cases, the link indication providing module 6-224 may further include a relationship indication providing module 6-226 configured to provide one or more indications that indicate one or more relationships (e.g., temporal, specific time, or spatial relationships) between the two or more relevant reported aspects 6-14. Such indications may also be useful in order to, for example, develop a template or a personalized plan designed to achieve one or more target outcomes. In particular, by providing the one or more indications of the one or more relationships between the two or more relevant reported aspects 6-14, the development of a template or a personalized plan (e.g., a template or personalized plan that may be embodied by, for example, a schedule of emulatable aspects) designed to achieve one or more target outcomes may be better facilitated (e.g., providing a basis for the relationships between the emulatable aspects that may be included in the template or the personalized plan).

Referring now to FIG. 6-2c illustrating one of the sensing devices 6-40 of FIGS. 6-1a and 6-1b. The sensing device 6-40, in various implementations, may include at least one or more sensors 6-240. The one or more sensors 6-240 that may be included in a sensing device 6-40 (as well as the computing device 6-10) may be designed to sense or detect one or more aspects associated with one or more source users 6-2*. For example, in various implementations, the one or more sensors 6-240 may include one or more devices that can monitor a user's physiological characteristics such as blood pressure sensors, heart rate monitors, glucometers (e.g., blood glucose meter), and so forth.

In some implementations, the one or more sensors 6-240 may include devices that can detect activities of a user (e.g., a source user 6-2*). Examples of such devices include, for example, 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 6-240 may also include, in various implementations, 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 6-2*, global positioning system (GPS) to provide location data related to a user (e.g., locations of the source user 6-2*), and so forth. In various implementations, a sensing device 6-40 may further include a network interface 6-242 and/or a memory 6-244. The network interface 6-242 may be designed to interface with a wireless network and/or a wired network 6-50 while the memory 6-244 may be designed to store, for example, sensing data provided by the one or more sensors 6-240.

Referring back to the computing device 6-10 of FIG. 6-1b, the various modules (e.g., the relevant reported aspect identification module 6-102, the relevant reported aspect providing module 6-104, and so forth) along with their sub-modules included in the computing device 6-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the relevant reported aspect identification module 6-102 and/or the relevant reported aspect providing module 6-104 may be implemented with a processor 6-602 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 6-604 (e.g., computer program product) stored in a storage medium 6-606 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 6-10 of FIG. 6-6. 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 computing device 6-10 of FIG. 6-1b will now be provided with respect to the processes and operations to be described herein. FIG. 6-3 illustrates an operational flow 6-300 representing example operations related to, among other things, identification (e.g., selective identification) of one or more relevant reported aspects 6-14 associated with one or more source users 6-2* 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 6-14 with respect to the achievement of the one or more target outcomes, the identification being in response to reception of one or more solicitations 6-13, and the providing of the one or more relevant reported aspects 6-14 that were identified.

In FIG. 6-3 and in the following figures that include various examples of operational flows, discussions and explanations may be provided with respect to the exemplary environment 6-100 described above as illustrated in FIGS. 6-1a and 6-1b, and/or with respect to other examples (e.g., as provided in FIGS. 6-2a, 6-2b, and 6-2c) 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. 6-1a, 6-1b, 6-2a, 6-2b, and 6-2c. 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. 6-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 6-300 may move to a relevant reported aspect identifying operation 6-302 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. For instance, and as an illustration, the relevant reported aspect identification module 6-102 of the computing device 6-10 of FIG. 6-1b identifying (e.g., finding, locating, searching, distinguishing, and so forth), in response to reception of one or more solicitations 6-13 (e.g., requests, queries, commands, and so forth), one or more relevant reported aspects 6-14 associated with one or more source users 6-2* that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects 6-14 being based, at least in part, on relevancy of the one or more relevant reported aspects 6-14 with respect to achieving the one or more target outcomes.

Note that in various implementations, the one or more solicitations 6-13 to be received may be for soliciting the one or more relevant reported aspects 6-14. Alternatively, the one or more solicitations 6-13 may be for soliciting data for developing one or more personalized plans or templates that may be designed to facilitate an end user 6-4* to achieve the one or more target outcomes. In other implementations, the one or more solicitations 6-13 may be for soliciting other types of data.

In addition to the relevant reported aspect identifying operation 6-302, operational flow 6-300 may also include a relevant reported aspect providing operation 6-304 for providing the one or more relevant reported aspects. For instance, the relevant reported aspect providing module 6-104 of the computing device 6-10 providing (e.g., transmitting, indicating, displaying, allowing access to, and so forth) the one or more relevant reported aspects 6-14. As will be further described herein, the relevant reported aspect identifying operation 6-302 as well as the relevant reported aspect providing operation 6-304 may be implemented in a number of different ways in various alternative implementations.

For example, FIGS. 6-4a, 6-4b, 6-4c, 6-4d, 6-4e, 6-4f, 6-4g, and 6-4h illustrate the various ways that the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may be implemented in various alternative implementations. In some implementations, for example, the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may include an operation 6-402 for identifying, in response to the reception of the one or more solicitations, the one or more relevant reported aspects from a plurality of reported aspects as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 of FIG. 6-1b identifying, in response to receiving the one or more solicitations 6-13 (e.g., as received by the solicitation reception module 6-122), the one or more relevant reported aspects 6-14 from a plurality of reported aspects 6-15.

In some implementations, operation 6-402 may further include an operation 6-403 for identifying, in response to the reception of the one or more solicitations, the one or more relevant reported aspects from a plurality of reported aspects that include one or more reported aspects that are relevant to achieving the one or more target outcomes and one or more reported aspects that are not relevant to achieving the one or more target outcomes as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying, in response to receiving the one or more solicitations 6-13, the one or more relevant reported aspects 6-14 from a plurality of reported aspects 6-15 that include one or more reported aspects that are relevant to achieving the one or more target outcomes (e.g., one or more relevant reported aspects 6-14) and one or more reported aspects 6-16 that are not relevant to achieving the one or more target outcomes.

In the same or different implementations, the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may include an operation 6-404 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more source users, the one or more source users having achieved the one or more target outcomes as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception of one or more solicitations 6-13 that indicate the one or more source users 6-2*, the one or more source users 6-2* having achieved the one or more target outcomes.

In the same or different implementations, the relevant reported aspect identifying operation 6-302 may include an operation 6-405 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes.

In various implementations, operation 6-405 may include one or more additional operations. For example, in some implementations, operation 6-405 may include an operation 6-406 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes and that do not indicate any of the one or more source users as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes and that do not indicate any of the one or more source users 6-2*.

In the same or different implementations, operation 6-405 may include an operation 6-407 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes and that indicate one or more relevancy factors as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes and that indicate one or more relevancy factors (e.g., bases for determining whether a reported aspect is relevant to achieving one or more target outcomes).

Operation 6-407 in turn may further include an operation 6-408 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes and that indicate one or more aspect types that are of interest to one or more end users, the one or more end users being beneficiaries of the providing of the one or more relevant reported aspects as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes and that indicate one or more aspect types (e.g., dietary activities, sleep or rest activities, reading activities, user locations, mental states, and so forth) that are of interest to one or more end users 6-4*, the one or more end users 6-4* being beneficiaries of the providing of the one or more relevant reported aspects 6-14.

In the same or different implementations, operation 6-407 may include an operation 6-409 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes and that indicate one or more aspect types indicated by at least one source user as being relevant to the achievement of the one or more target outcomes as depicted in FIG. 6-4a. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes and that indicate one or more aspect types (e.g., exercise activities, medication usage, mental attitudes, social or employment activities, and so forth) indicated by at least one source user 6-2* as being relevant to the achievement of the one or more target outcomes (e.g., losing weight, feeling more alert, reduce pain, increase sexual intimacy activities, and so forth).

In the same or different implementations, operation 6-407 may include an operation 6-410 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes and that indicate one or more aspect types 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. 6-4b. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes and that indicate one or more aspect types indicated by at least one third party source 6-6 as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 6-407 may include an operation 6-411 for identifying the one or more relevant reported aspects in response to reception of one or more solicitations that indicate the one or more target outcomes and that indicate one or more predefined time increments, the one or more predefined time increments to be considered in order to determine relevancy of one or more reported aspects with respect to achieving the one or more target outcomes as depicted in FIG. 6-4b. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception (e.g., reception by the solicitation module 6-122) of one or more solicitations 6-13 that indicate the one or more target outcomes and that indicate one or more predefined time increments, the one or more predefined time increments (e.g., one day, one week, three months, one year, five years, and so forth) to be considered in order to determine relevancy of one or more reported aspects 6-15 with respect to achieving the one or more target outcomes. For example, such predefined time periods may be used in order to eliminate from consideration those reported aspects 6-15 that are associated with one or more source users 6-2* who have achieved the one or more target outcomes but indicate aspects that occurred remotely from the accomplishment of the one or more target outcomes by the one or more source users 6-2*.

In various implementations, the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may include an operation 6-412 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that are relevant for achieving the one or more target outcomes from a plurality of reported aspects stored in memory as depicted in FIG. 6-4b. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by at least identifying one or more reported aspects (e.g., relevant reported aspects 6-14) that are relevant for achieving the one or more target outcomes from a plurality of reported aspects 6-15 stored in memory 6-116.

In order to identify relevant reported aspects 6-14 of one or more source users 6-2* that are relevant for achieving one or more target outcomes from, for example, a plurality of reported aspects 6-15, the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may include one or more operations to identify one or more source users 6-2* who have been reported as having successfully achieved the one or more target outcomes. For example, in some implementations, the relevant reported aspect identifying operation 6-302 may include an operation 6-413 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that are associated with the one or more source users, the one or more source users having achieved the one or more target outcomes as depicted in FIG. 6-4c. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by having the source user associated reported aspect identification module 6-202 (see FIG. 6-2a) at least identify one or more reported aspects 6-15 that are associated with the one or more source users 6-2*, the one or more source users 6-2* having achieved the one or more target outcomes.

In order to identify the one or more reported aspects 6-15 that are associated with the one or more source users 6-2* who have achieved the one or more target outcomes, operation 6-413 may include an operation to identify those reported aspects 6-15 that corresponds to the one or more target outcomes. For example, in some implementations, operation 6-413 may include an operation 6-414 for identifying the one or more relevant reported aspects by at least identifying one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 6-4c. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by having the target outcome corresponding reported aspect identification module 6-204 (see FIG. 6-2a) at least identify one or more reported aspects 6-15 that correspond (e.g., equivalent or substantially equivalent) to the one or more target outcomes.

In order to identify the one or more relevant reported aspects 6-14, operation 6-414 may include an operation 6-415 for determining one or more source users who are associated with the one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 6-4c. For instance, the associated source user determination module 6-206 (see FIG. 6-2a) of the computing device 6-10 determining one or more source users 6-2* who are associated with the one or more reported aspects 6-15 that correspond (e.g., equivalent or substantially equivalent) to the one or more target outcomes.

In some implementations, in order to identify the one or more relevant reported aspects 6-14 operation 6-415 may include at least an operation 6-416 for identifying one or more reported aspects that are associated with the one or more source users determined to be associated with the one or more reported aspects that corresponds to the one or more target outcomes as depicted in FIG. 6-4c. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying one or more reported aspects 6-15 that are associated with the one or more source users 6-2* determined to be associated with the one or more reported aspects 6-15 that corresponds to the one or more target outcomes.

In various implementations, operation 6-416 may include an operation 6-417 for identifying, from the one or more reported aspects that are associated with the one or more source users determined to be associated with the one or more reported aspects that correspond to the one or more target outcomes, one or more reported aspects that are relevant with respect to one or more relevancy factors as depicted in FIG. 6-4c. For instance, the relevancy factor relevant reported aspect identification module 6-208 (see FIG. 6-2a) of the computing device 6-10 identifying, from the one or more reported aspects 6-15 that are associated with the one or more source users 6-2* determined to be associated with the one or more reported aspects 6-15 that correspond to the one or more target outcomes, one or more reported aspects 6-15 that are relevant with respect to one or more relevancy factors. Examples of relevancy factors include, for example, identifying reported aspects 6-15 that are associated with specific source users 6-2* such as those source users 6-2* who have achieved the one or more target outcomes and who share certain common traits (e.g., ethnicity, religious beliefs, mental or physical handicaps, common social or employment networking groups, common health or medical states, and so forth) with an end user 6-4*).

The one or more relevancy factors considered in operation 6-417 may be provided by a variety of sources. For example, in some implementations, operation 6-417 may include an operation 6-418 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that belong to one or more aspect types that are of interest to an end user, the end user being a beneficiary of the one or more relevant reported aspects to be provided as depicted in FIG. 6-4c. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more reported aspects 6-15 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that belong to one or more aspect types (e.g., dietary behaviors, exercise behavior, reported aspects 6-14 associated with source users 6-2* who share a common trait with the end user 6-4*, and so forth) that are of interest to an end user 6-4*, the end user 6-4* being a beneficiary (e.g., recipient of the one or more relevant reported aspects 6-14 or a product, such as a personalized plan or a template, that may be generated from the one or more relevant reported aspects 6-14) of the one or more relevant reported aspects to be provided.

In the same or different implementations, operation 6-417 may include an operation 6-419 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 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. 6-4c. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 6-15 that belong to one or more aspect types (e.g., mental states, attitudes, spiritual or religious beliefs, conduct, and so forth) that have been indicated by at least one source user 6-2* as being relevant to the achievement of the one or more target outcomes (e.g., reduced blood pressure or reduced stress).

In the same or different implementations, operation 6-417 may include an operation 6-420 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 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. 6-4c. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more reported aspects 6-15 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that belong to one or more aspect types (e.g., sleep activities, dietary habits, exercise activities) that have been indicated by at least one third party source as being relevant to the achievement of the one or more target outcomes (e.g., weight loss).

In the same or different implementations, operation 6-417 may include an operation 6-421 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that indicate one or more aspects that occurred within one or more predefined time increments, respectively, from one or more occurrences of the one or more reported aspects that correspond to the one or more target outcomes as depicted in FIG. 6-4d. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more reported aspects 6-15 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 6-15 that indicate one or more aspects that occurred within one or more predefined time increments (e.g., one day, one week, three months, one year, five years, and so forth), respectively, from one or more occurrences of the one or more reported aspects 6-15 that correspond to the one or more target outcomes.

That is, not all relevant reported aspects 6-14 that may be relevant with respect to certain relevancy factors may actually be relevant to achieving the one or more target outcomes if the relevant reported aspects 6-14 indicate aspects that, time-wise, occurred remotely from occurrence of the one or more target outcomes as successfully achieved by the one or more source users 6-2* who have been reported as achieving the one or more target outcomes. For example, reported aspects 6-15 that are associated with source users 6-2* who have achieved the one or more target outcomes and that are relevant based on certain relevancy factors (e.g., belong to a type of aspect that is of interest to the end user 6-4* such as dietary behavior) may, nevertheless, not be relevant to achieving the one or more target outcomes if they occurred well before (or well after) the achievement of the one or more target outcomes (e.g., 20 pounds of weight loss as indicated by one or more reported aspects 6-15 that corresponds to the one or more target outcomes) by the one or more source users 6-2*.

Thus, a reported aspect 6-15 may, in some cases, be relevant to the achievement of the one or more target outcomes only if it falls within some time increment (e.g., “predefined time increment”) from the one or more occurrences of the one or more reported aspects 6-15 that correspond to the one or more target outcomes. The length of the predefined time increments to be considered in determining relevancy may depend on a number of factors including how the relevant reported aspects 6-14 may be used (e.g., to develop personalized plans for achieving target outcomes). The predefined time increments, in various implementations, may be provided by an end user 6-4*, by a source user 6-2*, or by a third party source (e.g., third party 6-6).

In various implementations, operation 6-421 may, in turn, include an operation 6-422 for identifying the one or more reported aspects that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects that indicate 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 aspects that correspond to the one or more target outcomes as depicted by FIG. 6-4d. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more reported aspects 6-15 that are relevant with respect to one or more relevancy factors by identifying one or more reported aspects 6-15 that indicate 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 aspects that correspond to the one or more target outcomes.

In some implementations, the relevant reported aspect identifying operation 6-302 may include an operation 6-423 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that are relevant to achieving the one or more target outcomes based on one or more relevancy factors as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that are relevant to achieving the one or more target outcomes based on one or more relevancy factors (e.g., relevancy factors as provided by an end user 6-4*, by a source user 6-2*, or by a third party source).

In various implementations, operation 6-423 may include an operation 6-424 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who share one or more common traits with an end user, the end user being a beneficiary of the one or more relevant reported aspects to be provided as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who share one or more common traits with an end user 6-4*, the end user 6-4* being a beneficiary of the one or more relevant reported aspects 6-14 to be provided. For these implementations, the end user 6-4* may be a beneficiary as a result of the end user 6-4* being the recipient of the one or more relevant reported aspects 6-14 or recipient of, for example, a personalized plan or template for achieving the one or more target outcomes and that was developed based on the one or more relevant reported aspects 6-14.

The one or more source users 6-2* who share one or more common traits with the end user 6-4* may have a variety of traits that may be shared with the end user 6-4* and which may be considered in identifying relevant reported aspects 6-14 in various implementations. For example, in some implementations, operation 6-424 may include an operation 6-425 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are members of one or more social networking groups that are associated with the end user as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are members of one or more social networking groups that are associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-426 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are members of one or more ethnic or religious groups that are associated with the end user as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are members of one or more ethnic or religious groups (e.g., Hispanic, German, Asian, Christian, Buddhist, and so forth) that are associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-427 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are members of at least one of a gender and an age group that is associated with the end user as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are members of at least one of a gender (e.g., female) and an age (e.g., over 65 years of age) group that is associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-428 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who have one or more physical or mental handicaps that are associated with the end user as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who have one or more physical or mental handicaps (e.g., missing a limb, blindness, phobias, bipolar, and so forth) that are associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-429 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are associated with one or more health or medical states that are further associated with the end user as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are associated with one or more health or medical states (e.g., having cancer, a tobacco user, high blood pressure, and so forth) that are further associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-430 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are associated with one or more intellectual or academic states that are further associated with the end user as depicted in FIG. 6-4e. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are associated with one or more intellectual or academic states that are further associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-431 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are associated with one or more social states that are further associated with the end user as depicted in FIG. 6-4f. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are associated with one or more social states (e.g., unmarried) that are further associated with the end user 6-4*.

In the same or different implementations, operation 6-424 may include an operation 6-432 for identifying the one or more relevant reported aspects including identifying one or more reported aspects associated with one or more source users who are associated with one or more spiritual, political, or social beliefs that are further associated with the end user as depicted in FIG. 6-4f. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 associated with one or more source users 6-2* who are associated with one or more spiritual, political, or social beliefs that are further associated with the end user 6-4*.

In various implementations, other types of relevancy factors may be considered in identifying the one or more relevant reported aspects 6-14 other than relevancy factors that relate to common traits of an end user 6-4* as was the case in operation 6-424. For example, in some implementations, operation 6-423 for identifying the one or more relevant reported aspects 6-14 based on one or more relevancy factors may include an operation 6-433 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more behavior incidences associated with the one or more source users as depicted in FIG. 6-4f. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more behavior incidences (e.g., exercise or sleep activities) associated with the one or more source users 6-2*.

Operation 6-433 may further include, in various implementations, an operation 6-434 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more incidences of activities executed by the one or more source users as depicted in FIG. 6-4f. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more incidences of activities (e.g., dietary activities, social or employment activities, leisure activities, and so forth) executed by the one or more source users 6-2*.

In the same or different implementations, operation 6-433 may include an operation 6-435 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more user attitudes or conduct associated with the one or more source users as depicted in FIG. 6-4f. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more user attitudes or conduct (e.g., mannerisms, outlook, approach, demeanor, and so forth) associated with the one or more source users 6-2*.

In some implementations, operation 6-423 may include an operation 6-436 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more incidences of one or more user beliefs associated with the one or more source users as depicted in FIG. 6-4g. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more incidences of one or more user beliefs (e.g., spiritual or religious beliefs, superstitious beliefs, dietary beliefs, and so forth) associated with the one or more source users 6-2*.

In the same or different implementations, operation 6-423 may include an operation 6-437 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more incidences of one or more subjective user states associated with the one or more source users as depicted in FIG. 6-4g. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more incidences of one or more subjective user states associated with the one or more source users 6-2*.

A subjective user state may be any state or status associated with a source user 6-2* that can typically only be indicated by the source user 6-2*. Examples of subjective user states include, for example, subjective user mental states (e.g., sadness, happiness, mental exhaustion, alertness, and so forth), subjective user physical states (e.g., sore back, blurred vision, overall physical exhaustion, and so forth), and subjective user overall states (e.g., any other subjective user states that are neither a subjective user mental state or a subjective user physical state including, for example, “feeling good,” “feeling bad,” “feeling alive,” and so forth).

In the same or different implementations, operation 6-423 may include an operation 6-438 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 6-4g. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more incidences of one or more user physical characteristics (e.g., hair color, skin color, overall physical shape, and so forth) associated with the one or more source users 6-2*.

In the same or different implementations, operation 6-423 may include an operation 6-439 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more incidences of one or more user locations associated with the one or more source users as depicted in FIG. 6-4g. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more incidences of one or more user locations (e.g., workplace, home, school, and so forth) associated with the one or more source users 6-2*.

In the same or different implementations, operation 6-423 may include an operation 6-440 for identifying the one or more relevant reported aspects including identifying one or more reported aspects that indicate one or more incidences of external events associated with the one or more source users as depicted in FIG. 6-4g. For instance, the relevancy factor relevant reported aspect identification module 6-208 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including identifying one or more reported aspects 6-15 that indicate one or more incidences of external events (e.g., local weather, performance of a stock that is of interest to a source user 6-2*, and so forth) associated with the one or more source users 6-2*.

The relevant reported aspects identified through the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may have been originally reported through various alternative means. For example, in some implementations, the relevant reported aspect identifying operation 6-302 may include an operation 6-441 for identifying the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported through log entries as depicted in FIG. 6-4h. For instance, the log entry originated relevant reported aspect identification module 6-212 (see FIG. 6-2a) of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by identifying one or more reported aspects 6-15 that were originally reported through log entries (e.g., electronic entries that are continuously, regularly, semi-regularly, or randomly entered).

In various implementations, operation 6-441 may include one or more additional operations. For example, in some implementations, operation 6-441 may include an operation 6-442 identifying the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported through blog entries as depicted in FIG. 6-4h. For instance, the log entry originated relevant reported aspect identification module 6-212 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by identifying one or more reported aspects 6-15 that were originally reported through blog entries (e.g., microblog entries).

In the same or different implementations, operation 6-441 may include an operation 6-443 for identifying the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported through status reports as depicted in FIG. 6-4h. For instance, the log entry originated relevant reported aspect identification module 6-212 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by identifying one or more reported aspects 6-15 that were originally reported through status reports (e.g., social networking status reports).

In the same or different implementations, operation 6-441 may include an operation 6-444 for identifying the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported through journal entries as depicted in FIG. 6-4h. For instance, the log entry originated relevant reported aspect identification module 6-212 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by identifying one or more reported aspects that were originally reported through journal entries (e.g., diary entries).

In the same or different implementations, operation 6-441 may include an operation 6-445 for identifying the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported through sensing device entries as depicted in FIG. 6-4h. For instance, the log entry originated relevant reported aspect identification module 6-212 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 by identifying one or more reported aspects 6-14 that were originally reported through sensing device entries (e.g., as provided by one or more sensing devices 6-40 or by sensors 6-240).

In various implementations, the relevant reported aspect identifying operation 6-302 of FIG. 6-3 may include an operation 6-446 for identifying the one or more relevant reported aspects including two or more relevant reported aspects associated with two or more source users as depicted in FIG. 6-4h. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including two or more relevant reported aspects 6-14 associated with two or more source users 6-2*.

In the same or different implementations, the relevant reported aspect identifying operation 6-302 may include an operation 6-447 for identifying the one or more relevant reported aspects including one or more relevant reported aspects indicating one or more intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 6-4h. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 including one or more relevant reported aspects 6-14 indicating one or more intermediate outcomes (e.g., running a mile in 10 minutes) associated with the one or more target outcomes (e.g., running a mile in 7 minutes).

In the same or different implementations, the relevant reported aspect identifying operation 6-302 may include an operation 6-448 for identifying the one or more relevant reported aspects in response to reception of the one or more solicitations via at least one of a wireless network and a wired network as depicted in FIG. 6-4h. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception of the one or more solicitations 6-13 (e.g., as received by the solicitation reception module 6-122) via at least one of a wireless network and a wired network 6-50.

In various implementations, operation 6-448 may in turn include one or more additional operations. For example, in some implementations, operation 6-448 may include an operation 6-449 for identifying the one or more relevant reported aspects in response to reception of the one or more solicitations from one or more network servers as depicted in FIG. 6-4h. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception of the one or more solicitations 6-13 from one or more network servers 6-60.

In the same or different implementations, operation 6-448 may include an operation 6-450 for identifying the one or more relevant reported aspects in response to reception of the one or more solicitations from one or more local end user devices as depicted in FIG. 6-4h. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to, for example, the solicitation reception module 6-122 receiving the one or more solicitations 6-13 from one or more local end user devices 6-30*.

In the same or different implementations, operation 6-448 may include an operation 6-451 for identifying the one or more relevant reported aspects in response to reception of the one or more solicitations from one or more local source user devices as depicted in FIG. 6-4h. For instance, the relevant reported aspect identification module 6-102 of the computing device 6-10 identifying the one or more relevant reported aspects 6-14 in response to reception of the one or more solicitations 6-13 from one or more local source user devices 6-20*.

Referring back to the relevant reported aspect providing operation 6-304 of FIG. 6-3, in various implementations, the relevant reported aspect providing operation 6-304 may include one or more additional operations. For example, in some implementations, the relevant reported aspect providing operation 6-304 may include an operation 6-552 for transmitting the one or more relevant reported aspects via at least one of a wireless network and a wired network as depicted in FIG. 6-5a. For instance, the network transmission module 6-220 (see FIG. 6-2b) of the computing device 6-10 transmitting the one or more relevant reported aspects 6-14 via at least one of a wireless network and a wired network 6-50.

In some implementations, operation 6-552 may further include an operation 6-553 for transmitting the one or more relevant reported aspects to one or more network devices as depicted in FIG. 6-5a. For instance, the network device transmission module 6-222 (see FIG. 6-2b) of the computing device 6-10 transmitting the one or more relevant reported aspects 6-14 to one or more network devices (e.g., network servers, client devices, and so forth).

Operation 6-553 may, in turn, include one or more additional operations. For example, in some implementations, operation 6-553 may include an operation 6-554 for transmitting the one or more relevant reported aspects to one or more network servers as depicted in FIG. 6-5a. For instance, the network device transmission module 6-222 of the computing device 6-10 transmitting the one or more relevant reported aspects 6-14 to one or more network servers 6-60.

In the same or different implementations, operation 6-553 may include an operation 6-555 for transmitting the one or more relevant reported aspects to one or more local end user devices as depicted in FIG. 6-5a. For instance, the network device transmission module 6-222 of the computing device 6-10 transmitting the one or more relevant reported aspects 6-14 to one or more local end user devices 6-30*.

In the same or different implementations, operation 6-553 may include an operation 6-556 for transmitting the one or more relevant reported aspects to one or more local source user devices as depicted in FIG. 6-5a. For instance, the network device transmission module 6-222 of the computing device 6-10 transmitting the one or more relevant reported aspects 6-14 to one or more local source user devices 6-20*.

In various implementations, the relevant reported aspect providing operation 6-304 of FIG. 6-3 may include an operation 6-557 for providing a plurality of relevant reported aspects as depicted in FIG. 6-5b. For instance, the relevant reported aspect providing module 6-104 of the computing device 6-10 providing a plurality of relevant reported aspects 6-14 (e.g., providing two or more relevant reported aspects 6-14 via user interface 6-120 and/or via network interface 6-118).

Operation 6-557 may, in turn, include an operation 6-558 for providing one or more indications that link together two or more of the relevant reported aspects as depicted in FIG. 6-5b. For instance, the link indication providing module 6-224 (see FIG. 6-2b) of the computing device 6-10 providing one or more indications that link together two or more of the relevant reported aspects 6-14. For example, each of the two or more relevant reported aspects 6-14 may be provided with attributes that indicate that each of the two or more relevant reported aspects 6-14 are associated with the same source user 6-2*.

Thus, in some implementations, operation 6-558 may further include an operation 6-559 for providing the one or more indications that link together two or more of the relevant reported aspects by providing one or more indications that indicate that each of the two or more of the relevant reported aspects is associated with a common source user as depicted in FIG. 6-5b. For instance, the link indication providing module 6-224 (see FIG. 6-2b) of the computing device 6-10 providing the one or more indications that link together two or more of the relevant reported aspects 6-14 by providing one or more indications that indicate that each of the two or more of the relevant reported aspects 6-14 is associated with a common source user 6-2*.

In the same or different implementations, operation 6-558 may further include an operation 6-560 for providing one or more indications that indicate one or more temporal relationships between the two or more of the relevant reported aspects as depicted in FIG. 6-5b. For instance, the relationship indication providing module 6-226 (see FIG. 6-2b) of the computing device 6-10 providing one or more indications that indicate one or more temporal relationships between the two or more of the relevant reported aspects 6-14.

In the same or different implementations, operation 6-558 may further include an operation 6-561 for providing one or more indications that indicate one or more specific time relationships between the two or more of the relevant reported aspects as depicted in FIG. 6-5b. For instance, the relationship indication providing module 6-226 of the computing device 6-10 providing one or more indications that indicate one or more specific time relationships between the two or more of the relevant reported aspects 6-14.

In the same or different implementations, operation 6-558 may further include an operation 6-562 for providing one or more indications that indicate one or more spatial relationships between the two or more of the relevant reported aspects as depicted in FIG. 6-5b. For instance, the relationship indication providing module 6-226 of the computing device 6-10 providing one or more indications that indicate one or more spatial relationships between the two or more of the relevant reported aspects 6-14.

In various implementations, operation 6-557 may include an operation 6-563 for providing one or more relevant reported aspects that are intermediate outcomes associated with the one or more target outcomes as depicted in FIG. 6-5b. For instance, the relevant reported aspect providing module 6-104 of the computing device 6-10 providing one or more relevant reported aspects 6-14 that are intermediate outcomes associated with the one or more target outcomes.

Turning now to FIG. 6-6, which is a high-level block diagram illustrating a particular implementation of the computing device 6-10 of FIG. 6-1b. As illustrated, the computing device 6-10 may include a processor 6-602 (e.g., microprocessor, controller, and so forth) coupled to storage medium 6-606 (e.g., volatile or non-volatile memory). The storage medium 6-606 may store computer readable instructions 6-604 (e.g., computer program product). The processor 6-602, in various implementations, may execute the computer readable instructions 6-604 in order to execute one or more operations described above and as illustrated in FIGS. 6-3, 6-4a, 6-4b, 6-4c, 6-4d, 6-4e, 6-4f, 6-4g, 6-4h, 6-5a, and 6-5b.

For example, the processor 6-602 may execute the computer readable instructions 6-604 in order to identify, in response to reception of one or more solicitations 6-13, one or more relevant reported aspects 6-14 associated with one or more source users 6-2* that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects 6-14 being based, at least in part, on relevancy of the one or more relevant reported aspects 6-14 with respect to the one or more target outcomes; and/or to provide the one or more relevant reported aspects 6-14 as illustrated by the operational flow 6-300 of FIG. 6-3.

VIII. Template Development Based on Sensor Originated Reported Aspects

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 everyday activities, behaviors, thoughts, beliefs, traits, physical or mental states, physical characteristics, and other aspects of the person's everyday life onto an open journal. One place where such open journals 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, 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 become very popular in recent times 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 journals 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.

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.

There are also other types of sensors that have traditionally been too large to carry around that are now becoming increasingly more compact and more portable for personal use. These include, for example, sensors that can monitor and detect various physiological characteristics of users including those that can, individually or in combination, collect physiological data that may be used in order to determine the inferred mental states (or simply “mental states”) of users. Examples of such sensors include, for example, functional near-infrared (fNIR) devices, functional magnetic resonance imaging (fMRI) devices, electroencephalography (EEG) devices, magnetoencephalography (MEG) devices, galvanic skin sensor devices, and so forth.

Other sensors may be integrated into user devices such as automobiles, exercise machines, household appliances, and so forth that may be employed in order to detect and monitor their usage. 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).

Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, and so forth) are now available through these 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 sites making it even more difficult to exploit such potentially useful data.

In various embodiments, methods, systems, circuitry, and computer program products are provided for developing one or more templates that may facilitate one or more end users in achieving one or target outcomes when one or more emulatable aspects included in the one or more templates are emulated. More particularly, the methods, systems, circuitry, and computer program products may be designed to develop the one or more templates based, at least in part, on one or more reported aspects of one or more “source users” that were at least originally reported by one or more sensors. In some embodiments, the one or more templates may be developed based on reported aspects that are reported by one or more sensors and one or more source users.

As briefly described above, in order to develop the one or more templates, one or more reported aspects that were at least originally reported by one or more sensors may at least initially be provided. In some cases, the providing of the one or more reported aspects that were originally reported by one or more sensors may involve acquiring or retrieving of such reported aspects from, for example, a wireless network, a wired network, and/or a memory. In some embodiments, the methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, a network device such as a server (e.g., network servers) or a local client device (e.g., a source user device or an end user device).

As previously indicated, the one or more reported aspects that are provided by the methods, systems, circuitry, and computer program products may be used in order to develop one or more templates. A “template” is a plan or a schedule that is designed to facilitate the achievement of one or more target outcomes when one or more emulatable aspects included in the template are emulated. The one or more emulatable aspects that may be included in the template may correspond to the one or more reported aspects that were provided and that were originally reported by one or more sensors.

In the discussion to follow below, a “personalized plan” is a particular type of template that has personalized for a particular end user. For example, a personalized plan may be developed by taking a generic template and modifying the generic template (e.g., modifying or replacing the emulatable aspects that may be included in the generic template) such that the modified generic template (e.g., personalized plan) meets or satisfies logistical or physical limitations of the end user. An example of a personalized plan (or a template) is a personalized plan (or a template) that is developed based on reported aspects of a source user that facilitates an end user to achieve a desired outcome such as weight loss, achieving a high score on the scholastic aptitude test (SAT).

A template may merely indicate a collection of activities (e.g., emulatable aspects) or may indicate a more precise schedule of activities (e.g., emulatable aspects) that an end user may emulate in order to achieve a target outcome or outcome. For example, if a template is designed to facilitate an end user to lose 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) the end user may need to execute in order to achieve the weight loss. Similarly, if the template is designed to facilitate an end user to achieve a high score for the 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) the end user may need to execute in order to achieve the high test score for the SAT. Note that in some cases a template may include one or more emulatable intermediate outcomes that are associated with the target outcome or outcomes associated with the template. For example, in the above weight loss example, the template may indicate the amount of weight loss an end user 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 other cases, a template may merely be a collection of one or more emulatable aspects that does not define any 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 “don't drink caffeine beverages.” Such a template would not necessarily have any indication of relationship between the two emulatable aspects indicated by the template.

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. In brief, and as will be further described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, 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, 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 a source user that has been reported by, for example, one or more sensors or by one or more source users. In some instances, such a reported aspect may be reported in the form of a log entry such as a microblog entry or a status report. A “relevant reported aspect,” in contrast, may be a reported aspect that is at least associated with one or more source users who have achieved one or more target outcomes (e.g., sought-after goals or desired outcomes). Alternatively, a “relevant reported aspect” may be a reported aspect that is relevant to achieving the one or more target outcomes. The relevancy of a reported aspect with respect to achieving the one or more target outcomes in some instances may be based on one or more relevancy factors as will be further described herein. Note that references in the following to “reported aspects” and “relevant reported aspects” will actually be in reference to data that indicate such information (e.g., data that indicate reported aspects and data that indicate relevant reported aspects) unless indicated otherwise.

A “target outcome” may be any type of desirable goal or result that may be sought by, for example, an end user. 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 who is a direct or indirect beneficiary of one or more templates that may be developed based at least in part on one or more reported aspects that may be provided by, for example, one or more sensors. 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. 7-1a, and 7-1b 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 7-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 various embodiments, the computing device 7-10 may be a server such as one of the one or more network servers 7-60 illustrated in FIG. 7-1a. Alternatively, the computing device 7-10 may be a source user device such as one of the local source user devices 7-20* illustrated in FIG. 7-1a. In still other embodiments, the computing device 7-10 may be an end user device such as one of the local end user device 7-30* illustrated in FIG. 7-1a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 7-2*” may be in reference to a source user 7-2a, a source user 7-2b, and so forth.

Note that for ease of understanding and explanation, the computing device 7-10 of the exemplary environment 7-100 of FIGS. 7-1a and 7-1b will be generally described in the following discussion 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 7-100 of FIG. 7-1a and 7-1b assumes that the computing device 7-10 is a server, the following discussion will, for the most part, be applicable even if the computing device 7-10 was operating as an end user device (e.g., local end user device 7-30*) or as a source user device (e.g., local source user device 7-20*) with certain obvious exceptions (e.g., if the computing device 7-10 is an end user device or a source user device rather than a server, the computing device 7-10 may communicate with an end user 7-4* or a source user 7-2* directly through a user interface 7-120 rather than indirectly through a wireless network and/or wired network 7-50 as may be the case when the computing device 7-10 is a server). In some embodiments, the computing device 7-10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 7-1a and 7-1b, and as previously indicated, the computing device 7-10 may be a network device such as a server (e.g., a network server 7-60) that is designed to communicate with other network devices. For example, the computing device 7-10 may communicate with one or more source users 7-2*(e.g., source user 7-2a, source user 7-2b, and so forth) through one or more local source user devices 7-20*(e.g., local source user device 7-20a, local source user device 7-20b, and so forth), with one or more end users 7-4*(e.g., end user 7-4a, end user 7-4b, and so forth) through one or more local end user devices 7-30*(e.g., local end user device 7-30a, local end user device 7-30b, and so forth), with one or more sensor integrated devices 7-40 (e.g., a transportation vehicle such as a car, an exercise machine, or any other type of device that may have an integrated sensor designed to sense, for example, usage), with one or more network servers 7-60, and/or with one or more third parties 7-6 (e.g., one or more content providers, one or more network service providers, and/or one or more other parties) via a wireless network and/or wired network 7-50. In various implementations, the wireless and/or wired network 7-50 may include 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 7-50.

In various embodiments, the computing device 7-10 may be designed to, among other things, provide (e.g., obtain, retrieve, receive, solicit, and so forth) one or more reported aspects 7-15 associated with one or more source users 7-2* that were originally reported by one or more sensors 7-240*. Based at least on a portion of the one or more reported aspects 7-15 that are provided, the computing device 7-10 may develop one or more templates 7-18, the one or more templates 7-18 to be developed being designed to facilitate one or more end users 7-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates 7-18 are emulated.

In various embodiments, the computing device 7-10 may randomly, semi-continuously, or continuously acquire (e.g., receive, retrieve, or solicit) reported aspects 7-15 associated one or more source user 7-2* that were at least originally reported by one or more sensors 7-240*. Such reported aspects 7-15 may indicate a variety of aspects (e.g., behavior aspects such as user activities, user states, environmental conditions, and so forth) associated with the one or more source users 7-2*. The reported aspects 7-15 to be acquired may, in some cases, include both reported aspects 7-15 that are relevant to achieving one or more target outcomes and reported aspects 7-15 that may not be relevant for achieving the one or more target outcomes.

The reported aspects 7-15 may be acquired from a variety of sources. For example, in some embodiments, the reported aspects 7-15 that may be acquired by the computing device 7-10 may be acquired from one or more network servers 7-60, from one or more local source user devices 7-20*, from one or more sensor integrated devices 7-40 (e.g., exercise machine or an automobile with integrated sensors), from one or more third parties 7-6 (e.g., content providers, network service providers, and so forth), and/or from a memory 7-116. In embodiments where the reported aspects 7-15 are acquired through a wireless network and/or a wired network 7-50, the acquisition of the reported aspects 7-15 may be as a result of transmitting one or more solicitations for such data.

Upon providing (e.g., acquiring) one or more reported aspects 7-15 that are associated with the one or more source users 7-2* and that were at least originally reported by one or more sensors 7-240*, the computing device 7-10 may develop one or more templates 7-18 that are designed to facilitate one or more end users 7-4* to achieve one or more target outcomes, the development of one or more templates 7-18 based on at least a portion of the one or more reported aspects that are provided. In particular, in order to develop the one or more templates 7-18, the computer device 7-10 may be designed to identify from the one or more reported aspects 7-15 that have been provided, one or more relevant reported aspects 7-16 that are determined to be relevant for achieving the one or more target outcomes. In some cases, this may mean at least identifying those reported aspects 7-15 that are associated with source users 7-2* who have been identified as achieving the one or more target outcomes. Alternatively or additionally, a reported aspect 7-15 may be deemed relevant for achieving the one or more target outcomes when the reported aspect 7-15 is determined to be relevant with respect to certain relevancy factors as will be further described herein.

In any event, upon identifying the one or more relevant reported aspects 7-16 that are relevant for achieving the one or more target outcomes, one or more templates 7-18 may be developed by including into each of the one or more templates 7-18, one or more emulatable aspects that corresponds to the one or more relevant reported aspects 7-16. In cases where multiple emulatable aspects are included into a template 7-18, one or more relationships (e.g., temporal, specific time, or spatial relationship) between the multiple emulatable aspects may be defined in the template 7-18.

In some alternative embodiments, the computing device 7-10 may be configured to selectively provide (e.g., acquire) reported aspects 7-15 that are relevant for achieving one or more target outcomes. In other words, selectively acquiring relevant reported aspects 7-16 rather than acquiring reported aspects 7-15 that are associated with the one or more source users 7-2* and that were originally reported by one or more sensors 7-240* and that include both relevant reported aspects 7-16 and non-relevant reported aspects 7-17. For example, acquiring only reported aspects 7-15 that are associated with source users 7-2* who have achieved the one or more target outcomes and/or that are relevant with respect to certain relevancy factors. For these embodiments, there may not be any need for an operation to identify relevant reported aspects 7-16 from the acquired reported aspects 7-15 since all of the acquired reported aspects 7-15 may be relevant for achieving the one or more target outcomes. Further, for these embodiments, one or more templates 7-18 may be developed by the computing device 7-10 based directly on the provided reported aspects 7-15 (e.g., developing the one or more templates 7-18 by including into each of the one or more templates 7-18 one or more emulatable aspects that corresponds to one or more provided reported aspects 7-15) rather than having to filter through the reported aspects 7-15 in order to identify the relevant reported aspects 7-16.

After developing the one or more templates 7-18, the computing device 7-10 may be designed to present the one or more templates 7-18. The one or more templates 7-18 may be presented by transmitting via the wireless network and/or wired network 7-50 the one or more templates 7-18 to one or more network servers 7-60, to one or more source users 7-2*(e.g., one or more local source user devices 7-20*), to one or more end users 7-4*(e.g., one or more local end user devices 7-30*), and/or to one or more third parties 7-6. In embodiments where the computing device 7-10 is a source user device or an end user device, the computing device 7-10 may indicate (e.g., visually display or audibly indicate) the one or more templates 7-18 via a user interface 7-120.

In some embodiments, the development of the one or more templates 7-18 may include developing the one or more templates 7-18 based on one or more reported aspects 7-15 that are associated with one or more source users 7-2* and that were originally reported by the one or more sensors 7-240* and one or more reported aspects 7-15 that are associated with the one or more source users 7-2* and that were originally reported by the source users 7-2*. In other words, for these embodiments, the one or more templates 7-18 may be developed based on data reported by one or more sensors 7-240* and by one or more source users 7-2*. In some cases, the one or more reported aspects 7-15 that are provided by the one or more source users 7-2* may have been provided through social networking entries such as blog or microblog entries, status reports, and so forth.

As will be further described, the one or more sensors 7-240* may include almost any type of sensors 7-240* including, for example, sensors 7-240* that can sense various physical characteristics of a source user 7-2*(e.g., heart rate sensor or blood pressure sensor), sensors 7-240* that can sense activities of a source user 7-2*(e.g., a pedometer), sensors 7-240* that can sense environment conditions (e.g., air quality sensors), sensors 7-240* that can sense the location of a source user 7-2*(e.g., global positioning system or GPS), sensors 7-240* that can provide physiological data that may be processed in order to determine inferred mental states of users, and so forth.

In some embodiments, the computing device 7-10, as previously indicated, may be a server (e.g., one of the one or more network servers 7-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 7-10 is a source user device (e.g., local source user device 7-20*) or an end user device (e.g., local end user device 7-30*) rather than a network server 7-60, the computing device 7-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.

With respect to the one or more sensor integrated devices 7-40 of the exemplary environment 7-100 of FIGS. 7-1a and 7-1b, the one or more sensor integrated devices 7-40 may directly communicate with the wireless network and/or the wired network 7-50 in some embodiments. Alternatively, the one or more sensor integrated devices 7-40 may indirectly communicate with the wireless network and/or the wired network 7-50 via the one or more local source user devices 7-20*(e.g., via, for example, personal area network or PAN). In various embodiments, a sensor integrated device 7-40 may be a variety of devices that may comprise of one or more sensors 7-240c and that may be operated or used by a source user 7-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 with respect to FIG. 7-2c, each of the one or more sensor integrated devices 7-40 (see FIG. 7-2c) may include one or more sensors 7-240c, a network interface 7-242, a memory 7-243, and/or one or more functional components 7-244. The one or more sensors 7-240c may be designed to detect or sense one or more aspects associated with one or more source users 7-2* such as usage of the sensor integrated device 7-40 by, for example a source user 7-2*. In some cases, the one or more sensors 7-240c may be designed to sense or monitor certain physical characteristics of a source user 7-2* when the sensor integrated device 7-40 is being used for its functional purpose. For example, some exercise machines such as treadmills have sensors 7-240* that can monitor the heart rate of, for example, a source user 7-2* when the source user 7-2* is using the treadmill.

As illustrated in FIGS. 7-1a and 7-1b, the computing device 7-10, the one or more local source user devices 7-20*, and the one or more sensor integrated devices 7-40 may include one or more sensors 7-240*(e.g., one or more sensors 7-240a for the computing device 7-10, one or more sensors 7-240b for the one or more local source user devices 7-20*, and one or more sensors 7-240c for the one or more sensor integrated devices 7-40) that are designed to detect or monitor various aspects of one or more source users 7-2*. FIG. 7-2d illustrates the types of devices that may be included in the one or more sensors 7-240* of the computing device 7-10, the one or more local source user devices 7-20*, and the one or more sensor integrated devices 7-40.

As illustrated in FIG. 7-2d, in some embodiments, the one or more sensors 7-240* that may be included with the computing device 7-10, the one or more local source user devices 7-20*, and/or the one or more sensor integrated devices 7-40 may include one or more behavior aspect sensors 7-246 that are designed to sense one or more behavior aspects of one or more source users 7-2*. Examples of sensing devices that may be considered behavior aspect sensors 7-246 include, for example, pedometers 7-247, accelerometers 7-248, exercise equipment sensors 7-249, transport vehicle sensors 7-250, household appliance sensors 7-251, and toilet usage sensors 7-252. Note that although some of these sensing devices (e.g., pedometers 7-247 and accelerometers 7-248 may directly detect activities of users (e.g., source users 7-2*), other sensing devices such as exercise equipment sensors 7-249 and transport vehicle sensors 7-250 may only sense usage of the underlying devices (e.g., exercise equipment and transport vehicle). Further, some sensors 7-240* such as exercise equipment sensors 7-249 may include sensing devices for detecting physiological characteristics (e.g., heart rate) of users.

In some embodiments, the one or more sensors 7-240* that may be included with the computing device 7-10, the one or more local source user devices 7-20*, and/or the one or more sensor integrated devices 7-40 may include one or more user physical characteristic sensors 7-253 that are designed to sense one or more physical characteristics of one or more source users 7-2*. Examples of sensing devices that may be considered physical characteristic sensors 7-253 include, for example, image capturing devices 7-261 such as digital cameras or portable ultrasound devices (e.g., to capture internal or external images of source users 7-2*), audio capturing devices (e.g., to capture voice or internal sound such as heart rate), and/or user physiological sensors 7-254. Examples of physiological sensors 7-254 include, for example, fNIR devices, fMRI devices, heart rate monitors, blood pressure devices, blood glucose meters, and so forth. Note that some physiological sensors 7-254 may be used in order to obtain physiological data that may be processed using appropriate software in order to determine at last inferred mental states of users.

In some embodiments, the one or more sensors 7-240* that may be included with the computing device 7-10, the one or more local source user devices 7-20*, and/or the one or more sensor integrated devices 7-40 may include one or more global position system (GPS) devices 7-255 that are designed to find the geographical locations of one or more source users 7-2*. As indicated earlier, GPS devices 7-255 are now commonly integrated into many mobile communication devices such as cellular telephones and Smartphones.

In some embodiments, the one or more sensors 7-240* that may be included with the computing device 7-10, the one or more local source user devices 7-20*, and/or the one or more sensor integrated devices 7-40 may include one or more user environmental condition sensors 7-256 that are designed to sense one or more environmental conditions associated with one or more source users 7-2*. Examples of sensing devices that may be considered environmental condition sensors 7-256 include, for example, air quality sensors 7-257 designed to sense quality of air (e.g., pollutant amount, pollen count, gas level, and so forth) that one or more source users 7-2* breathes, water quality sensors 7-259 designed to sense quality of water being drunk by one or more source users 7-2*, and/or atmospheric condition sensors 7-258 that are designed to measure certain atmospheric conditions such as temperature, humidity, pressure, wind speed, and so forth.

In some embodiments, the one or more sensors 7-240* that may be included with the computing device 7-10, the one or more local source user devices 7-20*, and/or the one or more sensor integrated devices 7-40 may include one or more mental state sensors 7-260 that are designed to sense one or more physical or physiological characteristics of one or more source users 7-2* that may be processed, using the appropriate software, in order to determine mental states of the one or more source users 7-2*. Examples of such mental state sensors 7-260 include, for example, fNIR devices, fMRI devices, EEG devices, MEG devices, galvanic skin sensor devices, and so forth.

As earlier indicated, in some embodiments, the one or more sensors 7-240* that may be included with the computing device 7-10, the one or more local source user devices 7-20*, and/or the one or more sensor integrated devices 7-40 may include one or more image capturing devices 7-261 (e.g., digital camera, camcorder, ultrasound devices, and so forth) that may be employed in order to capture, for example, physical characteristics of one or more source users 7-2*. Such devices may also be used in order to sense other types of aspects associated with one or more source users 7-2*. For example, in some cases, image capturing devices 7-261 may be employed in order to detect or capture activities being executed by one or more source users 7-2*. By using the appropriate software, images captured through such devices may be properly interpreted.

Referring back to the exemplary environment 7-100 of FIGS. 7-1a and 7-1b, each of the one or more local source user devices 7-20* and each of the one or more local end user devices 7-30*(as well as the computing device 7-10 in embodiments in which the computing device 7-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 7-20* and/or the one or more local end user devices 7-30*(as well as the computing device 7-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 7-20* and/or local end user device 7-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 7-10 as illustrated in FIG. 7-1b may include one or more modules, sub-modules, and various other components. As shown, the computing device 7-10 may include at least a sensor originated reported aspect providing module 7-102 (which may further include one or more sub-modules as illustrated in FIG. 7-2a) and a template development module 7-104 (which may also include one or more sub-modules as illustrated in FIG. 7-2b). In various embodiments, the computing device 7-10 may further include a presentation module 7-106 (which may further include a transmission module 7-236 and/or a user interface indication module 7-238) and a memory 7-116 (which may store a plurality of reported aspects 7-15 that may further include one or more relevant reported aspects 7-16 and/or one or more non-relevant reported aspects 7-17, one or more end user relevancy indications 7-142, one or more source user relevancy indications 7-144, one or more third party source relevancy indications 7-145, one or more predefined time increment indications 7-146, and/or one or more applications 7-140).

The computing device 7-10 may also include, in various embodiments, a network interface 7-118 (e.g., a network interface card or NIC), a user interface 7-120, a social networking entry reception module 7-110 (which may further include a blog entry reception module 7-111 and/or a status report reception module 7-112), a journal entry reception module 7-114, and/or one or more sensors 7-240a. In some cases, the presence or absence of some of these modules and sub-modules may depend on, for example, whether the computing device 7-10 is a server, an end user device, or a source user device. For example, if the computing device 7-10 is a server, then the computing device 7-10 may not include a user interface 7-120.

Referring now to the sensor originated reported aspect providing module 7-102, the sensor originated reported aspect providing module 7-102 may be configured to, among other things, provide (e.g., acquire from a memory 7-116 and/or from a wireless network and/or a wired network 7-50) one or more reported aspects 7-15 associated with one or more source users 7-2* that were originally reported by one or more sensors 7-240*. In contrast, the template development module 7-104 may be configured to, among other things, develop one or more templates 7-18 designed to facilitate one or more end users 7-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates 7-18 are emulated, the development of the one or more templates 7-18 being based at least on a portion of the one or more reported aspects 7-15.

The memory 7-116 may be designed to store various data including a plurality of reported aspects 7-15 associated with one or more source user 7-2*. The plurality of reported aspects 7-15 stored in the memory 7-116 may include one or more reported aspects 7-15 that were originally reported by one or more sensors 7-240* and in some cases, another one or more reported aspects 7-15 that were originally reported by the one or more source users 7-2*. The plurality of reported aspects 7-15 stored in memory 7-116 may include, in various implementations, one or more relevant reported aspects 7-16 that are relevant to achieving one or more target outcomes and/or one or more non-relevant reported aspects 7-17 that may not be relevant for achieving the one or more target outcomes.

Other types of data may be stored in the memory 7-116 in various implementations including, for example, one or more end user relevancy indications 7-142 (e.g., one or more indications that indicate the types of reported aspects 7-15 that an end user 7-4 has an interest in or believes is relevant to achieving one or more target outcomes) and/or one or more source user relevancy indications 7-144 (e.g., one or more indications provided by a source user 7-2* that indicate at least which types of reported aspects 7-15 are relevant to achieving one or more target outcomes).

In some cases, the memory 7-116 may also include, for example, one or more third party source relevancy indications 7-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 7-6 that indicate at least which types of reported aspects 7-15 are relevant to achieving one or more target outcomes), one or more predefined time increment indications 7-146 (e.g., one or more indications that indicate at least one time increment, such as a time interval or window, that may be considered in order to determine whether, for example, a reported aspect 7-15 is relevant for achieving a target outcome if the reported aspect 7-15 indicates an aspect that occurred within the time increment from an occurrence of the target outcome as successfully achieved by, for example, a source user 7-2*), and/or one or more applications 7-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). In various implementations, the memory 7-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 social networking entry reception module 7-110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 7-2*, from one or more end users 7-4*, from one or more third parties 7-6, from one or more sensor integrated devices 7-40, and/or from one or more network servers 7-60. The social networking entry reception module 7-110 may further include a blog entry reception module 7-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 7-112 for receiving social networking status reports. The journal entry reception module 7-114 may be configured to receive journal entries from, for example, one or more source users 7-2*, one or more end users 7-4*, and/or one or more third parties 7-6 (e.g., a non-user). The user interface 7-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. 7-2 a illustrates particular implementations of the sensor originated reported aspect providing module 7-102 of the computing device 7-10 of FIG. 7-1b. As illustrated, the sensor originated reported aspect providing module 7-102 may include, in various implementations, one or more sub-modules. For example, in some implementations, the sensor originated reported aspect providing module 7-102 may include a sensor originated reported aspect direct acquiring module 7-202, a sensor originated reported aspect network acquiring module 7-204, a sensor originated reported aspect memory acquiring module 7-206, and/or a relevant reported aspect acquiring module 7-208 (which may further include a source user associated reported aspect acquiring module 7-210 and/or a relevancy factor relevant reported aspect acquiring module 7-212).

The sensor originated reported aspect direct acquiring module 7-202 may be configured to acquire one or more reported aspects 7-15 directly from one or more sensors 7-240a (e.g., as may be the case when the computing device 7-10 is a source user device). The sensor originated reported aspect network acquiring module 7-204 may be configured to acquire one or more reported aspects 7-15 via at least one of a wireless network and a wired network 7-50. The sensor originated reported aspect memory acquiring module 7-206 may be configured to acquire one or more reported aspects 7-15 from the memory 7-116.

In various implementations, the relevant reported aspect acquiring module 7-208 may be configured to, among other things, selectively acquire one or more relevant reported aspects 7-16 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to achieving the one or more target outcomes. In order to facilitate the acquisition of the one or more relevant reported aspects 7-16, the relevant reported aspect acquiring module 7-208, in some implementations, may further include the source user associated reported aspect acquiring module 7-210 that is configured to selectively acquire one or more reported aspects 7-15 that were originally reported by one or more sensors 7-240* and that are associated with one or more source users 7-2* who have achieved the one or more target outcomes. In the same or different implementations, the relevant reported aspect acquiring module 7-208 may include the relevancy factor relevant reported aspect acquiring module 7-212 that may be configured to, among other things, selectively acquire one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to one or more relevancy factors (e.g., indications provided by an end user 7-4* that indicates that only particular types of user behaviors such as dietary behaviors are relevant).

FIG. 7-2 b illustrates particular implementations of the template development module 7-104 of FIG. 7-1b. The template development module 7-104, as illustrated, may include one or more sub-modules. For example, in various implementations, the template development module 7-104 may include an emulatable aspect including module 7-220, a relationship defining module 7-222, an emulatable intermediate outcome including module 7-223, a plausible determining module 7-224 (which may further include an action module 7-226 that may further include a not plausible notification module 7-228 and/or a template modification module 7-229), and/or a relevant reported aspect identification module 7-230 (which may further include a source user associated reported aspect identification module 7-232 and/or a relevancy factor relevant reported aspect identification module 7-234).

In brief, the emulatable aspect including module 7-220 may be configured to include into each of one or more templates 7-18 to be developed one or more emulatable aspects that correspond to at least a portion of one or more reported aspects 7-15 that may be provided by the sensor originated reported aspect providing module 7-102. The relationship defining module 7-222, in contrast, may be configured to define in each of the one or more templates 7-18 to be developed at least one temporal, specific time, or spatial relationship between at least two of the plurality of emulatable aspects that may be included in each of the one or more templates 7-18. The emulatable intermediate outcome including module 7-223 may be configured to include into the one or more templates 7-18 to be developed one or more emulatable intermediate outcomes that are associated with the one or more target outcomes, for example, if one of the target outcomes is to lose 20 pounds of body weight, an emulatable intermediate outcome might be a weight loss of 10 pounds at the midway point of the template 7-18 to be developed.

The plausible determining module 7-224 may be configured to determine whether at least one of one or more emulatable aspects to be included in the one or more templates 7-18 to be developed is a plausible aspect that has been successfully emulated by one or more third parties 7-6, and if not plausible, prompting for example the action module 7-226 to execute one or more actions. The not plausible notification module 7-228 that may be included in the action module 7-226 may be configured to notify, in response to a determination that the at least one of the one or more emulatable aspects to be included in the one or more templates 7-18 is not a plausible aspect, at least one of an end user 7-4*, a source user 7-2*, and a third party 7-6 regarding the determination that at least one of the one or more emulatable aspects to be included in the one or more templates 7-18 is not a plausible aspect. In contrast, the template modification module 7-229 that may be included in the action module 7-226 may be configured to modify, in response to a determination that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more templates 7-18 by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 7-6.

The relevant reported aspect identification module 7-230 that may be included in the template development module 7-104 may be configured to identify from the one or more reported aspects 7-15 that are provided by the sensor originated reported aspect providing module 7-102 one or more relevant reported aspects 7-16 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to achieving the one or more target outcomes. To facilitate the relevant reported aspect identification module 7-230 in identifying the relevant reported aspects 7-16, the relevant reported aspect identification module 7-230 may include the source user associated reported aspect identification module 7-232 configured to identify one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are associated with one or more source users 7-2* who have been determined to have achieved the one or more target outcomes.

In some implementations, the relevant reported aspect identification module 7-230 may include a relevancy factor relevant reported aspect identification module 7-234 that is configured to identify one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to one or more relevancy factors. The various relevancy factors that may be considered in determining relevancy of a reported aspect 7-15 with respect to achieving one or more target outcomes will be discussed in greater detail herein.

Referring now to FIG. 7-2c illustrating one of the sensor integrated devices 7-40 of FIGS. 7-1a and 7-1b. The sensor integrated device 7-40, in various implementations, may include at least one or more sensors 7-240c. The one or more sensors 7-240 that may be included in a sensor integrated device 7-40 (as well as the computing device 7-10 and/or one or more of the local source user devices 7-20*) may be designed to sense or detect one or more aspects associated with one or more source users 7-2*. For example, in various implementations, the one or more sensors 7-240 may include one or more devices that can monitor a user's physiological characteristics such as blood pressure sensors, heart rate monitors, glucometers (e.g., blood glucose meter), and so forth.

The sensor integrated device 7-40 may further include a network interface 7-242 (similar to the network interface 7-118 of the computing device 7-10), a memory 7-243 (similar to memory 7-116 of the computing device 7-10), and one or more functional components 7-244. With respect to the one or more functional components 7-244, and as an illustration, if the sensor integrated device 7-40 was an automobile, then the functional components 7-244 may include an engine, four tires, steering system, transmission system, and so forth.

Referring back to the computing device 7-10 of FIG. 7-1b, the various modules (e.g., the sensor originated reported aspect providing module 7-102, the template development module 7-104, and so forth) along with their sub-modules included in the computing device 7-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the sensor originated reported aspect providing module 7-102 and/or the template development module 7-104 may be implemented with a processor 7-802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 7-804 (e.g., computer program product) stored in a storage medium 7-806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 7-10 of FIG. 7-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 discussion relating to the functional aspects of the computing device 7-10 of FIG. 7-1b will now be provided with respect to the processes and operations to be described herein. FIG. 7-3 illustrates an operational flow 7-300 representing example operations directed to, among other things, development of 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 in part on at least a portion of one or more reported aspects associated with one or more source users that were originally reported by one or more sensors.

In FIG. 7-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 7-100 described above as illustrated in FIGS. 7-1a and 7-1b, and/or with respect to other examples (e.g., as provided in FIGS. 7-2a, 7-2b, 7-2c, and 7-2d) 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. 7-1a, 7-1b, 7-2a, 7-2b, 7-2c, and 7-2d. 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. 7-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 7-300 may move to a sensor originated reported aspect providing operation 7-302 for providing one or more reported aspects associated with one or more source users that were originally reported by one or more sensors. For instance, and as an illustration, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 of FIG. 7-1b providing (e.g., acquiring, retrieving, finding, locating, soliciting for, and so forth) one or more reported aspects 7-15 associated with one or more source users 7-2* that were originally reported (e.g., initially detected or sensed) by one or more sensors 7-240* (e.g., sensors 7-240* designed to sense one or more aspects associated with one or more source users 7-2* including, for example, behavior aspects associated with the one or more source users 7-2*).

In addition to the sensor originated reported aspect providing operation 7-302, operational flow 7-300 may also include a template developing operation 7-304 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. For instance, the template development module 7-104 of the computing device 7-10 developing one or more templates 7-18 designed to facilitate one or more end users 7-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates 7-18 are emulated, the development of the one or more templates 7-18 being based at least on a portion of the one or more reported aspects 7-15. As will be further described herein, the sensor originated reported aspect providing operation 7-302 as well as the template developing operation 7-304 may be implemented in a number of different ways in various alternative implementations.

For example, FIGS. 7-4a, 7-4b, 7-4c, 7-4d, 7-4e, and 7-4f illustrate the various ways that the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may be executed in various alternative implementations. For instance, the one or more reported aspects to be provided by the sensor originated reported aspect providing operation 7-302 may be provided by acquiring the one or more reported aspects from a variety of sources. In some implementations, for example, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-402 for acquiring the one or more reported aspects directly from the one or more sensors as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect direct acquiring module 7-202 (see FIG. 7-2a) of the computing device 7-10 of FIG. 7-1b acquiring (e.g., receiving, prompting for, collecting, and so forth) the one or more reported aspects 7-15 directly (e.g., instead of through a wireless network and/or wired network 7-50) from the one or more sensors 7-240a of the computing device 7-10.

In some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-403 for acquiring the one or more reported aspects via at least one of a wireless network and a wired network as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect network acquiring module 7-204 (see FIG. 7-2a) of the computing device 7-10 when the computing device 7-10 is a server (e.g., server embodiment) acquiring (e.g., receiving, soliciting for, searching for, and so forth) the one or more reported aspects 7-15 via at least one of a wireless network and a wired network 7-50.

In some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-404 for acquiring the one or more reported aspects from a memory as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect memory acquiring module 7-206 (see FIG. 7-2a) of the computing device 7-10 acquiring (e.g., retrieving, finding, locating, and so forth) the one or more reported aspects 7-15 from a memory 7-116.

Various types of source user aspects may be indicated by the one or more reported aspects 7-15 that are provided through the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 For example, in some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-405 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more behavior incidences associated with the one or more source users as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more behavior incidences associated with the one or more source users 7-2*.

In various implementations, operation 7-405 may include one or more additional operations. For example, in some implementations, operation 7-405 may include an operation 7-406 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more incidences of activities executed by the one or more source users as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more incidences of activities (e.g., dietary activities, exercise activities, social activities, medical treatment activities including drug consumption, and so forth) executed by the one or more source users 7-2*.

In the same or different implementations, operation 7-405 may include an operation 7-407 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more user attitudes or conduct associated with the one or more source users as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240*(e.g., fMRI, fNIR, and so forth) including one or more reported aspects 7-15 that indicate one or more user attitudes or conduct associated with the one or more source users 7-2*.

Other types of aspects may also be indicated by the one or more reported aspects 7-15 to be provided through the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 in various alternative implementations. For example, in some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-408 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more incidences of one or more mental states associated with the one or more source users as depicted in FIG. 7-4a. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more incidences of one or more mental states (e.g., anger, happiness or sadness, mental alertness, mental fatigue, jealousy, and so forth) associated with the one or more source users 7-2*.

In the same or different implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-409 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more incidences of one or more user physical characteristics associated with the one or more source users as depicted in FIG. 7-4b. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more incidences of one or more user physical characteristics (e.g., hair color, skin complexion, hair style, tattoos, blood pressure, body weight, body fat level, and so forth) associated with the one or more source users 7-2*.

In various implementations, operation 7-409 may include an operation 7-410 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more incidences of one or more user physiological characteristics associated with the one or more source users as depicted in FIG. 7-4b. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more incidences of one or more user physiological characteristics (e.g., heart rate, blood glucose level, blood circulation or volume, brain electrical activity, heart rate, and so forth) associated with the one or more source users 7-2*.

In the same or different implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-411 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more incidences of one or more user locations associated with the one or more source users as depicted in FIG. 7-4b. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more incidences of one or more user locations (e.g., home, workplace, school, New York City, Italy, and so forth) associated with the one or more source users 7-2*.

In the same or different implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-412 for providing the one or more reported aspects that were originally reported by the one or more sensors including one or more reported aspects that indicate one or more incidences of one or more external events associated with the one or more source users as depicted in FIG. 7-4b. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* including one or more reported aspects 7-15 that indicate one or more incidences of one or more external events (e.g., local weather or atmospheric conditions, air or water quality levels, traffic conditions, and so forth) associated with the one or more source users 7-2*.

The one or more reported aspects 7-15 provided through the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may in some cases include two or more reported aspects associated with two or more source users. For example, in some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-413 for providing two or more reported aspects associated with two or more source users that were originally reported by the one or more sensors as depicted in FIG. 7-4b. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing two or more reported aspects 7-15 associated with two or more source users 7-2* that were originally reported by one or more sensors 7-240*.

In some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-414 for providing two or more reported aspects associated with two or more source users that were originally reported by two or more sensors as depicted in FIG. 7-4b. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing two or more reported aspects 7-15 associated with two or more source users 7-2* that were originally reported by two or more sensors 7-240*.

In certain implementations, the sensor originated reported aspect providing operation 7-302 may involve selectively acquiring relevant reported aspects 7-16 that are relevant with respect to achieving one or more target outcomes rather than merely acquiring, for example, any reported aspects 7-15 that are determined to be associated with the one or more source users 7-2* and that were originally reported by the one or more sensors 7-240*. For example, in some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-415 for providing the one or more reported aspects by selectively acquiring one or more relevant reported aspects that were originally reported by the one or more sensors and that are relevant with respect to achieving the one or more target outcomes as depicted in FIG. 7-4c. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing the one or more reported aspects 7-15 by having the relevant reported aspect acquiring module 7-208 (see FIG. 7-2a) selectively acquiring (e.g., retrieving, finding, locating and so forth) one or more relevant reported aspects 7-16 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to achieving the one or more target outcomes.

Operation 7-415 for selectively acquiring the one or more relevant reported aspects may be executed in a number of different ways in various alternative implementations. For example, in some implementations, operation 7-415 may include an operation 7-416 for acquiring the one or more relevant reported aspects by selectively acquiring one or more reported aspects that were originally reported by the one or more sensors and that are associated with one or more source users who have achieved the one or more target outcomes as depicted in FIG. 7-4c. For instance, the relevant reported aspect acquiring module 7-208 of the computing device 7-10 acquiring the one or more relevant reported aspects 7-16 by having the source user associated reported aspect acquiring module 7-210 selectively acquiring one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are associated with one or more source users 7-2* who have achieved the one or more target outcomes. Note that if it is not known which source users 7-2* may have achieved the one or more target outcomes then a process may be executed to first find reported aspects 7-15 that correspond (e.g., equivalent or substantially equivalent) to the one or more target outcomes, and second, upon finding such corresponding reported aspects 7-15, identify the source users 7-2* who are associated with the corresponding reported aspects. By doing so, those source users 7-2* who have achieved the one or more target outcomes are identified.

In the same or different implementations, operation 7-415 may include an operation 7-417 for acquiring the one or more relevant reported aspects by selectively acquiring one or more reported aspects that were originally reported by the one or more sensors and that are relevant with respect to one or more relevancy factors as depicted in FIG. 7-4c. For instance, the relevant reported aspect acquiring module 7-208 of the computing device 7-10 acquiring the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect acquiring module 7-212 (e.g., see FIG. 7-2a) selectively acquiring one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to one or more relevancy factors.

Various types of relevancy factors may be considered in operation 7-417 in order to acquire the one or more relevant reported aspects 7-16. For example, in some implementations, operation 7-417 may include an operation 7-418 for acquiring the one or more relevant reported aspects by selectively acquiring one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects that belong to one or more aspect types that are of interest to the one or more end users as depicted in FIG. 7-4c. For instance, the relevant reported aspect acquiring module 7-208 of the computing device 7-10 acquiring the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect acquiring module 7-212 (e.g., see FIG. 7-2a) selectively acquiring one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that belong to one or more aspect types (e.g., dietary activities, mental states, exercise activities, rest activities, and so forth) that are of interest to the one or more end users 7-4*.

In the same or different implementations, operation 7-417 may include an operation 7-419 for acquiring the one or more relevant reported aspects by selectively acquiring one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects 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. 7-4c. For instance, the relevant reported aspect acquiring module 7-208 of the computing device 7-10 acquiring the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect acquiring module 7-212 (e.g., see FIG. 7-2a) selectively acquiring one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that belong to one or more aspect types (e.g., social activities, sleep patterns, bathroom usage, physical appearance, and so forth) that have been indicated by at least one source user 7-2* as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 7-417 may include an operation 7-420 for acquiring the one or more relevant reported aspects by selectively acquiring one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects 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. 7-4c. For instance, the relevant reported aspect acquiring module 7-208 of the computing device 7-10 acquiring the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect acquiring module 7-212 (e.g., see FIG. 7-2a) selectively acquiring one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that belong to one or more aspect types that have been indicated by at least one third party source as (e.g., a third party 7-6, a publication as provided by a third party 7-6, a content provider, and so forth) being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 7-417 may include an operation 7-421 for acquiring the one or more relevant reported aspects by selectively acquiring one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects that occurred within one or more predefined time increments, respectively, from one or more achievements of the one or more target outcomes by the one or more source users who have achieved the one or more target outcomes as depicted in FIG. 7-4c. For instance, the relevant reported aspect acquiring module 7-208 of the computing device 7-10 acquiring the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect acquiring module 7-212 (e.g., see FIG. 7-2a) selectively acquiring one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that occurred within one or more predefined time increments, respectively, from one or more achievements (e.g., occurrences) of the one or more target outcomes by the one or more source users 7-2* who have achieved the one or more target outcomes.

That is, not all relevant reported aspects 7-16 that may be relevant with respect to certain relevancy factors may actually be relevant to achieving the one or more target outcomes if the relevant reported aspects 7-16 indicate aspects that, time-wise, occurred remotely from occurrence (or achievement) of the one or more target outcomes as successfully achieved by the one or more source users 7-2* who have achieved the one or more target outcomes. For example, reported aspects 7-15 that are associated with source users 7-2* who have achieved the one or more target outcomes and that are relevant based on certain relevancy factors (e.g., belong to a type of aspect that is of interest to the end user 7-4* such as dietary behavior) may, nevertheless, not be relevant to achieving the one or more target outcomes if they occurred well before (or well after) the achievement of the one or more target outcomes by the one or more source users 7-2*.

Thus, a reported aspect 7-15 may, in some cases, be relevant to the achievement of the one or more target outcomes only if it falls within some time increment (e.g., “predefined time increment”) from one or more occurrences of one or more reported achievements by the one or more source users 7-2*(e.g., as reported through one or more reported aspects 7-15) of the one or more target outcomes. The length of the predefined time increments to be considered in determining relevancy may depend on a number of factors including, for example, the type of target outcomes being sought and/or the type of templates to be developed. In some implementations, the predefined time increments to be considered may be set by an end user 7-4*, by a source user 7-2*, and/or by a third party source (e.g., third party 7-6).

In various implementations, the one or more reported aspects 7-15 to be provided through the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may have been originally reported by a variety of sensors 7-240*. For example, in some implementations the sensor originated reported aspect providing operation 7-302 may include an operation 7-422 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by one or more sensors designed to sense one or more behavior aspects associated with the one or more source users as depicted by FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240*(e.g., behavior aspect sensors 7-246) designed to sense one or more behavior aspects associated with the one or more source users 7-2*.

Various types of sensors 7-240* may be used in order to sense various behavior aspects associated with source users 7-2*. For example, in some implementations, operation 7-422 may include an operation 7-423 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more pedometers as depicted in FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more pedometers 7-247.

In the same or different implementations, operation 7-422 may include an operation 7-424 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more accelerometers as depicted in FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more accelerometers 7-248.

In the same or different implementations, operation 7-422 may include an operation 7-425 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense usage of one or more exercise equipment as depicted in FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., exercise equipment sensors 7-249) designed to sense usage of one or more exercise equipment (e.g., bicycle, treadmill, elliptical exercise machines, and so forth).

In the same or different implementations, operation 7-422 may include an operation 7-426 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense usage of one or more transportation vehicles as depicted in FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240* (e.g., transport vehicle sensors 7-250) designed to sense usage of one or more transportation vehicles.

In the same or different implementations, operation 7-422 may include an operation 7-427 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense usage of one or more household appliances as depicted in FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240* (e.g., household appliance sensors 7-251) designed to sense usage of one or more household appliances.

In the same or different implementations, operation 7-422 may include an operation 7-428 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense toilet usage as depicted in FIG. 7-4d. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., toilet usage sensors 7-252) designed to sense toilet usage.

In some implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-429 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense one or more physical characteristics of the one or more source users as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., user physical characteristic sensors 7-253) designed to sense one or more physical characteristics of the one or more source users 7-2*.

In some cases, operation 7-429 may further include an operation 7-430 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense one or more physiological characteristics of the one or more source users as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240* (e.g., user physiological sensors 7-254) designed to sense one or more physiological characteristics of the one or more source users 7-2*. Examples of user physiological sensors 7-254 include, for example, blood pressure monitors, blood glucose meters, heart rate monitors, functional near-infrared (fNIR) devices, functional magnetic resonance imaging (fMRI) devices, and so forth).

In some implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-431 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more global positioning systems (GPSs) as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more global positioning systems (GPSs) 7-255.

In some implementations, the sensor originated reported aspect providing operation 7-302 may include an operation 7-432 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense one or more environmental conditions as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., environmental condition sensors 7-256) designed to sense one or more environmental conditions (e.g., source user environmental conditions).

Operation 7-432 may, in turn, further include an operation 7-433 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense water quality as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., water quality sensors 7-259) designed to sense water quality (e.g., qualities of drinking water consumed by the one or more source users 7-2*).

In the same or different implementations, operation 7-432 may include an operation 7-434 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense air quality as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., air quality sensors 7-257 such as particulate or pollen counter, gas detectors, and so forth) designed to sense air quality.

In the same or different implementations, operation 7-432 may include an operation 7-435 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense atmospheric conditions as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., atmospheric condition sensors 7-258) designed to sense atmospheric conditions.

Various types of sensors 7-240* may be employed in order to sense a variety of atmospheric conditions. For example, in some implementations, operation 7-435 may further include an operation 7-436 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including at least one of a barometer, a thermometer, and a humidity sensor as depicted in FIG. 7-4e. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including at least one of a barometer, a thermometer, and a humidity sensor.

In some implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-437 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more sensors designed to sense one or more physiological characteristics used to determine one or more mental states as depicted in FIG. 7-4f. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more sensors 7-240*(e.g., mental state sensors 7-260) designed to sense one or more physiological characteristics used to determine one or more mental states. Examples of mental state sensors 7-260 that can sense one or more physiological characteristics that may be used in order to determine mental states include, for example, fNIR devices, fMRI devices, electroencephalography (EEG) devices, magnetoencephalography (MEG) devices, galvanic skin sensor devices, respiration sensor devices, and so forth).

In some implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-438 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors including one or more image capturing devices as depicted in FIG. 7-4f. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* including one or more image capturing devices 7-261 (e.g., digital camera, digital camcorder, ultrasound devices, and so forth). Such image capturing devices 7-261 may be employed in some implementations in order to capture images of various aspects (e.g., user activities or facial expressions) associated with one or more source users 7-2*. In some cases, data provided by such image capturing devices 7-261 may be interpreted using, for example, image interpretation software (e.g., facial recognition applications).

In various implementations, the sensor originated reported aspect providing operation 7-302 of FIG. 7-3 may include an operation 7-439 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors and via one or more social networking entries as depicted in FIG. 7-4f. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by one or more sensors 7-240* and via one or more social networking entries.

In some implementations, operation 7-439 may further include an operation 7-440 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors via one or more blog entries as depicted in FIG. 7-4f. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by the one or more sensors 7-240* via one or more blog entries (e.g., microblog entries).

In the same or different implementations, operation 7-439 may include an operation 7-441 for providing one or more reported aspects associated with the one or more source users that were at least originally reported by the one or more sensors via one or more status reports as depicted in FIG. 7-4f. For instance, the sensor originated reported aspect providing module 7-102 of the computing device 7-10 providing one or more reported aspects 7-15 associated with the one or more source users 7-2* that were at least originally reported by the one or more sensors 7-240* via one or more status reports (e.g., social networking status reports).

Referring back to the template developing operation 7-304 of FIG. 7-3, the template developing operation 7-304, similar to the sensor originated reported aspect providing operation 7-302 of FIG. 7-3, may be executed in a number of different ways as illustrated in FIGS. 7-5a, 7-5b, 7-5c, and 5d. For example, in some implementations, the template developing operation 7-304 may include an operation 7-542 for including into each of the one or more templates one or more emulatable aspects that correspond to at least the portion of the one or more reported aspects as depicted in FIG. 7-5a. For instance, the emulatable aspect including module 7-220 (see FIG. 7-2b) of the computing device 7-10 including into each of the one or more templates 7-18 one or more emulatable aspects that correspond to at least the portion of the one or more reported aspects 7-15.

As further illustrated in FIG. 7-5a, operation 7-542 may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 7-542 may include an operation 7-543 for including into each of the one or more templates a plurality of emulatable aspects that correspond to a plurality of reported aspects associated with the one or more source users and that were originally reported by the one or more sensors as depicted in FIG. 7-5a. For instance, the emulatable aspect including module 7-220 of the computing device 7-10 including into each of the one or more templates 7-18 a plurality of emulatable aspects that correspond to a plurality of reported aspects 7-15 associated with the one or more source users 7-2* and that were originally reported by the one or more sensors 7-240*.

In various implementations, operation 7-543 may, in turn, further include an operation 7-544 for defining in each of the one or more templates one or more relationships between the plurality of emulatable aspects included in each of the one or more templates as depicted in FIG. 7-5a. For instance, the relationship defining module 7-222 (see FIG. 7-2b) of the computing device 7-10 defining in each of the one or more templates 7-18 at least one temporal, specific time, or spatial relationship between the plurality of emulatable aspects included in each of the one or more templates 7-18.

In some implementations, operation 7-544 may further include an operation 545 for defining in each of the one or more templates at least one temporal, specific time, or spatial relationship between at least two of the plurality of emulatable aspects included in each of the one or more templates as depicted in FIG. 7-5a. For instance, the relationship defining module 7-222 of the computing device 7-10 defining in each of the one or more templates 7-18 at least one temporal, specific time, or spatial relationship between at least two of the plurality of emulatable aspects included in each of the one or more templates 7-18.

In some cases, the operation 7-542 for including into each of the one or more templates 7-18 one or more emulatable aspects may include an operation 7-546 for determining whether at least one of the one or more emulatable aspects to be included in the one or more templates is a plausible aspect that has been successfully emulated by one or more third parties, and if not plausible, execute one or more actions as depicted in FIG. 7-5a. For instance, the plausible determining module 7-224 (see FIG. 7-2b) of the computing device 7-10 determining whether at least one of the one or more emulatable aspects to be included in the one or more templates 7-18 is a plausible aspect that has been successfully emulated by one or more third parties 7-6, and if not plausible, execute one or more actions (e.g., as executed by an action module 7-226 (see FIG. 7-2b).

Various types of actions may be executed upon a determination of non-plausibility. For example, in some implementations, operation 7-546 may include an operation 7-547 for notifying, in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more templates is not a plausible aspect, at least one of an end user, a source user, and a third party regarding the determination that at least one of the one or more emulatable aspects to be included in the one or more templates is not a plausible aspect as depicted in FIG. 7-5a. For instance, the not plausible notification module 7-228 (see FIG. 7-2b) of the computing device 7-10 notifying (e.g., transmitting or indicating a notification), in response to determining that the at least one of the one or more emulatable aspects to be included in the one or more templates 7-18 is not a plausible aspect, at least one of an end user 7-4*, a source user 7-2*, and a third party 7-6 regarding the determination that at least one of the one or more emulatable aspects to be included in the one or more templates 7-18 is not a plausible aspect.

In the same or different implementations, operation 7-546 may include an operation 7-548 for modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more templates by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties as depicted in FIG. 7-5a. For instance, the template modification module 7-229 (see FIG. 7-2b) of the computing device 7-10 modifying, in response to determining that the at least one of the one or more emulatable aspects is not a plausible aspect, at least one of the one or more templates 7-18 by revising the at least one of the one or more emulatable aspects determined to be not a plausible aspect or by replacing the at least one of the one or more emulatable aspects determined to be not a plausible aspect with at least one replacement emulatable aspect that is a plausible aspect that has been successfully emulated by one or more third parties 7-6. Note that the one or more third parties 7-6, in various implementations, may merely be other end users 7-4* who may have previously attempted to emulate the one or more templates 7-18.

In the same or different implementations, operation 7-546 may include an operation 7-549 for determining whether at least one of the one or more emulatable aspects to be included in the one or more templates is a plausible aspect that has been successfully emulated by the one or more third parties in order to achieve at least one of the one or more target outcomes, and if not plausible, execute the one or more actions as depicted in FIG. 7-5a. For instance, the plausible determining module 7-224 of the computing device 7-10 determining whether at least one of the one or more emulatable aspects to be included in the one or more templates 7-18 is a plausible aspect that has been successfully emulated by the one or more third parties 7-6 in order to achieve at least one of the one or more target outcomes, and if not plausible, execute the one or more actions.

In some cases, the template developing operation 7-304 of FIG. 7-3 may involve identifying from the one or more reported aspects that were provided through operation 7-302, one or more relevant reported aspects 7-16 that were at least originally reported by the one or more sensors 7-240* and that are relevant with respect to achieving the one or more target outcomes. For example, in some implementations, the template developing operation 7-304 may include an operation 7-550 for identifying from the one or more reported aspects one or more relevant reported aspects that were originally reported by the one or more sensors and that are relevant with respect to achieving the one or more target outcomes as depicted in FIG. 7-5b. For instance, the relevant reported aspect identification module 7-230 (see FIG. 7-2b) of the computing device 7-10 identifying from the one or more reported aspects 7-15 one or more relevant reported aspects 7-16 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to achieving the one or more target outcomes.

Various operations may be employed in order to identify the relevant reported aspects 7-16 identified through operation 7-550. For example, in various implementations, operation 7-550 may include an operation 7-551 for identifying from the one or more reported aspects the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported by the one or more sensors and that are associated with one or more source users who have achieved the one or more target outcomes as depicted in FIG. 7-5b. For instance, the relevant reported aspect identification module 7-230 of the computing device 7-10 identifying from the one or more reported aspects 7-15 the one or more relevant reported aspects 7-16 by having the source user associated reported aspect identification module 7-232 identifying one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are associated with one or more source users 7-2* who have achieved the one or more target outcomes.

Operation 7-551, in turn, may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 7-551 may include an operation 7-552 for identifying from the one or more reported aspects the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported by the one or more sensors and that are relevant with respect to one or more relevancy factors as depicted in FIG. 7-5b. For instance, the relevant reported aspect identification module 7-230 of the computing device 7-10 identifying from the one or more reported aspects 7-15 the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect identification module 7-234 identifying one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that are relevant with respect to one or more relevancy factors.

In some implementations, operation 7-552 may further include an operation 7-553 for identifying from the one or more reported aspects the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects that belong to one or more aspect types that are of interest to the one or more end users as depicted in FIG. 7-5b. For instance, the relevant reported aspect identification module 7-230 of the computing device 7-10 identifying from the one or more reported aspects 7-15 the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect identification module 7-234 identifying one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that belong to one or more aspect types that are of interest to the one or more end users 7-4*.

In the same or different implementations, operation 7-552 may include an operation 7-554 for identifying from the one or more reported aspects the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects 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. 7-5b. For instance, the relevant reported aspect identification module 7-230 of the computing device 7-10 identifying from the one or more reported aspects 7-15 the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect identification module 7-234 identifying one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that belong to one or more aspect types that have been indicated by at least one source user 7-2* as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 7-552 may include an operation 7-555 for identifying from the one or more reported aspects the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects 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. 7-5b. For instance, the relevant reported aspect identification module 7-230 of the computing device 7-10 identifying from the one or more reported aspects 7-15 the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect identification module 7-234 identifying one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that belong to one or more aspect types that have been indicated by at least one third party source (e.g. a third party 7-6, a content provider, or a publication) as being relevant to the achievement of the one or more target outcomes.

In the same or different implementations, operation 7-552 may include an operation 7-556 for identifying from the one or more reported aspects the one or more relevant reported aspects by identifying one or more reported aspects that were originally reported by the one or more sensors and that indicate one or more aspects that occurred within one or more predefined time increments, respectively, from one or more achievements of the one or more target outcomes by the one or more source users who have achieved the one or more target outcomes as depicted in FIG. 7-5b. For instance, the relevant reported aspect identification module 7-230 of the computing device 7-10 identifying from the one or more reported aspects 7-15 the one or more relevant reported aspects 7-16 by having the relevancy factor relevant reported aspect identification module 7-234 identifying one or more reported aspects 7-15 that were originally reported by the one or more sensors 7-240* and that indicate one or more aspects that occurred within one or more predefined time increments, respectively, from one or more achievements (e.g., occurrences) of the one or more target outcomes by the one or more source users 7-2* who have achieved the one or more target outcomes.

Various types of templates 7-18 may be developed through the template developing operation 7-304 of FIG. 7-3 in various alternative implementations. For example, in some implementations, the template developing operation 7-304 of FIG. 7-3 may include an operation 7-557 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more health or medical outcomes as depicted in FIG. 7-5c. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more health or medical outcomes (e.g., recover from a particular illness, avoid acquiring certain illnesses such as cancer or influenza, obtain improved physiological traits, improve mental health, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-558 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more athletic outcomes as depicted in FIG. 7-5c. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more athletic outcomes (e.g., finish a marathon, achieve a certain golf score, win a tennis tournament, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-559 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more gaming outcomes as depicted in FIG. 7-5c. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more gaming outcomes (e.g., achieve a certain chase ranking, become proficient at a particular electronic game, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-560 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more occupational outcomes as depicted in FIG. 7-5c. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more occupational outcomes (e.g., finish a work project, get a promotion, develop a certain computer skill, develop a personal work network, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-561 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more social outcomes as depicted in FIG. 7-5c. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more social outcomes (e.g., going out on a date, receive an invitation to join a particular social club, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-562 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more leisure outcomes as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more leisure outcomes (e.g., going to Hawaii on a vacation, setting aside time for a vacation, finish reading a novel, spending time with offspring, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-563 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more sexual intimacy outcomes as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more sexual intimacy outcomes (e.g., increase frequency and quality of sexual intimacy encounters).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-564 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more psychological outcomes as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more psychological outcomes (e.g., develop better self-esteem, be cured of a phobia, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-565 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more intellectual or academic outcomes as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more intellectual or academic outcomes (e.g., achieve a certain score for a test, graduate or be accepted from a particular school, win a particular academic award, and so forth).

In the same or different implementations, the template developing operation 7-304 may include an operation 7-566 for developing the one or more templates including at least one template that is designed to facilitate the one or more end users to achieve one or more user states as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 including at least one template 7-18 that is designed to facilitate one or more end users 7-4* to achieve one or more user states (e.g., be content, be relaxed, be focused, and so forth).

In some cases, the template developing operation 7-304 of FIG. 7-3 may involve developing one or more templates 7-18 based on data provided by sensors 7-240* and data provided by source users 7-2*. For example, in some implementations, the template developing operation 7-304 may include an operation 7-567 for developing the one or more templates based at least on the portion of the one or more reported aspects and on another one or more reported aspects that are associated with the one or more source users and that were originally reported by the one or more source users as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 based at least on the portion of the one or more reported aspects 7-15 and on another one or more reported aspects 7-15 that are associated with the one or more source users 7-2* and that were originally reported by the one or more source users 7-2*.

In some implementations, operation 7-567 may further include an operation 7-568 for developing the one or more templates based at least on the portion of the one or more reported aspects and on another one or more reported aspects that are associated with the one or more source users and that were originally reported by the one or more source users via one or more social networking entries as depicted in FIG. 7-5d. For instance, the template development module 7-104 of the computing device 7-10 developing the one or more templates 7-18 based at least on the portion of the one or more reported aspects 7-15 and on another one or more reported aspects 7-15 that are associated with the one or more source users 7-2* and that were originally reported by the one or more source users 7-2* via one or more social networking entries (e.g., blog entries such as microblog entries, status reports, and so forth).

Referring to FIG. 7-6 illustrating another operational flow 7-600 in accordance with various embodiments. Operational flow 7-600 includes certain operations that mirror the operations included in the operational flow 7-300 of FIG. 7-3. These operations include a sensor originated reported aspect providing operation 7-602 and a template developing operation 7-604 that corresponds to and mirror the sensor originated reported aspect providing operation 7-302 and the template developing operation 7-304, respectively, of FIG. 7-3.

In addition, operational flow 7-300 includes a template presenting operation 7-606 for presenting the one or more templates as depicted in FIG. 7-6. For instance, the presentation module 7-106 of the computing device 7-10 presenting the one or more templates 7-18 to one or more end users 7-4*, to one or more source users 7-2*, to one or more third parties 7-6, or to one or more network servers 7-60.

In some implementations, the template presentation operation 7-606 may include an operation 7-770 for transmitting the one or more templates via at least one of a wireless network and a wired network as depicted in FIG. 7-7. For instance, the transmission module 7-236 of the computing device 7-10 transmitting the one or more templates 7-18 via at least one of a wireless network and a wired network 7-50.

In the same or different implementations, the template presentation operation 7-606 may include an operation 7-771 for indicating the one or more templates via a user interface as depicted in FIG. 7-7. For instance, the user interface indication module 7-238 indicating (e.g., displaying or audibly indicating) the one or more templates 7-18 via a user interface 7-120 (e.g., a display monitor, a touch screen, and/or one or more audio speakers).

Turning now to FIG. 7-8, which is a high-level block diagram illustrating a particular implementation of the computing device 7-10 of FIG. 7-1b. As illustrated, the computing device 7-10 may include a processor 7-802 (e.g., microprocessor, controller, and so forth) coupled to storage medium 7-806 (e.g., volatile or non-volatile memory). The storage medium 7-806 may store computer readable instructions 7-804 (e.g., computer program product). The processor 7-802, in various implementations, may execute the computer readable instructions 7-804 in order to execute one or more operations described above and as illustrated in FIGS. 7-3, 7-4a, 7-4b, 7-4c, 7-4d, 7-4e, 7-4f, 7-5a, 7-5b, 7-5c, and 7-5d.

For example, the processor 7-802 may execute the computer readable instructions 7-804 in order to provide one or more reported aspects 7-15 associated with one or more source users 7-2* that were originally reported by one or more sensors 7-240*; and/or to develop one or more templates 7-18 designed to facilitate one or more end users 7-4* to achieve one or more target outcomes when one or more emulatable aspects indicated by the one or more templates 7-18 are emulated, the development of the one or more templates 7-18 being based at least on a portion of the one or more reported aspects 7-15 as illustrated by the operational flow 7-300 of FIG. 7-3.

IX. Source User Based Provision of One or More Templates

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 journal. One place where such open journals 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, 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 become very popular in recent times 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 journals 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.

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 their usage. 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).

Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, and so forth) are now available through these 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 sites making it even more difficult to exploit such potentially useful data.

In various embodiments, methods, systems, circuitry, and computer program products are provided for selectively providing from a plurality of templates one or more particular or specific templates that are associated with one or more source users and that are 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 templates are emulated. In some embodiments, the one or more templates to be provided may have been originally developed based on log data associated with the one or more source users and provided through, for example, social networking channels (e.g., blogs, microblogs, and so forth). Note that the phrases “particular template” and “particular templates” will be used merely in reference to templates that are to be provided.

In some cases, the plurality of templates that the one or more particular templates are provided (e.g., acquired or identified) from may be stored in a memory and/or located at one or more network locations (e.g., servers, client devices, and so forth). In some embodiments, the methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, a network device such as a server (e.g., network servers) or a local client device (e.g., a source user device or an end user device).

In various embodiments, the one or more templates that are provided by the methods, systems, circuitry, and computer program products may be presented to, for example, one or more end users to be used directly by the one or more end users in order to achieve the one or more target outcomes. Alternatively, the one or more provided templates may be further processed in order to generate one or more personalized templates (i.e., personalized plans) designed for use specifically by one or more particular end users. 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. The one or more emulatable aspects that may be included in the template may be based on and correspond to one or more reported aspects of one or more source users, who may or may not be the source for the one or more reported aspects. That is, a reported aspect may be reported by 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 indicated above, a template may comprise of one or more emulatable aspects that may be based on reported aspects of a particular source user. Note that the word “emulatable” as used herein has no significant meaning, but instead is used here to merely distinguish those aspects (emulatable aspects) indicated in a template from other types of aspects (e.g., reported aspects). 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 achieve medical or health related outcomes, to achieve athletic or gaming outcomes, to achieve particular user states such as mental or social states, to achieve intellectual or academic outcomes, and so forth.

In some cases, a template may indicate a collection of one or more activities (e.g., one or more emulatable aspects) or may indicate a more precise schedule of activities (e.g., emulatable aspects) that an end user may emulate in order to achieve a target outcome or outcomes. For example, if a template is designed to facilitate an end user 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) the end user may need to execute in order to achieve the weight loss. Similarly, if the template is designed to, for example, facilitate an end user 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) the end user may need to execute in order to achieve the high test score for the SAT. Note that in some instances a template may include one or more emulatable intermediate outcomes that are associated with 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 an end user 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 other cases, a template may merely be a collection of one or more emulatable aspects that does not define any 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.

In some embodiments, each template that may be developed 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.

Since there is a large volume of personal data already potentially available for use in the form of log entry data (e.g., as provided through social networking channels), the amount of templates that could be developed based on such data could be enormous. Each template developed may at least be associated with a specific source user and/or with a specific target outcome. The templates may also be spread across, for example, multiple communication networks (e.g., wireless networks and/or wired networks) at multiple network sites. Thus, trying to find a particular template associated with, for example, a particular source user and/or a particular target outcome could become a daunting and cumbersome task. Thus, in some embodiments, dynamic methods, systems, circuitry, and computer program products are provided that facilitate in the finding and/or providing of one or more selective templates from a plurality of templates that may be associated with multiple source users and/or multiple target outcomes.

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. In brief, and as will be further described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, 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, 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 that has been reported by, for example, the source user, by one or more sensors, or by one or more third parties (e.g., other source 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, an end user. 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 who is a direct or indirect beneficiary of one or more templates. 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. 8-1a, and 8-1b 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 8-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 8-10 may be a server such as one of the one or more network servers 8-60 illustrated in FIG. 8-1a. Alternatively, the computing device 8-10 may be a source user device such as one of the local source user devices 8-20* illustrated in FIG. 8-1a. In still other embodiments, the computing device 8-10 may be an end user device such as one of the local end user device 8-30* illustrated in FIG. 8-1a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 8-2*” may be in reference to a source user 8-2a, a source user 8-2b, and so forth.

Note that for ease of understanding and explanation, the computing device 8-10 of the exemplary environment 8-100 of FIGS. 8-1a and 8-1b will be generally described in the following discussion 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 8-100 of FIG. 8-1a and 8-1b assumes that the computing device 8-10 is a server, the following discussion will, for the most part, be applicable even if the computing device 8-10 is operating as an end user device (e.g., local end user device 8-30*) or as a source user device (e.g., local source user device 8-20*) with certain obvious exceptions (e.g., if the computing device 8-10 is an end user device or a source user device rather than a server, the computing device 8-10 may communicate with an end user 8-4* or a source user 8-2* directly through a user interface 8-120 rather than indirectly through one or more communication networks 8-50 as may be the case when the computing device 8-10 is a server). In some embodiments, the computing device 8-10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 8-1a and 8-1b, and as previously indicated, the computing device 8-10 may be a network device such as a server (e.g., a network server 8-60) that is designed to communicate with other network devices. For example, the computing device 8-10 may communicate with one or more source users 8-2*(e.g., source user 8-2a, source user 8-2b, and so forth) through one or more local source user devices 8-20*(e.g., local source user device 8-20a, local source user device 8-20b, and so forth), with one or more end users 8-4*(e.g., end user 8-4a, end user 8-4b, and so forth) through one or more local end user devices 8-30*(e.g., local end user device 8-30a, local end user device 8-30b, and so forth), with one or more sensor integrated devices 8-40 (e.g., a transportation vehicle such as a car, an exercise machine, or any other type of device that may have an integrated sensor designed to sense, for example, usage), with one or more network servers 8-60, and/or with one or more third parties 8-6 (e.g., one or more content providers, one or more network service providers, and/or one or more other parties) via one or more communication networks 8-50. In various implementations, the one or more communication networks 8-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 various embodiments, the computing device 8-10 may be designed to, among other things, receive one or more requests 8-16 for one or more particular templates 8-18 that are associated with one or more source users 8-2*, the one or more particular templates 8-18 designed to facilitate one or more end users 8-2* to achieve one or more target outcomes 8-14 (see FIG. 8-2b illustrating one perspective of a template 8-17, which may also be a particular template 8-18) when one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated. For these embodiments, the one or more requests 8-16 may be received from a variety of requesting sources including, for example, one or more end users 8-4*, one or more third parties 8-6, and/or one or more network servers 8-60. In some embodiments, such as in embodiments in which the computing device 8-10 is a server, the one or more requests 8-16 may be indirectly received from a requesting source via the one or more communication networks 8-50. In other embodiments, such as in embodiments in which the computing device 8-10 is, for example, an end user device, the one or more requests 8-16 may be received directly from a requesting source (e.g., end user 8-4*) via a user interface 8-120. In various embodiments, the one or more requests 8-16 may include data that may identify the one or more source users 8-2*(e.g., one or more source users 8-2* who may have achieved the one or more target outcomes 8-14. In some embodiments, the one or more requests 8-16 may include other data such as data that indicates the one or more target outcomes 8-14.

In response to receiving the one or more requests 8-16, the computing device 8-10 may be designed to selectively provide the requested one or more particular templates 8-18 from a plurality of templates 8-17, the providing of the one or more particular templates 8-18 being based at least on the association of the one or more particular templates 8-18 with the one or more source users 8-2*, the one or more particular templates 8-18 developed (e.g., previously created) based on one or more reported aspects 8-15 associated with the one or more source users 8-2*. In some embodiments, the computing device 8-10 may be designed to develop the plurality of templates 8-17 including the one or more particular templates 8-18 based on reported aspects 8-15 that may be acquired from one or more sources including, for example, one or more local source user devices 8-20*, one or more sensor integrated devices 8-40, one or more third parties 8-6, and/or one or more network servers 8-60. In some embodiments, the computing device 8-10 may be designed to present the one or more templates 8-17 via user interface 8-120 and/or via one or more communication networks 8-50.

In some embodiments, the one or more particular templates 8-18 that are provided may be presented by, for example, transmitting the one or more particular templates 8-18 to one or more network servers 8-60, to one or more source users 8-2* (e.g., one or more local source user devices 8-20*), to one or more end users 8-4*(e.g., one or more local end user devices 8-30*), and/or to one or more third parties 8-6. In some embodiments where, for example, the computing device 8-10 is a source user device or an end user device, the computing device 8-10 may indicate (e.g., visually display or audibly indicate) the one or more particular templates 8-18 via a user interface 8-120.

In embodiments in which the computing device 8-10 is designed to receive reported aspects 8-15, the computing device 8-10 may randomly, semi-continuously, or continuously receive reported aspects 8-15 associated with one or more source users 8-2*. Such reported aspects 8-15 may indicate a variety of aspects (e.g., behavior aspects such as user activities, user states, environmental conditions, and so forth) associated with the one or more source users 8-2*.

In embodiments in which the computing device 8-10 is configured to develop, for example, one or more particular templates 8-18 that is designed to facilitate achievement of one or more target outcomes 8-14, the one or more particular templates 8-18 may be developed by, for example, determining which of the acquired reported aspects 8-15 may be relevant to achieving the one or more target outcomes 8-14, and include into the one or more particular templates 8-18 one or more emulatable aspects 8-12 that correspond (e.g., equivalent) to one or more reported aspects 8-15 that have been determined to be relevant to achieving the one or more target outcomes 8-14. Note that throughout the following discussion, reference number 8-18 will be used in connection with the one or more particular templates 8-18 that are requested and provided, while reference number 8-17 will be used with respect to the general population or group of templates 8-17 that the one or more particular templates 8-18 are provided from.

In various embodiments, the computing device 8-10, as previously indicated, may be a server (e.g., one of the one or more network servers 8-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 8-10 is a source user device (e.g., local source user device 8-20*) or an end user device (e.g., local end user device 8-30*) rather than a network server 8-60, the computing device 8-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 8-100 of FIGS. 8-1a and 8-1b, the one or more sensor integrated devices 8-40 of the exemplary environment 8-100 of FIGS. 8-1a and 8-1b may directly communicate with the one or more communication networks 8-50 in various embodiments. Alternatively, the one or more sensor integrated devices 8-40 may indirectly communicate with the one or more communication networks 8-50 via the one or more local source user devices 8-20*(e.g., via, for example, personal area network or PAN). In various embodiments, a sensor integrated device 8-40 may be a variety of devices that may comprise of one or more sensors 8-240 and that may be operated or used by a source user 8-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 8-240, which may also be included in the one or more local source user devices 8-20* and/or the computing device 8-10, may include any type of sensors 8-240 that can sense one or more aspects of a source user 8-2*. Examples of such sensors 8-240 include, for example, sensors 8-240 that can sense various physical characteristics of a source user 8-2*(e.g., heart rate sensor or blood pressure sensor), sensors 8-240 that can sense activities of a source user 8-2*(e.g., a pedometer, an accelerometer, and so forth), sensors 8-240 that can sense environment conditions (e.g., air quality sensors), sensors 8-240 that can sense the location of a source user 8-2*(e.g., global positioning system or GPS), sensors 8-240 that can provide physiological data that may be processed in order to determined inferred mental states of users, and so forth.

Each of the one or more local source user devices 8-20* and each of the one or more local end user devices 8-30*(as well as the computing device 8-10 in embodiments in which the computing device 8-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 8-20* and/or the one or more local end user devices 8-30*(as well as the computing device 8-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 8-20* and/or local end user device 8-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 8-10 as illustrated in FIG. 8-1b may include one or more modules, sub-modules, and various other components. As shown, the computing device 8-10 may include at least a request receiving module 8-102 (which may further include a network receiving module 8-202 and/or a user interface receiving module 8-204) and a particular template providing module 8-104 (which may further include one or more sub-modules as illustrated in FIG. 8-2a). In various embodiments, the computing device 8-10 may further include a source user identification data interpreting module 8-103, a template developing module 8-105, a presentation module 8-106 (which may further include a transmission module 8-236 and/or a user interface indication module 8-238) and a memory 8-116 (which may store a plurality of templates 8-17, one or more end user trait indications 8-138, one or more end user limitation indications 8-140, one or more end user relevancy indications 8-142, one or more source user relevancy indications 8-144, one or more third party source relevancy indications 8-145, one or more predefined time increment indications 8-146, and/or one or more applications 8-140).

The computing device 8-10 may also include, in various embodiments, a network interface 8-118 (e.g., a network interface card or NIC), a user interface 8-120, a social networking entry reception module 8-110 (which may further include a blog entry reception module 8-111 and/or a status report reception module 8-112), and/or one or more sensors 8-240. In some cases, the presence or absence of some of these modules and sub-modules may depend on, for example, whether the computing device 8-10 is a server, an end user device, or a source user device. For example, if the computing device 8-10 is a server, then the computing device 8-10 may not include a user interface 8-120.

Referring particularly now to the request receiving module 8-102, the request receiving module 8-102 may be configured to, among other things, receive one or more requests 8-16 for one or more particular templates 8-18 that are associated with one or more source users 8-2*, the one or more particular templates 8-18 designed to facilitate one or more end users 8-4* to achieve one or more target outcomes 8-14 when one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated. In contrast, the particular template providing module 8-104 may be configured to, among other things, provide from a plurality of templates 8-17 the one or more particular templates 8-18, the providing being based at least on the association of the one or more particular templates 8-18 with the one or more source users 8-2*, the one or more particular templates 8-18 developed based on one or more reported aspects 8-15 related to the one or more source users 8-2*.

The memory 8-116 may be designed to store various data including a plurality of templates 8-17, which may have been developed based on reported aspects 8-15 associated with one or more source users 8-2*. Other types of data may also be stored in the memory 8-116 in various implementations including, for example, one or more end user trait indications 8-138 (e.g., one or more indications that indicate one or more traits of one or more end users 8-4*), one or more end user limitation indications 8-140 (e.g., one or more indications that indicate limitations associated with one or more end users 8-4* including contextual limitations, physical limitations, legal limitations, and so forth), one or more end user relevancy indications 8-142 (e.g., one or more indications that indicate the types of reported aspects 8-15 that an end user 8-4 has an interest in or believes is relevant to achieving one or more target outcomes 8-14) and/or one or more source user relevancy indications 8-144 (e.g., one or more indications provided by a source user 8-2* that indicate at least which types of reported aspects 8-15 are relevant to achieving one or more target outcomes 8-14).

In some cases, the memory 8-116 may also include, for example, one or more third party source relevancy indications 8-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 8-6 that indicate at least which types of reported aspects 8-15 are relevant to achieving one or more target outcomes 8-14), one or more predefined time increment indications 8-146 (e.g., one or more indications that indicate the lengths of time that may be allotted for executing one or more templates 8-17), and/or one or more applications 8-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). In various implementations, the memory 8-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 source user identification data interpreting module 8-103 may be configured to process and interpret identification data that may be included in a request 8-16 received by the request receiving module 8-102. By interpreting the identification data (which, in some cases, may be in the form of RFID data, location data, image data, and so forth), one or more source users 8-2* may be identified or determined.

In various implementations, the presentation module 8-106 may be configured to present one or more particular templates 8-18 provided by the particular template providing module 8-104. The transmission module 8-236 that may be included in the presentation module 8-106 may be designed to transmit the one or more particular templates 8-18 provided by the particular template providing module 8-104 via the one or more communication networks 8-50. The user interface indication module 8-238, in contrast, may be designed to indicate the one or more particular templates 8-18 via a user interface 8-120 (e.g., display monitor, speaker system, touch screen, and so forth).

The social networking entry reception module 8-110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 8-2*, from one or more end users 8-4*, from one or more third parties 8-6, from one or more sensor integrated devices 8-40, and/or from one or more network servers 8-60. The social networking entry reception module 8-110 may further include a blog entry reception module 8-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 8-112 for receiving social networking status reports. The user interface 8-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. 8-2 a illustrates particular implementations of the particular template providing module 8-104 of the computing device 8-10 of FIG. 8-1b. As illustrated, the particular template providing module 8-104 may include, in various implementations, one or more sub-modules. For example, in some implementations, the particular template providing module 8-104 may include a memory template acquiring module 8-202 and/or a network template acquiring module 8-204 (which may further include a solicitation transmitting module 8-206). In brief, the memory template acquiring module 8-202 may be designed to acquire from the memory 8-116 the one or more particular templates 8-18 that are to be provided. In contrast, the network template acquiring module 8-204 may be designed to acquire from the one or more communication networks 8-50, the one or more particular templates 8-18 that are to be provided. In some cases, the network template acquiring module 8-204 may further include a solicitation transmitting module 8-206 configured to transmit one or more solicitations for the one or more particular templates 8-18.

FIG. 8-2 b illustrates one perspective of a particular template 8-18 (or template 8-17). In particular, FIG. 8-2b shows the types of data that may be included in or be associated with a particular template 8-18. In various implementations, a particular template 8-18 (or template 8-17) may include data that indicates, for example, one or more emulatable aspects 8-12, one or more target outcomes 8-14 (which in some cases may be one or more of the emulatable aspects 8-12), one or more source user identifiers 8-226 (for identifying at least one source user 8-2* associated with the particular template 8-18), one or more source user traits 8-228 (indicates one or more traits of the source user 8-2* who is associated with the particular template 8-18), and/or a template time increment 8-230 (represents the amount of time it will take to fully emulate or execute the particular template 8-18). Note that FIG. 8-2b is provided for purposes of merely showing the types of data that may be included in or associated with a particular template 8-18 (or template 8-17) and is not meant to be an actual representation of a particular template 8-18 (or template 8-17).

In embodiments in which the particular template 8-18 includes data that indicate multiple emulatable aspects 8-12, the particular template 8-18 may also include data that defines the relationship (e.g., temporal, specific time, and/or spatial relationships) between the emulatable aspects. Also, when the particular templates 8-18 indicates multiple emulatable one or more of the emulatable aspects 8-12 may be one or more emulatable intermediate outcomes that are associated with the one or more target outcomes 8-14 of the particular template 8-18. For example, if a target outcome for a particular template 8-18 is to lose 20 pounds of body weight in two months, than an emulatable intermediate outcome may be, for example, 10 pounds of body weight loss after one month of emulating the particular template 8-18.

Referring back to the computing device 8-10 of FIG. 8-1b, the various modules (e.g., the request receiving module 8-102, the particular template providing module 8-104, and so forth) along with their sub-modules included in the computing device 8-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the request receiving module 8-102 and/or the particular template providing module 8-104 may be implemented with a processor 8-802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 8-804 (e.g., computer program product) stored in a storage medium 8-806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 8-10 of FIG. 8-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 discussion relating to the functional aspects of the computing device 8-10 of FIG. 8-1b and its components will now be provided with respect to the processes and operations to be described herein. FIG. 8-3 illustrates an operational flow 8-300 representing example operations directed to, among other things, provide from a plurality of templates 8-17 one or more particular templates 8-18 that are associated with one or more source users 8-2* and that are designed to facilitate one or more end users 8-4* to achieve one or more target outcomes 8-14 when one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated, the providing of the one or more particular templates 8-18 being based, at least in part, on their association with the one or more source users 8-2*.

In FIG. 8-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 8-100 described above as illustrated in FIGS. 8-1a and 8-1b, and/or with respect to other examples (e.g., as provided in FIGS. 8-2a and 8-2b) 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. 8-1a, 8-1b, 8-2a, and 8-2b. 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. 8-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 8-300 may move to a request receiving operation 8-302 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. For instance, and as an illustration, the request receiving module 8-102 of the computing device 8-10 of FIG. 8-1b receiving (e.g., from one or more communication networks 8-50 and/or via a user interface 8-120) one or more requests 8-16 (e.g., solicitations, queries, and so forth) for one or more particular templates 8-18 that are associated with one or more source users 8-2*, the one or more particular templates 8-18 designed to facilitate one or more end users 8-4* to achieve one or more target outcomes 8-14 when one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated. In various implementations, the one or more source users 8-2* who are associated with the one or more particular templates 8-18 may have previously achieved the one or more target outcomes 8-14 and may be the source for the data (e.g., reported aspects 8-15) used to develop the one or more particular templates 8-18.

In addition to the request reception operation 8-302, operational flow 8-300 may also include a template providing operation 8-304 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. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 the one or more particular templates 8-18, the providing of the one or more particular templates 8-18 being based at least on the association of the one or more particular templates 8-18 with the one or more source users 8-2*, the one or more particular templates 8-18 developed based on one or more reported aspects 8-15 associated with the one or more source users 8-2*. As will be further described herein, both the request receiving operation 8-302 and the template providing operation 8-304 of FIG. 8-3 may be executed in a number of different ways in various alternative implementations.

For example, FIGS. 8-4a, 8-4b, and 8-4c illustrate the various ways that the request reception operation 8-302 of FIG. 8-3 may be executed in various alternative implementations. For instance, the one or more requests 8-16 received through the request receiving operation 8-302 may be received from a variety of sources in a variety of different ways. For example, in some implementations, the request receiving operation 8-302 of FIG. 8-3 may include an operation 8-402 for receiving the one or more requests from at least one end user as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 of FIG. 8-1b receiving (e.g., via one or more communication networks 8-50 or via user interface 8-120) the one or more requests 8-16 from an end user 8-4*. Alternatively, the one or more requests 8-16 may be received from other sources such as from one or more third parties (e.g., network service providers) or from one or more network servers 8-60.

In the same or different implementations, the request receiving operation 8-302 may include an operation 8-403 for receiving the one or more requests via one or more communication networks as depicted in FIG. 8-4a. For instance, the network receiving module 8-202 of the computing device 8-10 receiving the one or more requests 8-16 via one or more communication networks 8-50 (e.g., a wireless network and/or a wired network).

In some implementations, the request receiving operation 8-302 may include an operation 8-404 for receiving the one or more requests via a user interface as depicted in FIG. 8-4a. For instance, the user interface receiving module 8-204 of the computing device 8-10 receiving the one or more requests 8-16 via a user interface 8-120.

In some implementations, the request reception operation 8-302 may include an operation 8-405 for receiving the one or more requests including one or more requests for one or more particular templates that are associated with one or more source users who have achieved the one or more target outcomes as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 for one or more particular templates 8-18 that are associated with one or more source users 8-2* who have achieved the one or more target outcomes 8-14.

Various types of information may be included in the one or more requests 8-16 to be received through the request receiving operation 8-302 of FIG. 8-3. For example, in some implementations, the request receiving operation 8-302 may include an operation 8-406 for receiving the one or more requests including one or more requests that indicate the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate the one or more source users 8-2*. For example, in some cases the one or more requests 8-16 may include identification data that may facilitate in identifying the one or more source users 8-2*.

For example, in some implementations, operation 8-406 may include an operation 8-407 for receiving the one or more requests including one or more requests that include identification data to identify at least one of the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that include identification data to identify at least one of the one or more source users 8-2*. Various types of data may be included in the one or more requests 8-16 in order to facilitate in the identification of at least one of the one or more source users 8-2* in various alternative implementations.

For example, in some implementations, operation 8-407 may include an operation 8-408 for receiving the one or more requests including one or more requests that include image data to identify at least one of the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that include image data (e.g., as recorded by a digital camera or camcorder) to identify at least one of the one or more source users 8-2*.

In the same or different implementations, the operation 8-407 may include an operation 8-409 for receiving the one or more requests including one or more requests that include location data to identify at least one of the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that include location data (e.g., geographical location data as provided by a GPS device) to identify at least one of the one or more source users 8-2*. Note that since multiple source users 8-2* may be at or near the same geographical location at any given moment in time, additional data may be needed in order to identify at least one of the one or more source users 8-2*.

In the same or different implementations, the operation 8-407 may include an operation 8-410 for receiving the one or more requests including one or more requests that include radio frequency identification (RFID) data to identify at least one of the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that include radio frequency identification (RFID) data to identify at least one of the one or more source users 8-2*. For example, in some implementations, source users 8-2* may choose to wear RFID tags in order to be identified without having to provide personal information such as their actual name or having their privacy intruded upon.

In the same or different implementations, the operation 8-407 may include an operation 8-411 for receiving the one or more requests including one or more requests that include audio data to identify at least one of the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that include audio data (e.g., voice data) to identify at least one of the one or more source users 8-2*.

In the same or different implementations, the operation 8-407 may include an operation 8-412 for receiving the one or more requests including one or more requests that include username data to identify at least one of the one or more source users as depicted in FIG. 8-4a. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that include username data (e.g., indicating one or more social networking usernames or an actual name) to identify at least one of the one or more source users 8-2*.

In order to identify the one or more source users 8-2*, identification data that in some cases may be included in the one or more requests 8-16 may be processed and interpreted. For example, in some implementations operation 8-407 may include an operation 8-413 for interpreting the identification data to identify the one or more source users as depicted in FIG. 8-4a. For instance, the source user identification data interpretation module 8-103 of the computing device 8-10 interpreting the identification data to identify the one or more source users 8-2*.

In some implementations, the request receiving operation 8-302 may include an operation 8-414 for receiving the one or more requests including one or more requests that indicate one or more source user groups as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more source user groups (e.g., social networking groups, academic groups, employment groups, business groups, athletic groups, and so forth).

In order to facilitate in selectively providing the one or more particular templates 8-18, the one or more requests 8-16 received through the request receiving operation 8-302 of FIG. 8-3 may include other information other than source user identification data. For example, in some implementations, the request receiving operation 8-302 may include an operation 8-415 for receiving the one or more requests including one or more requests that indicate one or more traits associated with at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more traits associated with at least one end user 8-4*. By including such information into the one or more requests 8-16, only templates 8-17 that are associated with source users 8-2* who have, for example, common traits with the at least one end user 8-4* may be provided.

Various types of user traits may be indicated by the one or more requests 8-16 that are received through operation 8-415 in various alternative implementations. For example, in some implementations, operation 8-415 may include an operation 8-416 for receiving the one or more requests including one or more requests that indicate one or more health or medical traits associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more health or medical traits (e.g., a particular illness or affliction such as stomach cancer or participating in a particular medical treatment such as chemotherapy) associated with the at least one end user 8-4*.

In the same or different implementations, operation 8-415 may include an operation 8-417 for receiving the one or more requests including one or more requests that indicate one or more physical or mental traits associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more physical or mental traits (e.g., being overweight, being short, having high blood pressure, inflicted with a particular phobia, being angry, and so forth) associated with the at least one end user 8-4*.

In the same or different implementations, operation 8-415 may include an operation 8-418 for receiving the one or more requests including one or more requests that indicate one or more fitness or athletic traits associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more fitness or athletic traits (e.g., being able to run a marathon under 8-3 hours) associated with the at least one end user 8-4*.

In the same or different implementations, operation 8-415 may include an operation 8-419 for receiving the one or more requests including one or more requests that indicate one or more academic or intellectual traits associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more academic or intellectual traits (e.g., having previously failed a particular exam or having an IQ under 120) associated with the at least one end user 8-4*.

In the same or different implementations, operation 8-415 may include an operation 8-420 for receiving the one or more requests including one or more requests that indicate one or more social or employment states associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more social or employment states (e.g., being unmarried or unemployed) associated with the at least one end user 8-4*.

In the same or different implementations, operation 8-415 may include an operation 8-421 for receiving the one or more requests including one or more requests that indicate one or more ethnic or gender traits associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more ethnic or gender traits (e.g., being Asian, being a female, and so forth) associated with the at least one end user 8-4*.

In the same or different implementations, operation 8-415 may include an operation 8-422 for receiving the one or more requests including one or more requests that indicate one or more religious or spiritual traits associated with the at least one end user as depicted in FIG. 8-4b. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more religious or spiritual traits (e.g., being a Hindu or Scientologist) associated with the at least one end user 8-4*.

In some cases, the one or more requests 8-16 received through the request receiving operation 8-302 of FIG. 8-3 may indicate the types of emulatable aspects 8-12 that at least one of the end users 8-4* may have an interest in. By providing such information, only templates 8-17 that are associated with the one or more source users 8-2* and that include emulatable aspects 8-12 that are of interest to the at least one of the end users 8-4* may be provided. For example, in some implementations, the request receiving operation 8-302 of FIG. 8-3 may include an operation 8-423 for receiving the one or more requests including one or more requests that indicate one or more types of aspects that are of interest to at least one end user as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more types of aspects (e.g., dietary activities or mental states) that are of interest to at least one end user 8-4*.

In some cases, the one or more requests 8-16 received through the request receiving operation 8-302 of FIG. 8-3 may include information that indicate certain limitations associated with one or more end users 8-4*. Such information may be used in order to prevent from being provided those templates 8-17 that include emulatable aspects 8-12 that may conflict with the limitations associated with the one or more end users 8-4*. For example, various implementations, the request receiving operation 8-302 of FIG. 8-3 may include an operation 8-424 for receiving the one or more requests including one or more requests that indicate one or more limitations associated with at least one end user as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more limitations (e.g., being a vegan) associated with at least one end user 8-4*.

Various types of end user limitations may be indicated by the one or more requests 8-16. For example, in some implementations, operation 8-424 may include an operation 8-425 for receiving the one or more requests including one or more requests that indicate one or more physical limitations associated with the at least one end user as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more physical limitations (e.g., has poor eyesight or hearing, or unable to walk) associated with the at least one end user 8-4*.

In some implementations, operation 8-424 may include an operation 8-426 for receiving the one or more requests including one or more requests that indicate one or more contextual limitations associated with the at least one end user as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more contextual limitations (e.g., logistical limitations such as no access to a swimming pool) associated with the at least one end user 8-4*.

In some implementations, operation 8-424 may include an operation 8-427 for receiving the one or more requests including one or more requests that indicate one or more personal limitations associated with the at least one end user as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate one or more personal limitations (e.g., won't participate in activities with in-laws) associated with the at least one end user 8-4*.

In some implementations, operation 8-424 may include an operation 8-428 for receiving the one or more requests including one or more requests that indicate one or more legal or regulatory limitations associated with the at least one end user as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate the one or more requests 8-16 including one or more requests 8-16 that indicate one or more legal or regulatory limitations (e.g., cannot use certain medications or cannot chew gum) associated with the at least one end user 8-4*.

In some implementations, the request receiving operation 8-302 of FIG. 8-3 may include an operation 8-429 for receiving the one or more requests including one or more requests that indicate at least one predefined time increment that is of interest as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate at least one predefined time increment that is of interest to, for example, an end user 8-4* or a third party 8-6. Such information may be used in order to exclude, for example, templates 8-17 that takes more time to execute than the predefined time increment indicated by the one or more requests 8-16. For example, if an end user wishes to lose 20 pounds in a month, templates 8-17 for losing 20 pounds that takes more than one month to execute may be excluded from being provided.

In some implementations, the request receiving operation 8-302 of FIG. 8-3 may include an operation 8-430 for receiving the one or more requests including one or more requests that indicate at least one of the one or more target outcomes as depicted in FIG. 8-4c. For instance, the request receiving module 8-102 of the computing device 8-10 receiving the one or more requests 8-16 including one or more requests 8-16 that indicate at least one of the one or more target outcomes 8-14.

Referring back to FIG. 8-3, the template providing operation 8-304 may be implemented in a number of different ways in various implementations. For example, in some implementations, the template providing operation 8-304 may include an operation 8-531 for acquiring the one or more particular templates from a plurality of templates stored in a memory as depicted in FIG. 8-5a. For instance, the memory template acquiring module 8-202 of the computing device 8-10 acquiring the one or more particular templates 8-18 from a plurality of templates 8-17 stored in a memory 8-116 (e.g., volatile and/or non-volatile memory).

In the same or different implementations the template providing operation 8-304 may include an operation 8-532 for acquiring the one or more particular templates from a plurality of templates located at one or more network sites as depicted in FIG. 8-5a. For instance, the network template acquiring module 8-204 (see FIG. 8-2a) of the computing device 8-10 acquiring the one or more particular templates 8-18 from a plurality of templates 8-17 located at one or more network sites. Note that in order to avoid confusion, the computing device 8-10 of FIGS. 8-1a and 8-1b is not shown acquiring the one or more particular templates 8-18 as is the case in operation 8-532 but instead is only depicted as transmitting the one or more particular templates 8-18 in order to, for example, present the one or more particular templates 8-18.

Operation 8-532 may, in turn, further include an operation 8-533 for transmitting one or more solicitations via one or more communication networks to solicit for the one or more particular templates, the one or more solicitations indicating at least the one or more source users as depicted in FIG. 8-5a. For instance, the solicitation transmitting module 8-206 (see FIG. 8-2a) of the computing device 8-10, when the computing device 8-10 is an end user device, transmitting one or more solicitations via one or more communication networks 8-50 to solicit for the one or more particular templates 8-18, the one or more solicitations indicating at least the one or more source users 8-2*. Note again that for purpose of clarity and ease of illustration, FIGS. 8-1a and 8-1b do not show the one or more solicitations being transmitted by the computing device 8-10.

In various cases, the plurality of templates 8-17 that the one or more particular templates 8-18 may be provided from may be associated with a plurality of source users 8-2*. For example, in the same or different implementations, the template providing operation 8-304 of FIG. 8-3 may include an operation 8-534 for providing the one or more particular templates from a plurality of templates that include at least a first one or more templates associated with a first source user and at least a second one or more templates associated with a second source user as depicted in FIG. 8-5a. For instance, the particular template providing module 8-104 of the computing device 8-10 providing the one or more particular templates 8-18 from a plurality of templates 8-17 that include at least a first one or more templates 8-17 associated with a first source user 8-2a and at least a second one or more templates 8-17 associated with a second source user 8-2b.

In the same or different implementations, the template providing operation 8-304 of FIG. 8-3 may include an operation 8-535 for providing the one or more particular templates from a plurality of templates that include at least a first one or more templates that are associated with the one or more target outcomes and a second one or more templates that are not associated with the one or more target outcomes as depicted in FIG. 8-5a. For instance, the particular template providing module 8-104 of the computing device 8-10 providing the one or more particular templates 8-18 from a plurality of templates 8-17 that include at least a first one or more templates 8-17 that are associated with the one or more target outcomes 8-14 and a second one or more templates 8-17 that are not associated with the one or more target outcomes 8-14.

In the same or different implementations, the template providing operation 8-304 of FIG. 8-3 may include an operation 8-536 for providing from the plurality of templates the one or more particular templates associated with the one or more source users, the one or more source users having achieved the one or more target outcomes as depicted in FIG. 8-5a. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 associated with the one or more source users 8-2*, the one or more source users 8-2* having achieved the one or more target outcomes 8-14.

In some implementations, operation 8-536 may further include an operation 8-537 for providing from the plurality of templates two or more templates associated with two or more source users including a first template associated with a first source user who has achieved the one or more target outcomes and a second template associated with a second source user who has achieved the one or more target outcomes as depicted in FIG. 8-5a. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 two or more templates 8-17 associated with two or more source users 8-2* including a first template 8-17 associated with a first source user 8-2a who has achieved the one or more target outcomes 8-14 and a second template 8-17 associated with a second source user 8-2b who has also achieved the one or more target outcomes 8-14.

In some implementations, the template providing operation 8-304 of FIG. 8-3 may include an operation 8-538 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that include one or more emulatable aspects that are based on one or more reported aspects associated with the one or more source users as depicted in FIG. 8-5a. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that include one or more emulatable aspects 8-12 that are based on one or more reported aspects 8-15 (e.g., as reported through microblog entries or status reports) associated with the one or more source users 8-2*.

The one or more particular templates 8-18 provided through the template providing operation 8-304 of FIG. 8-3 may be at least linked to the one or more source users 8-2*. For example, in various implementations, the template providing operation 8-304 may include an operation 8-539 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to the one or more source users as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing (e.g., acquiring, finding, or identifying) from the plurality of templates 8-17 one or more particular templates 8-18 that are linked (e.g., associated with) to at least the one or more source users 8-2*. In some cases, the one or more particular templates 8-18 may be linked to the one or more source users 8-2* by including or being hyperlinked to one or more source user identifiers 8-226 (see FIG. 8-2b) such as a name, an image, a location (which may be continuously updated), and so forth, that matches with identifiers for the one or more source users 8-2*.

In various implementations, operation 8-539 may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 8-539 may include an operation 8-540 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to (e.g., associated with) the one or more target outcomes 8-14.

In the same or different implementations, operation 8-539 may include an operation 8-541 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more particular user traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to (e.g., associated with) one or more particular user traits.

In other words, providing one or more particular templates 8-18 that are associated with one or more source users 8-2* who may be linked to one or more particular user traits (e.g., ethnicity, health issues, social states, and so forth). That is, an end user 8-4* in most cases, will likely prefer obtaining templates 8-17 of source users 8-2* who may have similar traits as the end user 8-4*. In some cases, the linking of the one or more particular templates 8-18 to the one or more particular user traits may be by including into or associating the one or more particular templates 8-18 with indications of one or more source user traits (see source user traits 8-228 in FIG. 8-2b).

Various types of user traits may be linked to the one or more particular templates 8-18 that may be provided. For example, in some implementations, operation 8-541 may include an operation 8-542 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more health or medical traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more health or medical traits (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to cancer or diabetes).

In the same or different implementations, operation 8-541 may include an operation 8-543 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more mental or physical traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more mental or physical traits (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to bi-polar personality, obesity, short stature, and so forth).

In the same or different implementations, operation 8-541 may include an operation 8-544 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more fitness or athletic traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more fitness or athletic traits (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to a golf handicap of 8-36 or linked to poor cardiovascular shape).

In the same or different implementations, operation 8-541 may include an operation 8-545 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more academic or intellectual traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more academic or intellectual traits (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to a particular University).

In the same or different implementations, operation 8-541 may include an operation 8-546 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more social or employment states as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more social or employment states (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to being divorced or being under employed).

In the same or different implementations, operation 8-541 may include an operation 8-547 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more ethnic or gender traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more ethnic or gender traits (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to a multi-racial background).

In the same or different implementations, operation 8-541 may include an operation 8-548 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that are linked to one or more religious or spiritual traits as depicted in FIG. 8-5b. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that are linked to one or more religious or spiritual traits (e.g., the one or more source users 8-2* associated with the one or more particular templates 8-18 being linked to after-life beliefs).

In some implementations, the template providing operation 8-304 of FIG. 8-3 for providing one or more particular templates 8-18 may include an operation 8-549 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more limitations associated with the one or more end users as depicted in FIG. 8-5c. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that do not conflict with one or more limitations (e.g., contextual limitations, physical limitations, legal limitations, and so forth) associated with one or more end users 8-4*.

In various implementations, operation 8-549 may further include an operation 8-550 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that include one or more emulatable aspects that do not conflict with one or more limitations associated with the one or more end users as depicted in FIG. 8-5c. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that include one or more emulatable aspects 8-12 that do not conflict with one or more limitations associated with the one or more end users 8-4*. For example, if the one or more end users 8-4* are vegans, than the one or more particular templates 8-18 to be provided should not include any activities related to consumption of meats.

In some implementations, the template providing operation 8-304 of FIG. 8-3 may include an operation 8-551 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that include one or more types of emulatable aspects that are of interest to the one or more end users as depicted in FIG. 8-5c. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that include one or more types of emulatable aspects 8-12 that are of interest to the one or more end users 8-4*.

In some implementations, the template providing operation 8-304 of FIG. 8-3 may include an operation 8-552 for providing from the plurality of templates the one or more particular templates by providing from the plurality of templates one or more particular templates that can be emulated within one or more predefined time increments as depicted in FIG. 8-5c. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from the plurality of templates 8-17 the one or more particular templates 8-18 by providing from the plurality of templates 8-17 one or more particular templates 8-18 that can be emulated within one or more predefined time increments. For example, if an end user 8-4* is only interested in templates 8-17 that can be executed within a month and that results in a weight loss of 20 pounds or more than any templates 8-17 for losing at least 20 pounds of weight that takes more than a month to execute would be excluded from being provided.

Various types of particular templates 8-18 may be provided by the template providing operation 8-304 of FIG. 8-3 in various alternative implementations. For example, in some implementations, the template providing operation 8-304 may include an operation 8-553 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more health or medical outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more health or medical outcomes (e.g., reduce blood pressure level or increase red blood cell count) when the one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-554 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more athletic or gaming outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more athletic or gaming outcomes (e.g., win a chess tournament) when the one or more emulatable aspects 8-12 (e.g., practice two hours every other day) included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-555 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more occupational outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more occupational outcomes (e.g., obtain a promotion) when the one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-556 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more social or leisure outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more social or leisure outcomes (e.g., going out on a date every weekend) when the one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-557 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more sexual intimacy outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more sexual intimacy outcomes when the one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-558 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more academic or intellectual outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more academic or intellectual outcomes (e.g., being accepted for enrollment to a particular University) when the one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-559 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more spiritual or religious outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more spiritual or religious outcomes when the one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

In the same or different implementations, the template providing operation 8-304 may include an operation 8-560 for providing from a plurality of templates one or more particular templates that are designed to facilitate the one or more end users to achieve one or more user state outcomes when the one or more emulatable aspects included in the one or more particular templates are emulated as depicted in FIG. 8-5d. For instance, the particular template providing module 8-104 of the computing device 8-10 providing from a plurality of templates 8-17 one or more particular templates 8-18 that are designed to facilitate the one or more end users 8-4* to achieve one or more user state outcomes (e.g., being content or satisfied, or being happy) when one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated.

Referring to FIG. 8-6 illustrating another operational flow 8-600 in accordance with various embodiments. Operational flow 8-600 includes certain operations that mirror the operations included in the operational flow 8-300 of FIG. 8-3. These operations include a request receiving operation 8-602 and a template providing operation 8-604 that corresponds to and mirror the request receiving operation 8-302 and the template providing operation 8-304, respectively, of FIG. 8-3.

In addition, operational flow 8-300 includes a template presenting operation 8-606 for presenting the one or more particular templates as depicted in FIG. 8-6. For instance, the presentation module 8-106 of the computing device 8-10 presenting the one or more particular templates 8-18 to, for example, one or more end users 8-4*, to one or more source users 8-2*, to one or more third parties 8-6, and/or to one or more network servers 8-60.

In some implementations, the template presentation operation 8-606 may include an operation 8-762 for transmitting the one or more particular templates via one or more communication networks as depicted in FIG. 8-7. For instance, the transmission module 8-236 of the computing device 8-10 transmitting the one or more particular templates 8-18 via at least one of one or more communication networks 8-50.

In the same or different implementations, the template presentation operation 8-606 may include an operation 8-763 for indicating the one or more particular templates via a user interface as depicted in FIG. 8-7. For instance, the user interface indication module 8-238 indicating (e.g., displaying or audibly indicating) the one or more particular templates 8-18 via a user interface 8-120 (e.g., a display monitor, a touch screen, and/or one or more audio speakers).

Turning now to FIG. 8-8, which is a high-level block diagram illustrating a particular implementation of the computing device 8-10 of FIG. 8-1b. As illustrated, the computing device 8-10 may include a processor 8-802 (e.g., microprocessor, controller, and so forth) coupled to storage medium 8-806 (e.g., volatile or non-volatile memory). The storage medium 8-808 may store computer readable instructions 8-804 (e.g., computer program product). The processor 8-802, in various implementations, may execute the computer readable instructions 8-804 in order to execute one or more operations described above and as illustrated in FIGS. 8-3, 8-4a, 8-4b, 8-4c, 8-5a, 8-5b, 8-5c, and 8-5d.

For example, the processor 8-802 may execute the computer readable instructions 8-804 in order to receive one or more requests 8-16 for one or more particular templates 8-18 that are associated with one or more source users 8-2*, the one or more particular templates 8-18 designed to facilitate one or more end users 8-4* to achieve one or more target outcomes 8-14 when one or more emulatable aspects 8-12 included in the one or more particular templates 8-18 are emulated; and/or to provide from a plurality of templates 8-17 the one or more particular templates 8-18, the providing being based at least on the association of the one or more particular templates 8-18 with the one or more source users 8-2*, the one or more particular templates 8-18 developed based on one or more reported aspects 8-15 associated with the one or more source users 8-2* as illustrated by the operational flow 8-300 of FIG. 8-3.

X. Target Outcome Based Provision of One or More Templates

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 journal. One place where such open journals 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, 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 become very popular in recent times 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 journals 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.

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 their usage. 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).

Although a wealth of personal information provided through log entries (e.g., microblogs, status reports, and so forth) are now available through these 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 sites making it even more difficult to exploit such potentially useful data.

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 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 the others in achieving those goals. Given the enormous volume of personal data that may be acquired through, for example, social networking channels, a large number of templates associated with multiple source users and multiple target outcomes may ultimately be generated. As a result, finding and providing particular templates for achieving particular outcomes from a rapidly expanding population of templates may swiftly become a cumbersome task.

In various embodiments, methods, systems, circuitry, and computer program products are provided for receiving one or more requests that indicate at least one or more target outcomes of one or more particular templates, and to selectively provide from a plurality of templates the one or more particular templates that are 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 templates are emulated, the providing of the one or more particular templates being based at least on the association of the one or more particular templates with the one or more target outcomes.

In some embodiments, the one or more templates to be provided may have been originally developed based on log data of one or more source users provided through, for example, one or more social networking channels (e.g., blogs, microblogs, and so forth).

In some cases, the plurality of templates that the one or more particular templates are provided (e.g., acquired or identified) from may be stored in a memory and/or located at one or more network locations (e.g., servers, client devices, and so forth). In some embodiments, the methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, a network device such as a server (e.g., network servers) or a local client device (e.g., a source user device or an end user device).

In some embodiments, the one or more particular templates that are provided by the methods, systems, circuitry, and computer program products may be presented to, for example, one or more end users. The one or more end users may then directly use the one or more particular templates in order to, for example, achieve the one or more target outcomes that may be associated with the one or more target outcomes. Alternatively, the one or more provided templates may be further processed in order to generate one or more personalized templates (i.e., personalized plans) designed for use specifically by one or more particular end users.

As previously described “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. The one or more emulatable aspects that may be included in the template may be based on and correspond to one or more reported aspects of one or more source users, who may or may not be the source for the one or more reported aspects. That is, a reported aspect may be reported by 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 indicated above, a template may comprise of one or more emulatable aspects that may be based on reported aspects of a particular source user. Note that the word “emulatable” as used herein has no significant meaning, but instead will be used herein 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 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 indicate a collection of one or more activities (e.g., one or more emulatable aspects) or may indicate a more precise schedule of activities (e.g., emulatable aspects) that an end user may emulate in order to achieve a target outcome or outcomes. For example, if a template is designed to facilitate an end user 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) the end user may need to execute in order to achieve the weight loss. Similarly, if the template is designed to, for example, facilitate an end user 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) the end user may need to execute in order to achieve the high test score for the SAT. Note that in some instances a template may include one or more emulatable intermediate outcomes that are associated with 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 an end user 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 other cases, a template may merely be a collection of one or more emulatable aspects without defining any 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.

In some embodiments, each template that may be developed 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. In brief, and as will be further described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, 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 network 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 that has been reported by, for example, the source user, by one or more sensors, or by one or more third parties (e.g., other source 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, an end user. 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 who is a direct or indirect beneficiary of one or more templates. 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. 9-1a, and 9-1b 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 9-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 9-10 may be a server such as one of the one or more network servers 9-60 illustrated in FIG. 9-1a. Alternatively, the computing device 9-10 may be a source user device such as one of the local source user devices 9-20* illustrated in FIG. 9-1a. In still other embodiments, the computing device 9-10 may be an end user device such as one of the local end user device 9-30* illustrated in FIG. 9-1a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 9-2*” may be in reference to a source user 9-2a, a source user 9-2b, and so forth.

Note further that for ease of understanding and explanation, the computing device 9-10 of the exemplary environment 9-100 of FIGS. 9-1a and 9-1b will be generally described in the following discussion 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 9-100 of FIG. 9-1a and 9-1b assumes that the computing device 9-10 is a server, the following discussion will, for the most part, be applicable even if the computing device 9-10 were operating as an end user device (e.g., local end user device 9-30*) or as a source user device (e.g., local source user device 9-20*) with certain obvious exceptions (e.g., if the computing device 9-10 is an end user device or a source user device rather than a server, the computing device 9-10 may communicate with an end user 9-4* or a source user 9-2* directly through a user interface 9-120 rather than indirectly through a communication network 9-50 as may be the case when the computing device 9-10 is a server). In some embodiments, the computing device 9-10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 9-1a and 9-1b, and as previously indicated, the computing device 9-10 may be a network device such as a server (e.g., a network server 9-60) that is designed to communicate with other network devices. For example, the computing device 9-10 may communicate with one or more source users 9-2*(e.g., source user 9-2a, source user 9-2b, and so forth) through one or more local source user devices 9-20*(e.g., local source user device 9-20a, local source user device 9-20b, and so forth), with one or more end users 9-4*(e.g., end user 9-4a, end user 9-4b, and so forth) through one or more local end user devices 9-30*(e.g., local end user device 9-30a, local end user device 9-30b, and so forth), with one or more sensor integrated devices 9-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, usage), with one or more network servers 9-60, and/or with one or more third parties 9-6 (e.g., one or more content providers, one or more network service providers, and/or one or more other parties) via one or more communication networks 9-50. In some implementations, the one or more communication networks 9-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 various embodiments, the computing device 9-10 may be designed to, among other things, receive one or more requests 9-16 indicating at least one or more target outcomes 9-14 of one or more particular templates 9-18, the one or more particular templates 9-18 designed to facilitate one or more end users 9-4* to achieve the one or more target outcomes 9-14 when one or more emulatable aspects 9-12 included in the one or more particular templates 9-18 are emulated. For these embodiments, the one or more requests 9-16 may be received from a variety of requesting sources including, for example, one or more end users 9-4*, one or more third parties 9-6, and/or one or more network servers 9-60. In some embodiments, such as in embodiments in which the computing device 9-10 is a server, the one or more requests 9-16 may be indirectly received from a requesting source (e.g., an end user 9-4*) via the one or more communication networks 9-50.

In other embodiments, such as in embodiments in which the computing device 9-10 is, for example, an end user device, the one or more requests 9-16 may be received directly from a requesting source (e.g., an end user 9-4*) via a user interface 9-120. In various embodiments, the one or more requests 9-16 may include data that may indicate the one or more target outcomes 9-14. Note that FIG. 9-2b illustrates one perspective of a particular template 9-18 (or a template 9-17). In particular, FIG. 9-2b as will be further described below illustrates the types of data that may be included in a particular template 9-18 including, for example, data indicating one or more emulatable aspects 9-12, data indicating one or more target outcomes 9-14, data indicating one or more source user identifiers 9-226, and/or other data that indicate other types of attributes that may be associated with the particular template 9-18.

In any event, in response to receiving the one or more requests 9-16, the computing device 9-10 may be designed to selectively provide from a plurality of templates 9-17 the one or more particular templates 9-18, the providing of the one or more particular templates 9-18 being based at least on the association of the one or more particular templates 9-18 with the one or more target outcomes 9-14, the one or more particular templates 9-18 developed based on one or more reported aspects 9-15 of one or more source users 9-2*. In some selective embodiments, the computing device 9-10 may be designed to develop the plurality of templates 9-17 including the one or more particular templates 9-18 based on reported aspects 9-15 that may be acquired from one or more sources including, for example, one or more local source user devices 9-20*, one or more sensor integrated devices 9-40, one or more third parties 9-6, and/or one or more network servers 9-60. In some embodiments, the computing device 9-10 may be designed to present the one or more templates 9-17 via user interface 9-120 and/or via one or more communication networks 9-50.

In embodiments in which the computing device 9-10 is designed to present the one or more particular templates 9-18, the one or more particular templates 9-18 may be presented by transmitting the one or more particular templates 9-18 to one or more network servers 9-60, to one or more source users 9-2*(e.g., one or more local source user devices 9-20*), to one or more end users 9-4*(e.g., one or more local end user devices 9-30*), and/or to one or more third parties 9-6. In embodiments where, for example, the computing device 9-10 is a source user device or an end user device rather than a sever, the computing device 9-10 may indicate (e.g., visually display or audibly indicate) the one or more particular templates 9-18 via a user interface 9-120.

In embodiments in which the computing device 9-10 is designed to receive reported aspects 9-15, the computing device 9-10 may randomly, semi-continuously, or continuously receive reported aspects 9-15 associated with one or more source user 9-2*. Such reported aspects 9-15 may indicate a variety of aspects (e.g., behavior aspects such as user activities, user states, environmental conditions, and so forth) associated with the one or more source users 9-2*.

In embodiments in which the computing device 9-10 is configured to develop, for example, one or more particular templates 9-18 that is designed to facilitate achievement of one or more target outcomes 9-14, the one or more particular templates 9-18 may be developed by initially determining which of the acquired reported aspects 9-15 may be relevant to achieving the one or more target outcomes 9-14. After determining which of the reported aspects 9-15 are relevant to achieving the one or more target outcomes 9-14, the computing device 9-10 may be designed to include into the one or more particular templates 9-18 one or more emulatable aspects 9-12 that correspond (e.g., equivalent) to one or more reported aspects 9-15 that have been determined to be relevant to achieving the one or more target outcomes 9-14. Note that throughout the following discussion, reference number “9-18” will be used in connection with the one or more particular templates 9-18 that are requested and provided, while reference number “9-17” will be used with respect to the general population or group of templates 9-17 that the one or more particular templates 9-18 are provided from.

In various embodiments, the computing device 9-10, as previously indicated, may be a server (e.g., one of the one or more network servers 9-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 9-10 is a source user device (e.g., local source user device 9-20*) or an end user device (e.g., local end user device 9-30*) rather than a network server 9-60, the computing device 9-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 9-100 of FIGS. 9-1a and 9-1b, the one or more sensor integrated devices 9-40 of the exemplary environment 9-100 of FIGS. 9-1a and 9-1b may directly communicate with the one or more communication networks 9-50 in various embodiments. Alternatively, the one or more sensor integrated devices 9-40 may indirectly communicate with the one or more communication networks 9-50 via the one or more local source user devices 9-20*(e.g., via, for example, personal area network or PAN). In various embodiments, a sensor integrated device 9-40 may be a variety of functional devices that may comprise of one or more sensors 9-240 and that may be operated or used by a source user 9-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 9-240, which may also be included in the one or more local source user devices 9-20* and/or the computing device 9-10, may include any type of sensors that can sense one or more aspects of a source user 9-2*. Examples of such sensors 9-240 include, for example, sensors 9-240 that can sense various physical characteristics of a source user 9-2*(e.g., heart rate sensor or blood pressure sensor), sensors 9-240 that can sense activities of a source user 9-2*(e.g., a pedometer, an accelerometer, and so forth), sensors 9-240 that can sense environment conditions (e.g., air quality sensors), sensors 9-240 that can sense the location of a source user 9-2*(e.g., global positioning system or GPS), sensors 9-240 that can provide physiological data that may be processed in order to determined inferred mental states of users, and so forth.

Each of the one or more local source user devices 9-20* and each of the one or more local end user devices 9-30*(as well as the computing device 9-10 in embodiments in which the computing device 9-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 9-20* and/or the one or more local end user devices 9-30*(as well as the computing device 9-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 9-20* and/or local end user device 9-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 9-10 as illustrated in FIG. 9-1b may include one or more modules, sub-modules, and various other components. As shown, the computing device 9-10 may include at least a request receiving module 9-102 (which may further include a network receiving module 9-202 and/or a user interface receiving module 9-204) and a particular template providing module 9-104 (which may further include one or more sub-modules as illustrated in FIG. 9-2b). In various embodiments, the computing device 9-10 may further include a target outcome identifying data interpreting module 9-103, a template developing module 9-105, a presentation module 9-106 (which may further include a transmission module 9-236 and/or a user interface indication module 9-238) and a memory 9-116 (which may store a plurality of templates 9-17, one or more end user trait indications 9-138, one or more end user limitation indications 9-140, one or more end user relevancy indications 9-142, one or more source user relevancy indications 9-144, one or more third party source relevancy indications 9-145, one or more predefined time increment indications 9-146, and/or one or more applications 9-140).

The computing device 9-10 may also include, in various embodiments, a network interface 9-118 (e.g., a network interface card or NIC), a user interface 9-120, a social networking entry reception module 9-110 (which may further include a blog entry reception module 9-111 and/or a status report reception module 9-112), and/or one or more sensors 9-240. In some cases, the presence or absence of some of these modules and sub-modules may depend on, for example, whether the computing device 9-10 is a server, an end user device, or a source user device. For example, if the computing device 9-10 is a server, then the computing device 9-10 may not include a user interface 9-120.

Referring particularly now to the request receiving module 9-102, the request receiving module 9-102 may be configured to, among other things, receive one or more requests 9-16 that indicate at least one or more target outcomes 9-14 of one or more particular templates 9-18, the one or more particular templates 9-18 designed to facilitate one or more end users 9-4* to achieve the one or more target outcomes 9-14 when one or more emulatable aspects 9-12 included in the one or more particular templates 9-18 are emulated. In contrast, the particular template providing module 9-104 may be configured to, among other things, provide from a plurality of templates 9-17 the one or more particular templates 9-18, the providing being based at least on the association of the one or more particular templates 9-18 with the one or more target outcomes 9-14, the one or more particular templates 9-18 developed based on one or more reported aspects 9-12 of one or more source users 9-2*.

The memory 9-116 may be designed to store various data including a plurality of templates 9-17, which may have been developed based on reported aspects 9-15 associated with one or more source users 9-2*. Other types of data may also be stored in the memory 9-116 in various implementations including, for example, one or more end user trait indications 9-138 (e.g., one or more indications that indicate one or more traits of one or more end users 9-4*), one or more end user limitation indications 9-140 (e.g., one or more indications that indicate one or more limitations associated with one or more end users 9-4* including contextual limitations, physical limitations, legal limitations, and so forth), one or more end user relevancy indications 9-142 (e.g., one or more indications that indicate the types of reported aspects 9-15 that an end user 9-4* has an interest in or believes is relevant to achieving one or more target outcomes 9-14) and/or one or more source user relevancy indications 9-144 (e.g., one or more indications provided by a source user 9-2* that indicate at least which types of reported aspects 9-15 are relevant to achieving one or more target outcomes 9-14).

In some cases, the memory 9-116 may also include, for example, one or more third party source relevancy indications 9-145 (e.g., one or more indications provided by one or more third party sources such as one or more third parties 9-6 that indicate at least which types of reported aspects 9-15 are relevant to achieving one or more target outcomes 9-14), one or more predefined time increment indications 9-146 (e.g., one or more indications that indicate one or more lengths of time that may be allotted for executing one or more templates 9-17), and/or one or more applications 9-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). In various implementations, the memory 9-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 target outcome identifying data interpreting module 9-103 may be configured to process and interpret target outcome identification data that may be included in a request 9-16 received by the request receiving module 9-102. By interpreting the target outcome identification data (e.g., alphanumeric data, image data, audio data, and so forth), one or more target outcomes 9-14 of one or more particular templates 9-18 may be identified or determined.

In various implementations, the presentation module 9-106 may be configured to present one or more particular templates 9-18 provided by the particular template providing module 9-104. The transmission module 9-236 that may be included in the presentation module 9-106 may be designed to transmit the one or more particular templates 9-18 provided by the particular template providing module 9-104 via the one or more communication networks 9-50. The user interface indication module 9-238, in contrast, may be designed to indicate the one or more particular templates 9-18 via a user interface 9-120 (e.g., display monitor, speaker system, touch screen, and so forth).

The social networking entry reception module 9-110 may be configured to receive social networking entries from one or more sources including, for example, one or more source users 9-2*, one or more end users 9-4*, one or more third parties 9-6, one or more sensor integrated devices 9-40, and/or one or more network servers 9-60. The social networking entry reception module 9-110 may further include a blog entry reception module 9-111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 9-112 for receiving social networking status reports. In some implementations, one or more reported aspects 9-15 of one or more source users 9-2* may be received via social networking entries (e.g., blog entries, status reports, and so forth). The user interface 9-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. 9-2 a illustrates particular implementations of the particular template providing module 9-104 of the computing device 9-10 of FIG. 9-1b. As illustrated, the particular template providing module 9-104 may include, in various implementations, one or more sub-modules. For example, in some implementations, the particular template providing module 9-104 may include a particular template memory acquiring module 9-202 and/or a particular template network acquiring module 9-204 (which may further include a solicitation transmitting module 9-206). In brief, the particular template memory acquiring module 9-202 may be designed to acquire from the memory 9-116 the one or more particular templates 9-18 that may be provided. In contrast, the particular template network acquiring module 9-204 may be designed to acquire from the one or more communication networks 9-50, the one or more particular templates 9-18 that may be provided. In some cases, the particular template network acquiring module 9-204 may further include a solicitation transmitting module 9-206 configured to transmit one or more solicitations for the one or more particular templates 9-18.

FIG. 9-2 b illustrates one perspective of a particular template 9-18 (or template 9-17). In particular, FIG. 9-2b shows the types of data that may be included in or be associated with a particular template 9-18 (or template 9-17). In various implementations, a particular template 9-18 (or template 9-17) may include data that indicates, for example, one or more emulatable aspects 9-12, one or more target outcomes 9-14 (which in some cases may be one or more of the emulatable aspects 9-12), one or more source user identifiers 9-226 (for identifying at least one source user 9-2* associated with the particular template 9-18), one or more source user traits 9-228 (indicates one or more traits of the source user 9-2* who is associated with the particular template 9-18), and/or a template time increment 9-230 (represents the amount of time it will take to fully emulate or execute the particular template 9-18). Note that FIG. 9-2b is provided for purposes of merely showing the types of data that may be included in or associated with a particular template 9-18 (or template 9-17) and is not meant to be an actual representation of a particular template 9-18 (or template 9-17).

In embodiments in which the particular template 9-18 includes data that indicate multiple emulatable aspects 9-12, the particular template 9-18 may also include data that defines the relationship (e.g., temporal, specific time, and/or spatial relationships) between the emulatable aspects 9-12. Also, when the particular templates 9-18 indicates multiple emulatable aspects 9-12 one or more of the emulatable aspects 9-12 may be one or more emulatable intermediate outcomes that are associated with the one or more target outcomes 9-14 of the particular template 9-18. For example, if a target outcome 9-14 for a particular template 9-18 is to lose 20 pounds of body weight in two months, than an emulatable intermediate outcome may be, for example, 10 pounds of body weight loss after one month of emulating the particular template 9-18.

Referring back to the computing device 9-10 of FIG. 9-1b, the various modules (e.g., the request receiving module 9-102, the particular template providing module 9-104, and so forth) along with their sub-modules included in the computing device 9-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the request receiving module 9-102 and/or the particular template providing module 9-104 may be implemented with a processor 9-802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 9-804 (e.g., computer program product) stored in a storage medium 9-806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 9-10 of FIG. 9-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 discussion relating to the functional aspects of the computing device 9-10 of FIG. 9-1b and its components will now be provided with respect to the processes and operations to be described herein. FIG. 9-3 illustrates an operational flow 9-300 representing example operations directed to, among other things, providing from a plurality of templates one or more particular templates 9-18 that are associated with one or more source users 9-2* and that are designed to facilitate one or more end users 9-4* to achieve one or more target outcomes 9-14 when one or more emulatable aspects 9-12 included in the one or more particular templates 9-18 are emulated, the providing of the one or more templates 9-17 being based, at least in part, on their association with the one or more target outcomes 9-14 and in response to reception of one or more requests 9-16 that indicate the one or more target outcomes 9-14.

In FIG. 9-3 and in the following figures that include various examples of operational flows, discussions and explanations of the operational flows with be provided with respect to the exemplary environment 9-100 described above as illustrated in FIGS. 9-1a and 9-1b, and/or with respect to other examples (e.g., as provided in FIGS. 9-2a and 9-2b) 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. 9-1a, 9-1b, 9-2a, and 9-2b. 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. 9-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 9-300 may move to a request receiving operation 9-302 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. For instance, and as an illustration, the request receiving module 9-102 of the computing device 9-10 of FIG. 9-1b receiving (e.g., from one or more communication networks 9-50 and/or via a user interface 9-120) one or more requests 9-16 (e.g., solicitations, queries, and so forth) indicating at least one or more target outcomes 9-14 of one or more particular templates 9-18, the one or more particular templates 9-18 designed to facilitate one or more end users 9-4* to achieve the one or more target outcomes 9-14 when one or more emulatable aspects 9-12 included in the one or more particular templates 9-18 are emulated.

In addition to the request reception operation 9-302, operational flow 9-300 may also include a particular template providing operation 9-304 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. For instance, the particular template providing module 9-104 of the computing device 9-10 providing from a plurality of templates 9-17 the one or more particular templates 9-18, the providing of the one or more particular templates 9-18 being based at least on the association of the one or more particular templates 9-18 with the one or more target outcomes 9-14, the one or more particular templates 9-18 developed (e.g., originally created) based on one or more reported aspects 9-15 of one or more source users 9-2*. As will be further described herein, both the request receiving operation 9-302 and the particular template providing operation 9-304 of FIG. 9-3 may be executed in a number of different ways in various alternative implementations.

For example, FIGS. 9-4a, 9-4b, and 9-4c illustrate the various ways that the request reception operation 9-302 of FIG. 9-3 may be executed in various alternative implementations. For instance, the one or more requests 9-16 received through the request receiving operation 9-302 may be received from a variety of sources in a variety of different ways. For example, in some implementations, the request receiving operation 9-302 of FIG. 9-3 may include an operation 9-402 for receiving the one or more requests indicating the at least one or more target outcomes from at least one end user as depicted in FIG. 9-4a. For instance, the request receiving module 9-102 of the computing device 9-10 of FIG. 9-1b receiving (e.g., via one or more communication networks 9-50 or via user interface 9-120) the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 from at least one end user 9-4*.

In the same or different implementations, the request receiving operation 9-302 may include an operation 9-403 for receiving the one or more requests indicating the at least one or more target outcomes via one or more communication networks as depicted in FIG. 9-4a. For instance, the network receiving module 9-202 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 via one or more communication networks 9-50 (e.g., a wireless network and/or a wired network).

In the same or different implementations, the request receiving operation 9-302 may include an operation 9-404 for receiving the one or more requests indicating the at least one or more target outcomes via a user interface as depicted in FIG. 9-4a. For instance, the user interface receiving module 9-204 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 via a user interface 9-120.

The one or more requests 9-16 that may be received through the request receiving operation 9-302 may include data that may be processed in order to facilitate the determination or identification of the one or more target outcomes 9-14. For example, in some implementations, the request reception operation 9-302 may include an operation 9-405 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that include data to facilitate determination of the one or more target outcomes as depicted in FIG. 9-4a. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that include data to facilitate determination of the one or more target outcomes 9-14.

Various types of data may be included in the one or more requests 9-16 that may facilitate in the determination or identification of the one or more target outcomes 9-14 in various alternative implementations. For example, in some implementations, operation 9-405 may include an operation 9-406 for receiving the one or more requests that include the data to facilitate the identification of the one or more target outcomes including receiving one or more requests that include alphanumeric data to determine the one or more target outcomes as depicted in FIG. 9-4a. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 that include the data to facilitate the identification of the one or more target outcomes 9-14 including receiving one or more requests 9-16 that include alphanumeric data to determine the one or more target outcomes 9-14.

In the same or different implementations, operation 9-405 may include an operation 9-407 for receiving the one or more requests that include the data to facilitate the identification of the one or more target outcomes including receiving one or more requests that include audio data to determine the one or more target outcomes as depicted in FIG. 9-4a. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 that include the data to facilitate the identification of the one or more target outcomes 9-14 including receiving one or more requests 9-16 that include audio data (e.g., voice data) to determine the one or more target outcomes 9-14. In some cases, such data may be processed using, for example, a voice recognition application in order to determine the one or more target outcomes 9-14.

In the same or different implementations, operation 9-405 may include an operation 9-408 for receiving the one or more requests that include the data to facilitate the identification of the one or more target outcomes including receiving one or more requests that include image data to determine the one or more target outcomes as depicted in FIG. 9-4a. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 that include the data to facilitate the identification of the one or more target outcomes 9-14 including receiving one or more requests 9-16 that include image data (e.g., data provided by a digital camera or by a camcorder) to determine the one or more target outcomes 9-14. For instance, if a target outcome 9-14 as achieved by a source user 9-2* may be indicated or represented by an image that captures as successfully achieved by the source user 9-2*, then image data that embodies the captured image may be included in a request 9-16. Examples of target outcomes 9-14 that could be indicated by a captured image include, for example, a physical characteristic, such as skin tone, of a source user 9-2*.

After receiving the one or more requests 9-16 that include the data to facilitate determination of the one or more target outcomes 9-14, the data may be processed in order to determine the one or more target outcomes 9-14. For example, in some implementations, operation 9-405 may include an operation 9-409 for interpreting the data to determine the one or more target outcomes as depicted in FIG. 9-4a. For instance, target outcome identifying data interpreting module 9-103 of the computing device 9-10 interpreting the data to determine the one or more target outcomes 9-14.

In various implementations, other types of data may be included in the one or more requests 9-16 that may be received through the request receiving operation 9-302 of FIG. 9-3. For example, in some implementations, the request receiving operation 9-302 may include an operation 9-410 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more traits associated with at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more traits associated with at least one end user 9-4*. By including such information into the one or more requests 9-16, only particular templates 9-18 that are associated with source users 9-2* who share, for example, the indicated traits associated with the at least one end user 9-4* may be provided.

Various types of user traits may be indicated by the one or more requests 9-16 that are received through operation 9-410 in various alternative implementations. For example, in some implementations, the operation 9-410 may include an operation 9-411 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more health or medical traits associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more health or medical traits (e.g., a particular illness or affliction such as stomach cancer or participating in a particular medical treatment such as chemotherapy) associated with the at least one end user 9-4*.

In the same or different implementations, the operation 9-410 may include an operation 9-412 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more physical or mental traits associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more physical or mental traits (e.g., being overweight, being short, having high blood pressure, inflicted with a particular phobia, being angry, and so forth) associated with the at least one end user 9-4*.

In the same or different implementations, the operation 9-410 may include an operation 9-413 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more fitness or athletic traits associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more fitness or athletic traits (e.g., being able to run a marathon under 3 hours) associated with the at least one end user 9-4*.

In the same or different implementations, the operation 9-410 may include an operation 9-414 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more academic or intellectual traits associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more academic or intellectual traits (e.g., having previously failed a particular exam or having an IQ under 120) associated with the at least one end user 9-4*.

In the same or different implementations, the operation 9-410 may include an operation 9-415 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more social or employment states associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more social or employment states (e.g., being unmarried or unemployed) associated with the at least one end user 9-4*.

In the same or different implementations, the operation 9-410 may include an operation 9-416 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more ethnic or gender traits associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more ethnic or gender traits (e.g., being Asian, being a female, and so forth) associated with the at least one end user 9-4*.

In the same or different implementations, the operation 9-410 may include an operation 9-417 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more religious or spiritual traits associated with the at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more religious or spiritual traits (e.g., being a Hindu or Scientologist) associated with the at least one end user 9-4*.

In some implementations, the request receiving operation 9-302 of FIG. 9-3 may include an operation 9-418 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more types of aspects that are of interest to at least one end user as depicted in FIG. 9-4b. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more types of aspects (e.g., dietary activities, sleep activities, social activities, and so forth) that are of interest to at least one end user 9-4*.

In some implementations, the request receiving operation 9-302 of FIG. 9-3 may include an operation 9-419 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more limitations associated with at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more limitations (e.g., being a vegan and not be able to consume meats, having no means of transportation, and so forth) associated with at least one end user 9-4*.

Various types of limitations associated with the at least one end user 9-4* may be indicated by the one or more requests 9-16. For example, in some implementations, operation 9-419 may include an operation 9-420 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more physical limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more physical limitations associated with the at least one end user 9-4*.

In the same or different implementations, operation 9-419 may include an operation 9-421 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more contextual limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more contextual limitations (e.g., logistical limitations such as no access to a swimming pool) associated with the at least one end user 9-4*.

In the same or different implementations, operation 9-419 may include an operation 9-422 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more personal limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more personal limitations (e.g., won't participate in activities with in-laws) associated with the at least one end user 9-4*.

In the same or different implementations, operation 9-419 may include an operation 9-423 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more legal or regulatory limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more legal or regulatory limitations (e.g., regulatory ban on certain medications or legal ban on chewing gum) associated with the at least one end user 9-4*.

In the same or different implementations, operation 9-419 may include an operation 9-424 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more psychological limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more psychological limitations (e.g., phobias) associated with the at least one end user 9-4*.

In the same or different implementations, operation 9-419 may include an operation 9-425 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more user state limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more user state limitations (e.g., being married, being unemployed, being ill, and forth) associated with the at least one end user 9-4*.

In the same or different implementations, operation 9-419 may include an operation 9-426 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate one or more medical or health limitations associated with the at least one end user as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate one or more medical or health limitations (e.g., being diabetic, having a heart defect, being overweight, and so forth) associated with the at least one end user 9-4*.

In some implementations, the request receiving operation 9-302 of FIG. 9-3 may include an operation 9-427 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate at least one predefined time increment that is of interest to at least one end user or a third party as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate at least one predefined time increment (e.g., one day, one month, one year, and so forth) that is of interest to at least one end user 9-4* or a third party 9-6. By providing a predefined time increment, templates 9-17 that may take longer than the predefined time increment to execute may be excluded from being provided. For example, an end user 9-4* may only be interested in templates 9-17 for losing weight that can be executed in two months or less (e.g., predefined time increment).

In some implementations, the request receiving operation 9-302 may include an operation 9-428 for receiving the one or more requests indicating the at least one or more target outcomes including one or more requests that indicate at least one of the one or more source users as depicted in FIG. 9-4c. For instance, the request receiving module 9-102 of the computing device 9-10 receiving the one or more requests 9-16 indicating the at least one or more target outcomes 9-14 including one or more requests 9-16 that indicate at least one of the one or more source users 9-2*. Note that in various implementations, the one or more source users 9-2* may be source users 9-2* who have at least previously achieved the one or more target outcomes 9-14.

Referring back to FIG. 9-3, the particular template providing operation 9-304 may be implemented in a number of different ways in various implementations. For example, in some implementations, the particular template providing operation 9-304 of FIG. 9-3 may include an operation 9-529 for acquiring the one or more particular templates from a plurality of templates stored in a memory as depicted in FIG. 9-5a. For instance, the particular template memory acquiring module 9-202 (se FIG. 9-2a) of the computing device 9-10 acquiring (e.g., retrieving or identifying) the one or more particular templates 9-18 from a plurality of templates 9-17 stored in a memory 9-116 (e.g., volatile and/or non-volatile memory).

In some implementations, the particular template providing operation 9-304 may include an operation 9-530 for acquiring the one or more particular templates from a plurality of templates located at one or more network sites as depicted in FIG. 9-5a. For instance, the particular template network acquiring module 9-204 (see FIG. 9-2a) of the computing device 9-10 acquiring (e.g., retrieving, soliciting, querying, and so forth) the one or more particular templates 9-18 from a plurality of templates 9-17 located at one or more network sites (e.g., local source user devices 9-20*, network servers 9-60, and so forth).

In some cases, operation 9-530 may in turn include an operation 9-531 for transmitting one or more solicitations via one or more communication networks to solicit for the one or more particular templates, the one or more solicitations indicating at least the one or more target outcomes as depicted in FIG. 9-5a. For instance, the solicitation transmitting module 9-206 (see FIG. 9-2a) of the computing device 9-10 transmitting one or more solicitations via one or more communication networks 9-50 to solicit for the one or more particular templates 9-18, the one or more solicitations indicating at least the one or more target outcomes 9-14.

In some implementations, the particular template providing operation 9-304 may include an operation 9-532 for providing the one or more particular templates from a plurality of templates that include at least a first one or more templates associated with the one or more source users and a second one or more templates that are not associated with the one or more source users as depicted in FIG. 9-5a. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from a plurality of templates 9-17 that include at least a first one or more templates 9-17 associated with the one or more source users 9-2*and a second one or more templates 9-17 that are not associated with the one or more source users 9-2*.

In some implementations, the particular template providing operation 9-304 may include an operation 9-533 for providing the one or more particular templates from a plurality of templates that include at least a first one or more templates that are associated with the one or more target outcomes and a second one or more templates that are not associated with the one or more target outcomes as depicted in FIG. 9-5a. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from a plurality of templates 9-17 that include at least a first one or more templates 9-17 that are associated with the one or more target outcomes 9-14 and a second one or more templates 9-17 that are not associated with the one or more target outcomes 9-14.

In some implementations, the particular template providing operation 9-304 may include an operation 9-534 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates designed to facilitate the one or more end users to achieve the one or more target outcomes and that include the one or more emulatable aspects that are based on the one or more reported aspects of the one or more source users as depicted in FIG. 9-5a. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 designed to facilitate the one or more end users 9-4* to achieve the one or more target outcomes 9-14 and that include the one or more emulatable aspects 9-12 that are based on the one or more reported aspects 9-15 of the one or more source users 9-2*.

In some implementations, the particular template providing operation 9-304 may include an operation 9-535 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes as depicted in FIG. 9-5b. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14. For example, the one or more particular templates 9-18 may include data that directly or indirectly identifies the one or more target outcomes 9-14. Thus, in some cases, this may mean that the one or more particular templates 9-18 may include target outcome identifiers (e.g., a description or a name of the target outcomes) or hyperlinks to indicate the one or more target outcomes 9-14.

For example, in some implementations, operation 9-535 may include an operation 9-536 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that include data that indicate the one or more target outcomes as depicted in FIG. 9-5b. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that include data (e.g., identifiers or hyperlinks) that indicate the one or more target outcomes 9-14.

In the same or different implementations, operation 9-535 may further include an operation 9-537 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more health or medical traits as depicted in FIG. 9-5b. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more health or medical traits (e.g., hypertension, arthritis, poor vision, and so forth). For these implementations, such health or medical traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-14.

In the same or different implementations, operation 9-535 may further include an operation 9-538 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more mental or physical traits as depicted in FIG. 9-5b. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more mental or physical traits (e.g., poor analytical abilities, over six feet tall, blood hair, mental exhaustion, and so forth). For these implementations, such mental or physical traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18.

In the same or different implementations, operation 9-535 may further include an operation 9-539 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more fitness or athletic traits as depicted in FIG. 9-5b. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more fitness or athletic traits (e.g., novice golfer). For these implementations, such fitness or athletic traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18.

In the same or different implementations, operation 9-535 may further include an operation 9-540 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more academic or intellectual traits as depicted in FIG. 9-5b. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more academic or intellectual traits (e.g., being in a particular graduate program or enrolled in a particular college or high school course). For these implementations, such academic or intellectual traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18.

In the same or different implementations, operation 9-535 may further include an operation 9-541 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more social or employment traits as depicted in FIG. 9-5c. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more social or employment traits (e.g., being unmarried or being unemployed). For these implementations, such social or employment traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18.

In the same or different implementations, operation 9-535 may further include an operation 9-542 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more ethnic or gender traits as depicted in FIG. 9-5c. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more ethnic or gender traits (e.g., Native American, male, and so forth). For these implementations, such ethnic or gender traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18.

In the same or different implementations, operation 9-535 may further include an operation 9-543 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more religious or spiritual traits as depicted in FIG. 9-5c. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more religious or spiritual traits (e.g., catholic). For these implementations, such religious or spiritual traits may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18. In some cases, the one or more particular templates 9-18 may be linked to one or more age groups (e.g., over 65 years of age).

In the same or different implementations, operation 9-535 may further include an operation 9-544 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that are linked to the one or more target outcomes and that are linked to one or more geographical traits as depicted in FIG. 9-5c. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are linked to the one or more target outcomes 9-14 and that are linked to one or more geographical traits. For these implementations, such geographic traits (e.g., geographic locations) may be associated with, for example, the one or more source users 9-2* who are associated with the one or more particular templates 9-18.

In various implementations, the particular template providing operation 9-304 of FIG. 9-3 may include an operation 9-545 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that do not conflict with one or more limitations associated with the one or more end users 9-4*.

In some implementations, operation 9-545 may further include an operation 9-546 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that include one or more emulatable aspects that do not conflict with one or more ability or skill limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that include one or more emulatable aspects 9-12 (e.g., walking or jogging) that do not conflict with one or more ability or skill limitations (e.g., swimming limitations) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-547 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more physical limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to reading or meditating activities) that do not conflict with one or more physical limitations (e.g., paraplegic) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-548 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more contextual limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to skiing activities) that do not conflict with one or more contextual limitations (e.g., logistical limitations such as no access to a swimming pool) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-549 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more personal limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to consumption of water) that do not conflict with one or more personal limitations (e.g., being a vegan) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-550 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more legal or regulatory limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to consumption of nutraceutical) that do not conflict with one or more legal or regulatory limitations (e.g., ban on narcotics) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-551 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more psychological limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to swimming) that do not conflict with one or more psychological limitations (e.g., fear of heights) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-552 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more user state limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to dating) that do not conflict with one or more user state limitations (e.g., being unmarried) associated with the one or more end users 9-4*.

In the same or different implementations, operation 9-545 may include an operation 9-553 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that do not conflict with one or more medical or health limitations associated with the one or more end users as depicted in FIG. 9-5d. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 (e.g., a particular template 9-18 that includes emulatable aspects 9-12 relating to reading) that do not conflict with one or more medical or health limitations (e.g., poor hearing) associated with the one or more end users 9-4*.

In some implementations, the particular template providing operation 9-304 of FIG. 9-3 may include an operation 9-554 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that include one or more emulatable aspects that are of interest to the one or more end users as depicted in FIG. 9-5e. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that include one or more emulatable aspects 9-12 that are of interest to the one or more end users 9-4*.

In some implementations, the particular template providing operation 9-304 of FIG. 9-3 may include an operation 9-555 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that can be emulated within one or more predefined time increments as depicted in FIG. 9-5e. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that can be emulated within one or more predefined time increments.

In some implementations, the particular template providing operation 9-304 of FIG. 9-3 may include an operation 9-556 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that were developed based on one or more reported aspects of the one or more source users that were reported through one or more social networking entries as depicted in FIG. 9-5e. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that were developed (e.g., created) based on one or more reported aspects 9-15 of the one or more source users 9-2* that were reported through one or more social networking entries.

In some implementations, operation 9-556 may further include an operation 9-557 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that were developed based on one or more reported aspects of the one or more source users that were reported through one or more blog entries as depicted in FIG. 9-5e. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that were developed based on one or more reported aspects 9-15 of the one or more source users 9-2*that were reported through one or more blog entries (e.g., microblog entries).

In the same or different implementations, operation 9-556 may include an operation 9-558 for providing the one or more particular templates from the plurality of templates by providing from the plurality of templates one or more particular templates that were developed based on one or more reported aspects of the one or more source users that were reported through one or more status reports as depicted in FIG. 9-5e. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that were developed based on one or more reported aspects 9-15 of the one or more source users 9-2* that were reported through one or more status reports.

Different types of particular templates 9-18 may be provided by the particular template providing operation 9-304 of FIG. 9-3 in various alternative implementations. For example, in some implementations, the particular template providing operation 9-304 may include an operation 9-559 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more health or medical outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more health or medical outcomes (e.g., reduce blood pressure level, increase red blood cell count, improve chemotherapy outcomes, and so forth).

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-560 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more athletic or gaming outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more athletic or gaming outcomes (e.g., achieve a particular level of Chess ranking, win a tennis tournament, score under 100 for a round of golf, and so forth).

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-561 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more occupational outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more occupational outcomes (e.g., obtain a promotion, pass an employment related exam, develop a business network, and so forth).

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-562 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more social or leisure outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more social or leisure outcomes (e.g., developing new friendships).

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-563 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more sexual intimacy outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more sexual intimacy outcomes (e.g., increase frequency of sexual encounters).

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-564 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more academic or intellectual outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more academic or intellectual outcomes (e.g., obtaining a particular grade point average).

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-565 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more spiritual or religious outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more spiritual or religious outcomes.

In the same or different implementations, the particular template providing operation 9-304 may include an operation 9-566 for providing the one or more particular templates from the plurality of templates by providing one or more particular templates that are designed to facilitate the one or more end users to achieve one or more user state outcomes as depicted in FIG. 9-5f. For instance, the particular template providing module 9-104 of the computing device 9-10 providing the one or more particular templates 9-18 from the plurality of templates 9-17 by providing from the plurality of templates 9-17 one or more particular templates 9-18 that are designed to facilitate the one or more end users 9-4* to achieve one or more user state outcomes (e.g., subjective user states such as “being happy” or “feeling well,” or an objective user state such as being engaged to be married).

Referring to FIG. 9-6 illustrating another operational flow 9-600 in accordance with various embodiments. Operational flow 9-600 includes certain operations that mirror the operations included in the operational flow 9-300 of FIG. 9-3. These operations include a request receiving operation 9-602 and a particular template providing operation 9-604 that corresponds to and mirror the request receiving operation 9-302 and the particular template providing operation 9-304, respectively, of FIG. 9-3.

In addition, operational flow 9-300 includes a particular template presenting operation 9-606 for presenting the one or more particular templates as depicted in FIG. 9-6. For instance, the presentation module 9-106 of the computing device 9-10 presenting the one or more particular templates 9-18 to, for example, one or more end users 9-4*, to one or more source users 9-2*, to one or more third parties 9-6, and/or to one or more network servers 9-60.

In some implementations, the particular template presentation operation 9-606 may include an operation 9-768 for transmitting the one or more particular templates via one or more communication networks as depicted in FIG. 9-7. For instance, the transmission module 9-236 of the computing device 9-10 transmitting the one or more particular templates 9-18 via one of one or more communication networks 9-50.

In the same or different implementations, the particular template presentation operation 9-606 may include an operation 9-769 for indicating the one or more particular templates via a user interface as depicted in FIG. 9-7. For instance, the user interface indication module 9-238 indicating (e.g., displaying or audibly indicating) the one or more particular templates 9-18 via a user interface 9-120 (e.g., a display monitor, a touch screen, and/or one or more audio speakers).

Turning now to FIG. 9-8, which is a high-level block diagram illustrating a particular implementation of the computing device 9-10 of FIG. 9-1b. As illustrated, the computing device 9-10 may include a processor 9-802 (e.g., microprocessor, controller, and so forth) coupled to storage medium 9-806 (e.g., volatile or non-volatile memory). The storage medium 9-806 may store computer readable instructions 9-804 (e.g., computer program product). The processor 9-802, in various implementations, may execute the computer readable instructions 9-804 in order to execute one or more operations described above and as illustrated in FIGS. 9-3, 9-4a, 9-4b, 9-4c, 9-5a, 9-5b, 9-5c, 9-5d, 9-5e and 9-5f.

For example, the processor 9-802 may execute the computer readable instructions 9-804 in order to receive one or more requests 9-16 indicating one or more target outcomes 9-14 of one or more particular templates 9-18, the one or more particular templates 9-18 designed to facilitate one or more end users 9-4* to achieve the one or more target outcomes 9-14 when one or more emulatable aspects 9-12 included in the one or more particular templates 9-18 are emulated; and/or to provide from a plurality of templates 9-17 the one or more particular templates 9-18, the providing being based at least on the association of the one or more particular templates 9-18 with the one or more target outcomes 9-14, the one or more particular templates 9-18 developed based on one or more reported aspects 9-15 of one or more source users 9-2* as illustrated by the operational flow 9-300 of FIG. 9-3.

XI. Detecting Deviation from Compliant Execution of a Template

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 journal. One place where such open journals 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 become very popular in recent times 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 journals 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.

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 their usage. 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 “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 the others 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 are generic templates that may not be designed for use by any particular end user or a particular group of end users but instead may be designed to be used 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).

In any event, once a template for achieving one or more target outcomes has been developed, the developed template, which could be a generic template or a personalized template, may be provided to one or more end users. An end user may then compliantly execute (i.e., properly execute) the provided template by fully or partially emulating all or some of the one or more emulatable aspects that may be included in the template in order to achieve the one or more target outcomes. Of course, if an end user is unable to compliantly emulate the template, than the one or more target outcomes associated with the template may not be realized.

What constitutes compliant execution of a template will depend on a number of factors including the type of template being emulated and the number and type of emulatable aspects that may be included in the template. For example, in some cases, the compliant execution of a template may require full and complete emulation each of the one or more emulatable aspects that may be included in the template (e.g., if the template requires 45 minutes of running every other day for two months, than to compliantly emulate the template an end user must execute 45 minutes of running every other day for two months). In other cases, however, the compliant execution of a template may merely require that each of the one or more emulatable aspects that may be included in the template be at least substantially emulated or at least only partially emulated (e.g., in the same example above, a compliant execution of the template may be achieved if, for example, on some occasions the end user runs 30 minutes rather than 45 minutes). In still other cases, the compliant execution of a template may only require that a substantial portion of a plurality of emulatable aspects that may be included in the template be fully or substantially emulated (e.g., in the above example, a compliant execution of the template may be achieved even if one or more two days of running are not emulated by the end user).

In various embodiments, methods, systems, circuitry, and computer program products are provided that are designed to, among other things, execute one or more actions in response to detecting deviation from a compliant execution of a template by an end user. For these embodiments, the template may have been originally developed based on selective log entry data of one or more source users provided through, for example, one or more social networking channels (e.g., blogs, microblogs, social networking internet sites, and so forth). In various embodiments, the detecting of the deviation may involve, for example, at least receiving and monitoring log entry data associated with the end user that indicate one or more reported aspects of the end user in order to at least determine whether the one or more emulatable aspects indicated by the template are being at least emulated by the end user. Upon detecting the deviation, a variety of actions may be executed including, for example, presenting one or more advisories, modifying the template and presenting the modified template, or providing (e.g., finding or identifying) and presenting one or more alternative templates. In some embodiments, the methods, systems, circuitry, and computer program products may be implemented by a variety of computing/communication devices including, for example, a network device such as a server (e.g., network servers) or a local client device (e.g., a source user device or an end user device).

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. Of course, and as briefly described above, in some cases, it may also be possible to achieve one or more target outcomes of a template without fully emulating all of the one or more emulatable aspects that may be included in the template or even failing to emulate a portion of a plurality of emulatable aspects that may be included in the template. 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, who may or may not be the source for the one or more reported aspects. That is, a reported aspect 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 indicated above, a template may comprise of one or more emulatable aspects that may be based on reported aspects of, for example, a particular source user. Note that the word “emulatable” as will be repeatedly used herein has no relevant 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 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 an end user may emulate in order to achieve one or more target outcomes. In other cases, however, a template may indicate a plurality of emulatable aspects as well as 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 the end user with respect to the other emulatable aspects included in the template. For example, if a template is designed to facilitate an end user 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) the end user may need to execute in order to achieve the weight loss. Similarly, if the template is designed to, for example, facilitate an end user 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) the end user 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 associated with 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 an end user 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 a 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.

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. In brief, and as will be further described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, 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 that has been reported by, for example, the source user, by one or more sensors, or by one or more third parties (e.g., other source 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, an end user. 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. 10-1a, and 10-1b 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-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-10 may be a server such as one of the one or more network servers 10-60 illustrated in FIG. 10-1a. Alternatively, the computing device 10-10 may be a source user device such as one of the local source user devices 10-20* illustrated in FIG. 10-1a. In still other embodiments, the computing device 10-10 may be an end user device such as the local end user device 10-30 illustrated in FIG. 10-1a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 10-2*” may be in reference to a source user 10-2a, a source user 10-2b, and so forth.

Note further that for ease of understanding and explanation, the computing device 10-10 of the exemplary environment 10-100 of FIGS. 10-1a and 10-1b 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 10-100 of FIG. 10-1a and 10-1b assumes that the computing device 10-10 is a server, the following discussion will, for the most part, be applicable even if the computing device 10-10 were operating as an end user device (e.g., local end user device 10-30*) or as a source user device (e.g., local source user device 10-20*) with certain obvious exceptions (e.g., if the computing device 10-10 is an end user device or a source user device rather than a server, the computing device 10-10 may communicate with an end user 10-4 or a source user 10-2* directly through a user interface 10-120 rather than indirectly through a communication network 10-50 as may be the case when the computing device 10-10 is a server). In some embodiments, the computing device 10-10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 10-1a and 10-1b, and as previously indicated, the computing device 10-10 may be a network device such as a server (e.g., a network server 10-60) that is designed to communicate with other network devices. For example, the computing device 10-10 may communicate with one or more source users 10-2*(e.g., source user 10-2a, source user 10-2b, and so forth) through one or more local source user devices 10-20*(e.g., local source user device 10-20a, local source user device 10-20b, and so forth), with at least one end user 10-4 through at least one local end user device 10-30, with one or more sensor integrated devices 10-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, usage), with one or more network servers 10-60, and/or with one or more third parties 10-6 (e.g., one or more content providers, one or more network service providers, and/or one or more other end users 10-4) via one or more communication networks 10-50. In some implementations, the one or more communication networks 10-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-10 may be designed to develop at least one template 10-16 that is designed to facilitate achievement of one or more target outcomes when one or more emulatable aspects included in the template 10-16 are emulated. The development of the template 10-16 may be based on one or more source user log entries 10-12 that may indicate one or more reported aspects associated with one or more source users 10-2* and that may be received from a variety of sources including for example, one or more network servers 10-60, one or more local source user devices 10-20*, one or more sensor integrated devices 10-40, and/or one or more third parties 10-6. In some cases, such log entries may be in the form of, for example, social networking entries such as blog entries, status reports, and so forth. After receiving the one or more source user log entries 10-12 indicating the one or more reported aspects associated with the one or more source user 10-2*, the template 10-16 may be developed by at least identifying from the one or more reported aspects one or more relevant reported aspects that are relevant to achieving the one or more target outcomes. Once the relevant reported aspects have been identified, the template 10-16 may be developed (e.g., created) by at least including into the template 10-16 one or more emulatable aspects that correspond to the one or more relevant reported aspects. In some cases, the development of the template 10-16 may further include defining in the template 10-16 the relationships (e.g., temporal or specific time relationships) between a plurality of emulatable aspects that may be included in the template 10-16.

After developing the template 10-16, the template 10-16 may be provided to at least one end user 10-4, to one or more network servers 10-60, to one or more third parties 10-6, or to one or more source users 10-2* via one or more communication networks 10-50. In embodiments in which the computing device 10-10 is a local client device such as local end user device 10-30 or a local source user device 10-20*, the template 10-16 may be presented via a user interface 10-120.

In alternative implementations, however, the template 10-16 may not be developed at the computing device 10-10. Instead, the template 10-16 may be developed at a remote network site (e.g., local source user device 10-20*) and provided to the computing device 10-10 via, for example, one or more communication networks 10-50.

In various implementations, after developing or being provided with the template 10-16, the computer device 10-10 may be designed to monitor the progress of an end user 10-4 in compliantly executing the template 10-16 in order to achieve the one or more target outcomes. In other words, the computing device 10-10 may be designed to at least detect deviation from a compliant execution of the template 10-16. In order to monitor the progress of the end user 10-4, the computing device 10-10 may receive one or more end user log entries 10-14 (e.g., microblogs, status reports, journal entries, sensor entries) associated with the end user 10-4 from one or more sources (e.g., local end user device 10-30, one or more sensor integrated devices 10-40, one or more third parties 10-6 such as other end users 10-4 and/or one or more network servers 10-60). The one or more end user log entries 10-14 to be received may indicate one or more reported aspects of the end user 10-4 when, for example, the template 10-16 is being executed. Note that in those embodiments in which the computing device 10-10 is an end user device (e.g., local end user device 10-30), the one or more log entries may be received directly from the end user 10-4 via the user interface 10-120.

In order to determine deviation from the compliant execution of the template 10-16 by the end user 10-4, the one or more reported aspects indicated by the one or more received end user log entries 10-14 may be compared to the one or more emulatable aspects of the template 10-16. By making the comparison, a determination may be made as to whether one or more deviations from the one or more emulatable aspects have occurred. By at least determining that one or more deviations from the one or more emulatable aspects of the template 10-16 have occurred, a determination may be made that a deviation from the compliant emulation of the template 10-16 has also occurred.

Note that in some cases, not all of the detected deviations from the one or more emulatable aspects of the template 10-16 may result in a determination that a deviation from the compliant emulation of the template 10-16 by the end user 10-4 has occurred. For example, suppose one of the emulatable aspects of the template 10-16 requires the end user 10-4 to jog for 45 minutes. If the end user 10-4 is reported as jogging for only 30 minutes instead of the 45 minutes as indicated by the template 10-16 then such a deviation from an emulatable aspect may not result in the conclusion that a deviation from the compliant execution of the template 10-16 has occurred since such a deviation may not be considered significant enough to change the outcome of executing the template 10-16 (e.g., achieving a target outcome). Thus, in some cases, there may be an additional operation after the operation for detecting one or more deviations from the one or more emulatable aspects that requires checking to see if the detected deviations are “significant” deviations. Of course which types of deviations will be considered significant may depend on a number of factors including the type of emulatable aspects that were not at least fully emulated and the type of template 10-16 being executed. Alternatively, those deviations from the one or more emulatable aspects of the template 10-16 that are determined to be not significant may be simply ignored and may simply not be considered as a “deviation.”

In any event, after determining or detecting a deviation from the compliant execution of the template 10-16, the computing device 10-10 may be designed to execute one or more actions. Various types of actions may be executed by the computing device 10-10 in various alternative implementations. For example, in some implementations, upon detecting the deviation from the compliant execution of the template 10-16, the computing device 10-10 may be designed to present one or more advisories. In some cases, the one or more advisories, which may be transmitted to the end user 10-4 or a third party 10-6, may include an alert or warning regarding the deviation. In other cases, the one or more advisories may indicate a recommendation for a future course of action (e.g., switching to a new or a different template).

Another action that may be taken is to modify the template 10-16 in order to accommodate the detected deviation. After modifying the template 10-16, the modified template 10-17 (indicated in FIGS. 10-1a and 10-1b as one or more modified/alternative templates 10-17) may be presented to, for example, the end user 10-4 and/or one or more third parties 10-6 via the one or more communication networks 10-50 and/or via the user interface 10-120. Another action that may be executed is to provide (e.g., identify, find, acquire, or retrieve) one or more alternative templates 10-17 (indicated in FIGS. 10-1a and 10-1b as one or more modified/alternative templates 10-17) that may be completely distinct from the template 10-16. In some cases, the one or more alternative templates 10-17 that are provided may accommodate the detected deviation and may be designed to achieve the same one or more target outcomes of the template 10-16.

In various embodiments, the computing device 10-10, as previously indicated, may be a server (e.g., one of the one or more network servers 10-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-10 is a source user device (e.g., local source user device 10-20*) or an end user device (e.g., local end user device 10-30) rather than a network server 10-60, the computing device 10-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 10-100 of FIGS. 10-1a and 10-1b, the one or more sensor integrated devices 10-40 of the exemplary environment 10-100 of FIGS. 10-1a and 10-1b may directly communicate with the one or more communication networks 10-50 in various embodiments. Alternatively, the one or more sensor integrated devices 10-40 may indirectly communicate with the one or more communication networks 10-50 via the one or more local source user devices 10-20* (e.g., via, for example, personal area network or PAN) or via the local end user device 10-30. In various embodiments, a sensor integrated device 10-40 may be a variety of functional devices that may comprise of one or more sensors 10-240 and that may be operated or used by a source user 10-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 10-240, which may also be included in the one or more local source user devices 10-20*, the local end user device 10-30, and/or the computing device 10-10, may include any type of sensors 10-240 that can sense one or more aspects of a source user 10-2* or an end user 10-4. Examples of such sensors 10-240 include, for example, sensors 10-240 that can sense various physical characteristics of a source user 10-2*(e.g., heart rate sensor or blood pressure sensor), sensors 10-240 that can sense activities of a source user 10-2* (e.g., a pedometer, an accelerometer, and so forth), sensors 10-240 that can sense environment conditions (e.g., air quality sensors), sensors 10-240 that can sense the location of a source user 10-2*(e.g., global positioning system or GPS), sensors 10-240 that can provide physiological data that may be processed in order to determine inferred mental states of users, and so forth.

Each of the one or more local source user devices 10-20* and the local end user device 10-30 (as well as the computing device 10-10 in embodiments in which the computing device 10-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 10-20* and/or the local end user device 10-30 (as well as the computing device 10-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 10-20* and/or local end user device 10-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-10 as illustrated in FIG. 10-1b may include one or more modules, sub-modules, and various other components. As shown, the computing device 10-10 may include at least a deviation detecting module 10-102 (which may further include one or more sub-modules as illustrated in FIG. 10-2a) and an action executing module 10-104 (which may also include one or more sub-modules as illustrated in FIG. 10-2b). The deviation detecting module 10-102 may be particularly configured to, among other things, detect deviation from a compliant execution by an end user 10-4 of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more target outcomes when one or more emulatable aspects included in the template 10-16 are emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users 10-2* that are relevant to achieving the one or more target outcomes. In contrast, the action executing module 10-104 may be particularly configured to, among other things, execute in response to the detection of the deviation one or more actions.

In various implementations, the computing device 10-10 may further include a template developing module 10-105 and a memory 10-116. The template developing module 10-105 may be particularly configured to develop one or more templates 10-16 based on relevant reported aspects of one or more source user 10-2* that have been determined to be relevant for achieving one or more target outcomes. The memory 10-116, in various implementations may store a plurality of templates including the template 10-16 and/or the one or more modified/alternative templates 10-17. In some implementations, the memory 10-116 may store one or more applications (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 10-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-10 may also include, in various implementations, a network interface 10-118 (e.g., a network interface card or NIC), a user interface 10-120 (e.g., a display monitor, a touchscreen, a microphone, a speaker, a mouse, and so forth), and/or one or more sensors 10-240 that are designed to measure or sense one or more user aspects. Examples of sensors 10-240 include, for example, devices that are design 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 monitor, devices that are designed to sense environmental conditions such as sensors 10-240 for measuring air quality, devices that are designed to detect user location such as GPS, and so forth. In some implementations, the presence or absence of some of these modules and components of computing device 10-10 may depend on, for example, whether the computing device 10-10 is a server, an end user device, or a source user device. For example, if the computing device 10-10 is a server, then the computing device 10-10 may not include a user interface 10-120.

In some implementations, the computing device 10-10 may include a log entry receiving module 10-108 that is particularly configured to, among other things, receive one or more log entries associated with users (e.g., an end user 10-4 and/or one or more source users 10-2*). Such log entries (e.g., end user log entries 10-14 and source user log entries 10-12) may be received from a variety of sources including, for example, a local end user device 10-30, one or more local source user devices 10-20*, one or more third parties 10-6, one or more sensor integrated devices 10-40, and/or one or more network servers 10-60. In embodiments in which the computing device 10-10 is a client device such as an end user device or a source user device, the log entries may be directly received from an end user 10-4 or from one or more source users 10-2* via the user interface 10-120.

In various embodiments, the log entry receiving module 10-108 may include a social networking entry receiving module 10-110 that may be particularly configured to receive social networking entries associated with the end user 10-4 and/or associated with one or more source users 10-2*. The social networking entry reception module 10-110 may further include a blog entry receiving module 10-111 configured to receive blog entries (e.g. microblog entries) and/or a status report reception module 10-112 configured to receive social networking status reports. In some implementations, the log entry receiving module 10-108 may include a journal entry receiving module 10-114 that is configured to receive journal entries from the end user 10-4, from the one or more source users 10-2*, and/or from one or more third parties 10-6. In some implementations, the log entry receiving module 10-108 may include a sensor entry receiving module 10-115 that is configured to receive sensor generated entries from one or more sensors 10-240.

FIG. 10-2 a illustrates particular implementations of the deviation detecting module 10-102. The deviation detecting module 10-102 may include a log entry monitoring module 10-202 (which may further include a comparing module 10-204) and an order deviation determining module 10-206. A more detailed discussion of these modules and sub-modules of the deviation detecting module 10-102 will be provided with respect to the processes and operation to be described herein.

FIG. 10-2 b illustrates particular implementations of the action executing module 10-104 of the computing device 10-10 of FIG. 10-1b. As illustrated, the action executing module 10-104 may include an advisory presenting module 10-208 (which may further include a network transmitting module 10-210, a user interface indicating module 10-212, and/or a recommendation presenting module 10-214) and/or a modified/alternative template providing module 10-215. As further illustrated the modified/alternative template providing module 10-215 may further include a template modifying module 10-216 and/or an alternative template providing module 10-236 (which may further include an alternative template presenting module 10-238). In some implementations, the template modifying module 10-216 may further include an emulatable aspect modifying module 10-218 (which may further include an emulatable aspect deleting module 10-220, an emulatable aspect revising module 10-222, and/or an emulatable aspect replacing module 10-224), an emulatable aspect adding module 10-226 (which may further include a plausible emulatable aspect adding module 10-228 and/or a non-conflicting emulatable aspect adding module 10-230), a relationship modifying module 10-232, and/or a modified template presenting module 10-234. A more detailed discussion of these modules and sub-modules of the action executing module 10-104 will be provided with respect to the processes and operation to be described herein.

Referring back to the computing device 10-10 of FIG. 10-1b, the various modules (e.g., the deviation detecting module 10-102, the action executing module 10-104, and so forth) along with their sub-modules included in the computing device 10-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the deviation detecting module 10-102 and/or the action executing module 10-104 may be implemented with a processor 10-602 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 10-604 (e.g., computer program product) stored in a storage medium 10-606 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 10-10 of FIG. 10-6. 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 relating to the functional aspects of the computing device 10-10 of FIG. 10-1b and its components will now be provided with respect to the processes and operations to be described herein. FIG. 10-3 illustrates an operational flow 10-300 representing example operations directed to, among other things, detection of deviation from a compliant execution of a template by an end user 10-4, and executing one or more actions in response to the detection of the deviation.

In FIG. 10-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 10-100 described above as illustrated in FIGS. 10-1a and 10-1b, and/or with respect to other examples (e.g., as provided in FIGS. 10-2a and 10-2b) 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. 10-1a, 10-1b, 10-2a, and 10-2b. 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. 10-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 10-300 may move to a deviation detecting operation 10-302 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. For instance, and as an illustration, the deviation detecting module 10-102 of the computing device 10-10 of FIG. 10-1b detecting deviation from a compliant execution of a template 10-16 by an end user 10-4, the template 10-16 designed to facilitate the end user 10-4 to achieve one or more target outcomes 10-16 (e.g., health or medical outcomes, mental state outcomes, academic or intellectual outcomes, and so forth) when one or more emulatable aspects (e.g., user acts or behaviors) included in the template 10-16 are emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users 10-2* that are relevant to achieving the one or more target outcomes.

In addition to the deviation detecting operation 10-302, operational flow 10-300 may also include an action executing operation 10-304 for executing one or more actions in response to the detecting of the deviation. For instance, the action executing module 10-104 of the computing device 10-10 executing one or more actions (e.g., presenting advisories, presenting modified and/or an alternative templates 10-17, and so forth) in response to the detecting of the deviation. As will be further described herein, both the deviation detecting operation 10-302 and the action executing operation 10-304 of FIG. 10-3 may be executed in a number of different ways in various alternative implementations.

For example, FIGS. 10-4a, 10-4b, 10-4c and 10-4d illustrate the various ways that the deviation detecting operation 10-302 of FIG. 10-3 may be executed in various alternative implementations. For instance, the deviation from the compliant execution of the template 10-16 by the end user 10-4 to be detected through the deviation detecting operation 10-302 may be performed in a variety of different ways. For example, in some implementations, the deviation detecting operation 10-302 of FIG. 10-3 may include an operation 10-402 for detecting the deviation from the compliant execution of the template by at least receiving one or more end user log entries associated with the end user as depicted in FIG. 10-4a. For instance, the deviation detecting module 10-102 including the log entry receiving module 10-108 (see FIG. 10-1b) of the computing device 10-10 detecting the deviation from the compliant execution of the template 10-16 when the log entry receiving module 10-108 at least receives one or more end user log entries 10-14 associated with the end user 10-4.

In some implementations, operation 10-402 may further include an operation 10-403 for monitoring the one or more received end user log entries to detect deviation from the one or more emulatable aspects included in the template, the one or more received end user log entries indicating one or more reported aspects of the end user as depicted in FIG. 10-4a. For instance, the log entry monitoring module 10-202 (see FIG. 10-2a) of the computing device 10-10 monitoring the one or more received end user log entries 10-14 to detect deviation from the one or more emulatable aspects included in the template 10-16, the one or more received end user log entries 10-14 indicating one or more reported aspects of the end user 10-4.

In various implementations, operation 10-403 may further include an operation 10-404 for comparing the one or more reported aspects of the end user to the one or more emulatable aspects included in the template to determine whether one or more deviations from the one or more emulatable aspects have occurred as depicted in FIG. 10-4a. For instance, the comparing module 10-204 (see FIG. 10-2a) of the computing device 10-10 comparing the one or more reported aspects of the end user 10-4 (as indicated by the end user log entries 10-14) to the one or more emulatable aspects included in the template 10-16 to determine whether one or more deviations from the one or more emulatable aspects has occurred.

Operation 10-404, in turn, may further include an operation 10-405 for comparing the one or more reported aspects of the end user to the one or more emulatable aspects included in the template to determine whether one or more deviations from the one or more emulatable aspects has occurred, the one or more emulatable aspects including at least one emulatable aspect that is an emulatable intermediate outcome associated with at least one of the one or more target outcomes as depicted in FIG. 10-4a. For instance, the comparing module 10-204 (see FIG. 10-2a) of the computing device 10-10 comparing the one or more reported aspects of the end user 10-4 to the one or more emulatable aspects included in the template 10-16 to determine whether one or more deviations from the one or more emulatable aspects has occurred, the one or more emulatable aspects including at least one emulatable aspect that is an emulatable intermediate outcome (e.g., lowering systolic blood pressure by 10 mmHg) associated with at least one of the one or more target outcomes (e.g., lowering systolic blood pressure by 30 mmHg).

Various types of end user log entries 10-14 may be received through operation 10-402 in various implementations. For example, in some implementations, operation 10-402 may include an operation 10-406 for receiving the one or more end user log entries including receiving one or more social networking entries associated with the end user as depicted in FIG. 10-4a. For instance, the log entry receiving module 10-108 including the social networking entry receiving module 10-110 of the computing device 10-10 receiving the one or more end user log entries 10-14 including the social networking entry receiving module 10-110 receiving one or more social networking entries associated with the end user 10-4.

In some implementations, operation 10-406 may further include an operation 10-407 for receiving the one or more end user log entries including receiving one or more blog entries associated with the end user as depicted in FIG. 10-4a. For instance, the log entry receiving module 10-108 including the blog entry receiving module 10-111 of the computing device 10-10 receiving the one or more end user log entries 10-14 including the blog entry receiving module 10-111 receiving one or more blog entries (e.g. microblog entries) associated with the end user 10-4.

In the same or different implementations, operation 10-406 may include an operation 10-408 for receiving the one or more end user log entries including receiving one or more status reports associated with the end user as depicted in FIG. 10-4a. For instance, the log entry receiving module 10-108 including the status report receiving module 10-112 of the computing device 10-10 receiving the one or more end user log entries 10-14 including the status report receiving module 10-112 receiving one or more status reports associated with the end user 10-4.

Other types of end user log entries 10-14 may be received through operation 10-402 in various alternative embodiments. For example, in some implementations, operation 10-402 may include an operation 10-409 for receiving the one or more end user log entries including receiving one or more journal entries associated with the end user as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 including the journal entry receiving module 10-114 (see FIG. 10-1b) of the computing device 10-10 receiving the one or more end user log entries 10-14 including the journal entry receiving module 10-114 receiving one or more journal entries associated with the end user 10-4.

The one or more end user log entries 10-14 to be received through operation 10-402 may be from a variety of sources in various embodiments. For example, in some implementations, operation 10-402 may include an operation 10-410 for receiving the one or more end user log entries from the end user as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 of the computing device 10-10 receiving (e.g., receiving via one or more communication networks 10-50 or via the user interface 10-120) the one or more end user log entries 10-14 from the end user 10-4.

In the same or different implementations, operation 10-402 may include an operation 10-411 for receiving the one or more end user log entries from one or more sensors as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 including the sensor entry receiving module 10-115 of the computing device 10-10 receiving one or more end user log entries 10-14 from one or more sensors 10-240 (e.g., sensors 10-240 that can sense physiological characteristics of the end user 10-4 such as heart rate monitor, sensors 10-240 that can sense activities of the end user 10-4 such as an accelerometer, sensors 10-240 that can sense environmental conditions such as sensors 10-240 for sensing air quality, GPS, and so forth).

In the same or different implementations, operation 10-402 may include an operation 10-412 for receiving the one or more end user log entries from one or more sensor integrated devices as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 including the sensor entry receiving module 10-115 of the computing device 10-10 receiving the one or more end user log entries 10-14 from one or more sensor integrated devices 10-40 (e.g., automobile, exercise machine, household appliance, and so forth).

In the same or different implementations, operation 10-402 may include an operation 10-413 for receiving the one or more end user log entries from one or more third party sources as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 of the computing device 10-10 receiving the one or more end user log entries 10-14 from one or more third party sources (e.g., one or more third parties 10-6 such as other end users or content providers).

In the same or different implementations, operation 10-402 may include an operation 10-414 for receiving the one or more end user log entries via one or more communication networks as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 of the computing device 10-10 receiving the one or more end user log entries 10-14 via one or more communication networks 10-50 (e.g., a wireless network such as WiMAX or a cellular network).

In the same or different implementations, operation 10-402 may include an operation 10-415 for receiving the one or more end user log entries via a user interface as depicted in FIG. 10-4b. For instance, the log entry receiving module 10-108 of the computing device 10-10 receiving the one or more end user log entries 10-14 via a user interface 10-120 (e.g., a keypad or keyboard, a touchscreen, a microphone, a mouse, and so forth).

In various implementations, the deviation detecting operation 10-302 of FIG. 10-3 may include an operation 10-416 for detecting the deviation from the compliant execution of the template by at least detecting whether each of the one or more emulatable aspects included in the template were fully emulated, partially emulated, or not emulated at all by the end user as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting the deviation from the compliant execution of the template 10-16 by at least detecting whether each of the one or more emulatable aspects included in the template 10-16 were fully emulated, partially emulated, or not emulated at all by the end user 10-4. That is, in some cases in order to achieve a “compliant execution” of the template 10-16 all of the one or more emulatable aspects may need to be fully or completely emulated. In other cases, however, at least a portion of the one or more emulatable aspects included in the template 10-16 may be allowed to be partially emulated without deviating from the compliant execution of the template 10-16. In still other cases, at least a portion of the one or more emulatable aspects included in the template 10-16 may be allowed to be not emulated at all without deviating from the compliant execution of the template 10-16.

In some implementations, the deviation detecting operation 10-302 of FIG. 10-3 may include an operation 10-417 for detecting the deviation from the compliant execution of the template by at least determining whether a plurality of emulatable aspects included in the template were emulated in a particular order as indicated by the template as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 including the order deviation determining module 10-206 of the computing device 10-10 detecting the deviation from the compliant execution of the template 10-16 when the order deviation determining module 10-206 at least determines whether a plurality of emulatable aspects included in the template 10-16 were emulated in a particular order as indicated by the template 10-16.

In some cases, operation 10-417 may include an operation 10-418 for detecting the deviation from the compliant execution of the template by at least determining whether the plurality of emulatable aspects included in the template were emulated in a particular temporal order as indicated by the template as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 including the order deviation determining module 10-206 of the computing device 10-10 detecting the deviation from the compliant execution of the template 10-16 when the order deviation determining module 10-206 at least determines whether the plurality of emulatable aspects included in the template 10-16 were emulated in a particular temporal order as indicated by the template 10-16.

In some cases, operation 10-417 may include an operation 10-419 for detecting the deviation from the compliant execution of the template by at least determining whether the plurality of emulatable aspects included in the template were emulated in a particular specific time order as indicated by the template as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 including the order deviation determining module 10-206 of the computing device 10-10 detecting the deviation from the compliant execution of the template 10-16 when the order deviation determining module 10-206 at least determines whether the plurality of emulatable aspects included in the template 10-16 were emulated in a particular specific time order as indicated by the template 10-16.

Various types of templates 10-16 may be involved in the deviation detecting operation 10-302 of FIG. 10-3. For example, in some implementations, the deviation detection operation 10-302 may include an operation 10-420 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that was developed based, at least in part, on selective acquisition or identification of the one or more relevant reported aspects from a plurality of reported aspects of at least the one or more source users as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that was developed based, at least in part, on selective acquisition or identification of the one or more relevant reported aspects from a plurality of reported aspects of at least the one or more source users 10-2*.

In some implementations, the deviation detection operation 10-302 may include an operation 10-421 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more health or medical outcomes as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more health or medical outcomes (e.g., reduce blood glucose level, improve results of treatment for leukemia, and so forth).

In some implementations, the deviation detection operation 10-302 may include an operation 10-422 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more athletic or gaming outcomes as depicted in FIG. 10-4c. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more athletic or gaming outcomes (e.g., lowering golf handicap, improve stamina, achieve a particular chess ranking, and so forth).

In some implementations, the deviation detection operation 10-302 may include an operation 10-423 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more occupational outcomes as depicted in FIG. 10-4d. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more occupational outcomes (e.g., obtain a promotion, complete a particular project on time, and so forth).

In some implementations, the deviation detection operation 10-302 may include an operation 10-424 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more social or leisure outcomes as depicted in FIG. 10-4d. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more social or leisure outcomes (e.g., increase dating activities, setting aside more time or more money for vacations, and so forth).

In some implementations, the deviation detection operation 10-302 may include an operation 10-425 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more sexual intimacy outcomes as depicted in FIG. 10-4d. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more sexual intimacy outcomes (e.g., improve frequency and length of sexual intimacy activities).

In some implementations, the deviation detection operation 10-302 may include an operation 10-426 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more academic or intellectual outcomes as depicted in FIG. 10-4d. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more academic or intellectual outcomes (e.g., being accepted into a particular University, achieving a particular grade point average, and so forth).

In some implementations, the deviation detection operation 10-302 may include an operation 10-427 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more spiritual or religious outcomes as depicted in FIG. 10-4d. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve one or more spiritual or religious outcomes (e.g., achieve spiritual harmony, acceptance to a particular church or religion, and so forth).

In some implementations, the deviation detection operation 10-302 may include an operation 10-428 for detecting deviation from the compliant execution of the template including detecting deviation from a compliant execution, by the end user, of a template that is designed to facilitate the end user to achieve one or more user state outcomes as depicted in FIG. 10-4d. For instance, the deviation detecting module 10-102 of the computing device 10-10 detecting deviation from the compliant execution of the template 10-16 including detecting deviation from a compliant execution, by the end user 10-4, of a template 10-16 that is designed to facilitate the end user 10-4 to achieve 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 back to FIG. 10-3, the action executing operation 10-304 may be implemented in a number of different ways in various implementations. For example, in some implementations, the action executing operation 10-304 of FIG. 10-3 may include an operation 10-529 for presenting one or more advisories related to the deviation in response to the detecting of the deviation as depicted in FIG. 10-5a. For instance, the advisory presenting module 10-208 (see FIG. 10-2b) of the computing device 10-10 presenting one or more advisories 10-18 related to the deviation in response to the detecting of the deviation.

In various implementations, various types of advisories 10-18 may be presented in various alternative ways. For example, in some implementations, operation 10-529 may include an operation 10-530 for transmitting the one or more advisories via one or more communication networks as depicted in FIG. 10-5a. For instance, the network transmitting module 10-210 (see FIG. 10-2b) of the computing device 10-10 transmitting the one or more advisories 10-18 via one or more communication networks 10-50.

In the same or different implementations, operation 10-529 may include an operation 10-531 for indicating the one or more advisories via a user interface as depicted in FIG. 10-5a. For instance, the user interface indicating module 10-212 (see FIG. 10-2b) of the computing device 10-10 indicating the one or more advisories 10-18 via a user interface 10-120.

In the same or different implementations, operation 10-529 may include an operation 10-532 for presenting the one or more advisories through one or more social networking channels as depicted in FIG. 10-5a. For instance, the advisory presenting module 10-208 of the computing device 10-10 presenting the one or more advisories 10-18 through one or more social networking channels.

Various types of social networking channels may be employed in order to present the one or more advisories 10-18. For example, in some implementations, operation 10-532 may include an operation 10-533 for presenting the one or more advisories through one or more blogs as depicted in FIG. 10-5a. For instance, the advisory presenting module 10-208 of the computing device 10-10 presenting the one or more advisories 10-18 through one or more blogs (e.g., microblogs).

In the same or different implementations, operation 10-532 may include an operation 10-534 for presenting the one or more advisories through one or more social networking internet sites as depicted in FIG. 10-5a. For instance, the advisory presenting module 10-208 of the computing device 10-10 presenting the one or more advisories 10-18 through one or more social networking internet sites.

In some implementations, operation 10-529 for presenting the one or more advisories may include an operation 10-535 for presenting the one or more advisories to at least one of the end user and a third party as depicted in FIG. 10-5a. For instance, the advisory presenting module 10-208 of the computing device 10-10 presenting the one or more advisories 10-18 to at least one of the end user 10-4 and a third party 10-6 (e.g., another end user 10-4).

In the same or different implementations, operation 10-529 may include an operation 10-536 for presenting the one or more advisories including one or more alerts indicating the deviation as depicted in FIG. 10-5a. For instance, the advisory presenting module 10-208 of the computing device 10-10 presenting the one or more advisories 10-18 including one or more alerts indicating the deviation.

In the same or different implementations, operation 10-529 may include an operation 10-537 for presenting the one or more advisories including one or more recommendations as depicted in FIG. 10-5a. For instance, the recommendation presenting module 10-214 (see FIG. 10-2b) of the computing device 10-10 presenting the one or more advisories 10-18 including one or more recommendations (e.g., recommendation for a future course of action).

In some implementations, operation 10-537 may further include an operation 10-538 for presenting at least one recommendation for a substitute template for emulating by the end user as depicted in FIG. 10-5a. For instance, the recommendation presenting module 10-214 of the computing device 10-10 presenting at least one recommendation for a substitute template for emulating by the end user 10-4. In various implementations, a substitute template may be a modified version of the template 10-16 or may be an alternative template 10-17 (e.g., an alternative template 10-17 that is completely new or unrelated to the “original” template 10-16). Note that in FIGS. 10-1a and 10-1b, the modified/alternative template[s] 10-17 represents a modified version of the template 10-16 and/or an alternative template 10-17.

Operation 10-538 may, in turn, further include an operation 10-539 for presenting at least one recommendation for a substitute template for emulating by the end user, the substitute template being a modified version of the template as depicted in FIG. 10-5a. For instance, the recommendation presenting module 10-214 of the computing device 10-10 presenting at least one recommendation for a substitute template 10-16 for emulating by the end user 10-4, the substitute template 10-16 being a modified version of the template 10-16 (e.g., modified/alternative template 10-17).

In some implementations, operation 10-537 for presenting one or more recommendations may include an operation 10-540 for presenting at least one recommendation to discontinue emulating the template as depicted in FIG. 10-5a. For instance, the recommendation presenting module 10-214 of the computing device 10-10 presenting at least one recommendation to discontinue emulating the template 10-16.

In various implementations, the one or more actions executed in the action executing operation 10-304 of FIG. 10-3 may include at least one action to modify the template 10-16. For example, in some implementations, the action executing operation 10-304 may include an operation 10-541 for modifying the template in response to the detecting of the deviation as depicted in FIG. 10-5b. For instance, the template modifying module 10-216 (see FIG. 10-2b) of the computing device 10-10 modifying the template 10-16 in response to the detecting of the deviation.

Clearly, there are many ways that the template 10-16 may be modified. For example, in some implementations, operation 10-541 may include an operation 10-542 for modifying the template including modifying at least one of the one or more emulatable aspects included in the template as depicted in FIG. 10-5b. For instance, the template modifying module 10-216 including the emulatable aspect modifying module 10-218 (see FIG. 10-2b) of the computing device 10-10 modifying the template 10-16 including the emulatable aspect modifying module 10-218 modifying at least one of the one or more emulatable aspects included in the template 10-16.

Operation 10-542 for modifying one or more emulatable aspects included in the template 10-16 may further include one or more additional operations in various implementations. For example, in some implementations, operation 10-542 may include an operation 10-543 for modifying the at least one of the one or more emulatable aspects included in the template by deleting the at least one of the one or more emulatable aspects as depicted in FIG. 10-5b. For instance, the emulatable aspect modifying module 10-218 including the emulatable aspect deleting module 10-220 modifying the at least one of the one or more emulatable aspects included in the template 10-16 by having the emulatable aspect deleting module 10-220 delete the at least one of the one or more emulatable aspects.

In the same or different implementations, operation 10-542 may include an operation 10-544 for modifying the at least one of the one or more emulatable aspects included in the template by revising the at least one of the one or more emulatable aspects as depicted in FIG. 10-5b. For instance, the emulatable aspect modifying module 10-218 including the emulatable aspect revising module 10-222 modifying the at least one of the one or more emulatable aspects included in the template 10-16 by having the emulatable aspect revising module 10-222 revise (e.g., edit) the at least one of the one or more emulatable aspects.

In the same or different implementations, operation 10-542 may include an operation 10-545 for modifying the at least one of the one or more emulatable aspects included in the template by replacing the at least one of the one or more emulatable aspects with one or more alternative emulatable aspects as depicted in FIG. 10-5b. For instance, the emulatable aspect modifying module 10-218 including the emulatable aspect replacing module 10-224 modifying the at least one of the one or more emulatable aspects included in the template 10-16 by having the emulatable aspect replacing module 10-224 replace the at least one of the one or more emulatable aspects with one or more alternative emulatable aspects.

In the same or different implementations, operation 10-542 may include an operation 10-546 for modifying the at least one of the one or more emulatable aspects to include into the template one or more plausible emulatable aspects that have been successfully emulated by one or more third parties as depicted in FIG. 10-5b. For instance, the emulatable aspect modifying module 10-218 of the computing device 10-10 modifying the at least one of the one or more emulatable aspects to include into the template 10-16 one or more plausible emulatable aspects that have been successfully emulated by one or more third parties 10-6 (e.g., another end user 10-4).

In some cases, 10-546 may, in turn, include an operation 10-547 for modifying the at least one of the one or more emulatable aspects to include into the template one or more plausible emulatable aspects that have been successfully emulated by one or more other end users in order to achieve the one or more target outcomes as depicted in FIG. 10-5b. For instance, the emulatable aspect modifying module 10-218 of the computing device 10-10 modifying the at least one of the one or more emulatable aspects to include into the template 10-16 one or more plausible emulatable aspects that have been successfully emulated by one or more other end users 10-4 in order to achieve the one or more target outcomes.

In various implementations, the operation 10-541 to modify the template 10-16 may include an operation 10-548 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template (e.g., modified/alternative template 10-17 of FIGS. 10-1a and 10-1b) that includes one or more emulatable aspects that does not conflict with one or more limitations (e.g., dietary or religious limitations) of the end user 10-4. In other words, to modify the template 10-16 without violating any limitations associated with the end user 10-4.

This may mean that in some implementations, operation 10-548 may include an operation 10-549 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more ability or skill limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more ability or skill limitations of the end user 10-4 (e.g., does not know how to use a spreadsheet or does not know how to swim).

In the same or different implementations, operation 10-548 may include an operation 10-550 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more physical limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more physical limitations (e.g., having severe arthritis) of the end user 10-4.

In the same or different implementations, operation 10-548 may include an operation 10-551 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more contextual limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template (e.g., modified/alternative template 10-17 of FIGS. 10-1a and 10-1b) that includes one or more emulatable aspects that does not conflict with one or more contextual limitations (e.g., logistical limitations such as unavailability of personal transportation vehicle) of the end user 10-4.

In the same or different implementations, operation 10-548 may include an operation 10-552 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more personal limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more personal limitations (e.g., disdain for certain ethnic foods) of the end user 10-4.

In the same or different implementations, operation 10-548 may include an operation 10-553 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more legal or regulatory limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more legal or regulatory limitations (e.g., local drug regulations) of the end user 10-4.

In the same or different implementations, operation 10-548 may include an operation 10-554 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more psychological limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more psychological limitations (e.g., phobias) of the end user 10-4.

In the same or different implementations, operation 10-548 may include an operation 10-555 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more user state limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more user state limitations (e.g., married or fatigued) of the end user 10-4.

In the same or different implementations, operation 10-548 may include an operation 10-556 for modifying the template resulting in a modified template that includes one or more emulatable aspects that does not conflict with one or more health or medical limitations of the end user as depicted in FIG. 10-5c. For instance, the template modifying module 10-216 of the computing device 10-10 modifying the template 10-16 resulting in a modified template 10-17 that includes one or more emulatable aspects that does not conflict with one or more health or medical limitations (e.g., lactose intolerant, defective heart, and so forth) of the end user 10-4.

In some implementations, the operation 10-541 for modifying the template 10-16 may include an operation 10-557 for modifying the template by adding one or more additional emulatable aspects into the template as depicted in FIG. 10-5d. For instance, the template modifying module 10-216 including the emulatable aspect adding module 10-226 of the computing device 10-10 modifying the template 10-16 when the emulatable aspect adding module 10-226 adds one or more additional emulatable aspects into the template 10-16.

In some implementations, operation 10-557 may include an operation 10-558 for modifying the template by adding one or more plausible emulatable aspects into the template, the one or more plausible emulatable aspects being successfully emulated by one or more third parties as depicted in FIG. 10-5d. For instance, the template modifying module 10-216 including the plausible emulatable aspect adding module 10-228 of the computing device 10-10 modifying the template 10-16 when the plausible emulatable aspect adding module 10-228 adds one or more plausible emulatable aspects into the template 10-16, the one or more plausible emulatable aspects being successfully emulated by one or more third parties 10-6.

In the same or different implementations, operation 10-557 may include an operation 10-559 for modifying the template by adding one or more additional emulatable aspects into the template, the one or more additional emulatable aspects not conflicting with one or more limitations of the end user as depicted in FIG. 10-5d. For instance, the template modifying module 10-216 including the non-conflicting emulatable aspect adding module 10-230 of the computing device 10-10 modifying the template 10-16 when the non-conflicting emulatable aspect adding module 10-230 adds one or more additional emulatable aspects into the template 10-16, the one or more additional emulatable aspects not conflicting with one or more limitations of the end user 10-4.

In various implementations, the operation 10-541 for modifying the template 10-16 may include an operation 10-560 for modifying one or more relationships indicated by the template defining one or more relationships between a plurality of emulatable aspects included in the template as depicted in FIG. 10-5d. For instance, the relationship modifying module 10-232 (see FIG. 10-2b) of the computing device 10-10 modifying one or more relationships indicated by the template 10-16 that defines one or more relationships (e.g., temporal, specific time, and/or spatial relationships) between a plurality of emulatable aspects included in the template 10-16.

In the same or different implementations, operation 10-541 may include an operation 10-561 for presenting the modified template to at least one of the end user and a third party as depicted in FIG. 10-5d. For instance, the modified template presenting module 10-234 of the computing device 10-10 presenting (e.g., transmitting via communication network 10-50 or indicating via a user interface 10-120) the modified template 10-17 to at least one of the end user 10-4 and a third party 10-6.

Referring back to the action executing operation 10-304 of FIG. 10-3, in various embodiments, the action executing operation 10-304 may include an operation 10-562 for providing one or more alternative templates in response to the detecting of the deviation as depicted in FIG. 10-5d. For instance, the alternative template providing module 10-236 (see FIG. 10-2b) of the computing device 10-10 providing (e.g., identifying or retrieving) one or more alternative templates (e.g., modified/alternative template 10-17 of FIGS. 10-1a and 10-1b) in response to the detecting of the deviation. Note that as described here an alternative template 10-17, with the exception of having common target outcomes, may be completely unrelated to the template 10-16. In other words, an alternative template 10-17 is not the modified version of the template 10-16.

In various implementations, operation 10-562 may further include an operation 10-563 for providing the one or more alternative templates from a plurality of templates, the providing being based, at least in part, on the one or more alternative templates' association with the one or more target outcomes as depicted in FIG. 10-5d. For instance, the alternative template providing module 10-236 of the computing device 10-10 providing the one or more alternative templates 10-17 from a plurality of templates, the providing being based, at least in part, on the association of the one or more alternative templates with the one or more target outcomes. Note that the plurality of templates may be stored in a memory 10-116 and/or located at one or more network sites (e.g., local source user devices 10-20*, network servers 10-60, and so forth) of one or more communication networks 10-50.

In some implementations, operation 10-563 may include an operation 10-564 for providing the one or more alternative templates from the plurality of templates, the providing being based, at least in part, on the one or more alternative templates' association with the one or more source users as depicted in FIG. 10-5d. For instance, the alternative template providing module 10-236 of the computing device 10-10 providing the one or more alternative templates 10-17 from a plurality of templates, the providing being based, at least in part, on the association of the one or more alternative templates 10-17 with the one or more source users 10-2*.

In the same or different implementations, operation 10-563 may include an operation 10-565 for providing the one or more alternative templates from the plurality of templates by providing one or more alternative templates that are compatible with the detected deviation as depicted in FIG. 10-5d. For instance, the alternative template providing module 10-236 of the computing device 10-10 providing the one or more alternative templates 10-17 from a plurality of templates by providing one or more alternative templates 10-17 that are compatible with the detected deviation. In other words, providing alternative templates 10-17 that will still result in the one or more target outcomes being achieved even with the occurrence of the deviation so long as the alternative templates 10-17 are compliantly emulated.

In some cases, operation 10-365 may further include an operation 10-566 for providing the one or more alternative templates that are compatible with the detected deviation by providing one or more alternative templates that include one or more emulatable aspects that correspond to the detected deviation as depicted in FIG. 10-5d. For instance, the alternative template providing module 10-236 of the computing device 10-10 providing the one or more alternative templates 10-17 that are compatible with the detected deviation by providing one or more alternative templates 10-17 that include one or more emulatable aspects that correspond to the detected deviation. In other words, one way to find alternative templates 10-17 is to find those that already include the detected deviation as one of their emulatable aspects. For example, if the detected deviation was to swim rather than jog as required by the template 10-16, then an alternative template 10-17 that is designed to achieve the same one or more target outcomes and that include at least an emulatable aspect that requires swimming may be provided.

In various implementations, the operation 10-562 for providing the one or more alternative templates 10-17 may include an operation 10-567 for presenting the one or more alternative templates to at least one of the end user and a third party as depicted in FIG. 10-5d. For instance, the alternative template presenting module 10-238 (see FIG. 10-2b) of the computing device 10-10 presenting the one or more alternative templates 10-17 to at least one of the end user 10-4 and a third party 10-6.

Turning now to FIG. 10-6, which is a high-level block diagram illustrating a particular implementation of the computing device 10-10 of FIG. 10-1b. As illustrated, the computing device 10-10 may include a processor 10-602 (e.g., microprocessor, controller, and so forth) coupled to storage medium 10-606 (e.g., volatile or non-volatile memory). The storage medium 10-606 may store computer readable instructions 10-604 (e.g., computer program product). The processor 10-602, in various implementations, may execute the computer readable instructions 10-604 in order to execute one or more operations described above and as illustrated in FIGS. 10-3, 10-4a, 10-4b, 10-4c, 10-4d, 10-5a, 10-5b, 10-5c, and 10-5d.

For example, the processor 10-602 may execute the computer readable instructions 10-604 in order to detect deviation from a compliant execution of a template 10-16 by an end user 10-4, the template 10-16 designed to facilitate the end user 10-4 to achieve one or more target outcomes when one or more emulatable aspects included in the template 10-16 are compliantly emulated, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users 10-2* that are relevant to achieving the one or more target outcomes; and/or to execute one or more actions in response to the detecting of the deviation as illustrated by the operational flow 10-300 of FIG. 10-3.

XII. Template Modification Based on Deviation from Compliant Execution of the Template

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 journal. One place where such open journals 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 become very popular in recent times 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 journals 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 their usage. 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 “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 the others 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 are generic templates that may not be designed for use by any particular end user or a particular group of end users but instead may be designed to be used 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 any event, once a template for achieving one or more target outcomes has been developed, the developed template, which could be a generic template or a personalized template, may be provided to one or more end users. An end user may then compliantly execute (i.e., properly execute) the provided template by fully or partially emulating all or some of the one or more emulatable aspects that may be included in the template in order to achieve the one or more target outcomes. Of course, if an end user is unable to compliantly emulate the template, than the one or more target outcomes associated with the template may or may not be realized. In many cases, however, it may still be possible to achieve the target outcomes associated with templates even if end users do not compliantly execute the templates.

What constitutes compliant execution of a template will depend on a number of factors including, for example, the type of template being emulated and the number and type of emulatable aspects that may be included in the template. For example, in some cases, the compliant execution of a template may require full and complete emulation of each of the one or more emulatable aspects that may be included in the template (e.g., if the template requires 45 minutes of running every other day for two months, than to compliantly emulate the template an end user must execute 45 minutes of running every other day for two months).

In other cases, however, the compliant execution of a template may merely require that each of the one or more emulatable aspects that may be included in the template be at least substantially emulated or at least only partially emulated (e.g., in the same example above, a compliant execution of the template may be achieved if, for example, on some occasions the end user runs 30 minutes rather than 45 minutes). In still other cases, the compliant execution of a template may only require that a substantial portion of a plurality of emulatable aspects that may be included in the template be fully or substantially emulated (e.g., in the above example, a compliant execution of the template may be achieved even if one or more two days of running are not emulated by the end user).

For purposes of this description, and unless indicated otherwise, the phrase “compliant execution of a template” may be in reference to a complete or substantially complete emulation of each of the one or more emulatable aspects that may be included the template. Further, in some cases, the “compliant execution of a template” may be in reference to a plurality of emulatable aspects that may be included in the template to be completely or substantially completely emulated in the order (e.g., sequential order) that is specified by the template.

In some cases, it may be possible to achieve one or more target outcomes of a template without strictly or compliantly executing the template. That is, upon end users executing a particular template, some end users may deviate from complete and total emulation of each of the one or more emulatable aspects that may be included in the particular template while still achieving the target outcomes.

In various embodiments, methods, systems, circuitry, and computer program products are provided that are designed to modify a template based on feedback provided by end users. More particularly, the methods, systems, circuitry, and computer program products may be designed to, among other things, modify a template based, at least in part, on determining that a plurality of end users deviated from compliantly executing the template. In some embodiments, the determining of the deviation may involve, for example, at least acquiring and processing log entry data (e.g., as acquired through blogs, microblogs, social networking internet sites, and so forth) associated with those end users who have deviated from the compliant execution of the template while still achieving the one or more target outcomes associated with the template. In some embodiments, the modification of the template may be based, at least, on the processing of the log entry data.

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. Of course, and as briefly described above, in some cases, it may also be possible to achieve one or more target outcomes of a template without fully emulating all of the one or more emulatable aspects that may be included in the template or even failing to emulate a portion of a plurality of emulatable aspects that may be included in the template. As also indicated earlier, 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, who may or may not be the source for the one or more reported aspects. That is, a reported aspect 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). Similarly, reported aspects of an end user, such as reported aspects of the end user while the end user is executing a template, may also be provided by a number of different sources. Such reported aspects of the end user may be used, in some cases, as end user feedback in order to modify or further develop a template.

As described, a template may comprise of one or more emulatable aspects that may be based on reported aspects of, for example, a particular source user. Note that the word “emulatable” as will be repeatedly used herein has no relevant 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 or end 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 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 cases, however, a template may indicate a plurality of emulatable aspects as well as 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. In brief, and as will be further described herein, an “aspect” may be any occurrence of any behavior, act, belief, characteristic, state, 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, by 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. 11-1a, and 11-1b 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 11-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 11-10 may be a server such as one of the one or more network servers 11-60 illustrated in FIG. 11-1a. Alternatively, the computing device 11-10 may be a source user device such as one of the local source user devices 11-20* illustrated in FIG. 11-1a. In still other embodiments, the computing device 11-10 may be an end user device such as one of the local end user device 11-30* illustrated in FIG. 11-1a. Note that in the following, “*” represents a wildcard. Thus, references in the following description to, for example, “a source user 11-2” may be in reference to a source user 11-2a, a source user 11-2b, and so forth, or a combination thereof.

Note further that for ease of understanding and explanation, the computing device 11-10 of the exemplary environment 11-100 of FIGS. 11-1a and 11-1b 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 11-100 of FIG. 11-1a and 11-1b assumes that the computing device 11-10 is a server, the following discussion will, for the most part, be applicable even if the computing device 11-10 were operating as an end user device (e.g., local end user device 1′-30*) or as a source user device (e.g., local source user device 1′-20*) with certain obvious exceptions (e.g., if the computing device 11-10 is an end user device or a source user device rather than a server, the computing device 11-10 may communicate with an end user 11-4* or a source user 11-2* directly through a user interface 11-120 rather than indirectly through one or more communication networks 11-50 as may be the case when the computing device 11-10 is a server). In some embodiments, the computing device 11-10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 11-1a and 1′-1b, and as previously indicated, the computing device 11-10 may be a network device such as a server (e.g., a network server 11-60) that is designed to communicate with other network devices. For example, the computing device 11-10 may communicate with one or more source users 11-2*(e.g., source user 11-2a, source user 11-2b, and so forth) through one or more local source user devices 11-20*(e.g., local source user device 11-20a, local source user device 11-20b, and so forth), with a plurality of end users 11-4*(e.g., end user 11-4a, end user 11-4b, and so forth) through a plurality of local end user devices 11-30*(e.g., local end user device 11-30a, local end user device 11-30b, and so forth), with one or more sensor integrated devices 11-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, usage), with one or more network servers 11-60, and/or with one or more third parties 11-6 (e.g., one or more content providers, one or more network service providers, and/or one or more other end users 11-4) via one or more communication networks 11-50. In some implementations, the one or more communication networks 11-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 11-10 may be designed to develop at least one template 11-16 that is designed to facilitate achievement of one or more target outcomes when one or more emulatable aspects included in the template 11-16 are emulated. The development of the template 11-16 may be based on one or more source user log entries 11-12 that may indicate one or more reported aspects associated with one or more source users 11-2* and that may be received from a variety of sources including for example, one or more network servers 11-60, one or more local source user devices 11-20*, one or more sensor integrated devices 11-40, and/or one or more third parties 11-6. In some cases, such source user log entries 11-12 may be in the form of, for example, social networking entries such as blog entries (e.g., microblog entries), status reports, and so forth. After receiving the one or more source user log entries 11-12 indicating the one or more reported aspects associated with the one or more source user 11-2*, the template 11-16 may be developed by at least identifying from the one or more reported aspects one or more relevant reported aspects that are deemed to be relevant to achieving the one or more target outcomes. Once the relevant reported aspects have been identified, the template 11-16 may be developed (e.g., created) by at least including into the template 11-16 one or more emulatable aspects that correspond to the one or more relevant reported aspects. In some cases, the development of the template 11-16 may further include defining in the template 11-16 the relationships (e.g., temporal or specific time relationships) between a plurality of emulatable aspects that may be included in the template 11-16.

After developing the template 11-16, the template 11-16 may be provided to at least one end user 11-4, to one or more network servers 11-60, to one or more third parties 11-6, or to one or more source users 11-2* via one or more communication networks 11-50. In embodiments in which the computing device 11-10 is a local client device such as local end user device 11-30* or a local source user device 11-20*, the template 11-16 may be presented via a user interface 11-120.

In alternative implementations, however, the template 11-16 may not be developed at the computing device 11-10, but instead, may be provided to the computing device 11-10 from a remote network site (e.g., a local source user device 11-20*, a network server 11-60, a local end user device 11-30*, and so forth) through, for example, one or more communication networks 11-50.

In various implementations, after developing or being provided with a template 11-16, the computing device 11-10 may be designed to monitor the progress of, for example, a plurality of end users 11-4*in compliantly executing the template 11-16 in order to achieve the one or more target outcomes associated with the template 11-16. In particular, such monitoring may be performed in order to determine any deviation by the end users 11-4* from a compliant execution of the template 11-16.

In order to monitor the progress of the end users 11-4* in compliantly executing the template 11-16, the computing device 11-10 may be designed to receive one or more end user log entries 11-14 (e.g., in the form of, for example, microblogs, status reports, journal entries, sensor entries, and so forth) associated with the end users 11-4* from one or more sources (e.g., local end user devices 11-30*, one or more sensor integrated devices 11-40, one or more third parties 11-6 such as other end users 11-4* and/or one or more network servers 11-60). The end user log entries 11-14 to be received may indicate a plurality of reported aspects of a plurality of end users 11-4* when the end users 11-4* are, for example, executing the template 11-16. Note that in embodiments in which the computing device 11-10 is an end user device (e.g., local end user device 11-30), one or more of the end user log entries 11-14 may be received directly from an end user 11-4* via the user interface 11-120.

In order to determine deviation from the compliant execution of the template 11-16 by the plurality of end users 11-4*, the reported aspects indicated by the received end user log entries 11-14 may be compared to the one or more emulatable aspects of the template 11-16. By making the comparison, a determination may be made as to whether one or more deviations from the one or more emulatable aspects included in the template 11-16 may have occurred. By at least determining that one or more deviations from the one or more emulatable aspects of the template 11-16 have occurred, a determination may be made that one or more deviations from the compliant emulation of the template 11-16 may have also occurred.

In any event, after determining or detecting deviation from the compliant execution of the template 11-16 by a plurality of end users 11-4*, the computing device 11-10 may be designed to modify the template 11-16 resulting in a modified template 11-18. The template 11-16 may be modified in a number of different ways in various alternative implementations. For example, in some implementations, the template 11-16 may be modified by modifying at least one of one or more emulatable aspects included in the template 11-16. In some instances, the modification of at least one of the one or more emulatable aspects may involve revising at least one of the one or more emulatable aspects, replacing at least one of the one or more emulatable aspects with one or more replacement or substitute emulatable aspects, or deleting at least one of the one or more emulatable aspects. In some implementations, a template 11-16 may be modified by adding one or more additional emulatable aspects. In implementations where a template 11-16 includes multiple emulatable aspects, the template 11-16 may be modified by modifying the one or more relationships (e.g., temporal or specific time relationships) between the plurality of emulatable aspects included in the template 11-16. Other ways of modifying a template 11-16 may also be employed in various alternative implementations.

In some implementations, the template 11-16 may be modified (e.g., by substituting or modifying existing emulatable aspects, or by adding additional emulatable aspects) in order to include at least one plausible emulatable aspect that was successfully emulated by at least a portion of a plurality of end users 11-4* who were determined to have deviated from the compliant execution of the template 11-16. In the same or different implementations, the template 11-16 may be modified in order to include at least one emulatable aspect that was developed by processing reports aspects (e.g., as indicated by end user log entries 11-14) of end users 11-4* who were determined to have deviated from the compliant execution of the template 11-16. These various approaches for modifying a template 11-16 as well as other approaches for modifying the template 11-16 will be discussed in greater detail herein. In some implementations, the template 11-16 may be modified to include one or more emulatable aspects belonging to a wide variety of emulatable aspect types (e.g., emulatable behaviors such as emulatable user activities, user attitudes, and user conduct, emulatable user beliefs, emulatable user states, and so forth).

As a result of modifying the template 11-16, a modified template 11-18 may be generated by the computing device 11-10. In some cases, the modified template 11-18 may be presented to, for example, at least one of the end users 11-4*, one or more network servers 11-60, and/or one or more third parties 11-6 via the one or more communication networks 11-50 and/or via the user interface 11-120.

In various embodiments, the computing device 11-10, as previously indicated, may be a server (e.g., one of the one or more network servers 11-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 11-10 is a source user device (e.g., local source user device 11-20*) or an end user device (e.g., local end user device 11-30*) rather than a network server 11-60, the computing device 11-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 11-100 of FIGS. 11-1a and 1′-1b, the one or more sensor integrated devices 11-40 of the exemplary environment 11-100 of FIGS. 11-1a and 11-1b may directly communicate with the one or more communication networks 11-50 in various embodiments. Alternatively, the one or more sensor integrated devices 11-40 may indirectly communicate with the one or more communication networks 11-50 via the one or more local source user devices 11-20* or via the one or more local end user devices 11-30*(e.g., via, for example, personal area network or PAN). In various embodiments, a sensor integrated device 11-40 may be a variety of functional devices that may comprise of one or more sensors 11-140 and that may be operated or used by a source user 11-2* or by an end user 11-4*. 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 11-140, which may also be included in the one or more local source user devices 11-20*, the local end user devices 11-30*, and/or the computing device 11-10, may include any type of sensors 11-140 that can sense one or more aspects of a source user 11-2* or an end user 11-4*. Examples of such sensors 11-140 include, for example, sensors 11-140 that can sense various physical characteristics of a source user 11-2* or an end user 11-4*(e.g., heart rate sensor or blood pressure sensor), sensors 11-140 that can sense activities of a source user 11-2* or an end user 11-4*(e.g., a pedometer, an accelerometer, and so forth), sensors 11-140 that can sense environment conditions (e.g., air quality sensors), sensors 11-140 that can sense the location of a source user 11-2* or an end user 11-4* (e.g., global positioning system or GPS), sensors 11-140 that can provide physiological data that may be processed in order to determine inferred mental states of source or end users 11-2* or 11-4*, and so forth.

Each of the one or more local source user devices 11-20* and the local end user devices 11-30*(as well as the computing device 11-10 in embodiments in which the computing device 11-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 11-20* and/or the local end user devices 11-30*(as well as the computing device 11-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 11-20* and/or local end user devices 11-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 11-10 as illustrated in FIG. 11-1b may include one or more modules, sub-modules, and various other components. As shown, the computing device 11-10 may include at least a deviation determining module 11-102 (which may further include one or more sub-modules as illustrated in FIG. 11-2a) and a template modifying module 11-104 (which may also include one or more sub-modules as illustrated in FIG. 11-2b). The deviation determining module 11-102 may be particular configured to, among other things, determine whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more target outcomes when one or more emulatable aspects included in the template 11-16 are emulated by the plurality of end users 11-4*, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users 11-2* that were deemed to have been relevant to achieving the one or more target outcomes. In contrast, the template modifying module 11-104 may be particularly configured to, among other things, modify the template 11-16 based, at least in part, on determining that the plurality of end users 11-4* deviated from compliantly executing the template 11-16.

In various implementations, the computing device 11-10 may further include a template developing module 11-103 and a memory 11-116. The template developing module 11-103 may be particularly configured to develop one or more templates 11-16 by at least initially identifying or determining one or more relevant reported aspects of one or more source user 11-2* that have been determined to be relevant for achieving one or more target outcomes. After identifying one or more relevant reported aspects, the template developing module 11-103 may be particularly configured to develop (e.g., create) a template 11-16 by at least including into the template 11-16 one or more emulatable aspects that correspond to the one or more identified relevant reported aspects. The determination of relevancy of a reported aspect associated with one of the source users 11-2* may be based on a number of factors including, for example, whether it is a type of reported aspect that is of interest to end users 11-4* or source users 11-2* and whether the reported aspect occurred proximate to the occurrence of the one or more target outcomes as achieved by the source user 11-2*.

The memory 11-116, in various implementations, may store a plurality of templates 11-14 including a template 11-16 and/or a modified template 11-18 that is a modified version of template 11-16. In some implementations, the memory 11-116 may store one or more applications 11-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 11-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 11-10 may also include, in various implementations, a network interface 11-118 (e.g., a network interface card or NIC), a user interface 11-120 (e.g., a display monitor, a touchscreen, a microphone, a speaker, a mouse, and so forth), and/or one or more sensors 11-140 that are designed to measure or sense one or more user aspects. Examples of sensors 11-140 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 sensors 11-140 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 11-10 may depend on, for example, whether the computing device 11-10 is a server, an end user device, or a source user device. For example, if the computing device 11-10 is a server, then the computing device 11-10 may not include a user interface 11-120.

FIG. 11-2 a illustrates particular implementations of the deviation determining module 11-102 of FIG. 11-1b. The deviation determining module 11-102 in various implementations may include, among other things, a reported aspect data receiving module 11-202 particularly configured for, among other things, receiving data indicating reported aspects of end users 11-4*, a comparing module 11-218 particularly configured to compare reported aspects of end users 11-4* with one or more emulatable aspects included in a template 11-16, and/or an emulatable aspect identifying module 11-220 particularly configured to, among other things, identify which of the one or more emulatable aspects included in template 11-16 were not emulated at all or only partially emulated by one or more of the end users 11-4* based on the comparison of the reported aspects with the one or more emulatable aspects included in the template 11-16.

The deviation determining module 11-102 may also include, in various implementations, an end user identifying module 11-222 particularly configured to, among other things, identify which of the plurality of end users 11-4* did not emulate at all or only partially emulated the one or more emulatable aspects included in the template 11-16 that were identified by the emulatable aspect identifying module 11-220 as being not emulated at all or were only partially emulated by one or more of the end users 11-4*, a reported aspect identifying module 11-224 particularly configured to, among other things, identify which of the reported aspects of the plurality of end users 11-4* represent one or more replacement aspects for one or more emulatable aspects included in the template 11-16, and/or a particular order determining module 11-226 that is specifically designed to, among other things, determine whether the plurality of end users 11-4* did not emulate a plurality of emulatable aspects included in the template 11-16 in a particular order as defined by the template 11-16.

In various implementations, the reported aspect data receiving module 11-202 may further include one or more sub-modules including for example, a network receiving module 11-204 (designed to, among other things, receive data indicating at least one reported aspect associated with at least one end user 11-4* from one or more communication networks 11-50), a user interface receiving module 11-206 (designed to, among other things, receive at least one reported aspect associated with at least one end user 11-4* via a user interface 11-120), and/or a log entry receiving module 11-208 (designed to, among other things, receive data indicating at least one reported aspect associated with at least one end user 11-4* via one or more end user log entries 11-14).

The log entry receiving module 11-208, in various implementations, may further include a social networking entry receiving module 11-210 (which may further include a blog entry receiving module 11-212 and/or a status report receiving module 11-214) and/or a journal entry receiving module 11-216. The social networking entry receiving module 11-210 may be configured to receive the data indicating the at least one reported aspect associated with the at least one end user 11-4* via one or more social networking entries. The blog entry receiving module 11-212 may be configured to receive the data indicating the at least one reported aspect associated with the at least one end user 11-4* via one or more blog entries. The status report receiving module 11-214 may be configured to receive the data indicating the at least one reported aspect associated with the at least one end user 11-4* via one or more social networking status reports. The journal entry receiving module 11-216, in contrast, may be configured to receive the data indicating the at least one reported aspect associated with the at least one end user 11-4* via one or more journal entries.

FIG. 11-2 b illustrates particular implementations of the template modifying module 11-104 of the computing device 11-10 of FIG. 11-1b. As illustrated, the template modifying module 11-104 may include, in various implementations, an emulatable aspect modifying module 11-230 (which may further include an emulatable aspect revising module 11-232, an emulatable aspect replacing module 11-234, and/or an emulatable aspect deleting module 11-236). As further illustrated, in some implementations the template modifying module 11-104 may also include an emulatable aspect adding module 11-238 (which may further include a relationship defining module 11-240), a relationship modifying module 11-242, and/or a reported aspect analyzing module 11-243. In some implementations the reported aspect analyzing module 11-243 may further include a mean value emulatable aspect developing module 11-246 and/or an average value emulatable aspect developing module 11-248. These modules and sub-module of the template modifying module 11-104, as well as the modules and sub-modules of the deviation determining module 11-102 of FIG. 11-2a, will be discussed in greater detail below with respect to the processes and operation to be described herein.

Referring back to the computing device 11-10 of FIG. 11-1b, the various modules (e.g., the deviation determining module 11-102, the template modifying module 11-104, and so forth) along with their sub-modules included in the computing device 11-10 may be implemented using hardware, software, firmware, or any combination thereof. For example, in some implementations, the deviation determining module 11-102 and/or the template modifying module 11-104 may be implemented with a processor 11-802 (e.g., microprocessor, controller, and so forth) executing computer readable instructions 11-804 (e.g., computer program product) stored in a storage medium 11-806 (e.g., volatile or non-volatile memory) such as a signal-bearing medium as depicted in the computing device 11-10 of FIG. 11-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 11-10 of FIG. 11-1b and its components will now be provided with respect to the processes and operations to be described herein. FIG. 11-3 illustrates an operational flow 11-300 representing example operations directed to, among other things, modification of a template 11-16 based, at least in part, on determining whether a plurality of end users 11-4* deviated from compliantly executing the template 11-16 that is designed to facilitate the plurality of end users 11-4* to achieve one or more target outcomes when one or more emulatable aspects included in the template 11-16 or emulated. In various implementations, the plurality of end users 11-4* may have still achieved the one or more target outcomes associated with the template 11-16 even though the end users 11-4* may have deviated from the compliant execution of the template 11-16.

In FIG. 11-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 11-100 described above as illustrated in FIGS. 11-1a and 11-1b, and/or with respect to other examples (e.g., as provided in FIGS. 11-2a and 11-2b) 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. 11-1a, 11-1b, 11-2a, and 11-2b. 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. 11-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 11-300 may move to a deviation determining operation 11-302 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. For instance, and as an illustration, the deviation determining module 11-102 of the computing device 11-10 of FIG. 11-1b determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more target outcomes (e.g., health or medical outcomes, user state outcomes, employment or leisure outcomes, and so forth) when one or more emulatable aspects included in the template 11-16 are emulated by the plurality of end users 11-4*, the one or more emulatable aspects being based on one or more relevant reported aspects (e.g., as indicated by source user log entries 11-12) of one or more source users 11-2* that were deemed to have been relevant to achieving the one or more target outcomes.

In addition to the deviation determining operation 11-302, operational flow 11-300 may also include a template modifying operation 11-304 for modifying the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 based, at least in part, on determining that the plurality of end users 11-4* deviated from compliantly executing the template 11-16. In various implementations, end user data such as data obtained through end user log entries 11-14 that indicate reported aspects of the plurality of end users 11-4* may be processed in order to facilitate in the modification of the template 11-16. Such processing may be implemented in order to, for example, determine the type of emulatable aspects that may be included in the modified template 11-18. In various implementations, the deviation determining operation 11-302 and the template modifying operation 11-304 of FIG. 11-3 may be executed in a number of different ways.

For example, FIGS. 11-4a, 11-4b, and 11-4c illustrate various ways that the deviation determining operation 11-302 of FIG. 11-3 may be executed in various alternative implementations. For instance, the deviation from the compliant execution of the template 11-16 by the plurality of end users 11-4* to be determined through the deviation determining operation 11-302 may be accomplished in a variety of different ways. In some implementations, for example, the deviation determining operation 11-302 of FIG. 11-3 may include an operation 11-402 for determining whether the plurality of end users deviated from compliantly executing the template by at least receiving data indicating reported aspects of the plurality of end users as depicted in FIG. 11-4a. For instance, the deviation determining module 11-102 including the reported aspect data receiving module 11-202 (see FIG. 11-2a) of the computing device 11-10 determining whether the plurality of end users 11-4* deviated from compliantly executing the template 11-16 when the reported aspect data receiving module 11-202 at least receives data indicating reported aspects (e.g., dietary activities, exercise activities, mental states, medical treatment, and so forth) of the plurality of end users 11-4*. In some implementations, the reported aspects of the plurality of end users 11-4* may be the reported aspects of the end users 11-4* when the end users 11-4* were executing the template 11-16.

Operation 11-402 for receiving the data that indicates the reported aspects of the plurality of end users 11-4* may be executed in a number of ways. For example, in some implementations, operation 11-402 may include an operation 11-403 for receiving the data indicating the reported aspects of the plurality of end users including receiving data indicating at least one of the reported aspects from one or more communication networks as depicted in FIG. 11-4a. For instance, the reported aspect data receiving module 11-202 including the network receiving module 11-204 of the computing device 11-10 receiving the data indicating the reported aspects of the plurality of end users 11-4* including receiving by the network receiving module 11-204 of data (e.g., end user log entries 11-14) that indicates at least one of the reported aspects from one or more communication networks 11-50.

In the same or different implementations, operation 11-402 may include an operation 11-404 for receiving the data indicating the reported aspects of the plurality of end users including receiving data indicating at least one of the reported aspects via a user interface as depicted in FIG. 11-4a. For instance, the reported aspect data receiving module 11-202 including the user interface receiving module 11-206 of the computing device 11-10 when the computing device 11-10 is an end user device (e.g., local end user device 11-30*) receiving the data indicating the reported aspects of the plurality of end users 11-4* including receiving by the user interface receiving module 11-206 of data indicating at least one of the reported aspects via a user interface 11-120 (e.g., a keyboard or keypad, a microphone, a mouse, a touchscreen, and so forth).

In the same or different implementations, operation 11-402 may include an operation 11-405 for receiving the data indicating the reported aspects of the plurality of end users including receiving data indicating at least one of the reported aspects via one or more end user log entries as depicted in FIG. 11-4a. For instance, the reported aspect data receiving module 11-202 including the log entry receiving module 11-208 of the computing device 11-10 receiving the data indicating the reported aspects of the plurality of end users 11-4* including receiving by the log entry receiving module 11-208 of data indicating at least one of the reported aspects via one or more end user log entries 11-14.

Operation 11-405, in turn, may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 11-405 may include an operation 11-406 for receiving the data indicating at least one of the reported aspects via one or more social networking entries as depicted in FIG. 11-4a. For instance, the social networking entry receiving module 11-210 of the computing device 11-10 receiving the data indicating at least one of the reported aspects via one or more social networking entries.

In some implementations, operation 11-406 may further include an operation 11-407 for receiving the data indicating at least one of the reported aspects via one or more blog entries as depicted in FIG. 11-4a. For instance, the blog entry receiving module 11-212 of the computing device 11-10 receiving the data indicating at least one of the reported aspects via one or more blog entries (e.g., microblog entries).

In the same or different implementations, operation 11-406 may include an operation 11-408 for receiving the data indicating at least one of the reported aspects via one or more status reports as depicted in FIG. 11-4a. For instance, the status report receiving module 11-114 of the computing device 11-10 receiving the data indicating at least one of the reported aspects via one or more (social networking) status reports.

In some implementations, operation 11-405 for receiving the data indicating at least one of the reported aspects via one or more end user log entries may include an operation 11-409 for receiving the data indicating at least one of the reported aspects via one or more journal entries as depicted in FIG. 11-4a. For instance, the journal entry receiving module 11-216 of the computing device 11-10 receiving the one or more end user log entries 11-14 including the journal entry receiving module 11-216 receiving the data indicating at least one of the reported aspects via one or more journal entries.

In the same or different implementations, operation 11-405 may include an operation 11-410 for receiving the one or more end user log entries including the data indicating at least one of the reported aspects from one or more of the end users as depicted in FIG. 11-4a. For instance, the log entry receiving module 11-208 of the computing device 11-10 receiving (e.g., receiving via one or more communication networks 11-50 the one or more end user log entries 11-14 including the data indicating at least one of the reported aspects from one or more of the end users 11-4*.

In the same or different implementations, operation 11-405 may include an operation 11-411 for receiving the one or more end user log entries including the data indicating at least one of the reported aspects from one or more sensors as depicted in FIG. 11-4a. For instance, the log entry receiving module 11-208 of the computing device 11-10 receiving the one or more end user log entries 11-14 including the data indicating at least one of the reported aspects from one or more sensors 11-140.

In the same or different implementations, operation 11-405 may include an operation 11-412 for receiving the one or more end user log entries including the data indicating at least one of the reported aspects from one or more sensor integrated devices as depicted in FIG. 11-4a. For instance, the log entry receiving module 11-208 of the computing device 11-10 receiving the one or more end user log entries 11-14 including the data indicating at least one of the reported aspects from one or more sensor integrated devices 11-40 (e.g., an automobile, a treadmill, a household appliance, and so forth).

In various implementations, the operation 11-402 for determining whether the plurality of end users 11-4* deviated from compliantly executing the template 11-16 by at least receiving data indicating reported aspects of the plurality of end users may include an operation 11-413 for determining whether the plurality of end users deviated from compliantly executing the template by at least comparing the reported aspects with the one or more emulatable aspects included in the template as depicted in FIG. 11-4b. For instance, the deviation determining module 11-102 including the comparing module 11-218 determining whether the plurality of end users 11-4* deviated from compliantly executing the template 11-16 when the comparing module 11-218 at least compares the reported aspects with the one or more emulatable aspects included in the template 11-16.

As further illustrated in FIG. 11-4b, operation 11-413 may include one or more additional operations in various alternative implementations. For example, in some implementations, operation 11-413 may include an operation 11-414 for identifying which of the one or more emulatable aspects included in the template were not emulated at all by one or more of the end users based on the comparison of the reported aspects with the one or more emulatable aspects as depicted in FIG. 11-4b. For instance, the emulatable aspect identifying module 11-220 of the computing device 11-10 identifying (e.g., determining, or finding) which of the one or more emulatable aspects included in the template 11-16 were not emulated at all by one or more of the end users 11-4* based on the comparison of the reported aspects with the one or more emulatable aspects. In some cases, by making such identification, a determination may be made as to which of the one or more emulatable aspects included in the template 11-16 may need to be modified. Note that the phrase “at all” as used above in reference to the emulatable aspects in the template 11-16 that were not emulated at all indicate that these emulatable aspects were not even partially emulated by one or more end users 11-4* but were, for example, completely ignored or disregarded.

In some cases, operation 11-414 may further include an operation 11-415 for identifying which of the plurality of end users did not emulate at all the one or more emulatable aspects included in the template that were identified as being not emulated at all by one or more of the end users as depicted in FIG. 11-4b. For instance, the end user identifying module 11-222 of the computing device 11-10 identifying which of the plurality of end users 11-4* did not emulate at all those emulatable aspects included in the template 11-16 that were identified as being not emulated at all by one or more of the end users 11-4*. In some implementations, by making such identification, a determination may be made as to whether the template 11-16 should be modified. For example, in some cases, template 11-16 may be modified only if a majority of end users 11-4* or at least a significant portion of the end user 11-4* were identified as not emulating at all one, some, or all of the one or more emulatable aspects of the template 11-16.

In various implementations, operation 11-413 may include an operation 11-416 for identifying which of the one or more emulatable aspects included in template were only partially emulated by one or more of the end users based on the comparison of the reported aspects with the one or more emulatable aspects as depicted in FIG. 11-4b. For instance, the emulatable aspect identifying module 11-220 of the computing device 11-10 identifying which of the one or more emulatable aspects included in template 11-16 were only partially emulated by one or more of the end users 11-4* based on the comparison of the reported aspects with the one or more emulatable aspects. In some cases, by making such an identification, a determination may be made as to which of the one or more emulatable aspects included in the template 11-16 may need to be modified.

In some implementations, operation 11-416 may further include an operation 11-417 for identifying which of the plurality of end users only partially emulated the one or more emulatable aspects included in the template that were identified as being only partially emulated by one or more of the end users as depicted in FIG. 11-4b. For instance, the end user identifying module 11-222 of the computing device 11-10 identifying which of the plurality of end users 11-4* only partially emulated those emulatable aspects included in the template 11-16 that were identified as being only partially emulated by one or more of the end users 11-4*. In some implementations, by making such identification, a determination may be made as to whether the template 11-16 should be modified. For example, in some cases template 11-16 may be modified only if a majority of end users 11-4* or at least a significant portion of the plurality of end users 11-4* were identified as only partially emulating one, some, or all of the one or more emulatable aspects of the template 11-16.

In some implementations, operation 11-413 may include an operation 11-418 for identifying which of the reported aspects of the plurality of end users represent one or more replacement aspects for the one or more emulatable aspects included in the template as depicted in FIG. 11-4b. For instance, the reported aspect identifying module 11-224 of the computing device 11-10 identifying which of the reported aspects of the plurality of end users 11-4* represent one or more replacement aspects for the one or more emulatable aspects included in the template 11-16 that may be replaced or revised when the template 11-16 is being, for example, modified. The identification of one or more replacement aspects from the reported aspects of the plurality of end users 11-4* may be based on a number of factors. For example, in some implementations, reported aspects that are deviations from the one or more emulatable aspects included in the template 11-16 and that are most commonly executed by the end users 11-4* may be identified as replacement aspects. Suppose, for example, template 11-16 included an emulatable aspect that required end users 11-4* to go jogging for 30 minutes on the fourth day. However, if most of the non-compliant end users 11-4* went swimming 20 minutes on the fourth day rather than jogging, than swimming for 20 minutes may be identified as a replacement aspect.

In same or different implementations, operation 11-413 may include an operation 11-419 for determining whether the plurality of end users deviated from compliantly executing the template by at least determining whether the plurality of end users did not emulate a plurality of emulatable aspects included in the template in a particular order as defined by the template as depicted in FIG. 11-4b. For instance, the deviation determining module 11-102 including the particular order determining module 11-226 of the computing device 11-10 determining whether the plurality of end users 11-4* deviated from compliantly executing the template 11-16 when the particular order determining module 11-226 at least determines whether the plurality of end users 11-4* did not emulate a plurality of emulatable aspects included in the template 11-16 in a particular order as defined by the template 11-16. In other words, if the template 11-16 includes a plurality of emulatable aspects, and the template 11-16 defines the temporal or specific time order in which the emulatable aspects are to be emulated, than an end user 11-4* may not have compliantly executed the template 11-16 if the end user 11-4* emulates at least some of the emulatable aspects in an incorrect order (e.g., incorrect sequence).

In various implementations, operation 11-419 may further include an operation 11-420 for determining whether the plurality of end users deviated from compliantly executing the template by at least determining whether the plurality of end users did not emulate a plurality of emulatable aspects included in the template in a particular temporal order as defined by the template as depicted in FIG. 11-4b. For instance, the deviation determining module 11-102 including the particular order determining module 11-226 of the computing device 11-10 determining whether the plurality of end users 11-4* deviated from compliantly executing the template 11-16 when the particular order determining module 11-226 at least determines whether the plurality of end users 11-4* did not emulate a plurality of emulatable aspects included in the template 11-16 in a particular temporal order as defined by the template 11-16.

In some implementations, operation 11-419 may include an operation 11-421 for determining whether the plurality of end users deviated from compliantly executing the template by at least determining whether the plurality of end users did not emulate a plurality of emulatable aspects included in the template in a specific time order as defined by the template as depicted in FIG. 11-4b. For instance, the deviation determining module 11-102 including the particular order determining module 11-226 of the computing device 11-10 determining whether the plurality of end users 11-4* deviated from compliantly executing the template 11-16 when the particular order determining module 11-226 at least determines whether the plurality of end users 11-4* did not emulate a plurality of emulatable aspects included in the template 11-16 in a specific time order as defined by the template 11-16.

Various types of templates 11-16 may be involved in the deviation determining operation 11-302 of FIG. 11-3. For example, in some implementations, the deviation determining operation 11-302 may include an operation 11-422 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 health or medical outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving 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 some implementations, the deviation determining operation 11-302 may include an operation 11-423 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 athletic or gaming outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving 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 some implementations, the deviation determining operation 11-302 may include an operation 11-424 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 occupational outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more occupational outcomes (e.g., be promoted, develop business network, complete a project, and so forth).

In some implementations, the deviation determining operation 11-302 may include an operation 11-425 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 social or leisure outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more social or leisure outcomes (e.g., develop more friendships, achieve certain social status, be invited to join a particular social club, and so forth).

In some implementations, the deviation determining operation 11-302 may include an operation 11-426 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 sexual intimacy outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more sexual intimacy outcomes (e.g., increase the frequency of sexual encounters).

In some implementations, the deviation determining operation 11-302 may include an operation 11-427 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 academic or intellectual outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving 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 some implementations, the deviation determining operation 11-302 may include an operation 11-428 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 spiritual or religious outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more spiritual or religious outcomes (e.g., achieve spiritual harmony, acceptance to a particular church or religion, and so forth).

In some implementations, the deviation determining operation 11-302 may include an operation 11-429 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 user state outcomes as depicted in FIG. 11-4c. For instance, the deviation determining module 11-102 of the computing device 11-10 determining whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving 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 back to FIG. 11-3, the template modifying operation 11-304 may be implemented in a number of different ways in various alternative implementations. For example, in some implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-530 for modifying the template by modifying at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 including the emulatable aspect modifying module 11-230 of the computing device 11-10 modifying the template 11-16 when the emulatable aspect modifying module 11-230 modifies at least one of the one or more emulatable aspects included in the template 11-16.

There are a number of ways in which an emulatable aspect that may be included in a template 11-16 may be modified. For example, in some implementations, operation 11-530 may include an operation 11-531 for modifying the at least one of the one or more emulatable aspects included in the template by revising the at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the emulatable aspect modifying module 11-230 including the emulatable aspect revising module 11-232 modifying the at least one of the one or more emulatable aspects included in the template 11-16 when the emulatable aspect revising module 11-232 revises the at least one of the one or more emulatable aspects included in the template 11-16.

In the same or different implementations, operation 11-530 may include an operation 11-532 for modifying the at least one of the one or more emulatable aspects included in the template by replacing the at least one of the one or more emulatable aspects included in the template with at least one replacement emulatable aspect as depicted in FIG. 11-5a. For instance, the emulatable aspect modifying module 11-230 including the emulatable aspect replacing module 11-234 modifying the at least one of the one or more emulatable aspects included in the template 11-16 when the emulatable aspect replacing module 11-234 replaces the at least one of the one or more emulatable aspects included in the template 11-16 with at least one replacement emulatable aspect.

In the same or different implementations, operation 11-530 may include an operation 11-533 for modifying the at least one of the one or more emulatable aspects included in the template by deleting the at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the emulatable aspect modifying module 11-230 including the emulatable aspect deleting module 11-236 modifying the at least one of the one or more emulatable aspects included in the template 11-16 when the emulatable aspect deleting module 11-236 deletes the at least one of the one or more emulatable aspects included in the template 11-16. Note that a deletion of an emulatable aspect may be possible when, for example, it is determined that end users 11-4* when executing the template 11-16 may have skipped emulating a particular emulatable aspect included in the template 11-16 without compromising the outcome (e.g., achieving the target outcome).

In various implementations, the template modifying operation 11-304 may include an operation 11-534 for modifying the template by adding to the template at least one additional emulatable aspect as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 including the emulatable aspect adding module 11-238 of the computing device 11-10 modifying the template 11-16 when the emulatable aspect adding module 11-238 adds to the template 11-16 at least one additional emulatable aspect. This may be possible, for example, when end users 11-4* deviate from the compliant execution of the template 11-16 that results in the need for an additional emulatable aspect in order to achieve the one or more target outcomes. For example, if end users 11-4* deviate from the compliant execution of the template 11-16 by swimming for only 20 minutes rather than swimming for 40 minutes as required by the template 11-16, then the template 11-16 may be modified to include an additional emulatable aspect for another 20 minute swim.

In some implementations, operation 11-534 may further include an operation 11-535 for adding to the template the at least one additional emulatable aspect by defining in the template one or more relationships between the at least one additional emulatable aspect and the one or more emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the emulatable aspect adding module 11-238 including the relationship defining module 11-240 of the computing device 11-10 adding to the template 11-16 the at least one additional emulatable aspect including defining by the relationship defining module 11-240 in the template 11-16 one or more relationships (e.g., temporal or specific time relationships) between the at least one additional emulatable aspect and the one or more emulatable aspects included in the template 11-16.

In the same or different implementations, the template modifying operation 11-304 may include an operation 11-536 for modifying the template by modifying one or more relationships between a plurality of emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 including the relationship modifying module 11-242 modifying the template 11-16 including modifying by the relationship modifying module 11-242 one or more relationships between a plurality of emulatable aspects included in the template 11-16.

In various implementations, operation 11-536 may further include an operation 11-537 for modifying the template by modifying one or more temporal relationships between the plurality of emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 including the relationship modifying module 11-242 modifying the template 11-16 including modifying by the relationship modifying module 11-242 one or more temporal relationships between a plurality of emulatable aspects included in the template 11-16.

In some implementations, operation 11-536 may include an operation 11-538 for modifying the template by modifying one or more specific time relationships between the plurality of emulatable aspects included in the template as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 including the relationship modifying module 11-242 modifying the template 11-16 including modifying by the relationship modifying module 11-242 one or more specific time relationships between a plurality of emulatable aspects included in the template 11-16.

In the same or different implementations, the template modifying operation 11-304 may include an operation 11-539 for modifying the template to include at least one plausible emulatable aspect that has been determined to have been successfully emulated by at least a portion of the plurality of end users as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include at least one plausible emulatable aspect (e.g., a plausible modified emulatable aspect, a plausible replacement emulatable aspect, a plausible additional emulatable aspect, and so forth) that has been determined to have been successfully emulated by at least a portion of the plurality of end users 11-4*.

In some implementations, operation 11-539 for presenting one or more recommendations may include an operation 11-540 for modifying the template to include at least one plausible emulatable aspect that has been determined to have been successfully emulated by a majority of the plurality of end users as depicted in FIG. 11-5a. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include at least one plausible emulatable aspect (e.g., a plausible modified emulatable aspect, a plausible replacement emulatable aspect, a plausible additional emulatable aspect, and so forth) that has been determined to have been successfully emulated by a majority of the plurality of end users 11-4*.

In various implementations, the one or more actions executed in the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-541 for modifying the template to include at least one emulatable aspect that was provided by at least analyzing a plurality of reported aspects of the plurality of end users, the plurality of reported aspects deviating from at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 including the reported aspect analyzing module 11-243 modifying the template 11-16 to include at least one emulatable aspect that was provided by the reported aspect analyzing module 11-243 at least analyzing a plurality of reported aspects (e.g., as acquired through end user log entries 11-14) of the plurality of end users 11-4*, the plurality of reported aspects deviating from at least one of the one or more emulatable aspects included in the template 11-16.

Operation 11-541 may, in turn, include an operation 11-542 for modifying the template to include at least one mean value emulatable aspect that was at least provided by developing a mean value for a plurality of reported aspects of the plurality of end users, the reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 including the mean value emulatable aspect developing module 11-246 of the computing device 11-10 modifying the template 11-16 to include at least one mean value emulatable aspect that was at least provided by the mean value emulatable aspect developing module 11-246 by developing a mean value for a plurality of reported aspects of the plurality of end users 11-4*, the reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template 11-16. For example, suppose the template 11-16 included an emulatable aspect that required the end users 11-4* to study a particular reference book for one hour. However, if the end users 11-4* in executing the template 11-16 reported that they studied for less than or more than one hour as required by the template 11-16, then the mean value emulatable aspect, in this case, would be the mean reported aspects of the end users 11-4*.

In some implementations, operation 11-541 may include an operation 11-543 for modifying the template to include at least one average value emulatable aspect that was at least provided by developing an average value for a plurality of reported aspects of the plurality of end users, the plurality of reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 including the average value emulatable aspect developing module 11-248 of the computing device 11-10 modifying the template 11-16 to include at least one average value emulatable aspect that was at least provided by the average value emulatable aspect developing module 11-248 by developing an average value for a plurality of reported aspects of the plurality of end users 11-4*, the plurality of reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template 11-16.

In some implementations, operation 11-541 may include an operation 11-544 for modifying the template to include at least one emulatable aspect that was provided by determining from a plurality of reported aspects of the plurality of end users an end user aspect that was reported more than once, the plurality of reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 including the reported aspect analyzing module 11-243 configured to modify the template 11-16 to include at least one emulatable aspect that was provided by the reported aspect analyzing module 11-243 when the reported aspect analyzing module 11-243 determines from a plurality of reported aspects of the plurality of end users an end user aspect (e.g., jogging for 40 minutes instead of one hour as required by the template 11-16) that was reported more than once, the plurality of reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template 11-16. In other words, looking at the reported aspects of end users 11-4* and look for deviations that occurred repeatedly. Such deviation may then be used in order to modify the template by, for example, modifying, substituting, or adding an emulatable aspect into the template 11-16 that corresponds to the repeated deviations.

In some implementations, operation 11-544 may further include an operation 11-545 for modifying the template to include at least one emulatable aspect that was provided by determining a reported aspect that was most commonly reported aspect from a plurality of reported aspects of the plurality of end users, the plurality of reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 including the reported aspect analyzing module 11-243 configured to modify the template 11-16 to include at least one emulatable aspect that was provided by the reported aspect analyzing module 11-243 when the reported aspect analyzing module 11-243 determines a reported aspect that was most commonly reported aspect from a plurality of reported aspects (e.g., as indicated by end user log entries 11-14) of the plurality of end users 11-4*, the plurality of reported aspects corresponding to and deviating from at least one of the one or more emulatable aspects included in the template. In other words, to modify the template by including into the template 11-16 (e.g., by substitution, modification, or addition), an emulatable aspect corresponding to the most commonly occurring deviation.

In the same or different implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-546 for modifying the template in response to determining that one or more of the end users did not emulate at all at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 in response to determining that one or more of the end users 11-4* did not emulate at all at least one of the one or more emulatable aspects included in the template 11-16.

In the same or different implementations, the template modifying operation 11-304 may include an operation 11-547 for modifying the template in response to determining that one or more of the end users only partially emulated at least one of the one or more emulatable aspects included in the template as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 in response to determining that one or more of the end users 11-4* only partially emulated at least one of the one or more emulatable aspects included in the template 11-16.

In the same or different implementations, the template modifying operation 11-304 may include an operation 11-548 for modifying the template to include at least one emulatable aspect that relate to at least one emulatable behavior as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one emulatable behavior (e.g., dietary behavior, social behavior, and so forth).

In some implementations, operation 11-548 may include an operation 11-549 for modifying the template to include at least one emulatable aspect that relate to at least one emulatable user activity as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one emulatable user activity (e.g., walking, resting, riding a bicycle, attending church, and so forth).

In the same or different implementations, operation 11-548 may include an operation 11-550 for modifying the template to include at least one emulatable aspect that relate to at least one emulatable user attitude as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one emulatable user attitude (e.g., distaste, positive or negative attitude, and so forth).

In the same or different implementations, operation 11-548 may include an operation 11-551 for modifying the template to include at least one emulatable aspect that relate to at least one emulatable user conduct as depicted in FIG. 11-5b. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one emulatable user conduct (e.g., treating subordinates as equals, being evasive, and so forth).

In some implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-552 for modifying the template to include at least one emulatable aspect that relate to at least one emulatable user belief as depicted in FIG. 11-5c. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one emulatable user belief (e.g., religious belief, spiritual belief, dietary belief, and so forth).

In the same or different implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-553 for modifying the template to include at least one emulatable aspect that relate to at least one emulatable user state as depicted in FIG. 11-5c. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one emulatable user state (e.g., subjective user states such as being happy, being alert, or being prepared, objective user states such as being married, being underweight, being employed, and so forth).

In the same or different implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-554 for modifying the template to include at least one emulatable aspect that relate to at least one user physical characteristic as depicted in FIG. 11-5c. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one user physical characteristic (e.g., low blood pressure, hair color, low body fat level, and so forth).

In the same or different implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-555 for modifying the template to include at least one emulatable aspect that relate to at least one user external event as depicted in FIG. 11-5c. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 to include (e.g., by revising, replacing, or adding) at least one emulatable aspect that relate to at least one user external event (e.g., local atmospheric conditions, drinking water quality, road traffic, and so forth).

In the same or different implementations, the template modifying operation 11-304 of FIG. 11-3 may include an operation 11-556 for modifying the template based, at least in part, on determining that the plurality of end users deviated from the compliant execution of the template, the plurality of end users determined to have achieved the one or more target outcomes even though the template was not compliantly executed by the plurality of end users as depicted in FIG. 11-5c. For instance, the template modifying module 11-104 of the computing device 11-10 modifying the template 11-16 based, at least in part, on determining that the plurality of end users 11-4*deviated from the compliant execution of the template 11-16, the plurality of end users 11-4* determined to have achieved the one or more target outcomes even though the template 11-16 was not compliantly executed by the plurality of end users 11-4*.

Referring to FIG. 11-6 illustrating another operational flow 11-600 in accordance with various embodiments. Operational flow 11-600 includes certain operations that mirror the operations included in the operational flow 11-300 of FIG. 11-3. These operations include a deviation determining operation 11-602 and a template modifying operation 11-604 that corresponds to and mirror the deviation determining operation 11-302 and the template modifying operation 11-304, respectively, of FIG. 11-3.

In addition, operational flow 11-600 includes a modified template presenting operation 11-606 for presenting the modified template as depicted in FIG. 11-6. For instance, the modified template presenting module 11-106 of the computing device 11-10 presenting the modified template 11-18 resulting from the template modifying operation 11-604.

In some implementations, the modified template presenting operation 11-606 of FIG. 11-6 may include an operation 11-758 for transmitting the modified template via one or more communication networks as depicted in FIG. 11-7. For instance, the network transmitting module 11-130 (see FIG. 11-1b) of the computing device 11-10 transmitting the modified template 11-18 via one or more communication networks 11-50.

In the same or different implementations, the modified template presenting operation 11-606 of FIG. 11-6 may include an operation 11-759 for presenting the modified template to at least one of the plurality of end users as depicted in FIG. 11-7. For instance, the modified template presenting module 11-106 of the computing device 11-10 presenting the modified template 11-18 to at least one of the plurality of end users 11-4*.

In the same or different implementations, the modified template presenting operation 11-606 of FIG. 11-6 may include an operation 11-760 for presenting the modified template to one or more third parties as depicted in FIG. 11-7. For instance, the modified template presenting module 11-106 of the computing device 11-10 presenting the modified template 11-18 to one or more third parties 11-6 (e.g., network servers 11-60, content providers, and so forth).

In the same or different implementations, the modified template presenting operation 11-606 of FIG. 11-6 may include an operation 11-761 for presenting the modified template to one or more other end users as depicted in FIG. 11-7. For instance, the modified template presenting module 11-106 of the computing device 11-10 presenting the modified template 11-18 to one or more other end users who may have yet to execute the template 11-16 or the modified template 11-18.

Turning now to FIG. 11-8, which is a high-level block diagram illustrating a particular implementation of the computing device 11-10 of FIG. 11-1b. As illustrated, the computing device 11-10 may include a processor 11-802 (e.g., microprocessor, controller, and so forth) coupled to storage medium 11-806 (e.g., volatile or non-volatile memory). The storage medium 11-806 may store computer readable instructions 11-804 (e.g., computer program product). The processor 11-802, in various implementations, may execute the computer readable instructions 11-804 in order to execute one or more operations described above and as illustrated in FIGS. 11-3, 11-4a, 11-4b, 11-4c, 11-5a, 11-5b, 11-5c, 11-6, and 11-7.

For example, the processor 11-802 may execute the computer readable instructions 11-804 in order to determine whether a plurality of end users 11-4* deviated from compliantly executing a template 11-16 designed to facilitate the plurality of end users 11-4* in achieving one or more target outcomes when one or more emulatable aspects included in the template 11-16 are emulated by the plurality of end users 11-4*, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users 11-2* that were deemed to have been relevant to achieving the one or more target outcomes; and/or to modify the template 11-16 based, at least in part, on determining that the plurality of end users 11-4* deviated from compliantly executing the template 11-16 as illustrated by the operational flow 11-300 of FIG. 11-3.

Claims

1. A computationally-implemented method, comprising: 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; anddeveloping 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.

2.-64. (canceled)

65. A computationally-implemented system, comprising: 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; andmeans 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.

66. The computationally-implemented system of claim 65, wherein said 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, comprises: means for acquiring the relevant reported aspects from a memory.

67. The computationally-implemented system of claim 65, wherein said 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, comprises: means for acquiring the relevant reported aspects via one or more communication networks.

68. The computationally-implemented system of claim 67, wherein said means for acquiring the relevant reported aspects via one or more communication networks, comprises: means 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.

69. The computationally-implemented system of claim 65, wherein said 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, comprises: means for providing the plurality of relevant reported aspects by at least identifying reported aspects that correspond to the one or more target outcomes.

70. The computationally-implemented system of claim 69, wherein said means for providing the plurality of relevant reported aspects by at least identifying reported aspects that correspond to the one or more target outcomes, comprises: means for identifying the source users based on the source users association with the reported aspects that corresponds to the one or more target outcomes.

71. The computationally-implemented system of claim 70, wherein said means for identifying the source users based on the source users association with the reported aspects that corresponds to the one or more target outcomes, comprises: means for providing reported aspects that are at least associated with the identified source users.

72. The computationally-implemented system of claim 71, wherein said means for providing reported aspects that are at least associated with the identified source users, comprises: means 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.

73. The computationally-implemented system of claim 72, wherein said means 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, comprises: means 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.

74. The computationally-implemented system of claim 72, wherein said means 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, comprises: means 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.

75. The computationally-implemented system of claim 72, wherein said means 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, comprises: means 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.

76.-77. (canceled)

78. The computationally-implemented system of claim 65, wherein said 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, comprises: means 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.

79. The computationally-implemented system of claim 78, wherein said means 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, comprises: means 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.

80. The computationally-implemented system of claim 79, wherein said means 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, comprises: means 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.

81. The computationally-implemented system of claim 79, wherein said means 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, comprises: means 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.

82. The computationally-implemented system of claim 78, wherein said means 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, comprises: means 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.

83. The computationally-implemented system of claim 78, wherein said means 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, comprises: means 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.

84.-129. (canceled)

130. A computer program product comprising: 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; andone 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.

131. (canceled)