throbber
Application No. 14/364,911
`Reply to Office Action dated June 30, 2017
`
`REMARKS
`
`The examiner is thanked for the clearly stated action and for conducting a
`
`telephone interview on August 16, 2017. The present amendment is filed in response to the final
`
`Office Action mailed June 30, 2017, in view of the discussion during the interview, under a
`
`Request for Continued Examination (RCE) concurrently filed herewith. Claims 1-11 are
`
`pending, of which claims 1, 9 and 11 are independent.
`
`1.
`
`Rejections under 35 U.S.C. §112 are Overcome
`
`Claims 1-11 were rejected under 35 U.S.C. §112(a) for reciting "processing
`
`circuitry." In response, applicant has replaced the "processing circuitry" with "detecting section"
`
`and "processor," which is more explicitly supported in FIG. 4 (R881 "detecting section" 150, and
`
`control section 210 including distance information determining section 211, output selecting
`
`section 212, locator operation selecting section 213 and locator selecting section 214, which may
`
`comprise a central "processing unit" (CPU), see fl[0053]) of the application. Claims 1, 9 and 11
`
`were rejected for reciting use of the same "wireless communications protocol" in the call mode
`
`and in the locator mode. In response, applicant has amended these claims to recite use of the
`
`same "synchronization method" in the call mode and in the locator mode, which is more
`
`explicitly supported in 11[0030] and Fig. 3 of the application. Claims 4 and 5 were rejected for
`
`reciting "sound level." In response, applicant has deleted this claim term.
`
`Claims 1, 6, 9 and 10 were rejected under 35 U.S.C. §112(b) for reciting "radio
`
`transceiver." In response, applicant has replaced the "radio transceiver" with "radio section,"
`
`which is more explicitly supported in FIG. 4 ("radio section" 130) of the application. Claims 5-6
`
`and 8 were rejected for reciting "user interface." In response, applicant has replaced the "user
`
`interface" with "operating section," which is more explicitly supported in FIG. 4 ("operating
`
`section" 190) and 11[0051] of the application.
`
`2.
`
`Rejection under 35 U.S.C. §102 is Overcome
`
`Claims 1-3, 8-9 and 11 were rejected under 35 U.S.C. §102(b) as being
`
`anticipated by Hironari (JP 2012/099016). In response, applicant has amended independent
`
`

`

`Application No. 14/364,911
`Reply to Office Action dated June 30, 2017
`
`claims 1, 9 and 11 to more explicitly recite that the same synchronization method ("a defined
`
`synchronization method") is used in both the call mode and in the locator mode. This is
`
`technically advantageous in allowing the mobile terminal, "after outputting the determined
`
`distance information, transitions from the locator mode to the call mode," without having to
`
`perform another synchronization method when transitioning from one mode to another, as
`
`further explicitly recited in claims 1, 9 and 11. Hironari does not teach or suggest the subject
`
`matter now recited in claims 1, 9 and 11 and, therefore, these claims are now believed to be
`
`clearly allowable.
`
`Dependent claims 4-7 and 10 were rejected under 35 U.S.C. §103 as being
`
`obvious over Hironari in combination with various other prior art references. Applicant
`
`respectfully submits that none of these additional references cures the deficiencies of Hironari
`
`and, therefore, independent claims 1, 9 and 11, as amended, are allowable over Hironari even in
`
`combination with any of these additional references. Further, claims 2-8 and 10 depend from
`
`claim 1 or claim 9 and, therefore, these dependent claims are further submitted to be allowable
`
`due at least to their dependency from allowable claims 1 and 9.
`
`Closing
`
`The present application including claims 1-11, as amended, is now believed to be
`
`clearly in condition for allowance. Favorable consideration and a Notice of Allowance are
`
`earnestly solicited.
`
`Respectfully submitted,
`
`SEED Intellectual Property Law Group LLP
`
`/Shoko Leek/
`
`Shoko I. Leek
`
`Registration No. 43,746
`
`SILzmck
`
`701 Fifth Avenue, Suite 5400
`Seattle, Washington 98104-7092
`Phone:
`(206) 622-4900
`Fax: (206) 682-6031
`
`565761571
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket