Document:

<PAGE>

                                                                   Exhibit 10.15

                               T-Mobile USA, Inc.

                      Java Wireless Applications Agreement
                      ------------------------------------

     THIS JAVA WIRELESS APPLICATIONS AGREEMENT (the "Agreement") is made by and
between T-Mobile USA, Inc., a Delaware corporation ("T-Mobile"), and Dwango
North America, Inc., a Texas corporation ("Content Provider"), whose primary
business address is 5847 San Felipe St., Suite 2825, Houston, Texas 77057-3000,
and is effective as of Sept. 3/rd/, 2003 or, if not filled in, the later of the
two signature dates below (the "Effective Date").

     T-Mobile is developing a component of its wireless communications and data
network that enables T-Mobile's subscribers to discover, purchase, download, and
use J2ME games and other J2ME-based applications ("Java Content") on Wireless
Devices via T-Mobile Internet Services.

     Content Provider provides Java Content formatted for discovery, download,
and use on Wireless Devices.

     The parties desire to make available the wireless Java Content of Content
Provider and to enable T-Mobile Subscribers to access, purchase, download, and
use Java Content and/or related services made available by Content Provider.

This Agreement consists of this cover page, the NDA (defined below), the
attached Terms and Conditions, and the Exhibits hereto (collectively, the
"Agreement").

     EXHIBITS

     Exhibit A - Content Provider Deliverables
     Exhibit B - T-Mobile Deliverables
     Exhibit C - Compensation and Payment
     Exhibit D - T-Mobile Java Platform Applications Product Requirements
                 Document ("Java PRD")
     Exhibit E - T-Mobile Java Applications Submission Document

--------------------------------------------------------------------------------
     EACH PARTY'S SIGNATURE BELOW ACKNOWLEDGES THAT SUCH PARTY HAS READ AND
       UNDERSTANDS EACH OF THE TERMS AND CONDITIONS OF THIS AGREEMENT AND
                           AGREES TO BE BOUND BY THEM.
--------------------------------------------------------------------------------
Content Provider                          T-MOBILE USA, Inc.

By: /s/ Rick J. Hennessey                 By: /s/ Nick Sears
   -----------------------------------       -----------------------------------
Title: President                          Title: VP Pwd Mkt
      --------------------------------          --------------------------------
Date:  09.03.03                           Date:  10/1/03
     ---------------------------------         ---------------------------------
--------------------------------------------------------------------------------

<PAGE>

                              TERMS AND CONDITIONS

1.   Definitions. As used herein, the following terms have the following
     meanings:

"Affiliate" means, with respect to either party, an entity that controls
(whether through ownership of a controlling equity interest, majority of board
members, by contract or otherwise), is controlled by, or is under common control
with said party.

"Commercial Launch Date" means the date upon which the Content Provider content
is first made available to Users through the T-Mobile Internet Service.

"Content Provider Marks" means those Marks of Content Provider as Content
Provider may from time to time notify T-Mobile to be "Content Provider Marks" in
connection with this Agreement.

"Content Provider Mobile Services" means any and all games or other applications
containing Java Content as described in Exhibit A (as such may be amended or
supplemented from time to time by mutual agreement of the parties) and
accessible through the T-Mobile Internet Service. It also includes any
applicable network services, related WML content, and HTML content and services.

"Content Provider User Data" means identification and usage data provided by
T-Mobile or Users to Content Provider or collected by Content Provider in
connection with a User's use of the Content Provider Mobile Services. However,
Content Provider User Data does not include Header Information, Gateway Data, or
User Profile information provided or transmitted by T-Mobile or Users, except
where such User Profile information is keyed in by Users directly to Content
Provider while a User is connected to the Content Provider network. Content
Provider User Data includes aggregate, anonymous User demographic information
collected or derived by Content Provider from sources other than T-Mobile, e.g.
focus group research.

"Equipment" means those certain wireless microbrowser handsets (and other
wireless devices, if any) that support the T-Mobile Internet Service, as
identified by T-Mobile in writing from time to time.

"Gateway Data" means the number of times a User accesses the Content Provider
Mobile Services, the time spent by a User within the Content Provider Mobile
Services, the total number of pages on which such User clicks while inside the
Content Provider Mobile Services, and the URLs accessed by the User during the
session.

"Header Information" means the information, including without limitation,
subscriber identification information, internet protocol address and network
equipment identifier, transmitted as the header in data packets sent through the
T-Mobile Internet Service to the Content Provider Mobile Services.

"Intellectual Property Rights" means all intellectual property rights in any
jurisdiction, whether existing under intellectual property, unfair competition
or trade secret laws, or under statute or at common law or equity, including but
not limited to: (i) copyrights, trade secrets, trademarks, trade names, patents,
inventions, designs, logos and trade dress, "moral rights," mask works, rights
of personality, publicity or privacy, and any other intellectual property and
proprietary rights; and (ii) any application or right to apply for any of the
rights referred to in this clause; and (iii) any and all renewals, extensions
and restorations thereof, now or hereafter in force and effect.

"Look and Feel" means the general background of the Equipment screen while
executing applications of the Content Provider Mobile Services, (whether on a
wireless handset or other device) and the

                                       -2-

<PAGE>

functionality and user interfaces relating to such screen. It does not include
any look and feel of the Equipment while executing applications other than the
Java Content.

"Marks" means any trademarks, service marks, trade dress, trade names, corporate
names, proprietary logos or indicia, domain names, and other source or business
identifiers.

"Person" means any natural person, corporation, partnership, limited liability
company, or other legal entity.

"T-Mobile Internet Service" means any or all items included in data products and
services offered by T-Mobile to Users that allow Users to access content
sourced from the Internet that is either pushed to or pulled by the User through
the Equipment.

"T-Mobile Marks" means those Marks of T-Mobile as T-Mobile may from time to time
notify Content Provider to be "T-Mobile Marks" in connection with this
Agreement.

"T-Mobile User Data" means the following identification and usage data provided
by Users to T-Mobile or collected by T-Mobile in connection with the User's use
of the Content Provider Mobile Services (a) Gateway Data, (b) Header
Information, (c) User Profile and (d) any other User Data which is not expressly
included within the definition of Content Provider User Data. Other than Gateway
Data, T-Mobile User Data does not include data arising from Users' activities
within the Content Provider Mobile Services.

"User" means any Person who accesses the Content Provider Mobile Services via
the T-Mobile Internet Service.

"User Data" means T-Mobile User Data and Content Provider User Data.

"User Profile" means User identification information such as name, address,
email addresses, rate plan information or any other profile information that may
be collected by T-Mobile in connection with a User's use of the T-Mobile
Internet Service or use of Content Provider Mobile Services, whether or not
passed by T-Mobile to Content Provider through the T-Mobile Internet Service.

2.   Content Provider Mobile Services

     2.1  Deliverables. Content Provider will provide to T-Mobile the
deliverables identified on, and in accordance with the terms contained in,
Exhibit A hereto. T-Mobile will provide to Content Provider the deliverables
identified on, and in accordance with the terms contained in, Exhibit B hereto.
Prior to making a material modification to the features or functionality of the
Content Provider Mobile Services as described in Exhibit A, Content Provider
must present such modification to T-Mobile for review and consultation with a
reasonable amount of time to permit T-Mobile to provide feedback on the
modification. In the event T-Mobile disapproves such modifications, T-Mobile may
terminate, upon prior notice, this Agreement or, at its option, that portion of
the Content Provider Mobile Services which have been materially modified, or may
require Content Provider to provide the unmodified Content Provider Mobile
Services for the remainder of the Term.

     2.2  Financial Terms. The respective obligations of the parties with
respect to fees to be paid related to this Agreement are set forth in Exhibit C.
Unless otherwise set forth in the Exhibits, the following general terms apply:
(a) each party will pay to the other party all amounts due hereunder when due or
when invoiced, as the case may be; and (b) any undisputed amounts not paid when
due, or as invoiced, will be subject to a finance charge equal to one percent
(1%) per month or the highest rate

                                       -3-

<PAGE>

allowable by law, whichever is less. Where an invoiced amount is disputed in
good faith, the parties will meet and confer in a manner reasonable under the
circumstances to resolve the dispute. Where the resolution indicates
underpayment or overpayment, such correction shall be paid within thirty (30)
days of the resolution or the above finance charge will apply thereafter to the
amount owed until paid.

     2.3  Service Requirements

          2.3.1 Trademark Guidelines. Content Provider will at all times comply
with the T-Mobile Trademark Guidelines with respect to any use by Content
Provider of T-Mobile Marks, in form as provided by T-Mobile. T-Mobile will at
all times comply with Content Provider's mobile logo and Content Provider
trademark guidelines with respect to any use by T-Mobile of Content Provider
Marks, in form as provided by Content Provider. Either party may modify its
respective trademark guidelines from time to time upon and will provide written
notice thereof to the other party, whereupon the other party will comply with
the trademark guidelines as modified.

          2.3.2 Hosting and Service Levels. T-Mobile will provide all network
connectivity, authentication, billing, hosting, serving, download and related
first-tier customer support activities in support of the Content Provider Mobile
Services. For network enabled games, or games that allow Users to check
high-scores, interact with other subscribers and similar type of network pulled
features, Content Provider will host and provide such services and connectivity
in compliance with an agreed-upon attached Service Level Agreement.

          2.3.3 Service Prohibitions. Content Provider represents and warrants
that the Content Provider Mobile Services: (i) do not and will not violate or
infringe upon the rights of any third party (including, for example, copyrights,
trademarks, privacy, or other personal or proprietary rights); (ii) are not
unlawful, harmful, threatening, defamatory, obscene, harassing or racially
objectionable; (iii) do not depict sexually explicit images; and (iv) do not
promote unreasonable violence or illegal activities (bearing in mind that
certain game genres contain, e.g., inherent simulated violence and/or reference
to illegal activities). Notwithstanding anything to the contrary in this
Agreement, T-Mobile may, in its sole discretion, remove, suspend or otherwise
disable User access to any of the Content Provider Mobile Services if, in
T-Mobile's sole discretion, the Content Provider Mobile Services: (a) infringe
upon the rights of any third party (including, for example, copyrights,
trademarks, privacy, or other personal or proprietary rights); (b) are unlawful,
harmful, threatening, defamatory, obscene, harassing or racially objectionable;
(c) contain sexually explicit images; or (d) promote unreasonable violence or
illegal activities.

          2.3.4 Online Advertising. Content Provider may include (a) advertising
on the Content Provider Mobile Services, giving T-Mobile twenty percent (20%) of
the User generated revenues there from; and (b) advertising, sponsorships,
inserts and product/service tie-ins, including but not limited to game title
within the games, content and other applications (if any) which Content Provider
makes available to Users through the Content Provider Mobile Services, giving
T-Mobile twenty percent (20%) of the User generated revenues there from. Any
such advertising, sponsorships, inserts and/or product/service tie-ins shall be
relevant to the premise of the game or application, may not detract from game
play, and may not promote the products or services of any competitor of T-Mobile
or its Affiliates. In the event the parties agree to include a game or other
application within the Content Provider Mobile Service on an exclusive basis,
the parties will negotiate in good faith an equitable share of the advertising
revenue generated thereby and reflect such agreement in an amended Exhibit A.

          2.3.5 Service Security. The parties agree to maintain an appropriate
level of security and integrity for the T-Mobile network and its Users in
connection with the Content Provider Mobile Services, including but not limited
to, implementing procedures to prevent third parties who use the

                                       -4-

<PAGE>

Content Provider Mobile Services from sending or transmitting to Users (a)
unsolicited data or messages, (b) viruses or (c) a volume of messages that
unreasonably burdens the T-Mobile network. Content Provider will immediately
notify T-Mobile if it knows or has reason to know that any such unsolicited
data, messages or viruses are being sent to Users by virtue of such Users' use
of the Content Provider Mobile Services and agrees to use its best commercially
reasonable efforts to prevent and/or block any such unsolicited data, messages
or viruses from being sent to Users. Content Provider agrees to notify T-Mobile
immediately if it knows or has reason to know that Users are being sent an
unusual or abnormal flow, number or type of messages in connection with the
Content Provider Mobile Services and will use cooperate with T-Mobile to prevent
continuing transmission of such data or messages to Users.

     2.4  Privacy and User Data. Notwithstanding anything in this Agreement to
the contrary, the data collected by a party from Users will be subject to that
party's standard privacy policies and the security, privacy and confidentiality
provisions contained in this Agreement. Each party's privacy policy will conform
to applicable legal requirements and industry standards for protection of online
privacy and security. T-Mobile will use commercially reasonable efforts to
comply with Content Provider's requests for aggregate and statistical reporting
of User data, from time to time.

          2.4.1 Restrictions on Use of T-Mobile User Data. Content Provider
agrees that it will only use T-Mobile User Data to perform its obligations
under this Agreement. Content Provider will not use any T-Mobile User Data for
direct marketing or promotions to Users. Content Provider will not distribute
T-Mobile User Data to any third party or allow any third party to access
T-Mobile User Data without the prior written approval of T-Mobile. Content
Provider may not provide, authorize, or allow any third party (including
subsidiaries and affiliates) to provide, any T-Mobile User Data to any wireless
carrier or any non-United States government. Content Provider will store all
T-Mobile User Data collected by Content Provider during the Term in the United
States, and make all T-Mobile User Data collected and stored by Content Provider
during the Term available to T-Mobile or T-Mobile's designee for at least two
(2) years from the later of the creation or collection of such T-Mobile User
Data by Content Provider. Content Provider will not, at any time, store or send
T-Mobile User Data, in any form, outside of the United States. Content Provider
will ensure that any and all User Data is not and will not be subject to any
mandatory foreign destruction laws. To the extent Content Provider is permitted
to provide and does provide T-Mobile User Data to any third party (including
subsidiaries and affiliates) in accordance with this Agreement, such third party
must either (a) agree to be bound by the terms and conditions relating to use of
T-Mobile User Data as set forth in this Agreement, or (b) use and enforce
privacy policies which are no less restrictive as to T-Mobile User Data than the
provisions of this Agreement.

          2.4.2 Restrictions on Use of Content Provider User Data. T-Mobile
agrees that it will only use Content Provider User Data to perform its
obligations under this Agreement. T-Mobile will not use any Content Provider
User Data for direct marketing or promotions to Users. T-Mobile will not
distribute Content Provider User Data to any third party without the prior
written approval of Content Provider.

          2.4.3 Ownership of User Data. The parties agree that all T-Mobile User
Data will be owned by T-Mobile and all Content Provider User Data will be owned
by Content Provider.

          2.4.4 Aggregate Data. The parties agree to cooperate in good faith to
share with each other on a confidential basis on the other's request aggregate,
anonymous information (not containing or referring to personally identifiable
information) regarding Users' use of the Content Provider Services, to the
extent that sharing of information is permitted by other Content Provider
agreements.

                                       -5-

<PAGE>

     2.5  Publicity. Neither party may issue any publicity or general marketing
communications concerning their relationship without the prior written consent
of the other party, which may be withheld in that party's sole discretion.

3.   Certain Rights Granted

     3.1  Content Provider Grant. Subject to the terms and conditions of this
Agreement, Content Provider hereby grants to T-Mobile the non-exclusive right,
within the United States, Canada and Mexico, to use, reproduce, and distribute
the Content Provider Mobile Services in order to enable Users to access the
Content Provider Mobile Services and all content or applications within the
Content Provider Mobile Services through Equipment via the T-Mobile Internet
Service. Notwithstanding the foregoing, Content Provider agrees and understands
that T-Mobile USA, Inc. customers may access the Content Provider Mobile
Services from countries other than the United States, Canada and Mexico when
using the T-Mobile Internet Service.

     3.2  Notices. Neither party may remove, obscure or alter any notices of
Intellectual Property Rights appearing in or on any materials provided by the
other party.

     3.3  T-Mobile Marks License. Subject to the other provisions of this
Agreement (including without limitation Section 3.5), T-Mobile hereby grants
Content Provider the right to use, reproduce, publish, perform and display the
T-Mobile Marks in promotional and marketing materials, content directories and
indices, and electronic and printed advertising, publicity, press releases,
newsletters and mailings about Content Provider and its relationship with
T-Mobile and the Content Provider Mobile Services.

     3.4  Content Provider Marks License. Subject to the other provisions of
this Agreement (including without limitation Section 3.5), Content Provider
hereby grants T-Mobile the right to use, reproduce, publish, perform and display
the Content Provider Marks in and in connection with the development, use and
reproduction of promotional and marketing materials, content directories and
indices, and electronic and printed advertising, publicity, press releases,
newsletters and mailings about T-Mobile and its relationship with Content
Provider.

     3.5  Use of Marks. Prior to each new use of any of the other party's Marks
in the manner permitted herein, the party using such Marks must submit a sample
of such proposed use to the other party for its prior written approval, which
may not be unreasonably withheld or delayed. Once a party approves a particular
use of a Mark, the approval will remain in effect for such use until withdrawn
with reasonable prior written notice. Without limiting the generality of the
foregoing, each party must strictly comply with all standards with respect to
the other party's Marks which may be furnished by such party from time to time,
and all uses of the other party's Marks in proximity to the trade name,
trademark, service name or service mark of any other Person must be consistent
with the standards furnished by the other party from time to time. Further,
neither party may create a combination mark consisting of one or more Marks of
each party. All uses of the other party's Marks shall inure to the benefit of
the party owning such Mark and each party hereby assigns to the other any
goodwill arising from such party's use of the other's Marks. Each party hereby
acknowledges and agrees that, as between the parties hereto, the other party is
the owner of the Marks identified as its Marks on the applicable attachment to
the Agreement.

     3.6  Non-Exclusivity. Each party acknowledges and agrees that the rights
granted to the other party in this Agreement are non-exclusive and that nothing
in this Agreement prohibits either party from participating in business
arrangements similar to those described herein.

                                       -6-

<PAGE>

4.   Warranties, Indemnification and Limitation of Liability

     4.1  Warranties. Each party to this Agreement represents and warrants to
the other party that (a) it has the full corporate right, power and authority to
enter into this Agreement and to perform the acts required of it hereunder; (b)
its execution of this Agreement by such party and performance of its obligations
hereunder, do not and will not violate any agreement to which it is a party or
by which it is bound; and (c) when executed and delivered, this Agreement will
constitute the legal, valid and binding obligation of such party, enforceable
against it in accordance with its terms.

     4.2  Indemnification. Each party (the "Indemnifying Party") will defend,
indemnify and hold harmless the other party and its Affiliates (the
"Indemnified Party"), and the respective directors, officers, employees,
suppliers, and agents of the Indemnified Party, from and against any and all
claims, costs, losses, damages, judgments and expenses (including reasonable
attorneys' fees) (collectively, "Claims") arising out of or in connection with
any third-party claim alleging (i) any breach of such party's representations or
warranties or covenants set forth in this Agreement, (ii) that any
advertisements or other content or materials served to such party to or through
the Content Provider Mobile Services contains any material that is obscene,
libelous, or defamatory, or infringes any Intellectual Property Rights or other
rights of any third party, (iii) any misuse or unauthorized disclosure of User
Data in violation of the terms of this Agreement, (iv) in the case of Content
Provider, that the Content Provider Mobile Services, including any content,
technology, or information contained therein or used in the creation, operation,
maintenance, or use thereof, including use (within the United States, Canada or
Mexico) on or through T-Mobile's telecommunications network infringes on the
Intellectual Property Rights of any person, or (v) in the case of T-Mobile, that
the T-Mobile Internet Service or the technology or information used by T-Mobile
in the creation, operation or maintenance of the wireless telecommunications
network used to deliver the T-Mobile Internet Service (excluding Section 4.2(iv)
above) infringes on the Intellectual Property Rights of any person. The
obligations of the Indemnifying Party are subject to the requirements that (a)
the Indemnified Party notify the Indemnifying Party in writing within a
reasonable time after the Indemnified Party is notified of a claim (provided,
failure to provide timely notice will not alter the Indemnifying Party's duties
hereunder except to the extent such party is materially prejudiced thereby), (b)
the Indemnifying Party have primary control of the defense of the claim (except
that, if an Indemnified Party elects to do so, it may participate in the defense
at its own expense) and all related monetary settlement negotiations (it being
agreed that any non-monetary terms, including any licensing terms, of any
settlement of a claim that directly affects the Indemnified Party shall require
the prior written approval of the Indemnified Party), and (c) the Indemnified
Party provides the Indemnifying Party with reasonable assistance, information
and authority necessary for the Indemnifying Party to perform its obligations
under this section; provided always that the Indemnified Party will not be
required to admit liability under any circumstances. Reasonable out-of-pocket
expenses incurred by an Indemnified Party in providing such assistance must be
reimbursed by the Indemnifying Party promptly upon receipt of an account of such
expenses. The obligations of the parties as set forth in this Section shall
survive expiration or termination of this Agreement for any reason.

     4.3  Limitation of Liability; Disclaimer

          4.3.1 Liability. EXCEPT WHERE SUCH LIABILITY ARISES PURSUANT TO AN
INDEMNIFIED CLAIM OR A BREACH OF CONFIDENTIALITY OBLIGATIONS, UNDER NO
CIRCUMSTANCES WILL EITHER PARTY BE LIABLE TO THE OTHER PARTY FOR INDIRECT,
INCIDENTAL, CONSEQUENTIAL, SPECIAL OR EXEMPLARY DAMAGES (EVEN IF THAT PARTY HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), ARISING OUT OF OR IN
CONNECTION WITH THIS AGREEMENT, INCLUDING, BUT NOT LIMITED TO, LOSS OF REVENUE
OR ANTICIPATED PROFITS OR LOST BUSINESS. EXCEPT FOR LIABILITY ARISING UNDER THE
INDEMNIFICATION OR CONFIDENTIALITY OBLIGATIONS ABOVE,

                                       -7-

<PAGE>

THE AGGREGATE LIABILITY OF EITHER PARTY TO THE OTHER ARISING OUT OF OR IN
CONNECTION WITH THIS AGREEMENT SHALL NOT EXCEED THE TOTAL OF ALL AMOUNTS
RECEIVED BY T-MOBILE HEREUNDER.

          4.3.2 No Additional Warranties. THE EXPRESS WARRANTIES SET FORTH IN
THIS AGREEMENT ARE IN LIEU OF ALL OTHER WARRANTIES, IMPLIED OR STATUTORY,
INCLUDING, BUT NOT LIMITED TO ANY: (A) IMPLIED WARRANTY OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE OR (B) IMPLIED WARRANTY ARISING FROM COURSE OF
PERFORMANCE, COURSE OF DEALING OR USAGE OF TRADE.

5.   Term and Termination

     5.1  Term. The initial term of this Agreement will commence on the
Effective Date and, unless earlier terminated as provided below, will end one
year after the commercial launch of the Content Provider Mobile Service on the
T-Mobile Internet Service (the "Commercial Launch Date"); provided that the term
will automatically renew for successive three-month periods, unless either party
provides written notice of termination to the other party no less than thirty
(30) days prior to the end of the then-current renewal term. The initial term
together with any renewal terms will be referred to herein as the "Term."

     5.2  Termination. Either party may terminate this Agreement upon not less
than thirty (30) days' prior written notice to the other party of any material
breach hereof by such other party, provided that such other party has not cured
such material breach within such thirty (30)-day period.

     5.3  Effect of Termination. Upon termination of this Agreement for any
reason, all rights and obligations of the parties hereunder will be
extinguished, except that: (a) all accrued payment obligations hereunder will
survive such termination or expiration; (b) termination of this Agreement will
have no effect on licenses of content previously granted to Users, which will
continue in accordance with their terms, and (c) the rights and obligations of
the parties under Sections 2.4, 4, 5, 6, 7 and 8 will survive such termination
or expiration.

     5.4  Suspension. In the event the Content Provider Mobile Service fails to
meet T-Mobile's standards, including but not limited to quality, uptimes, and
customer satisfaction, T-Mobile may suspend the link(s) to the Java Content upon
notice to Content Provider. Thereafter, Content Provider shall have thirty (30)
days to cure all noted deficiencies after which, if such are not cured, they
shall become material breach defaults which may lead to termination of this
Agreement by T-Mobile under this Section 5.

6.   Intellectual Property

     6.1  T-Mobile. As between T-Mobile and Content Provider, and except for the
licenses and rights granted herein by Content Provider, which shall remain the
sole property of Content Provider and its licensors, T-Mobile reserves and
retains all right, title and interest, including but not limited to all
Intellectual Property Rights in the technology owned or licensed from third
parties by T-Mobile in connection with this Agreement, and no title to or
ownership of any of the technology is transferred to Content Provider or any
other Person under this Agreement. Without limiting the foregoing, as between
the parties, T-Mobile retains all Intellectual Property Rights and all other
right, title and interest in and to the T-Mobile Internet Service (but excluding
any items supplied by Content Provider) and the T-Mobile Marks. Except as
specifically set forth in this Agreement, Content Provider obtains no right to
use T-Mobile Intellectual Property Rights beyond the term of this Agreement.

                                       -8-

<PAGE>

     6.2  Content Provider. As between T-Mobile and Content Provider, and except
for the licenses and rights granted herein by Content Provider, which shall
remain the sole property of Content Provider and its licensors, Content Provider
reserves and retains all right, title and interest, including but not limited to
all Intellectual Property Rights in the technology owned or licensed from third
parties by Content Provider in connection with this Agreement and no title to or
ownership of any of the technology is transferred to T-Mobile or any other
Person under this Agreement. Without limiting the foregoing, as between the
parties, Content Provider retains all Intellectual Property Rights and all
right, title and interest in and to the Content Provider Mobile Services
(including, without limitation, any and all content, data, URLs, domain names,
technology, software, code, user interfaces, the Look and Feel, Marks and other
items posted thereon or used in connection or associated therewith; but
excluding any items supplied by T-Mobile) and the Content Provider Marks. Except
as specifically set forth in this Agreement, T-Mobile obtains no right to use
Content Provider Intellectual Property Rights beyond the term of this Agreement.

     6.3  Further Assurances. Each party will take, at the other party's
expense, such action (including, without limitation, execution of affidavits or
other documents) as the other party may reasonably request to effect, perfect or
confirm such other party's ownership interests and other rights as set forth
above in this Section 6.

7.   Confidentiality

The terms and conditions of the Non-Disclosure Agreement dated effective April
4, 2003 ("NDA") entered into between the parties are hereby incorporated into
this Agreement, and will apply during the Term hereof, and for two (2) years
thereafter. To the extent that any terms of the NDA conflict with any terms in
this Agreement, this Agreement will control. The terms and conditions of this
Agreement are Confidential Information, as defined in the NDA.

8.   General Provisions

     8.1  Independent Contractors. T-Mobile and Content Provider are independent
contractors under this Agreement, and nothing herein shall be construed to
create a partnership, joint venture, franchise or agency relationship between
T-Mobile and Content Provider. Neither party has any authority to enter into
agreements of any kind on behalf of the other party.

     8.2  Attorneys' Fees. If any arbitration or court action is commenced by
either party, the substantially prevailing party in that action is entitled to
recover its out-of-pocket expenses, including without limitation court costs and
reasonable attorneys' fee, incurred therein.

     8.3  Choice of Law. This Agreement will be governed by, and construed in
accordance with, the laws of the State of Washington without reference to its
choice of law rules. The parties hereby submit to the exclusive jurisdiction of
the state and federal courts sitting in King County, Washington regarding any
dispute arising under this Agreement or in connection herewith, and waive all
objection to said jurisdiction, including without limitation forum non
conveniens.

     8.4  Assignment. Neither party may assign this Agreement or any of its
rights or delegate any of its duties under this Agreement without the prior
written consent of the other party, not to be unreasonably withheld, provided,
however, that either party may assign this Agreement to an Affiliate of that
party or pursuant to a merger, consolidation, corporate reorganization, or sale
of all or substantially all of the assigning party's stock or relevant business
assets. Subject to the foregoing, this Agreement will be binding upon,
enforceable by, and inure to the benefit of the parties and their respective
successors and assigns.

                                       -9-

<PAGE>

     8.5  Nonwaiver. No waiver of any breach of any provision of this Agreement
will constitute a waiver of any prior, concurrent or subsequent breach of the
same or any other provisions hereof, and no waiver will be effective unless made
in writing and signed by an authorized representative of the waiving party.

     8.6  Force Majeure. Neither party will be deemed to be in default of or to
have breached any provision of this Agreement as a result of any delay, failure
in performance or interruption of service, resulting directly or indirectly from
acts of God, acts of civil or military authorities, civil disturbances, wars,
strikes or other labor disputes, fires, transportation contingencies,
interruptions in telecommunications or Internet services or network provider
services, failure of equipment and/or software, other catastrophes or any other
occurrences which are beyond such party's reasonable control. Should a force
majeure event continue for more than thirty (30) days, the other party shall be
free to terminate this Agreement effective immediately upon the giving of notice
thereof.

     8.7  Notices. Any notice or other communication required or permitted to be
given hereunder must be given in writing and delivered in person, mailed, or
delivered by recognized courier service, properly addressed to the applicable
party at its address specified on the cover sheet to this Agreement, with a copy
to the applicable party's Legal Department, and will be deemed effective upon
receipt. Either party may from time to time change the individual to receive
notices or its address by giving the other party notice of the change in
accordance with this section.

     8.8  Invalidity. If any provision of this Agreement is for any reason held
to be invalid, illegal or unenforceable in any respect, the remaining provisions
will remain in full force and effect. If any provision of this Agreement is, for
any reason, determined by a court of competent jurisdiction to be excessively
broad or unreasonable as to scope or subject, such provision must be enforced to
the extent necessary to be reasonable under the circumstances and consistent
with applicable law while reflecting as closely as possible the intent of the
parties as expressed herein.

     8.9  Integration; Amendment. This Agreement and the NDA contain the entire
understanding of the parties with respect to the subject matter hereof, and
supersedes all previous agreements or negotiations between the parties
concerning the same subject matter. This Agreement cannot be amended except by a
writing signed by both parties.

     8.10 Counterparts; Electronic Signature. This Agreement may be executed in
multiple counterparts, each of which shall be deemed an original, and all of
which together shall constitute one and the same instrument. To expedite the
process of entering into this Agreement, the parties acknowledge that
Transmitted Copies (as defined below) of the Agreement will be equivalent to
original documents until such time as original documents are executed and
delivered. "Transmitted Copies" will mean copies that are reproduced or
transmitted via photocopy, facsimile or other process of complete and accurate
reproduction and transmission which reflect the signature of a party or of the
parties.

                                 EXHIBITS FOLLOW

                                      -10-

<PAGE>

                                    EXHIBIT A

                          CONTENT PROVIDER DELIVERABLES

1.   Applications:

     a.   Minimum Features. This Agreement is intended to set forth the terms
and conditions under which Content Provider will provide the Content Provider
Mobile Services across the T-Mobile Telecommunications Network to Users with
Equipment. Content Provider will provide T-Mobile with the data and applications
in appropriate form as described in the T-Mobile Submission Document, attached
hereto as Exhibit E (which shall be completed by Content Provider and submitted
to T-Mobile as to each application of Java Content) in a mutually agreed format
(email, diskette or FTP) for incorporation into the T-Mobile Internet Service.
Content Provider will make the Content Provider Mobile Services available to
T-Mobile for testing and approval as provided below. In providing the Content
Provider Mobile Services, Content Provider agrees to comply with the
requirements of the Java PRD attached to the Agreement as Exhibit D. Content
Provider will make available for release on the Content Provider Mobile
Services, at a minimum, the following titles as of the Commercial Launch Date:

          .  Star Exceed
          .  Dwango Racing
          .  Jumpyon
          .  AquaX
          .  BlackJack
          .  Slots
          .  Roulette
          .  Casino Suite (Subscription)

     b.   Handsets/Wireless Devices: The above titles will be available to
T-Mobile on the Commercial Launch Date and according to the delivery schedule
outlined below and optimized for the following color T-Mobile devices:

<TABLE>
<CAPTION>
Game Title      Min MSRP           Production Dates
-----------------------------------------------------------------------------------------------------------------
<S>             <C>                <C>             <C>             <C>             <C>             <C>
                                   Samsung         Samsung         Nokia           Nokia           Moto
                                   S105            X105            3650            3595            V300
Star Exceed     $ [**]             1-Sep           15-Sep          1-Sep           n/a             30-Sep
dwango Racing   $ [**]             1-Sep           15-Sep          1-Sep           n/a             30-Sep
JumPuyon        $ [**]             1-Sep           15-Sep          1-Sep           n/a             30-Sep
BlackJack       $ [**]             1-Sep           15-Sep          1-Sep           1-Sep           30-Sep
Slots           $ [**]             15-Sep          15-Sep          15-Sep          15-Sep          30-Sep
Roulette        $ [**]             15-Sep          15-Sep          15-Sep          15-Sep          30-Sep
Casino Sub*     $ [**]             30-Sep          30-Sep          30-Sep          30-Sep          30-Sep
AquaX           $ [**]             1-Sep           15-Sep          1-Sep           n/a             30-Sep
</TABLE>

* Monthly subscription fee.

     c.   Schedule:

----------------
** Certain information on this page has been omitted and filed separately with
   the Securities and Exchange Commission. Confidential treatment has been
   requested with respect to the omitted portions.

                                       B-1

<PAGE>

          (1)  The parties will cooperate in good faith to make a test version
of the Java Content available for T-Mobile's beta testing process as promptly as
practicable after signing the Agreement (or an amendment to Exhibit A for
later-added Java Content) and in any event no later than fifteen (15) days
thereafter, unless otherwise agreed to by the parties. T-Mobile will test the
Java Content and communicate any errors or usability problems that it observes
promptly to Content Provider.

          (2)  Both parties will use commercially reasonable efforts to complete
development and beta testing in order to prepare the Java Content for full-scale
commercial use with the T-Mobile Internet Services as promptly as practicable
after signing the Agreement (or an amendment to Exhibit A for later-added Java
Content) and in any event no later than thirty (30) days thereafter, unless
otherwise agreed to by the parties. Content Provider acknowledges that
T-Mobile, in its sole discretion, will be entitled to determine the Commercial
Launch Date of each item of Java Content as made available via the T-Mobile
Internet Services, and without limiting the foregoing T-Mobile will not be
obligated to make Java Content commercially available to Users until such time
as T-Mobile determines through its beta testing process that Content Provider
has resolved all issues identified by T-Mobile and the applicable Java Content
meets T-Mobile's quality and user experience standards.

     d.   Trial/Free Versions: Content Provider acknowledges that T-Mobile shall
be entitled to offer the Java Content as free trials to its Users. See Exhibit
B.

     e.   Screenshots for each application to be hosted by T-Mobile. Details to
be set forth on Exhibit E, Submission Document.

     f.   Instructions for each application, FAQs, etc., to be hosted by
T-Mobile. Details to be set forth on Exhibit E, Submission Document.

     g.   Java PRD - Content Provider agrees to conform the Content Provider
Services, and specifically the Java Content to the T-Mobile Java PRD, attached
as Exhibit D to the Agreement.

     h.   Contextual Download Content:

          1. Graphics for download for each application - characters and logos
          2. Ringtone(s) for each application
          3. If T-Mobile charges a premium for downloading (fee to T-Mobile
          Subscribers beyond transport cost of downloading) - Content Provider
          and T-Mobile will share [*] of net revenue.
          4. T-Mobile, or its designated third-party provider, will host, serve,
          and bill for any downloadable services

2.   Marketing

     a.   Partner Listing. In the event that Content Provider has a web site
that includes a listing of wireless communications carriers with which Content
Provider has a relationship, Content Provider will provide a listing for
T-Mobile.

     b.   Co-Marketing and Exclusive Titles: Parties to discuss opportunities
for co-marketing, development of exclusive titles and in-game T-Mobile
advertising -and/or sponsorships.

3.   Product/Application Delivery

* Certain information on this page has been omitted and filed separately with
the Securities and Exchange Commission. Confidential treatment has been
requested with respect to the omitted portions.

                                       B-2

<PAGE>

     a.   Device Schedule: Content Provider will deliver eight (8) applications
as outlined above in Section l(a) and available for the devices referenced in
Section l(b) for the Commercial Launch Date. T-Mobile will choose a subset of
these applications for inclusion on the T-Mobile Internet Service, however
T-Mobile will offer commercially no fewer than three (3) applications for each
device, to its Users for download.

     b.   T-Mobile and Content Provider will agree on an applications release
schedule.

     c.   Parties will discuss and agree to product roadmap, preliminary launch
schedules and applications development for the following handsets:

          TBD

     d.   Device Compliance and Pre Launch Requirements. T-Mobile acknowledges
that Content Provider needs devices in advance in order to launch simultaneously
with T-Mobile handset introductions. T-Mobile will use best efforts to provide a
mutually agreed upon number of production or near-production devices to Content
Provider for testing and development in advance of commercial launch.

     e.   Other Devices: Parties will mutually explore games and launch
schedules for the T-Mobile SideKick and the T-Mobile PocketPC devices.

4.   User Support Obligations (SLA).

     a.   Customer Care. In addition to application FAQ's and other descriptive
materials outlined in Exhibit E, Content Provider shall provide T-Mobile
Customer Care staff or T-Mobile Users (at T-Mobile discretion) with support
related to requests directly based on application play, functionality, and other
issues inherent to the nature of the specific application (i.e. not related to
download, billing or other T-Mobile service obligations), in the following
formats:
          1.   Toll-free number to be answered at a minimum during business
               hours
          2.   Email support to be answered at a minimum in 24 hours

     b.   Technical Support. In addition to (a), above, Content Provider will
provide T-Mobile with additional developer and technical support including, but
not limited to:

          1. Devoting sufficient resources to resolve problems reported by
T-Mobile within a reasonable time under the circumstances, based on the severity
of the problem and its effect on development and operation of the Content
Provider Mobile Services, and functionality of content thereon.

          2. Designated technical account manager

          3. Reasonable technical support.

     c.   General Service Level Agreement. Content Provider acknowledges that
prior to launching any networked games (games that allow users to connect via
GPRS or SMS to high scores, challenge other users, or allow any communication
between users and/or the Content Provider), Content Provider and T-Mobile will
agree to a Service Level Agreement complete with uptime requirements and
escalation procedures.

                                       B-3

<PAGE>

                                    EXHIBIT B
                              T-MOBILE DELIVERABLES

1. General and Support Deliverables:

     a.   Upon T-Mobile's reasonable acceptance of the Content Provider Mobile
Services, T-Mobile will include a link to the Content Provider Mobile Services
as listed in Section 3 below. T-Mobile, in its reasonable discretion, will
program the overall T-Mobile Internet Service menu and will seek to provide
efficient and consistent user navigation.

     b.   T-Mobile will provide Content Provider with the highest level
membership in T-Mobile's third-party content developer program, will waive any
fees associated with that program, and will make a designated contact person
available to Content Provider for the provision of services thereunder. T-Mobile
will provide Content Provider with documentation, engineering and technical
resources as reasonably necessary for Content Provider to carry out its
obligations hereunder, but in no event less than those generally provided to
other third-party developers having highest level developer status. T-Mobile
will also provide demonstration Equipment in a quantity to be determined by
T-Mobile, in its reasonable discretion.

     c.   In addition to b, above, T-Mobile will provide Content Provider with
additional highest-level developer support including, but not limited to:

          1. Devoting sufficient resources to resolve problems reported by
Content Provider within a reasonable time under the circumstances, based on the
severity of the problem and its effect on development and operation of the
Content Provider Mobile Services, and download of content therefrom

          2. Designated technical account manager

          3. Reasonable technical support.

          4. Equipment, including but not limited to the following: T-Mobile
to provide Content Provider with not less than two (2) fully functioning and
service-enabled units of each type of Equipment to be enabled for Commercial
Launch of the Java Content (one for development, one for quality assurance).

          5. Reasonable access upon request to T-Mobile's developer program
materials, style guides, white papers, etc.

2. Retail Pricing: Parties to discuss retail pricing for the Java Content,
including any minimum suggested retail pricing of Content Provider.

3. Linking/Category Placement Obligations:

     a.   Provided that Content Provider (i) complies with the then-current
version of T-Mobile's Java PRD, (ii) provides all information required by
T-Mobile to do so, and (ii) is otherwise performing its obligations under this
agreement in all material respects, T-Mobile will, at its discretion:

          1. Include a link to the mobile gaming section of Content Provider's
internet web site from a T-Mobile internet web site designed to provide
information about Content Provider Mobile Services,

          2. Include a link to information (to be provided by Content
Provider) about Content Provider's wireless product and service offerings
(including game playing instructions and information) accessible by T-Mobile
Users via their Equipment on the T-Mobile Internet Service.

                                       B-4

<PAGE>

     b.   For services available through wireless devices T-Mobile will provide
placement for the Content Provider Mobile Services and the content offered
thereon, including at a minimum placement on the "Games Deck" or equivalent area
of the T-Mobile Internet Service, and on each game genre subcategory page
thereunder. For each newly released Content Provider title, T-Mobile and Content
Provider will mutually agree on inclusion within (a) the appropriate game genre
subcategory(ies), (b) in any other appropriate categories or locations, together
with the duration of such placement.

4. Free Trials. T-Mobile shall make trial versions of each application of Java
Content available to Users for up to one (1) free trial session per application.

5. Marketing:

     a.   T-Mobile and Content Provider will schedule and hold periodic meetings
on a schedule to be agreed for both parties to keep abreast and informed about
marketing, upcoming handset road map, technical features and updates, allowing
the two parties to make marketing preparations which are not inconsistent with
one another.

     b.   Parties will discuss in good faith additional marketing opportunities
including advertising, point of sale support, game co-branding, game exclusivity
and launch etc.

                                       B-5

<PAGE>

                                    EXHIBIT C

COMPENSATION AND PAYMENT

1.   Revenue Share. T-Mobile agrees to pay Content Provider the following:

     a. (*) of the Net Revenue per unit of Java Content sold by T-Mobile to a
     User (the "Revenue Share"). For the purposes of this Agreement, "Net
     Revenue" means all amounts received by T-Mobile, minus taxes, in connection
     with any sale of Content Provider content to a User (provided that such
     sale shall not occur, and Net Revenue shall not be received by T-Mobile,
     until such time as the User has (a) purchased the Content Provider content,
     and (b) saved the Content Provider content on the User's Interactive
     Device), less a fixed amount ("Basic Deduction") attributable to credits to
     Subscribers, customer care, and bad debt of (*) of net revenue. T-Mobile
     shall be solely responsible for any expenses relating to fraudulent
     transactions and similar expenses, and such expenses shall not affect the
     Revenue Share.

     b. Formulas for revenue share:

     Gross Revenue - tax = Net Revenue
     Net Revenue - Basic Deduction = Revenue Share Basis

2.   Inclusion on Monthly Billing Statements. T-Mobile will include an itemized
     charge on its monthly billing statement to each User for Content Provider
     content accessed/downloaded (regardless of pricing model) by that User
     during the month in question. Content Provider acknowledges that Users may
     see other content providers' charges and line items in the same section as
     Content Provider content billing.

3.   Payment. Within thirty (30) days after the end of each calendar month,
     T-Mobile will provide Content Provider with all activity and reports under
     this Exhibit Section 1 for such monthly period. All payments shall be made
     within thirty (30) days of the T-Mobile fiscal Quarter, in lawful currency
     of the United States of America, shall be accompanied by reports which show
     in reasonable detail the basis for the payment made, and shall be sent to
     the following attention:

                              Dwango North America
                              Attn.: Jacques Faust
                              5847 San Felipe St.
                              Houston, TX. 77057

4.   Audit Right. No more than once in each twelve (12) month period during the
     Term and once thereafter. Content Provider shall have the right, during
     normal business hours, upon fifteen (15) business days' written notice and
     at Content Provider's expense, to examine, audit and take extracts from
     T-Mobile's books and records relating to any payments due to Content
     Provider hereunder; provided that Content Provider will treat such books
     and records as confidential information of T-Mobile subject to Section 7.
     In the event that any such examination or audit reveals an underpayment of
     amounts due, T-Mobile shall promptly pay the amounts owed. In the event
     that the underpayment exceeds ten percent (10%) of amounts due during the
     audited period,

     * Certain information on this page has been omitted and filed separately
     with the Securities and Exchange Commission. Confidential treatment has
     been requested with respect to the omitted portions.

<PAGE>

     T-Mobile shall also pay Content Provider's actual and reasonable costs of
     conducting said audit. If such audit reveals an overpayment, the parties
     will agree on whether to generate a refund or credit in the amount of the
     overpayment.

5.   Multiple Pricing Models.
     a. Parties acknowledge that T-Mobile consumers are charged separately
     through monthly subscription fees (and overages as applicable) for GPRS
     transport associated with Java application downloads ("Current Fee
     Structure"), and that such fees are not subject to the revenue share
     outlined in Exhibit C, Section 1. However, Content Provider agrees that in
     the event T-Mobile modifies its Current Fee Structure so that the cost of
     GPRS transport fees become additive to each java application download
     price ("Adjusted Price"), any existing revenue share as outlined in Exhibit
     C, Section 1, will be based on retail price prior to adding such fees. The
     Adjusted Price will be at T-Mobile discretion and based on file size of
     application

     b. T-Mobile will explore the potential for supporting in the future a
     variety of pricing and billing models, including without limitation
     pay-per-play, bundles, all-you-can eat, and recurring periodic fee
     subscription channel service. However, both parties recognize that as of
     the Commercial Launch Date, pay-per-download will be the default
     pricing/billing structure.

<PAGE>

                                    EXHIBIT D

                                    Java PRD

                              [Provided Separately]

<PAGE>

                                    EXHIBIT E

                 T-Mobile Java Applications Submission Document

Below is a detailed list of items required from Content Provider in order to
successfully submit the content into the T-Mobile Java Provisioning Server. This
information serves as a starting place for out Beta-testing teams to begin
working with Content Provider.

Partner Information:
--------------------

1.   Partner Name

2.   Partner Technical Contact Name

3.   Partner Technical Contact Information (Phone, Fax, Email, Hours
     availability)

Application Information:
------------------------

1.   Application Name (as it should appear to the consumer)

2.   Application Detailed Description

3.   Application Keywords (consumers will be able to search for these keywords
     to find the application in the product catalog)

4.   Application Version Number

5.   Application Size

6.   Runtime Memory Requirements

7.   Application makes network connections (yes/no, please specify if the
     application will transfer information using the T-Mobile data network. If
     yes, specify how the application does this and what information will be
     transferred.)

Physical Resources:
-------------------

1.   .jad file

2.   .jar file

3.   Screenshots of application (3 images required in .jpg format)

Device Support Information:
---------------------------

1.   Device Support (List of targeted T-Mobile devices that application is
     supported on)

2.   Device Specific API usage (detailed list of device specific APIs used in
     the application)

Marketing Information
---------------------

1.   Game description (format and restrictions to be supplied by T-Mobile)

2.   Game instructions ("How to play")

3.   Game FAQ

4.   Screenshots

5.   Non-interactive demonstration (flash or AVI)<PAGE>

                                                                   Exhibit 10.17

                                 [LOGO OF BREW]

                             BREW(TM) Pricing Terms

Percentage of DAP for each Carrier. The following table sets forth the
percentage of the DAP payable to Developer by QUALCOMM on behalf of Carriers for
BREW Applications that are submitted to QUALCOMM by Developer using Developer's
Extranet account credentials and downloaded by the applicable Carrier's end user
subscribers from the Carrier Catalog. No fees will be due Developer when a
Carrier includes a BREW Application in the Carrier Catalog. The percentages in
the following table will not change during the term of QUALCOMM's BREW Carrier
Agreement with the particular Carrier.

--------------------------------------------------
  Carrier Name     Developer Percentage of DAP (1)
--------------------------------------------------
Verizon Wireless               80%
--------------------------------------------------
--------------------------------------------------

(1)  These percentages are subject to the terms in the BREW Developer Agreement
     regarding taxes and other amounts withheld by Carriers, payments made in a
     currency other than U.S. dollars, payments due to BREW Extension
     developers, and the other terms in the BREW Developer Agreement.

Minimum Amounts Due QUALCOMM for Certain BREW Applications. Developer agrees to
pay QUALCOMM the following amounts for Local Applications and Network
Applications submitted by Developer that either (i) do not have a DAP (e.g.,
Applications pre-loaded onto BREW Devices) or (ii) have a DAP of less than a
minimum amount. For purposes of determining the fees owed by Developer, the
following definitions will apply:

     "Local Application" means a BREW Application or Other Application written
     by Developer that does not communicate or exchange information outside the
     BREW Device.

     "Network Application" means a BREW Application or Other Application written
     by Developer that does communicate or exchange information outside the BREW
     Device.

     "Other Application" means an executable software application stored on a
     BREW Device that (i) is not in the BREW Catalog and that requires the use
     of a BREW Extension, or (ii) that uses or accesses, either directly or
     indirectly, the BREW API as embedded in a BREW Device.

--------------------------------------------------------------------------------
    Type of BREW Application                   Amount Due QUALCOMM
--------------------------------------------------------------------------------
Local Applications without a DAP  Ten cents ($0.10), payable each time (i) an
or a DAP less than $1.00.         end user subscriber downloads the Local
                                  Application or (ii) such Application is
                                  pre-loaded onto a BREW Device.
--------------------------------------------------------------------------------
"Subscription" based Network      Ten cents ($0.10) per month per end user
Applications
--------------------------------------------------------------------------------

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary

                                        1

<PAGE>

--------------------------------------------------------------------------------
without a DAP or with a DAP less  subscriber with such Network Application.
than $1.00/month (e.g., a music   Payable monthly until QUALCOMM receives a
player with a per month           message from the end user's BREW Device that
subscription fee).                the subscription has ended.
--------------------------------------------------------------------------------
"Number of Days" based Network    Ten cents ($0.10) per month (prorated) per end
Applications without a DAP or     user subscriber with such Network Application.
with a DAP less than $1.00/month  Payable in full each time (i) an end user
(prorated) (e.g., a game          subscriber downloads the Network Application
application that can be played    or (ii) such Application is pre-loaded onto a
for 60 days).                     BREW Device.
--------------------------------------------------------------------------------
"Elapsed Time" based Network      One cent ($0.01) per minute of use (prorated)
Applications without a DAP or     per end user subscriber with such Network
with a DAP less than $0.10 per    Application. Payable in full each time (i) an
minute of use (prorated) (e.g.,   end user subscriber downloads the Network
a game application that can be    Application or (ii) such Application is
played for a maximum of 60        pre-loaded onto a BREW Device.
minutes).
--------------------------------------------------------------------------------
"Number of Uses" based Network    One cent ($0.01) per use (prorated per end
Applications without a DAP or     user subscriber with such Network Application.
with a DAP less than $0.10 per    Payable in full each time (i) an end user
use (prorated} (e.g., a stock     subscriber downloads the Network Application
trading application that allows   or (ii) such Application is pre-loaded onto a
the user to make 3 stock          BREW Device.
trades).
--------------------------------------------------------------------------------
"Expiration Date" based Network   Ten cents ($0.10) per month (prorated) per end
Applications without a DAP or     user subscriber with such Application. Payable
with a DAP less than $1,00/month  in full each time (i) an end user subscriber
(prorated) (e.g., a game          downloads the Network Application or (ii) such
application that expires on a     Application is pre-loaded onto a BREW Device.
specified date).
--------------------------------------------------------------------------------
All other Network Applications    Fifty cents ($0.50) per end user subscriber
without a DAP or with a DAP less  with such Application. Such fee will be
than $5,00 (e.g., a global        payable each time (i) an end user subscriber
positioning system (GPS)          downloads the Application or (ii) such
application that allows for       Application is pre-loaded onto a BREW Device.
unlimited use).
--------------------------------------------------------------------------------

Additional Revenue Sharing. QUALCOMM reserves the right to collect from
Developer ten percent (10%) of any revenue or other benefit or consideration.
Developer receives from a Carrier, a wireless device manufacturer, an end user
or any third party for (i) BREW Applications submitted or developed by Developer
and made available to a Carrier, wireless device manufacturer, or any third
party, and (ii) software applications submitted or developed by Developer that
use, directly or indirectly, the BREW API embedded in BREW Devices, to the
extent such 10% exceeds the minimum fees set forth above. Developer agrees to
report to QUALCOMM the amount of any revenue, other benefits or consideration
received from Carriers, wireless device manufacturers, end users, or any third
parties.

Payments by Carrier. Notwithstanding anything to the contrary in these BREW
Pricing Terms or in the BREW Developer Agreement, upon QUALCOMM's notice to
Developer. Developer agrees that payments to Developer for BREW Applications as
described in these Pricing Terms or such Agreement may be made directly by the
Carrier. Such payment to be made in accordance with the Carrier's agreement with
Developer, and not by QUALCOMM on behalf of the Carrier as provided above.
Developer acknowledges that QUALCOMM may charge Carrier amounts for services
provided by QUALCOMM or as otherwise agreed to by QUALCOMM and the Carrier, and
that Developer will not be entitled to any such additional amounts.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary

                                        2

<PAGE>

Pricing Templates. For a summary of the pricing templates set forth in the
Developer Extranet, please see the Application Pricing Overview set forth
below.

Fees for BREW Extensions. Developer agrees to pay the fees for each BREW
Extension used, accessed or called by a BREW Application developed by Developer
as described in the pricing terms for the BREW Extension, as posted on
QUALCOMM's Developer Extranet. Payments to the BREW Extension developer will be
made by QUALCOMM on behalf of Developer from amounts otherwise due Developer
under the BREW Developer Agreement, and Developer acknowledges and agrees that
QUALCOMM may (i) reduce amounts otherwise owed to Developer to make such
payments and (ii) make such payments to the BREW Extension developer in
accordance with the terms agreed to by QUALCOMM and such developer. If such
payments are required to be made by QUALCOMM on behalf of Developer to the BREW
Extension developer and there are no amounts due Developer under the BREW
Developer Agreement, then QUALCOMM may, as provided in the BREW Developer
Agreement, charge such fees and amounts, to Developer.

Confidentiality. You acknowledge and agree that these BREW Pricing Terms (as
amended from time to time by QUALCOMM) are the confidential and proprietary
information of QUALCOMM and are subject to the confidentiality and
non-disclosure terms in the BREW Developer Agreement.

             Please print these BREW Pricing Terms for your records.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        3

<PAGE>

Qualcomm(R)

                              EXPORT QUESTIONNAIRE
--------------------------------------------------------------------------------
Product Name:                           QUALCOMM Class ID No.:

--------------------------------------------------------------------------------
Contact Name:                           Phone Number:

--------------------------------------------------------------------------------
Company Name:                           Email Address

--------------------------------------------------------------------------------
Product Description:

--------------------------------------------------------------------------------
Does your product contain encryption or perform
cryptographic functions? (Circle)                                 Yes     No
--------------------------------------------------------------------------------
        Complete the remaining information only if your product contains
                 encryption or performs cryptographic functions.
      If you answered no to the above question, please sign and return this
                      form to QUALCOMM as instructed below.

                            ENCRYPTION QUESTIONNAIRE
--------------------------------------------------------------------------------
Describe all symmetric and asymmetric algorithms and how the algorithms are used
in the software:

--------------------------------------------------------------------------------
Is this software not user-accessible and is it limited to or specially designed
for any the following functions (select Yes or No):
     Yes  No

          Execution of copy-protected software,
          Copy-protected read-only media,
          Information stored in encrypted form on media where the media is
          offered for sale in identical sets to the public,
          One-time encryption of copyright protected audio or video data,
          Authentication or digital signatures,
          Fixed data compression or coding techniques, or
          Banking or money transactions.

     If the encryption is not limited to any of the above functions (if you
     answered no to all of the above questions), please complete the Export
     Classification information below or complete the two page Commodity
     Classification Encryption Questionnaire. If you have obtained the commodity
     classification from the U.S. government, please fill out the export
     classification information below.

--------------------------------------------------------------------------------
 Export Classification    ECCN:   License Exception:   CCATS #:   CCATS Date:
      Information
(if applicable or known)

--------------------------------------------------------------------------------
          Was this encryption product granted RETAIL status
by the U.S. Department of Commerce? (circle one)                   YES   NO   NA
*If applicable, send a fax copy of the CCATS classification to
(858) 651 -1767 along with this completed form.
--------------------------------------------------------------------------------
I hereby certify that the above information is correct.
--------------------------------------------------------------------------------
Print Name                              Signature

--------------------------------------------------------------------------------
Title                                   Date

--------------------------------------------------------------------------------
 Please return the completed form by fax to (858) 651-1767 or by email to
                        qcel@qualcomm.com.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        4

<PAGE>

Qualcomm(R)

--------------------------------------------------------------------------------
               COMMODITY CLASSIFICATION - ENCRYPTION QUESTIONNAIRE
--------------------------------------------------------------------------------
The U.S. Government's Bureau of Export Administration regulates exports of
products and technology, including software offered for download outside the
U.S. To determine the export requirements of your software application, the
technical characteristics of the software must be reviewed against U.S.
government guidelines. The below information is required to determine which
export requirements may apply to your BREW application.
--------------------------------------------------------------------------------
1.  List the symmetric and asymmetric encryption algorithms and key lengths and
    also describe how the algorithms are used (e.g., 56-bit DES, 168-bit 3DES,
    128-bit RC4, 448-bit Blowfish, etc). Specify which encryption modes are
    supported (e.g., cipher feedback mode or cipher block chaining mode.):
    ------------------------------------------------------------------------
    Symmetric Algorithms
    ------------------------------------------------------------------------
    Name of Algorithm   Maximum Key Length     Mode(s)        Use
    ------------------------------------------------------------------------

    ------------------------------------------------------------------------

    ------------------------------------------------------------------------

    ------------------------------------------------------------------------
    Asymmetric Algorithms
    ------------------------------------------------------------------------
    Name of Algorithm   Maximum Modulus Size   Use
    ------------------------------------------------------------------------

    ------------------------------------------------------------------------

    ------------------------------------------------------------------------
    Hash Algorithms (list names)               Use
    ------------------------------------------------------------------------

    ------------------------------------------------------------------------

    ------------------------------------------------------------------------

2.  State the key management algorithms and any key management protocols not
    listed above, including modulus sizes, which are supported (e.g., 512-bit
    RSA, 1024-bit Diffie-Hellman):

    Explain how the application uses these algorithms and protocols.

3.  If using a proprietary algorithm not widely available, include a textual
    description of the algorithm.
    Attach the source code for review by the U.S. Government.

4.  Describe any pre-processing methods (e.g., data compression [LZS, Deflate,
    etc.] or data interleaving) that are applied to the plain text data prior to
    encryption.

--------------------------------------------------------------------------------

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        5

<PAGE>

Qualcomm(R)

--------------------------------------------------------------------------------
5.  Describe any post-processing methods (e.g., packetization, encapsulation)
    that are applied to the cipher text data after encryption:

6.  List the communication protocols (e.g., X.25, Telnet or TCP) and encryption
    protocols (e.g., SSL, IPSEC, or PKCS standards) that are supported:

    Describe these protocols and explain how the application uses them:
    Attach the source code for review by the U.S. Government if the protocols
    are not widely available.

7.  Does this software contain a general application programming interface
    (e.g., one that accepts either a cryptographic or non-cryptographic
    interface but does not itself maintain any cryptographic functionality)?
    Yes [ ]  No [ ]  If Yes, describe and identify which are for internal
    (private) use and which are external (public) use:

8.  Identify the third party libraries or other sources for the encryption
    functionality below:
---------------------------------------------------------------------------
Library                    Manufacturer                   Static or Dynamic
---------------------------------------------------------------------------

---------------------------------------------------------------------------

---------------------------------------------------------------------------

---------------------------------------------------------------------------

9.  For commodities or software using Java byte code, describe the techniques
    that are used to protect against decompilation and misuse.

10. Explain how the product precludes user modification of the encryption
    algorithms, key management and key space.

11. Check all that apply to this product:
    Can the cryptographic functionality be easily changed by the user?
    Yes [ ]    No [ ]

    Does the product require substantial support for installation or use (beyond
    phone support, e.g. requiring a service contract).
    Yes [ ]    No [ ]

    Has the cryptographic functionality been modified or customized to customer
    specification.
    Yes [ ]    No [ ]

12. You must certify that the application does not implement an open
    cryptographic interface (OCI). An OCI provides end users with the ability to
    plug in encryption functionality of their choice. Applications implementing
    an OCI are not eligible for download via the BREW platform.

    [ ]  I certify that this software application does not contain an open
         cryptographic interface.

--------------------------------------------------------------------------------
I hereby certify that the above information is correct.
--------------------------------------------------------------------------------

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        6

<PAGE>

                         BREW END USER LICENSE AGREEMENT

BY INSTALLING OR USING THIS BREW APPLICATION ("APPLICATION") YOU ARE AGREEING TO
BE BOUND BY ALL OF THE TERMS SET FORTH BELOW, IF YOU DO NOT AGREE TO THE TERMS
OF THIS AGREEMENT, DO NOT INSTALL OR USE THE APPLICATION.

Limited License. The developer of the Application ("Developer") hereby
grants to you a non-exclusive limited license to install the object code version
of the Application on one wireless communication device and to use the
Application on such device. All rights not expressly granted are reserved by the
Developer. The term Application includes any software that is provided to you at
the same time the Application is provided to you, or that is used in connection
with the Application.

Restrictions. You agree not to reproduce, modify or distribute the Application
or other software included in your wireless device ("Other Software"). Subject
to applicable law, you agree not to decompile or reverse engineer the
Application or the Other Software. You agree not to (i) remove any copyright or
other proprietary notice from the Application or the Other Software, or (ii)
sublicense or transfer the Application or the Other Software to a third party.

Ownership. You agree that the Developer and its licensors retain all right,
title and interest in and to the Application and all copies of the Application,
including all copyrights therein. You agree to erase an Application from your
wireless device upon receipt of notice.

Termination. This Agreement shall terminate immediately, without notice, if you
fail to comply with any material term of this Agreement. Upon termination you
agree to immediately erase the Application from your wireless device.

Disclaimer of Warranty. THE APPLICATION IS LICENSED TO YOU "AS IS." DEVELOPER
AND ITS LICENSORS DISCLAIM ANY AND ALL WARRANTIES REGARDING THE APPLICATION,
WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. DEVELOPER DOES NOT WARRANT THAT THE OPERATION OF THE
APPLICATION WILL BE UNINTERRUPTED OR ERROR FREE. SOME JURISDICTIONS DO NOT ALLOW
THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY OR MAY
BE LIMITED.

Limitation of Liability. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN
NO EVENT SHALL THE DEVELOPER OR ITS LICENSORS BE LIABLE FOR ANY CONSEQUENTIAL,
SPECIAL, INCIDENTAL OR INDIRECT DAMAGES OF ANY KIND ARISING OUT OF THE USE OF
THE APPLICATION (INCLUDING BUT NOT LIMITED TO LOST DATA OR LOST PROFITS), EVEN
IF THE DEVELOPER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE
MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL THE DEVELOPER'S
LIABILITY FOR ANY CLAIM, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE) OR ANY
OTHER THEORY OF LIABILITY, EXCEED THE FEE PAID BY YOU. SOME JURISDICTIONS DO NOT
ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL
DAMAGES SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY OR MAY BE LIMITED.

Export. The Application is subject to the export control laws and regulations of
the United States and other jurisdictions. You agree to comply with all such
laws and regulations.

Government. If you are or are acting on behalf of an agency or instrumentality
of the United States Government, the Application is "commercial computer
software" developed exclusively at private expense. Pursuant to FAR 12.212 or
FEARS 227 7202 and their successors, as applicable, use, reproduction and
disclosure of the Application is governed by the terms of this Agreement.

Miscellaneous. This Agreement is governed by the laws of the State of
California, USA, without regard to California's conflict of law principles. The
United Nations Convention on Contracts for the Sale of International Goods does
not apply to this Agreement. If any provision hereof is held illegal, invalid
or unenforceable, in whole or in part, such provision shall be modified to the
minimum extent necessary to make it legal, valid and enforceable, and the
legality, validity and enforceability of all other provisions of this Agreement
shall not be affected thereby. This Agreement constitutes the entire agreement
between you and the Developer regarding its subject matter and supersedes any
prior agreement, whether written or oral, relating to the subject matter of this
Agreement. No modification or alteration of this Agreement will be valid except
in writing signed by you and the Developer.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        7

<PAGE>

                            CARRIER LICENSE AGREEMENT

Capitalized terms used herein shall have the same meaning ascribed to them in
the BREW Developer Agreement between QUALCOMM and the Developer. The terms of
this Carrier License Agreement shall apply unless Developer and the applicable
Carrier enter into a separate written agreement.

     1.  License Grant.

          1.1  Grant of License to BREW Software. Subject to this Carrier
License Agreement, Developer hereby grants to Carrier a world-wide, assignable,
non-exclusive license to: (i) to reproduce and include each BREW Application and
related documentation developed by Developer in the Carrier Catalog in object
code format only; and (ii) to distribute through multiple tiers of distribution
to Carrier's end user subscribers ("End Users") an unlimited number of copies of
such BREW Applications in object code form only and such documentation. With
respect to each BREW Application, the foregoing license shall commence on the
date the BREW Applications is downloaded into the Carrier Catalog and will
terminate on the earlier of (a) the date the BREW Application is removed from
the Carrier Catalog, or (b) the date of termination of this Carrier License
Agreement. Any such termination shall not terminate an End User's right to
continue to use a BREW Application downloaded by the End User prior to such
termination. All rights not granted in this Carrier License Agreement are hereby
reserved by Developer and its licensors.

          1.2  License Restrictions. Except to the extent permitted by this
Carrier License Agreement or by applicable law. Carrier agrees (i) it will not
otherwise distribute BREW Applications; (ii) it will not modify, reverse
assemble, decompile or reverse engineer a BREW Application, and (iii) it will
not remove, efface or obscure any copyright notices, logos or other proprietary
notices or legends included in a BREW Application.

     2.  Removal of a BREW Application from the Carrier Catalog.

          2.1  Developer's Requested Removal of a BREW Application from the
Carrier Catalog. Carrier will remove a BREW Application from the Carrier
Catalog within thirty (30) days after receipt of Developer's written request.

          2.2  Carrier's Removal of a BREW Application from the Carrier Catalog.
Subject to the terms in the BREW Carrier Agreement, the Carrier may remove a
BREW Application from the Carrier Catalog at any time and for any reason in the
Carrier's sole discretion. Developer acknowledges that Carrier's removal of a
BREW Application from the Carrier Catalog does not terminate the rights or
licenses of End Users who obtained such BREW Application from Carrier prior to
the date of removal.

     3.  BREW Extensions. For purposes of Section 1 (License Grant) and Section
2 (Removal of BREW Applications from the Carrier Catalog) the term "BREW
Application" includes any BREW Extensions used, accessed or called by a BREW
Application.

     4.  The DAP.

          4.1  DAP Negotiation. Developer and Carrier may choose, from time to
time, to discuss and negotiate a DAP for a particular BREW Application that will
apply only to Carrier. If Developer and Carrier negotiate an alternate DAP for a
BREW Application, Developer will submit an alternate Pricing Template for the
BREW Application.

          4.2  No Fees. No payments shall be made by either Developer or Carrier
to the other under this Carrier License Agreement, or for any use or development
of BREW Applications.

     5.  Ownership. Subject to the licenses granted in this Carrier License
Agreement and the End User License Agreement, Developer and its licensors are
and will remain the owner of all right, title and interest in and to each BREW
Application and BREW Extension, including all intellectual property rights
therein.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        8

<PAGE>

     6.   Representations and Warranties.

               6.1  No Viruses. Developer represents and warrants to Carrier
that each BREW Application developed by Developer will be free from (i) viruses
and code that might disrupt, disable, harm, erase the memory of, or otherwise
impede the operation, features or functions of any software, firmware, hardware,
wireless device, computer system or network, or (ii) code that would permit
Developer or any third party to access the BREW Application to cause the
disablement or impairment of the BREW Application or a BREW Device. In the event
of a breach of the foregoing warranty. Developer will be liable and responsible
for all losses, costs, expenses and damages, including, without limitation, the
cost of recalling BREW Devices.

               6.2  BREW Application Warranty. Each BREW Application will be
deemed accepted by Carrier at the time it is downloaded by the Carrier from
QUALCOMM. Developer warrants to Carrier, for a period of thirty (30) days after
Carrier downloads a copy of a BREW Application from QUALCOMM, that the BREW
Application will perform substantially in accordance with the applicable
documentation. In the event of a breach of this warranty. Carrier must provide
written notice to Developer within the warranty period and Developer will, after
receipt of such notice (i) repair the BREW Application, (ii) replace the BREW
Application with a BREW Application which conforms to the foregoing warranty, or
(iii) terminate this Carrier License Agreement with respect to the BREW
Application. THE FOREGOING WILL BE CARRIER'S SOLE AND EXCLUSIVE REMEDY IN THE
EVENT OF A BREACH OF THE FOREGOING WARRANTY. Developer does not warrant that the
operation of a BREW Application will be uninterrupted or error free.

     7.   DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES AND REPRESENTATIONS SET
FORTH IN THIS CARRIER LICENSE AGREEMENT, NEITHER DEVELOPER, ITS LICENSORS NOR
CARRIER MAKE ANY OTHER WARRANTIES. EXPRESS OR IMPLIED. EACH PARTY EXPRESSLY
DISCLAIMS ALL OTHER WARRANTIES AND REPRESENTATIONS. WHETHER EXPRESS, IMPLIED, OR
STATUTORY, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF
MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE. AND NON-INFRINGEMENT.

     8.   Indemnification.

               8.1  Indemnification. Developer hereby agrees to defend,
indemnify and hold harmless Carrier and its End Users (each, an "Indemnified
Party") against any and all claims, demands, causes of action, damages, costs,
expenses, penalties, losses and liabilities (whether under a theory of
negligence, strict liability, contract or otherwise) incurred or to be incurred
by an Indemnified Party (including reasonable attorney fees) arising out of
resulting from or related to (i) a breach of any representation or warranty
under this Carrier License Agreement or (ii) any use, reproduction or
distribution of a BREW Application or BREW Application documentation developed
by Developer which causes an infringement of any patent, copyright, trademark,
trade secret, or other property rights of any third parties arising in any
jurisdiction throughout the world. Carrier agrees to provide Developer with
written notice of any third party claim subject to indemnification, allowing
Developer to have sole control of the defense of such claim and any resulting
disposition or settlement of such claim; provided, however that the Carrier may
participate in the defense of a claim at its own expense. Any disposition or
settlement that imposes any liability on or affects the rights of Carrier will
require the Carrier's written consent.

               8.2  Limited Remedies. If Developer determines that a BREW
Application becomes, or is likely to become, the subject of an infringement
claim or action. Developer may at its sole option: (i) procure, at no cost to
Carrier, the right to continue distributing such BREW Application, or portion
thereof, as applicable; (ii) replace or modify the BREW Application, or portion
therefor, as applicable to render it non-infringing, provided there is no
material loss of functionality; or (iii) if, in Developer's reasonable opinion,
neither (i) nor (ii) above are commercially feasible, (a) Carrier shall
immediately remove the BREW Application from the Carrier Catalog upon
Developer's written request; and (b) Developer may terminate this Carrier
License Agreement for such BREW Application.

               8.3  Exceptions. Developer will have no liability under this
Section 8 (Indemnification) for any claim or action where: (i) such claim or
action would have been avoided but for modifications of a BREW Application, or
any portion thereof, made by Carrier or a third party; (ii) such claim or action
would have been avoided but for the combination or use of the BREW Application,
or any portion thereof, with other products,

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                        9

<PAGE>

processes or materials not supplied by Developer; (iii) such claim or action
would have been avoided but for Carrier's failure to implement the infringement
remedy of removal as requested, if at all, by Developer under Section 8.2
(Limited Remedies): or (iv) Carrier's use of the BREW Application, or any
portion thereof, is not in compliance with the terms of this Carrier License
Agreement and such claim would have been avoided but for such non-compliance.

               8.4  Sole Remedy. The obligations and remedies set forth in this
Section 8 (Indemnification) shall be the sole and exclusive remedies of Carrier
for the infringement of third-party rights by a BREW Application.

     9.   Liability Limitations.

               9.1  No Consequential Damages. EXCEPT FOR THE OBLIGATIONS AND
LIABILITIES ARISING UNDER SECTION 8 (INDEMNIFICATION) OR A BREACH OF SECTION 1.2
(LICENSE RESTRICTIONS), IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER
PARTY IN ANY MANNER, UNDER ANY THEORY OF LIABILITY. WHETHER IN CONTRACT, TORT
(INCLUDING NEGLIGENCE). BREACH OF WARRANTY OR OTHER THEORY, FOR ANY INDIRECT,
CONSEQUENTIAL, INCIDENTAL, EXEMPLARY, PUNITIVE, STATUTORY OR SPECIAL DAMAGES,
INCLUDING LOST PROFITS AND LOSS OF DATA, REGARDLESS OF WHETHER SUCH PARTY WAS
ADVISED OF OR WAS AWARE OF THE POSSIBILITY OF SUCH DAMAGES.

               9.2  Limit on Liability. EXCEPT FOR THE OBLIGATIONS AND
LIABILITIES ARISING UNDER SECTION 8 (INDEMNIFICATION) OR A BREACH OF SECTION 1.2
(LICENSE RESTRICTIONS), IN NO EVENT SHALL THE TOTAL, CUMULATIVE LIABILITY OF
EITHER PARTY TO THE OTHER PARTY REGARDING ANY AND ALL CLAIMS AND CAUSES OF
ACTION, UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, IN TORT (INCLUDING
NEGLIGENCE). OR OTHERWISE, EXCEED THE AMOUNTS RECEIVED BY DEVELOPER FOR THE
DEVELOPER'S BREW APPLICATIONS DISTRIBUTED BY CARRIER TO END USERS.

               THE LIMITATIONS SET FORTH IN THIS SECTION 9 (LIABILITY
LIMITATIONS) SHALL BE DEEMED TO APPLY TO THE MAXIMUM EXTENT PERMITTED BY
APPLICABLE LAW AND NOTWITHSTANDING THE FAILURE OF THE ESSENTIAL PURPOSE OF ANY
LIMITED REMEDIES SET FORTH IN THIS CARRIER LICENSE AGREEMENT.

               THE PARTIES ACKNOWLEDGE AND AGREE THAT THEY HAVE FULLY CONSIDERED
THE FOREGOING ALLOCATION OF RISK AND FIND IT REASONABLE. AND THAT THE FOREGOING
LIMITATIONS IN THIS SECTION 9 (LIABILITY LIMITATIONS) ARE AN ESSENTIAL BASIS OF
THE BARGAIN BETWEEN THE PARTIES.

     10.  Term and Termination.

               10.1 Term. This Carrier License Agreement will become in effect
on the date Carrier downloads a BREW Application developed by Developer from the
BREW Catalog and will remain in effect until terminated as provided in this
Carrier License Agreement.

               10.2 Termination. Either Party may terminate this Carrier License
Agreement, with or without cause, upon thirty (30) days prior written notice to
the other Party. Upon termination of this Carrier License Agreement, Carrier
agrees (i) to remove from the Carrier Catalog all BREW Applications developed by
Developer; and (ii) to cease permitting End Users (or any other person) from
downloading BREW Applications from the Carrier Catalog. Developer acknowledges
that the termination of this Carrier License Agreement does not terminate the
rights or licenses of End Users who obtained a BREW Application from Carrier
prior to the date of termination of this Carrier License Agreement.

               10.3 Survival. Upon any termination or expiration of this Carrier
License Agreement, the following provisions will survive any such termination or
expiration; Sections titled ("Ownership"), ("Indemnification "). ("Liability
Limitations"), ("Term and Termination"), and ("General").

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       10

<PAGE>

     11.  General.

               11.1 Relationship of Parties. Developer and Carrier are
independent contractors and this Carrier License Agreement shall not establish
any relationship of partnership, joint venture, employment, franchise, or agency
between Developer and Carrier. Neither Developer nor Carrier shall have the
power to bind the other or incur obligations on the other's behalf without the
other's prior written consent.

               ll.2 Export Control Compliance. Carrier agrees that it will not
export or re-export a BREW Application, or any portion of thereof, in any form
in violation of the laws and regulations of the United States or any other
jurisdiction or country without the appropriate United States and foreign
government export or import licenses or other official authorization.

               11.3 Assignment. Developer and Carrier may assign this Carrier
License Agreement in whole without the consent of the other. This Carrier
License Agreement will bind and inure to the benefit of the respective
successors and permitted assigns of Developer or Carrier.

               ll.4 Entire Agreement and Amendment. This Carrier License
Agreement completely and exclusively states the agreement between Developer and
Carrier regarding its subject matter. This Carrier License Agreement supersedes
and govern all prior or contemporaneous understandings, representations,
agreements, or other communications between Developer and Carrier, oral or
written, regarding such subject matter.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       11

<PAGE>

                        BREW EXTENSION LICENSE AGREEMENT

Capitalized terms used herein shall have the same meaning ascribed to them in
the BREW Extension Developer Agreement between QUALCOMM and Extension
Developer. The terms of this BREW Extension License Agreement shall apply unless
Extension Developer and the applicable Application Developer enter into a
separate written agreement.

     1.   License Grant and Restrictions.

               1.1  Grant of License to BREW Extensions. Subject to this BREW
Extension License Agreement, Extension Developer hereby grants to each
Application Developer a world-wide, assignable, non-exclusive license to: (i) to
use and reproduce each BREW Extension and Windows Version of such BREW
Extension, in object code form only, for the purpose of developing one or more
BREW Applications; (ii) to reproduce and distribute to Carriers the BREW
Extension in connection with the distribution of the BREW Applications to the
Carrier, and (iii) sublicense to each such Carrier the non-exclusive right to
reproduce the BREW Extension in the Carrier's Catalog and to distribute the BREW
Extension to the Carrier's end user subscribers ("End Users") in connection with
the distribution of BREW Applications to the End Users. With respect to each
BREW Extension, the foregoing license shall commence on the earliest date that
the BREW Extension or Windows Version is downloaded by Application Developer,
and will terminate on the date of termination of this BREW Extension License
Agreement. Any such termination shall not terminate an End User's right to
continue to use a BREW Extension downloaded by the End User prior to such
termination. All rights not granted in this BREW Extension License Agreement are
hereby reserved by Extension Developer and its licensors.

               1.2  License Restrictions. Except to the extent permitted by
this BREW Extension License Agreement or by applicable law. Application
Developer agrees (i) it will not otherwise distribute BREW Extensions; (ii) it
will not modify, reverse assemble, decompile or reverse engineer a BREW
Extension, and (iii) it will not remove, efface or obscure any copyright
notices, logos or other proprietary notices or legends included in a BREW
Extension.

     2.   The E-DAP. Application Developer acknowledges that Extension Developer
has set an E-DAP for each BREW Extension offered by Extension Developer.
Extension Developer shall have the right to revise the E-DAP and such revisions
will be effective six (6) months after posting by QUALCOMM on the Extensions
portion of QUALCOMM's Developer Extranet. No payments shall be made by either
Extension Developer or Application Developer to the other under this Extension
License Agreement, or for any use or development of BREW Extensions.

     3.   Ownership. Subject to the licenses and sublicense rights granted in
this BREW Extension License Agreement, Extension Developer and its licensors are
and will remain the owner of all right, title and interest in and to each BREW
Extension, including all intellectual property rights therein.

     4.   Representations and Warranties.

               4.1  No Viruses. Extension Developer represents and warrants to
Application Developer that each BREW Extension developed by Extension Developer
will be free from (i) viruses and code that might disrupt, disable, harm, erase
the memory of, or otherwise impede the operation, features or functions of any
software, firmware, hardware, wireless device, computer system or network, or
(ii) code that would permit Extension Developer or any third party to access the
BREW Extension to cause the disablement or impairment of the BREW Extension or a
BREW Device. In the event of a breach of the foregoing warranty. Extension
Developer will be liable and responsible for all losses, costs, expenses and
damages, including, without limitation, the cost of recalling BREW Devices.

               4.2  BREW Extension Warranty. Each BREW Extension will be deemed
accepted by Application Developer at the time it is downloaded by the
Application Developer from QUALCOMM. Extension Developer warrants to Application
Developer, for a period of thirty (30) days after Application Developer
downloads a copy of a BREW Extension from QUALCOMM, that the BREW Extension will
perform substantially

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       12

<PAGE>

in accordance with the applicable documentation. In the event of a breach of
this warranty, Application Developer must provide written notice to Extension
Developer within the warranty period and Extension Developer will, after receipt
of such notice (i) repair the BREW Extension, (ii) replace the BREW Extension
with a BREW Extension which conforms to the foregoing warranty, or (iii)
terminate this BREW Extension License Agreement with respect to the BREW
Extension. THE FOREGOING WILL BE APPLICATION DEVELOPER'S SOLE AND EXCLUSIVE
REMEDY IN THE EVENT OF A BREACH OF THE FOREGOING WARRANTY. EXTENSION DEVELOPER
DOES NOT WARRANT THAT THE OPERATION OF A BREW EXTENSION WILL BE UNINTERRUPTED OR
ERROR FREE.

     5.   DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES AND REPRESENTATIONS SET
FORTH IN THIS BREW EXTENSION LICENSE AGREEMENT. NEITHER EXTENSION DEVELOPER, ITS
LICENSORS NOR APPLICATION DEVELOPER MAKE ANY OTHER WARRANTIES, EXPRESS OR
IMPLIED. EACH PARTY EXPRESSLY DISCLAIMS ALL OTHER WARRANTIES AND
REPRESENTATIONS, WHETHER EXPRESS, IMPLIED, OR STATUTORY. INCLUDING WITHOUT
LIMITATION THE IMPLIED WARRANTIES OF MERCHANTIBILITY, FITNESS FOR A PARTICULAR
PURPOSE, AND NON-INFRINGEMENT.

     6.   Indemnification.

               6.1  Indemnification. Extension Developer hereby agrees to
defend, indemnify and hold harmless Application Developer and its End Users
(each, an "Indemnified Party") against any and all claims, demands, causes of
action, damages, costs, expenses, penalties, losses and liabilities (whether
under a theory of negligence, strict liability, contract or otherwise) incurred
or to be incurred by an Indemnified Party (including reasonable attorney fees)
arising out of, resulting from or related to (i) a breach of any representation
or warranty under this BREW Extension License Agreement or (ii) any use,
reproduction or distribution of a BREW Extension or BREW Extension documentation
developed by Extension Developer which causes an infringement of any patent,
copyright, trademark, trade secret, or other property rights of any third
parties arising in any jurisdiction throughout the world. Application Developer
agrees to provide Extension Developer with written notice of any third party
claim subject to indemnification, allowing Extension Developer to have sole
control of the defense of such claim and any resulting disposition or settlement
of such claim; provided, however that the Application Developer may participate
in the defense of a claim at its own expense. Any disposition or settlement that
imposes any liability on or affects the rights of Application Developer will
require the Application Developer's written consent.

               6.2  Limited Remedies. If Extension Developer determines that a
BREW Extension becomes, or is likely to become, the subject of an infringement
claim or action. Extension Developer may at its sole option: (i) procure, at no
cost to Application Developer, the right to continue distributing such BREW
Extension, or portion thereof, as applicable; (ii) replace or modify the BREW
Extension, or portion therefor, as applicable to render it non-infringing,
provided there is no material loss of functionality; or (iii) if, in Extension
Developer's reasonable opinion, neither (i) nor (ii) above are commercially
feasible, (a) Application Developer shall immediately remove the BREW Extension
from the Carrier Catalog upon Extension Developer's written request: and (b)
Extension Developer may terminate this BREW Extension License Agreement for such
BREW Extension.

               6.3  Exceptions. Extension Developer will have no liability under
this Section 6 (Indemnification) for any claim or action where: (i) such claim
or action would have been avoided but for modifications of a BREW Extension, or
any portion thereof, made by Application Developer or a third party; (ii) such
claim or action would have been avoided but for the combination or use of the
BREW Extension, or any portion thereof, with other products, processes or
materials not supplied by Extension Developer; (iii) such claim or action
would have been avoided but for Application Developer's failure to implement the
infringement remedy of removal as requested, if at all, by Extension Developer
under Section 6.2 (Limited Remedies); or (iv) Application Developer's use of the
BREW Extension, or any portion thereof, is not in compliance with the terms of
this BREW Extension License Agreement and such claim would have been avoided but
for such non-compliance.

               6.4  Sole Remedy. The obligations and remedies set forth in this
Section 6 (Indemnification) shall be the sole and exclusive remedies of
Application Developer for the infringement of third-party rights by a BREW
Extension.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       13

<PAGE>

     7.   Liability Limitations.

               7.1  No Consequential Damages. EXCEPT FOR THE OBLIGATIONS AND
LIABILITIES ARISING UNDER SECTION 6 (INDEMNIFICATION) OR A BREACH OF SECTION 1.2
(LICENSE RESTRICTIONS), IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER
PARTY IN ANY MANNER, UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, TORT
(INCLUDING NEGLIGENCE), BREACH OF WARRANTY OR OTHER THEORY. FOR ANY INDIRECT,
CONSEQUENTIAL, INCIDENTAL, EXEMPLARY, PUNITIVE, STATUTORY OR SPECIAL DAMAGES,
INCLUDING LOST PROFITS AND LOSS OF DATA. REGARDLESS OF WHETHER SUCH PARTY WAS
ADVISED OF OR WAS AWARE OF THE POSSIBILITY OF SUCH DAMAGES.

               7.2  Limit on Liability. EXCEPT FOR THE OBLIGATIONS AND
LIABILITIES ARISING UNDER SECTION 6 (INDEMNIFICATION) OR A BREACH OF SECTION 1.2
(LICENSE RESTRICTIONS), IN NO EVENT SHALL THE TOTAL, CUMULATIVE LIABILITY OF
EITHER PARTY TO THE OTHER PARTY REGARDING ANY AND ALL CLAIMS AND CAUSES OF
ACTION, UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, IN TORT (INCLUDING
NEGLIGENCE), OR OTHERWISE, EXCEED THE AMOUNTS RECEIVED BY EXTENSION DEVELOPER
FOR EXTENSION DEVELOPER'S BREW EXTENSIONS DISTRIBUTED BY APPLICATION DEVELOPER
TO END USERS.

               THE LIMITATIONS SET FORTH IN THIS SECTION 7 (LIABILITY
LIMITATIONS) SHALL BE DEEMED TO APPLY TO THE MAXIMUM EXTENT PERMITTED BY
APPLICABLE LAW AND NOTWITHSTANDING THE FAILURE OF THE ESSENTIAL PURPOSE OF ANY
LIMITED REMEDIES SET FORTH IN THIS BREW EXTENSION LICENSE AGREEMENT.

               THE PARTIES ACKNOWLEDGE AND AGREE THAT THEY HAVE FULLY CONSIDERED
THE FOREGOING ALLOCATION OF RISK AND FIND IT REASONABLE, AND THAT THE FOREGOING
LIMITATIONS IN THIS SECTION 7 (LIABILITY LIMITATIONS) ARE AN ESSENTIAL BASIS OF
THE BARGAIN BETWEEN THE PARTIES.

     8.   Term and Termination.

               8.1  Term. This BREW Extension License Agreement will become
effective on the date Application Developer downloads a BREW Extension developed
by Extension Developer from the BREW Catalog and will remain in effect until
terminated as provided in this BREW Extension License Agreement.

               8.2  Termination. Either Party may terminate this BREW Extension
License Agreement, with or without cause, upon thirty (30) days prior written
notice to the other Party. Upon termination of this BREW Extension License
Agreement, Application Developer agrees to remove from the BREW Catalog all BREW
Applications developed by Application Developer that use, access or call to each
BREW Extension licensed under this BREW Extension License Agreement Extension
Developer acknowledges that the termination of this BREW Extension License
Agreement does not terminate the rights or licenses of End Users who obtained a
BREW Application from Application Developer that uses, accesses or calls to a
BREW Extension prior to the date of termination of this BREW Extension License
Agreement.

               8.3  Survival. Upon any termination or expiration of this BREW
Extension License Agreement, the following provisions will survive any such
termination or expiration; Sections titled ("Ownership"), ("Indemnification"),
("Liability Limitations"), ("Term and Termination"), and ("General").

     9.   General.

               9.1  Relationship of Parties. Extension Developer and Application
Developer are independent contractors and this BREW Extension License Agreement
shall not establish any relationship of partnership, joint venture, employment,
franchise, or agency between Extension Developer and Application Developer.
Neither

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       14

<PAGE>

Extension Developer nor Application Developer shall have the power to bind the
other or incur obligations on the other's behalf without the other's prior
written consent.

               9.2  Export Control Compliance. Application Developer agrees that
it will not export or re-export a BREW Extension, or any portion of thereof, in
any form in violation of the laws and regulations of the United States or any
other jurisdiction or country without the appropriate United States and foreign
government export or import licenses or other official authorization.

               9.3  Assignment. Extension Developer and Application Developer
may assign this BREW Extension License Agreement in whole without the consent of
the other. This BREW Extension License Agreement will bind and inure to the
benefit of the respective successors and permitted assigns of Extension
Developer or Application Developer.

               9.4  Entire Agreement and Amendment. This BREW Extension License
Agreement completely and exclusively states the agreement between Extension
Developer and Application Developer regarding its subject matter. This BREW
Extension License Agreement supersedes and govern all prior or contemporaneous
understandings, representations, agreements, or other communications between
Extension Developer and Application Developer, oral or written, regarding such
subject matter.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       15

<PAGE>

                          APPLICATION PRICING OVERVIEW

The Developer will submit BREW Application specific pricing information via the
BREW Developer Extranet. Developers who submit their BREW Applications for TRUE
BREW Testing will be notified to submit BREW Application pricing information
after their BREW Application has successfully completed the TRUE BREW Testing.

The Developer enters pricing plans for their BREW Applications on the BREW
Developer Extranet. Pricing plans are submitted for a particular Carrier or
across all BREW Carriers. There are two main aspects of pricing plans; the
Pricing Method and the Pricing Basis.

Pricing Methods

The Developer must select at least one of the four following BREW Application
pricing methods:

     1.   The Demonstration pricing method is the pricing method associated with
          no cost to the consumer.

     2.   The Purchase pricing method is the method associated with usage-based
          cost.

     3.   The Subscription pricing method is the method associated with a
          monthly cost.

     4.   The Upgrade pricing method is the method associated with an optional
          cost for BREW Application enhancements. An upgrade is a one-time
          enhancement purchase. It does not change the consumer's usage settings
          on the BREW Application being upgraded.

Pricing Basis

The Developer has a choice from four valid pricing bases:

     1)   Number of Uses (as defined by the BREW Application)

     2)   Expiration Date

     3)   Number of Days

     4)   Elapsed Time (in minutes)

The Pricing Method selected dictates which Pricing Basis are available for the
BREW Application in the Pricing Template submitted by Developer.

BREW Pricing Terms
GT\6240358.20
March 5, 2002
Rev. 6.0                                                    QUALCOMM Proprietary
                                       16

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00070-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00070-of-00352.parquet"}]]