Apparatus and method for quickly finding paired devices
By storing the device identifier key set and decoding the DIR information field, paired Wi-Fi P2P devices are identified, solving the problems of device privacy and pairing efficiency in the prior art, and achieving fast and secure device pairing.
Patent Information
- Application Number
- CN202410363919.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-05
- Filing Date
- 2024-03-28
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art is difficult to quickly find paired Wi-Fi P2P devices without compromising device privacy, especially in Bluetooth low-energy and Wi-Fi co-bit devices, and traditional methods cannot effectively identify and connect paired devices.
By storing the device identifier key (DIK) set of paired devices, decode the device identifier resolution (DIR) information field in the received discovery packet, export the DIR tag set, and match the received DIR tag. If the match is identified, the device is a paired device. Skip the credential sharing process and perform P2P pairing verification directly.
It realizes the rapid identification and connection of paired Wi-Fi P2P devices without affecting device privacy, reducing device discovery and connection time and improving device pairing efficiency.
Smart Images

Figure CN119095022A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to wireless communications, and particularly to apparatus and methods for quickly determining Internet Protocol (IP) addresses. Background Art
[0002] With the emergence of applications such as device sharing, wireless docking, and in-vehicle displays, there is a need to design ultra-low power solutions that can always be online to assist wireless fidelity (Wi-Fi) peer-to-peer (P2P) discovery. Especially for Bluetooth Low Energy (LE) and Wi-Fi collocated devices, using LE to assist Wi-Fi discovery and connection will enable two devices to quickly find each other without interrupting existing Wi-Fi operations. Summary of the invention
[0003] One aspect of the present disclosure provides an apparatus comprising: a memory for storing a set of device identifier keys (DIKs) of all paired peer devices; and a processor circuit coupled to the memory, wherein the processor circuit is used to: decode a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; derive a DIR tag set based at least in part on the stored DIK set in response to the discovery packet; compare the DIR tag included in the DIR information field with a DIR tag in the derived DIR tag set; when the DIR tag included in the DIR information field matches the DIR tag in the derived DIR tag set, identify the P2P device as a paired peer device; and skip a credential sharing process and perform a P2P pairing verification process with the P2P device.
[0004] One aspect of the present disclosure provides a computer-readable medium having instructions stored thereon, which, when executed by a processing circuit, causes the processing circuit to perform the following operations: decoding a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; deriving a DIR tag set based at least in part on a stored set of device identifier keys (DIKs) of all paired peer devices in response to the discovery packet; comparing the DIR tag included in the DIR information field with a DIR tag in the derived DIR tag set; identifying the P2P device as a paired peer device when the DIR tag included in the DIR information field matches a DIR tag in the derived DIR tag set; and skipping a credential sharing process and performing a P2P pairing verification process with the P2P device. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Embodiments of the present disclosure will be illustrated by way of example and not limitation in the accompanying drawings in which like reference numerals refer to similar elements.
[0006] Figure 1 is a network diagram illustrating an example network environment according to one or more example embodiments of the present disclosure.
[0007] Figure 2 is a network diagram illustrating another example network environment according to one or more example embodiments of the present disclosure.
[0008] Figure 3 is a flow chart of a method for fast device pairing determination according to one or more example embodiments of the present disclosure.
[0009] Figure 4 is an example of an LE TDS advertisement packet according to one or more example embodiments of the present disclosure.
[0010] Figure 5 is an example of a fast device pairing determination process according to one or more example embodiments of the present disclosure.
[0011] Figure 6 A functional diagram of an exemplary communication station that may be suitable for use as user equipment according to one or more example embodiments of the present disclosure is shown.
[0012] Figure 7 A block diagram is shown of an example machine upon which any of one or more techniques (eg, methodologies) may be performed according to one or more example embodiments of the present disclosure.
[0013] Figure 8is a block diagram of a radio architecture according to some examples.
[0014] Fig. 9 A method for performing a multi-function circuit according to one or more example embodiments of the present disclosure is shown. Figure 8 Example front-end module circuit in a radio architecture of FIG.
[0015] Fig.10 A method for performing a multi-function circuit according to one or more example embodiments of the present disclosure is shown. Figure 8 Example radio IC circuit in a radio architecture of FIG.
[0016] Fig.11 A method for performing a multi-function circuit according to one or more example embodiments of the present disclosure is shown. Figure 8 Example baseband processing circuitry in a radio architecture of FIG. DETAILED DESCRIPTION
[0017] The various aspects of the illustrative embodiments will be described using terms commonly used by those skilled in the art to convey the essence of the present disclosure to other persons skilled in the art. However, it will be readily understood by those skilled in the art that many alternative embodiments may be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth to provide a thorough understanding of the illustrative embodiments. However, it will be readily understood by those skilled in the art that alternative embodiments may be practiced without these specific details. In other cases, well-known features may be omitted or simplified to avoid blurring the illustrative embodiments.
[0018] Furthermore, various operations will be described as multiple discrete operations in a manner that is most helpful for understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations are necessarily order dependent. In particular, these operations do not need to be performed in the order presented.
[0019] The phrases "in an embodiment," "in one embodiment," and "in some embodiments" are used repeatedly herein. The phrase generally does not refer to the same embodiment; however, it may. The terms "comprising," "having," and "including" are synonymous unless the context dictates otherwise. The phrases "A or B" and "A / B" mean "(A), (B), or (A and B)."
[0020] Figure 1 1 is a network diagram illustrating an example network environment according to some example embodiments of the present disclosure. A wireless network 100 may include one or more user devices 120 and one or more access points (APs) 102, which may communicate according to the IEEE 802.11 communication standard. The user device 120 may be a mobile device that is not fixed (e.g., does not have a fixed location) or may be a fixed device.
[0021] In some embodiments, user equipment 120 and AP 102 may include one or more computer systems, similar to Figure 6 Functional diagram and / or Figure 7 An example machine / system is shown.
[0022] One or more illustrative user devices 120 and / or AP 102 may be operated by one or more users 110. It should be noted that any addressable unit may be a station (STA). A STA may have a plurality of different features, each of which shapes its functionality. For example, a single addressable unit may be a portable STA, a quality of service (QoS) STA, a subordinate STA, and a hidden STA at the same time. One or more illustrative user devices 120 and AP 102 may be STAs. One or more illustrative user devices 120 and / or AP 102 may operate as a personal basic service set (PBSS) control point / access point (PCP / AP). User devices 120 (e.g., 124, 126, or 128) and / or AP 102 may include any suitable processor-driven device, including but not limited to mobile devices or non-mobile devices, such as static devices. For example, the user equipment 120 and / or the AP 102 may include a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., a wristband, a watch, glasses, a ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook TMcomputer, notebook computer, tablet computer, server computer, handheld computer, handheld device, Internet of Things (IoT) device, sensor device, PDA device, handheld PDA device, vehicle-mounted device, non-vehicle-mounted device, hybrid device (e.g., combining cellular phone functionality with PDA device functionality), consumer device, vehicle-mounted device, non-vehicle-mounted device, mobile or portable device, non-mobile or non-portable device, mobile phone, cellular phone, PCS device, PDA device including wireless communication device, mobile or portable GPS device, DVB device, relatively small computing device, non-desktop computer, "travel light, live life" (CSLL) device, ultra mobile device (UMD), ultra mobile PC (UMPC), mobile Internet device (MID), "origami" "Device or computing device, device supporting Dynamic Combination Computing (DCC), context-aware device, video device, audio device, A / V device, set-top box (STB), Blu-ray Disc (BD) player, BD recorder, digital video disc (DVD) player, high-definition (HD) DVD player, DVD recorder, HDDVD recorder, personal video recorder (PVR), broadcast HD receiver, video source, audio source, video receiver, audio receiver, stereo tuner, broadcast radio receiver, flat panel display, personal media player (PMP), digital video camera (DVC), digital audio player, speaker, audio receiver, audio amplifier, gaming device, data source, data receiver, digital still camera (DSC), media player, smartphone, television, music player, etc. Other devices, including smart devices such as lamps, climate control, automotive components, household components, appliances, etc., may also be included in this list."
[0023] As used herein, the term "Internet of Things (IoT) device" is used to refer to any object (e.g., appliance, sensor, etc.) that has an addressable interface (e.g., Internet Protocol (IP) address, Bluetooth identifier (ID), near field communication (NFC) ID, etc.) and can transmit information to one or more other devices through a wired or wireless connection. IoT devices can have passive communication interfaces, such as quick response (QR) codes, radio frequency identification (RFID) tags, NFC tags, etc., or active communication interfaces, such as modems, transceivers, transmitter-receivers, etc. IoT devices can have a set of specific attributes (e.g., device states, such as whether the IoT device is turned on or off, on or off, idle or active, available for task execution or busy, etc., cooling or heating functions, environmental monitoring or recording functions, light emission functions, sound emission functions, etc.), which can be embedded in and / or controlled / monitored by a central processing unit (CPU), a microprocessor, an ASIC, etc., and configured to be connected to an IoT network, such as a local ad hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, washers, dryers, stoves, air conditioners, thermostats, televisions, lamps, vacuum cleaners, sprinklers, electric meters, gas meters, etc., as long as these devices are equipped with an addressable communication interface for communicating with the IoT network. IoT devices may also include mobile phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Therefore, an IoT network may include a combination of "traditional" Internet-accessible devices (e.g., laptop or desktop computers, mobile phones, etc.) and devices that do not typically have Internet connectivity (e.g., dishwashers, etc.).
[0024] User equipment 120 and / or AP 102 may also include, for example, mesh stations in a mesh network in accordance with one or more IEEE 802.11 standards and / or 3GPP standards.
[0025] Any of the user devices 120 (e.g., user devices 124, 126, 128) and AP 102 may be configured to communicate with each other in a wireless or wired manner via one or more communication networks 130 and / or 135. The user devices 120 may also communicate with each other peer-to-peer or directly with or without AP 102. Any of the communication networks 130 and / or 135 may include, but are not limited to, any combination of suitable communication networks of different types, such as broadcast networks, wired networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and / or public networks. In addition, any of the communication networks 130 and / or 135 may have any suitable communication range associated therewith, and may include, for example, a global network (e.g., the Internet), a metropolitan area network (MAN), a wide area network (WAN), a local area network (LAN), or a personal area network (PAN). In addition, any communication network 130 and / or 135 may include any type of medium that can carry network traffic, including but not limited to coaxial cable, twisted pair, optical fiber, hybrid fiber-coaxial (HFC) medium, microwave ground transceiver, radio frequency communication medium, white space communication medium, ultra-high frequency communication medium, satellite communication medium, or any combination thereof.
[0026] Any of the user devices 120 (e.g., user devices 124, 126, 128) and the AP 102 may include one or more communication antennas. The one or more communication antennas may be any suitable type of antenna corresponding to the communication protocol used by the user devices 120 (e.g., user devices 124, 126, and 128) and the AP 102. Some non-limiting examples of suitable communication antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 series standard compliant antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, etc. The one or more communication antennas may be communicatively coupled to a radio component to send and / or receive signals, such as communication signals, to and / or from the user devices 120 and / or the AP 102.
[0027] Any one of the user equipment 120 (e.g., user equipment 124, 126, 128) and AP 102 can be configured to perform directional transmission and / or directional reception in conjunction with wireless communication in a wireless network. Any one of the user equipment 120 (e.g., user equipment 124, 126, 128) and AP 102 can be configured to use a set of multiple antenna arrays (e.g., DMG antenna arrays, etc.) to perform such directional transmission and / or reception. Each of the multiple antenna arrays can be used for transmission and / or reception in a specific corresponding direction or range of directions. Any one of the user equipment 120 (e.g., user equipment 124, 126, 128) and AP 102 can be configured to perform any given directional transmission to one or more defined transmission sectors. Any one of the user equipment 120 (e.g., user equipment 124, 126, 128) and AP 102 can be configured to perform any given directional reception from one or more defined reception sectors.
[0028] MIMO beamforming in wireless networks can be implemented using RF beamforming and / or digital beamforming. In some embodiments, in performing a given MIMO transmission, user equipment 120 and / or AP 102 can be configured to perform MIMO beamforming using all or a subset of its one or more communication antennas.
[0029] Any of the user devices 120 (e.g., user devices 124, 126, 128) and AP 102 may include any suitable radio and / or transceiver for sending and / or receiving radio frequency (RF) signals in a bandwidth and / or channel corresponding to a communication protocol used by any of the user devices 120 and AP 102 to communicate with each other. The radio component may include hardware and / or software to modulate and / or demodulate communication signals according to a pre-established transmission protocol. The radio component may also have hardware and / or software instructions to communicate via one or more Wi-Fi and / or Wi-Fi Direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. In certain example embodiments, a radio component cooperating with a communication antenna may be configured to communicate via a 2.4 GHz channel (e.g., 802.11b, 802.11g, 802.11n, 802.11ax), a 5 GHz channel (e.g., 802.11n, 802.11ac, 802.11ax), or a 60 GHZ channel (e.g., 802.11ad, 802.11ay), an 800 MHz channel (e.g., 802.11ah). The communication antenna may operate at 28 GHz and 40 GHz. It should be understood that the list of communication channels according to certain 802.11 standards is only a partial list, and other 802.11 standards (e.g., next generation Wi-Fi or other standards) may be used. In some embodiments, non-Wi-Fi protocols may be used for communication between devices, such as Bluetooth, dedicated short range communication (DSRC), ultra-high frequency (UHF) (e.g., IEEE 802.11af, IEEE 802.22), white band frequencies (e.g., white space), or other packet radio communications. The radio assembly may include any known receiver and baseband suitable for communicating via a communication protocol. The radio assembly may also include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A / D) converter, one or more buffers, and a digital baseband.
[0030] In one embodiment, referring to Figure 1 , the user device 120 may communicate with one or more APs 102. For example, the (one or more) APs 102 and the (one or more) user devices 120 may be BLE and Wi-Fi co-located devices, and the (one or more) APs 102 may implement a fast device pairing determination 142 with the (one or more) user devices 120. The (one or more) APs 102 and the (one or more) user devices 120 may establish one or more links (e.g., link 1, link 2, ..., link n) between each individual AP and the user device. It should be understood that the above description is for illustrative purposes and is not meant to be limiting.
[0031] Figure 2is a network diagram illustrating another example network environment according to one or more example embodiments of the present disclosure.
[0032] Wireless network 200 may include one or more user devices 220 (eg, 222, 224, 226, or 228) that may communicate via network(s) 230 in accordance with wireless standards such as the Bluetooth protocol and the Wi-Fi protocol standardized by the IEEE 802.11 communications standard.
[0033] In some embodiments, user device 220 may include one or more computer systems, similar to Figure 6 Functional diagrams and / or Figure 7 An example machine / system is shown.
[0034] One or more illustrative user devices 220 may be operated by one or more users 210. User device(s) 220 (e.g., 222, 224, 226, or 228) may include any suitable processor-driven user device, including, but not limited to, a desktop user device, a laptop user device, a server, a router, a switch, an access point, a smartphone, a tablet computer, a wearable wireless device (e.g., a bracelet, a watch, glasses, a ring, etc.), etc.
[0035] Any user device 220 (eg, 222 , 224 , 226 , or 228 ) may be configured to communicate with each other and any other components of the wireless network 200 in a wireless or wired manner, directly and / or through one or more communication networks 230 .
[0036] In the design of Wi-Fi peer-to-peer (P2P) discovery, P2P devices must quickly find devices that can provide the required services. But it is also very important that P2P devices can quickly find P2P devices that have been paired (or bonded) with the P2P device. Such a paired device has previously connected to the device and can provide the required services. Both P2P devices store the credentials of each other. If the P2P device can find a paired P2P device with the required services during the discovery process, then the two P2P devices can skip the Out-Of-Band bootstrapping process (e.g., credential sharing) and go directly to pairing verification and connection setup, which can greatly reduce P2P discovery / connection time.
[0037] LE Transport Discovery Service (TDS) can be used to assist Wi-Fi P2P discovery. The common frame format specified in TDS is used to carry basic service information and assist P2P discovery. Wi-Fi Alliance (WFA) Wi-Fi Aware R3 defines a solution for using LE TDS to find P2P devices that provide the required services. However, the solution defined in Wi-Fi Aware R3 cannot help P2P devices find previously paired P2P devices.
[0038] Some implementations may use P2P device address information to identify paired P2P devices. However, for privacy reasons, P2P devices need to frequently change their P2P device addresses to avoid being tracked. Therefore, using P2P device addresses to identify paired P2P devices may undermine privacy requirements.
[0039] The present disclosure provides a solution for a Wi-Fi P2P device to use LE TDS to quickly find a paired P2P device without compromising its device privacy requirements.
[0040] Example embodiments of the present disclosure are directed to systems, methods, and devices that enable LE / Wi-Fi co-located devices to quickly find paired Wi-Fi devices using LE.
[0041] Figure 3 1 is a flow chart of a method 300 for fast device pairing determination according to one or more example embodiments of the present disclosure. The method 300 may be performed by a LE and Wi-Fi co-located device. As shown, the method 300 may include operations 310 to 350.
[0042] At 310, a discovery packet received from a P2P device is decoded. The discovery packet includes a Device Identifier Resolution (DIR) information field. The DIR information field includes a DIR Tag.
[0043] At 320, in response to the discovery packet, a set of DIR tags is derived based at least in part on a stored (e.g., cached) set of device identifier keys (DIKs) of all paired peer devices, where paired peer devices are peer devices that were previously connected to the LE and Wi-Fi co-located device.
[0044] In some embodiments, each DIK in the stored DIK set is provided to the LE and Wi-Fi co-located device by a corresponding paired peer device, for example, provided through a secure channel after establishing a P2P device pairing with the paired peer device. The LE and Wi-Fi co-located device can use the DIK to identify the paired peer device by parsing the DIR tag.
[0045] In some embodiments, the length of the DIK is 128 bits. In some embodiments, the DIK may have other lengths. The present disclosure is not limited in this regard.
[0046] At 330, the DIR tag included in the DIR information field is compared to the DIR tags in the derived set of DIR tags.
[0047] At 340, when the DIR tag included in the DIR information field matches a DIR tag in the derived set of DIR tags, the P2P device is identified as a paired peer device.
[0048] In some embodiments, during the discovery process, when a P2P device receives a DIR tag from another P2P device, it derives a set of tags based on the DIKs of all paired peer devices that it has cached. If the tag value in the received DIR tag matches the derived tag value, the sender of the DIR tag is identified as a paired peer device.
[0049] At 350 , the credential sharing process is skipped and a P2P pairing authentication process is performed with the P2P device.
[0050] In some embodiments, the DIR information field also includes a P2P device address and a random number (Nonce).
[0051] In some embodiments, the length of the P2P device address may be 64 bits (8 bytes). In some embodiments, the P2P device address may have other lengths. The present disclosure is not limited in this regard.
[0052] In some embodiments, if there is enough space in the TDS announcement packet, the length of the DIR tag and the random number can be 64 bits (8 bytes). In some embodiments, the length of the DIR tag and the random number can be shorter. For example, the length of the DIR tag and the random number can be 16 bits (2 bytes). In another example, the DIR tag and the random number can have other lengths. The present disclosure is not limited in this respect. In some embodiments, the length of the DIR tag can be the same as or different from the length of the random number, and the present disclosure is not limited to this.
[0053] In some embodiments, a DIR tag set may be further derived based on the P2P device address and the random number. For example, the DIR tag may be a hash value of the DIK, the P2P device address and the random number.
[0054] Table 1 below illustrates an example of how the DIR tag is calculated.
[0055]
[0056] The DIR tag calculation method shown in Table 1 is a SHA-256 calculation method where the input is the address and the identity key (shared secret, DIK) and the output is the tag. If both devices know the shared secret (DIK), then they will resolve the address to the same tag. In this case, it is known that the two devices have been paired before and continue to pair and connect using the secret key.
[0057] The DIR tag calculation method in Table 1 is only an example. In another example, a different method may be used to calculate the DIR tag. The present disclosure is not limited in this respect.
[0058] In some embodiments, the discovery packet includes an LE TDS advertisement packet or LE TDS ADV frame.
[0059] Figure 4 1 is an example of an LE TDS advertising packet according to one or more example embodiments of the present disclosure. As shown in the figure, the Advertising Data (AD) length, the Transport Discovery Data Type AD Type Code, the Organization ID, the TDS Flag, and the Transport Data Length fields are defined in the Bluetooth Transport Discovery Service Specification 1.1. The Bloom Filter field and the Channel Information field are defined in Wi-Fi Aware R3.
[0060] In some embodiments, in addition to the LE TDS format defined in Wi-Fi Aware R3, the LE TDS ADV may also include a DIR information field. In some embodiments, the LE TDS advertising packet may also include a transport data header field and a DIR information field.
[0061] For example, the transport data header field and the DIR information field may be defined in Table 2. In another example, they may be defined in other ways. The present disclosure is not limited in this regard.
[0062]
[0063] When a LE Seeker or LE Provider receives the P2P device address, random number, and P2P DIR tag in an LE TDS announcement packet, it derives a set of DIR tag values based on the cached DIKs of all paired peers. If the DIR tag value in the LE TDS ADV frame matches the derived DIR tag value, the LE Seeker / LE Provider identifies the sender of the LE TDS ADV frame as a paired P2P device. If an application or user wants to connect to the paired P2P device, there is no need to initiate a LE secure connection. In this case, the two devices can directly initiate the P2P pairing verification process.
[0064] Figure 5 is an example of a fast device pairing determination process according to one or more example embodiments of the present disclosure. As shown in the figure, P2P device A and P2P device B perform LE TDS discovery by communicating LE TDS advertisement packets including DIR information with each other. After P2P device A and P2P device B recognize that the other device is a paired peer device of each other, they will directly perform a pairing verification process (e.g., via pre-association security negotiation (PSAN) (3 messages)) and a connection setup process (e.g., via group owner negotiation (GON), authentication, association, 4-step handshake), and skip the LE security connection process (e.g., credential sharing).
[0065] By using the technical solution of the present disclosure, even if the device address changes, LE and Wi-Fi co-located devices can use LE to quickly find paired Wi-Fi devices, thereby allowing LE and Wi-Fi co-located devices to identify paired Wi-Fi P2P devices without affecting device privacy requirements. In addition, a flexible format is defined for the DIR information field, which can be included in the existing LE TDS format (short version) and the extended LE TDS format (long version), thereby providing a flexible solution that can be used in the existing LE TDS format or the extended LE TDS format.
[0066] Figure 6 1 shows a functional diagram of an exemplary communication station 600 according to one or more example embodiments of the present disclosure. In one embodiment, Figure 6 FIG. 1 shows an example of an AP 102 ( Figure 1 ) or user equipment 120( Figure 1 ) or user equipment 220( Figure 2) is a functional block diagram of a communication station of the present invention. The communication station 600 may also be suitable for use as a handheld device, a mobile device, a cellular phone, a smart phone, a tablet computer, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) user station, an access point, an access terminal, or other personal communication system (PCS) equipment.
[0067] The communication station 600 may include a communication circuit 602 and a transceiver 610 for sending signals to other communication stations and receiving signals from other communication stations using one or more antennas 601. The communication circuit 602 may include a circuit that can operate the following communications: physical layer (PHY) communication and / or a medium access control (MAC) communication for controlling access to a wireless medium, and / or any other communication layer for sending and receiving signals. The communication station 600 may also include a processing circuit 606 and a memory 608, which are arranged to perform the operations described herein. In some embodiments, the communication circuit 602 and the processing circuit 606 may be configured to perform the operations detailed in the above figures, diagrams, and processes.
[0068] According to some embodiments, the communication circuit 602 may be arranged to compete for a wireless medium and configure a frame or packet for communication via a wireless medium. The communication circuit 602 may be arranged to send and receive signals. The communication circuit 602 may also include circuits for modulation / demodulation, up-conversion / down-conversion, filtering, amplification, etc. In some embodiments, the processing circuit 606 of the communication station 600 may include one or more processors. In other embodiments, two or more antennas 601 may be coupled to the communication circuit 602 arranged to send and receive signals. The memory 608 may store information for configuring the processing circuit 606 to perform operations for configuring and sending message frames and for performing various operations described herein. The memory 608 may include any type of memory, including non-transitory memory, for storing information in a machine (e.g., computer) readable form. For example, the memory 608 may include a computer-readable storage device, a read-only memory (ROM), a random access memory (RAM), a disk storage medium, an optical storage medium, a flash memory device, and other storage devices and media.
[0069] In some embodiments, the communication station 600 can be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capabilities, a web tablet, a wireless phone, a smart phone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or other device that can wirelessly receive and / or transmit information.
[0070] In some embodiments, communication station 600 may include one or more antennas 601. Antenna 601 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmitting RF signals. In some embodiments, a single antenna with multiple apertures may be used to replace two or more antennas. In these embodiments, each aperture may be considered as a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, antennas may be effectively separated for spatial diversity and different channel characteristics that may occur between each antenna and the antenna of the transmitting station.
[0071] In some embodiments, the communication station 600 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, a speaker, and other mobile device elements. The display may be an LCD screen including a touch screen.
[0072] Although the communication station 600 is shown as having several separate functional elements, two or more functional elements may be combined and may be implemented by a combination of software-configured elements (e.g., processing elements including digital signal processors (DSPs)) and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and combinations of various hardware and logic circuits for implementing at least the functions described herein. In some embodiments, the functional elements of the communication station 600 may refer to one or more processes operating on one or more processing elements.
[0073] Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a machine (e.g., computer) readable form. For example, a computer-readable storage device may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium, an optical storage medium, a flash memory device, and other storage devices and media. In some embodiments, the communication station 600 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
[0074] Figure 7A block diagram of an example of a machine 700 or system is shown, on which any one or more techniques (e.g., methods) discussed herein can be performed. In other embodiments, the machine 700 can operate as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine 700 can run in the capacity of a server machine, a client machine, or both in a server-client network environment. In an example, the machine 700 can act as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 700 can be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a wearable computer device, a network device, a network router, a switch or a bridge, or any machine capable of executing instructions (sequential or otherwise) that specify the actions to be taken by the machine (e.g., a base station). In addition, although only a single machine is shown, the term "machine" should also be understood to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more methods discussed herein, such as cloud computing, software as a service (SaaS) or other computer cluster configurations.
[0075] As described herein, examples may include or may operate on a logic or multiple components, modules or mechanisms. A module is a tangible entity (e.g., hardware) that is capable of performing a specified operation when in operation. A module includes hardware. In one example, the hardware may be specifically configured to perform a specific operation (e.g., hardwired). In another example, the hardware may include a configurable execution unit (e.g., a transistor, a circuit, etc.) and a computer-readable medium containing instructions, wherein the instructions configure the execution unit to perform a specific operation at runtime. Configuration may occur under the guidance of the execution unit or a loading mechanism. Therefore, when the device is running, the execution unit is communicatively coupled to the computer-readable medium. In this example, the execution unit may be a member of more than one module. For example, in operation, the execution unit may be configured by a first set of instructions to implement a first module at a point in time, and reconfigured by a second set of instructions to implement a second module at a second point in time.
[0076] The machine (e.g., computer system) 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 704, and a static memory 706, some or all of which may communicate with each other via an interconnection link (e.g., a bus) 708. The machine 700 may also include a power management device 732, a graphics display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse). In an example, the graphics display device 710, the alphanumeric input device 712, and the UI navigation device 714 may be a touch screen display. The machine 700 may also include a storage device (i.e., a drive unit) 716, a signal generating device 718 (e.g., a speaker), a fast device pairing determination unit 719, a network interface device / transceiver 720 coupled to an antenna 730, and one or more sensors 728, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The machine 700 may include an output controller 734, such as a serial (e.g., universal serial bus (USB)), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., printer, card reader, etc.). The operations according to one or more example embodiments of the present disclosure may be performed by a baseband processor. The baseband processor may be configured to generate corresponding baseband signals. The baseband processor may also include a physical layer (PHY) and a media access control layer (MAC) circuit, and may further interface with the hardware processor 702 for baseband signal generation and processing, and for controlling the operation of the main memory 704, the memory device 716 and / or the fast device pairing determination unit 719. The baseband processor may be provided on a single radio card, a single chip or an integrated circuit (IC).
[0077] The storage device 716 may include a machine-readable medium 722 on which is stored one or more sets of data structures or instructions 724 (e.g., software) embodying or utilized by any one or more of the techniques or functionality described herein. The instructions 724 may also reside, completely or at least partially, within the main memory 704, within the static memory 706, or within the hardware processor 702 during execution thereof by the machine 700. In an example, one or any combination of the hardware processor 702, the main memory 704, the static memory 706, or the storage device 716 may constitute a machine-readable medium.
[0078] The fast device pairing determination unit 719 may perform or implement any of the operations and processes described and illustrated above.
[0079] It should be understood that the above is only a subset of the functions that the fast device pairing determination unit 719 may be configured to perform, and other functions included throughout the present disclosure may also be performed by the fast device pairing determination unit 719 .
[0080] Although the machine-readable medium 722 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (eg, a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 724 .
[0081] Various embodiments may be implemented in whole or in part in software and / or firmware. The software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. These instructions may then be read and executed by one or more processors to enable the execution of the operations described herein. The instructions may be in any suitable form, such as, but not limited to, source code, compiled code, parsed code, executable code, static code, dynamic code, etc. Such computer-readable media may include any tangible, non-transitory media for storing information in a form readable by one or more computers, such as, but not limited to, read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, etc.
[0082] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions for execution by the machine 700 and causing the machine 700 to perform any one or more of the techniques of the present disclosure, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memory and optical and magnetic media. In one example, a large number of machine-readable media include machine-readable media having a plurality of particles having a rest mass. Specific examples of a large number of machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; CD-ROM and DVD-ROM disks.
[0083] The instructions 724 may also be sent or received over a communication network 726 using a transmission medium through a network interface device / transceiver 720 that utilizes any of a variety of transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, a wireless data network (e.g., the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as IEEE 802.16 series of standards, known as ), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, etc. In an example, the network interface device / transceiver 720 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 726. In an example, the network interface device / transceiver 720 may include multiple antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission medium" should be understood to include any intangible medium that can store, encode, or carry instructions for execution by the machine 700, and includes digital or analog communication signals or other intangible media to facilitate the communication of such software.
[0084] Figure 8 It is based on Figure 1 The example AP 102 and / or the example STA 120 and / or the user equipment 220 ( Figure 2 ) is a block diagram of the radio architecture 105A, 105B of some embodiments implemented in any one of the ). The radio architecture 105A, 105B may include radio front end module (FEM) circuits 804a-b, radio IC circuits 806a-b, and baseband processing circuits 808a-b. The radio architecture 105A, 105B shown includes wireless local area network (WLAN) functionality and Bluetooth (BT) functionality, but the embodiments are not limited thereto. In the present disclosure, "WLAN" and "Wi-Fi" may be used interchangeably.
[0085] The FEM circuits 804a-b may include WLAN or Wi-Fi FEM circuits 804a and Bluetooth (BT) FEM circuits 804b. The WLAN FEM circuits 804a may include a receive signal path including circuits configured to operate on WLAN RF signals received from one or more antennas 801, amplify the received signals, and provide an amplified version of the received signals to the WLAN radio IC circuits 806a for further processing. The BT FEM circuits 804b may include a receive signal path including circuits configured to operate on BT RF signals received from one or more antennas 801, amplify the received signals, and provide an amplified version of the received signals to the BT radio IC circuits 806b for further processing. The FEM circuits 804a may also include a transmit signal path including circuits configured to amplify WLAN signals provided by the radio IC circuits 806a for wireless transmission to one or more of the antennas 801. Additionally, the FEM circuitry 804b may also include a transmit signal path that may include circuitry configured to amplify BT signals provided by the radio IC circuitry 806b for wireless transmission to one or more antennas. Figure 1 1, while FEM 804a and FEM 804b are shown as being distinct from one another, the embodiments are not limited thereto and include within their scope the use of a FEM (not shown) that includes a transmit path and / or receive path for both WLAN and BT signals, or the use of one or more FEM circuits where at least some of the FEM circuits share transmit and / or receive signal paths for both WLAN and BT signals.
[0086] The illustrated radio IC circuits 806a-b may include a WLAN radio IC circuit 806a and a BT radio IC circuit 806b. The WLAN radio IC circuit 806a may include a receive signal path that may include circuitry for down-converting a WLAN RF signal received from the FEM circuit 804a and providing a baseband signal to the WLAN baseband processing circuit 808a. The BT radio IC circuit 806b may in turn include a receive signal path that may include circuitry for down-converting a BT RF signal received from the FEM circuit 804b and providing a baseband signal to the BT baseband processing circuit 808b. The WLAN radio IC circuit 806a may also include a transmit signal path that may include circuitry for up-converting a WLAN baseband signal provided by the WLAN baseband processing circuit 808a and providing a WLAN RF output signal to the FEM circuit 804a for subsequent wireless transmission by one or more antennas 801. The BT radio IC circuit 806b may also include a transmit signal path that may include circuitry for up-converting a BT baseband signal provided by the BT baseband processing circuit 808b and providing a BT RF output signal to the FEM circuit 804b for subsequent wireless transmission by the one or more antennas 801. Figure 8 Although radio IC circuits 806a and 806b are shown as being distinct from one another, embodiments are not limited thereto and include within their scope the use of a radio IC circuit (not shown) that includes a transmit signal path and / or receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuits at least some of which share transmit and / or receive signal paths for both WLAN and BT signals.
[0087] The baseband processing circuits 808a-b may include a WLAN baseband processing circuit 808a and a BT baseband processing circuit 808b. The WLAN baseband processing circuit 808a may include a memory, such as a set of RAM arrays in a fast Fourier transform or inverse fast Fourier transform block (not shown) of the WLAN baseband processing circuit 808a. Each of the WLAN baseband circuit 808a and the BT baseband circuit 808b may further include one or more processors and control logic. Each of the WLAN baseband circuit 808a and the BT baseband circuit 808b may further include an interface circuit to couple with the corresponding one or more processors or control logic. The one or more processors and control logic may process signals received from the corresponding WLAN or BT receive signal paths of the radio IC circuits 806a-b via the interface circuits, and also generate corresponding WLAN or BT baseband signals for the transmit signal paths of the radio IC circuits 806a-b. Each of the baseband processing circuits 808a and 808b may further include physical layer (PHY) and medium access control layer (MAC) circuits and may further interface with devices for generation and processing of baseband signals and for controlling operation of the radio IC circuits 806a-b.
[0088] Still reference Figure 8 According to the illustrated embodiment, the WLAN-BT coexistence circuit 813 may include logic for providing an interface between the WLAN baseband circuit 808a and the BT baseband circuit 808b to implement use cases requiring WLAN and BT coexistence. In addition, a switch 803 may be provided between the WLAN FEM circuit 804a and the BT FEM circuit 804b to allow switching between the WLAN and BT radios as required by the application. Furthermore, while the antenna 801 is depicted as being connected to the WLAN FEM circuit 804a and the BT FEM circuit 804b, respectively, embodiments include within their scope sharing one or more antennas between the WLAN and BT FEMs, or providing more than one antenna connected to each FEM 804a or 804b.
[0089] In some embodiments, the front end module circuits 804a-b, the radio IC circuits 806a-b, and the baseband processing circuits 808a-b may be provided on a single radio card, such as radio card 802. In other embodiments, one or more antennas 801, the FEM circuits 804a-b, and the radio IC circuits 806a-b may be provided on a single radio card. In some other embodiments, the radio IC circuits 806a-b and the baseband processing circuits 808a-b may be provided on a single chip or integrated circuit (IC), such as IC 812.
[0090] In some embodiments, the radio card 802 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture 105A, 105B may be configured to receive and transmit orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals on a multi-carrier communication channel. The OFDM or OFDMA signal may include multiple orthogonal subcarriers.
[0091] In some of these multi-carrier embodiments, the radio architecture 105A, 105B may be part of a Wi-Fi communication station (STA), such as a wireless access point (AP), a base station, or a mobile device including a Wi-Fi device. In some of these embodiments, the radio architecture 105A, 105B may be configured to send and receive signals according to a specific communication standard and / or protocol, such as any Institute of Electrical and Electronics Engineers (IEEE) standard, including 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.11ay and / or 802.11ax standards and / or 802.11ax standards and / or proposed WLAN specifications, but the scope of the embodiments is not limited in this regard. The radio architecture 105A, 105B may also be suitable for sending and / or receiving communications according to other technologies and standards.
[0092] In some embodiments, the radio architectures 105A, 105B may be configured for high-efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.11ax standard. In these embodiments, the radio architectures 105A, 105B may be configured to communicate in accordance with OFDMA technology, but the scope of the embodiments is not limited in this regard.
[0093] In some other embodiments, the radio architectures 105A, 105B may be configured to send and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and / or frequency hopping code division multiple access (FH-CDMA)), time division multiplexing (TDM) modulation, and / or frequency division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.
[0094] In some embodiments, Figure 8 As further shown in FIG. 8 , the BT baseband circuit 808 b may comply with a Bluetooth (BT) connection standard, such as Bluetooth, Bluetooth 8.0, or Bluetooth 6.0, or any other iteration of the Bluetooth standard.
[0095] In some embodiments, the radio architecture 105A, 105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced, or 7G communications).
[0096] In some IEEE 802.11 embodiments, the radio architectures 105A, 105B may be configured to communicate over a variety of channel bandwidths, including bandwidths with center frequencies of approximately 900 MHz, 2.4 GHz, 5 GHz, and approximately 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with continuous bandwidth) or 80+80 MHz (160 MHz) (with non-continuous bandwidth). In some embodiments, a channel bandwidth of 920 MHz may be used. However, the scope of the embodiments is not limited to the above center frequencies.
[0097] Fig. 9 WLAN FEM circuit 804a is shown in accordance with some embodiments. Fig. 9 The example is described in conjunction with the WLAN FEM circuit 804a, but may be combined with the example BT FEM circuit 804b ( Figure 8 ) to describe Fig. 9 , although other circuit configurations may also be suitable.
[0098] In some embodiments, FEM circuit 804a may include a TX / RX switch 902 to switch between transmit mode and receive mode operation. FEM circuit 804a may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 804a may include a low noise amplifier (LNA) 906 to amplify received RF signal 903 and provide an amplified received RF signal 907 as an output (e.g., provided to radio IC circuits 806a-b ( Figure 8 )). The transmit signal path of circuitry 804a may include a power amplifier (PA) to amplify an input RF signal 909 (e.g., provided by radio IC circuitry 806a-b), and one or more filters 912, such as a bandpass filter (BPF), a lowpass filter (LPF), or other type of filter, to generate an RF signal 915 for subsequent transmission via an example duplexer 914 (e.g., through one or more antennas 801 ( Figure 8 )).
[0099] In some dual-mode embodiments for Wi-Fi communications, the FEM circuit 804a can be configured to operate in the 2.4 GHz spectrum or the 5 GHz spectrum. In these embodiments, the receive signal path of the FEM circuit 804a can include a receive signal path duplexer 904 to separate the signal from each spectrum and provide a separate LNA 906 for each spectrum, as shown. In these embodiments, the transmit signal path of the FEM circuit 804a can also include a power amplifier 910 and a filter 912, such as a BPF, LPF, or other type of filter for each spectrum, and a transmit signal path duplexer 904 to provide the signal of one of the different spectrums onto a single transmit path for subsequent transmission by one or more antennas 801 ( Figure 8 In some embodiments, BT communications may utilize a 2.4 GHz signal path and may utilize the same FEM circuit 804a as used for WLAN communications.
[0100] Fig.10 806a according to some embodiments. The radio IC circuit 806a may be suitable for use as a WLAN or BT radio IC circuit 806a / 806b ( Figure 8 ), but other circuit configurations may also be suitable. Alternatively, Fig.10 Examples of may be described in conjunction with example BT radio IC circuit 806b.
[0101] In some embodiments, the radio IC circuit 806a may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuit 806a may include at least a mixer circuit 1002, such as a down-conversion mixer circuit, an amplifier circuit 1006, and a filter circuit 1008. The transmit signal path of the radio IC circuit 806a may include at least a filter circuit 1012 and a mixer circuit 1014, such as an up-conversion mixer circuit. The radio IC circuit 806a may also include a synthesizer circuit 1004 for synthesizing a frequency 1005 for use by the mixer circuit 1002 and the mixer circuit 1014. According to some embodiments, the mixer circuits 1002 and / or 1014 may be configured to provide a direct conversion function, respectively. Compared to a standard superheterodyne mixer circuit, the latter type of circuit presents a simpler architecture and any flicker noise introduced therefrom may be mitigated by, for example, using OFDM modulation. Fig.10Only a simplified version of the radio IC circuit is shown, and embodiments may be included (although not shown) in which each of the depicted circuits may include more than one component. For example, mixer circuit 1014 may include one or more mixers, respectively, and filter circuits 1008 and / or 1012 may include one or more filters, respectively, such as one or more BPFs and / or LPFs as required by the application. For example, when the mixer circuits are of the direct conversion type, they may each include two or more mixers.
[0102] In some embodiments, mixer circuit 1002 may be configured to generate a synthesized frequency 1005 from FEM circuits 804a-b based on the synthesized frequency 1005 provided by synthesizer circuit 1004. Figure 8 ) down-converts the received RF signal 907. The amplifier circuit 1006 may be configured to amplify the down-converted signal and the filter circuit 1008 may include an LPF configured to remove unwanted signals from the down-converted signal to generate an output baseband signal 1007. The output baseband signal 1007 may be provided to the baseband processing circuits 808a-b ( Figure 8 ) for further processing. In some embodiments, output baseband signal 1007 may be a zero frequency baseband signal, but this is not required. In some embodiments, mixer circuit 1002 may include a passive mixer, although the scope of the embodiments is not limited in this respect.
[0103] In some embodiments, mixer circuit 1014 may be configured to up-convert input baseband signal 1011 based on synthesized frequency 1005 provided by synthesizer circuit 1004 to generate RF output signal 909 for FEM circuits 804a-b. Baseband signal 1011 may be provided by baseband processing circuits 808a-b and may be filtered by filter circuit 1012. Filter circuit 1012 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.
[0104] In some embodiments, mixer circuit 1002 and mixer circuit 1014 may each include two or more mixers and may be arranged for quadrature down-conversion and / or up-conversion, respectively, with the aid of synthesizer 1004. In some embodiments, mixer circuit 1002 and mixer circuit 1014 may each include two or more mixers, each mixer being configured for image rejection (e.g., Hartley image rejection). In some embodiments, mixer circuit 1002 and mixer circuit 1014 may each be arranged for direct down-conversion and / or direct up-conversion, respectively. In some embodiments, mixer circuit 1002 and mixer circuit 1014 may be configured for superheterodyne operation, but this is not required.
[0105] According to one embodiment, mixer circuit 1002 may include: quadrature passive mixers (eg, for in-phase (I) and quadrature-phase (Q) paths). In such an embodiment, Fig.10 The RF input signal 907 may be downconverted to provide I and Q baseband output signals to be sent to a baseband processor.
[0106] The quadrature passive mixers may be driven by zero and ninety degree time varying LO switching signals provided by a quadrature circuit, which may be configured to receive an LO frequency (fLO) from a local oscillator or synthesizer, such as LO frequency 1005 (fLO) of synthesizer 1004. Fig.10 ). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half of the carrier frequency, one-third of the carrier frequency). In some embodiments, the zero-degree and ninety-degree time-varying switching signals may be generated by a synthesizer, but the scope of the embodiments is not limited in this respect.
[0107] In some embodiments, the LO signal can differ in duty cycle (the percentage of a cycle that the LO signal is high) and / or offset (the difference between the start points of the cycle). In some embodiments, the LO signal can have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuit (e.g., the in-phase (I) and quadrature-phase (Q) paths) can operate at an 80% duty cycle, which can result in a significant reduction in power consumption.
[0108] RF input signal 907 ( Fig. 9 ) may include balanced signals, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to a low noise amplifier, such as amplifier circuit 1006 ( Fig.10 ) or filter circuit 1008 ( Fig.10 ).
[0109] In some embodiments, output baseband signal 1007 and input baseband signal 1011 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, output baseband signal 1007 and input baseband signal 1011 may be digital baseband signals. In these alternative embodiments, the radio IC circuit may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits.
[0110] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, or for signals for other spectrums not mentioned herein, although the scope of the embodiments is not limited in this respect.
[0111] In some embodiments, the synthesizer circuit 1004 may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1004 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuit 1004 may include a digital synthesizer circuit. One advantage of using a digital synthesizer circuit is that, although it may still contain some analog components, its footprint may be much smaller than that of an analog synthesizer circuit. In some embodiments, the frequency input to the synthesizer circuit 1004 may be provided by a voltage controlled oscillator (VCO), although this is not required. Depending on the desired output frequency 1005, the divider control input may be further controlled by the baseband processing circuits 808a-b ( Figure 8 ) is provided. In some embodiments, the divider control input (e.g., N) can be determined from a lookup table (e.g., within a Wi-Fi card) based on the channel number and channel center frequency determined or indicated by the example application processor 810. The application processor 810 can include or otherwise be connected to one of the example secure signal converter 101 or the example receive signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).
[0112] In some embodiments, the synthesizer circuit 1004 can be configured to generate a carrier frequency as the output frequency 1005, while in other embodiments, the output frequency 1005 can be a fraction of the carrier frequency (e.g., one-half of the carrier frequency, one-third of the carrier frequency). In some embodiments, the output frequency 1005 can be the LO frequency (fLO).
[0113] Fig.11 808a according to some embodiments. The baseband processing circuit 808a is a functional block diagram of a baseband processing circuit 808a that can be suitable for use as a baseband processing circuit 808a ( Figure 8 ) is an example of a circuit, although other circuit configurations may also be suitable. Alternatively, Fig.10 The example can be used to implement Figure 8 An example BT baseband processing circuit 808b.
[0114] The baseband processing circuit 808a may include a receive baseband processor (RX BBP) 1102 for processing signals received by the radio IC circuits 806a-b ( Figure 8 ) and a transmit baseband processor (TX BBP) 1104 for generating a transmit baseband signal 1011 for the radio IC circuits 806a-b. The baseband processing circuit 808a may also include control logic 1106 for coordinating the operation of the baseband processing circuit 808a.
[0115] In some embodiments (e.g., when analog baseband signals are exchanged between baseband processing circuits 808a-b and radio IC circuits 806a-b), baseband processing circuits 808a may include ADC 1110 to convert analog baseband signals 1109 received from radio IC circuits 806a-b into digital baseband signals for processing by RX BBP 1102. In these embodiments, baseband processing circuits 808a may also include DAC 1112 to convert digital baseband signals from TX BBP 1104 into analog baseband signals 1111.
[0116] In some embodiments, such as transmitting an OFDM signal or an OFDMA signal by the baseband processor 808a, the transmit baseband processor 1104 may be configured to generate an OFDM or OFDMA signal suitable for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 1102 may be configured to process the received OFDM signal or OFDMA signal by performing an FFT. In some embodiments, the receive baseband processor 1102 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation to detect a preamble such as a short preamble, and to detect a long preamble by performing a cross-correlation. The preamble may be part of a predetermined frame structure for Wi-Fi communications.
[0117] Return to reference Figure 8 In some embodiments, antenna 801 ( Figure 8 ) can each include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of suitable antennas for transmission of radio frequency signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas can be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Antennas 801 can each include a set of phased array antennas, but the embodiments are not limited thereto.
[0118] Although the radio architecture 105A, 105B is shown as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by a combination of software-configured elements, such as processing elements including digital signal processors (DSPs) and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and combinations of various hardware and logic circuits for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes operating on one or more processing elements.
[0119] The operations and processes described and shown above can be performed or implemented in any suitable order according to the needs in various embodiments. In addition, in some embodiments, at least a portion of the operations can be performed in parallel. In addition, in some embodiments, less than or more than the described operations can be performed.
[0120] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The terms "computing device," "user device," "communication station," "station," "handheld device," "mobile device," "wireless device," and "user equipment" (UE) as used herein refer to a wireless communication device, such as a cellular phone, smartphone, tablet computer, netbook, wireless terminal, laptop computer, femtocell, high data rate (HDR) subscriber station, access point, printer, point of sale device, access terminal, or other personal communication system (PCS) device. The device may be mobile or fixed.
[0121] As used in this document, the term "communication" is intended to include sending or receiving, or both sending and receiving. This may be particularly useful in a claim when describing the organization of data transmitted by one device and received by another device, but requiring only the functionality of one of these devices would infringe the claim. Similarly, a two-way data exchange between two devices (both devices that send and receive during the exchange) may be described as "communication" when only the functionality of one of these devices is required. The term "communication" as used herein with respect to wireless communication signals includes sending wireless communication signals and / or receiving wireless communication signals. For example, a wireless communication unit capable of transmitting wireless communication signals may include a wireless transmitter that sends wireless communication signals to at least one other wireless communication unit, and / or a wireless communication receiver that receives wireless communication signals from at least one other wireless communication unit.
[0122] As used herein, unless otherwise indicated, the use of ordinal adjectives "first," "second," "third," etc. to describe common objects merely indicates different instances of the similar objects referred to, and is not intended to imply that the objects so described must be in a given order, whether temporally, spatially, in ranking, or in any other manner.
[0123] The term "access point" (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved Node B (eNodeB), or some other similar terms known in the art. An access terminal may also be referred to as a mobile station, a user equipment (UE), a wireless communication device, or some other similar terms known in the art. The embodiments disclosed herein are generally related to wireless networks. Some embodiments may relate to a wireless network operating according to one of the IEEE 802.11 standards.
[0124] Some embodiments may be used in conjunction with various devices and systems, such as a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, a vehicle-mounted device, a non-vehicle-mounted device, a hybrid device, a vehicle-mounted device, a non-vehicle-mounted device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A / V) device, a wired or wireless network, a wireless local area network, a wireless video local area network (WVAN), a local area network (LAN), a wireless local area network (WLAN), a personal area network (PAN), a wireless PAN (WPAN), etc.
[0125] Some embodiments may be used in conjunction with the following systems or devices: one-way and / or two-way radio communication systems, cellular radio-telephone communication systems, mobile phones, cellular phones, wireless phones, personal communication system (PCS) devices, PDA devices including wireless communication devices, mobile or portable global positioning system (GPS) devices, devices including GPS receivers or transceivers or chips, devices including RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcasting (DVB) devices or systems, multi-standard radio devices or systems, wired or wireless handheld devices (such as smart phones), wireless application protocol (WAP) devices, etc.
[0126] Some embodiments may be used in conjunction with one or more types of wireless communication signals and / or systems that follow one or more wireless communication protocols, such as radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), time division multiplexing (TDM), time division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee, Ultra-Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data Rates for GSM Evolution (EDGE), etc. Other embodiments may be used in various other devices, systems and / or networks.
[0127] The following paragraphs describe examples of various embodiments.
[0128] Example 1 includes an apparatus comprising: a memory for storing a set of device identifier keys (DIKs) of all paired peer devices; and a processor circuit coupled to the memory, wherein the processor circuit is used to: decode a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; derive a DIR tag set based at least in part on the stored DIK set in response to the discovery packet; compare the DIR tag included in the DIR information field with a DIR tag in the derived DIR tag set; when the DIR tag included in the DIR information field matches the DIR tag in the derived DIR tag set, identify the P2P device as a paired peer device; and skip a credential sharing process and perform a P2P pairing verification process with the P2P device.
[0129] Example 2 includes the apparatus of Example 1, wherein the discovery packet comprises a low energy (LE) transport discovery service (TDS) advertisement packet.
[0130] Example 3 includes the apparatus of Example 1 or 2, wherein the DIR information field further includes a P2P device address and a random number, and wherein the processor circuit is further configured to: derive the DIR tag set also based on the P2P device address and the random number.
[0131] Example 4 includes the apparatus of any of Examples 1 to 3, wherein the DIR tags in the derived DIR tag set are hash values of corresponding DIKs in the stored DIK set, the P2P device address, and the random number.
[0132] Example 5 includes the apparatus described in any one of Examples 1 to 4, wherein: the length of the P2P device address is 64 bits, and the length of the random number is 64 bits; or the length of the P2P device address is 16 bits, and the length of the random number is 16 bits.
[0133] Example 6 includes the apparatus described in any one of Examples 1 to 5, wherein the discovery packet further includes a transmission data header field for indicating whether the DIR information field exists or the length of the DIR information field.
[0134] Example 7 includes the apparatus of any one of Examples 1 to 6, wherein the length of the DIR information field is 10 bytes or 22 bytes.
[0135] Example 8 includes the apparatus of any of Examples 1 to 7, wherein each DIK in the stored set of DIKs is provided by a corresponding paired peer device after establishing a P2P device pairing with the paired peer device.
[0136] Example 9 includes the apparatus of any one of Examples 1 to 8, wherein the length of a DIK in the stored DIK set is 128 bits.
[0137] Example 10 includes the apparatus of any of Examples 1 to 9, wherein the apparatus is applicable to low energy (LE) and wireless fidelity (Wi-Fi) co-located devices.
[0138] Example 11 includes a computer-readable medium having instructions stored thereon, which, when executed by a processing circuit, causes the processing circuit to perform the following operations: decoding a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; deriving a DIR tag set based at least in part on a stored set of device identifier keys (DIKs) of all paired peer devices in response to the discovery packet; comparing the DIR tag included in the DIR information field with a DIR tag in the derived DIR tag set; identifying the P2P device as a paired peer device when the DIR tag included in the DIR information field matches a DIR tag in the derived DIR tag set; and skipping a credential sharing process and performing a P2P pairing verification process with the P2P device.
[0139] Example 12 includes the computer-readable medium of Example 11, wherein the discovery packet comprises a low energy (LE) transport discovery service (TDS) advertisement packet.
[0140] Example 13 includes the computer-readable medium described in Example 11 or 12, wherein the DIR information field also includes a P2P device address and a random number, and wherein the instruction, when executed by the processing circuit, also causes the processing circuit to perform the following operations: deriving the DIR tag set based on the P2P device address and the random number.
[0141] Example 14 includes the computer-readable medium of any of Examples 11 to 13, wherein the DIR tags in the derived set of DIR tags are hash values of corresponding DIKs in the stored set of DIKs, the P2P device address, and the random number.
[0142] Example 15 includes the computer-readable medium described in any one of Examples 11 to 14, wherein: the length of the P2P device address is 64 bits and the length of the random number is 64 bits; or the length of the P2P device address is 16 bits and the length of the random number is 16 bits.
[0143] Example 16 includes the computer-readable medium of any of Examples 11 to 15, wherein the discovery packet further includes a transport data header field for indicating whether the DIR information field exists or a length of the DIR information field.
[0144] Example 17 includes the computer-readable medium of any one of Examples 11 to 16, wherein the length of the DIR information field is 10 bytes or 22 bytes.
[0145] Example 18 includes the computer-readable medium of any of Examples 11 to 17, wherein each DIK in the stored set of DIKs is provided by a corresponding paired peer device after establishing a P2P device pairing with the paired peer device.
[0146] Example 19 includes the computer-readable medium of any of Examples 11 to 18, wherein the length of the DIKs in the stored DIK set is 128 bits.
[0147] Example 20 includes the computer-readable medium of any of Examples 11 to 19, wherein the P2P device comprises a low energy (LE) and wireless fidelity (Wi-Fi) co-located device.
[0148] Example 21 includes a method comprising: decoding a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; in response to the discovery packet, deriving a set of DIR tags based at least in part on a stored set of device identifier keys (DIKs) of all paired peer devices; comparing the DIR tag included in the DIR information field with a DIR tag in the derived set of DIR tags; when the DIR tag included in the DIR information field matches a DIR tag in the derived set of DIR tags, identifying the P2P device as a paired peer device; and skipping a credential sharing process and performing a P2P pairing verification process with the P2P device.
[0149] Example 22 includes the method of Example 21, wherein the discovery packet comprises a low energy (LE) transport discovery service (TDS) advertisement packet.
[0150] Example 23 includes the method of Example 21 or 22, wherein the DIR information field further includes a P2P device address and a random number, and wherein the method further includes: deriving the DIR tag set based also on the P2P device address and the random number.
[0151] Example 24 includes the method of any of Examples 21 to 23, wherein the DIR tags in the derived DIR tag set are a hash value of a corresponding DIK in the stored DIK set, the P2P device address, and the random number.
[0152] Example 25 includes the method described in any one of Examples 21 to 24, wherein: the length of the P2P device address is 64 bits and the length of the random number is 64 bits; or the length of the P2P device address is 16 bits and the length of the random number is 16 bits.
[0153] Example 26 includes the method of any one of Examples 21 to 25, wherein the discovery packet further includes a transmission data header field for indicating whether the DIR information field exists or the length of the DIR information field.
[0154] Example 27 includes the method of any one of Examples 21 to 26, wherein the length of the DIR information field is 10 bytes or 22 bytes.
[0155] Example 28 includes the method of any of Examples 21 to 27, wherein each DIK in the stored set of DIKs is provided by a corresponding paired peer device after establishing a P2P device pairing with the paired peer device.
[0156] Example 29 includes the method of any one of Examples 21 to 28, wherein the length of the DIK in the stored DIK set is 128 bits.
[0157] Example 30 includes the method of any one of Examples 21 to 29, wherein the method is applicable to low energy (LE) and wireless fidelity (Wi-Fi) co-located devices.
[0158] Example 31 includes an apparatus comprising: a component for decoding a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; a component for deriving a set of DIR tags based at least in part on a stored set of device identifier keys (DIKs) of all paired peer devices in response to the discovery packet; a component for comparing the DIR tag included in the DIR information field with a DIR tag in the derived set of DIR tags; a component for identifying the P2P device as a paired peer device when the DIR tag included in the DIR information field matches a DIR tag in the derived set of DIR tags; and a component for skipping a credential sharing process and performing a P2P pairing verification process with the P2P device.
[0159] Example 32 includes the apparatus of Example 31, wherein the discovery packet comprises a low energy (LE) transport discovery service (TDS) advertisement packet.
[0160] Example 33 includes the apparatus of Example 31 or 32, wherein the DIR information field further includes a P2P device address and a random number, and wherein the apparatus further includes: a component for deriving the DIR tag set also based on the P2P device address and the random number.
[0161] Example 34 includes the apparatus of any of Examples 31 to 33, wherein the DIR tags in the derived DIR tag set are hash values of corresponding DIKs in the stored DIK set, the P2P device address, and the random number.
[0162] Example 35 includes the apparatus described in any one of Examples 31 to 34, wherein: the length of the P2P device address is 64 bits, and the length of the random number is 64 bits; or the length of the P2P device address is 16 bits, and the length of the random number is 16 bits.
[0163] Example 36 includes the apparatus of any one of Examples 31 to 35, wherein the discovery packet further includes a transmission data header field for indicating whether the DIR information field exists or the length of the DIR information field.
[0164] Example 37 includes the apparatus of any one of Examples 31 to 36, wherein the length of the DIR information field is 10 bytes or 22 bytes.
[0165] Example 38 includes the apparatus of any of Examples 31 to 37, wherein each DIK in the stored set of DIKs is provided by a corresponding paired peer device after establishing a P2P device pairing with the paired peer device.
[0166] Example 39 includes the apparatus of any of Examples 31 to 38, wherein the length of a DIK in the stored DIK set is 128 bits.
[0167] Example 40 includes the apparatus of any of Examples 31 to 39, wherein the apparatus is applicable to low energy (LE) and wireless fidelity (Wi-Fi) co-located devices.
[0168] Embodiments according to the present disclosure are specifically disclosed in the attached claims for methods, storage media, devices, and computer program products, wherein any feature mentioned in one claim category (e.g., method) may also be claimed in another claim category (e.g., system). Dependencies or references in the attached claims are selected for formal reasons only. However, any subject matter resulting from intentional tracing back to any previous claim (especially multiple dependencies) may also be claimed, so that any combination of claims and their features is disclosed and may be claimed, regardless of the dependencies selected in the attached claims. The subject matter that may be claimed includes not only the combination of features listed in the attached claims, but also any other combination of features in the claims, wherein each feature mentioned in the claims may be combined with any other feature or combination of other features in the claims. In addition, any embodiments and features described or depicted herein may be claimed in separate claims and / or in any combination with any embodiment or feature described or depicted herein or with any feature of the attached claims.
[0169] The foregoing description of one or more embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.
[0170] Certain aspects of the present disclosure are described above with reference to block diagrams and flow charts of systems, methods, devices and / or computer program products according to various embodiments. It should be understood that one or more blocks in the block diagrams and flow charts and combinations of blocks in the block diagrams and flow charts can be implemented by computer executable program instructions, respectively. Likewise, according to some embodiments, some blocks of the block diagrams and flow charts may not necessarily need to be executed in the order presented, or may not need to be executed at all.
[0171] These computer executable program instructions can be loaded onto a special purpose computer or other specific machine, processor or other programmable data processing device to produce a specific machine, so that these instructions executed on the computer, processor, or other programmable data processing device create a device for implementing one or more functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer readable storage medium or memory, which can instruct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable storage medium produce a product, which includes an instruction means for implementing one or more functions specified in a flowchart block or block. As an example, some embodiments can provide a computer program product, including a computer readable storage medium having a computer readable program code or program instruction implemented therein, and the computer readable program code is suitable for being executed to implement one or more functions specified in one or more flowchart blocks. Computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating elements or steps are executed on a computer or other programmable device, thereby generating a computer-implemented process, so that the instructions executed on a computer or other programmable device provide elements or steps for implementing the functions specified in one or more flowchart blocks.
[0172] Therefore, the blocks of the block diagrams and flow charts support a combination of devices for performing a specified function, a combination of elements or steps for performing a specified function, and a program instruction means for performing a specified function. It will also be understood that each block of the block diagrams and flow charts and the combination of blocks in the block diagrams and flow charts can be implemented by a dedicated, hardware-based computer system or a combination of dedicated hardware and computer instructions that performs a specified function, element or step.
[0173] Conditional language, such as "may" or "might", etc., unless expressly stated otherwise or otherwise understood in the context of use, is generally intended to convey that certain embodiments may include, while other embodiments do not include, certain features, elements, and / or operations. Thus, such conditional language is generally not intended to imply that features, elements, and / or operations are in any way required for one or more embodiments, or that one or more embodiments must include logic for determining, with or without user input or prompting, whether such features, elements, and / or operations are included in any particular embodiment or are to be performed in any particular embodiment.
[0174] Many modifications and other embodiments of the disclosure set forth herein will clearly benefit from the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that the disclosure is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are used herein, they are used in a general and descriptive sense only and not for the purpose of limitation.
Claims
1. A device comprising: a memory for storing a set of device identifier keys (DIKs) of all paired peer devices; and a processor circuit coupled to the memory, Wherein, the processor circuit is used for: decoding a discovery packet received from a peer-to-peer (P2P) device, wherein the discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; deriving, in response to the discovery packet, a set of DIR tags based at least in part on the stored set of DIKs; comparing the DIR tag included in the DIR information field with the DIR tags in the derived DIR tag set; When the DIR tag included in the DIR information field matches a DIR tag in the derived DIR tag set, identifying the P2P device as a paired peer device; and The credential sharing process is skipped, and a P2P pairing verification process is performed with the P2P device.
2. The device according to claim 1, wherein: The discovery packet includes a low energy (LE) transport discovery service (TDS) advertisement packet.
3. The device according to claim 1, wherein: The DIR information field also includes a P2P device address and a random number, and wherein the processor circuit is further configured to: The DIR tag set is also derived based on the P2P device address and the random number.
4. The device according to claim 3, wherein: The DIR tag in the derived DIR tag set is a hash value of the corresponding DIK in the stored DIK set, the P2P device address, and the random number.
5. The device according to claim 3, wherein: The length of the P2P device address is 64 bits, and the length of the random number is 64 bits; or The length of the P2P device address is 16 bits, and the length of the random number is 16 bits.
6. The device according to claim 1, wherein: The discovery packet also includes a transmission data header field for indicating whether the DIR information field exists or the length of the DIR information field.
7. The device according to claim 1, wherein: The length of the DIR information field is 10 bytes or 22 bytes.
8. The device according to claim 1, wherein: Each DIK in the stored DIK set is provided by a corresponding paired peer device after establishing a P2P device pairing with the paired peer device.
9. The device according to claim 1, wherein: The length of the DIK in the stored DIK set is 128 bits.
10. The device according to any one of claims 1 to 9, wherein: The apparatus may be applicable to low energy (LE) and wireless fidelity (Wi-Fi) co-located devices.
11. A computer-readable medium having instructions stored thereon, wherein when the instructions are executed by a processing circuit, the processing circuit performs the following operations: decoding a discovery packet received from a peer-to-peer (P2P) device, wherein: The discovery packet includes a device identifier resolution (DIR) information field, and wherein the DIR information field includes a DIR tag; deriving, in response to the discovery packet, a set of DIR tags based at least in part on a stored set of device identifier keys (DIKs) of all paired peer devices; comparing the DIR tag included in the DIR information field with the DIR tags in the derived DIR tag set; When the DIR tag included in the DIR information field matches a DIR tag in the derived DIR tag set, identifying the P2P device as a paired peer device; and The credential sharing process is skipped, and a P2P pairing verification process is performed with the P2P device.
12. The computer-readable medium of claim 11, wherein: The discovery packet includes a low energy (LE) transport discovery service (TDS) advertisement packet.
13. The computer-readable medium of claim 11, wherein: The DIR information field also includes a P2P device address and a random number, and wherein the instruction, when executed by the processing circuit, further causes the processing circuit to perform the following operations: The DIR tag set is also derived based on the P2P device address and the random number.
14. The computer-readable medium of claim 13, wherein: The DIR tag in the derived DIR tag set is a hash value of the corresponding DIK in the stored DIK set, the P2P device address, and the random number.
15. The computer-readable medium of claim 13, wherein: The length of the P2P device address is 64 bits, and the length of the random number is 64 bits; or The length of the P2P device address is 16 bits, and the length of the random number is 16 bits.
16. The computer-readable medium of claim 11, wherein: The discovery packet also includes a transmission data header field for indicating whether the DIR information field exists or the length of the DIR information field.
17. The computer-readable medium of claim 11, wherein: The length of the DIR information field is 10 bytes or 22 bytes.
18. The computer-readable medium of claim 11, wherein: Each DIK in the stored DIK set is provided by a corresponding paired peer device after establishing a P2P device pairing with the paired peer device.
19. The computer-readable medium of claim 11, wherein: The length of the DIK in the stored DIK set is 128 bits.
20. The computer readable medium according to any one of claims 11 to 19, wherein: The P2P devices include Low Energy (LE) and Wireless Fidelity (Wi-Fi) co-located devices.
