throbber
Receipt date: 04/17/2020
`
`16/757,217 ~ GAU: 2647
`
`ATTY. DOCKET NO
`
`733456.596USPC
`
`Sheet _1 of 1
`
`APPLICATION NO.
`
`PATENT AND TRADEMARK OFFICE
` U.S, DEPARTMENT OF COMMERCE
`
`
`
`
`
`a DOCUMENTNUMBER CODE eeeeeepepo
`
`INFORMATION DISCLOSURE STATEMENT
`
`Lei HUANG
`
`*EXAMINER
`
`U.S. PATENT DOCUMENTS
`KIND
`
`
`FILING DATE
`IF APPROPRIATE
`
`
`
`
`
`
`FOREIGN PATENT DOCUMENTS
`
`
`
`
`
`
`
`
`
`
`TRANSLATION
`Pages, Columns, Lines
`INER
`*
`where Relevant Passages or
`COUNTRY
`DATE
`Cone
`DOCUMENT NUMBER
`NAAT
`YES
`NO
`
`Relevant Figures Appear
`eseeee
`
`
`
`
`
`
`
`NON-PATENT LITERATURE DOCUMENTS(/ncluding Author, Title, Date, Pertinent Pages, Etc.)
`Alfred Asterjadhiet al., “Considerations on WUR frame format,” IEEE 802.11-17/1004r4,
`Qualcomm Inc, July 4, 2017, 26
`
`Intemational Search Report, dated January 8, 2019, for corresponding International Application
`No. PCT/JP2018/0405 14, 2
`Po-Kai Huangetal., “High Level MAC Concept for WUR,” IEEE 802.11-17/0071r0, Intel,
`Janua:
`
`Po-Kai Huanget al.,“WUR Negotiation and Acknowledgement Procedure Follow up,” IEEE
`802.11-17/0342r4, Intel, March 12, 2017, 17
`
`Steve Shellhammeretal., “Considerations on WUR Synchronization,” IEEE 802.11-17/067113,
`Qualcomm Inc, May
`10, 2017, 6
`Steve Shellhammeret al., “WUR Preamble Bit Duration,” IEEE 802.11-17/1354r0, Qualcomm,
`September 10, 2017, 29
`
`YonghoSeoket al., “WUR Synchronization,” [EEE 802.11-17/13841r0, MediaTek Inc., September
`11, 2017, 10
`
`EXAMINER
`* EXAMINER: _
`
`7320016I.docx
`
`06/14/2021
`DATE CONSIDERED
`/DINH NOUYEN/
`Initial if reference considered, whetheror notcitation is in conformance with MPEP 609. Draw line throughcitation if not in
`conformance and not considered. Include copy of this form with next communication to applicant.
`
`April 17, 2020
`
`ALL REFERENCES CONSIDERED EXCEPT WHERE LINED THROUGH.
`
`/D.N/
`
`

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