IP Library › Granted Patent US 12,732,486
Granted Patent B2
US 12,732,486 · App. 18/231,641 · Granted Sep 8, 2026

Obfuscation in privacy beacon

Inventors: Jarkko L. Kneckt (Los Gatos, CA); Debashis Dash (San Jose, CA); Elliot S. Briggs (Carmel, CA); Nisan Reuven (Rehovot, IL); Qi Wang (Sunnyvale, CA); Sidharth R. Thakur (San Jose, CA); Su Khiong Yong (Palo Alto, CA); Yong Liu (Campbell, CA); Tianyu Wu (Monterey, CA)
Assignee: Apple Inc.
H04L63/0421H04L5/0048H04W12/02H04W12/037
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,732,486
App. No.
18/231,641
Granted
Sep 8, 2026
Kind
B2
Abstract

Techniques are disclosed for obfuscation in a privacy beacon. An example method includes a first communication device creating a beacon field to be included in a beacon frame. The first communication device can generate a timing synchronization field to be included in the beacon frame. The first communication device can apply an offset to the timing synchronization field of the beacon frame. The first communication device can transmit the beacon frame to a second communication device, the beacon frame comprising the offset timing synchronization field and the beacon field.

Claims (41)

1 . A method, comprising;

by a first communication device:

creating a beacon field to be included in a beacon frame;

generating a timing synchronization field to be included in the beacon frame;

applying an offset to the timing synchronization field of the beacon frame to create an offset timing synchronization field;

obfuscating the offset timing synchronization field based at least in part on applying the offset;

encrypting the beacon frame based at least in part on the obfuscation of the timing synchronization field; and

transmitting the encrypted beacon frame to a second communication device, the encrypted beacon frame comprising the obfuscated offset timing synchronization field and the beacon field.

2 . The method of claim 1 , wherein the method further comprises encrypting the beacon field separately from the timing synchronization field.

3 . The method of claim 1 , wherein the first communication device and the second communication device are configured to comprise a same key to decrypt the obfuscated offset timing synchronization field.

4 . The method of claim 1 , wherein the first communication device is configured to have a second communication device specific key for decrypting the obfuscated offset timing synchronization field.

5 . The method of claim 1 , wherein applying the offset comprises performing an “exclusive or” operation on an original timing synchronization field value and the offset.

6 . The method of claim 1 , wherein the offset applied to the timing synchronization field is a same as a separate offset applied to a medium access control header of the beacon frame.

7 . The method of claim 1 , wherein a timing of the applying the offset to the timing synchronization field is based at least in part on a target beacon transmission time.

8 . A first communication device, comprising:

one or more processors; and

one or more computer-readable media including instructions that, when executed, cause the one or more processors to:

create a beacon field to be included in a beacon frame;

generate a timing synchronization field to be included in the beacon frame;

apply an offset to the timing synchronization field of the beacon frame to create an offset timing synchronization field;

obfuscate the offset timing synchronization field based at least in part on applying the offset;

encrypt the beacon frame based at least in part on the obfuscation of the offset timing synchronization field; and

transmit the encrypted beacon frame to a second communication device, the encrypted beacon frame comprising the obfuscated offset timing synchronization field and the beacon field.

9 . The first communication device of claim 8 , wherein the instructions that, when executed by the one or more processors, further causes the one or more processors to perform operating comprising encrypting the beacon field, wherein the beacon field is encrypted separately from the timing synchronization field.

10 . The first communication device of claim 8 , wherein the first communication device and the second communication device are configured to comprise a same key to decrypt the obfuscated offset timing synchronization field.

11 . The first communication device of claim 8 , wherein the first communication device is configured to have a second communication device specific key for decrypting the obfuscated offset timing synchronization field.

12 . The first communication device of claim 8 , wherein applying the offset comprises performing an “exclusive or” operation on an original timing synchronization field value and the offset.

13 . The first communication device of claim 8 , wherein the offset applied to the timing synchronization field is a same as a separate offset applied to a medium access control header of the beacon frame.

14 . The first communication device of claim 8 , wherein a timing of the applying the offset to the timing synchronization field is based at least in part on a target beacon transmission time.

15 . One or more non-transitory, computer-readable media having stored thereon a sequence of instructions which, when executed, causes one or more processors of a first communication device to:

create a beacon field to be included in a beacon frame;

generate a timing synchronization field to be included in the beacon frame;

apply an offset to the timing synchronization field of the beacon frame to create an offset timing synchronization field;

obfuscate the offset timing synchronization field based at least in part on applying the offset;

encrypt the beacon frame based at least in part on the obfuscation of the timing synchronization field; and

transmit the beacon frame to a second communication device, the beacon frame comprising the offset timing synchronization field and the beacon field.

16 . The one or more non-transitory, computer-readable media of claim 15 , wherein the instructions that, when executed, further cause the one or more processors to encrypt the beacon field, wherein the beacon field is encrypted separately from the timing synchronization field.

17 . The one or more non-transitory, computer-readable media of claim 15 , wherein the first communication device and the second communication device are configured to comprise a same key to decrypt the obfuscated offset timing synchronization field.

18 . The one or more non-transitory, computer-readable media of claim 15 , wherein the first communication device is configured to have a second communication device specific key for decrypting the obfuscated offset timing synchronization field.

19 . The one or more non-transitory, computer-readable media of claim 15 , wherein applying the offset comprises performing an “exclusive or” operation on an original timing synchronization field value and the offset.

20 . The one or more non-transitory, computer-readable media of claim 15 , wherein the offset applied to the timing synchronization field is a same as a separate offset applied to a medium access control header of the beacon frame.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 14, 2023
From: KNECKT, JARKKO L.; DASH, DEBASHIS; BRIGGS, ELLIOT S.; REUVEN, NISAN; WANG, QI; THAKUR, SIDHARTH R.; YONG, SU KHIONG; LIU, YONG; WU, TIANYU
To: APPLE INC.
Reel/Frame 064583/0218 →
Continuity (2)
Provisional Application 63396221 · Aug 8, 2022
Related Publication 20240048531A1 · Feb 8, 2024
References Cited (30)
US 7801095B2 · Kil · 2010 [cited by applicant]
US 11522695B2 · Hariharan et al. · 2022 [cited by applicant]
US 20080219452A1 · Lu et al. · 2008 [cited by applicant]
US 20110178862A1 · Daigle · 2011 [cited by applicant]
US 20130294232A1 · Segev et al. · 2013 [cited by applicant]
US 20140105097A1 · Liu · 2014 [cited by applicant]
US 20150271667A1 · Bernsen · 2015 [cited by applicant]
US 20160029377A1 · Masuda et al. · 2016 [cited by applicant]
US 20160337783A1 · Seok · 2016 [cited by applicant]
US 20170094587A1 · Ding et al. · 2017 [cited by applicant]
US 20170142604A1 · Reial et al. · 2017 [cited by applicant]
US 20170164387A1 · Lou et al. · 2017 [cited by applicant]
US 20200169977A1 · Agardh · 2020 [cited by applicant]
US 20200244325A1 · Motozuka · 2020 [cited by examiner]
US 20210105579A1 · Akkarakaran et al. · 2021 [cited by applicant]
US 20220247726A1 · Mooney · 2022 [cited by examiner]
US 20220303893A1 · Chu · 2022 [cited by applicant]
US 20220329510A1 · Barrett et al. · 2022 [cited by applicant]
US 20230098093A1 · Hawkes · 2023 [cited by examiner]
US 20230328669A1 · Naik · 2023 [cited by examiner]
CN 105706505A · 2016 [cited by applicant]
CN 106060809A · 2016 [cited by applicant]
CN 112825520A · 2021 [cited by applicant]
WO 2019139627A1 · 2019 [cited by applicant]
WO WO2024008841A1 · 2024 [cited by examiner]
U.S. Appl. No. 18/231,566, “Final Office Action”, Oct. 27, 2025, 20 pages. [cited by applicant]
U.S. Appl. No. 18/231,566, “Non-Final Office Action”, Apr. 11, 2025, 17 pages. [cited by applicant]
“Machine translation of CN 112825520 A”, May 21, 2021, 18 pages. [cited by applicant]
“Machine translation of WO 2019139627 A1”, Jul. 18, 2019, 17 pages. [cited by applicant]
U.S. Appl. No. 18/231,566, “Non-Final Office Action”, May 28, 2026, 22 pages. [cited by applicant]