Non-wakeup retention of near owner state

Scan the beacon advertisements through the wireless network interface and send timer reset packets to achieve efficient reporting and resource savings on wireless device connection status, while maintaining the near-owner mode of wireless attachments near the owner device, solving resource consumption and malicious tracking The problem.

CN119014028APending Publication Date: 2024-11-22APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033574.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-10-28
Filing Date
2023-04-07
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The prior art consumes device resources when reporting wireless device connection status, resulting in waste of resources and inaccurate proximity notifications, and wireless attachments may be maliciously tracked when detected by non-owner device.

Method used

Scan the beacon advertisements through the wireless network interface, detect the identifiers, and selectively send the timer reset packets and authorization tokens, making the wireless attachments sleep for a predetermined time, reducing resource consumption, and keeping them close to all around the owner's device mode to avoid unnecessary tracking notifications.

Benefits of technology

Effectively reduces device battery consumption and unnecessary tracking notifications, improves the accuracy of connection status reporting, and prevents malicious tracking of wireless accessories on non-owner devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014028A_ABST
    Figure CN119014028A_ABST
Patent Text Reader

Abstract

Embodiments described herein provide a mobile electronic device comprising a wireless network interface coupled to a bus, a memory device coupled to the bus, and one or more processors coupled to the bus, the one or more processors are to execute instructions to: perform, via the wireless network interface, a scan of beacon advertisements broadcasted by wireless devices within the range of the wireless network interface; detecting a beacon advertisement broadcast by the wireless device; retrieving an identifier broadcast within the beacon advertisement; selectively sending a timer reset packet and an authorization token to the wireless device based on a comparison between the identifier and the at least one expected identifier to maintain the wireless accessory in a near owner mode; and allowing the one or more processors to sleep within a predetermined time.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related patent applications

[0002] This application claims priority to U.S. Patent Application No. 18 / 050,887 filed on October 28, 2022, U.S. Provisional Patent Application No. 63 / 348,802 filed on June 3, 2022, and U.S. Provisional Patent Application No. 63 / 330,221 filed on April 12, 2022, each of which is incorporated herein by reference. Technical Field

[0003]

[0013] Embodiments described herein generally relate to systems and methods for locating wireless devices and accessories. Background Art

[0004] Applications that provide notifications about the location of another device rely on being able to establish a wireless connection with the other device. When a first device loses the ability to form a wireless connection with the other wireless device, the owner of the first device can be alerted within the user interface of the application that the connection is lost. Continuously reporting the status of a connection with another wireless device rapidly consumes device resources because, even if the first device stores information about the time window in which the other device is scheduled to advertise (i.e., every X minutes), the first device cannot know when the other device is expected to send an advertisement because the first device does not have the latest information about where the other device is located in the time window. In order to report the connection status, the owner device must repeatedly wake up the device processor or allow the processor to sleep to be able to detect advertisements from the other device. In order to avoid consuming resources, the wireless connection between the first device and the other device may be missed, and notifications about proximity to the first device may be inaccurate. Therefore, existing methods for reporting connection status with other devices unnecessarily consume device batteries. Summary of the invention

[0005] Methods, non-transitory machine-readable media, and systems for providing location services for locating wireless devices and accessories are described. In one embodiment, a device provides a wireless network interface coupled to a bus, a memory device coupled to the bus, and one or more processors coupled to the bus. In some embodiments, the one or more processors execute instructions stored on the memory device, wherein when executed, the instructions cause the one or more processors to perform the following operations: perform a scan via the wireless network interface for beacon advertisements broadcast by wireless devices within the range of the wireless network interface; detect beacon advertisements broadcast by wireless devices; retrieve an identifier broadcast within the beacon advertisement; based on a comparison result between the identifier and at least one expected identifier, selectively send a timer reset packet and an authorization token to the wireless device to keep the wireless accessory in a near-owner mode; and allow the one or more processors to sleep for a predetermined time. In one embodiment, the identifier is a hardware address. In some embodiments, the instructions cause the one or more processors to determine whether the wireless device associated with the beacon advertisement is associated with an account on a mobile electronic device. In some embodiments, the instructions additionally cause the one or more processors to generate a set of cryptographic keys based on stored key material, wherein the key material is generated in collaboration with the wireless accessory. In one embodiment, the set of cryptographic keys includes keys for one or more privacy time periods for the wireless accessory, and the operation further includes changing one or more keys used to generate a hardware address with the wireless accessory during each privacy time period. In one embodiment, at least one processor wakes up after a predetermined time period. In one embodiment, the timer reset packet includes a reset identifier and a channel selection. In some embodiments, the wireless network interface is a Bluetooth network interface.

[0006] In one embodiment, the wireless accessory provides a wireless network interface coupled to a bus, a memory device coupled to the bus, and one or more processors coupled to the bus, the one or more processors being configured to execute instructions stored on the memory device, wherein when executed, the instructions cause the one or more processors to: verify that the contents of a received timer reset packet include an expected identifier; enter a near-owner mode; and broadcast a near-owner mode packet after a timer expires. In one embodiment, the instructions further cause the one or more processors to generate a set of cryptographic keys based on stored key material, wherein the key material is generated in collaboration with the wireless accessory. In one embodiment, the set of cryptographic keys includes keys for one or more privacy time periods for the wireless accessory, and the operation further includes changing one or more keys used to generate a hardware address with the wireless accessory during each privacy time period. In another embodiment, the predetermined time for the timer to expire depends on at least one of a location and a motion state of the wireless accessory.

[0007] In one embodiment, a method provides: performing a scan via a wireless network interface for beacon advertisements broadcast by wireless devices within range of the wireless network interface; detecting beacon advertisements broadcast by wireless devices; retrieving an identifier broadcast within the beacon advertisement; selectively sending a timer reset packet and an authorization token to the wireless device based on a comparison result between the identifier and at least one expected identifier to keep the wireless accessory in near-owner mode; and allowing the one or more processors to sleep for a predetermined time.

[0008] In one embodiment, the identifier is a hardware address. In one embodiment, the method also provides determining whether a wireless device associated with a beacon advertisement is associated with an account on a mobile electronic device. In one embodiment, the method also provides generating a set of cryptographic keys based on stored key material, wherein the key material is generated in collaboration with a wireless accessory. In one embodiment, the set of cryptographic keys includes keys for one or more privacy time periods for the wireless accessory, and the operation further includes changing one or more keys used to generate a hardware address in conjunction with the wireless accessory during each privacy time period. In one embodiment, at least one processor wakes up after a predetermined time period. In one embodiment, a timer reset packet includes a reset identifier and a channel selection. In some embodiments, the wireless network interface is a Bluetooth network interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a block diagram of a network operating environment for a mobile device according to an embodiment.

[0010] Figure 2 A system for locating a wireless accessory according to an embodiment is shown.

[0011] Figure 3 A system for pairing and locating a wireless accessory according to embodiments described herein is shown.

[0012] Figure 4 is a flow chart illustrating a method for pairing a group of accessory devices according to embodiments of the present invention.

[0013] Figure 5 is a flow chart illustrating a method for use with the device locator system described herein.

[0014] Figure 6 A method for determining a location of a wireless accessory via a device locator server is shown.

[0015] Figure 7 Additional methods for determining the location of a wireless accessory via a device locator server are shown.

[0016] Figure 8 is a flow chart illustrating a method of broadcasting a signal beacon at a wireless accessory according to an embodiment.

[0017] Figures 9 and 10 Operations of a method that may be performed by a detector device according to embodiments described herein are shown.

[0018] Fig.11 The acquisition of signal and ranging data performed by a detector device according to an embodiment is shown.

[0019] Figures 12 to 17 A device locator user interface is shown according to an embodiment.

[0020] Fig.18 is a block diagram illustrating an exemplary API architecture that may be used in some embodiments of the present invention.

[0021] Fig.19 is a block diagram of a device architecture for a mobile or embedded device according to an embodiment.

[0022] Fig. 20 is a block diagram of a computing system according to an embodiment.

[0023] Fig.21 A system for collaboratively performing key generation between an owner device and a wireless accessory according to an embodiment is shown.

[0024] Fig. 22 A process of collaborative key generation according to an embodiment is shown.

[0025] Fig.23 is a flow chart of a process for entering a near owner state and subsequently maintaining a near owner state at a secondary device according to an embodiment.

[0026] Fig.24 is a flow chart of a process for entering a near owner state and subsequently maintaining a near owner state at a secondary device according to an embodiment.

[0027] Fig.25 is a flow chart of a process for entering a near owner state and subsequently maintaining a near owner state at a secondary device according to an embodiment.

[0028] Fig.26 A connection packet for a timer reset packet is shown.

[0029] Fig. 27 is a flow diagram of a process of connecting to and commanding a secondary device according to an embodiment.

[0030] Fig.28 An advertising beacon packet for a wireless accessory is shown.

[0031] Fig.29 A computing system including a security processor according to an embodiment is shown.

[0032] FIG. 30A to FIG. 30C An unwanted tracking user interface on an electronic device is shown according to an embodiment.

[0033] FIG. 31A to FIG. 31C An unwanted tracking user interface on an electronic device is shown according to an embodiment. DETAILED DESCRIPTION

[0034] Embodiments described herein provide techniques for enabling separation notifications, unwanted tracking notifications, and locator services for lost or misplaced devices or items. An accessory device detected near an owner device can be placed in a "near owner" mode. The near owner mode can indicate that the accessory has detected that the owner device associated with the accessory is present nearby. In some embodiments, a method is described for maintaining near owner mode to avoid unnecessary unwanted tracking notifications, inaccurate separation notifications, and reduce the impact on the resources of the owner device (e.g., device battery, execution time on an application processor, etc.).

[0035] Unwanted tracking notifications may occur when an accessory device is detected by a device other than the owner device and the accessory device does not have near owner status. A potential downside to the privacy protection described herein is the risk of allowing an accessory to remain undetected or allowing an accessory to be placed on an individual with malicious intent to track that individual. Therefore, unwanted tracking notifications may be provided to the other device to notify the user of potential unwanted tracking of the accessory device. If near owner mode is not properly maintained in the presence of the owner device due to loss of near owner status, unnecessary unwanted tracking notifications may be presented to non-owner devices even when the accessory device is in the presence of the owner device.

[0036] For example, if a first user with an owner device and a second user with a non-owner device (e.g., a different user account than the first user) travel together (e.g., in a vehicle) to a location (e.g., a defined location such as a store, a park, etc.) and the accessory device does not maintain a near-owner state, the non-owner device's beacon scan buffer may be being scanned from an accessory device (e.g., an Apple Watch) in field mode that is associated with the owner device. ) to receive advertisements. When not remaining in the near-owner state for a certain period of time, the wireless accessory will enter a discoverable wild mode. Heuristics can be applied using sensor data to infer movement or activity context to additionally determine whether to cause the device to enter discoverable wild mode. When in discoverable wild mode, the accessory device will begin advertising a new payload containing a stable identifier. Upon arriving at the next location (e.g., home, another store, etc.), the non-owner device can trigger an unwanted tracking notification due to the accumulation of advertisements received from accessory devices in wild mode (e.g., sending advertisements with a stable identifier) ​​in the beacon scan buffer of the non-owner device that triggers unwanted tracking notifications. In this example, the resulting unwanted tracking notification is a false positive unwanted tracking notification because the accessory device is still near the owner device.

[0037] In some embodiments, a timer reset packet is sent by the owner device to the accessory device to inform the accessory device when to send advertisements to the owner device and to reduce the impact on the owner device while maintaining near-owner mode.

[0038] In some embodiments, the locator service can be a locating device, which can be part of a device group, which is a group of accessory devices (e.g., a pair of earbuds, such as an Apple ), each of which can be independently and individually authenticated and paired with another device. The association of accessory devices in a device group can allow the accessory device to access information to facilitate pairing with other accessory devices within the device group and to find accessories within the device group.

[0039] In various embodiments, description is made with reference to the accompanying drawings. In various embodiments, description is made with reference to the accompanying drawings. However, certain embodiments may be practiced without one or more of these specific details or in combination with other known methods and structures. In the following description, many specific details such as specific configurations, sizes and processes are shown to provide a thorough understanding of the embodiments. In other cases, well-known semiconductor processes and manufacturing techniques are not described in particular detail to avoid unnecessarily obscuring the embodiments. "One embodiment" mentioned throughout the specification refers to the specific features, structures, constructions or characteristics described in conjunction with the embodiments being included in at least one embodiment. Therefore, the phrase "in one embodiment" that appears in multiple places throughout the specification does not necessarily refer to the same embodiment. In addition, specific features, structures, constructions or characteristics may be combined in one or more embodiments in any appropriate manner.

[0040] In the following discussion, a computing device including a touch-sensitive display is described. However, it should be understood that the computing device may include one or more other physical user interface devices. Various applications that may be executed on the device may use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device may be adjusted and / or varied from one application to the next, and / or may be adjusted and / or varied within a corresponding application. In this way, the common physical architecture of the device (such as a touch-sensitive surface) may support a variety of applications with an intuitive and transparent user interface.

[0041] Some processes are described below with regard to some sequential operations. However, it should be understood that some operations in the described operations can be performed in different orders. In addition, some operations can also be performed in parallel rather than in order.

[0042] Figure 1 1 is a block diagram of a network operating environment 100 for a mobile device according to an embodiment. The network operating environment 100 includes a plurality of mobile devices, such as accessory devices 101A and 101B (collectively 101), and a mobile device 102. In some embodiments, the devices may be part of a device group, which is a group of accessory devices (e.g., a pair of earbuds, such as an Apple ), each of which can be independently and individually authenticated and paired with another device. For example, mobile devices 101A and 101B can be accessory devices that can be paired as device group 105. The association of accessory devices in a device group can allow the accessory device to access information to facilitate pairing with other accessory devices within the device group and to find accessories within the device group. In other embodiments, accessory device 101 is a single accessory device rather than part of device group 105.

[0043] Optionally, the device set with the accessory device 101 can be stored in the mobile device through a wired connection, such as a box 103 for holding the accessory device 101. In some embodiments, the box 103 can also be an accessory device that can be paired with the mobile device 102. For example, the accessory device 101 can be such as an Apple and / or In some embodiments, accessory device 101 may not be able to communicate over a wide area network.

[0044] In other embodiments, mobile devices 101 and 102 may each be any electronic device capable of communicating with a wireless network and wireless accessory devices. Some exemplary mobile devices 101 and 102 include, but are not limited to, the following: smartphones, tablet computers, notebook computers, wearable computers (e.g., smart watches or other wearable computing accessories), mobile media players, personal digital assistants, Locator tags, headphones, head-mounted displays, health equipment, speakers, and other similar devices. Each of the mobile devices 101 and 102 may optionally include a user interface, such as the user interface 104 of the mobile device 102. In other embodiments, the mobile device 101 as an accessory device may not have a user interface. The mobile devices 101 and 102 may be third-party devices that use application programming interfaces to access the device locator service. The third-party devices may be provided by different device manufacturers or may be part of different ecosystems (e.g., operating systems) from the mobile devices 101 and 102. The mobile devices 101 and 102 may communicate through one or more wired and / or wireless networks 110 to perform data communications. For example, the wireless network 112 (e.g., a cellular network, a Wi-Fi network) may communicate with a wide area network 114 (such as the Internet) using a gateway 116. Similarly, an access device 118, such as a mobile hotspot wireless access device, may provide communication access to the wide area network 114. Then, the gateway 116 and the access device 118 may communicate with the wide area network 114 through a combination of wired networks and / or wireless networks.

[0045] In some implementations, both voice and data communications can be established through the wireless network 112 and / or the access device 118. For example, the mobile device 102 can make and receive phone calls (e.g., using the VoIP protocol), send and receive email messages (e.g., using the POP3 protocol), and retrieve electronic documents and / or streams, such as web pages, photos, and videos, through the wireless network 112, the gateway 116, and the wide area network 114 (e.g., using the TCP / IP or UDP protocol). In some implementations, the mobile device 102 can make and receive phone calls, send and receive email messages, and retrieve electronic documents through the access device 118 and the wide area network 114. In some implementations, the mobile device 101 and / or the mobile device 102 can be physically connected to the access device 118 using one or more cables, for example, where the access device 118 is a personal computer. In this configuration, the mobile device 101 or the mobile device 102 can be referred to as a "tethered" device. In one embodiment, the mobile device 101 can communicate with the mobile device 102 via a wireless peer-to-peer connection 120. The wireless peer-to-peer connection 120 may be used to synchronize data between devices.

[0046] Mobile device 101 or mobile device 102 can communicate with one or more services, such as telephone service 130, instant messaging service 140, media service 150, storage service 160, and device locator service 170, through one or more wired and / or wireless networks 110. For example, telephone service 130 can enable telephone communication between mobile devices or between a mobile device and a wired telephone device. Telephone service 130 can route voice over IP (VoIP) calls through wide area network 114, or can access a cellular voice network (e.g., wireless network 112). Instant messaging service 140 can, for example, provide email and / or other instant messaging services. Media service 150 can, for example, provide access to media files, such as song files, audiobooks, movie files, video clips, and other media data. Storage service 160 can provide network storage capabilities to mobile device 101 and mobile device 102 to store documents and media files. Device locator service 170 can enable a user to locate a lost or misplaced device that is connected to one or more wired and / or wireless networks 110 at least at some point. Other services may also be provided, including software update services for updating operating system software or client software on mobile devices. In one embodiment, instant messaging service 140, media service 150, storage service 160 and device locator service 170 may each be associated with a cloud service provider, wherein various services are facilitated via a cloud service account associated with mobile devices 101 and 102.

[0047] In some embodiments, accessory device 101A, accessory device 101B, mobile device 102, box 103, and / or device group 105 may register with certificate authority 106. In some embodiments, certificate authority 106 is an entity that issues digital certificates, and the service may be implemented using a group of servers managed by a device manufacturer, service provider, or registration service. The certificate provided by certificate authority 106 may verify the validity of verifiable information received about the device, such as a specific manufacturer of the device, a serial number, an identifier or other identifier of the device group, an indicator that the device is part of device group 105, and / or any other verifiable information. In some embodiments, the device manufacturer may establish device group 105 by grouping the serial numbers of accessory devices in device group 105. In other embodiments, the certificate may be encrypted by device 101, 102, or 103 before being sent to a third party, and may be decrypted at a verification service (e.g., certificate authority or another verification service) when a third party requests verification of information provided by accessory device 101, mobile device 102, box 103, and / or devices within device group 105. In some embodiments, a security token can be provided in the pairing request by the accessory device 101. Additional examples of pairing devices using location services can be found in U.S. patent application Ser. No. 17 / 219,595, filed on Mar. 21, 2021, entitled “Secure Pairing and Pairing Lock for Accessory Devices,” which is incorporated herein by reference in its entirety.

[0048] Mobile devices 101 and 102 may have applications, services, and functions that are locally accessible on the device including location services 180. Mobile device 102 may have a device locator application (e.g., a "find my" application) 190 to utilize device locator service 170 and location services 180 to locate accessory device 101. Locally accessible data may be stored on known locations 182 and safe or trusted locations 184. In some cases, machine learning algorithms 186 may be used to identify known locations 182 and / or safe and trusted locations 184. Although cluster analysis is provided as an example of a machine learning algorithm that may be used, those skilled in the art will recognize that other algorithms may be used to identify potential known or trusted locations. For example, cluster data analysis may be used to identify and classify and provide semantic labels for locations, such as locations frequented by a user. Safe or trusted locations 184 may be explicitly specified or confirmed by a user of devices 102A-B after data analysis. In other cases, known locations 182 or trusted locations 184 may be classified offline and provided by device locator service 170 or a third party (e.g., a database with map information).

[0049] On-device heuristics and / or machine learning models may be used to infer relationships between users and locations based on analysis of locally stored data about frequently visited locations, including locations frequently visited by the user, known locations, and / or any other locations. For example, frequently visited locations such as home, vehicle, workplace, any location frequently visited by a user with a mobile device (e.g., accessory device 101 and mobile device 102), and / or any other location designated by the user as a trusted location 184. Known locations 182 may be commercial locations, public spaces, parks, museums, and / or any other location that a user may frequently visit. Boundary information for the corresponding stored locations may be stored along with the classification type of the location and any semantic tags assigned to the location. The stored information may include a defined set of boundaries or radius distances around a point location to allow the creation of a geo-fence for the location. A geo-fence is a virtual perimeter of a real-world geographic area. A global positioning system (GPS) may be used to create a virtual fence around a location and track the physical location of mobile devices 101 and 102 within the geo-fence boundaries and the entry and exit of the bounded area.

[0050] The machine learning algorithm 186 may include on-device heuristics, machine learning algorithms, or a combination thereof to analyze and assign labels regarding the movement or travel of a device, which is designated as being in an "in transit" state or a "stable" state at a particular location for a certain period of time. The analysis may be performed using various signals from data sources available to the mobile device 102, including but not limited to the following: sensor data, positioning data, calendar data, transit card usage data, application data, historical data regarding travel patterns / routines, and / or any other data accessible to the mobile device 102. [[Perhaps somewhat redundant, in some embodiments, the mobile device 102 may be classified with a "stable" semantic label after remaining within the geographic boundaries of a defined location (e.g., a trusted location 184) for a defined period of time. The positioning data of the mobile device 102 may remain within the boundaries of a geo-fence of a specific location for a certain period of time (e.g., 5 minutes). Sensor data (such as accelerometer data) may indicate that the mobile device 102 is in a stationary state to support an inference that it is stabilized. Application data may support an inference that the mobile device 102 is stabilized, such as that the mobile device is at a calendar appointment location. Application data indicating the type of application in use may also provide an inference of the device being stabilized, such as the use of media applications. Historical data about the user's routines or patterns in travel can be used to determine whether the mobile device 102 is stabilized, such as a bedtime routine at a home or hotel location. The mobile device 102 may be classified as having an "in transit" label based on the user's previous behavior, pattern, or routine and analyzed on the mobile device 102. For example, a user may have a routine of working around the same time every day, and if the data on the device supports the repetition of the pattern, the "in transit" status may be assigned. The speed at which the mobile device moves or enters and exits a known geographic area (e.g., using a geo-fence) may allow an inference that the mobile device 102 is in transit. If the mobile device 102 is detected as accelerating in a known transportation area (e.g., on a road, highway, train route, etc.), the mobile device 102 may be given a "in transit" status. Similarly, if a transportation application / card is used / being used, the mobile device 102 may be designated as "in transit".

[0051] Figure 2A system 200 for locating wireless accessories 201A and / or 201B is shown according to an embodiment. In one embodiment, wireless accessories 201A and 201B (collectively referred to as 201) are another embodiment of accessory devices 101A and 101B (and optional box 103), which can be paired as part of device group 105 and can be used interchangeably throughout the specification. Each wireless accessory includes one or more wireless transceivers and can communicate with a companion device (e.g., mobile device 102) directly or indirectly (e.g., through another device or computer) via a wireless network or a peer-to-peer communication link. Accessory device 101A is shown as being in box 103 and can provide a beacon signal for box 103 and any accessories in box 103. Accessory device 101B is separate from box 103 and is independently and individually able to be found by providing a beacon signal. Some examples of additional wireless accessory devices 101 include, but are not limited to, wireless earbuds, Input devices, charging devices, cases for accessories, headphones, headphones, fitness equipment, health equipment, display devices, external hard drives, other wearable devices (e.g., smart watches, fitness bands, optical head mounted displays) adapters, speakers, and / or other devices. A paired accessory group can be devices of the same type (e.g., speakers, fitness weights, etc.) or different types of devices (e.g., smartphones and credit card readers, etc.). Wireless accessory 201 may also include other wireless devices, such as input devices, including but not limited to credit card reading devices, stylus devices, mice, keyboards, game controllers, or remote controls. In one embodiment, wireless accessory 201 also includes a device that is at least temporarily unable to access a wide area network such as the Internet (e.g., Figure 1 A smartphone, tablet computer, laptop computer, smart speaker device, television, or television set-top box connected to a wide area network 114 (shown in FIG. 1 ). Wireless accessory 201 may also be any other wireless device, including a beacon or locator tag that can be attached to other devices to allow tracking or locating those devices. In one embodiment, wireless accessory 201 may be from a wireless technology standard such as, but not limited to, ) is a device group of accessory devices that are paired with the mobile device 102. The wireless accessory 201 can also communicate with the mobile device 102 via wireless technology, which includes specific implementations of any wireless standards and protocols, such as Wi-Fi Direct, Zigbee, or AirPlay. Although the companion device with which the wireless accessory 201 is paired is generally referred to as the mobile device 102, the companion device is not limited to a mobile device. In some embodiments, the companion device may also include a laptop or desktop device, and may also include some wearable accessories, such as but not limited to a smart watch device or a wearable display.

[0052] In one embodiment, the wireless accessory 201 can periodically transmit a wireless beacon signal. The wireless accessory 201 can use various wireless technologies described herein (e.g., The beacon signal may be transmitted using one of the wireless technologies (e.g., Wi-Fi, etc.), and in one embodiment, ultra-wideband (UWB) radio technology may also be used to send the beacon. The beacon signal may be transmitted using a single wireless technology, one of multiple selectable wireless technologies, or multiple simultaneous wireless technologies. The beacon signal may transmit a beacon identifier that includes information that specifically identifies an individual wireless accessory 201A or 201B and / or device group 105. In one embodiment, the beacon identifier is a public encryption key associated with the device.

[0053] The beacon signal may also transmit information about the wireless accessory 201, such as device status information and / or verifiable information. The device status information in the beacon signal may include, but is not limited to, the following: beacon type, device classification, battery level, any predefined device status, device status, lost status, alarm status, separated from owner status, owner nearby status, state of proximity to one or more accessory devices 101 in the device group, wired or wireless connection status, state of physical connection to one or more accessory devices 101 in the device group, pairing status indicating whether the accessory device is paired, pending pairing status, battery life status, charging status, and / or any other status information. The lost or "separated from owner" status may indicate that the wireless accessory 201 has determined that it has been lost or has been placed in a lost state by the owner of the device. The alarm state may indicate that the wireless accessory 201 is placed in a state where the device should trigger an alarm if the device moves from its current location. The near owner state may indicate that the wireless accessory 201 has detected that a mobile device 102 associated with the owner of the accessory is nearby.

[0054] In some embodiments, the verifiable information may include any information that may be needed to establish trust or authorization, i.e., the pairing process and / or the search process may continue, wherein the device presents the verifiable information. For example, the verifiable information may include information established by the device manufacturer, such as a serial number or a set of serial numbers in the device group 105. In some embodiments, the verifiable information may include the state or status information of the device. The verifiable information may include, but is not limited to, the following: device type, member of the device group, serial number, device group, serial number of other devices in the device group, state or status information, software version, and / or any other verifiable information. The verifiable information may be sent to a certificate authority 106 or other certification service to verify the received information presented by the device to another device. The verifiable information may be encrypted and / or sent with a token to allow further verification of the device.

[0055] In some embodiments, the beacon signal can be detected by a detector device 202 that is locally near the wireless accessory 201A or 201B to use crowdsourcing to locate the lost wireless accessory 201. The detector device 202 can be a device similar to the mobile device 102 and can receive and transmit data over the wide area network 114, and the reception and transmission are performed using similar wireless technology as the wireless accessory 201 (e.g., In particular, the detector device 202 may receive data using a wireless protocol through which the beacon signal is transmitted. The detector device 202 may determine the location using one or more location and / or positioning services, including but not limited to a satellite positioning service 206 or a ground positioning system using RF signals received from a wireless base station 205 such as a Wi-Fi access point or a cellular tower transmitter of a cellular telephone network. In one embodiment, the detector device 202 periodically stores its location determined based on one or more location and / or positioning services. The stored location may be associated with a timestamp for which the location is determined. When the detector device 202 receives a beacon signal from the wireless accessory 201, the detector device 202 may transmit the location of the detector device 202 to the device locator server 203 via the wide area network 114. The timestamp used to determine the location of the detector device 202 may be associated with the timestamp when the beacon signal is received to associate the geographic location with the received beacon signal.

[0056] In the event that the wireless accessory 201 provides a public key within the beacon signal, the detector device 202 can encrypt the determined location data and transmit the encrypted location data to the device locator server 203 via the wide area network 114. In one embodiment, additional data can be encrypted and transmitted with the location data, or transmitted to the device locator server 203 without encryption. For example, a received signal strength indication (RSSI) of the beacon signal can be transmitted with the location data. The RSSI data can then be used to determine the distance of the wireless accessory 201 from the detector device 202 and assist in triangulation on the owner device. In the event that the RSSI data is transmitted in an unencrypted state, in one embodiment, the server can use the RSSI information to reduce noise by discarding very weak signals if other stronger signals are present. In one embodiment, UWB ranging data can also be provided, where such data is available.

[0057] In one embodiment, the detector device 202 can behave differently upon receiving a beacon signal from the wireless accessory 201 depending on the device state communicated by the wireless accessory 201. For a standard beacon signal, the detector device 202 can place the encrypted location data in a queue and transmit the location data to the device locator server 203 during a periodic transmission window. However, if the wireless accessory 201 is indicating an alarm state, the detector device 202 can immediately transmit the location data to the device locator server 203. Additionally, if the beacon signal of the wireless accessory 201 indicates that the accessory is near the owner of the accessory, the detector device 202 may not transmit the location data to the device locator server 203. Alternatively, the detector device 202 can delay the transmission of the encrypted location data.

[0058] If the owner of the wireless accessory 201 wishes to locate the wireless accessory, the owner may access the device locator user interface 204 on the mobile device 102. The device locator user interface 204 may be associated with a device locator application that is used to locate electronic devices and accessories registered to a user's online account (such as a cloud service account or another type of online account). The device owner may use the device locator UI 204 to query the device locator server 203 for location data that may have been transmitted to the device locator server by the detector device 202 of the wireless accessory 201. In one embodiment, the mobile device 102 may transmit a public encryption key associated with the wireless accessory 201 to the device locator server 203. The device locator server 203 may then return any stored location data corresponding to the public encryption key. The location data returned to the mobile device 102 may be encrypted data encrypted by the detector device 202 using the public encryption key. The mobile device 102 may decrypt the encrypted location data using the associated private key. The decrypted location data is then processed by the mobile device 102 to determine the most likely location of the wireless accessory 201. In various embodiments, the most likely location of wireless accessory 201 can be determined by triangulation from multiple receive locations and using other data such as beacon signal RSSI associated with each location and timestamp or UWB ranging data included within the location data.

[0059] Figure 3A system 300 for pairing and locating a wireless accessory is shown according to embodiments described herein. In one embodiment, a mobile device 102 (e.g., an example of device 101A, 101B, or 103) of a user of a wireless accessory 201 can present an accessory pairing UI 302 through which the user can pair the mobile device 102 with the wireless accessory 201. During an initial pairing (305) between the mobile device 102 and the wireless accessory 201, a public key exchange (310) can be performed between the mobile device and the wireless accessory 201. In one embodiment, during the public key exchange (310), the mobile device 102 and the wireless accessory 201 exchange public keys of a public key pair generated by the device and the accessory 201. In one embodiment, the public key exchange (310) is a one-way transmission in which the mobile device 102 transmits a public key of a public / private key pair to the wireless accessory 201. Additionally or alternatively, the public key exchange (310) can be a Diffie-Hellman key exchange in which the device and the accessory establish a shared secret between the two parties. In one embodiment, the public key exchange (310) additionally uses elliptic curve cryptography to establish a shared secret. For example, Elliptic Curve Diffie-Hellman (ECDH) can be used to implement the establishment of a public key pair and one or more shared secrets. In one embodiment, the one or more shared secrets include an anti-tracking secret that can be used by wireless accessory 201 to periodically derive additional public keys.

[0060] After the wireless accessory 201 has been paired with the mobile device 102, the wireless accessory 201 can periodically broadcast a beacon signal 301 that includes device status information and a beacon identifier. In one embodiment, the beacon identifier is a public key derived from a shared secret established during the public key exchange (310). In addition, the wireless accessory 201 can periodically perform public key derivation (315) to generate a new public key and begin broadcasting the new public key as a beacon identifier. The public key is a K-byte key, where a new K-byte key is generated every M minutes. The values ​​K and M can vary between embodiments. In one embodiment, a 28-byte K value is used. In one embodiment, a 27-byte K value is used. The value K can be determined at least in part based on a beacon length associated with a wireless protocol used to transmit the beacon signal 301. In one embodiment, the beacon signal can be transmitted in accordance with a low power radio protocol such as A variant of the beacon advertising packet associated with low power consumption).

[0061] In one embodiment, the value M is 15 minutes, such that a new K-byte key is generated every 15 minutes. The public key can be deterministically derived based on the timestamp and anti-tracking secret generated during the public key exchange 310. The public key derivation (315) process enables the wireless accessory 201 to use different keys over time, thereby preventing a particular key from being associated with a particular device for a long time. The key can be derived based on an anti-tracking secret known only to the mobile device 102 and the wireless accessory 201, thereby allowing the mobile device 102 and only the mobile device to determine which public key the wireless accessory 201 will broadcast at any given timestamp. The anti-tracking secret can be generated along with the ECDH public key and transmitted to the wireless accessory 201. The anti-tracking secret can then be used to enable the wireless accessory 201 to generate a public key sequence P i In one embodiment, the public key sequence P i =λ i P, which defines the scalar or exponential value λ i Group operations with group elements, such as elliptic curve points P. Scalar or exponent value λ = KDF(AT,i), where KDF is a key derivation function, AT is an anti-tracking secret, and i is a counter or timestamp.

[0062] In one embodiment, backtracking resistance can be enabled to protect the anti-tracking secret in the event that the wireless accessory 201 is compromised. When backtracking resistance is enabled, the anti-tracking secret is transmitted to the wireless accessory 201, but the wireless accessory does not retain the anti-tracking secret. Instead, the accessory calculates the value λ i+1 =H(λ i || time), where λ0=AT and H is a cryptographic hash function. The wireless accessory 201 then stores λ i for a given period of time i. If wireless accessory 201 is compromised, only the current and future values ​​of λ for i are exposed i In one embodiment, reverse tracking resistance is achieved by periodically changing λ i The data is written to the non-volatile memory of the wireless accessory 201 for execution.

[0063] In one embodiment, the wireless accessory 201 can transmit a beacon signal 301 every two seconds, but other beacon rates can be used and can vary in certain circumstances. For example, when in a near owner state, the wireless accessory 201 can reduce the beacon rate. The beacon rate can also vary based on events triggered by an accelerometer. For example, when in an alarm state, the wireless accessory 201 can increase the beacon rate, which can be triggered by an accelerometer on the wireless accessory 201.

[0064] If, after transmitting beacon signal 301, wireless accessory 201 receives a reply from a mobile device 102 associated with a user of the accessory indicating that mobile device 102 is within range of the wireless accessory, then wireless accessory 201 can enter the near owner state. Additionally, the amount of data transmitted by beacon signal 301 can be reduced while the wireless accessory is in the near owner state. In one embodiment, the rate at which new public keys are generated can also be reduced while the wireless accessory is in the near owner state.

[0065] The wireless accessory 201 can enter an alert state upon receiving a message from the mobile device 102 indicating that the wireless accessory 201 should enter an alert state. While in the alert state, the wireless accessory can initially enter an alert state in which the wireless accessory 201 can reduce or stop transmitting locator beacon signals, but other types of wireless signaling can continue to exist. The wireless accessory 201 can remain in the alert state until the mobile device 102 deactivates the state or an alarm is triggered. In one embodiment, the alarm can be triggered when movement is detected, for example, via an accelerometer within the wireless accessory 201. In one embodiment, the alarm can also be triggered when it is detected that the wireless accessory has moved out of range of the mobile device and is no longer in a near owner state. When the alarm is triggered, the rate of the beacon signal 301 can increase to increase the speed at which the wireless accessory 201 can be located.

[0066] The beacon signal 301 transmitted by the wireless accessory 201 can be detected by a set of detector devices 303 (the detector device can be the detector device 202) and / or the mobile device 102, which are other electronic devices that can receive the beacon signal transmitted by the wireless accessory and transmit the location and other data associated with the beacon signal 301 to the device locator server 203 via the wide area network 114. In one embodiment, the set of detector devices 303 includes a variation of the mobile device 102, or can be other types of electronic devices. For example, the set of detector devices 303 can perform operations (320) to associate the beacon signal 301 received from the wireless accessory 201 with the device location associated with the detector device 303. As described in detail in relation to FIG. Figure 2 The device location may be determined via a satellite positioning service or a ground positioning system using RF signals received from a wireless base station (e.g., a Wi-Fi access point or a cellular tower transmitter). In one embodiment, the group of detector devices 303 may also include fixed devices that can receive beacon signals 301, such as smart speaker devices, televisions, or television set-top boxes.

[0067] The set of detector devices 303 may encrypt the location data using the beacon identifier (e.g., a public key) received within the beacon signal 301 and send the location data (325) to the device locator server 203. The data sent by the set of detector devices 303 is sent anonymously, and identification information of the detector devices is not stored with the data sent by the detector devices.

[0068] The device locator server 203 may store the encrypted location data in a data repository 304, which in one embodiment may be a distributed database with multiple nodes. A hash of the beacon identifier / public key of the attachment may be sent together with the encrypted location data. The encrypted location data may be stored in a database node based on a hash of the beacon identifier. The encrypted location data may be indexed by the device locator server 203 using a hash of the beacon identifier. Sending a hash of the beacon identifier instead of a complete beacon identifier may prevent the complete beacon identifier from being stored in the server. Other information may also be sent and stored in an encrypted or unencrypted state with the location data. Other information may include a timestamp of when the beacon signal 301 was received, RSSI information of the received beacon, and / or ranging information such as determined via UWB ranging.

[0069] When a user or owner of the wireless accessory 201 wishes to locate the accessory, the user or owner may access the device locator UI 204 on the mobile device 102. The device locator UI 204 may be associated with a locator application 190 or feature of the mobile device 102. The device locator UI 204 may also have a web-based interface that may be accessed from the mobile device 102 or another type of electronic device, such as a laptop or desktop device. Upon loading the device locator UI 204, the mobile device 102 may send a request (330) for location data to the device locator server 203. The request 330 may include a set of public keys or public key hashes that may be used as beacon identifiers for beacon data. The mobile device 102 may generate this set of public keys based on secret information held by the mobile device 102 and the wireless accessory 201 and a timestamp at which the mobile device 102 wishes to receive location data. In one embodiment, this set of public keys is a sequence of public keys P generated based on a secret anti-tracking key. i . Public key sequence P i Matching sequence d with the private key i The mobile device 102 may generate a public key sequence and a corresponding public key sequence d i , where i is a counter or timestamp. In one embodiment, the mobile device 102 may generate and send a public key for the previous 24 hours (or a hash of the public key for the previous 24 hours) in the request 330. If no data for a 24-hour public key is found, the mobile device 102 may send a key generated in an earlier time period, returning to a predetermined location data retention limit.

[0070] In one embodiment, encrypted location data is stored and indexed based on a hash of a public key rather than a public key to prevent providers of location service data from storing data that can be used to tie the encrypted location data to a specific device and, therefore, to a specific user or user account. The probe device may send a hash of a public key broadcast within a beacon signal 301 associated with the observed location. The owner of the device may query the device locator server 203 using the hash of the public key determined for the query period.

[0071] In some embodiments, if a location query is to be performed via a web-based interface from an electronic device, such as a laptop or desktop device, a key may need to be sent to the electronic device to enable decryption of the location data. In one embodiment, the decryption key for the location data may be sent to a server that provides a web-based interface to enable the server to decrypt the location data at least when viewing the location data through the web-based interface. Prior to displaying the location data via the web-based interface, a notification may be presented to inform the user that the location decryption key is being temporarily shared with the web-based interface server to enable decryption and presentation of the location data. In one embodiment, the sharing of the location decryption key may be performed via automatic and temporary authorization of location query permissions for a proxy account associated with the web-based interface.

[0072] In one embodiment, the wireless accessory 201 can be placed in a light lost mode. In the light lost mode, a set of future public keys can be generated for the wireless accessory and transmitted to the device locator server 203. The device locator server 203 can then notify the mobile device 102 if any location data corresponding to a key in the set of future public keys is received. In one embodiment, a detector device that sends the location of the wireless accessory in the light lost mode can be directed by the device locator server 203 to relay a message to the wireless accessory 201 that notifies the wireless accessory that it is in the light lost mode. A similar mechanism can also be used to relay a message to the wireless accessory 201 that places the accessory in an explicit lost mode. The user can enable the explicit lost mode via the device locator UI 204. In the explicit lost mode, the wireless accessory 201 cannot be paired with another device unless it is unlocked by the owner. Additional examples of paired devices using location services can be found in U.S. Patent Application No. 16 / 543,227, filed on August 16, 2019, entitled "A System and Method for Locating Wireless Accessories," which is incorporated herein by reference in its entirety.

[0073] Figure 44 is a flow chart illustrating a method for pairing a set of accessory devices according to embodiments herein. Mobile device 102 can receive a pairing status from first accessory device 101A indicating whether first accessory device 101A is paired (402). Pairing exists between the devices when mobile device 102 has access to at least one key associated with the first accessory device of a user account (e.g., a cloud-based account) of mobile device 102. Pairing status, status information, and / or verifiable information can be provided in a beacon signal indicating whether first accessory device 101A is currently paired, pending pairing, or unpaired.

[0074] If the first accessory device 101A is not currently paired with the mobile device 102 according to the pairing status, the pairing process can be optionally started (404), such as Figure 5 As shown. In some embodiments, the pairing state may indicate that the pairing is pending for the first accessory device 101A, and the device group profile of the device group 105 may be retrieved from the database of the device locator server 203. The device group profile may be part of the data model of the device group, with crowdsourced location data about the device locator service 170. The device group profile may be stored on the mobile device 102 and synchronized between devices linked to a cloud-based account. In addition, the device group profile may be stored in a database on the mobile device 102 and the device locator server 203. For example, the device group profile may record the relationship between the accessory devices, status information, and verifiable information received from the accessory device and / or device manufacturer. The device group profile may be updated by information received from the accessory device 101 via the mobile device. The device group profile may include, but is not limited to, the following information: the number of accessory devices in the device group, the number of paired devices, the serial number of the accessory devices in the device group, the pairing status of the accessory devices, and any other information used to provide the device location service 170. Thus, any state and / or verifiable information previously stored in the device group profile can be compared to state information and / or verifiable information received from devices in device group 105 and stored in the device profile of device group 105. In some embodiments, if there is a mismatch of information between the information received from first accessory device 101A and the device profile, and / or if the verifiable information received from first accessory device 101A cannot be verified, the pairing process can cease. Each member device or accessory device 101 that is part of device group 105 can be a beaconing peripheral device that can be individually identified to allow all accessory devices 101 in device group 105 to be found and verified.

[0075] The first accessory device 101A can provide verifiable information in the beacon signal that can be verified by a certificate authority or other verification service that the first accessory device 101A has a serial number that is consistent with devices from the device group 105, as expected by the device manufacturer or user-defined device group. In addition, the certificate authority or other verification service can use the verifiable information to verify that the first accessory device 101A has a specific device manufacturer. Those skilled in the art will recognize that there are many ways to verify the information provided by the first accessory device, which can be performed before continuing the pairing process to confirm that the first accessory device can be trusted.

[0076] Alternatively, if first accessory device 101A does not provide verifiable information, the pairing process cannot proceed. An embodiment can request first accessory device 101A to provide verifiable information (e.g., cryptographically verifiable information such as a certificate and / or token) for first accessory device 101A to initiate pairing, the verifiable information including, but not limited to, the following: a serial number, a manufacturer identifier, a software version, an indication that the accessory device is part of a device group of accessory devices, expected accessory device identifiers of other accessory devices in the device group, an expected number of accessory devices in the device group, and / or any other information. In one embodiment, the verifiable information can be cryptographically verified and authenticated by certificate authority 106.

[0077] A request for information about accessory devices in a device group can be sent to first accessory device 101A (406). For example, the requested information can include an indication that accessory device 101A is part of a multi-part device or device group 105, the number of devices in device group 105, and the number of devices proximate to first accessory device 101A in the device group (406). The received accessory device information about device group 105 can be stored in a device group profile and referenced by mobile device 102 for a pairing process.

[0078] Information about a second accessory device 101B in device group 105 may be received (408). Information about second accessory device 101B received from first accessory device 101A may assist in further pairing of remaining unpaired accessory devices in device group 105. In one embodiment, if second accessory device 101B is close to first accessory device 101A, first accessory device 101A may send verifiable information about second accessory device 101B. If the second accessory device is close (410), a continue pairing message may be sent to the second accessory device to attempt to pair the second accessory device 101B. If the second accessory device is not close and / or pairing is unsuccessful, the verifiable information of the second accessory device may be stored in the corresponding device group profile. The second accessory device 101B information may be stored in the device group profile so as to be accessible to mobile device 102 for later attempts to pair the second accessory device 101B, and the pairing state of the second accessory device may be set to "pairing pending". Alternatively, if the received information from the second accessory device 101B is consistent with the verifiable information from the first accessory device 101A, the pairing process may be completed in Figure 5 Continue to pair the second accessory device 101B. For ease of description, only pairing of two accessory devices is described, and those skilled in the art will recognize that when the accessory devices in the device group provide verifiable information to the mobile device 102, pairing can continue for any number of accessory devices.

[0079] Information about the number of parts, received information about the second accessory device, and any other status information and / or verifiable information for device group 105 may be stored (412). If a device profile for device group 105 does not exist, a device group profile for device group 105 may be created. The device profile may be updated to store information about device group 105 received from accessory device 101 and / or mobile device 102. Information that may be stored in the device group profile includes, but is not limited to, the following: verifiable information received on devices in device group 105, the last received beacon signal received from any device within device group 105 (e.g., status, advertisement, proximity information, location data, etc.), and any other information for pairing and / or using devices in device group 105. Optionally, for the first and / or second accessory device 101, pairing may continue with other proximity devices (414). The next device to be paired may be considered the first accessory device, and the process may continue (402).

[0080] Figure 5 is a flow chart illustrating a method for use with the device locator system described herein. Figure 5 A method 500 for pairing a mobile device with a wireless accessory 101 is shown. Aspects of the method 500 are also described in Figure 2 and Figure 3For example, the following description of operations involves mobile device 102, wireless accessory 201, and device locator server 203.

[0081] like Figure 5 As shown, method 500 includes an operation of performing an initial pairing with a wireless accessory (502). The initial pairing may be During initial pairing, the mobile device and the wireless accessory can exchange identifiers, keys, or other credentials that enable wireless data exchange between the mobile device or another electronic device and the wireless accessory. In one embodiment, initial pairing with a wireless accessory can include the exchange of credentials associated with the wireless protocol for which pairing is performed, thereby allowing all data exchanged wirelessly to have at least a first layer of encryption.

[0082] The mobile device can then generate a public / private key pair and one or more additional shared secrets (504). The device can then send the public key and the one or more additional shared secrets to the wireless accessory (506). A variety of key generation techniques can be used. In one embodiment, a variant of ECDH is used to generate a public key pair for encryption. In one embodiment, the one or more additional shared secrets can include an anti-tracking secret that enables the wireless accessory to derive a new public key based on an existing public key.

[0083] After generating the public / private key pair and one or more additional shared secrets, the mobile device may store the public / private key pair in a key store (508). In one embodiment, the key store is a cloud-based key store that can be synchronized with other devices associated with the same cloud service account or a series of cloud service accounts to which the mobile device and the wireless accessory are associated. The cloud-based key store allows the wireless accessory to be located by other synchronized devices. The mobile device may then register the wireless accessory with a device management server (510). Registering the wireless accessory with the device management server may form an association between the wireless accessory and the cloud service account to which the mobile device is associated. In some embodiments, the mobile device may register the wireless accessory with a device group 105. Information stored in a device group profile of a device group 105 may also be synchronized between devices bound to a cloud service account (e.g., a user account). The device management server may communicate with other cloud-based servers such as Figure 2 and Figure 3 The other cloud-based server is associated with a device locator server 203) for facilitating cloud-based services accessible to mobile devices.

[0084] Figure 6 A method 600 for determining a location of a wireless accessory via a device locator server 203 is shown. Figure 7An additional method 700 is shown for determining the location of a wireless accessory via the device locator server 203. In one embodiment, by Figure 6 and / or Figure 7 The location data retrieved by the illustrated method may include data of the accessory devices 101 in the device group 105. In another embodiment, the method may be executed for each accessory in the device group 105. Figure 6 and / or Figure 7 As shown in the method. Figure 6 As shown, method 600 includes an operation of an electronic device launching a device locator UI (601). In response to launching the device locator UI, an electronic device, which may be a mobile device 102 as described herein, or another electronic device associated with the same cloud service account as the mobile electronic device 102, may perform operations to generate a set of public keys (602) included in a beacon signal broadcast by the wireless accessory during a first time period. The first time period may be, for example, the previous 24 hours. The electronic device knows the frequency with which the wireless accessory generates new public keys, and using a shared secret generated with the wireless accessory, a set of public keys corresponding to the keys generated by the wireless accessory during the first time period may be generated. The electronic device may then send the set of public keys in a request to the device locator server 203 to send location data corresponding to the set of public keys (603). In one embodiment, the location data sent by the server in response to the request will be encrypted using a public key transmitted as a beacon identifier of the wireless accessory. The electronic device may decrypt the encrypted location data received by the server using a private key generated during the initial pairing with the wireless accessory (604). The electronic device may then process the location data to determine the highest probability location of the wireless accessory (605).

[0085] Processing location data may include a variety of different operations. In one embodiment, the location data includes latitude and longitude information and a timestamp that determines the location. The electronic device may perform triangulation based on the timestamp and remove noise or abnormal locations. In one embodiment, the location data specifies the location of the detector device that detected the beacon. The location data may also include UWB ranging information and / or RSSI information of the beacon detected by the detector device. The electronic device may analyze the UWB ranging information and / or RSSI information in the context of the device location to obtain a more accurate location of the wireless accessory. Data that may be transmitted by the detector device and used for location processing is in Fig.12 and described below.

[0086] like Figure 7As shown, method 7 includes operations that can be performed when a device locator server does not have location data to provide to an electronic device in response to a request. In the case of a device group, an electronic device (e.g., mobile device 102) can provide location data about devices in device group 105. The electronic device can generate a first set of public keys (701) included in a beacon signal broadcast by a wireless accessory during a first time period. The first time period can be, for example, 24 hours, but other initial search time periods can be used. The electronic device can perform subsequent operations to request the device locator server to send location data corresponding to the first set of public keys (702). If the data is returned by the server (703, "yes"), the electronic device can use the private key corresponding to this set of public keys to decrypt the location data received from the server (box 709).

[0087] If the server does not return data (703, "No"), the electronic device can generate a second set of public keys included in a beacon signal broadcast by the wireless accessory during a second time period (704). The second time period can be 24, 48, or other number of hours before the first time period. The electronic device can then request the device locator server to send data corresponding to the second set of public keys (705). If the server returns data in response to the request (706, "Yes"), the method 700 can proceed to box 709, where the electronic device decrypts the received data. If the server does not return data (706, "No"), or the server sends a reply indicating that the data is not available, the method 700 includes: the electronic device can widen the search time by continuously requesting earlier time periods until the maximum time period is reached (707).

[0088] Figure 8 is a flow chart illustrating a method 800 of broadcasting a signal beacon at a wireless accessory according to an embodiment. Aspects of the method 800 are also described in Figure 2 and Figure 3. The method 800 includes the wireless accessory deriving a public key (block 802). The public key may be derived based on a shared secret and a timestamp determined based on a clock or timing device of the wireless accessory. Optionally, a determination is made as to whether the wireless accessory is part of a device group (804). If the wireless accessory is part of a device group (804), status information and / or verifiable information of other accessory devices 101 in the device group 105 is provided in the beacon signal (806). The wireless accessory may indicate status information and / or verifiable information, such as whether any other wireless accessory in the device group is close, connected (physically or wirelessly), and / or any other information about other wireless accessories in the device group 105. In one embodiment, a set of bits included in the beacon signal may represent each accessory in the device group, and setting a Boolean value (e.g., true (1) or false (0)) may indicate whether the corresponding accessory is close to and / or connected to the accessory device that sent the beacon signal. Alternatively, if the wireless accessory is not part of the device group (804), no information is provided on the device group. The wireless accessory can then transmit a beacon signal at a first frequency, wherein the beacon signal includes the public key (808). The first frequency can be variable, and in one embodiment is one beacon every two seconds.

[0089] After transmitting the beacon signal, the wireless accessory can listen for a response from the owner device (810). If the wireless signal receives a response from the owner device (810, "yes"), the wireless accessory can enter a near owner state (812) and begin transmitting beacon signals at a second, lower frequency (816). If the wireless accessory does not receive a response from the owner device (810, "no"), the wireless accessory can continue to send beacons at the first frequency (814).

[0090] The method 800 also includes rotating the public key once every M minutes by the wireless device when sending beacons, where the value of M can vary between implementations and / or based on the device state. Based on a timer expiration, a counter, or other mechanism, the wireless accessory can determine whether the accessory has entered a new key time period (818). Although the wireless accessory has not yet entered a new key time period (818, "No"), the accessory can continue to send beacons using the current public key (822). When the wireless accessory detects that it has entered a new key time period (818, "Yes"), the accessory can derive a new public key using the current timestamp (box 820). In one embodiment, the new public key can be derived using an existing public key, a timestamp, and an anti-tracking secret.

[0091] Figures 9 and 10 900 operations that may be performed by a detector device according to embodiments described herein. Aspects of method 900 are also described in Figure 2 and Figure 3 Shown in.

[0092] like Fig. 9 As shown, method 900 includes the detector device performing periodic beacon scans using a wireless baseband processor when an application processor of the detector device is in a low power mode (901). Although beacon scans can also be performed when the application processor is in an active state, beacon scans can be performed by the wireless processor and the radio device receiver as a low power operation when the detector device is idle, inactive or otherwise in a low power state. The detector device can store a timestamp and a beacon identifier to a beacon scan buffer for any beacon data received by the detector device (902). In one embodiment, the beacon identifier is a public key generated by the wireless device based on the timestamp and a shared secret generated using the owner's mobile device.

[0093] The method 900 also includes performing, by the probe device, a periodic Wi-Fi scan using the wireless processor while the application processor is in the low power mode (903). Although the Wi-Fi scan may also be performed while the application processor is active, the Wi-Fi scan may be performed by the wireless processor and the radio device receiver as a low power operation when the probe device is idle, inactive, or otherwise in a low power state. The probe device may then store a Wi-Fi service set identifier (SSID) and a scan timestamp to a Wi-Fi scan buffer on the probe device (904).

[0094] In one embodiment, the Wi-Fi scan buffer is a rolling buffer that stores the most recently detected SSIDs while overwriting earlier detected SSIDs. In one embodiment, the beacon scan buffer can be a fixed size buffer with space for a predetermined number of entries. When the beacon scan buffer becomes full, the probe device can wake up the application processor (905) and associate those beacon scans with the most recently detected SSIDs in the Wi-Fi scan buffer. If the beacon indicates that a beacon signal was received from a device group (906), a set of device locations corresponding to the received beacon can be performed based on the Wi-Fi scan buffer data for the beacon signal from the device group 105 (910). For example, if a beacon signal is received from a first accessory device from the device group 105, and the beacon signal includes information about a set of proximity devices that are physically or wirelessly connected to the first accessory device, the last known location of the first accessory device can be attributed / stored to each of the first accessory device and the proximity devices in the device group 105. Alternatively, the correlation can enable the probe device to determine a set of device locations corresponding to the received beacon based on the Wi-Fi scan buffer data (908).

[0095] Method 900 Fig.10, and includes: if other location data is available, the detector device associates the device location from the Wi-Fi scan buffer data with the other location data (1007) to generate a refined device location. If a refined device location is generated, the detector device may optionally combine the beacon data with the refined device location (1008). The detector device may also add signal strength (RSSI) and / or ranging data to the location data (1009). When the detector device receives a beacon signal, signal strength and ranging data (e.g., UWB ranging data) may be collected. The detector device may then encrypt the location data with one or more public keys received in the beacon data (1010). The signal and ranging data may be encrypted together with the location data, or may be sent unencrypted together with the encrypted location data. The detector device may queue the encrypted location data for transmission to a device locator server (1011). The device locator server may be one of a plurality of cloud service servers, typically communicating in a batch and throttled manner. A batch of encrypted data may be collected and placed in a transmission queue until a transmission interval is reached, during which the probe device may transmit the data to the cloud service server (1012).

[0096] Fig.11 1 shows the collection of signal and ranging data performed by a detector device according to an embodiment. In one embodiment, the detector device 202 can collect signal strength information (e.g., RSSI 1104A-1104N) for beacon signals 301 received from the wireless accessory 201 across multiple locations 1102A-1102N. The detector device 202 can also represent multiple detector devices, such as Figure 3 A group of detector devices 303 in which each detector device detects beacon signals at different locations. Each detector device 202 can send different locations and signal strengths, and the location and signal strength data received from multiple detector devices will be aggregated by the device locator server. In one embodiment, where the detector device and the wireless device each include a UWB radio device, if the detector device and the wireless device are within the range of the UWB transmission, UWB ranging 1106 can be performed. The UWB ranging and signal strength data can be transmitted to the device locator server together with the location data of the detector device.

[0097] The owner device can retrieve RSSI and / or UWB information from the device locator server along with location data, which in one embodiment is provided in the form of latitude and longitude information and a timestamp determining the location. The owner device can then use the location data, timestamp, and signal information to triangulate the most likely location of the wireless accessory 201.

[0098] Figures 12 to 17A device locator UI 204 is shown according to an embodiment. Fig.12 A first graphical user interface of the device locator UI 204 is shown showing notifications of various wireless accessories for the user, in accordance with an embodiment. Figures 16 to 21 A device locator UI 204 is shown according to an embodiment. Fig.12 A first graphical user interface of a device locator UI 204 is shown showing notifications of various wireless accessories of a user in accordance with an embodiment. The device locator UI 204 can cause a detached notification 1202 to be presented on a home screen 1201 of an electronic device 1200 . Fig.13 A second graphical user interface of the device locator UI 204 is shown that enables viewing of left-behind accessory devices on a map, adding a trusted location, or requesting notifications for an item be stopped, in accordance with an embodiment. Fig.14 A third graphical user interface of the device locator UI 204 according to an embodiment is shown, which enables locating the accessory device 101 in the device group 105. As shown, the electronic device 1500 including the mobile device 102 can be used to scan the device group 105 for accessory devices (as shown by the "L" left and "R" right options in 1404) using the location data from the beacon signal and using the discovery method described herein. The selectable element 1405 can be selected to continue to find the accessory device in the device group 105.

[0099] Fig.15 A fourth graphical user interface of a device locator UI 204 is shown that enables accessory devices 101 (including devices in device group 105) to be found on a map in accordance with an embodiment. Fig.16 A fifth graphical user interface of a device locator UI 204 according to an embodiment is shown that enables a wireless accessory to be set to a lost mode or to notify when found. The device locator UI 204 can be displayed on an electronic device, which can be a mobile device 102, or any other type of electronic device described herein. Fig.17 A sixth graphical user interface of device locator UI 204 is shown that enables a wireless accessory to add a trusted location in accordance with an embodiment.

[0100] like Fig.13As shown, the device locator UI 204 can present a unified graphical interface on the electronic device 1300 through which a variety of different types of devices and accessories can be located, including wireless devices with network or cellular access and wireless accessories without local network access. The device locator UI 204 may include a map 1304 with a marker 1505 that shows the current or last known location of the wireless device or accessory. The marker 1505 can be an icon, image, graphic, or any other user interface element that identifies the accessory and communicates the location of the accessory. The selectable element 1306 in the device locator UI 204 can present a description or name of the wireless device or accessory, and can show an estimated distance between the wireless device or accessory and the current location of the electronic device 1500, such as Fig.15 shown.

[0101] like Fig.15 As shown, the device locator UI 204 can present a fourth user interface that enables the wireless accessory to view the item 1503 and the distance from the electronic device 1500. In one embodiment, the second user interface can be responsive to selecting Fig.13 The second user interface can present a user interface element 1502 representing and / or describing the wireless accessory under consideration, as well as a map 1501 and a marker 1502 showing the current or last known location of the wireless accessory.

[0102] like Fig.16As shown, the device locator UI 204 may present a fifth graphical user interface that enables the wireless accessory to be set to lost mode. In one embodiment, when the wireless accessory cannot be located via the device locator UI 204, the map 1601 will not display a mark indicating the location of the accessory. The device locator UI 204 may present a user interface element 1604 representing and / or describing the wireless accessory under consideration and a set of optional user interface elements. An optional user interface element 1606 may present an option for notifying the user when the accessory is found. When notification when discovery is enabled, in one embodiment, the wireless accessory may be placed in a light lost mode. An electronic device associated with the device locator UI 204 may generate a set of public keys, and the wireless accessory will broadcast this set of public keys together with the beacon signal during a future time period (e.g., the next 24 hours, the next 48 hours, etc.). If the detector device detects a signal using one of the future keys, the device locator server may notify one or more electronic devices associated with the user. The device locator UI 204 may present a selectable user interface element 1605 to allow the user to give the user the option of requesting the lost device to play a sound. If a connection is established with the lost device from device group 105, a request to play the sound may be sent to the lost device. If a connection cannot be established, the user may be given the option, via a selectable user interface element (not shown), to queue the request to play the sound to be sent to the lost device, if a connection can be made within a defined time period. If the user chooses to queue the request at mobile device 102, the status of the queued request may be provided on the user interface, such as by indicating with a selectable user interface element 1608 that the request is pending with "Sound Pending".

[0103] Another optional user interface element 1607 can place the wireless accessory in an explicit lost mode. When explicitly placed in lost mode, the wireless accessory will not be able to pair with other devices until the accessory is unlocked by the user or owner who placed the device in lost mode. When a request is sent to place a wireless accessory in lost mode, the requesting user can be required to enter authentication information to ensure that the requesting user is authorized to request to initiate lost mode on the lost accessory. The authentication information can include a username or password associated with an account of the user, such as a cloud service account associated with the user, the electronic device, and the wireless accessory. The authentication information can also include biometric information, such as fingerprint or facial recognition data.

[0104] In one embodiment, the message and contact information provided by the requesting user can be displayed on the user device to prompt the person who finds the lost wireless accessory how to contact the requesting user. In one embodiment, the message and contact information can be displayed when another user attempts to pair another electronic device with the lost accessory.

[0105] like Fig.17As shown, the device locator UI 204 can present a sixth graphical user interface in the electronic device 100 that enables the designation of a known location 1706 shown on the map with 1704 to become a trusted location with the selection of the selectable element 1703. The device locator UI 204 can present a user interface element 1705 representing and / or describing the wireless accessory under consideration.

[0106] Fig.18 is a block diagram illustrating an exemplary API architecture that may be used in some embodiments of the present invention. Fig.18 As shown, the API architecture 1800 includes an API implementation component 110 (e.g., an operating system, library, device driver, API, application, software, or other module) that implements an API 1120. The API 1820 specifies one or more functions, methods, classes, objects, protocols, data structures, formats, and / or other features of the API implementation component that can be used by an API calling component 1830. The API 1820 may specify at least one calling convention that specifies how a function in the API implementation component receives parameters from the API calling component and how a function returns a result to the API calling component. The API calling component 1830 (e.g., an operating system, library, device driver, API, application, software, or other module) makes an API call through the API 1820 to access and use the features of the API implementation component 1810 specified by the API 1820. The API implementation component 1810 may return a value to the API calling component 1830 through the API 1820 in response to the API call.

[0107] It should be understood that the API implementation component 1810 may include additional functions, methods, classes, data structures, and / or other features that are not specified by the API 1820 and are not available to the API calling component 1830. It should be understood that the API calling component 1830 may be on the same system as the API implementation component 1810, or may be located remotely and access the API implementation component 1810 using the API 1820 over a network. Fig.18 A single API calling component 1830 is shown interacting with API 1820 , but it should be understood that other API calling components written in a different language than API calling component 1830 (or the same language) may use API 1820 .

[0108] The API implementation component 1810, API 1820, and API calling component 1830 may be stored in a machine-readable medium, which includes any mechanism for storing information in a form readable by a machine (e.g., a computer or other data processing system). For example, a machine-readable medium includes a disk, an optical disk, a random access memory, a read-only memory, a flash memory device, etc.

[0109] Fig.19 1 is a block diagram of a device architecture 1900 for a mobile or embedded device according to an embodiment. The device architecture 1900 includes a memory interface 1902, a processing system 1904 including one or more data processors, an image processor and / or a graphics processing unit, and a peripheral device interface 1906. The various components may be coupled via one or more communication buses or signal lines. The various components may be separate logic components or devices or may be integrated in one or more integrated circuits, such as a system-on-chip integrated circuit.

[0110] The memory interface 1902 may be coupled to a memory 1950, which may include high-speed random access memory such as static random access memory (SRAM) or dynamic random access memory (DRAM) and / or non-volatile memory such as but not limited to flash memory (e.g., NAND flash, NOR flash, etc.).

[0111] Sensors, devices, and subsystems may be coupled to the peripheral device interface 1906 to facilitate multiple functions. For example, a motion sensor 1910, a light sensor 1912, and a proximity sensor 1914 may be coupled to the peripheral device interface 1906 to facilitate mobile device functions. There may also be one or more biometric sensors 1915, such as a fingerprint scanner for fingerprint recognition or an image sensor for facial recognition. Other sensors 1916 may also be connected to the peripheral device interface 1906, such as a positioning system (e.g., a GPS receiver), a temperature sensor, or other sensing devices to facilitate related functions. A camera subsystem 1920 and an optical sensor 1922 (e.g., a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) optical sensor) may be utilized to facilitate camera functions, such as taking pictures and video clips.

[0112] Communication functions may be facilitated by one or more wireless communication subsystems 1924, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the wireless communication subsystem 1924 may depend on the communication network over which the mobile device is intended to operate. For example, a mobile device including the illustrated device architecture 1900 may include a device designed to communicate over a GSM network, a CDMA network, an LTE network, a Wi-Fi network, a The wireless communication subsystem 1924 may be configured to operate over a network or any other wireless network. Specifically, the wireless communication subsystem 1924 may provide a communication mechanism by which a media playback application may retrieve resources from a remote media server or retrieve scheduled events from a remote calendar or event server.

[0113] The audio subsystem 1926 may be coupled to a speaker 1928 and a microphone 1930 to facilitate voice-enabled functions such as voice recognition, voice replication, digital recording, and telephony. In the smart media devices described herein, the audio subsystem 1926 may be a high-quality audio system including support for virtual surround sound.

[0114] The I / O subsystem 1940 may include a touch screen controller 1942 and / or other input controllers 1945. For computing devices that include a display device, the touch screen controller 1942 may be coupled to a touch-sensitive display system 1946 (e.g., a touch screen). The touch-sensitive display system 1946 and the touch screen controller 1942 may detect contact and movement and / or pressure using, for example, any of a variety of touch and pressure sensing technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch-sensitive display system 1946. The display output of the touch-sensitive display system 1946 may be generated by the display controller 1943. In one embodiment, the display controller 1943 may provide frame data to the touch-sensitive display system 1946 at a variable frame rate.

[0115] In one embodiment, a sensor controller 1944 is included to monitor, control, and / or process data received from one or more motion sensors 1910, light sensors 1912, proximity sensors 1914, or other sensors 1916. The sensor controller 1944 may include logic to interpret the sensor data to determine the occurrence of one of a plurality of motion events or activities by analyzing the sensor data from the sensors.

[0116] In one embodiment, the I / O subsystem 1940 includes other input controllers 1945 that may be coupled to other input / control devices 1948 such as one or more buttons, rocker switches, thumb wheels, infrared ports, USB ports, and / or pointer devices such as a stylus, or control devices such as up / down buttons for volume controls for the speaker 1928 and / or microphone 1930.

[0117] In one embodiment, memory 1950 coupled to memory interface 1902 may store instructions for an operating system 1952, including portable operating system interface (POSIX) compliant and non-compliant operating systems or embedded operating systems. Operating system 1952 may include instructions for handling basic system services and for performing hardware-related tasks. In some implementations, operating system 1952 may be a kernel.

[0118] The memory 1950 may also store communication instructions 1954 to facilitate communication with one or more additional devices, one or more computers and / or one or more servers, such as obtaining network resources from a remote network server. The memory 1950 may also include user interface instructions 1956, including graphical user interface instructions to facilitate graphical user interface processing.

[0119] In addition, the memory 1950 may store sensor processing instructions 1958 to facilitate sensor-related processing and functions; phone instructions 1960 to facilitate processes and functions related to phone calls; instant messaging instructions 1962 to facilitate processes and functions related to electronic message processing; web browser instructions 1964 to facilitate processes and functions related to web browsing; media processing instructions 1966 to facilitate processes and functions related to media processing; location service instructions including GPS and / or navigation instructions 1968 and Wi-Fi-based location instructions to facilitate location-based functionality; camera instructions 1970 to facilitate processes and functions related to cameras; and / or other software instructions 1972 to facilitate other processes and functions, such as security processes and functions and system-related processes and functions. The memory 1950 may also store other software instructions, such as web video instructions to facilitate processes and functions related to web videos; and / or web shopping instructions to facilitate processes and functions related to web shopping. In some specific implementations, the media processing instructions 1966 are divided into audio processing instructions and video processing instructions to facilitate processes and functions related to audio processing and processes and functions related to video processing, respectively. A mobile device identifier, such as an International Mobile Equipment Identity (IMEI) 1974 or similar hardware identifier may also be stored in memory 1950 .

[0120] Each of the instructions and applications identified above may correspond to an instruction set for performing one or more of the functions described above. These instructions need not be implemented as separate software programs, processes, or modules. Memory 1950 may include additional instructions or fewer instructions. In addition, various functions may be performed in hardware and / or software, including in one or more signal processing and / or application specific integrated circuits.

[0121] Fig. 20It is a block diagram of a computing system 2000 according to an embodiment. The computer system 2000 shown is intended to represent a series of computing systems (wired or wireless), including, for example, a desktop computer system, a laptop computer system, a tablet computer system, a cellular phone, a personal digital assistant (PDA) including a cellular PDA, a set-top box, an entertainment system or other consumer electronic device, an intelligent electrical appliance, or one or more specific implementations of an intelligent media playback device. Alternative computing systems may include more, less and / or different components. The computing system 2000 can be used to provide a computing device and / or a server device that a computing device may be connected to.

[0122] The computing system 2000 includes a bus 2035 or other communication device for transmitting information, and a processor 2010 coupled to the bus 2035 that can process information. Although the computing system 2000 is illustrated as having a single processor, the computing system 2000 may include multiple processors and / or coprocessors. The computing system 2000 may also include a memory 2020 in the form of a random access memory (RAM) or other dynamic storage device coupled to the bus 2035. The memory 2020 may store information and instructions that can be executed by the processor 2010. The memory 2020 may also be a main memory for storing temporary variables or other intermediate information during the execution of instructions by the processor 2010.

[0123] The computing system 2000 may also include a read-only memory (ROM) 2030 and / or other data storage device 2040 coupled to the bus 2035 that may store information and instructions for the processor 2010. The data storage device 2040 may be or include a variety of storage devices, such as a flash memory device, a magnetic disk, or an optical disk and may be coupled to the computing system 2000 via the bus 2035 or via a remote peripheral interface.

[0124] The computing system 2000 may also be coupled to a display device 2050 via bus 2035 to display information to a user. The computing system 2000 may also include an alphanumeric input device 2060, which includes alphanumeric and other keys, which may be coupled to bus 2035 to send information and command options to the one or more processors 2010. Another type of user input device includes a cursor control 2070 device, such as a touch pad, mouse, trackball, or cursor direction keys, for communicating direction information and command selections to the processor 2010 and controlling cursor movement on the display device 2050. The computing system 2000 may also receive user input from a communicatively coupled remote device via one or more network interfaces 2080.

[0125] The computing system 2000 may also include one or more network interfaces 2080 to provide access to a network such as a local area network. The network interface 2080 may include, for example, a wireless network interface having an antenna 2085, which may represent one or more antennas. The computing system 2000 may include multiple wireless network interfaces, such as Wi-Fi, A combination of near field communication (NFC) and / or a cellular phone interface. The network interface 2080 may also include, for example, a wired network interface to communicate with a remote device via a network cable 2087, which may be, for example, an Ethernet cable, a coaxial cable, a fiber optic cable, a serial cable, or a parallel cable.

[0126] In one embodiment, the network interface 2080 may provide access to a local area network, for example by complying with the IEEE 802.11 wireless standard, and / or the wireless network interface may provide access to a local area network, for example by complying with the IEEE 802.11 wireless standard. Standards for providing access to a personal area network. Other wireless network interfaces and / or protocols may also be supported. In addition to or in lieu of communicating via wireless LAN standards, network interface 2080 may provide wireless communications using, for example, a time division multiple access (TDMA) protocol, a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) protocol, a long term evolution (LTE) protocol, and / or any other type of wireless communication protocol.

[0127] The computing system 2000 may also include one or more energy sources 2005 and one or more energy measurement systems 2045. The energy source 2005 may include an AC / DC adapter coupled to an external power source, one or more batteries, one or more charge storage devices, a USB charger, or other energy sources. The energy measurement system includes at least one voltage or current measurement device that can measure the energy consumed by the computing system 2000 over a predetermined time period. In addition, one or more energy measurement systems may be included to measure, for example, the energy consumed by a display device, a cooling subsystem, a Wi-Fi subsystem, or other commonly used or high energy consumption subsystems.

[0128] Encryption for wireless accessory location and communication [not sure if required]

[0129] Fig.21 A system 2100 is shown for cooperatively performing key generation between an owner device 2102 and a wireless accessory 2130 according to an embodiment. The owner device can be a version of the mobile device 102 described herein. The wireless accessory 2130 can be a variation of the wireless accessory 201 described herein. The system 2100 shown can be used to implement Figure 3300, wherein the initial pairing 2105 is performed through a secure data session, and the public key exchange 310 is a process of collaborative key generation 2110 performed between the owner device 2102 and the wireless accessory 2130. In addition, although the wireless accessory 2130 is shown and described, the device location functionality described herein can be applied to any electronic device without an independent network connection to allow the device to update its location at a device location server and using at least one radio component capable of broadcasting a beacon signal 2131.

[0130] Collaboration key generation may begin after initial pairing 2105 performed through a secure session. In one embodiment, the NFC-initiated NFC data exchange between the owner device 2102 and the wireless accessory 2130 can be used to establish or exchange encrypted The encrypted The connection exchanges data used to generate cryptographic material for locating the wireless accessory 2130. In some embodiments, a specific implementation of the encryption and key hierarchy described in U.S. Patent Application No. 17 / 603,562, entitled "Sharing Keys for a Wireless Accessory," can be used and is incorporated herein by reference.

[0131] Collaborative key generation process

[0132] Fig. 22 2202 may be an owner device, such as a secondary device 2230. Fig.21 The user device 1402 in , or an equivalent device described herein. The secondary device 2230 may be, for example Fig.21 The wireless accessory 1430 or an equivalent device described herein.

[0133] During collaborative key generation, the primary device 2202 and the secondary device 2230 collaboratively generate a key pair {d, P} and a secret key SK. During this process, the secondary device 2230 cannot learn the private key d, and neither device can bias P or SK. The collaborative key generation process also prevents the primary device 2202 from fully controlling the secret key SK and the key pair {d, P}, and an attacker can extract secrets from one device to reprogram them onto another legitimate device.

[0134] In one embodiment, the primary device 2202 and the secondary device 2230 may perform operations 2211A-2211B to establish a secure data communication session. The secure data communication session may be a secure A connection is established via a secret data exchange via an out-of-band (OOB) mechanism (such as a password, identification number, or NFC data exchange). A secure data communication session can also be established via a wired connection, such as via an accessory interface cable connecting the primary device 2202 and the secondary device 2230.

[0135] The devices may then perform operations 2212A-2212B to generate key material and randomized data. In one embodiment, the secondary device 2230 may generate a P-224 elliptic curve scalar value s and a random value r during operation 2212B. During operation 2212A, the primary device 2202 may generate a P-224 elliptic curve scalar value s′ and a 32-byte random value r′. The primary device may additionally calculate a value S′=s′·G, where G is an elliptic curve generator parameter.

[0136] Then, the primary device 2202 and the secondary device 2230 may perform operations 2213 and 2214 to exchange randomized data through a secure session. During operation 2213, the primary device 2202 may send {S′, r′} to the secondary device 2230, which is an 89-byte transmission in one embodiment. During operation 2214, the secondary device 2230 may send a commitment value to the primary device 2202, where commitment=Hash(s||r). In one embodiment, commitment is a 32-byte value. The secondary device 2230 may also send a value {s, r} to the primary device 2202.

[0137] Then, the primary device 2202 and the secondary device 2230 may perform operations 2216A-2216B to calculate shared secret data based on the combined random data. The secondary device 2130 may calculate P=S′+s·G. The primary device 2102 may confirm commitment=Hash(s||r). The primary device 2102 may also calculate d=s′+s(mod q) and P=d·G=(s′+s)·G=s′·G+s·G=S′+s·G. Then, both the primary device 2102 and the secondary device 2130 may calculate a shared secret key SK=KDF(x(P), r||r′). In one embodiment, |SK|=32 bytes. Then, the primary device 2102 and the secondary device 2130 may derive key material based on the shared secret in operations 2117 and 2118. In operation 2119, the primary device 2102 may store the key material in a key store, such as a shared cloud key store. The secondary device 2130 may store the key material to a local non-volatile storage device in operation 2120 .

[0138] In one embodiment, the device may derive key material based on the secret key using the following techniques. Secondary device 2230 can export SK i , where counter is the current value of the internal counter and N is the number of seconds per privacy window. For example, for a 15-minute privacy window, N = 900. The owner device can derive SK by setting i :set up or Among them, UT lookup is the time corresponding to the period for which position reports should be retrieved, UT now is the current time, and UT delegate It is a delegation period during which the trustee is allowed to control the secondary device 2230. NVM Refers to the time when the primary device 2202 configures the secondary device 2230, which can be retrieved from the non-volatile memory of the secondary device 2230. In one embodiment, the primary device 2202 can set SK0 = SK NVM , and for j=0, ..., i-1, calculate SK j+1 =KDF(SK j , “update”), where for any x, |SK x |=32 bytes, but the size of each key may vary between implementations.

[0139] Using the diversified secret key SK i , can generate owner command key OK i and anti-tracking secret ATi In one embodiment, OK i =KDF(SK i , “Owner”). In addition, AT i =(u i ,v i )=KDF(SK i , “diversification”), where (u i ,v i ) represents the coordinates of the elliptic curve point. In one embodiment, AT i is a 72-byte secret, but this size may vary between implementations.

[0140] Diversified public key P i is a diversified version of the public key P. P can be derived without knowing the private device key d i , and can be used as a location encryption key instead of P to prevent long-term tracking of the secondary device 2230. i =(u i ,v i ), P i =u i ·P+v i G. In one embodiment, u is generated according to FIPS 186-4, B.5.1 Per-Message Secret Number Generation Using Extra Random Bits i and v i is converted to a valid scalar. For example, u i :=(u i mod(n-1))+1 and v i :=(v i mod(n-1))+1, where n is the order of the base point G as defined for P-224.

[0141] Diversification Key d i is the diversified private key d and can be passed to the trustee without revealing d. i and SK i In this case, the main device 2202 can calculate d i =(d·u i +v i ). A set of d i The trustee device can then calculate P i =d i G. The main device 2202 and the trustee can use P i The location of the secondary device 2230 is queried at the positioning server.

[0142] Intermediate Key IK i =KDF(SK i , “intermediate”) can be calculated by the primary device 2202 and shared with the trustee without revealing the private key d. The trustee (and the primary device 2202) can calculate the state byte key BK i , command key CK i and the connection key LTK i . BK i is an encryption key used to protect the secret transmitted via the status byte broadcast by the secondary device 2230 while sending the beacon, where (BK i , BIV i )=KDF(IK i CK i is a command key used to ensure the authenticity of commands sent to the secondary device 2230, where CK i =KDF(IK i , "Command"). LTK i is the connection key used to establish a connection to the secondary device 2230, where LTK i =KDF(IK i In one embodiment, each key is a 32-byte key, and BIV i is a 16-byte value, but this size may vary between implementations.

[0143] Entering near owner mode and near owner status retention

[0144] Fig.23 Flowchart of a process for entering a near-owner state at a secondary device and subsequently maintaining a near-owner mode according to an embodiment. In one embodiment, a primary device 2302 (e.g., mobile device 102) can place a secondary device 2304 in a near-owner mode when the primary device 2302 detects that a secondary device 2304 (e.g., wireless accessory 101) is present nearby (e.g., near-owner state). Prior to entering and subsequently maintaining a near-owner state as described, the secondary device 2304 may have been in "field mode" or near-owner mode. If the secondary device 2304 is not near the primary device 2302, the wireless accessory 101 can enter the field mode. For example, if no packet exchange or connection occurs between the primary device 2302 and the secondary device 2304 within the near-owner timeout period, the secondary device 2304 can enter the field mode. Alternatively, the secondary device 2304 can continue to be in a near-owner state maintained due to detection of a nearby secondary device 2304.

[0145] The primary device 2302 may send a command to the secondary device 2304, instructing the secondary device 2304 to send an advertisement. For example, the primary device 2302 may issue a command to set a near-owner retention timer that should expire after a time period defined by a retention timeout before sending an advertisement, change the frequency of sending advertisements, communicate a new timeout period, indicate a location state corresponding to the timeout period, and / or any other command about advertisements sent between devices. In some embodiments, the retention timeout period is predefined, and in other embodiments, the retention time may be communicated to the secondary device. The retention timeout period may depend on the current location and / or motion state of the primary and secondary devices. For example, if the device is in a trusted location, the retention timeout period may be longer than if the device is not in a trusted location. In another example, the timeout period may be changed based on whether the primary device 2302 and / or the secondary device 2304 are "on the way".

[0146] In one embodiment, the secondary device 2304 is placed in a near-owner mode before certain commands can be issued. The secondary device 2304 can use a command key CK based in part on the i and the diversified public key P i Exported tokens (e.g. Fig.23 The primary device 2302 and the secondary device 2304 may each perform operations (2306A-2306B) to enter a new privacy window and calculate new key material. The primary device 2302 and the secondary device 2304 may each calculate new key material for the privacy window i based on the key P, SK, or d, as described above. The primary device 2302 may then perform operations to derive additional key material, which may include the near owner authorization token. In one embodiment, the diversified public key P i There is a 1:1 mapping between the near owner authorization token and the corresponding near owner authorization token, allowing tokens to be pre-computed for multiple privacy windows. In such an embodiment, the near owner authorization token of a privacy window can be derived as:

[0147] NearOwnerAuthToken i

[0148] =MostSignificant6Bytes(MAC(CK i ,x(P i )||“NearOwmerAuthToken”))

[0149] The primary device 2302 may perform an operation (2308) to update the radio controller lookup table with the expected broadcast address. The expected broadcast address may be based on a derived key. The secondary device 2304 may perform an operation (2307) to update the broadcast address based on the derived key. The primary device 2302 and the secondary device 2304 may derive the derived key based on the calculated key material of the privacy window.

[0150] In one embodiment, the derived key is the diversified public key P i . The reduced bit representation may be a compressed or ciphered representation of the diversified public key storing a reduced number of elliptic curve coordinates. In one embodiment, the derived key is a compact representation x(P i ), where |x(P i )|=28 bytes, where only the x-coordinate of the elliptic curve point is provided. In one embodiment, an indicator of which of the two valid y-coordinates corresponds to the x-coordinate may also be provided.

[0151] In one embodiment, the broadcast address of the secondary device 2304 is updated by encoding the bytes of the derived key into the hardware address of the secondary device, for example, by setting the most significant bytes of the hardware address to the corresponding bytes of the derived key. The primary device 2302 may then update the radio controller (e.g., controller) looks up the table to find the updated hardware address.

[0152] Optionally, an application processor (such as Fig.29 The primary device 2302 may perform an operation (2312) to detect a nearby secondary device 2304 based on an expected broadcast address. In operation, the broadcast address retrieved from the secondary device 2304 is compared to the expected broadcast address of the secondary device 2304 (2314).

[0153] The primary device 2302 selectively performs an operation (2316) to send a message with a timer reset packet and a near owner authorization token as a source address based on the comparison result. If the comparison results in a match between the retrieved hardware address and the expected hardware address, the near owner state is maintained to save resources, such as allowing the application processor to sleep. In one embodiment, the message is sent along with the near owner authorization token as Source hardware address Network Packets. A timer reset packet may include a reset identifier and specify a channel on which advertisements are expected.

[0154] Then, in operation (2319), the secondary device 2304 may enter near owner mode in response to receiving the message with the near owner authorization token as the original address. After time has elapsed according to the retention time periods (2321) and (2322), the secondary device may send a near owner advertisement (2321).

[0155] Fig.24 is a flowchart 2400 of a process for entering a near-owner state and subsequently maintaining a near-owner state at a secondary device from the perspective of a primary device 2302, according to an embodiment.

[0156] Initially, a scan for beacon advertisements broadcast by wireless devices (eg, secondary devices 2304) within range of the wireless network interface is performed by the primary device 2302 via the wireless network interface (2402). A beacon advertisement broadcast by a wireless device is detected (2404).

[0157] Next, at least one identifier is retrieved from the broadcast in the beacon advertisement (2406). The comparison between the retrieved identifier (such as a hardware address) and the expected identifier (such as the hardware address in the lookup table of the secondary device 2304) is performed by the primary device 2302. In some embodiments, the hardware address can be a derived key. Based on the comparison result between the at least one identifier and at least one expected identifier (e.g., hardware address), a timer reset packet and an authorization token are sent to the wireless device (e.g., the secondary device 2402) to remain in the near-owner mode (2408). If the comparison result matches, a timer reset packet 2402 is sent to the secondary device. One or more identifiers can be used to convey a valid timer reset command. In one embodiment, the hardware address, channel, and reset identifier should be in the timer reset packet to allow the secondary device 2304 to identify the packet as a reset packet and set a timer on the secondary device 2304.

[0158] One or more processors may sleep for a predetermined retention period (2410). The application processor of the primary device 2302 may sleep until the retention period has elapsed. In one embodiment, the primary device 2302 may be in a low power state and beacon scanning may be performed by the wireless processor and the radio device receiver as a low power operation when the probe device is idle, inactive, or otherwise in a low power state. Alternatively, the application processor may process other requests.

[0159] Fig.252500 is a flow chart of a process for entering a near-owner state at a secondary device and subsequently maintaining near-owner mode according to an embodiment. A received timer reset packet content includes at least one expected identifier verified by the secondary device (2502). The received timer reset packet may be a packet having one or more identifiers for triggering a timer. Connect_IND connection request packet. In one embodiment, the identifiers including the hardware address, reset identifier and channel number can be matched so as to continue to set the timer on the secondary device 2304. In one embodiment, the timer reset packet contains the expected near-owner authorization token (e.g., hardware address), the specific identifier indicating that the packet is a timer reset packet, and the channel selection in the preamble indicating that the connection should not be established. In one embodiment, the channel selection and / or the absence of the reset identifier can indicate that the packet is a request to form a connection. In some embodiments, a connection will not be formed between the primary device 2302 and the secondary device 2304, but the near-owner mode can be maintained. The secondary device 2304 enters the near-owner state (2504) after the verification of the timer reset packet, and the secondary device sends the near-owner mode packet (2506) to the primary device 2302 after the timer expires. If the secondary device 2304 receives a packet from the primary device 2302 after the timer expires, the timer can be reset again. Alternatively, if no packet is received from the primary device 2302, the secondary device will enter the field mode.

[0160] In one embodiment, the secondary device 2304 filters received advertisements to only receive advertisements from the primary device 2302 and will not accept requests to play sounds used to identify unwanted tracking devices.

[0161] Fig.26 FIG. 26 shows a connection packet 2600 used for a timer reset packet in some embodiments. The connection packet 2600 may be used to form a connection mode. CONNECT_IND packet implementation, this connection mode allows The specification allows two-way communication between two devices. In some embodiments, the packet format may be different from the standard wireless protocol packet. In one embodiment, a connection packet may be used to send a reset to the timer without forming a connection. In another embodiment, the timer reset packet 2511 includes a first public key portion (PubKey1 / 2) InitA used as the initiator advertising address (e.g., hardware address). The first key portion may include the first six bytes of the current public key of the wireless accessory. In one embodiment, the most significant bits of the advertising address are constrained to the value 0b11, which specifies a static device address. In contrast, if the wireless accessory is a wireless beacon tag, the actual address bits are stored in the EK (Extra Key) field along with bits that define the tag type of the wireless accessory. The timer reset packet may include the fields: Advertiser Address, LLData, AA, CRCInit, WinZize, WinOffset, Interval, Delay, Timeout, ChSel (part of the preamble), Hop, ChM, and SCA. In one embodiment, the Hop increment value may have a value of 0b11. A value other than the value specified in the specification (e.g., outside the range of 5 to 16). The ChSel field may be in the preamble of a Connect_IND packet with an expected broadcast channel. In one embodiment, ChSel needs to be set to a value of 1 to set the timer and not establish a connection between the primary device 2302 and the secondary device 2304. The secondary device 2304 may identify the connection packet as a reset timer packet command based on receiving the expected InitA value, Hop value, and ChSel value. Optionally, the AA field value may be an access address, the CRCInit field value may be an initialization for CRC calculation, WinSize and WinOffest may define the window size and transmission window offset, respectively, the interval may define the frequency with which devices exchange data, the delay may be the number of times the wireless device skips a connection event to save power, the timeout may provide a time value for the timeout, and the SCA field may be used to correct the clock accuracy of the primary device.

[0162] Connection and Command Tokens

[0163] Fig. 27 1 is a flow chart of a process for connecting to and commanding a secondary device according to an embodiment. The process may be performed by a primary device to connect to and command a secondary device in a manner protected by keys and tokens as described herein.

[0164] In one embodiment, the primary device may perform operation 2701 to detect a nearby secondary device. For example, the primary device may detect a secondary device within wireless range. The secondary device may be a paired secondary device. During operation 2702, the primary device may use a near-owner authorization token to place the secondary device in near-owner mode.

[0165] The primary device can detect a nearby secondary device and put the secondary device into near owner mode, as described above with respect to Fig.26 The primary device may then perform operation 2703 to trigger a connection with the secondary device using the connection authorization token when the secondary device is in near owner mode. The primary device and the secondary device may each calculate the connection authorization token as: ConnectionAuthToken i =MostSignificant6Bytes(MAC(CK i ,x(P i )||"ConnectionAuthToken"))

[0166] In the above formula, MAC refers to the message authentication code. The secondary device can use ConnectionAuthToken i Placed into the wireless controller lookup table. The primary device can get the ConnectionAuthToken from i The primary device may then perform operation 1804 to connect to the secondary device using the connection key. For example, the primary device and the secondary device may use the connection key LTK i Establishing wireless connections such as but not limited to In one embodiment, to prevent the use of an incorrect LTK i Repeated battery drain attacks can rate limit the token's responses.

[0167] The primary device may then perform operation 2705 to send a command to the secondary device using the command key. Some commands can only be sent by the owner device using the owner command key OK i For this type of command, the owner device can send a command to the secondary device via a command composed as follows:

[0168] send <command> ||MAC(OK i ,x(P i )||“OwnerCommand”||

[0169] <command> || <counter>)

[0170] In this command composition, counter is a 32-bit integer that increases monotonically with each valid owner command sent to the secondary device. The counter value can be reset at each privacy period. The primary device and the secondary device each track the counter value. In one embodiment, if the secondary device receives a command with an invalid hardware address, the secondary device will discard the command, not increment the counter value, and terminate the connection. Although authentication commands using command keys are described, some commands may be non-authentication commands that do not require the presence of command keys. The device may support both authentication commands and non-authentication commands. In one embodiment, some commands may be authenticated or non-authenticated depending on the state of the secondary device. In one embodiment, the secondary device may determine the validity of the command based in part on the owner or trustee status associated with the primary device and whether the primary device has the appropriate key for the attempted command. Delegation is described in more detail below.

[0171] Fig.28 An advertising beacon packet 2810 for a wireless accessory (e.g., secondary device 2304) is shown. The advertising packets broadcast by the wireless accessory may vary based on whether the accessory is in near owner mode (packet 2811), in field mode (packet 2512), or is broadcasting unwanted tracking determination and / or suppression data (packet 2813). In one embodiment, the advertising packets may be Low power advertising packets. However, the implementation is not limited to this. In addition, the packet format may be different from the standard wireless protocol advertising packets.

[0172] In one embodiment, the near-owner advertising packet 2811 includes a first public key portion (PubKey1 / 2) used as an advertising address. The first key portion may include the first six bytes of the current public key of the wireless accessory. In one embodiment, the most significant bits of the advertising address are constrained to a value of 0b11, which specifies a static device address. In contrast, if the wireless accessory is a wireless beacon tag, the actual address bits are stored in the EK (Extra Key) field along with bits that define the tag type of the wireless accessory. The near-owner packet may additionally include fields L1, T1, CID, T2, L2, and S1. L1 is the length of the advertising type field, T1 is the advertising type field, CID is the companion ID field, T2 is the payload type (e.g., object discovery), L2 is the length of the object discovery field, and S1 is the status flag field. The length of the object discovery payload may vary depending on whether the wireless accessory is in near-owner mode or field mode. The status flag field may include, for example, battery status and additional device type flags, such as whether the wireless accessory is a wireless beacon tag.

[0173] In one embodiment, the wild mode advertisement packet 2812 may include fields similar to the near owner advertisement packet 2511. The wild mode advertisement packet 2812 may additionally include a second public key portion (PubKey2 / 2) that includes additional bits of the public key. In one embodiment, the additional bits of the public key or combined public key (PubKey1 / 2, PubKey2 / 2, EK) may be used as a static identifier for the wireless accessory that allows for suppression of unwanted tracking notifications. In one embodiment, the combined public key may also be used by the detector device as an encryption key to encrypt the observed location of the wireless beacon when uploading the observations to the device locator server.

[0174] In one embodiment, the wireless accessory is configured to broadcast separate UT advertisement packets 2813 and wild mode advertisement packets 2812 in an alternating sequence when the accessory is in wild mode. The UT advertisement packets 2813 may include RPA1 and RPA2 values ​​that can be used to ignore or suppress notifications until the end of the day or indefinitely. The RPA1 and RPA2 values ​​are based on a diversified public key and an IRK value that rolls over every privacy period (e.g., every 15 minutes). In one embodiment, IRK_EOD rolls over every 24 hours, while IRK_INDEF does not roll over unless the wireless accessory undergoes a factory reset. The wireless accessory can be factory reset in response to unpairing the accessory from a companion device.

[0175] UT advertisement packet 25813 is optional. In one embodiment, UT advertisement packet 2813 may be excluded and suppression may be performed by using a static identifier for a wireless accessory. The static identifier may be configured to roll over once every 24 hours, thereby allowing unwanted tracking notifications of an accessory to be suppressed once a day. For example, in one embodiment, the diversified public key of the device may continue to roll over internally for the accessory when in field mode, while the field mode advertisement address is configured to roll over at, for example, midnight local time for the wireless accessory. During key rolling, the currently active internal public key may be configured as the advertisement address of the beacon advertisement. In order to facilitate the owner device to reconnect to the accessory when the accessory is in field mode, the field mode advertisement packet 2812 may include a hint field HT, which contains a set of bits (e.g., a set of least significant bits) of the public key currently used by the accessory. The owner device may use this information to generate the correct owner key token to place the wireless accessory in near owner mode. Once in near owner mode, the wireless accessory may begin advertising using near owner advertisement packet 2811.

[0176] Computing system with a secure processor

[0177] Fig.29 A computing system 2200 including a security processor is shown according to an embodiment. In one embodiment, the security processor 2903 shown is a secure area processor, but other types of security processors can be used to accelerate cryptographic operations described herein. The computing system 2900 can enable a device to perform secure accelerated cryptographic operations, provide secure storage for a subset of private keys, and enable encryption of other private keys. Versions of the computing system 2900 can be included in primary devices (e.g., smartphones) and secondary devices (e.g., computing devices, wearable devices, wireless accessories), as described herein.

[0178] The computing system 2900 includes an application processor 2921 communicatively coupled to the security processor 2903 via a security interface 2919. The computing system 2900 can be part of any of the client devices described herein. In addition, the computing system 2900 can be included in one or more of the servers described herein. In one embodiment, the security processor 2903 can be implemented as a system on a chip. In another embodiment, the application processor 2921 and the security processor 2903 can be implemented on a system on a chip and include one or more processors and a memory controller and other components on a single integrated circuit.

[0179] The security processor 2903 may perform cryptographic operations as described herein, as well as other system security operations, such as encrypting user files or verifying code signatures, processing user passwords, or performing other security operations. Cryptographic operations may be performed in part by the security processor core 2915 by executing software stored as firmware 2911 in the security processor 2903. The security processor core 2915 may also be coupled to the ROM 2913, which may be trusted software capable of verifying the software in the firmware 2911 before allowing it to execute, by checking the code signature of the firmware and verifying that the signature code indicates that the firmware is valid and has not been corrupted, and then allowing the firmware to be executed by the security processor core 2915.

[0180] The security processor 2903 may also include a cryptographic accelerator such as a cryptographic accelerator 2907, which may perform asymmetric cryptography as well as symmetric cryptography using hardware accelerators. The cryptographic accelerator 2907 may be coupled to a memory 2905, which may be a non-volatile and immutable memory for storing a device identifier or a set of device identifiers and a set of one or more certificates and private keys in a secure manner, which in one embodiment are hidden from and cannot be read by the rest of the system. The cryptographic accelerator 2907 may access private keys and other data within the memory 2905 and does not allow components outside the security processor 2903 to access the memory 2905. In one embodiment, the cryptographic accelerator 2907 may be coupled to an accelerator memory 2909, which may be a scratch pad memory for performing cryptographic operations performed by the cryptographic accelerator 2907. The application processor 2921 may be coupled to one or more buses 2923, which are coupled to one or more input and output (I / O) devices 2927, such as a touch screen display, Radio components, NFC radio components, Wi-Fi radio components, etc. Other input and output devices may be included. The application processor 2921 is also coupled to the application processor ROM 2925, which provides software for starting the application processor. Similarly, ROM 2913 provides code to start the security processor core 2915 within the security processor 2903.

[0181] Detection of unwanted tracking

[0182] A potential downside to the rolling key privacy protection described herein is the risk of allowing an attachment to remain undetected or allowing an attachment to be placed on an individual with malicious intent to track that individual. Therefore, techniques are provided that enable user devices to detect the possibility of unwanted tracking using the device locator techniques described herein.

[0183] Techniques are provided to mitigate the risk that an accessory that supports a privacy-preserving locator service is used to secretly and maliciously track an individual, without losing the utility of the service to enable lost accessories to be found. A wireless accessory will enter a discoverable wild mode when separated from the owner's device for a period of time. Heuristics can be applied using sensor data to infer movement or activity context to additionally determine whether to cause the device to enter a discoverable wild mode. When in discoverable wild mode, the device will begin advertising a new payload containing a stable identifier alternating with a standard privacy-preserving advertisement payload. The discoverable wild mode uses the same privacy-preserving hardware address as the standard payload, allowing the owner to quickly discover the wireless accessory when in the same location as the wireless accessory. The stable identifier is broadcast as part of the data field of the payload. The stable identifier can be broadcast in alternating packets as a standard beacon broadcast. The stable identifier is non-unique, and for every N devices, an identifier collision will occur (for various values ​​of N based on the selected identifier length). The non-uniqueness of the stable identifier prevents the use of the stable identifier as a tracking tool among large groups of people (e.g., shopping malls, etc.), while allowing the identifier to be used to detect ongoing malicious tracking if the same stable identifier is continuously observed on non-owned devices.

[0184] The alternate packets may have truncated headers to allow additional data to be included in the payload. The additional data may include, for example, information that can be used to suppress any warnings associated with the wireless device. When the same stable identifier of a wireless accessory in discoverable field mode is observed continuously, the user of the detector (e.g., non-owner) device may be alerted. Heuristics are used to filter true and false positive alerts. In addition to the warnings, the user of the detector device may be provided with options on how to proceed, such as how to locate and identify an accessory potentially useful for tracking an individual, or how to suppress notifications of wireless accessories known to the user of the user device.

[0185] Based on certain trigger scenarios, a scan of a device in discoverable field mode may be initiated. For example, a scan may be triggered when a user is on the go (such as walking, running, or biking) for more than a certain period of time and / or for more than a threshold distance. A scan may be triggered when the device detects a state transition in the motion of the device, for example, when a trip via public or private transportation is started or ended. A scan may also be triggered when a user leaves or arrives at a location of interest, such as the user's home or work, or other places where the user frequently spends time (e.g., a gym, coffee shop, etc.).

[0186] Heuristics and / or machine learning models can be used to reduce the number of true and false positives for tracking detection. In one embodiment, context-based heuristics are applied, including analysis of device motion, device location, and the number of wireless devices detected around the device, which can be detected by various advertising beacons broadcast by these devices. For example, when the device is at the user's home location and stationary, the alarm can be suppressed on the device because it is unlikely to track the user at that time. The alarm can also be suppressed when the user is on crowded public transportation (e.g., buses, subways, trains, etc.) because there are legitimate reasons that the user's device will continue to detect tags with the same stable identifier. In one embodiment, heuristics can be applied via a machine learning model that has been trained using device context data corresponding to a high probability of potential false positives and unwanted tracking notifications. The on-device model can apply inference operations to identify potential false positives based on device context data and suppress warnings that may be false positives.

[0187] Heuristics and / or machine learning models may also be applied to determine the increased likelihood of unwanted tracking. For example, if the same persistent identifier is detected at the beginning and end of a vehicle state transition, after leaving a high-density area, or after leaving a location of interest, it is likely that the detected wild-mode tag is being used to track the user. The on-device model may be configured to detect such scenarios and lower the warning threshold in such scenarios, thereby generating faster notifications in scenarios where the device context information suggests that unwanted tracking is more likely.

[0188] In one embodiment, determining the density of an area may include determining the number of beacon wireless devices within range of the electronic device. The determination may include performing a wireless scan to detect, for example, beacon wireless devices within range of the electronic device. Equipment or The number of low-power devices. Operations can then be performed to merge multiple devices that appear to be on the same individual. For example, if multiple beacon devices appear to be in the same location for a certain period of time, it can be determined that those devices are associated with a single individual. Additionally, if multiple beacon devices within a small radius appear to move in the same direction at the same rate for a certain period of time, those devices can be determined to be associated with the same mobile individual. Merging beacons enables the density of individuals in an area to be determined, rather than the number of devices. The number of individuals in an area can then be used to determine the population density of an area for the purpose of true or false positives or possible tracking scenarios.

[0189] Example Unwanted Tracking User Interface

[0190] FIG. 30A to FIG. 30C Unwanted tracking notifications and warnings are shown according to an embodiment. Fig. 30A An electronic device 3001 is shown, which may include a display 3002, which may be used to display a lock screen user interface 3003 when the electronic device 3001 is in a locked state. When in the locked state, the electronic device 3001 may respond to determining (e.g., based on Fig.25 Operation 2500 shown in A) The beacon wireless accessory may be allowing unwanted tracking of the user and displays an unwanted tracking notification 3004.

[0191] Fig. 30B An electronic device 3001 is shown with a display 3002 on which an unwanted tracking warning 3006 may be presented. The unwanted tracking alert 3006 may notify the user that the location of the tag is remotely visible and / or that the tag may allow an unauthorized person to remotely track the user's location. The unauthorized person may track the location of the tag via, for example, the device locator UI 204 described herein. When an unwanted tracking notification is issued, a plurality of options may be presented to the user. An interface element 3007 may be presented to enable the user to allow the presence of the tag for the day (e.g., suppressing the unwanted tracking alert). An interface element 3008 may also be presented to allow the tag indefinitely. Additional interface elements 3009 may be presented to provide information about the unwanted tracking alert.

[0192] Fig. 30C A user interface on an electronic device 3001 with a display 3002 is shown, on which a user interface can be displayed that presents information about the owner of a device being used for potentially unwanted tracking. The user interface can display a representation of a detected wireless device (e.g., a tag 3011) and information text 3013 that informs the user that the detected wireless device may be on (e.g., attached to or included in) a borrowed item. The tag can also be on an individual traveling with the user. In one embodiment, the user can also be presented with an option to perform an NFC tap to reveal a masked identifier of the attachment. The NFC tap can obtain information about the tag, which can be sent to a registration server. The registration server can return information that allows the user interface to display an incomplete identifier 3015 of a registered user of the tag. The user can identify the incomplete identifier 3015 and determine that the tag is safe. In one embodiment, if there is a relationship between a user account on the electronic device 3001 and the user account to which the attachment is registered, the identifier can be a complete or unmasked identifier. The relationship can be determined by a registration server, which can send an unmasked identifier, or the relationship can be determined by an electronic device. For example, the masked identifier can be sent as plain text, while the unmasked identifier can be sent encrypted. If the electronic device 3001 already knows the appropriate decryption key, such as the public key of the account to which the accessory is registered, the electronic device 3001 decrypts and displays the unmasked identifier.

[0193] FIG. 31A to FIG. 31C An unwanted tracking user interface is shown on an electronic device 3101 according to an embodiment. The unwanted tracking user interface may be presented on the display 3102 of the electronic device 3101 after the unwanted tracking notification or warning has been presented.

[0194] like Fig.31A As shown, an unwanted tracking user interface can be presented, which includes a display of a representation 3101 of a tag or other wireless accessory that may allow unwanted tracking of the user, and information text 3102 about the nature of the unwanted tracking warning and / or the nature of the accessory device that may allow the user to be tracked. In addition, an interface element 3103 can be presented to play a sound that allows the user to find the accessory. An interface element 3104 can also be presented to ignore the warning for the accessory. An interface element 3105 can also be presented to present a screen that informs the user how to disable the accessory if the accessory is being used to facilitate unwanted tracking.

[0195] like Fig.31B As shown in , an unwanted tracking user interface can be presented that includes a graphical display 3111 and instruction text 3112 on how to use the NFC touch of the accessory device to ignore the accessory device indefinitely. An interface element 3113 can also be presented to send a command to the accessory device that causes the accessory device to play a sound that allows the accessory device to be located.

[0196] like Fig.31C As shown, an unwanted tracking user interface can be presented that includes a display of a representation 2621 of a tag or other accessory device that may be allowing unwanted tracking of the user and instruction text 3124 informing the user how to disable the accessory device. An interface element 3122 can also be presented to send a command to the accessory device that causes the accessory device to play a sound that allows the accessory device to be located.

[0197] Although the embodiments have been described in language specific to structural features and / or methodological acts, it should be understood that the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts disclosed should be understood as illustrative embodiments of the claims.< / counter>

Claims

1. A mobile electronic device, comprising: a wireless network interface coupled to the bus; a memory device coupled to the bus; and one or more processors coupled to the bus, the one or more processors configured to execute instructions stored on the memory device, wherein when executed, the instructions cause the one or more processors to: performing, via the wireless network interface, a scan for beacon advertisements broadcast by wireless devices within range of the wireless network interface; detecting the beacon advertisement broadcast by the wireless device; retrieving an identifier broadcast within the beacon advertisement; Based on a comparison between the identifier and at least one expected identifier, selectively sending a timer reset packet and an authorization token to the wireless device to maintain the wireless accessory in a near-owner mode; as well as The one or more processors are allowed to sleep for a predetermined time. The mobile electronic device of claim 1 , wherein the identifier is a hardware address.

3. The mobile electronic device of claim 1 , wherein the instructions cause the one or more processors to: A determination is made as to whether the wireless device associated with the beacon advertisement is associated with an account on the mobile electronic device.

4. The device of claim 1, the instructions further causing the one or more processors to generate a set of cryptographic keys based on stored keying material, wherein the keying material is generated in cooperation with the wireless accessory.

5. The device of claim 4, wherein the set of cryptographic keys includes keys for one or more privacy time periods for the wireless accessory, and the operation further includes changing one or more keys used to generate a hardware address with the wireless accessory during each privacy time period. The mobile electronic device of claim 1 , wherein the at least one processor wakes up after a predetermined period of time.

7. The mobile electronic device of claim 1, wherein the timer reset packet includes a reset identifier and a channel selection.

8. The mobile electronic device of claim 1, wherein the wireless network interface is a Bluetooth network interface.

9. A wireless accessory, comprising: a wireless network interface coupled to the bus; a memory device coupled to the bus; and one or more processors coupled to the bus, the one or more processors configured to execute instructions stored on the memory device, wherein when executed, the instructions cause the one or more processors to: Verifying that the content of the received timer reset packet includes the expected identifier; Enter near owner mode; and The near owner mode packet is broadcast after the timer expires.

10. The wireless accessory of claim 9, the instructions further causing the one or more processors to generate a set of cryptographic keys based on stored keying material, wherein the keying material is generated in cooperation with the wireless accessory.

11. The wireless accessory of claim 10, wherein the set of cryptographic keys includes keys for one or more privacy time periods for the wireless accessory, and operations further include changing one or more keys used to generate a hardware address with the wireless accessory during each privacy time period.

12. The wireless accessory of claim 9, wherein the predetermined time at which the timer expires depends on at least one of a location and a motion state of the wireless accessory.

13. A method comprising: performing, via a wireless network interface, a scan for beacon advertisements broadcast by wireless devices within range of the wireless network interface; detecting the beacon advertisement broadcast by the wireless device; retrieving an identifier broadcast within the beacon advertisement; selectively sending a timer reset packet and an authorization token to the wireless device to maintain the wireless accessory in a near-owner mode based on a comparison between the identifier and at least one expected identifier; as well as The one or more processors are allowed to sleep for a predetermined time. The method of claim 13 , wherein the identifier is a hardware address.

15. The method according to claim 13, further comprising: A determination is made as to whether the wireless device associated with the beacon advertisement is associated with an account on a mobile electronic device.

16. The method according to claim 13, further comprising: A set of cryptographic keys is generated based on stored keying material, wherein the keying material is generated in cooperation with the wireless accessory.

17. The method of claim 16, wherein the set of cryptographic keys includes keys for one or more privacy time periods for the wireless accessory, and the operations further include changing one or more keys used to generate a hardware address with the wireless accessory during each privacy time period.

18. The method of claim 13, wherein at least one processor wakes up after a predetermined period of time.

19. The method of claim 13, wherein the timer reset packet includes a reset identifier and a channel selection.

20. The method of claim 13, wherein the wireless network interface is a Bluetooth network interface.

21. A non-transitory machine-readable medium storing instructions, the instructions causing one or more processors of an electronic device to perform operations comprising: performing, via a wireless network interface, a scan for beacon advertisements broadcast by wireless devices within range of the wireless network interface; detecting the beacon advertisement broadcast by the wireless device; retrieving an identifier broadcast within the beacon advertisement; selectively sending a timer reset packet and an authorization token to the wireless device to maintain the wireless accessory in a near-owner mode based on a comparison between the identifier and at least one expected identifier; as well as The one or more processors are allowed to sleep for a predetermined time.

22. The non-transitory machine-readable medium of claim 21, wherein the identifier is a hardware address.