PTO/SB/08a (08-03 )
`Approved for use through 07/31/2006. OMB 0651-0031
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`App'icati°nNumber —
`Fiingvate —
`
`
`
`-- Artvni —(Not for submission under 37 CFR 1.99)
`—
`
`
`
`Examiner Cite
`No
`
`Patent Number
`
`Kind
`Code1
`
`Issue Date
`
`Name of Patentee or Applicant PageS’CO|UmnS’LmeS Where
`.
`Relevant Passages or Relevant
`of cited Document
`.
`Figures Appear
`
`U.S.PATENTS
`
`1990-04-17
`1995-02-14
`
`1995-12-26
`
`Lindemann, ; et al.
`
`1998-01-20
`
`Tiapholm, ; et al.
`
`1998-02-24
`
`Anderson
`
`1998-10-20
`
`Zilberman, ; et al.
`
`1998-11-10
`
`lshige, ; et al.
`
`2000-02-01
`
`Puthuff, ; et al.
`
`4918737
`5390254
`
`I I II I
`
`5479522
`
`I I
`
`I
`
`I
`
`I
`
`EFS Web 2.0
`
`‘I
`
`HIMPP 1003
`
`HIMPP 1003
`
`1
`
`

`

`'“F°R“"”'°“°'S°L°S“RE
`STATEMENT B”""”°’*“TT(Not for submission under 37 CFR 1.99)
`—
`
`2000-03-07
`
`Weinfurtner, ; et al.
`
`I6035050
`6041129
`6058197
`
`2 E
`IIII
`
`Adams’ etal-
` Hagen’
`etal-
`
`Berger’
`
`etal-
`
`I I I I I
`
`FS Web 2.0
`
`2
`
`

`

`'“F°R“"’“'°“°'S°L°S“RE
`STATEMENT BY ’“"’“°’*“T T(Not for submission under 37 CFR 1.99)
`—
`
`2005-05-03
`
`Hagen, ; et al.
`
`2005-05-17
`
`Bye, ; et al.
`
`2005-10-11
`
`Arndt, ; et al.
`
`2005-12-13
`
`Bogason, ; et al.
`
`2005-12-20
`2006-05-30
`
`2007-08-14
`
`Kaltenbach, ; et al.
`
`2007-10-16
`
`2007-11-06
`
`Niederdrank, ; et al.
`
`I IIII I I I I
`
`If you wish to add additional U.S. Patent citation information please click the Add button.
`
`U.S.PATENT APPLICATION PUBLICATIONS
`
`Examiner Cite
`.
`.
`*
`Initial
`No
`
`.
`.
`Publication Number
`
`Publication
`Kind
`Code1 Date
`
`Name of Patentee or Applicant PageS’CO|UmnS’LineS Where
`.
`Relevant Passages or Relevant
`of cited Document
`Figures Appear
`
`EFS Web 2.0
`
`3
`
`3
`
`

`

`APP"<=ai°n Number —
`Filing Date
`
`Art Unit
`
`— A
`
`delmaniRoger
`Adams,TheodoreP.; etal.
`Stuart;AndrewM.; etal.
`
`'NF°RMAT'°N NSCLOSURE
`STATEMENT BY APPLICANT
`
`(Not for submission under 37 CFR 1.99)
`
`20070225050
`
`2007-09-27
`
`20070239294
`
`2007-10-11
`
`FOREIGN PATENT DOCUMENTS
`
`Examiner Cite Foreign Document
`No
`
`Country
`Code2 i
`
`Publication
`Kind
`Code4 Date
`
`Name of Patentee or
`A “Cant of Cited
`pp
`Document
`
`Pages,Columns,Lines
`where Relevant
`Passages or Relevant
`Figures Appear
`
`I
`
`If you wish to add additional Foreign Patent Document citation information please click the Add button
`
`NON-PATENT LITERATURE DOCUMENTS
`
`Examiner Cite
`
`Include name of the author (in CAPITAL LETTERS), title of the article (when appropriate), title of the item
`(book, magazine, journal, serial, symposium, catalog, etc), date, pages(s), volume-issue number( ),
`publisher, city and/or country where published.
`
`If you wish to add additional non-patent literature document citation information please click the Add button
`
`EFS Web 2.0
`
`4
`
`4
`
`

`

`'“F°R“"”'°“°'S°L°S“RE
`STATEMENT B”""”°’*“TT(Not for submission under 37 CFR 1.99)
`—
`
`EXAMINER SIGNATURE
`
`*EXAM|NER: Initial if reference considered, whether or not citation is in conformance with MPEP 609. Draw line through a
`citation if not in conformance and not considered.
`Include copy of this form with next communication to applicant.
`
`2 Enter office that issued the document, by the two-letter code (WIPO
`1 See Kind Codes of USPTO Patent Documents at www.USPTO.GOV or MPEP 901.04.
`Standard ST.3).
`3 For Japanese patent documents, the indication of the year of the reign of the Emperor must precede the serial number of the patent document.
`4 Kind of document by the appropriate symbols as indicated on the document under WIPO Standard ST.16 if possible.
`5 Applicant is to place a check mark here i
`English language translation is attached.
`
`EFS Web 2.0
`
`5
`
`5
`
`

`

`'“F°R“"”'°“°'S°L°S“RE
`STATEMENT B”""”°’*“TT(Not for submission under 37 CFR 1.99)
`—
`
`Please see 37 CFR 1.97 and 1.98 to make the appropriate selection(s):
`
`CERTIFICATION STATEMENT
`
`E]
`
`That each item of information contained in the information disclosure statement was first cited in any communication
`from a foreign patent office in a counterpart foreign application not more than three months prior to the filing of the
`information disclosure statement. See 37 CFR 1.97( )(1).
`
`That no item of information contained in the information disclosure statement was cited in a communication from a
`
`foreign patent office in a counterpart foreign application, and, to the knowledge of the person signing the certification
`after making reasonable inquiry, no item of information contained in the information disclosure statement was known to
`any individual designated in 37 CFR 1.56(c) more than three months prior to the filing of the information disclosure
`statement. See 37 CFR1.97( )(2).
`
`|:| See attached certification statement.
`
`|:| Fee set forth in 37 CFR 1.17 (p) has been submitted herewith.
`
`None
`
`SIGNATURE
`
`A signature of the applicant or representative is required in accordance with CFR 1.33, 10.18. Please see CFR 1.4(d) for the
`form of the signature.
`
`Name/Print
`
`Date WW-MM-DD>
`Registration Number
`
`59,217
`
`This collection of information is required by 37 CFR 1.97 and 1.98. The information is required to obtain or retain a benefit by the
`public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR
`1.14. This collection is estimated to take 1 hour to complete, including gathering, preparing and submitting the completed
`application form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you
`require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S.
`Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND
`FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria,
`VA 22313-1450.
`
`EFS Web 2.0
`
`6
`
`6
`
`

`

`Privacy Act Statement
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the
`attached form related to a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised
`that:
`(1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited
`is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and Trademark Office is to
`process and/or examine your submission related to a patent application or patent.
`If you do not furnish the requested
`information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act
`(5 U.S.C. 552) and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the
`Department of Justice to determine whether the Freedom of Information Act requires disclosure of these record s.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a
`court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of settlement
`negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a
`request involving an individual, to whom the record pertains, when the individual has requested assistance from the
`Member with respect to the subject matter of the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for
`the information in order to perform a contract. Recipients of information shall be required to comply with the
`requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(
`).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records
`may be disclosed, as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant
`to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of
`National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218( )).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or
`his/her designee, during an inspection of records conducted by GSA as part of that agency's responsibility to
`recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and
`2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this
`purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make
`determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of the
`application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be
`disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an application
`which became abandoned or in which the proceedings were terminated and which application is referenced by either a
`published application, an application open to public inspections or an issued patent.
`
`9.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law
`enforcement agency, if the USPTO becomes aware of a violation or potential violation of law or regulation.
`
`EFS Web 2.0
`
`7
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Serial No. ....................................................................................................................... ..
`
`Filing Date ..................................................................................................................... ..
`Confirmation No. ........................................................................................................... ..
`First Named Inventor ........................................................................... ..Vasant Shridhar
`
`Assignee ......................................................................................................................... ..
`Group Art Unit ............................................................................................................... ..
`Examiner ....................................................................................................................... ..
`
`............................................................................. ..IG1-0002US
`Attorney's Docket No.
`Title:
`.......................................... ..Hearing Assistance Using an External Coprocessor
`
`To:
`
`Commissioner for Patents
`P.O. Box 1450
`
`Alexandria, VA 22313-1450
`
`From:
`
`Benjamin A. Keim (Tel. 509-324-9256; Fax 509-323-8979)
`Customer Number: 29150
`
`Lee & Hayes, PLLC
`601 W. Riverside Avenue, Suite 1400
`Spokane, WA 99201
`
`Fees will be paid by credit card through the EFS Web; however the
`
`Commissioner is hereby authorized to charge any deficiency of fees and credit any
`
`overpayments to Deposit Account Number 12-0769.
`
`
`Dated: November 17 2008
`
`By:
`
`Respectfully Submitted,
`
`/Benjamin Kein1/
`Benjamin A. Keim
`Reg. No. 59,217
`(509) 324-9256
`
`LEE & HAYES, PLLC
`
`1
`
`1117081254 U.'lDA$FORMWPD
`
`8
`
`

`

`Electronic Patent Application Fee Transmittal
`
`— F
`
`iling Date:
`
`Title of Invention:
`
`Hearing Assistance Using an External Coprocessor
`
`;
`
`Utility under 35 USC111(a) Filing Fees
`
`Description
`
`Fee Code
`
`Quantity
`
`Sub-Total in
`
`USD($)
`
`Claims:
`
`Claims in excess of20
`
`Independent claims in excess of3
`
`2202
`
`2201
`
`2
`
`26
`
`110
`
`220
`
`Miscellaneous-Filing:
`
`9
`
`

`

`Description
`
`Fee Code
`
`Quantity
`
`Sub-Total in
`
`USD($)
`
`Patent Appeals and Interference
`
`Post-AIIowance-and-Post-Issuance:
`
`Extenslon of-Tlme
`
`Miscellaneous.
`
`Total in USD ($)
`
`968
`
`10
`
`10
`
`

`

`Electronic Acknowledgement Receipt
`
`Application Number:
`
`International Application Number:
`
`4311777
`
`12273389
`
`Confirmation Number:
`
`8200
`
`Title of Invention:
`
`Hearing Assistance Using an External Coprocessor
`
`First Named Inventor/Applicant Name:
`
`Customer Number:
`
`Filer Authorized By:
`
`Attorney Docket Number:
`
`Receipt Date:
`
`Filing Date:
`
`Time Stamp:
`
`Application Type:
`
`Payment information:
`
`—
`
`Submitted with Payment
`
`Payment Type
`
`Payment was successfully received in RAM
`
`RAM confirmation Number
`
`Credit Card
`
`$968
`
`3420
`
`Part /.zip (if appl.)
`
`Deposit Account
`
`Authorized User
`
`FHeLBfing:
`
`Document
`Number
`
`Document Description
`
`1'-1-le Name
`
`File Size(Bytes)/
`Message Digest
`
`Multi
`
`Pages
`
`11
`
`

`

`FX3 O47.PDF
`
`228808
`
`2e9344bc2I 8c78b20d2468c5680b7f2ebd0
`
`Multipart Description/PDF files in .zip description
`
`Drawings-only black and white line
`drawings
`
`Application Data Sheet
`
`FX4426.PDF
`
`bd98735bbcec89d83cdda575309e7ee27a
`96e0If
`
`This is not an USPTO supplied ADS fillable form
`
`Oath or Declaration filed
`
`FX2891.PDF
`
`I 72660
`
`90e02477df5758ff2I 26934b783022I 000a6
`6755
`
`Information:
`
`Information Disclosure Statement (IDS)
`Filed (SB/08)
`
`FX9220.PDF
`
`3158d60927dcc5aI6762c5ceId39c7399ca
`37609
`
`Information:
`
`This is not an USPTO supplied IDS fillable form
`
`Miscellaneous Incoming Letter
`
`FX4415.PDF
`
`0d27dfI 07786809aI cb45f270d033f859c3d
`bI4b
`
`Information:
`
`Fee Worksheet (PTO-06)
`
`fee-info.pdf
`
`9486a2cI 8867246804ac56c5 I d82642c8ad
`a55c8
`
`12
`
`

`

`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO ofthe indicated documents,
`characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`New Applications Under 35 U.S.C. 111
`lfa new application is being filed and the application includes the necessary components for a filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
`Acknowledgement Receipt will establish the filing date of the application.
`
`National Stage of an International Application under 35 U.S.C. 371
`lfa timely submission to enter the national stage of an international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCT/DO/E0/903 indicating acceptance of the application as a
`national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
`
`New International Application Filed with the USPTO as a Receiving Office
`lfa new international application is being filed and the international application includes the necessary components for
`an international filing date (see PCT Article 11 and MPEP 1810), a Notification of the International Application Number
`and ofthe International Filing Date (Form PCT/R0/105) will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of
`the application.
`
`13
`
`13
`
`

`

`HEARING ASSISTANCE USING AN EXTERNAL COPROCESSOR
`
`RELATED APPLICATION
`
`[0001]
`
`This application claims the benefit of U.S. Provisional Application No.
`
`61/188,840 filed August l3, 2008.
`
`TECHNICAL FIELD
`
`[0002]
`
`The subject matter of this disclosure relates to a hearing enhancement
`
`device, and more specifically, to a hearing enhancement device capable of functioning
`
`together with a coprocessor device.
`
`BACKGROUND
`
`[0003]
`
`Historically, hearing aids assisted people with hearing loss by providing
`
`sound amplification. Typically, hearing aids include microphones to detect external
`
`sound, a processor to amplify the detected sound, a battery, and a speaker to present
`
`amplified sound to a user. Many hearing aids presently translate the detected sound into
`
`a digital signal and use a digital signal processor (DSP) to process the signal. The DSP
`
`can manipulate the signal by applying signal processing algorithms stored on the hearing
`
`aid to improve the quality of the amplified sound.
`
`[0004]
`
`Wearers of hearing aids desire increasingly smaller sized devices to
`
`improve comfort and personal appearance. However, the small size of hearing aids limits
`
`functionality. This form-factor constraint is apparent in short battery life, low powered
`
`|ee@hayes pllc
`
`509-324~9256
`
`I
`14
`
`/G1-0002US
`
`14
`
`

`

`processors, and weak signal processing algorithms. Sound processing is limited due to
`
`the constraints imposed by the small size of hearing aids. For example, much of the
`
`processing power of current hearing aids is devoted to reducing feedback, and thus,
`
`remaining processing power is unable to run powerful signal processing algorithms.
`
`[0005]
`
`It is desirable to maintain the hearing aid as a small device that is placed in
`
`or on the ear of a user.
`
`It is also desirable to hearing aid users to have a device which is
`
`portable, always present, and able to produce high quality amplified sound. Even with
`
`increases in processor power and component miniaturization, hearing aid users still have
`
`many complaints about the capabilities of current hearing aids. Therefore, methods and
`
`devices that provide improved signal processing and function within the existing form-
`
`factor constraints would have considerable utility.
`
`SUMMARY
`
`[0006]
`
`Most of the form-factor limitations of conventional hearing aids can be
`
`overcome by coupling a hearing aid to an external coprocessor device.
`
`Since the
`
`coprocessor device is not required to be placed in or near the ear, it is possible for the
`
`coprocessor device to have a powerful processor with greater functionality than a stand-
`
`alone hearing assist device. By sending a signal detected at the hearing assist device out
`
`to a coprocessor for processing it is possible realize the benefits of a small hearing assist
`
`device, without sacrificing signal processing power.
`
`[0007]
`
`In one aspect, the hearing assist device has a processor and a memory to
`
`store signal processing algorithms. Thus the hearing assist device is able to process
`
`|ee@hayes pllc
`
`509-324~9256
`
`2
`
`/G1-0002US
`
`15
`
`

`

`signals (e.g., audio signals converted into electronic form) without a coprocessor device.
`
`In order to communicate with the coprocessor device, the hearing assist device may also
`
`include a communication interface to communicate with the coprocessor device, and a
`
`handshaking module to receive information regarding a functionality of the coprocessor
`
`device via the communication interface.
`
`In some instances the coprocessor device may
`
`have different capabilities than the hearing assist device, so a functionality comparing
`
`module in the hearing assist device compares the functionality of the coprocessor device
`
`to a functionality of the hearing assist device. Since there may be instances in which the
`
`hearing assist device will provide better signal processing and other instances in which
`
`the coprocessor device would be a superior processor, a processor switching module in
`
`the hearing assist device may direct the signal for at least partial processing to a processor
`
`in either (or both) of the hearing assist device or the coprocessor device. The processed
`
`signal is then returned to the hearing assist device (if processed by a coprocessor device)
`
`and presented to a user by means, such as a speaker on the hearing assist device.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0008]
`
`The detailed description is described with reference to the accompanying
`
`figures.
`
`In the figures,
`
`the use of the same reference numbers in different figures
`
`indicates similar or identical items. These drawings depict only illustrative embodiments
`
`of the invention and are not, therefore, to be considered to be limiting of its scope.
`
`|ee@hayes pllc
`
`509-324~9256
`
`3
`
`/G1-0002US
`
`16
`
`

`

`[0009]
`
`FIG. 1 illustrates a system of a plurality of hearing assist devices in
`
`communication with a plurality of coprocessor devices in accordance with one illustrative
`
`embodiment of the present disclosure.
`
`[0010]
`
`FIG. 2 is a schematic view of an illustrative hearing assist device usable in
`
`the system of FIG. l.
`
`[0011]
`
`FIG. 3 is a schematic view of an illustrative coprocessor device usable in
`
`the system of FIG. l.
`
`[0012]
`
`FIG. 4 is flowchart of an illustrative process for directing a signal for
`
`processing in accordance with an embodiment of the present disclosure.
`
`[0013]
`
`FIG. 5 is flowchart of an illustrative process for directing a signal for
`
`processing in accordance with another embodiment of the present disclosure.
`
`DETAILED DESCRIPTION
`
`[0014]
`
`This disclosure describes techniques, by which the form—factor constraints
`
`inherent
`
`in hearing aids are overcome by leveraging the processing power of an
`
`additional processor, such as a coprocessor, which does not suffer from the same form-
`
`factor constraints. Processing power superior to that provided by conventional hearing
`
`aids has become ubiquitous in modern societies in the form of mobile phones, personal
`
`digital assistants, electronic music players, desktop and laptop computers, game consoles,
`
`television set-top-boxes, automobile radios, navigation systems, and the like. Any of
`
`these devices may function as a coprocessor, while continuing to perform the primary
`
`|ee@hayes pllc
`
`509-324~9256
`
`4
`
`/G1-0002US
`
`17
`
`

`

`functions of each respective device. The coprocessor may also be a device specially
`
`designed to function together with a hearing aid.
`
`[0015]
`
`Permanent coupling to the coprocessor device, however, requires that a
`
`hearing aid user always bring a coprocessor device if he or she desires to benefit from the
`
`hearing aid. The bulk of a coprocessor device may be undesirable when, for example,
`
`engaged in sports. Operation of the coprocessor device may even be prohibited at times
`
`such as while on an airplane or near sensitive medical equipment.
`
`In such situations the
`
`hearing aid user may desire whatever benefit
`
`the hearing aid can provide even if
`
`enhanced processing of the coprocessor device is not available. Thus, it is desirable to
`
`have a hearing aid that will function as a stand-alone-device in the absence of a
`
`coprocessor device, and provide enhanced functionality if and when a coprocessor is
`
`available.
`
`[0016]
`
`In some embodiments, the hearing aid provides sound enhancement to a
`
`user with diminished hearing capacity. However, in other embodiments, the methods and
`
`devices of the present disclosure enhance the hearing abilities of a user with or without
`
`impaired hearing. For example, appropriate signal processing algorithms used together
`
`with the subject of the present disclosure may allow a solider to distinguish the snap of a
`
`twig from other sounds in a forest, or allow a mechanic to detect a grating of gears inside
`
`a noisy engine. Accordingly, devices of the present disclosure are referred to as hearing
`
`assist devices to encompass devices used to enhance sound for users with or without
`
`hearing impairment.
`
`|ee@hayes pllc
`
`509-324~9256
`
`5
`
`/G1-0002US
`
`18
`
`

`

`[0017]
`
`FIG.
`
`1
`
`illustrates a system 100 of a plurality of hearing assist devices
`
`l02(a) to l02(n) in communication with a plurality of coprocessor devices 104(a) to
`
`l04(m).
`
`A communication interface between the hearing devices 102 and the
`
`coprocessor devices
`
`104 may be wired 106 and/or wireless
`
`108.
`
`The wired
`
`communication interface 106 may include, but is not limited to, controller-area network,
`
`recommended standard-232, universal serial bus, stereo wire, IEEE 1394 serial bus
`
`standard (FireWire) interfaces, or the like. The wireless communication interface 108
`
`may include, but is not limited to, Bluetooth, IEEE 802.11x, AM/FM radio signals,
`
`wireless wide area network (WWAN) such as cellular, or the like.
`
`[0018]
`
`Each hearing assist device 102 may include a processor switching module
`
`110 to manage routing of signals amongst the processors of the hearing assist device 102
`
`and one or more of the coprocessor devices 104. The coprocessor devices may include a
`
`handshaking module 112 to facilitate communication between the hearing assist device
`
`102 and the coprocessor device 104,
`
`including sending information describing a
`
`functionality of the coprocessor device 104 to the hearing assist device 102 as part of the
`
`handshaking.
`
`[0019]
`
`Flexibility inherent in the system 100 of the present disclosure allows one
`
`hearing assist device 102 to communicate with zero to m coprocessor devices 104.
`
`Moreover,
`
`the hearing assist device 102 may dynamically add or drop coprocessor
`
`devices 104 on the fly. The hearing assist device 102 functions as a stand—alone device
`
`when zero coprocessor devices 104 are present. The hearing assist device l02(a) may,
`
`for example, communicate only with coprocessor device 104(a) via the wired
`
`|ee@hayes pllc
`
`509-324~9256
`
`6
`
`/G1-0002US
`
`19
`
`

`

`communication interface 106.
`
`In other embodiments, hearing assist device l02(a) may
`
`communicate with a first coprocessor device 104(a) via the wired communication
`
`interface 106 and a second coprocessor device 104(m) via the wireless communication
`
`interface. Many other communication paths are covered within the scope of the present
`
`disclosure including a hearing assist device 102 communicating with more than two
`
`coprocessor devices
`
`104
`
`through any combination of wired and/or wireless
`
`communication interfaces.
`
`[0020]
`
`It is also envisioned that, in some embodiments, more than one hearing
`
`assist device 102 may communicate with a coprocessor device. For example, hearing
`
`assist device 102(a) and hearing assist device l02(n) may both communicate with
`
`coprocessor device 104(m) via two wireless communication interfaces 108. The two
`
`hearing assist devices, 102(a) and l02(n), may represent devices placed in a right ear and
`
`a left ear of a single user. The two hearing assist devices 102(a) and l02(n) may
`
`alternatively represent devices worn by two different users. Many other communication
`
`paths are covered within the scope of the present disclosure, including multiple users
`
`each wearing one or two hearing assist devices 102 and all of the hearing assist devices
`
`102 using a coprocessor device 104 through a plurality of wired and/or wireless
`
`communication interfaces.
`
`[0021]
`
`Any combination of multiple hearing assist devices 102 in communication
`
`with single or multiple coprocessor devices 104 is also within the scope of the present
`
`disclosure. For example, hearing assist device l02(a) may be connected to coprocessor
`
`device 104(a) via a wired communication interface 106 and to coprocessor device 104(m)
`
`|ee@hayes pllc
`
`509-324~9256
`
`7
`
`/G1-0002US
`
`20
`
`

`

`via a wireless communication interface 108. While at the same time, hearing assist
`
`device l02(n) may also be connected to coprocessor device 104(m) via a wireless
`
`communication interface.
`
`[0022]
`
`The hearing assist devices 102 may also be able to communicate with other
`
`hearing assist devices either directly (not shown) or via a coprocessor device 104 such as
`
`hearing assist device 102(a) communicating with hearing assist device l02(n) via
`
`coprocessor device 104(m). Thus, a given hearing assist device 102 may stand alone and
`
`communicate with no other devices, it may communicate with a one or more coprocessor
`
`devices 104, it may communicate with a one or more other hearing assist devices 102, or
`
`it may communicate with the one or more coprocessor devices 104 and one or more other
`
`hearing assist devices 102.
`
`[0023]
`
`The coprocessor devices 104 may also be able to communicate with other
`
`coprocessor devices (not shown). The coprocessor devices 104 may also communicate
`
`with a server 110.
`
`In some embodiments,
`
`the server 110 may be a network server
`
`connected to a network such as the Internet. Communication between the coprocessor
`
`devices 104 and the server 110 may be wired or wireless.
`
`In some embodiments, not
`
`shown, a coprocessor device 104 may be a component of a larger computing device and
`
`the server may be another component of the same larger computing device. Thus, a
`
`given coprocessor device 104 may communicate with a one or more hearing assist
`
`devices 102, and/or with a one or more other coprocessor devices 104, and/or with a one
`
`or more servers 110.
`
`|ee@hayes pllc
`
`509-324~9256
`
`8
`21
`
`/G1-0002US
`
`21
`
`

`

`HEARING ASSIST DEVICE
`
`[0024]
`
`FIG. 2 shows a schematic view 200 of the hearing assist device 102 of FIG.
`
`1. The hearing assist device 102 includes a sensor 202 configured to detect energy in the
`
`form of sound waves. This sensor may be a microphone or any other device capable of
`
`detecting sound.
`
`The hearing assist device 102 may also include a converter 204
`
`configured to convert the detected energy of the sound waves into a signal. The signal
`
`may be an analog signal, a digital signal, or a signal in any other form that is capable of
`
`undergoing processing. The signal is processed by a processor 206 of the hearing assist
`
`device 102. In some embodiments, the processor 206 is a digital signal processor (DSP).
`
`The hearing assist device 102 also includes a memory 208 which may be configured to
`
`store signal processing algorithms 210. Depending on the exact configuration and type of
`
`hearing assist device 102,
`
`the memory 208 may be volatile (such as random access
`
`memory (RAM)), non—volatile (such as read only memory (ROM) and flash memory), or
`
`some combination of the two. The signal processing algorithms 210 may include, but are
`
`not limited to, echo cancellation, noise reduction, directionality, speech processing, pitch-
`
`shifting, signal separation, audio compression, sub—band processing, language translation,
`
`user customized hearing profiles, and feedback reduction algorithms as well as
`
`audiologist customizations. The hearing assist device 102 also includes a communication
`
`interface 212 which may provide a communicative connection via a wired or wireless
`
`communication interface to coprocessor devices 104 or other hearing assist devices 102.
`
`[0025]
`
`The handshaking module 214 of the hearing assist device 102 may be
`
`configured to receive information describing a functionality of the coprocessor device
`
`|ee@hayes pllc
`
`509-324~9256
`
`9
`
`/G1-0002US
`
`22
`
`

`

`104 via the communication interface 212. Examples of specific functionalities of the
`
`coprocessor device are described below. In some embodiments, the handshaking module
`
`214 may also send information describing a functionality of the hearing assist device 102
`
`to the coprocessor device 104. By using the handshaking module 214 to mediate initial
`
`communications between the hearing assist device 102 and the coprocessor device 104,
`
`the hearing assist device 102 is able to do more than merely open a communication
`
`channel to passively await a transfer of data. The handshaking module 214 allows for
`
`exchange of information describing the functionalities of the hearing assist device 102
`
`and the coprocessor device 104, such that communicative connections will be made only
`
`if necessary and only to the extent necessary to provide an enhanced processing to the
`
`hearing assist device 102.
`
`[0026]
`
`Once the functionalities of the hearing assist device
`
`102 and the
`
`coprocessor device 104 are known, then a functionality comparing module 216 may
`
`compare the functionality of the coprocessor device 104 to the functionality of the
`
`hearing assist device 102.
`
`If multiple coprocessor devices 104 are available,
`
`the
`
`functionality comparing module 216 may compare the functionality of each coprocessor
`
`device 104 to each other and/or to the functionality of the hearing assist device 102.
`
`In
`
`some embodiments,
`
`the functionality may be a signal processing algorithm.
`
`The
`
`functionality comparing module 216 may determine that a signal processing algorithm on
`
`one of the coprocessor devices 104 provides a signal processing functionality absent from
`
`the hearing assist device 102 and also absent from other coprocessor devices 104. For
`
`example, a laptop computer functioning as a coprocessor device may have a pitch-
`
`|ee@hayes pllc
`
`509-324~9256
`
`1 O
`23
`
`/G1-0002US
`
`23
`
`

`

`shifting signal processing algorithm which all other devices in the system lack. In such a
`
`situation it may be desirable to process the signal at the laptop computer to benefit from
`
`the pitch-shifting ability of the coprocessor 104.
`
`[0027]
`
`Even if a same general type of signal processing functionality is present on
`
`both the hearing assist device 102 and the coprocessor device