U.S. patent application number 17/750516 was filed with the patent office on 2022-09-08 for systems and methods for task assistance.
The applicant listed for this patent is Google LLC. Invention is credited to Erwin Can Sar, Seth Isaac Glickman, Tristan Harris, Timothy Youngjin Sohn, Jacqueline Amy Tsay, Vijay Umapathy.
Application Number | 20220284404 17/750516 |
Document ID | / |
Family ID | 1000006348234 |
Filed Date | 2022-09-08 |
United States Patent
Application |
20220284404 |
Kind Code |
A1 |
Harris; Tristan ; et
al. |
September 8, 2022 |
Systems and Methods for Task Assistance
Abstract
A method of task management executes at a computing device
having one or more processors and memory. The memory stores one or
more programs configured for execution by the one or more
processors. There is received a description of a task associated
with a user. Upon receipt of the description of the task, one or
more entities associated with the task are identified using at
least the description of the task and geographic information about
the user. Information is identified for performing the task with
the at least one respective entity in the one or more entities
based upon an identity of the entity. This identified information
for performing the task is then formatted for use by the user.
Inventors: |
Harris; Tristan; (Santa
Rose, CA) ; Can Sar; Erwin; (San Francisco, CA)
; Sohn; Timothy Youngjin; (Mountain View, CA) ;
Umapathy; Vijay; (Sunnyvale, CA) ; Tsay; Jacqueline
Amy; (Mountain View, CA) ; Glickman; Seth Isaac;
(San Francisco, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Google LLC |
Mountain View |
CA |
US |
|
|
Family ID: |
1000006348234 |
Appl. No.: |
17/750516 |
Filed: |
May 23, 2022 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16536687 |
Aug 9, 2019 |
11367052 |
|
|
17750516 |
|
|
|
|
14473564 |
Aug 29, 2014 |
10423932 |
|
|
16536687 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06Q 50/26 20130101;
G06Q 30/018 20130101; H04L 51/222 20220501; G06Q 10/063114
20130101; H04L 2101/38 20220501; G06Q 10/1097 20130101; G06Q 10/107
20130101; H04L 51/18 20130101 |
International
Class: |
G06Q 10/10 20060101
G06Q010/10; G06Q 10/06 20060101 G06Q010/06; G06Q 30/00 20060101
G06Q030/00; G06Q 50/26 20060101 G06Q050/26; H04L 51/18 20060101
H04L051/18; H04L 51/222 20060101 H04L051/222 |
Claims
1. A method of providing task assistance in association with an
electronic messaging application, the method comprising: obtaining,
by one or more processors of a computing device associated with the
electronic messaging application, an identification of a task to be
performed by a user; identifying, by the one or more processors, at
least one entity corresponding to the task based on a description
of the task and information about the user; based on identifying
the at least one entity, the one or more processors identifying
information for performing the task; formatting, by one or more
processors, the identified information for performing the task for
presentation via a user interface; and outputting by one or more
processors, for presentation with the electronic messaging
application via the user interface, the identified information for
performing the task and information about the identified at least
one entity.
2. The method of claim 1, wherein obtaining the identification of
the task to be performed includes identifying the task based on an
electronic message object associated with one or more messages of
the electronic messaging application.
3. The method of claim 1, wherein identifying the at least one
entity includes evaluating whether each entity of a set of entities
is capable of enabling performance of the task.
4. The method of claim 3, wherein identifying the at least one
entity includes further includes comparing geographical locations
for each of the entities in the set to geographical information for
a location associated with a computing device of the user.
5. The method of claim 1, further comprising selecting the at least
one entity from a set of entities associated with the task by
determining that the at least one entity is capable of enabling the
user to perform the task.
6. The method of claim 5, wherein the set of entities includes one
or more of business entities or government entities.
7. The method of claim 1, wherein the at least one entity is a
government entity, and the task is one of obtaining a government
license, renewing the government license, obtaining a government
permit, or amending the government permit.
8. The method of claim 1, wherein the at least one entity is a
business entity, and the task is one of a service request, a
cancellation request, or a renewal request.
9. The method of claim 1, wherein formatting the identified
information for performing the task for presentation via the user
interface includes adding the identified information to a task item
in a message list.
10. The method of claim 1, wherein identifying the at least one
entity corresponding to the task includes identifying a time of day
or an amount of time in which the at least one entity is able to
assist in performing the task.
11. The method of claim 10, wherein identifying the time of day or
the amount of time includes evaluating at least one of an opening
time, a closing time, or a time of day when the at least one entity
will stop receiving requests to assist in performing the task.
12. The method of claim 1, wherein the electronic messaging
application is either an email application or an instant messaging
application.
13. A computing device, comprising: one or more processors; and
memory operatively coupled to the one or more processors, the
memory storing one or more programs configured for execution by the
one or more processors, the one or more programs comprising
instructions for a method of providing task assistance in
association with an electronic messaging application, the method
comprising: obtaining an identification of a task to be performed
by a user; identifying at least one entity corresponding to the
task based on a description of the task and information about the
user; based on identifying the at least one entity, identifying
information for performing the task; formatting the identified
information for performing the task for presentation via a user
interface; and outputting, for presentation with the electronic
messaging application via the user interface, the identified
information for performing the task and information about the
identified at least one entity.
14. The computing device of claim 13, wherein obtaining the
identification of the task to be performed includes identifying the
task based on an electronic message object associated with one or
more messages of the electronic messaging application.
15. The computing device of claim 13, wherein identifying the at
least one entity includes evaluating whether each entity of a set
of entities is capable of enabling performance of the task.
16. The computing device of claim 15, wherein identifying the at
least one entity includes further includes comparing geographical
locations for each of the entities in the set to geographical
information for a location associated with a computing device of
the user.
17. The computing device of claim 13, wherein the method further
comprises selecting the at least one entity from a set of entities
associated with the task by determining that the at least one
entity is capable of enabling the user to perform the task.
18. A non-transitory computer readable storage medium storing one
or more programs configured for execution by a computing device
having one or more processors, the one or more programs comprising
instructions for performing a method of providing task assistance
in association with an electronic messaging application, the method
comprising: obtaining an identification of a task to be performed
by a user; identifying at least one entity corresponding to the
task based on a description of the task and information about the
user; based on identifying the at least one entity, identifying
information for performing the task; formatting the identified
information for performing the task for presentation via a user
interface; and outputting, for presentation with the electronic
messaging application via the user interface, the identified
information for performing the task and information about the
identified at least one entity.
19. The non-transitory computer readable storage medium of claim
18, wherein obtaining the identification of the task to be
performed includes identifying the task based on an electronic
message object associated with one or more messages of the
electronic messaging application.
20. The non-transitory computer readable storage medium of claim
18, wherein identifying the at least one entity includes evaluating
whether each entity of a set of entities is capable of enabling
performance of the task.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 16/536,687, filed Aug. 9, 2019, which is a
continuation of U.S. patent application Ser. No. 14/473,564, filed
Aug. 29, 2014 and issued as U.S. Pat. No. 10,423,932 on Sep. 24,
2019, the entire disclosures of which are incorporated herein by
reference.
TECHNICAL FIELD
[0002] The disclosure relates generally to electronic messaging
applications, and more specifically to providing task
assistance.
BACKGROUND
[0003] Electronic messaging applications, such as email, convey
various types of information to a recipient such as messages to and
from various others. Some messages include a task that the
recipient must perform. As such, many messaging applications track
not only messages received by or sent by a recipient but also tasks
that the recipient is to perform. Such tasks may be independent of
messages to and from others, or associated with messages from
others. What are needed in the art are systems and methods for
assisting a recipient with performing such tasks.
SUMMARY
[0004] Disclosed implementations address the above deficiencies and
other problems associated with performing tasks. The disclosed
implementations provide ways to help a recipient perform tasks.
[0005] In accordance with some implementations, a method of task
assistance executes at a computing device having one or more
processors and memory. The memory stores one or more programs
configured for execution by the one or more processors. A
description of a task associated with a user is received. In some
instances the user creates the task. In other instances the task is
inferred, subject to user confirmation, from a message sent to the
user, for instance an E-mail message. Upon receipt of the
description of the task, one or more entities associated with the
task are identified using at least the description of the task and
geographic information about the user. In some instances, an entity
is deemed to be associated with a task when the entity is capable
of performing the task and the entity services such tasks from
users that are at or from the location identified in the
geographical information. Information for performing the task with
at least one respective entity in the one or more entities based
upon an identity of the entity is identified and formatted for use
by the user.
[0006] In some instances, an entity in the one or more entities is
a business or a government entity. In some instances, the task is
cancellation of a subscription or recurring service and the
information for performing the task is a telephone number, uniform
resource locator, or mailing address used by an entity in the one
or more entities to service requests to cancel subscription
requests or requests to cancel a recurring service. In some
instances, the task is a service request and the information for
performing the task is a telephone number or uniform resource
locator used by an entity in the one or more entities to handle the
service request.
[0007] In some embodiments, the method further comprises providing
an identification of a first entity in the one or more entities and
a set of opening and closing times for each day of the week in
which the first entity is available to handle the task.
[0008] In some instances, the method further comprises providing
information on whether or not an entity in the one or more entities
is presently available to perform the task. In some embodiments,
when the entity is available to perform the task, a time of day is
provided when the entity will stop receiving requests to perform
the task.
[0009] In some embodiments, an entity in the one or more entities
is a government entity and the task is obtaining or renewing a
government license or obtaining or amending a government
permit.
[0010] In some embodiments, the identifying one or more entities
associated with the task comprises retrieving non-transient stored
geographical information about the user. In some such embodiments,
the information is stored as a user profile.
[0011] In some instances, the identifying the one or more entities
associated with the task comprises retrieving the geographical
information about the user from a wireless device associated with
the user. In some such instances, the geographical information is a
present location of the user. In other instances, the geographical
information is a geographic position, such as a street address,
that the user has provided for storage in a profile or other form
of record associated with the user.
[0012] In some embodiments, an entity in the one or more entities
is part of a larger organization and the identifying one or more
entities associated with the task comprises resolving which entity
in the larger organization pertains to the task based upon the
geographical information about the user. For instance, in some
embodiments the larger organization is a first government entity
and an entity in the one more entities is a government office for
the first government entity. In one example, the larger
organization a Department of Motor Vehicles and the entity within
the larger organization that is identified for a user is the office
of the Department of Motor Vehicles that is most proximate to the
and geographic information about the user. In another instance, the
larger organization is a business organization and an entity in the
one more entities is a location of an office for the business
organization.
[0013] In some embodiments, the identifying information for
performing the task with the at least one respective entity in the
one or more entities is further based upon the description of the
task. In some embodiments, the task is returning merchandise. In
some embodiments, the method further comprises verifying that a
first entity in the one or more entities is presently available to
service the task and, when the first entity is not presently
available to service the task, the method further comprises
refraining from presenting information regarding the first
entity.
[0014] Another aspect of the present disclosure provides a
computing device comprising one or more processors, memory, and one
or more programs stored in the memory. The one or more programs are
configured for execution by the one or more processors. The one or
more programs comprise instructions for receiving a description of
a task associated with a user. Upon receipt of the description of
the task, one or more entities associated with the task are
identified using at least the description of the task and
geographic information about the user. Information for performing
the task with at least one respective entity in the one or more
entities is identified based upon an identity of the entity. This
information for performing the task is formatted for use by the
user.
[0015] Another aspect of the present disclosure provides a
non-transitory computer readable storage medium storing one or more
programs configured for execution by a computing device having one
or more processors and memory. The one or more programs comprise
instructions for receiving a description of a task associated with
a user. Upon receipt the description of the task, one or more
entities associated with the task are identified using at least the
description of the task and geographic information about the user.
Information for performing the task with at least one respective
entity in the one or more entities is identified based upon an
identity of the entity. This information for performing the task is
formatted for use by the user.
BRIEF DESCRIPTION OF THE DRAWINGS
[0016] For a better understanding of the aforementioned
implementations of the invention as well as additional
implementations thereof, reference should be made to the
Description of Implementations below, in conjunction with the
following drawings in which like reference numerals refer to
corresponding parts throughout the figures.
[0017] FIG. 1 illustrates a context in which some implementations
operate.
[0018] FIG. 2 is a block diagram of a client computing device
according to some implementations.
[0019] FIG. 3 is a block diagram of a server according to some
implementations.
[0020] FIGS. 4A-4E illustrate aspects of a user interface for task
assistance in accordance with some implementations.
[0021] FIGS. 5A-5C provide a flowchart of a process for task
assistance according to some implementations.
[0022] Reference will now be made in detail to implementations,
examples of which are illustrated in the accompanying drawings. In
the following detailed description, numerous specific details are
set forth in order to provide a thorough understanding of the
present invention. However, it will be apparent to one of ordinary
skill in the art that the present invention may be practiced
without these specific details.
DESCRIPTION OF IMPLEMENTATIONS
[0023] FIG. 1 is a block diagram that illustrates the major
components of some implementations. The various client devices 102
(also identified herein as computing devices) and servers 300 in a
server system 110 communicate over one or more networks 108 (such
as the Internet). A client device 102 may be a smart phone, a
tablet computer, a laptop computer, a desktop computer, or other
computing device that has access to a communication network 108 and
can run a messaging application 106. In some implementations, the
messaging application runs within a web browser 104.
[0024] In some implementations, the server system 110 consists of a
single server 300. More commonly, the server system 110 includes a
plurality of servers 300. In some implementations, the servers 300
are connected by an internal communication network of bus 122. The
server system 110 includes one or more web servers 112, which
receive requests from users (e.g., from client devices 102) and
return appropriate information, resources, links, and so on. In
some implementations, the server system 110 includes one or more
application servers 114, which provide various applications, such
as a messaging application 106. The server system 110 typically
includes one or more databases 116, which store information such as
web pages, a user list 118, and various user information 120 (e.g.,
user names and encrypted passwords, user preferences, and so
on).
[0025] FIG. 2 is a block diagram illustrating a client device 102
that a user uses to access a messaging application 106. A client
device is also referred to as a computing device, which may be a
tablet computer, a laptop computer, a smart phone, a desktop
computer, a PDA, or other computing device than can run a messaging
application 106 and has access to a communication network 108. A
client device 102 typically includes one or more processing units
(CPUs) 202 for executing modules, programs, or instructions stored
in memory 214 and thereby performing processing operations; one or
more network or other communications interfaces 204; memory 214;
and one or more communication buses 212 for interconnecting these
components. The communication buses 212 may include circuitry
(sometimes called a chipset) that interconnects and controls
communications between system components. A client device 102
includes a user interface 206 comprising a display device 208 and
one or more input devices or mechanisms 210. In some
implementations, the input device/mechanism includes a keyboard and
a mouse; in some implementations, the input device/mechanism
includes a "soft" keyboard, which is displayed as needed on the
display device 208, enabling a user to "press keys" that appear on
the display 208.
[0026] In some implementations, the memory 214 includes high-speed
random access memory, such as DRAM, SRAM, DDR RAM or other random
access solid state memory devices. In some implementations, memory
214 includes non-volatile memory, such as one or more magnetic disk
storage devices, optical disk storage devices, flash memory
devices, or other non-volatile solid state storage devices. In some
implementations, the memory 214 includes one or more storage
devices remotely located from the CPU(s) 202. The memory 214, or
alternately the non-volatile memory device(s) within memory 214,
comprises a non-transitory computer readable storage medium. In
some implementations, the memory 214, or the computer readable
storage medium of memory 214, stores the following programs,
modules, and data structures, or a subset thereof: [0027] an
operating system 216, which includes procedures for handling
various basic system services and for performing hardware dependent
tasks; [0028] a communications module 218, which is used for
connecting the client device 102 to other computers and devices via
the one or more communication network interfaces 204 (wired or
wireless) and one or more communication networks 108, such as the
Internet, other wide area networks, local area networks,
metropolitan area networks, and so on; [0029] a display module 220,
which receives input from the one or more input devices 210, and
generates user interface elements for display on the display device
208; [0030] a web browser 104, which enables a user to communicate
over a network 108 (such as the Internet) with remote computers or
devices; [0031] a messaging application 106, which enables the user
to send and receive electronic messages. In some implementations,
the messaging application is an email application. In some
implementations, the messaging application is an instant messaging
application. In some implementations, the messaging application 106
runs within the web browser 104 as illustrated in FIG. 1. In some
implementations, the messaging application 106 runs independently
of a web browser 104 (e.g., a desktop application). An example
messaging application is illustrated below in FIGS. 4A-4E; and
[0032] application data 222, which is used by the messaging
application 106. The application data comprises messages 224 (e.g.,
email messages or instant messages) as well as tasks 226, and
information 228 for completing tasks. In some embodiments a task
226 is associated with a message 224. In some embodiments a task
226 is independent of all messages. The application data 222 may
include configuration data 230, such as user preferences, user
history, geographic information about the user, or the state of
configuration options.
[0033] Each of the above identified executable modules,
applications, or sets of procedures may be stored in one or more of
the previously mentioned memory devices and corresponds to a set of
instructions for performing a function described above. The above
identified modules or programs (i.e., sets of instructions) need
not be implemented as separate software programs, procedures, or
modules, and thus various subsets of these modules may be combined
or otherwise re-arranged in various implementations. In some
implementations, the memory 214 may store a subset of the modules
and data structures identified above. Furthermore, the memory 214
may store additional modules or data structures not described
above.
[0034] Although FIG. 2 shows a client device 102, FIG. 2 is
intended more as a functional description of the various features
that may be present rather than as a structural schematic of the
implementations described herein. In practice, and as recognized by
those of ordinary skill in the art, items shown separately could be
combined and some items could be separated.
[0035] FIG. 3 is a block diagram illustrating a server 300 that may
be used in a server system 110. A typical server system includes
many individual servers 300, which may be hundreds or thousands. A
server 300 typically includes one or more processing units (CPUs)
302 for executing modules, programs, or instructions stored in the
memory 314 and thereby performing processing operations; one or
more network or other communications interfaces 304; memory 314;
and one or more communication buses 312 for interconnecting these
components. The communication buses 312 may include circuitry
(sometimes called a chipset) that interconnects and controls
communications between system components. In some implementations,
a server 300 includes a user interface 306, which may include a
display device 308 and one or more input devices 310, such as a
keyboard and a mouse.
[0036] In some implementations, the memory 314 includes high-speed
random access memory, such as DRAM, SRAM, DDR RAM or other random
access solid state memory devices. In some implementations, the
memory 314 includes non-volatile memory, such as one or more
magnetic disk storage devices, optical disk storage devices, flash
memory devices, or other non-volatile solid state storage devices.
In some implementations, the memory 314 includes one or more
storage devices remotely located from the CPU(s) 302. The memory
314, or alternately the non-volatile memory device(s) within memory
314, comprises a non-transitory computer readable storage medium.
In some implementations, the memory 314, or the computer readable
storage medium of memory 314, stores the following programs,
modules, and data structures, or a subset thereof: [0037] an
operating system 316, which includes procedures for handling
various basic system services and for performing hardware dependent
tasks; [0038] a communications module 318, which is used for
connecting the server 300 to other computers via the one or more
communication network interfaces 304 (wired or wireless), an
internal network or bus 122, or other communication networks 108,
such as the Internet, other wide area networks, local area
networks, metropolitan area networks, and so on; [0039] an optional
display module 320, which receives input from one or more input
devices 310, and generates user interface elements for display on a
display device 308; [0040] one or more web servers 112, which
receive requests from client device 102, and returns responsive web
pages, resources, or links. In some implementations, each request
is logged in the database 116; [0041] one or more application
servers 114, which provide various applications (such as an email
or other messaging application) to client devices 102. In some
instances, applications are provided as a set of web pages, which
are delivered to client devices 102 and displayed in a web browser
104. The web pages are delivered as needed or requested. In some
instances, an application is delivered to a client device 102 as a
download, which is installed and run from the client device 102
outside of a web browser 104; [0042] one or more databases 116,
which store various data used by the modules or programs identified
above. In some implementations, the database 116 includes a list of
authorized users, which may include user names, encrypted
passwords, and other relevant information about each user. The
database 116 also stores user specific data 120 that is used by one
or more of the applications provided by the application server. For
example, some implementations store the electronic messages 224 for
each user. As another example, some implementations store
geographic information about a user.
[0043] Each of the above identified elements in FIG. 3 may be
stored in one or more of the previously mentioned memory devices.
Each executable program, module, or procedure corresponds to a set
of instructions for performing a function described above. The
above identified modules or programs (i.e., sets of instructions)
need not be implemented as separate software programs, procedures
or modules, and thus various subsets of these modules may be
combined or otherwise re-arranged in various implementations. In
some implementations, the memory 314 may store a subset of the
modules and data structures identified above. Furthermore, the
memory 314 may store additional modules or data structures not
described above.
[0044] Although FIG. 3 illustrates a server 300, FIG. 3 is intended
more as functional illustration of the various features that may be
present in a set of one or more servers rather than as a structural
schematic of the implementations described herein. In practice, and
as recognized by those of ordinary skill in the art, items shown
separately could be combined and some items could be separated. The
actual number of servers used to implement these features, and how
features are allocated among them, will vary from one
implementation to another, and may depend in part on the amount of
data traffic that the system must handle during peak usage periods
as well as during average usage periods.
[0045] As illustrated in FIGS. 2 and 3, the functionality for a
messaging application may be shared between a client device 102 and
a server system 110. In some implementations, after the messaging
application is installed on a client device 102, the majority of
the subsequent processing occurs on the client device. In other
implementations, the majority of the processing and data storage
occurs at a server 300, and the client device 102 uses a web
browser 104 to view and interact with the data. One of skill in the
art recognizes that various allocations of functionality between
the client device 102 and the server system 110 are possible, and
some implementations support multiple configurations (e.g., based
on user selection).
[0046] FIG. 4A illustrates features of a messaging application that
supports task assistance in accordance with some implementations.
FIG. 4A illustrates an electronic message list 402, which may be
displayed as part of an electronic messaging application (e.g., an
email application). In this example, each row in the list
represents a separate message object (e.g., messages 404, 408, and
414-426), a separate message cluster (e.g., 406, 410), or a task
412. The message objects all are intended for a user associated
with the electronic message list 402. In some embodiments,
individual messages (e.g., messages 404, 408, and 414-426) are
message threads, message conversations, or messages that are
addressed to one or more users, including the user uniquely
associated with the electronic message list 402.
[0047] In FIG. 4A, the electronic message list 402 is, in
particular, shown to comprise at least two message clusters,
cluster 406 and cluster 410. Cluster 406 is a group of electronic
messages having a collective association, namely promotional
material (e.g., advertisements for retail sales, newsletters from
stores). As can be seen in FIG. 4A, cluster 406 comprises nine new
electronic messages, and cluster 410 comprises 1 new electronic
message. In some embodiments, a new electronic message refers to a
message that has not been viewed, opened, acknowledged or read by
the user of the messaging application. Message clusters are
disclosed further in U.S. patent application Ser. No. 14/145,005,
entitled "Systems and Methods for Throttling Display of Electronic
Messages," filed Dec. 31, 2013, and U.S. patent application Ser.
No. 14/139,205, entitled "Systems and Methods for Clustering
Electronic Messages," filed Dec. 23, 2013, each of which is hereby
incorporated by reference herein in its entirety.
[0048] Continuing to refer to FIG. 4A, task assistance is disclosed
in more detail. A description of a task 428 associated with a user
is received. In some instances the user creates the description of
the task 428 by direct input (e.g. through a keypad interface). In
other instances, the task is inferred from an electronic message
object in the electronic message list 402. Ways to infer a task
from an electronic message object are disclosed in U.S. patent
application Ser. No. 14/161,368, entitled "Identifying Tasks in
Messages," filed Jan. 22, 2014, which is hereby incorporated by
reference herein in its entirety.
[0049] Upon receipt of the description of the task (e.g., directly
after the user provide the task), one or more entities associated
with the task are identified using at least the description of the
task and geographic information about the user. In some instances,
an entity is deemed to be associated with a task when the entity is
capable of performing the task and the entity services such tasks
from users that are at or from the location identified in the
geographical information. Information 430 for performing the task
with at least one respective entity in the one or more entities
based upon an identity of the entity is identified and formatted
for use by the user. In the example illustrated in FIG. 4A, the
description of the task "renew drivers license" coupled with
geographic information about the user ("e.g., the user's home
address or home GPS coordinates") is used to determine the correct
department of motor vehicles website to suggest to the user. In one
example, the user's geographic information identifies Daly City,
Calif. and the Daly City office of the California Department of
Motor Vehicles is identified as the information 430 for performing
the task of renewing a driver's license. In this example, the URL
for the Daly City office of the California Department of Motor
Vehicles is formatted for use by the user. In another example, the
user's geographic information identifies Daly City, Calif. and the
California URL for the California Department of Motor Vehicles is
identified as the information 430 for performing the task of
renewing a driver's license. In this example, the California URL
for the California Department of Motor Vehicles is formatted for
use by the user.
[0050] In some instances, an entity in the one or more entities is
a business or a government entity. In some instances, the task is
cancellation of a subscription or recurring service. For example,
referring to FIG. 4B, the task 434 is cancelling a cable
subscription and the information 436 for performing the task is a
uniform resource locator for cancelling the cable subscription. In
some instances, the information 438 for performing the task 436
using two or more entities in the identified one or more entities
is provided, as illustrated in FIG. 4C. While FIGS. 4A through 4C
provide the example of uniform resource locators that lead to
information for performing the task, mailing addresses, phone
numbers, social media handles, or any other form of method of
communication information to perform the task can be provided. In
some instances, the task is a service request (e.g., "call
plumber") and the information for performing the task is a
telephone number or uniform resource locator used by an entity in
the one or more entities to handle the service request.
[0051] Referring to FIG. 4D, in some embodiments, the method
further comprises providing an identification 440 of a first entity
in the one or more entities and a set of opening and closing times
442 for each day of the week in which the first entity is available
to handle the task.
[0052] Referring to FIG. 4E, in some instances, the method further
comprises providing information on whether or not an entity in the
one or more entities is presently available to perform the task. In
some embodiments, when the entity is available to perform the task,
a time of day is provided when the entity will stop receiving
requests to perform the task 444 or an amount of time 446 before
the entity will stop receiving requests to perform the task is
provided.
[0053] In some embodiments, an entity in the one or more entities
is a government entity and the task is obtaining or renewing a
government license or obtaining or amending a government permit.
Examples of government licenses and permits include, but are not
limited to drivers licenses, building permits, disabled parking
permits, gun permits, hunting permits, environmental permits,
fishing license, a liquor license, and a nightclub permit, to name
a few nonlimiting examples.
[0054] In some embodiments, the identifying one or more entities
associated with the task comprises retrieving non-transient stored
geographical information about the user. In some such embodiments,
the information is stored as a user profile. For example, referring
to FIG. 3, in some embodiments the non-transient stored
geographical information about the user is stored in a user profile
340 uniquely associated with the user.
[0055] In some instances, the identifying the one or more entities
associated with the task comprises retrieving the geographical
information about the user from a wireless device associated with
the user. In some such instances, the geographical information is a
present location of the user. In other instances, the geographical
information is a geographic position, such as a street address,
that the user has provided for storage in a profile (e.g., user
profile 340 of FIG. 3) or other form of record associated with the
user.
[0056] In some embodiments, the identifying information for
performing the task with the at least one respective entity in the
one or more entities is further based upon the description of the
task. For example, if the description of the task is "repair
automobile", the one or more entities provided will be those that
wash automobiles. Alternatively, if the description of the task is
"wash car", the one or more entities provided will be those that
wash cars. Alternatively still, if the description of the task is
"donate car", the one or more entities provided will be those that
accept automobile donations.
[0057] Referring to FIG. 2, a display device 208 is inherently
limited in size. Accordingly, the number of message objects
displayed in the message list 402 is necessarily limited. Scrolling
may be necessary for a user to get to a desired message. If the
number of messages in the message list is small enough, all of the
messages may be able to be displayed.
[0058] FIGS. 5A-5C provide a flowchart of a process 500, performed
by a computing device, for providing task management (502). The
method is performed (504) at a computing device 102 and/or 110
having one or more processors and memory. The memory stores (504)
one or more programs configured for execution by the one or more
processors.
[0059] A description of a task associated with a user is received.
Upon receipt of the description of the task, one or more entities
associated with the task are identified using at least the
description of the task and geographic information about the user
(508). Further, information is identified for performing the task
with at least one respective entity in the one or more entities
based upon an identity of the entity. In some implementations, an
entity in the one or more entities is a business or a government
entity (512).
[0060] In some implementations, the task is cancellation of a
subscription or recurring service and the information for
performing the task is a telephone number, uniform resource
locator, or mailing address used by an entity in the one or more
entities to service requests to cancel subscription requests or
requests to cancel a recurring service (514). In some
implementations, the task is a service request and the information
for performing the task is a telephone number or uniform resource
locator used by an entity in the one or more entities to handle the
service request (516). In some implementations, the method further
comprises providing an identification of a first entity in the one
or more entities and a set of opening and closing times for each
day of the week in which the first entity is available to handle
the task (518).
[0061] In some implementations, information is provided on whether
or not an entity in the one or more entities is presently available
to perform the task and, when the entity is available to perform
the task, a time of day when the entity will stop receiving
requests to perform the task (520). In some implementations, an
entity in the one or more entities is a government entity and the
task is obtaining or renewing a government license or obtaining or
amending a government permit (522). In some implementations, the
identifying one or more entities associated with the task comprises
retrieving non-transient stored geographical information about the
user (524). In some implementations, the identifying one or more
entities associated with the task comprises retrieving the
geographical information about the user from a wireless device
associated with the user (526).
[0062] In some implementations, an entity in the one or more
entities is part of a larger organization and the identifying one
or more entities associated with the task comprises resolving which
entity in the larger organization pertains to the task based upon
the geographical information about the user (528). In some
implementations, the larger organization is a first government
entity and an entity in the one more entities is a government
office for the first government entity (530). In some
implementations, the larger organization is a business organization
and an entity in the one more entities is a location of an office
for the business organization (532).
[0063] In some implementations, the identifying information for
performing the task with the at least one respective entity in the
one or more entities is further based upon the description of the
task (534). In some implementations, the task is returning
merchandise (536). The identified information is formatted for use
by the user (538). For example, in some embodiments, the identified
information is formatted for display on a client device 102.
[0064] The terminology used in the description of the invention
herein is for the purpose of describing particular implementations
only and is not intended to be limiting of the invention. As used
in the description of the invention and the appended claims, the
singular forms "a," "an," and "the" are intended to include the
plural forms as well, unless the context clearly indicates
otherwise. It will also be understood that the term "and/or" as
used herein refers to and encompasses any and all possible
combinations of one or more of the associated listed items. It will
be further understood that the terms "comprises" and/or
"comprising," when used in this specification, specify the presence
of stated features, steps, operations, elements, and/or components,
but do not preclude the presence or addition of one or more other
features, steps, operations, elements, components, and/or groups
thereof.
[0065] The foregoing description, for purpose of explanation, has
been described with reference to specific implementations. However,
the illustrative discussions above are not intended to be
exhaustive or to limit the invention to the precise forms
disclosed. Many modifications and variations are possible in view
of the above teachings. The implementations described herein were
chosen and described in order to best explain the principles of the
invention and its practical applications, to thereby enable others
skilled in the art to best utilize the invention and various
implementations with various modifications as are suited to the
particular use contemplated.
* * * * *