U.S. patent application number 13/178959 was filed with the patent office on 2012-03-15 for method and system for accessing wireless account information.
This patent application is currently assigned to GOTV NETWORKS, INC.. Invention is credited to Pierre CARION.
Application Number | 20120066119 13/178959 |
Document ID | / |
Family ID | 44245627 |
Filed Date | 2012-03-15 |
United States Patent
Application |
20120066119 |
Kind Code |
A1 |
CARION; Pierre |
March 15, 2012 |
METHOD AND SYSTEM FOR ACCESSING WIRELESS ACCOUNT INFORMATION
Abstract
A method for managing wireless account information. A list of
applications is presented via a web interface on a computing
device. The applications are operable to run on a wireless handheld
device and a plurality of billing options are presented. In
response to receiving a selection of an application, a wireless
account is updated via a link between a web account and a wireless
account according to the selected application, such that the
selected application is available when a wireless account is
accessed via a wireless handheld device.
Inventors: |
CARION; Pierre; (La Jolla,
CA) |
Assignee: |
GOTV NETWORKS, INC.
Sherman Oaks
CA
|
Family ID: |
44245627 |
Appl. No.: |
13/178959 |
Filed: |
July 8, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11977186 |
Oct 23, 2007 |
7979350 |
|
|
13178959 |
|
|
|
|
Current U.S.
Class: |
705/40 |
Current CPC
Class: |
H04M 15/705 20130101;
H04M 15/68 20130101; H04M 15/725 20130101; H04M 15/51 20130101;
H04W 4/24 20130101; H04M 15/721 20130101; H04M 2215/018 20130101;
H04W 4/50 20180201; G06Q 20/123 20130101; H04M 15/71 20130101; G06Q
20/322 20130101; H04M 15/72 20130101; H04M 15/00 20130101; H04M
15/70 20130101 |
Class at
Publication: |
705/40 |
International
Class: |
G06Q 20/22 20120101
G06Q020/22 |
Claims
1. A method for managing wireless account information, said method
comprising: presenting a list of applications via a web interface
on a computing device, wherein said applications are operable to
run on a wireless handheld device; receiving a selection of an
application from said computing device; presenting a plurality of
billing options; updating a wireless account via a link between a
web account and a wireless account according to said selection of
an application, such that said application is available when said
wireless account is accessed via a wireless handheld device.
2. A method as described in claim 1 wherein said wireless account
is independent of a wireless carrier account.
3. A method as described in claim 1 wherein said web interface is
independent of a wireless carrier website.
4. A method as described in claim 1 further comprising: presenting
an interactive version of a wireless application.
5. A method as described in claim 1 further comprising:
establishing a secure connection between a client and a server;
wherein said client is a computing system.
6. A method as described in claim 1 further comprising: setting an
expiration date corresponding to said application on said second
account, wherein said expiration date causes a wireless device to
display a message indicating access to an application has
expired.
7. A method as described in claim 1 further comprising: presenting
application customization options.
8. A computer readable media comprising instructions therein that
when executed by a processor to implement a method of account
management, said method comprising: receiving a first message to
create an account; sending a second message with an identifier to a
wireless handheld device; receiving a third message comprising said
identifier; creating a web account; and establishing a link between
said web account and a wireless applications account.
9. A method as described in claim 8 wherein said second message is
an SMS message.
10. A method as described in claim 8 wherein said second message
comprises a link which when accessed via said wireless device,
identifies the wireless device.
11. A method as described in claim 8 wherein login information is
stored on a computing device for return access.
12. A method as described in claim 8 wherein said identifier
comprises an identification code.
13. A method as described in claim 8 further comprising: presenting
customization options associated with said wireless applications
account.
14. A system for accessing information for wireless applications:
an account management component for managing web accounts and the
associated authentication information; a billing component for
managing billing and purchasing of applications; an account setup
component for creating a web account and associating the account
with a corresponding wireless device account; and a wireless device
account interface for accessing wireless device account
information.
15. A system as described in claim 14 further comprising: a sending
component for sending a purchased application to a different
account.
16. A system as described in claim 15 wherein said sending
component sends a notification message of a purchased
application.
17. A system as described in claim 14 wherein said customization
component allows selection of one or more application objects.
18. A system as described in claim 14 wherein said application
objects are RSS feeds.
19. A system as described in claim 14 wherein said application
objects are icons.
20. A system as described in claim 14 further comprising: a
customization component for customizing information related to said
wireless device account.
Description
TECHNICAL FIELD
[0001] Embodiments of the present invention relate to the field of
wireless communication systems. More particularly, embodiments of
the present invention relate to a method and system for accessing
wireless account information.
BACKGROUND ART
[0002] The widespread increase in the number of wireless devices
has increased the demand and the corresponding opportunity for
businesses to provide applications, content, and services for
various wireless devices.
[0003] The limited abilities of wireless devices further complicate
otherwise simple tasks. Unfortunately, most wireless devices are
plagued by small screens and small or limited keypads which make it
cumbersome and difficult to type information. Users often identify
themselves to a resource via a username and password, however on a
wireless device the entry of a username and password can be a
lengthy process. Further, purchases, such as software or
applications, are likewise complicated by the limited interfaces of
wireless devices. For example, if a user wishes to purchase an
application, it can quickly become time consuming and frustrating
for a user to enter billing information such as a credit card and
billing address via a 10 digit keypad of most cellular phones.
Moreover, some wireless devices lack the resources necessary to
create secure connections needed for safe and secure purchases.
[0004] Businesses further require an efficient and effective way to
bill customers for the services or products provided. Often times,
each wireless carrier has a proprietary billing platform which
requires developers to tailor the software billing system to each
carrier. Any changes to the carriers billing system may necessitate
substantial changes by developers and thus more work for
developers. Furthermore, the various billing platforms may have
different abilities with regard to frequency of billing and other
billing attributes. For example, a billing platform may not support
recurring billing. Such a lack of support may run counter to a
software vendor's business model. Thus, efficient and effective
selling of wireless applications requires that both user and
software developers be able to purchase and charge customers
accordingly.
[0005] Thus, a need exists for a solution that facilitates the easy
purchase of services and software for wireless devices and allows
flexibility in the type of billing. What is further needed is an
interface for users to easily and efficiently initiate purchases of
products and services for the wireless devices without being
required to use the limited interfaces of wireless devices.
SUMMARY
[0006] Accordingly, a need has arisen to enable software vendors to
provide a convenient way for users to purchase applications,
services, and content and thereby allowing users to purchase
applications without having to use the limited interfaces of the
wireless device. Moreover, a need has arisen to have flexibility in
billing users and relieve software vendors of tailoring billing
systems to each carrier or service provider. It will become
apparent to those skilled in the art after reading the detailed
description of the present invention that the embodiments of the
present invention satisfy the above mentioned needs.
[0007] According to one embodiment, the present invention is
implemented as a method for managing wireless account information.
The method includes presenting, via a web interface on a computing
device, a list of applications which are operable to run on a
wireless handheld device. A selection of an application is then
received from the computing device and a plurality of billing
options may then be presented. In response to receiving the
application selection and billing option selection, a wireless
account is updated via a link between a web account and a wireless
account such that the selected application is available when the
wireless account is accessed via a wireless handheld device.
[0008] In another embodiment of the present invention, the present
invention is implemented as a method for account management. The
method includes receiving a first message to create an account. In
response to the first message, a second message is sent to a
wireless device including an identifier. Upon receiving a third
message including the identifier a web account is created. A link
may then be established between the web account and a wireless
applications account.
[0009] In another embodiment, the present invention is implemented
as system for accessing information for wireless applications. The
system includes an account management component for managing web
accounts and the associated authentication information. The web
accounts are created and associated with a corresponding wireless
device account by an account setup component. The wireless device
account information may be accessed through a wireless device
account interface component. The system further includes a billing
component for managing billing and thereby purchasing of
applications.
[0010] In this manner, embodiments of the present invention relieve
users of having to use the limited interfaces of wireless devices
to purchase applications, services and content because a web
interface allows use of a computer to conduct the transactions in
ways familiar to users. Moreover, embodiments of the present
invention allow billing to be conducted independent of the
carrier's billing platform and thus, in a flexible manner. Thus,
software vendors and developers are relieved of having to tailor
billing systems to each carriers billing platform.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1 shows an exemplary communication system in accordance
with one embodiment of the present invention including wireless
clients, a remote server, and a web client.
[0012] FIG. 2 shows an exemplary device block diagram in accordance
with one embodiment of the present invention.
[0013] FIG. 3 shows an exemplary web server block diagram in
accordance with one embodiment of the present invention.
[0014] FIG. 4 shows an exemplary computer controlled flow diagram
for managing wireless account information in accordance with one
embodiment of the present invention.
[0015] FIG. 5 shows an exemplary computer controlled flow diagram
of a server implemented method of account management in accordance
with one embodiment of the present invention.
DETAILED DESCRIPTION
[0016] Reference will now be made in detail to embodiments of the
present invention, examples of which are illustrated in the
accompanying drawings. While the invention will be described in
conjunction with these embodiments, it will be understood that they
are not intended to limit the invention to these embodiments. On
the contrary, the invention is intended to cover alternative,
modifications and equivalents, which may be included within the
spirit and scope of the invention as defined by the appended
claims. Furthermore, in the following detailed description of the
present invention, numerous specific details are set forth in order
to provide a thorough understanding of the present invention.
However, it will be evident to one ordinary skill in the art that
the present invention may be practiced without these specific
details. In other instances, well known methods, procedures,
components, and circuits have not been described in detail as not
to unnecessarily obscure aspects of the invention.
Notation and Nomenclature
[0017] Some portions of the detailed descriptions which follow are
presented in terms of procedures, steps, logic blocks, processing,
and other symbolic representations of operations on data bits that
can be performed on computer memory. These descriptions and
representations are the means used by those skilled in the art to
most effectively convey the substance of their work to others
skilled in the art. A procedure, computer executed step, logic
block, process, etc., is here, and generally, conceived to be a
self-consistent sequence of steps or instructions leading to a
desired result. The steps are those requiring physical
manipulations of physical quantities.
[0018] Usually, though not necessarily, these quantities take the
form of electrical or magnetic signals capable of being stored,
transferred, combined, compared, and otherwise manipulated in a
computer system. It has proven convenient at times principally for
reasons of common usage, to refer to these signals as bits, values,
elements, symbols, characters, terms, numbers, or the like.
[0019] It should be borne in mind, however, that all of these and
similar terms are to be associated with the appropriate physical
quantities and are merely convenient labels applied to these
quantities. Unless specifically stated otherwise as apparent from
following discussions, it is appreciated that throughout the
present invention, discussions utilizing terms such as "processing"
or "creating" or "transferring" or "executing" or "determining" or
"instructing" or "issuing" or "halting" or "clearing" or
"accessing" or "aggregating" or "obtaining" or "selecting" or
"initiating" or "receiving" or "analyzing" or "generating" or
"constructing" or "outputting" or "collecting" or "monitoring" or
"outputting" or "storing" or "sending" or "receiving" or
"identifying" or using" or "rendering" or "translating" or
"providing" or the like, refer to the action and processes of a
computer system, or similar electronic computing device, that
manipulates and transforms data represented as physical
(electronic) quantities within the computer system's registers and
memories into other data similarly represented as physical
quantities within the computer system memories or registers or
other such information storage, transmission or display
devices.
[0020] The increase in the number of wireless devices has led to a
demand for efficient and easy way to sell users wireless
applications, content, and services. However, conventionally
billing methods require software billing systems to be tailored to
the wireless carrier or service provider's billing platform.
Embodiments of the present invention relieve software vendors from
tailoring their billing systems to each specific carrier and allow
software vendors to provide an easy way for users to purchase
applications, content, and services for their wireless devices.
Moreover, embodiments of the present invention provide centralized
location for managing and purchasing of applications for wireless
devices. Thus, users are able to purchase and access applications
without having to use the limited interfaces of wireless
devices.
[0021] FIG. 1 shows an exemplary communication system in accordance
with one embodiment of the present invention including wireless
clients, a remote server, and a web client. It is appreciated that
the remote server and web server may execute on the same physical
computing system. In one embodiment, one or more wireless devices
110 are coupled to a server 130 through a network 120. The wireless
devices 110 may be any mobile wireless electronic device, e.g., a
cellular phone, a personal digital assistant (PDA), a pager, a
smart phone, a BlackBerry, a laptop and the like. It is appreciated
that the wireless device described herein is exemplary and is not
intended to limit the scope of the present invention. Network 120
includes wireless communication capability.
[0022] According to an embodiment of the present invention, the
remote server 130 hosts wireless accounts 135 which may be a
plurality of wireless: applications, content, and/or service
accounts. The accounts may include information such as the type(s)
of wireless device(s), billing information (e.g., payment plan,
payment method, expiration date), and applications associated with
the account. Remote server 130 may run generic applications which
are then customized for display on wireless devices 110.
[0023] In one embodiment, web server 140 executes a web server
application which allows web server 140 to communicate with various
web clients (e.g., web client 150) running web browsers and the
like. Web client 150 may be any computing system (e.g., desktop,
laptop, or the like) capable of running or executing a web client
such as a web browser for communicating with web server 140.
[0024] According to one embodiment of the present invention, web
server 140 provides an interface for web clients to create and
access web accounts 145 and further provides a link between web
accounts 145 and wireless accounts 135. This link allows user to
change and access properties of a wireless account via a web
client. Advantageously, the ability to make changes to a wireless
account allows the selection and purchase of applications and
corresponding billing information to be entered quickly and
conveniently via the web client (e.g., desktop or laptop) as
opposed to via the wireless devices 110. For example, entering a
billing address and credit card number via a wireless device can be
quite time consuming. Thus, embodiments of the present invention
harness the power of the internet to allow users to quickly and
efficiently manage their wireless applications/content
accounts.
[0025] System 100 further allows a consumer's applications account
(e.g., wireless accounts 135) to be independent of a carrier or
service provider. For example, if a user changes wireless carriers,
the new wireless device may be added to the current wireless
applications account (e.g., wireless accounts 135) and thereby
allow the user to keep using the purchased wireless applications
and any associated customizations without requiring changes or
interruption to application access. In another embodiment, system
100 may further be integrated with a service provider's (e.g.,
wireless carrier) website. For example, a wireless carrier may
include system 100 within the carrier's website to sell
applications to users.
[0026] FIG. 2 shows an exemplary device block diagram in accordance
with one embodiment of the present invention. Computing system
environment 200 may implement the process for establishing and
linking web accounts and wireless accounts as shown in FIGS. 5 and
6 and includes a bus 216 or other communication mechanism for
communicating information, and a processor 202 coupled with bus 216
for processing information.
[0027] With reference to FIG. 2, an exemplary system for
implementing embodiments includes a general purpose computing
system environment, such as computing system environment 200.
Computing system environment 200 may include, but is not limited
to, servers. In its most basic configuration, computing system
environment 200 typically includes at least one processing unit 202
and memory 204. Depending on the exact configuration and type of
computing system environment, memory 204 may be volatile (such as
RAM), non-volatile (such as ROM, flash memory, etc.) or some
combination of the two. System memory 204 may include, among other
things, a web server application. Computing system environment 200
may further include additional storage media as illustrated in FIG.
2 by non-removable storage 206 and removable storage 208. Computer
storage media includes volatile and nonvolatile, removable and
non-removable media implemented in any method or technology for
storage of information such as computer readable instructions, data
structures, program modules or other data.
[0028] Computing system environment 200 may also contain
communications connection(s) 210 that allow it to communicate with
other devices. Communications connection(s) 210 is an example of
communication media. Communication media typically embodies
computer readable instructions, data structures, program modules or
other data in a modulated data signal such as a carrier wave or
other transport mechanism and includes any information delivery
media. The term "modulated data signal" means a signal that has one
or more of its characteristics set or changed in such a manner as
to encode information in the signal. By way of example, and not
limitation, communication media includes wired media such as a
wired network or direct-wired connection, and wireless media such
as acoustic, RF, infrared and other wireless media. The term
computer readable media as used herein includes both storage media
and communication media.
[0029] Communications connection(s) 210 may allow computing system
environment 200 to communication over various networks types
including, but not limited to, Bluetooth, Ethernet, Wi-fi, Infrared
Data Association (IrDA), Local area networks (LAN), Wireless Local
area networks (WLAN), wide area networks (WAN) such as the
internet, serial, and universal serial bus (USB). It is appreciated
the various network types that communication connection(s) 210
connect to may run a plurality of network protocols including, but
not limited to, transmission control protocol (TCP), internet
protocol (IP), and hypertext transfer protocol (HTTP).
[0030] The term "computer-readable medium" as used herein refers to
any medium that participates in providing instructions to processor
202 for execution. Such a medium may take many forms, including but
not limited to, non-volatile media, volatile media, and
transmission media. Non-volatile media includes, for example,
optical or magnetic disks or the like. Volatile media includes
dynamic memory and the like.
[0031] The claimed subject matter is described in terms of these
example environments. Description in these terms is provided for
convenience only. It is not intended that the invention be limited
to application in this example environment. In fact, after reading
the following description, it will become apparent to a person
skilled in the relevant art how to implement the claimed subject
matter in alternative embodiments.
[0032] FIG. 3 illustrates example components used by various
embodiments of the present technology for managing accounts. System
300 includes components or modules that, in various embodiments,
are carried out by a processor under the control of
computer-readable and computer-executable instructions. The
computer-readable and computer-executable instructions reside, for
example, in data storage features such as computer memory 204,
removable storage 208, and/or non-removable storage 206 of FIG. 2.
The computer-readable and computer-executable instructions are used
to control or operate in conjunction with, for example, processing
unit 202 of FIG. 2. It should be appreciated that the
aforementioned components of system 300 can be implemented in
hardware or software or in a combination of both. Although specific
components are disclosed in system 300 such components are
examples. That is, embodiments are well suited to having various
other components or variations of the components recited in system
300. It is appreciated that the components in system 300 may
operate with other components than those presented, and that not
all of the components of system 300 may be required to achieve the
goals of system 300.
[0033] FIG. 3 shows an exemplary web server block diagram in
accordance with one embodiment of the present invention. System 300
may implement a process for accessing information related to
wireless applications. In one embodiment, modules or components of
system 300 may be executed by a web server (e.g., web server 140).
It is appreciated that system 300 may be executed on a system
independent of a carrier or service provider. System 300 may also
be integrated into the offerings of a wireless service provider.
Thus, system 300 may allow carrier independent purchasing and
wireless application accounts so that a user may access his or her
wireless applications via different phones and service providers.
System 300 includes account manager 302, billing component 304,
account setup 306, customization component 308, wireless device
account interface 310, and sending component 312.
[0034] Account manager 302 facilitates management of web accounts
and the associated authentication information. Account manager 302
presents an authentication interface (e.g., username and password
prompt or page) for access to web accounts. Account manager 302 may
act similar to a portal in providing a plurality of options such as
a section for purchasing applications, services, and content as
well as managing account information such as billing and
authentication information. Account manager 302 may further allow
users to apply customizations to the web interface such as skins or
custom graphical user interface objects (e.g., icons and colors)
and layouts.
[0035] Billing Component 304 manages billing and purchasing of
applications. Billing component 304 may complete payment collection
from a user or subscriber. For example, the billing component may
carry out the charging of a customer's credit or debit card. It is
appreciated that billing component 304 may accept payment in the
various forms that various Internet e-commerce sites allow. In
another embodiment, billing component 304 may also support charging
a user's service provider account where possible.
[0036] Additionally, billing component 304 allows the purchase of
wireless applications and/or associated content via a wide variety
of billing options. For example, purchase options may include a
number of use trial (e.g., use only three times), one day trial,
one month, several month subscription, or recurring
subscription.
[0037] Billing component 304 may further determine the expiration
time and/or date of an application purchase in the wireless
account. Upon attempting to access an expired application, the
wireless device may display a message informing the user that the
current application is expired and he/she may update their
subscription/access to the application via a web interface as
describe herein. It is appreciated that the wireless device may
allow the user to purchase renewed or continued access via the
wireless device.
[0038] Account setup component 306 facilitates creating a web
account and wireless accounts and associating the web accounts with
a corresponding wireless device account. Account setup component
306 may perform a process (e.g., process 500) as described herein
for creating a web account and verifying or confirming
communication with the wireless device (e.g., sending a message
with an identifier or identification information).
[0039] Account setup component 306 may also receive and store login
information for use later by account manager 302. Account setup
component 306 may further store information with a web client to
allow quick return access upon the revisiting of a user. For
example, upon creation of an account, account setup component 306
may facilitate the creation of a cookie on a web client which can
be later used to verify the client was previously
authenticated.
[0040] In addition, account setup component 306 may present various
advertisements including advertisements for wireless applications,
services, and associated content. It is appreciated that such
advertising is well suited for presentation via a web
interface.
[0041] Customization component 308 allows for customizing
information related to the wireless device account. Customization
308 may allow selection of one or more application objects (e.g.,
RSS feeds, location information, information components or modules
such as a sports module, user information, etc.) and visual objects
(e.g., icons, skins, and the like) to be added to an application.
For example, a user may be able to select several RSS (Really
Simple Syndication) feeds for viewing in a news application on a
cellular telephone. It is appreciated that selecting and otherwise
entering RSS feed information (e.g., URLs) could be cumbersome and
time consuming to enter via a wireless device (e.g., cellular
telephone).
[0042] Similarly, customization component 308 may facilitate the
selection of bookmarks, contact or buddy lists, sports teams, and
email login information. Thus, customization component 308 allows a
user to quickly and easy add information via the powerful web
interface of a web client and avoid the complications of doing so
via a wireless device. It is appreciated that some or all functions
available via customization component 308 may be accessed via a
wireless device (e.g., cellular telephone).
[0043] Wireless device account interface 310 facilitates access to
wireless device account information. Wireless device account
interface 310 may further facilitate the modification of wireless
device accounts stored on a remote server (e.g., server 130) or
accounts stored locally on a server. It is appreciated that
wireless device account interface 310 may update wireless device
accounts in a plurality of ways including, but not limited to,
application programming interfaces (APIs) or database access. More
specifically, wireless account interface 310 may update the
wireless account immediately after an application has been
purchased.
[0044] Wireless device account interface 310 may further allow
communication between wireless users and internet users. For
example, a chat application may be purchased which allows the
wireless device users to communicate with computer users. As
described herein, customization component 308 may allow a user to
create, add, and modify a list of buddies to be presented in the
chat application.
[0045] Sending component 312 facilitates sending of a purchased
application, service, or content to a different wireless account.
In one embodiment, sending component 312 facilitates the delivery
of an application as a gift for a user. For example, a user may
purchase an application as a birthday gift for a friend (e.g.,
identified by the friend's phone number) and the friend will
receive a notification message that an application has been
purchased and may be accessed by going to wireless applications
browser, list, or client. If the user does not currently have a
wireless applications account, sending component 312 may send an
SMS message with a link to download the client for accessing
wireless applications.
[0046] In another embodiment, sending component 312 may also push a
purchased application to a phone. The wireless device may request a
list of applications upon startup and receive (e.g., via a push)
information related to the new applications. For example, a newly
purchased software application may require a skin or set of images
to be pushed to the wireless device for quick viewing in the
future.
[0047] Different blocks have been described as separate units.
However, it is appreciated that each functional unit described
herein may be integrated as a single working unit. As such,
depiction of functional units as separate units is exemplary and
should not be construed as limiting the scope of the present
invention.
[0048] The following discussion sets forth in detail the operations
of the present technology for account management. With reference to
FIGS. 4 and 5, flowcharts 400 and 500 each illustrate example
blocks used by various embodiments of the present technology.
Flowcharts 400 and 500, include processes that, in various
embodiments, are carried out by a processor under the control of
computer-readable and computer-executable instructions. The
computer-readable and computer-executable instructions reside, for
example, in data storage features such as computer memory 204,
removable storage 208, and/or non-removable storage 206 of FIG. 2.
The computer-readable and computer-executable instructions are used
to control or operate in conjunction with, for example, processing
unit 202 of FIG. 2. Although specific blocks are disclosed in
flowcharts 400 and 500, such blocks are examples. That is,
embodiments are well suited to performing various other blocks or
variations of the blocks recited in flowcharts 400 and 500. It is
appreciated that the blocks in flowcharts 400 and 500 may be
performed in an order different than presented, and that not all of
the blocks in flowcharts 400 and 500 may be performed.
[0049] FIG. 4 shows an exemplary computer controlled flow diagram
400 for managing wireless account information in accordance with
one embodiment of the present invention. The blocks of flowchart
400 may be carried out by a computing system (e.g., computing
system environment 200) acting as a web server (e.g., web server
140) via software based units (e.g., system 300). It is appreciated
that the blocks of flowchart 400 may be carried out by a computing
system that also hosts or stores various wireless device accounts
as described herein.
[0050] At block 402, a secure connection is established. In one
embodiment, the secure connection (e.g., via secure sockets layer
(SSL) or the like) is established between a client (e.g., web
client 150) and a computing system such as a server (e.g., web
server 140). It is noted that the client may be a computing system
that executes a web browser. The secure connection allows the
communication of login and billing information which might
otherwise be insecure if communicated via a wireless device.
[0051] At block 404, an account interface is presented. In one
embodiment, the account interface may be presented via a software
based unit (e.g., account manager 302). The account interface may
be a web interface including a plurality of static and dynamic
pages presented to a user via a web browser or may be presented to
a user via a specialized or customized application for running
natively on a computer operating system. The account interface
allows a user to authenticate themselves (e.g., via login name and
password). Users may further be able to store pertinent information
including, but not limited to, contact information, billing
information, phone model, and service provider. It is noted that a
user may repeatedly access the account interface to update
information and change application related options, such as,
customizations. The interface may further allow the user to create
web and associated wireless accounts as well as managing wireless
applications including remove applications from his/her wireless
account.
[0052] At block 406, a list of applications is presented. The
account interface described herein, may allow a user to browse and
find applications, services, and content in a variety of ways,
including, but not limited to, searching, categories, and lists
such as most popular. A list of the applications that a user
currently has associated with his/her wireless account may also be
presented.
[0053] At block 408, information related to an application is
presented. The list of applications may contain descriptions,
pictures, sounds, and video associated with an application. For
example, a description and animated image showing various screens
of an application may be presented. The information may also
contain cost and minimum or optimal device requirements.
[0054] At block 410, an interactive version of an application is
presented. In one embodiment, interactive versions capable of
running in the web interface or the application interface may be
presented. The interactive versions may allow users to try the
applications or service with partial or complete functionality. For
example, a news application which uses RSS feeds may be presented
and the user will be able to navigate around as if he/she was using
the application via a wireless device (e.g., cellular
telephone).
[0055] At block 412, an application selection is received. As
described herein, the application selection may be received from a
web client (e.g., web client 150). For example, a user may select
an application that he/she is interested in purchasing and select
the application for immediate purchase. In one embodiment, a user
may add a selected application to a shopping cart for later
purchase.
[0056] At block 414, a plurality of billing options are presented.
In one embodiment, the billing options may be presented as part of
checkout process. A wide variety of billing options may be
presented, as described herein, including, but not limited to, use
based trial, one day trial, one month, several month subscription,
or recurring subscription.
[0057] At block 416, a request is received to purchase the selected
application. As described herein, the request to purchase a
selected application may be received from a web client (e.g., web
client 150). The request may include a selected application and the
selected billing option as described herein. In one embodiment, as
described herein, the request to purchase the application may have
been initiated from a shopping cart or checkout interface or
page.
[0058] At block 418, an expiration is set. In one embodiment, the
expiration is set immediately in the wireless device account. The
expiration may be set via a software based unit (e.g., billing
module 304). The expiration corresponds to billing options selected
and be set accordingly in the wireless device account. For example,
if a several month subscription was selected the expiration date
will be several months from the current date. In another example,
if the user selects a recurring subscription an appropriate
expiration date may be set to 00/00/0000 or other symbol. It is
appreciated that the date could also include more information such
as time of day or application use count.
[0059] At block 420, application customization options are
presented. In one embodiment, the customization options may be
presented and stored via a software based unit (e.g., customization
module 308). Cutomization options, as described herein, allow a
user to select one or more application objects (e.g., RSS feeds,
location information, information components or modules such as a
weather module, user information, etc.) and visual objects (e.g.,
icons, skins, layouts, and the like) to be added to an
application.
[0060] At block 422, the wireless device account is updated. The
wireless account (e.g., one of wireless accounts 135), as described
herein, is updated to include the newly purchased application and
expiration. In one embodiment, the wireless device account may also
be updated with an customization options that have been
selected.
[0061] FIG. 5 shows an exemplary computer controlled flow diagram
of a server implemented method for account management in accordance
with one embodiment of the present invention. The blocks of
flowchart 500 may be carried out by a computing system (e.g.,
computing system environment 200) acting as a web server (e.g., web
server 140) via software based units (e.g., system 300). It is
appreciated that the blocks of flowchart 500 may be carried out by
a computing system that also hosts or stores various wireless
devices accounts as described herein.
[0062] At block 502, a web interface is presented for creating an
account. In one embodiment, a web interface may be presented via a
software based unit (e.g., account manager 302). A user can enter
authentication information such as username and password
information as well as billing information (e.g., credit card,
billing address, and the like). The web interface may further
facilitate convenient access by allowing a user to stay logged in
(e.g., not require reentry of authentication information) such as
with the use of cookies. It is noted that the secure updating of
the wireless account via the web interface allows the phone to
access the wireless account without requiring authentication (e.g.,
username and password) via the wireless device.
[0063] At block 504, a first message to create an account is
received. The first message may include a phone number, electronic
serial number, or the like which may be used to determine carrier
or service provider as well as the phone model. In one embodiment,
the message may be issued from the web interface via a web browser
(e.g., executing on web client 150).
[0064] At block 506, a second message with an identifier is sent to
a wireless device, as described herein. In one embodiment, the
message may be an SMS (Short Message Service) message. The
identifier or identification information may include an
identification code or key (e.g., hash, password, or the like)
which may be a unique identifier. The identification information
may also include a link (e.g., URL) that contains unique
identification information.
[0065] At block 508, a third message is received including the
identifier from the second message previously sent. The identifier
may be verified or confirmed by having the information (e.g. key)
entered into the web interface (e.g., via web client 150). The
identifier may also be verified by the following of a link (e.g.,
URL) via the wireless device. This verification ensures the system
is dealing with the owner of the wireless device.
[0066] At block 510, a web account is created. In one embodiment,
the web account (e.g., one of web accounts 145) may be created by
the execution of a software based unit (e.g., account setup module
306). The web account may contain login information, billing info,
phone number, and other wireless device information. In one
embodiment, the authentication information is stored (e.g., via a
cookie) on a computing device (e.g., web client 150) for return
access.
[0067] At block 512, a link is established between the web account
a wireless applications account. In one embodiment, the link
between the web account (e.g., one of web accounts 145) and the
wireless applications account (e.g., one of wireless accounts 135)
may be established by a software based unit (e.g., account setup
module 306). The link may allow users to see all the applications
that he/she currently has access to via his/her wireless device
(e.g., cellular telephone) and to add applications to his/her
wireless account as described herein.
[0068] At block 514, customization options associated with said
wireless applications account are presented. In one embodiment, the
customization options may be presented and stored via a software
based unit (e.g., customization module 308). As described herein,
the customization options may allow the customization of wireless
applications and the web interfaces. For example, any default
applications or applications with free trials may be may require a
skin (or set of images) or RSS feed to be selected.
[0069] Accordingly, applications can be purchased and customized
for a wireless account with the ease of a web interface. Users are
able to quickly and easily purchase applications via a familiar web
interface without having to use the limited interface of a wireless
device. Software vendor and developers are relieved from having to
tailor their applications to the various billing systems of diverse
carriers or service providers. Moreover, businesses are able to
charge customers in any format (e.g., one time billing, recurring
billing, or the like) and thereby not limited by the abilities of a
carriers' billing systems.
[0070] In the foregoing specification, embodiments of the invention
have been described with reference to numerous specific details
that may vary from implementation to implementation. Thus, the sole
and exclusive indicator of what is, and is intended by the
applicants to be, the invention is the set of claims that issue
from this application, in the specific form in which such claims
issue, including any subsequent correction. Hence, no limitation,
element, property, feature, advantage or attribute that is not
expressly recited in a claim should limit the scope of such claim
in any way. The specification and drawings are, accordingly, to be
regarded in an illustrative rather than a restrictive sense.
* * * * *