Patent Grant
8260807
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 and 1b show a high-level block diagram of a Computing Device 10 operating in a network environment.
a shows another perspective of the Relevant Reported Aspect Identification Module 102 of the Computing Device 10 of
b shows another perspective of the Relevant Reported Aspect Providing Module 104 of the Computing Device 10 of
c shows one perspective of one of the Sensing Devices 40 of the environment of
a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
c is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
d is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
e is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
f is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
g is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
h is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect identifying operation 302 of
a is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 304 of
b is a high-level logic flowchart of a process depicting alternate implementations of the relevant reported aspect providing operation 304 of
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
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
Note that for ease of understanding and explanation, the computing device 10 of the exemplary environment 100 of
Referring back to
In various embodiments, the computing device 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 14 associated with one or more source users 2* that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects 14 being based, at least in part, on relevancy of the one or more relevant reported aspects 14 with respect to achieving the one or more target outcomes. The identification of the one or more relevant reported aspects 14 may, in some cases, be in response to reception of one or more solicitations 13 from one or more end users 4*(e.g., via one or more local end user devices 30*), from one or more source users 2*(e.g., via one or more local source user devices 20*), from one or more network servers 60, or from other parties (e.g., one or more third parties 6). Note that in embodiments where the computing device 10 is an end user device or a source user device, the one or more solicitations 13 may be directly received from an end user 4* or a source user 2* via a user interface 120.
In various embodiments, the identification of the one or more relevant reported aspects 14 may be by identifying the one or more relevant reported aspects 14 from a plurality of reported aspects 15, which may, in some embodiments, be stored in memory 116. The plurality of reported aspects 15 may include both relevant reported aspects 14 that are relevant to achieving one or more target outcomes, and non-relevant reported aspects 16 that are not relevant to achieving the one or more target outcomes. In some implementations, the plurality of reported aspects 15 may be associated with a single source user 2*. In other implementations, however, the plurality of reported aspects 15 may be associated with a plurality of source users 2*.
The plurality of reported aspects 15, which may be associated with one or more source users 2*, may be acquired from a variety of different sources. For example, in some implementations, one or more of the plurality of reported aspects 15 may be acquired from one or more local source user devices 20*, from one or more network servers 60, from one or more sensing devices 40, and/or one or more third parties 6.
Note that in embodiments where the computing device 10 is a source user device, one or more of the plurality of reported aspects 15 may be acquired directly from one or more sensing devices 40 or directly from a source user 2* via a user interface 120. Further, in embodiments where the computing device 10 is a source user device, the computing device 10 may include one or more integrated sensors 240 that may be employed in order to directly sense or detect one or more aspects associated with a source user 2*. As will be further described, a sensor 240 may be any type of sensor including, for example, sensors that can sense various physical characteristics of a source user 2* (e.g., heart rate sensor or blood pressure sensor), sensors that can sense activities of a source user 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 2*(e.g., global positioning system or GPS), and so forth.
In any event, after identifying the one or more relevant reported aspects 14, the computing device 10, may be configured to, among other things, provide the one or more relevant reported aspects 14 to one or more entities. In this context, the providing of the one or more relevant reported aspects 14 may involve transmitting, via the wireless network and/or the wired network 50, the one or more relevant reported aspects 14 to one or more network entities such as local source user devices 20*, network servers 60, local end user devices 30*, and/or third parties 6. The one or more relevant reported aspects 14 may also be provided by displaying or indicating the one or more relevant reported aspects 14 through a user interface 120 (e.g., a display monitor and/or speakers) in embodiments where, for example, the computing device 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 14 by the computing device 10 may be in response to the computing device 10 receiving, via the wireless network and/or the wired network 50, one or more solicitations 13 from, for example, one or more end users 4* (e.g., via one or more local end user devices 30*), from one or more source users 2*(e.g., via one or more local source user devices 20*), from one or more network servers 60, or from one or more third parties 6 (e.g., a network service provider, a content provider, and so forth). The one or more solicitations 13 may be, in various implementations, one or more requests, queries, and so forth. In some embodiments, the one or more solicitations 13 may indicate at least one or more target outcomes. In other embodiments, however, the one or more solicitations 13 may indicate one or more source users 2* who have achieved the one or more target outcomes. In embodiments where the computing device 10 is a source user device or an end user device, the one or more solicitations 13 may be received through the user interface 120.
The computing device 10 as previously indicated 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, 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.
With respect to the one or more sensing devices 40 of the exemplary environment 100 of
Examples of sensors 240 include, for example, devices that can detect physical or physiological characteristics of one or more source users 2*, devices that can detect activities of the one or more source users 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 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 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 20* and each of the one or more 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 one or more 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 device 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
Referring to the relevant reported aspect identification module 102, the relevant reported aspect identification module 102 may be configured to, among other things, identify one or more relevant reported aspects 14 based, at least in part, on relevancy of the one or more relevant reported aspects 14 with respect to achievement of one or more target outcomes, the one or more relevant reported aspects 14 to be identified being associated with one or more source users 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 13. In contrast, the relevant reported aspect providing module 104 may be configured to, among other things, provide the identified one or more relevant reported aspects 14.
The memory 116 may be designed to store various data including a plurality of reported aspects 15 associated with one or more source user 2*. The plurality of reported aspects 15 stored in the memory 116 may include both relevant reported aspects 14 that are relevant to achieving one or more target outcomes and non-relevant reported aspects 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 116 in various implementations including, for example, one or more end user relevancy indications 142 (e.g., one or more indications that indicate the types of reported aspects that an end user 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 144 (e.g., one or more indications provided by a source user 2* that indicate at least which types of reported aspects 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 are relevant to achieving one or more target outcomes), one or more predefined time increment indications 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 2*), and/or 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). In various implementations, 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 social networking entry reception module 110 may be configured to receive social networking entries from one or more sources including, for example, from one or more source users 2*, from one or more end users 4*, from one or more third parties 6, from one or more sensing devices 40, and/or from one or more network servers 60. The social networking entry reception module 110 may further include a blog entry reception module 111 for receiving blog entries (e.g. microblog entries) and/or a status report reception module 112 for receiving social networking status reports. The journal entry reception module 114 may be configured to receive journal entries from, for example, one or more source users 2*, one or more end users 4*, and/or one or more third parties 6 (e.g., a non-user). The sensor data reception module 115 may be configured to receive sensing data that indicate one or more reported aspects 15 associated with one or more source users 2* from one or more sensing devices 40 or one or more integrated sensors 240. The user interface 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.
a illustrates particular implementations of the relevant reported aspect identification module 102 of the computing device 10 of
The source user associated reported aspect identification module 202 may further include a target outcome corresponding reported aspect identification module 204 and/or an associated source user determination module 206. The target outcome corresponding reported aspect identification module 204 may be configured to identify the one or more relevant reported aspects 14 by at least identifying one or more reported aspects 15 that correspond to the one or more target outcomes. In contrast, the associated source user determination module 206 may be configured to determine one or more source users 2* who are associated with the one or more reported aspects 15 that correspond to the one or more target outcomes. In doing so, the one or more source users 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 2* who have achieved the one or more target outcomes, the relevant reported aspect identification module 102 may identify one or more reported aspects 15 that are associated with the one or more source users 2* who have achieved the target outcomes.
In some implementations, the relevant reported aspect identification module 102 may include a relevancy factor relevant reported aspect identification module 208 and/or a log entry originated relevant reported aspect identification module 212. In brief, the relevancy factor relevant reported aspect identification module 208 may be configured to identify one or more reported aspects 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 14 belonging to a type or types of aspects that are of interest to an end user 4*). In contrast, the log entry originated relevant reported aspect identification module 212 may be configured to identify the one or more relevant reported aspects 14 by identifying one or more reported aspects 15 that were originally reported through log entries (e.g., microblog entries, status reports, and so forth).
b illustrates particular implementations of the relevant reported aspect providing module 104 of
In various implementations, the relevant reported aspect providing module 104 may include a link indication providing module 224 that is configured to provide one or more indications that links (e.g., associates) two or more relevant reported aspects 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 14 may be facilitated by indicating the link between the two or more relevant reported aspects 14. In some cases, the link indication providing module 224 may further include a relationship indication providing module 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 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 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
In some implementations, the one or more sensors 240 may include devices that can detect activities of a user (e.g., a source user 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 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 2*, global positioning system (GPS) to provide location data related to a user (e.g., locations of the source user 2*), and so forth. In various implementations, a sensing device 40 may further include a network interface 242 and/or a memory 244. The network interface 242 may be designed to interface with a wireless network and/or a wired network 50 while the memory 244 may be designed to store, for example, sensing data provided by the one or more sensors 240.
Referring back to the computing device 10 of
A more detailed discussion related to the computing device 10 of
In
Further, in
In any event, after a start operation, the operational flow 300 may move to a relevant reported aspect identifying operation 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 102 of the computing device 10 of
Note that in various implementations, the one or more solicitations 13 to be received may be for soliciting the one or more relevant reported aspects 14. Alternatively, the one or more solicitations 13 may be for soliciting data for developing one or more personalized plans or templates that may be designed to facilitate an end user 4* to achieve the one or more target outcomes. In other implementations, the one or more solicitations 13 may be for soliciting other types of data.
In addition to the relevant reported aspect identifying operation 302, operational flow 300 may also include a relevant reported aspect providing operation 304 for providing the one or more relevant reported aspects. For instance, the relevant reported aspect providing module 104 of the computing device 10 providing (e.g., transmitting, indicating, displaying, allowing access to, and so forth) the one or more relevant reported aspects 14. As will be further described herein, the relevant reported aspect identifying operation 302 as well as the relevant reported aspect providing operation 304 may be implemented in a number of different ways in various alternative implementations.
For example,
In some implementations, operation 402 may further include an operation 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
In the same or different implementations, the relevant reported aspect identifying operation 302 of
In the same or different implementations, the relevant reported aspect identifying operation 302 may include an operation 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
In various implementations, operation 405 may include one or more additional operations. For example, in some implementations, operation 405 may include an operation 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
In the same or different implementations, operation 405 may include an operation 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
Operation 407 in turn may further include an operation 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
In the same or different implementations, operation 407 may include an operation 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
In the same or different implementations, operation 407 may include an operation 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
In the same or different implementations, operation 407 may include an operation 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
In various implementations, the relevant reported aspect identifying operation 302 of
In order to identify relevant reported aspects 14 of one or more source users 2* that are relevant for achieving one or more target outcomes from, for example, a plurality of reported aspects 15, the relevant reported aspect identifying operation 302 of
In order to identify the one or more reported aspects 15 that are associated with the one or more source users 2* who have achieved the one or more target outcomes, operation 413 may include an operation to identify those reported aspects 15 that corresponds to the one or more target outcomes. For example, in some implementations, operation 413 may include an operation 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
In order to identify the one or more relevant reported aspects 14, operation 414 may include an operation 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
In some implementations, in order to identify the one or more relevant reported aspects 14 operation 415 may include at least an operation 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
In various implementations, operation 416 may include an operation 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
The one or more relevancy factors considered in operation 417 may be provided by a variety of sources. For example, in some implementations, operation 417 may include an operation 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
In the same or different implementations, operation 417 may include an operation 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
In the same or different implementations, operation 417 may include an operation 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
In the same or different implementations, operation 417 may include an operation 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
That is, not all relevant reported aspects 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 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 2* who have been reported as achieving the one or more target outcomes. For example, reported aspects 15 that are associated with source users 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 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 15 that corresponds to the one or more target outcomes) by the one or more source users 2*.
Thus, a reported aspect 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 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 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 4*, by a source user 2*, or by a third party source (e.g., third party 6).
In various implementations, operation 421 may, in turn, include an operation 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
In some implementations, the relevant reported aspect identifying operation 302 may include an operation 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
In various implementations, operation 423 may include an operation 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
The one or more source users 2* who share one or more common traits with the end user 4* may have a variety of traits that may be shared with the end user 4* and which may be considered in identifying relevant reported aspects 14 in various implementations. For example, in some implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In the same or different implementations, operation 424 may include an operation 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
In various implementations, other types of relevancy factors may be considered in identifying the one or more relevant reported aspects 14 other than relevancy factors that relate to common traits of an end user 4* as was the case in operation 424. For example, in some implementations, operation 423 for identifying the one or more relevant reported aspects 14 based on one or more relevancy factors may include an operation 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
Operation 433 may further include, in various implementations, an operation 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
In the same or different implementations, operation 433 may include an operation 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
In some implementations, operation 423 may include an operation 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
In the same or different implementations, operation 423 may include an operation 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
A subjective user state may be any state or status associated with a source user 2* that can typically only be indicated by the source user 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 423 may include an operation 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
In the same or different implementations, operation 423 may include an operation 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
In the same or different implementations, operation 423 may include an operation 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
The relevant reported aspects identified through the relevant reported aspect identifying operation 302 of
In various implementations, operation 441 may include one or more additional operations. For example, in some implementations, operation 441 may include an operation 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
In the same or different implementations, operation 441 may include an operation 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
In the same or different implementations, operation 441 may include an operation 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
In the same or different implementations, operation 441 may include an operation 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
In various implementations, the relevant reported aspect identifying operation 302 of
In the same or different implementations, the relevant reported aspect identifying operation 302 may include an operation 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
In the same or different implementations, the relevant reported aspect identifying operation 302 may include an operation 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
In various implementations, operation 448 may in turn include one or more additional operations. For example, in some implementations, operation 448 may include an operation 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
In the same or different implementations, operation 448 may include an operation 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
In the same or different implementations, operation 448 may include an operation 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
Referring back to the relevant reported aspect providing operation 304 of
In some implementations, operation 552 may further include an operation 553 for transmitting the one or more relevant reported aspects to one or more network devices as depicted in
Operation 553 may, in turn, include one or more additional operations. For example, in some implementations, operation 553 may include an operation 554 for transmitting the one or more relevant reported aspects to one or more network servers as depicted in
In the same or different implementations, operation 553 may include an operation 555 for transmitting the one or more relevant reported aspects to one or more local end user devices as depicted in
In the same or different implementations, operation 553 may include an operation 556 for transmitting the one or more relevant reported aspects to one or more local source user devices as depicted in
In various implementations, the relevant reported aspect providing operation 304 of
Operation 557 may, in turn, include an operation 558 for providing one or more indications that link together two or more of the relevant reported aspects as depicted in
Thus, in some implementations, operation 558 may further include an operation 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
In the same or different implementations, operation 558 may further include an operation 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
In the same or different implementations, operation 558 may further include an operation 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
In the same or different implementations, operation 558 may further include an operation 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
In various implementations, operation 557 may include an operation 563 for providing one or more relevant reported aspects that are intermediate outcomes associated with the one or more target outcomes as depicted in
Turning now to
For example, the processor 602 may execute the computer readable instructions 604 in order to identify, in response to reception of one or more solicitations 13, one or more relevant reported aspects 14 associated with one or more source users 2* that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects 14 being based, at least in part, on relevancy of the one or more relevant reported aspects 14 with respect to the one or more target outcomes; and/or to provide the one or more relevant reported aspects 14 as illustrated by the operational flow 300 of
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.”
The present application is related to and claims the benefit of the earliest available effective filing date(s) from the following listed application(s) (the “Related Applications”) (e.g., claims earliest available priority dates for other than provisional patent applications or claims benefits under 35 USC §119(e) for provisional patent applications, for any and all parent, grandparent, great-grandparent, etc. applications of the Related Application(s)). All subject matter of the Related Applications and of any and all parent, grandparent, great-grandparent, etc. applications of the Related Applications is incorporated herein by reference to the extent such subject matter is not inconsistent herewith. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/584,489, entitled PERSONALIZED PLAN DEVELOPMENT, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 3 Sep. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/584,653, entitled PERSONALIZED PLAN DEVELOPMENT, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 8 Sep. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/587,018, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 29 Sep. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/587,127, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 30 Sep. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/590,027, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORE SOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 29 Oct. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/590,039, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORE SOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 30 Oct. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/590,600, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 10 Nov. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/590,841, entitled PERSONALIZED PLAN DEVELOPMENT BASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 12 Nov. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/592,075, entitled DEVELOPMENT OF PERSONALIZED PLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 17 Nov. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/592,161, entitled DEVELOPMENT OF PERSONALIZED PLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 18 Nov. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation or continuation-in-part. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTO Official Gazette Mar. 18, 2003, available at http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm. The present Applicant Entity (hereinafter “Applicant”) has provided above a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization, such as “continuation” or “continuation-in-part,” for claiming priority to U.S. patent applications. Notwithstanding the foregoing, Applicant understands that the USPTO's computer programs have certain data entry requirements, and hence Applicant is designating the present application as a continuation-in-part of its parent applications as set forth above, but expressly points out that such designations are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).
| Number | Name | Date | Kind |
|---|---|---|---|
| 4853854 | Behar et al. | Aug 1989 | A |
| 5961446 | Beller et al. | Oct 1999 | A |
| 6338044 | Cook et al. | Jan 2002 | B1 |
| 6353447 | Truluck et al. | Mar 2002 | B1 |
| 6842604 | Cook et al. | Jan 2005 | B1 |
| 7587368 | Felsher | Sep 2009 | B2 |
| 7668735 | Grace et al. | Feb 2010 | B2 |
| 7702685 | Shrufi et al. | Apr 2010 | B2 |
| 7860852 | Brunner et al. | Dec 2010 | B2 |
| 7908182 | Gupta | Mar 2011 | B1 |
| 7959567 | Stivoric et al. | Jun 2011 | B2 |
| 8005906 | Hayashi et al. | Aug 2011 | B2 |
| 20020107707 | Naparstek et al. | Aug 2002 | A1 |
| 20040015337 | Thomas et al. | Jan 2004 | A1 |
| 20050197553 | Cooper | Sep 2005 | A1 |
| 20050216300 | Appelman et al. | Sep 2005 | A1 |
| 20060036619 | Fuerst et al. | Feb 2006 | A1 |
| 20070088576 | de Beus et al. | Apr 2007 | A1 |
| 20080091471 | Michon et al. | Apr 2008 | A1 |
| 20080288425 | Posse et al. | Nov 2008 | A1 |
| 20080294012 | Kurtz et al. | Nov 2008 | A1 |
| 20090044113 | Jones et al. | Feb 2009 | A1 |
| 20090070679 | Shen et al. | Mar 2009 | A1 |
| 20090075242 | Schwarzberg et al. | Mar 2009 | A1 |
| 20090076335 | Schwarzberg et al. | Mar 2009 | A1 |
| 20090100469 | Conradt et al. | Apr 2009 | A1 |
| 20090176526 | Altman | Jul 2009 | A1 |
| 20090258710 | Quatrochi et al. | Oct 2009 | A1 |
| 20090271247 | Karelin et al. | Oct 2009 | A1 |
| 20090292814 | Ting et al. | Nov 2009 | A1 |
| 20090299990 | Setlur et al. | Dec 2009 | A1 |
| 20090313041 | Eder | Dec 2009 | A1 |
| 20090319288 | Slaney et al. | Dec 2009 | A1 |
| 20090326981 | Karkanias et al. | Dec 2009 | A1 |
| 20100063993 | Higgins et al. | Mar 2010 | A1 |
| 20100114788 | White et al. | May 2010 | A1 |
| 20100268830 | McKee et al. | Oct 2010 | A1 |
| 20100281364 | Sidman | Nov 2010 | A1 |
| 20100293247 | McKee et al. | Nov 2010 | A1 |
| 20100305806 | Hawley | Dec 2010 | A1 |
| 20110022602 | Luo et al. | Jan 2011 | A1 |
| 20110179161 | Guy et al. | Jul 2011 | A1 |
| 20110185020 | Ramamurthy et al. | Jul 2011 | A1 |
| 20110252101 | Davis et al. | Oct 2011 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20110055269 A1 | Mar 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12592161 | Nov 2009 | US |
| Child | 12592544 | US | |
| Parent | 12592075 | Nov 2009 | US |
| Child | 12592161 | US | |
| Parent | 12590841 | Nov 2009 | US |
| Child | 12592075 | US | |
| Parent | 12590600 | Nov 2009 | US |
| Child | 12590841 | US | |
| Parent | 12590039 | Oct 2009 | US |
| Child | 12590600 | US | |
| Parent | 12590027 | Oct 2009 | US |
| Child | 12590039 | US | |
| Parent | 12587127 | Sep 2009 | US |
| Child | 12590027 | US | |
| Parent | 12587018 | Sep 2009 | US |
| Child | 12587127 | US | |
| Parent | 12584653 | Sep 2009 | US |
| Child | 12587018 | US | |
| Parent | 12584489 | Sep 2009 | US |
| Child | 12584653 | US |
