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 and 1b show a high-level block diagram of a Computing Device 10 operating in a network environment.
a shows another perspective of the Particular template providing module 104 of the Computing Device 10 of
b shows one perspective of a Particular Template.
a is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 302 of
b is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 302 of
c is a high-level logic flowchart of a process depicting alternate implementations of the request receiving operation 302 of
a is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 304 of
b is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 304 of
c is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 304 of
d is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 304 of
e is a high-level logic flowchart of a process depicting alternate implementations of the particular template providing operation 304 of
f is a high-level logic flowchart of a process depicting alternate implementations of the particular template 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. 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
Note further 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, receive one or more requests 16 indicating at least one or more target outcomes 14 of one or more particular templates 18, the one or more particular templates 18 designed to facilitate one or more end users 4* to achieve the one or more target outcomes 14 when one or more emulatable aspects 12 included in the one or more particular templates 18 are emulated. For these embodiments, the one or more requests 16 may be received from a variety of requesting sources including, for example, one or more end users 4*, one or more third parties 6, and/or one or more network servers 60. In some embodiments, such as in embodiments in which the computing device 10 is a server, the one or more requests 16 may be indirectly received from a requesting source (e.g., an end user 4*) via the one or more communication networks 50.
In other embodiments, such as in embodiments in which the computing device 10 is, for example, an end user device, the one or more requests 16 may be received directly from a requesting source (e.g., an end user 4*) via a user interface 120. In various embodiments, the one or more requests 16 may include data that may indicate the one or more target outcomes 14. Note that
In any event, in response to receiving the one or more requests 16, the computing device 10 may be designed to selectively provide from a plurality of templates 17 the one or more particular templates 18, the providing of the one or more particular templates 18 being based at least on the association of the one or more particular templates 18 with the one or more target outcomes 14, the one or more particular templates 18 developed based on one or more reported aspects 15 of one or more source users 2*. In some selective embodiments, the computing device 10 may be designed to develop the plurality of templates 17 including the one or more particular templates 18 based on reported aspects 15 that may be acquired from one or more sources including, for example, one or more local source user devices 20*, one or more sensor integrated devices 40, one or more third parties 6, and/or one or more network servers 60. In some embodiments, the computing device 10 may be designed to present the one or more templates 17 via user interface 120 and/or via one or more communication networks 50.
In embodiments in which the computing device 10 is designed to present the one or more particular templates 18, the one or more particular templates 18 may be presented by transmitting the one or more particular templates 18 to one or more network servers 60, to one or more source users 2*(e.g., one or more local source user devices 20*), to one or more end users 4*(e.g., one or more local end user devices 30*), and/or to one or more third parties 6. In embodiments where, for example, the computing device 10 is a source user device or an end user device rather than a sever, the computing device 10 may indicate (e.g., visually display or audioally indicate) the one or more particular templates 18 via a user interface 120.
In embodiments in which the computing device 10 is designed to receive reported aspects 15, the computing device 10 may randomly, semi-continuously, or continuously receive reported aspects 15 associated with one or more source user 2*. Such reported aspects 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 2*.
In embodiments in which the computing device 10 is configured to develop, for example, one or more particular templates 18 that is designed to facilitate achievement of one or more target outcomes 14, the one or more particular templates 18 may be developed by initially determining which of the acquired reported aspects 15 may be relevant to achieving the one or more target outcomes 14. After determining which of the reported aspects 15 are relevant to achieving the one or more target outcomes 14, the computing device 10 may be designed to include into the one or more particular templates 18 one or more emulatable aspects 12 that correspond (e.g., equivalent) to one or more reported aspects 15 that have been determined to be relevant to achieving the one or more target outcomes 14. Note that throughout the following discussion, reference number “18” will be used in connection with the one or more particular templates 18 that are requested and provided, while reference number “17” will be used with respect to the general population or group of templates 17 that the one or more particular templates 18 are provided from.
In various embodiments, 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 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
As will be further described herein, the one or more sensors 240, which may also be included in the one or more local source user devices 20* and/or the computing device 10, may include any type of sensors that can sense one or more aspects of a source user 2*. Examples of such, ensors 240 include, for example, sensors 240 that can sense various physical characteristics of a source user 2*(e.g., heart rate sensor or blood pressure sensor), sensors 240 that can sense activities of a source user 2*(e.g., a pedometer, an accelerometer, and so forth), sensors 240 that can sense environment conditions (e.g., air quality sensors), sensors 240 that can sense the location of a source user 2*(e.g., global positioning system or GPS), sensors 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 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
The computing device 10 may also include, in various embodiments, a network interface 118 (e.g., a network interface card or NIC), a user interface 120, a social networking entry reception module 110 (which may further include a blog entry reception module 111 and/or a status report reception module 112), and/or one or more sensors 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 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.
Referring particularly now to the request receiving module 102, the request receiving module 102 may be configured to, among other things, receive one or more requests 16 that indicate at least one or more target outcomes 14 of one or more particular templates 18, the one or more particular templates 18 designed to facilitate one or more end users 4* to achieve the one or more target outcomes 14 when one or more emulatable aspects 12 included in the one or more particular templates 18 are emulated. In contrast, the particular template providing module 104 may be configured to, among other things, provide from a plurality of templates 17 the one or more particular templates 18, the providing being based at least on the association of the one or more particular templates 18 with the one or more target outcomes 14, the one or more particular templates 18 developed based on one or more reported aspects 12 of one or more source users 2*.
The memory 116 may be designed to store various data including a plurality of templates 17, which may have been developed based on reported aspects 15 associated with one or more source users 2*. Other types of data may also be stored in the memory 116 in various implementations including, for example, one or more end user trait indications 138 (e.g., one or more indications that indicate one or more traits of one or more end users 4*), one or more end user limitation indications 140 (e.g., one or more indications that indicate one or more limitations associated with one or more end users 4* including contextual limitations, physical limitations, legal limitations, and so forth), one or more end user relevancy indications 142 (e.g., one or more indications that indicate the types of reported aspects 15 that an end user 4* has an interest in or believes is relevant to achieving one or more target outcomes 14) 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 15 are relevant to achieving one or more target outcomes 14).
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 15 are relevant to achieving one or more target outcomes 14), one or more predefined time increment indications 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 17), 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 target outcome identifying data interpreting module 103 may be configured to process and interpret target outcome identification data that may be included in a request 16 received by the request receiving module 102. By interpreting the target outcome identification data (e.g., alphanumeric data, image data, audio data, and so forth), one or more target outcomes 14 of one or more particular templates 18 may be identified or determined.
In various implementations, the presentation module 106 may be configured to present one or more particular templates 18 provided by the particular template providing module 104. The transmission module 236 that may be included in the presentation module 106 may be designed to transmit the one or more particular templates 18 provided by the particular template providing module 104 via the one or more communication networks 50. The user interface indication module 238, in contrast, may be designed to indicate the one or more particular templates 18 via a user interface 120 (e.g., display monitor, speaker system, touch screen, and so forth).
The social networking entry reception module 110 may be configured to receive social networking entries from one or more sources including, for example, one or more source users 2*, one or more end users 4*, one or more third parties 6, one or more sensor integrated devices 40, and/or 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. In some implementations, one or more reported aspects 15 of one or more source users 2* may be received via social networking entries (e.g., blog entries, status reports, and so forth). 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 particular template providing module 104 of the computing device 10 of
b illustrates one perspective of a particular template 18 (or template 17). In particular,
In embodiments in which the particular template 18 includes data that indicate multiple emulatable aspects 12, the particular template 18 may also include data that defines the relationship (e.g., temporal, specific time, and/or spatial relationships) between the emulatable aspects 12. Also, when the particular templates 18 indicates multiple emulatable aspects 12 one or more of the emulatable aspects 12 may be one or more emulatable intermediate outcomes that are associated with the one or more target outcomes 14 of the particular template 18. For example, if a target outcome 14 for a particular template 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 18.
Referring back to the computing device 10 of
A more detailed discussion relating to the functional aspects of the computing device 10 of
In
Further, in
In any event, after a start operation, the operational flow 300 may move to a request receiving operation 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 102 of the computing device 10 of
In addition to the request reception operation 302, operational flow 300 may also include a particular template providing operation 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 104 of the computing device 10 providing from a plurality of templates 17 the one or more particular templates 18, the providing of the one or more particular templates 18 being based at least on the association of the one or more particular templates 18 with the one or more target outcomes 14, the one or more particular templates 18 developed (e.g., originally created) based on one or more reported aspects 15 of one or more source users 2*. As will be further described herein, both the request receiving operation 302 and the particular template providing operation 304 of
For example,
In the same or different implementations, the request receiving operation 302 may include an operation 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
In the same or different implementations, the request receiving operation 302 may include an operation 404 for receiving the one or more requests indicating the at least one or more target outcomes via a user interface as depicted in
The one or more requests 16 that may be received through the request receiving operation 302 may include data that may be processed in order to facilitate the determination or identification of the one or more target outcomes 14. For example, in some implementations, the request reception operation 302 may include an operation 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
Various types of data may be included in the one or more requests 16 that may facilitate in the determination or identification of the one or more target outcomes 14 in various alternative implementations. For example, in some implementations, operation 405 may include an operation 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
In the same or different implementations, operation 405 may include an operation 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
In the same or different implementations, operation 405 may include an operation 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
After receiving the one or more requests 16 that include the data to facilitate determination of the one or more target outcomes 14, the data may be processed in order to determine the one or more target outcomes 14. For example, in some implementations, operation 405 may include an operation 409 for interpreting the data to determine the one or more target outcomes as depicted in
In various implementations, other types of data may be included in the one or more requests 16 that may be received through the request receiving operation 302 of
Various types of user traits may be indicated by the one or more requests 16 that are received through operation 410 in various alternative implementations. For example, in some implementations, the operation 410 may include an operation 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
In the same or different implementations, the operation 410 may include an operation 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
In the same or different implementations, the operation 410 may include an operation 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
In the same or different implementations, the operation 410 may include an operation 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
In the same or different implementations, the operation 410 may include an operation 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
In the same or different implementations, the operation 410 may include an operation 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
In the same or different implementations, the operation 410 may include an operation 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
In some implementations, the request receiving operation 302 of
In some implementations, the request receiving operation 302 of
Various types of limitations associated with the at least one end user 4* may be indicated by the one or more requests 16. For example, in some implementations, operation 419 may include an operation 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
In the same or different implementations, operation 419 may include an operation 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
In the same or different implementations, operation 419 may include an operation 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
In the same or different implementations, operation 419 may include an operation 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
In the same or different implementations, operation 419 may include an operation 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
In the same or different implementations, operation 419 may include an operation 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
In the same or different implementations, operation 419 may include an operation 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
In some implementations, the request receiving operation 302 of
In some implementations, the request receiving operation 302 may include an operation 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
Referring back to
In some implementations, the particular template providing operation 304 may include an operation 530 for acquiring the one or more particular templates from a plurality of templates located at one or more network sites as depicted in
In some cases, operation 530 may in turn include an operation 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
In some implementations, the particular template providing operation 304 may include an operation 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
In some implementations, the particular template providing operation 304 may include an operation 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
In some implementations, the particular template providing operation 304 may include an operation 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
In some implementations, the particular template providing operation 304 may include an operation 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
For example, in some implementations, operation 535 may include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In the same or different implementations, operation 535 may further include an operation 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
In various implementations, the particular template providing operation 304 of
In some implementations, operation 545 may further include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In the same or different implementations, operation 545 may include an operation 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
In some implementations, the particular template providing operation 304 of
In some implementations, the particular template providing operation 304 of
In some implementations, the particular template providing operation 304 of
In some implementations, operation 556 may further include an operation 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
In the same or different implementations, operation 556 may include an operation 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
Different types of particular templates 18 may be provided by the particular template providing operation 304 of
In the same or different implementations, the particular template providing operation 304 may include an operation 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
In the same or different implementations, the particular template providing operation 304 may include an operation 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
In the same or different implementations, the particular template providing operation 304 may include an operation 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
In the same or different implementations, the particular template providing operation 304 may include an operation 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
In the same or different implementations, the particular template providing operation 304 may include an operation 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
In the same or different implementations, the particular template providing operation 304 may include an operation 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
In the same or different implementations, the particular template providing operation 304 may include an operation 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
Referring to
In addition, operational flow 300 includes a particular template presenting operation 606 for presenting the one or more particular templates as depicted in
In some implementations, the particular template presentation operation 606 may include an operation 768 for transmitting the one or more particular templates via one or more communication networks as depicted in
In the same or different implementations, the particular template presentation operation 606 may include an operation 769 for indicating the one or more particular templates via a user interface as depicted in
Turning now to
For example, the processor 802 may execute the computer readable instructions 804 in order to receive one or more requests 16 indicating one or more target outcomes 14 of one or more particular templates 18, the one or more particular templates 18 designed to facilitate one or more end users 4* to achieve the one or more target outcomes 14 when one or more emulatable aspects 12 included in the one or more particular templates 18 are emulated; and/or to provide from a plurality of templates 17 the one or more particular templates 18, the providing being based at least on the association of the one or more particular templates 18 with the one or more target outcomes 14, the one or more particular templates 18 developed based on one or more reported aspects 15 of one or more source users 2* 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. 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,544, entitled IDENTIFICATION AND PROVISION OF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OF TARGET OUTCOMES, 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 24 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,548, entitled IDENTIFICATION AND PROVISION OF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OF TARGET OUTCOMES, 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 25 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,944, entitled TEMPLATE DEVELOPMENT BASED ON SENSOR ORIGINATED 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 3 Dec. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. 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,946, entitled TEMPLATE DEVELOPMENT BASED ON SENSOR ORIGINATED 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 4 Dec. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U. S. patent application Ser. No. 12/653,117 entitled SOURCE USER BASED PROVISION OF ONE OR MORE. TEMPLATES, 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 7 Dec. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U. S. patent application Ser. No. 12/653,180, entitled SOURCE USER BASED PROVISION OF ONE OR MORE TEMPLATES, 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 Dec. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U. S. patent application Ser. No. 12/653,387, entitled TARGET OUTCOME BASED PROVISION OF ONE OR MORE TEMPLATES, naming Shavari P. Pinninger; Jason Garms; Roderick A. Hyde; Edward K.Y. Jung; Chris D. Karkanias; Eric C. Leathardt; Royce A. Levien; Richard T. Lord; Robert W. Lord: Mark A. Malemud; John D . Rinaldo, Jr.; Clarence T. Tegreene; Kristin Tolle; Lowell L. Woo& Jr. as Inventors, filed 10 Dec. 2009, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. 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 | |
---|---|---|---|
20110055126 A1 | Mar 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12592544 | Nov 2009 | US |
Child | 12653386 | US | |
Parent | 12592548 | Nov 2009 | US |
Child | 12592544 | US | |
Parent | 12592944 | Dec 2009 | US |
Child | 12592548 | US | |
Parent | 12592946 | Dec 2009 | US |
Child | 12592944 | US | |
Parent | 12653117 | Dec 2009 | US |
Child | 12592946 | US | |
Parent | 12653180 | Dec 2009 | US |
Child | 12653117 | US | |
Parent | 12653387 | Dec 2009 | US |
Child | 12653180 | US | |
Parent | 12584489 | Sep 2009 | US |
Child | 12653180 | US |