US 12,705,643 B2Grant

Efficient and secure communication using wireless service identifiers

Issue Date:2026-08-11

•20 Claims

•15 Drawing Sheets

Abstract

Systems and methods are provided for reducing communications between servers and a mobile device and providing enhanced security and privacy to wireless beacon services. This can involve a broadcast device transmitting a beacon transmission using a short range wireless radio, such a Bluetooth or WiFi, and including a MAC address, a first unique identifier, and a beacon service identifier. The mobile device then selects one or more unique identifiers from received beacon transmissions, by filtering (that is, selecting) those beacon transmissions which include the beacon service identifier. The wireless device then takes further action, if the first unique identifier is present among the selected one or more unique identifiers, using stored information from the server. The stored information may be delivered to the wireless device in response to the wireless device sending the first unique identifier to a server, or the stored information may have been previously downloaded.

Metadata

Assignee

Secure Communication Technologies, LLC

Inventors

James A. Proctor, Jr.
James Arthur Proctor, III

Application Information

Application Number:US 19/027,075

Filing Date:2025-01-17

Priority Date:2008-09-08

Art Unit:2468

Classifications

IPC:

H04W12/06G06F21/60G06Q10/0875G06Q20/20G06Q20/32G06Q20/38G06Q20/40G06Q30/0207G06Q30/0226G06Q30/0242G06Q30/0251G06Q30/0282G06Q30/0601G06Q50/00H04L9/40H04L67/306H04L67/52H04L67/54H04L69/18H04W4/02H04W4/029H04W4/21H04W4/80H04W8/00H04W8/26H04W12/02H04W12/04H04W40/24H04W76/11H04L61/5038H04L101/622H04W88/06

Field of Search:

H04W 4/80H04W 4/029H04W 4/02H04W 4/023H04W 76/10H04W 4/025H04L 9/0872H04L 2209/80H04L 67/306H04L 9/3229

Patent Drawings (15 sheets)

Description

BACKGROUND

[0001] This patent application relates to wireless communication, and more particularly to efficient and secure communication using wireless service identifiers, such as Bluetooth or WiFi beacon service identifiers.

[0002] Most mobile phones on the market today support at least two wireless standards; one for the cellular wireless wide area network connection (WWAN) and one for a wireless personal or local area network (WPAN, WLAN). The cellular connection or WWAN is utilized for voice and data and can adhere to many different standards such as CDMA (IS-2000), GSM, W-CDMA, 1×EV-DO, HSDPA, EDGE, GPRS, WiMax, etc. The WPAN or WLAN connection is typically for short range communications and is often used for wireless hands free devices, such as headsets, peripherals, or higher speed internet connections. The typical standards used for the sort range wireless communications include Bluetooth, Wi-Fi, and in some cases Ultra-Wide-Band (UWB).

[0003] In another approach to mobile networking some services have attempted to utilize short range wireless capabilities often available on phones such as IEEE802.11 (Wi-Fi) or Bluetooth to facilitate peer to peer communications. These are also referred to a MANETs or Mobile Ad-hoc Networks. These services typically consist of a software application operating on a mobile phone using peer to peer networks to facilitate communication between wireless devices. Examples of such existing applications include Mobile-Cheddar, Peer-2-Me, and Flobbi. Published US Patent application US 2008/0182591 A1 filed Dec. 13, 2007 describes one such peer to peer approach.

[0004] One issue with these approaches is that all information to be exchanged must be stored locally on each of the peer devices as the communication occurs directly between the two devices and any policy for the delivery of locally stored content is difficult to enforce without the potential for fraud such as spoofing identities between the peers. Such fraud may lead to concerns of personal safety or privacy allowing the identity of an individual to be determined when it is not desired.

SUMMARY

[0005] Preferred embodiments are generally concerned with facilitating the exchange of information between two entities associated with two wireless devices. In one embodiment, this can be accomplished by a first device using a first short range wireless capability to detect an identifier transmitted from a second device, ideally using existing short range radio communication standard capabilities such as Bluetooth (IEEE802.15.1-2002) or Wi-Fi (IEEE802.11). The detected identifier, being associated with the device, is also associated with an entity. Rather than directly exchanging application data flow between the two devices using the short range wireless capability, a second wireless capability then allows for one or more of the devices to communicate with a central server via the internet, and perform an exchange of application data flow. By using a central server to draw on stored information and content associated with the entity or entities, the server can manage the subsequent exchange of information between the entities and the devices. In a preferred embodiment, this exchange may be comprised of information stored on the server associated with a detected entity, and it may be comprised of information received from the detected device via the second wireless capability and facilitated by the server.

[0006] In addition, the server can also allow for a brokering service, ideally independent of the entities, to enable the application of policy based on the identity of the two entities for the disclosure of stored information associated with the entities, the flow in information between the devices and the entities, and the enablement of procedures such as security verification between the entities.

[0007] In one embodiment, a method is provided for reducing communications between one or more servers and a wireless device, as well as providing enhanced security and privacy to wireless beacon services.

[0008] The method involves transmitting, by at least one beacon transmitter using a short range wireless radio, a first beacon transmission in a first time period. The beacon, which may be a short range wireless protocol such a Bluetooth or WiFi service beacon, comprises a first MAC address, a first unique identifier, and a beacon service identifier.

[0009] Using a second radio, the one or more servers also transmit stored information relating to an entity or object associated with the first unique identifier.

[0010] A first plurality of beacon transmissions are received by the wireless device during the first time period.

[0011] The wireless device then selects one or more unique identifiers from the first plurality of beacon transmissions, by filtering (that is, selecting) only those beacon transmissions which include the beacon service identifier.

[0012] The wireless device then takes further action, if the first unique identifier is present among the selected one or more unique identifiers, using the stored information, which includes at least the identity of the entity or object associated with the first unique identifier.

[0013] Other embodiments may transmit, by the same beacon transmitter using the short range wireless radio, a second beacon transmission in a second time period. The second beacon transmission also includes a second MAC Address, a second unique identifier, and the same beacon service identifier. In this embodiment, the wireless device also receives, using the short range wireless radio, a second plurality of beacon transmissions during the second time period, as well as second stored information relating to the entity or object associated with the second unique identifier, from the one or more servers using a second radio.

[0014] In those embodiments, a second set of one or more unique identifiers are selected from the second plurality of beacon transmissions, by filtering the second plurality of beacon transmissions which include the same beacon service identifier. Further action taken is taken related to the second stored information, if the second unique identifier is present among the selected second set of one or more unique identifiers.

[0015] In some embodiments, the further action may include preventing the sending of the first or second unique identifier by the first wireless device to the one or more servers.

[0016] In some embodiments, the MAC address is a randomly generated 48 bit number matching a format of a Bluetooth BD_ADDR.

[0017] In some embodiments, the further action may include determining that at least one beacon transmitter is a broadcast device having a predetermined location.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The foregoing will be apparent from the following more particular description of example embodiments, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the embodiments.

[0019] FIG. 1 is a block diagram of two mobile devices utilizing a preferred embodiment.

[0020] FIG. 2 is a block diagram of a fixed broadcast device and a mobile device.

[0021] FIG. 3 is a flow diagram of the operation of an application on the mobile devices.

[0022] FIG. 4 is a message sequence chart showing the Bluetooth discovery process using in one embodiment.

[0023] FIG. 5 is a message sequence chart showing the Bluetooth Remote Name Request Process.

[0024] FIG. 6 is a message sequence chart showing the IBSS beacon process.

[0025] FIG. 7 is a message sequence chart showing the interaction between the server and two devices performing a detection and entering a chat application.

[0026] FIG. 8A is a message sequence chart showing an E-commerce example.

[0027] FIG. 8B is a continued example message sequence chart showing an E-commerce example.

[0028] FIG. 9 is a message sequence chart showing an example of a mobile device and a fixed broadcast device interaction.

[0029] FIG. 10 is a flow diagram for the server processing associated with the detection process.

[0030] FIG. 11 is an example individual account record stored in the server associated with an Entity.

[0031] FIG. 12 illustrates a timing reference for intermittent active and dormant times.

[0032] FIG. 13 shows a diagram of functional blocks associated with management of dynamically assigned device identifiers.

DETAILED DESCRIPTION

[0033] A description of example embodiments follows.

[0034] The teachings of all patents, published applications and references cited herein are incorporated by reference in their entirety.

[0035] FIG. 1 is a block diagram of two mobile devices utilizing a preferred embodiment.

[0036] Referring to FIG. 1, a central server 100 is connected to devices 106 and 108 by an internet protocol (IP) based network, carried over a series of connections, at least one of which is a wireless connection. For example, the server 100 has a connection allowing IP based communications to a cellular network 102 using connection 101. The cellular network is connected to devices 106 and 108 by wide area wireless links 104 and 103 respectively, allowing for IP based communications between the devices (106 and 108) and the server 100.

[0037] Devices 106, 108 can be considered “client(s)” of the server 100. The clients 106, 108 and server 100 provide processing, storage, and input/output devices for executing wireless system protocols, interfaces, and application level programs according to several embodiments. Client devices 106, 108 can also be linked through various communications networks to other computing devices, including other client devices/processes and other server computer(s). Communications network(s) providing the connection 101 can typically be part of a remote access network, a global network (e.g., the Internet), a worldwide collection of computers, Local area or Wide area networks, and gateways that currently use respective protocols (TCP/IP, 3G Wireless, Bluetooth, etc.). Other electronic device/computer network architectures are suitable.

[0038] The internal structure of devices 106, 108 or server 100 includes one or more data processors (not shown in detail) that are well known in the art to include a system bus for data transfer among the other internal components of a computer system (e.g., processor, disk storage, memory, input/output ports, network ports, etc.). Attached to the bus are other input/output devices (e.g., keyboard, mouse, displays, printers, speakers, network interfaces, etc.). Network interfaces allow the computer to connect to various other devices attached to a network. Memory provides volatile storage for computer software instructions and data used to implement an embodiment (e.g., applications programs and the like). Disk storage can provide non-volatile storage for computer software instructions and data used to implement the embodiments.

[0039] One embodiment may include a computer program product including a computer readable medium (e.g., a removable storage medium such as one or more DVD-ROM's, CD-ROM's, diskettes, tapes, etc.) that provides at least a portion of the software instructions for the system. Computer program product can be installed by any suitable software installation procedure, as is well known in the art. In another embodiment, at least a portion of the software instructions may also be downloaded over a cable, communication and/or wireless connection. In other embodiments, the programs are a computer program propagated signal product 107 embodied on a propagated signal on a propagation medium (e.g., a radio wave, an infrared wave, a laser wave, a sound wave, or an electrical wave propagated over a global network such as the Internet, or other network(s)). Such carrier medium or signals provide at least a portion of the software instructions.

[0040] More particularly, a given device 106, 108 uses a short range wireless link 107 such as a Bluetooth (IEEE802.15.1) or Wi-Fi (IEEE802.11) link to detect the presence of other devices such as device 108, and uses the wide area wireless network connections 103, 104 such as IS-2000, WCDMA, GPRS, EDGE, LTE, Wi-Max (IEEE802.16), or the like to perform communications to central server 100, and to perform the actual substantive communications between the wireless devices 106 and 108. Device 108 typically uses the short range wireless link 107 and wide area wireless link 103 in a similar manner to locate and initiate communicate with device 106. One distinction relative to prior art is that the short range wireless 107 is only used for the detection process, or to advertise a device's presence. In this embodiment, specific information called “wireless identifier” or simply “identify” (described in more detail below) is passed between devices 106 and 108 over the short range link 107. By transmitting a wireless identifier using the short range Wi-Fi, Bluetooth or other short range wireless link 107 and receiving wireless identifiers from other devices, this short range wireless link 107 will allow for a proximity detection process.

[0041] The support for IP based networking is standard for WWAN or 3G connections such as 1×EV-DO or HSPA, and as a result, communication between one device to another using the WWAN is currently supported in many devices with no modification. The use of simple detection of one or more identifiers requires significantly less resources in a phone than performing a complete peer to peer based communication network protocol, which accommodates dynamic configuration of nodes being added and dropped continuously. It is noted that the IP address on the WWAN interface is not location dependent in the present embodiment, but is addressing approaches are location dependent when true Peer to Peer topologies are used. The present embodiment has the advantage that communication between two devices may continue after the devices have left proximity of each other, but in the same manner as they had been communicating previously. As a result, a user who detects a short range transmission of an identifier, then begins a conversation or some other interaction with that device via the wireless wide area network may continue that conversation even in the case where the two devices move out of the proximity of the each other, and are no longer within the reception range of the short range wireless communication protocol. Further, since it is contemplated that the wireless identifiers transmitted on the short range wireless link from the devices would occasionally change, for security reasons, the present embodiment has the advantage that ongoing communications between mobile devices will not be interrupted despite a change in one of the device's identifier. In the case where the identifier is a MAC address of the short range wireless network adapter for one of the devices, it is not otherwise possible to change this address and easily maintain on going communications in a true peer to peer topology.

[0042] Referring to FIG. 2, central server 100 is connected to the cellular network 101, and is able to communicate information to and from wireless device 202 using a wide area wireless link such as IS-2000, WCDMA, GPRS, EDGE, LTE, Wi-Max (IEEE802.16), or the like within structure 205. Device 204 does not have a wide area wireless or cellular link, but transmits identifying information using short range wireless link 203. Device 202 is capable of receiving the indentifying information and requesting information related to that device from server 100.

[0043] An example of an application using this infrastructure follows. The device 204 will simply broadcast an identifier, with no WWAN connection but may facilitate advertising or local information. For instance, an account associated with one or more identifiers may belong to a museum. As a museum patron walks to an exhibit, the patron's device 202 will receive an identifier sent from museum broadcast device 204 operated by the museum. The patron device 202 passes the identifier or museum device 204 to the central server 100, which in-turn recognizes it as being associated with that exhibit within that museum and passes relevant information back to the user's device 202. A distinguishing feature of this approach relative to prior art is that the patron device 202 in this example may move out of proximity of broadcast device 204, yet continue to view the content being provided by the server 100 related to the detected broadcast device 204. Content may include text, pictures, web pages, application software such as games, informative display applications, or other content such as audio or video to be offered to the user's device as well. Other examples might include electronic coupons (such as in a grocery store), menus or special offers in a restaurant.

[0044] FIG. 3 is a block diagram with further detail of this operation. A device 106, 108, or 202 after performing a search (FIG. 3, step 301) for identifiers on the WPAN or WLAN, will subsequently use the WWAN link to communicate with the central server 100. If the device does not find identifiers 302 it will either continue to search, or search at a later time 301. If identifiers are found in 302, the device may employ an action function 303, which would act as a filter that determines which of the detected identifiers should be passed to the server. This function may instead be omitted and all identifiers passed to the server 100. The idealized effect of the action function would be to reduce the number of requests to the server by not re-requesting recently requested identifiers which have already been passed to the server, for some period of time. In step 304, if no identifiers require server information, searching is continued in step 301.

[0045] Assuming there are identifiers which are new to the device, the device will pass along a list of currently detected identifiers and request 305 that the server return information related to any other local device. The server will return the information related to any identifier that meets certain policy requirements. For instance, information is returned which is 1) relevant to that device, and 2) that the device is authorized to receive.

[0046] As an example of the overall process, a detected identifier may be relevant to the receiving device if the user associated with the detected identifier is listed in a “friends list” for the owner of the receiving device. If the identifiers for the individuals within the friends list have been passed to the device, the action function 303 may make this determination. In the preferred embodiment, the server would determine the identity and the relevance of the detected identifiers, and the action function 303 would work to reduce frequency of re-requests to the server. FIG. 7 describes an example of how to use this for messaging associated with the device and server interaction during the detection and identifier inquiry process, with a more detailed explanation to follow.

[0047] To enable server 100 to associate an identifier with an entity, each device or entity (such as the museum) associated with an identifier has an account on server 100 or a related server as is common in information technology. The account is associated with the entity and the device and the current identifier.

[0048] As used herein, an “entity” may be a legal entity, such as an individual person or a business.

[0049] An “object” is intended to include a physical thing, such as a product that is being offered for sale, and may include a tangible article or intangible such as an electronic music or video file or photograph.

[0050] There is various information associated with each account. An example data record for an account is shown in FIG. 11. When the account is associated with an individual or (other entity), there may be personal information such as the individual's name, contact information, information regarding allowed communication, such as chat or IM, links to their other social networking services, and the like. When the account is associated with a broadcast device 204 the account may contain content to be displayed to the detecting device 202. By utilizing the central server 100, broadcast devices may be tied to a location or product thereby providing relevant information about the location such as in the museum tour example previously discussed. In this situation, the content delivered to device 202 may be informative information about an exhibit including pictures, text, audio, or video and the like. In the case of a broadcast device being in a supermarket and near a specific product, advertisement or discounts with electronic coupons my be stored in the account and provided to device 202.

[0051] There can also be policy based permissions associated with each account and applied to any information associated with that account. The stored policy permissions can be used to determine what information and under which situations information may be disclosed to another device or user associated with another account. For example, the entity (person in this case) associated with device 202 may have set a policy in their account to not receive any unsolicited information from a broadcast device so as to not be disturbed. However, the person associated with 202 may see the broadcast device and a sign stating a discount is available, and provide input to their device to request any broadcast information on a one time exception basis. The messaging associated with an example mobile and broadcast device process will be described in more detail to follow associated with FIG. 9.

[0052] As already mentioned above, in step 301 of FIG. 3, each device performs a search function looking for identifiers sent from other devices utilizing a short range wireless capability. The following describes the process of devices detecting identifiers from other devices in more detail.

[0053] The identifiers themselves may be a hardware address such as the MAC address of the wireless device, or they may be another label such as the SSID for a IEEE802.11 device, or the device name for a Bluetooth device. Referring to FIG. 4, in the case where a Bluetooth wireless personal area network device is utilized, a first device 401 transmits an inquiry (ID_Packet) message 404, and any proximal Bluetooth devices 402, 403 respond with messages identifying the MAC address, called BD_ADDR in IEEE802.15.1 of each device using a message referred to as an “Inquiry Response” FHS message 405 containing the BD_ADDR or Bluetooth device address of the detected device. In the Bluetooth standard all devices 402, 403 are required to respond in this manner assuming they are enabled to be discoverable. To enable this, an application on the mobile device ensures the Bluetooth device is set to discoverable mode. Device 1 (401) will attempt to locate Devices on different channels by scanning the channels and transmitting multiple Inquiry (ID_Packet) messages. Such an example is shown with inquiry exchange 406 and 407 to discover Device N (403).

[0054] In one embodiment the BD_ADDR or MAC address of the Bluetooth device can be used as the Identifier and no further Bluetooth interaction is required until the next scan process is performed.

[0055] In another embodiment, the Bluetooth “Device Name” is used as the identifier. FIG. 5 shows the process of a first device “Device 1” (501) determining another Bluetooth enabled device's (502) Bluetooth Device Name. Following the device discovery process completion from FIG. 4, Device 1 501 sends a Page message 503 to another device (Device L 502). Message 504 is sent in response to create a temporary Asynchronous Connectionless Link (ACL) to be established between Device 1 501 and Device L 502, without an explicit connection request. Not having an explicit connection request indications the Entity associated with Device L would not have to provide explicit approval for a connection from their user input on the device, as would be the case if other services were requested from the device such as might be the case with a wireless headset or remotely connected GPS receiver to a phone. An ACL connection allows link management packets to be exchanged, and following interchanges of messages 505 and 506 to determine features of the devices, a temporary connection is established between the two devices. A name request message (507) is then sent by Device 1 to Device L, and Device L responds with at least one LMS_name_res message 508 containing the Bluetooth device name of Device L 502. If the name is longer than that allowed within the LMS_name_res message, additional messages follow to allow for the entire name to be delivered. Finally the connection is ended with message 509, LMP_detach.

[0056] The transmitted identifiers associated with any given device are only known to the central server and the device transmitting the identifiers. These identifiers may change from time to time, making a user's or a device's identity anonymous over time. The central server and any particular device must be coordinated such that the identifier and any device transmitting it, remains identifiable by the central server. This process is coordinated between the wireless device, and the central server utilizing the WWAN or cellular data link, carrying messaging between them and using an identifier manager 1303 to maintain a list of device identifiers 1302 in a central but secure location. This is shown in more detail in FIG. 13.

[0057] Referring to FIG. 6, an example of using on IEEE802.11 link as the short range wireless capability is discussed. Generally, Wi-Fi devices operation in a so-called infrastructure mode which utilizes a BSS or basic service set. One component of a infrastructure network based wireless LAN is the use of a central access point or AP. In a mobile network the use of a central AP is not practical, as only the AP transmits an identifier, which does not meet the requirements of the preferred embodiment. The second topology for Wi-Fi networks is the so-called Ad-Hoc mode of operations, referred to as an independent basic service set or IBSS. In an IBSS all devices participating or advertising their interest in participating in an ad-hoc network transmit identifiers called beacons. These beacons contain the MAC address of the transmitting network adapter, the basic service set identifier (BSSID), and ad-hoc network name or service set identity (SSID). The BSSID in a typical ad-hoc network is generated by the first station to enter the BSSID and is locally administered, typically a randomly generated 48 bit number matching the format of a MAC address. In an ad-hoc network, each device 601, 602, 603 participating or desiring to participate transmits a beacon. There are several embodiments related using the IBSS beacons and the identifiers. First the identifier may be used as the MAC address of the station device or network adapter, and one or both the BSSID and the SSID may be used to indicate these particular beacons are associated with a service. In other embodiments, one or more of the BSSID and the SSID may be used as the identifier. In any of the embodiments for delivery of the identifier in an IBSS beacon, it is possible to coordinate the change of those identifiers with the server 100. As the MAC address is always broadcast in any operation of a Bluetooth or Wi-FI link, the use of a MAC address as an identifier provides for an additional level of security for the device 601, 602, 603, when identifier is changed from time to time as devices may be detected and identities tracked using a constant MAC address. In the preferred embodiment, where the MAC address is used for the identifier, all the devices participating would likely have the same network name and SSID to aid in the identification of the device as being enabled, although not necessarily required. Examples using an 802.11 network in ad-hoc mode transmitting beacons are showed as messages 604, 605, and 606.

Chat Example Between Two Mobile Devices

[0058] FIG. 7 shows an example of a message flow diagram for an embodiment where an individual is in a library for example, and a friend arrives. The individual is notified by their device receiving an identifier that their friend is present and they enter a chat session. Each person has a device (FIGS. 1, 106 and 108 respectively) that implements the preferred embodiments described above. The first individual associated with Device 1 (702) referred to as Entity 1 (EI1) performs a detection process as described in FIGS. 4, 5, and 6 previously (step 704). The device identifier associated with Device 2 (703), DI2 is thereby detected. Device 1 (702) then transmits an inquiry message 705 using the WWAN (cellular data link such as GPRS, EDGE, 1×EV-DO, IS-2000, Wi-Max, LTE, or the like) to the server 701 inquiring if information related to the account and entity associated with DI2 is relevant, and available to the entity EI1 associated with Device 1 (702). The server 701 retrieves the account information related to EI1 and determines that EI2 is listed in a friends list in the account associated with EI1 and that EI1 should be notified when EI2 is detected. Next the server retrieves the account information associated with EI2 and determines that EI1 is on a list of entities which are allowed to be notified of EI2 being present and personal information such a the name of the individual, their phone number and the like. The server having determined that EI1 wants to be notified and is allowed to be notified responds in Step 706 to Device 1 (702) with a message indicating the DI2 is relevant to EI1 and including information such as Entity Identifier EI2 and associated details. A user application on Device 1 (702) notifies the user that the entity associated with Device 2 is in proximity in step 707. The user of Device 1 provides input to the device directing it to request a chat session with the entity associated with Device 2 (703), and a message 708 is sent the server 701 commanding “send ‘Hello’ to EI2”. The server acknowledges reception of the message with a “ACK” message 709, in return. Next server 701 sends “Request Chat: ‘Hello’ from EI1” to Device 2 703. The user of Device 2 accepts the chat and returns a message “I'm by the front door” with message 711, sending it to the server to be relayed to device 1 (702).

E-Commerce Between Two Mobile Devices

[0059] FIGS. 8A and 8B show a message flow diagram for an embodiment where two individuals are performing a financial transaction on the street (for example, a customer and a street vendor). Each has a device (FIGS. 1, 106 and 108 respectively) enabled with the preferred embodiments described above. In this example, an individual's device would see a vendor and the vendor's device (enabled with various embodiments) would notify them that the vendor was also enabled with a device supporting the identifier search and other protocols described above, as well as being capable of electronic payments. These steps are performed in the following way. In step 804 the customer's device 802 (Device 1) performs an identifier search process as previously described, and detects a device identifier 2 (DI2) sent from Device 2 (803) belonging to the merchant. Device 1 will send a message to the server 801 (also represented by 100 in FIG. 1) using the WWAN (cellular data link such as GPRS, EDGE, 1×EV-DO, IS-2000, Wi-Max, LTE, or the like) 104 requesting information related to DI2 and its relevance to the entity related to device 1 802. The server 801 then determines the relevance of DI2 based on the account properties stored in the account associated with the consumer Device 1. In this case, the account settings only allow messages from or notifications of entities on a friends list stored in the account record (represented in FIG. 10) associated with the consumer. Server 801 responds to device 802 with “no” indicating that DI2 is not relevant to the Consumer.

[0060] The customer, having an account enabled with electronic payments, and wanting an item the vendor has, would press a button or make other input to his phone (or other device) which would indicate they would like to make a purchase and pay using their device (808). In this case the input selection would be “search for merchants.” The customer's device would then send a message (809) to the central server directing the server to perform a one time search for merchants, despite the current account settings. In one embodiment, the server would then direct the consumer's device 802 to initiate another search (809). Other embodiments may not include the server commanding Device 1 (802) to perform the search, but rather the search may be performed automatically, or use results from a recent search. In Step 811, Device 1 (802) performs another search and detects the identifier from Device 2 (803), DI2. Device 1 then sends a message 812 to the server again requesting information for all relevant devices detected, which will include at least DI2. In Step 813 the server, having received the request and list including DI2, looks up account information associated with DI2 and determines that the associated entity is a merchant. As the settings of the account associated Device 1 now allow for the notification of the user when a merchant is detected in proximity, DI2 is determined to be relevant to Device 1 and the Entity 1 (EI1) should be notified. The server then sends a message 814 to Device 1 (802) stating merchant services are available in proximity with a list of available merchant's information including information related to the entity (EI2). The user of device 1, Entity 1 (EI1) then provides input in step 815, (pressing a soft key on a touch screen for instance), selecting the specific merchant EI2 to engage with in a transaction. Device 1 (802) will then send a message (816) to the server requesting a transaction with EI2 associated with Device 2 (803). The server (801) will then respond in this embodiment with a message 817 to Device 1 confirming receipt of the requested transaction and providing information to allow the EI1 associated with Device 1 to independently confirm the identity of EI2 associated with Device 2 (803). In this embodiment the identifying information can include the name of the merchant, the merchant's logo, a picture of the vendor, or their mobile shopping cart. In other embodiments, the picture may be of a specific unattended vending machine in the location it is currently operating. It may also include other information such as the address of the merchant in cases where a fixed store location is provided. As this particular merchant in this example is a street vendor, an address may not be used. GPS information stored in the account associated with Device 2 may be used as further confirmation in some instances. However, in this example, GPS coordinates are not be available on Device 2 due to lack of capability, or Device 2 being indoors and without sufficient signal to determine a location. Further GPS information from Device 1 (802) may be used to provide further confirmation information. In this embodiment the photograph sent in message 817 shows a picture of the particular merchant and also his city issued business license in text and as a picture of where it is displayed on the cart. The consumer entity EI1 provides input to Device 1 in step 818 confirming the identity of EI2, the merchant entity associated with Device 2 (803). Device 1 then sends a message 819 to the server 801 confirming the identity of the merchant.

[0061] Server 801 then sends a message 820 to the merchant's device 803 notifying them of the request for a transaction with EI1. Device 2 (803) then indicates to the merchant that a customer with the capability and desire to pay electronically is in proximity. In step 821 the customer associated with Device 1 (802) places an order with the merchant associated with Device 2 (803) and a list of products to be purchased is generated and the merchant provides input to Device 2 (803) to proceed with a electronic transaction. In step 822 Device 2 performs a scan of identifiers and DI1 associated with device 1 (802) and the Consumer is detected. A request is sent to the server 801 with a list of identifiers which were detected to determine if any of them are relevant to the merchant. Note that while the merchant device 803, (and the merchant) have now been notified of the desire for EI1 to enter a transaction, they do not necessarily know the identifier for EI1 yet. In other embodiments, the identifier associated with EI1 and Device 1 (802) may be sent in message 819, and a confirmation that this identifier is detected during the scan process 821 may be performed at the device. In the preferred embodiment, further security may be provided by the having the server perform this function independently. The server performs this confirmation in step 824 may matching the device 1 identifier DI1 with the information stored in the account associated with Entity 1 (EI1) also referred to as the Consumer.

[0062] The server than generates a message 825 to Device 2 (803) indicating that EI1 is relevant, and the transaction participant is present. The message in the preferred embodiment can also include a picture of the Consumer. Additionally, the message could also include other pictures of other individuals allowed to use this device for purchases. If more than one identifier was detected in step 822 and matched in step 824 to entities having requested transactions previously which are pending for that merchant, a list of information for each entity involved with a pending transaction request can be provided in message 825. The merchant then selects the correct consumer using the picture of that consumer, confirming the identity of the part to the transaction in step 826. The consumer information provided in message 825 in another embodiment may simply be the name of the customer and the merchant may either ask their name, or request identification such as a driver's license. In the preferred embodiment, where a picture is passed in message 825, it is not necessary that the individual's name be passed to the merchant for the merchant to be able to provide confirmation of the identity of the Consumer thus providing a level of anonymity to the transaction such as may be present when cash is used.

[0063] Following the confirmation by the merchant of the identity of the Consumer participating in the current transaction in step 826, Device 2 sends a message 827 to the server confirming the identity of the Consumer as Entity 1 (E1), and with information required for the transaction including the list of products to be purchased, their prices, the total price, and a request to charge E1 this total amount. Server 801 then confirms receipt of this message in step 828. The server then sends a message 829 to Device 1 requesting the Consumer to confirm the list of goods to be purchased and the total price to be paid. In step 830, the Consumer (Entity 1) reviews the list and amount to be paid and provides input to device 1 confirming the accuracy of the information and they the authorizing the server to pay. In step 832 the server charges E1 utilizing stored preferred charge card information, stored credit, or other payment method such as a PalPal™ user name (PayPal is a trademark of Ebay, Inc.) and password stored in the account associated with E1, and charges the consumer. In the case where a stored credit is used, the Consumer's account can be debited, and the credits not applied to the merchants account until a later step. In the case of a credit card, or PalPal™ transaction, the server provides payment to E2 (the merchant) utilizing information stored in the account associated with Device 2. The server then indicates payment is made to the merchant, and instructing the merchant to deliver the goods with message 833. E2 (the Merchant) then provides the goods and provides input to Device 2 that the goods have been delivered in step 834. Message 835 is generated by Device 2 (803) to the server confirming product delivery, and acknowledging the receipt of the payment confirmation message 833. The server can then send message 836 requesting the Consumer to confirm they received the goods. If a confirmation is not received in response to this request, this information may later be used to settle any dispute that might arise. In step 837 the consumer confirms receipt of the products, and message 838 is generated to the server confirming the receipt of goods by the consumer. In Step 839 the server concludes the transaction by completing any steps required to credit the Merchant with the payment amount from the Consumer, if required. The server then sends a message 840 to the Merchant indication the transaction is complete, which is acknowledges in message 841. The Consumer is notified of the completed transaction with message 842, which is acknowledged with message 843.

[0064] Finally, the transaction details may be stored by the server, or sent to a thirdly party server for tracking spending habits of that account holder, or customers of that merchant allowing the merchant to track that specific customer's behavior and cater to them in the future with various specials delivered via email, or during their next visit via their device in the form of an electronic coupon. This process can be performed with a goal to help the merchant expose the customer to other products or services the merchant believes the customer might find desirable.

[0065] The apparatus, systems and methods can be extended to facilitate other types of transactions as well. In one specific application, consider use of the invention to facilitate a transaction such as the rental of an automobile. A well known business called ZipCar™, presently operating in several major urban areas in the United States, makes available a fleet of vehicles for shared use by their club members who pay a monthly fee plus a per use charge. Using the embodiments herein, the club member would have a wireless device that serves as the “Consumer device” (Device 1) and the ZipCar vehicle would be equipped with a wireless device serving as the “Merchant” device (Device 2). The consumer would walk up to an available ZipCar vehicle and, using their wireless device, start an initial exchange of identifiers with the desired Merchant device, for example, using the short range local wireless network. The Consumer device and/or Merchant device would send a message to an application running on the Server requesting that a person associated with an account for the Consumer be granted access to a specific vehicle (e.g., an “object”) that is in the vicinity of and associated with the Merchant device. A set of confirmatory messages (such as to exchange access codes, to confirm the location of the vehicle, the per-use fee due, and payment for the same, etc.), are then typically also exchanged between the Consumer and the Merchant device with the assistance of the Server and the long range wireless network. Upon confirmation of the necessary transaction information, the Server sends a message to the Merchant device to unlock the vehicle requested (which may be sent over the second long range wireless network or a yet another network, such as a satellite network).

Example of a Mobile Device and a Broadcast Device.

[0066] FIG. 9 shows a message flow diagram for an embodiment where an individual is in the presence of a broadcast device, such as for the museum example of FIG. 2. As with FIG. 2, the individual device 202 and the broadcast device 204 are present and enabled. In this example, an individual 902 is in a grocery store and their device 902 (Device 1) performs a scan for identifiers in step 904, as described previously. DI2 is detected having been transmitted from device 2 (903). Device 1 (902) sends a message to server 901 inquiring if DI2 is relevant to the entity associated with Device 1 and if the information associated with that device identifier (DI2) is available to be returned. In step 906, the server retrieves the accounts associated with both DI2 and Device 1 (EI1). The server detects that the entity associated with DI2 is an advertisement company, and that this device is a broadcast device only, and that there is an electronic coupon available for download to Device 1, and multimedia content available to be played if desired. Additionally, the account settings associated with EI1 allow for the notification of broadcast devices in proximity.

[0067] Server 901 then transmits a Response message 907 indicated the presence of the detected device and the content available. The device 902 requests input from the entity associated with the device 901 for permission to download the coupon, and the availability to play content such as video about how to prepare a recipe using the vendors product. In this case the individual associated with Device 1 accepts the content, and a message 909 is sent to the server accepting the content. Response message 910 begins the delivery of the content.

[0068] As previously mentioned, several key distinctions of this embodiment include that the user of device 902 may walk away out of range form the broadcast device 903 and continue to receive the content using their cellular link, or may choose to play the content at a later time having stored the detected like in a favorites list. Additionally, the content stored in the account associated with the broadcast device 2 (903) is relevant to the placement of the device and the products near it. Further, as the content is stored in the server 901 rather than in the broadcast device 903, the content may be updated, modified, or deleted at anytime. For example the server 901 knowing that the consumer has never been detected previously, may customize the electronic coupon to provide a deeper discount than a regularly detected consumer. In the case where the devices are used for electronic commerce as in FIG. 8, knowledge of the user's past purchases may be used to induce the consumer to try a new product. Alternatively if the consumer is a regular purchaser a loyalty program may provide a coupon upon a particular number of repeated purchases.

[0069] FIG. 10 is a processing flow chart performed by the server receiving a request from a device inquiring about the relevant and availability of information associated with detected device identifiers. In step 1001 the server is waiting for a request from a device. When a request is received in decision 1002, step 1003 is performed. In this step the account information associated with the requesting device is retrieved. In step 1004 the information associated with the accounts for each of the detected device identifiers is retrieved. In step 1005 the server performs a matching process between the policies of the requesting account and each of the policies for each account associated with each detected device identifier. In step 1006 the information related to the matched policies for the associated entities will be sent to the requesting mobile device.

[0070] Just as in the previous example of an identifier being deemed relevant to a user based on a friends list, permission for disclosing a device's presence may require being on a friends list as well. For example, when a server receives an inquiry from a device with a list of identifiers, it may only respond with information for users associated with the identifiers that are on that device's friends list, and on each of the individual's friend lists as well. These friends' lists and policies can be stored within a user account which allows for disclosure of a user's presence only to individuals on this list, such as described in FIG. 11 (to be described below.)

[0071] It is contemplated that the permissions not be an “all or nothing” decision, but that different classes of information may be assigned different permissions and mechanisms. An example of this might be a user's presence, identity, and cart services being made available to only one set of other accounts (or users), while the presence of an anonymous individual being made available to anyone, but with other classes services available such as multi-player games being treated differently. Additionally multiple contacts may be included in the account, each given customized permissions. An example can be that any user may be notified of an anonymous user or other information based on additional policies.

[0072] As only the server contains personal information, and performs the association of an account with a particular identifier, it can inherently enforce the security of the policies as a distinct advantage relative to true peer to peer services. In this way, the central server controls the process of passing information related to an account to a particular requesting device.

[0073] FIG. 11 shows an example account record to be associated with an entity and at least one device. The columns of the account record can consist of a Record Index which will be used to described the account, a Field which is a descriptive name for the contents stored in the record, and a Field Information Group Disclosure Policy Assignment List (PAL). The PAL provides rules for the disclosure of the information in the associated row in the Field column. The following list are possible PAL entries:

- [0074] ALL: may be disclosed to any requesting entity
- [0075] EXPLICIT APPROVAL: the Entity associated with the account must provide input approving the disclosure of the information
- [0076] NONE: Do not disclose this information to any other entity
- [0077] M: where M is a integer from 1 to N indicating a Information Group Disclosure Policy which may consist of a list of contacts, friends, groups, characteristics, and the like.

[0078] Most of the fields in FIG. 11 are self explanatory and typical in the industry such as the account number, however a few fields are worth a clarifying discussion. The Device identifier is in record index 2, with a Identifier type in record 4. The identifier type can define what type of identifier the device associated with this account would use. Record index 10 is the Entity Type Field. This describes is the entity is a Merchant, Individual, or if the device associated with this account is a broadcast only device.

[0079] Referring now to FIG. 12 a timing map reference for scanning times and dormant times for devices is shown. In one embodiment, it is desired that the power consumption and scan timing for the devices in a cellular network be reduced. Since the server and the WWAN is involved with all mobile devices, coordination of the broadcasting periods and the searching periods for the short range radios is possible. This can be based on a common reference time such as that provided by most cellular systems, any the time of day clocks inherently within mobile devices. This allows for reduced power consumption and other resource consumption in the devices. If no coordination is achieved, then the short range receivers in each device must be scanning for transmitted identifiers much more often and for longer durations. Utilizing a common timing base, and the central server to notify the devices of a coordination approach for “active times” and “non-active times” and will allow for the devices to minimize the power consumption in the transmission of and scanning for identifiers. This approach also allows for synchronizing the update of each device's identifier (as described previously) to enhance anonymity and security, coordinated with the central server. The “non-active times” may be used as “boundaries” over which the changing identifiers may be updated. This update may be based on either direct communication with the server, or rule and algorithm based updates previously coordinated with the central server so as to minimize server messaging, but allowing the updates to remain synchronized to the server such that the device and the server are always associating the same identifier between them.

[0080] As will be recognized by an individual skilled in the area of information technology, the concept of a central server may well be implemented as a collection of servers to allow for load balancing, redundancy, and the like in a manor common to the information technology industry.

[0081] FIG. 13 shows a diagram of functional blocks associated with the management of dynamically assigned device identifiers. The Server 1301 has an application agent called an Identifier Manager (1303) which has access to a pool of device identifiers (1302). The Identifier Manager monitors timing information and determines when it is time to update a particular device's identifier. This time may be a regular interval, or a random generated time period by an algorithm such as a pseudo-random sequence generator, or a combination of both. When it is time to update a device identifier, Manager 1303 retrieves a new identifier form the pool 1302. The pool of identifiers may be a list or range of identifiers, or generated algorithmically. The new identifier is stored in the account associated with the entity determined to require updating and a message sent to the device 1305 associated with that account commanding it to update its device identifier with the new one. This message is sent over the WWAN Data network 1304 such as IS-2000, HSPA, GPRS, IS-95, Edge, Wi-Max, and the like. All devices 1305 to 1307 will eventually all be updated in a similar manner. This update process does not disrupt ongoing communication and interaction between devices despite the update as the communications are preformed based on the identity of the entities following the detection of the device identifiers which are no longer utilized. This unique capability allows for the updating process to be implemented and not impact the applications being utilized concurrently.

[0082] Other example applications utilizing still other embodiments follow below.

[0083] Requiring the brokering of the communication via a central server can also allow a mobile device to receive information associated with a “broadcast only” device, such as in the museum example discussed previously. This is important, as such broadcast devices can enable a vast set of new applications built upon the infrastructure developed in this application, beyond the museum application. Some of these applications may involve an electronic commerce aspect, for example.

Electronic Commerce Applications

Ecommerce Between a Fixed Broadcast Device and a Mobile Device

Football Stadium Example

[0084] An embodiment of a transaction model, enabled by the infrastructure described above can be an event such as a concert, or sporting event (particularly when it is an indoor venue where no GPS is available). A number of the broadcast only devices are placed through out the seating areas. The devices are very short range, and only transmit intermittently and as a result may be battery powered and to remain active over a very long time period. Each device can be placed in a known location, in a predicable manner.

[0085] An attendee at the event has his or her device enabled with the identifier protocol and other embodiments described above. The device detects a broadcast device, and interacts over the internet with the server via the WWAN connection (as already described above). The server receives an indication of the broadcast device's identifier and the identifier of the account associated with the device which detected the broadcast device. The server retrieves content associated with the service provider's account and provide that content to the application on the requesting mobile device. The content may indicate that the venue has a product delivery service. The user may then press an indication on their device that they would like to see a menu or list of items for sale from the merchant(s) in the venue. The application on the user's device would then allow them to see a menu, for instance, and select items to purchase. The user then would be asked to confirm the purchase. The server would then indicate to the merchant that a user located near a specific broadcast device has ordered something. In this case, it is expected that a delivery fee could also be charged for the enhanced service. The server would facilitate the purchasing of the goods or services from the merchant and payment from customer's account, and provide confirmation to each. Such confirmation can include an electronic receipt provided to the customer, for user upon arrival of the delivery person of the good or service. The customer can then select an indication on their device confirming receipt of the good or service via the mobile device, thereby completing the transfer of funds and the transition. Optionally, the delivery person of the good or service may have an enabled mobile device as well. In this case the identifiers may be detected by the customer's device and reported to the server to confirm that the provider's delivery person was present. Further, the delivery person's device can be able to detect the broadcast device's identifier and reported to the server confirming the delivery person was in the correct area independently. Even further proximity confirmation may be achieved by the customer's device's transmitted identifier being detected by the delivery person's device and reported to the central server further confirming the physical proximity of the parties involved in the transaction. Upon arrival of the delivery person, the customer may be notified that the delivery person is looking for them, and has arrived. These cross confirmations can allow for the central server evidence to justify payments both in completed transactions and in disputed or failed transactions. Further, the delivery person may receive a picture of the requesting customer assisting to identify the customer to whom the food is to be delivered. Once the customer is found, the delivery person can confirm the delivery of the good or service to the customer via the user input on their mobile device, and that confirmation being reported to the central server. The customer can have the option to report confirmation or denial of the reception of the product or service as well, as in the last example.

[0086] In another embodiment, the merchant device may be fixed, but have an internet connection (wireless or otherwise). Further, in some embodiments, the merchant may be an automated device such as a vending machine. In such a model, a customer may use their enabled cell phone to purchase an item such as a beverage from the machine without the need to insert currency into the machine. This can be accomplished by the customer's cell phone detecting the vending machine transmission of the identifier or visa-versa. Following the detection of either the customer's identifier by the vending machine, or the customer detecting the vending machine identifier, the respective device notifies the server, which in turn provides notification (assuming the account settings allow for notification) to the potential customer via their device. Assuming the customer selects to purchase an item from the vending machine using their account associated with their device, the customer may be presented a menu as in the example above. The customer may further be presented information to ensure the identity of the vending machine, such as a description of the machine, a machine identification number, or a (most likely) a picture of the machine where it is located. The customer can then confirm this is the machine they are interfacing with, and select to pay via their account. The customer may in one model select the item to dispense by input to their phone, or they may simply select to provide payment to the machine allowing them to make the selection manually as is the typical mode of operation today. The vending machine can then interact with the server via its own internet connection, and participate in the transaction in a manner similar to the mode described above allowing for step by step confirmation as previously described.

Electronic Opinion Polling, Tied to a Known Location.

[0087] In a much simpler example, such a capability might be used to tie a survey to a known location in such a way as to provide an e-coupon to the survey taker on their device in return for completion of the survey. Alternatively, this type of interaction can enable a very large crowd to interact with a Jumbo-Tron like display to provide input to polls or to participate in group activities. Users at different locations in a audience may form teams and interact with other teams for group activities.

Other Preferred Embodiments

[0088] Applications running on a device may also interact with the server to perform various functions, for example retrieving information associated with an entity or device, by utilizing a detected identifier. Such information may include stored content associated with the entity's account record such as music, pictures, links to social networking sites, instant messaging addresses, advertising content, and even executable scripts or application such as in AJAX. An example of such an application may include the detection of a device's identifier in a fixed location allowing for tour guide like information to be provided for that location.

[0089] As the server may be running applications which perform more function than just the retrieval of content, a pre-defined interaction process may also be applied by the server to the devices such as allowing the approval to share private content with the entity associated with the detected device. This process may eventually allow or disallow the sharing of information and to facilitate the interacting with another entity.

[0090] As a more complex example, in other embodiments, the devices may utilize the server as a third party to provide for new capabilities such as a secure three way e-commerce transaction between two entities. In this more complex process, the server may require confirmation of each party's identity with visual cross verification of the parties using pictures or other unique identifiers. The server may use this visual cross verification in conjunction with detecting that the individuals are in proximity with each other. The server may verify the proximity using GPS or using the peer to peer detection process in another embodiment. Further, the server may facilitate a process requiring each party to perform a step by step confirmation during the transaction including the stages of: the request for purchase, the payment, the receipt of goods and services, and the providing of payment receipt.

[0091] This differs from the approaches employed by prior art location aware mobile social networking techniques in that no GPS is needed to determine when one device is in proximity to another. Many wireless devices in use are not GPS-capable, and even when they are, GPS will often not operate indoors or where the GPS signal is weak. Using a peer to peer detection process to locate nearby devices allows for the operation of proximity detection indoors.

[0092] Preferred embodiments can also differ from known peer to peer based social networking in that the information flow between the devices running the applications are over the wide area network via a central server, rather than carried over the peer to peer network itself. An example of this is a service called Flobbi, as discussed previously, where community members can identify each other via Bluetooth transmissions, then interact with chat. The messaging in this case is carried over Bluetooth itself. A distinction from such peer to peer approaches is the use of a central server to “broker” the transactions between peers, enhancing the ability to manage security and information disclosure. Such use allows for the opportunity to customize delivered content to include elements such as advertising or other content customized to the recipient based on additional information such as known personal purchasing history, or interests.

[0093] A further distinction of the preferred embodiment is the use of a central server to determine identities of detected peer devices, which additionally allows for secure and fraud resistant application of policies for the disclosure of information and content. An issue with the existing pure peer to peer approaches is that they are not capable of enforcing policy associated with the disclosure of information to unknown entities in a secure and fraud resistant manor. One reason for this is that information related to a user's device must be disclosed in the process of detection in the form of a static identifier. By the nature of the identifier, it must be static or peers would not be able to directly determine the identity of a friend over time with the information stored on their device. By using a central server, the system may coordinate the change of the identifiers from time to time such that the disclosure of an identifier by one device to another does not compromise the identity of the device. In this case the identifier may be assigned from a central server and such server coordinate the identifier's change from time to time.

[0094] Reliance on a central server also allows the secure and fraud resistant application of disclosure policy. Such policy might include the verification of the identity of the party to which information (identity and presence for instance) or content (pictures of the account owner) is to be provided. Such verification is performed in an anonymous way such that in the process of verifying information associated with each party, no personal information is disclosed between the parties prior to satisfaction of some pre-set policy such as inclusion on a friend list or belonging to a specific group or organization. Another important policy required for such services would be the determination of any past negative feed back ratings by other past peers for behavior for the particular user to which the information is to be provided. An individual with significant poor ratings having detected a peer, may be denied access to personal information or even notification of arrival of the detected peer based on the server policy setting by the detected peer or the server in general.

[0095] A further distinction is to enable electronic payments for individuals who are in close proximity to each other. The central server can act as a third trusted party to help facilitate the electronic transaction between the individuals. Secondly, the server allows for a convenient, electronically secure, personally secure and anonymous method for each of the individuals to specify the party with which they wish to engage in a transaction. Thirdly, participants in a transaction can cross validate the identities of the individuals engaged in the transaction. Finally, because this method is proximity based it will also work indoors or in other situations where GPS location information is not available.

Feature Summary of Preferred Embodiments

[0096] 1. In a first embodiment:

- [0097] One device is transmitting a wireless identifier using a wireless protocol capable of peer to peer communication;
- [0098] The wireless identifier being associated with a specific account on a server connected to the internet;
- [0099] A second device receiving the wireless identifier
- [0100] The second device capable of communicating with the server over an internet connection;
- [0101] The second device requesting information from the service associated with the first identifier

[0102] The second device having a second identifier associated with a second account on the server; and/or

[0103] The server providing different amounts of information related to the first account based on the parameters associated with one or both of the first and second accounts

[0104] The identifiers associated with the accounts being updated such that the identifiers would no longer be recognized as being associated with specific accounts without past or current interaction with the server;

[0105] Using one or more of Cellular network timing information, and information form the central server to coordinate the broadcast and search times amongst the devices. (to reduce power and resource consumption); and/or

[0106] Data necessary to engage in an E-commerce transaction may be exchanged as well such as the identity verification such as via a picture and/or mutual identifier detection.

[0107] 2. In a second embodiment,

- [0108] A device is capable of operating two wireless protocols simultaneously, utilizing a first wireless protocol in the device to detect the proximity of another wireless device and using the second wireless protocol to communicate with a remote server, where:
- [0109] One or more of the devices are mobile devices;
- [0110] Where the first wireless protocol is a local, or personal area network wireless protocol such as 802.11, Bluetooth, UWB or other local connectivity protocol;
- [0111] Where the first wireless capability used for detecting the presence of another device, or advertising the presence or a device;
- [0112] Utilizing a wireless wide area data link from one or more of the wireless devices to, optionally:
- [0113] Connect to a central server;
- [0114] Perform user authorization functions;
- [0115] Perform download of information associated with account identifiers utilizing the short range wireless capability;
- [0116] Request forwarding of messages/packets to the other active account;
- [0117] Utilizing the messaging with a mobile proximity based social networking capability; and optionally,
- [0118] The messaging being performed via the WWAN; and/or
- [0119] The server providing a centrally assigned user identity, with relationship brokering or identification capability.

[0120] 3. In another embodiment,

- [0121] A central serving capability is provided to mobile devices utilizing a wireless WAN connection to provide and exchange information between one or more application on one or more wireless devices and the central server where
- [0122] the information passed to the central server is collected by one wireless device from another wireless device via a separate local wireless reception from the other wireless device;
- [0123] the separate local wireless reception from the second wireless device contains information directly assigned by, derived from, or known to the central server associated with the identity of the second wireless device;
- [0124] this identity is related to certain information and preferences of an account holder associated with an application operating on the second wireless device;
- [0125] the application is operating on both wireless devices;
- [0126] the application operating on the first device also provides its own identifying information to the central server as well as detected identifiers from devices with applications on them;
- [0127] The central server contains account information registered to the applications running on each wireless device;
- [0128] The preferences associated with the account information also contain policies related to the disclosure of one accounts stored information to other accounts and hence to their application on their devices;
- [0129] These policies including a classification of other accounts each classification having different policies some of these policies being one of:
- [0130] no not allow notification of my presence
- [0131] allow notification of my presence
- [0132] disclose my name/do not disclose my name
- [0133] disclose age/do not disclose age
- [0134] disclose personal details;
- [0135] Where an application running on each device can optionally perform point of sale transitions coordinated via the central server, over the WWAN, utilizing user input on each device as confirmation of successive steps in the transition;
- [0136] Further, where at least one of the confirmation steps additionally involves displaying an identifying picture related to one of the devices, on the other device;
- [0137] Additionally the server performing an authorization for the transition to a third party;
- [0138] Or, optionally, a device is interacting with a point of sale device to associate an itemized list of items with a detected second device;
- [0139] The service performing a confirmation with the application on the second device requiring user input that the bill of goods list is correct; and/or
- [0140] The server storing the information related to the second devices detected account identity and inventory in a database for later use

[0141] 4. In still other embodiments, a device has a wireless capability with no WWAN capability, but only with the ability to broadcast a unique identifier, and

- [0142] A central server stores having the broadcast device's details;
- [0143] And when the first device provides these detail to the server, authorized and current information about the broadcast device are provided to the first wireless device;
- [0144] Where this information optionally includes advertising information or information related to “e-coupons” for special offers for products or services; and/or
- [0145] Where the content of the e-coupons might be customized based on the identity of the requesting device or account holder;
- [0146] Where the content is further customized based on other information known by the server related to the user's account; or
- [0147] Where the other information is related to the user's past purchasing practices or previous requests; and/or
- [0148] A mobile device, upon detecting a broadcast device and if enabled to do so, will report that broadcast Id to the server over a WWAN, and retrieve the current content from the server associated with that device and:
- [0149] Display it to the user on their device; or
- [0150] Execute instructions associated with the information retrieved from the server.

[0151] 5. In still further embodiments, a good or service delivery model utilizing the above described broadcast device, is placed in a known location, and further

- [0152] A mobile device is for detecting the fixed device's identifier via the WPAM/WLAN;
- [0153] The mobile device reporting this identifier and passing an identifier associated with itself, or the account associated with the user utilizing the device;
- [0154] The server determining that the detected broadcast device is associated with the broadcast device with a known location;
- [0155] The server further determining that the identifier is associated with a service, and further associated with an account or that service;
  - [0156] The server retrieving content associated with the service provider's account and providing that content to the application on the requesting mobile device;
- [0157] Where that content may be a list of items for sale, services for sale, a opinion pole, food menu, or other menu style content which allows for user selection of items, which can be implemented in java code, xml, simple text, or other for example optionally including active code elements;
- [0158] The application on the mobile device displaying the content to the user display with the itemized list of goods, services, or other selection items;
- [0159] A user providing selection of one or more of the items, and confirming they wish to purchase said items, and take delivery at or near the location of the fixed broadcast device;
- [0160] The server facilitating the purchasing of the goods or services from the merchant's account and the customer's account, and providing confirmation to each. Such confirmation including an electronic receipt provided to the customer, for user upon arrival of the deliverer of the good to or service;
- [0161] The customer confirming receipt of the good or service via the mobile device, thereby completing the transfer of funds and the transition; and/or
- [0162] The deliverer of the good or service optionally having a mobile device and optionally:
- [0163] such that identifiers from that device may be detected by the customers device and reported to the server to confirm that the provider's delivery person was present;
- [0164] such that the broadcast devices identifier is detected by the delivery person's mobile device and reported to the server confirming the deliver person was in the correct area
- [0165] such that the customer's device's transmitted identifier is detected by the delivery persons device and reported to the central server further confirming the physical proximity of the parties involved in the transaction; and/or
- [0166] The delivery person confirming the delivery of the good or service to the customer via the user input on their mobile device, and that confirmation being reported to the central server.

[0167] 6. In another embodiment, a software program is arranged to operate at the application layer on a mobile device, which interfaces to a device driver interface:

- [0168] Using wi-fi 802.11 to perform a WLAN local connection protocol; or
- [0169] Using Bluetooth to perform the WLAN local connection;
- [0170] Where the device driver interface is an NDIS driver or the like;
- [0171] Using 1×EVDO, HSDPA, GPRS, EDGE or the like for a wide area WWAN interface;
- [0172] The application then providing the reported identifiers to a server, which will make decisions regarding a users interest in these detected identifiers, and policy regard privacy other identifiers;
- [0173] The decision process optionally based on priority of the identifier, the class an identifier belongs to, a list the identifier is, or is not included on;
- [0174] Based on the result of the action function,
- [0175] Sending at least one detected identifier to the network, potentially with additional information from the action function, and retrieving information back from the server related to that identifiers' account information stored on that server;
- [0176] The server then receiving a request from a device's application, with a detected identifier
- [0177] The server examining both the requesting and the requested identifier's identity and making a policy decision regarding the release of the requested identifiers information related to their account;
- [0178] The server in some cases providing a continuously or periodically changing account or device identifier to a specific application on a device to enhance the privacy of the identity of that device;
- [0179] The changing of the identifier may be effected by a rule based generation local to the application, or may be downloaded from the server directly; and/or
- [0180] The update of the identifier being synchronized to such that it is coordinated with predetermined scanning and broadcasting periods allowing for a known update boundary;

[0181] 7. In still another embodiment, a method uses the mobile device's time of day derived from the network or other reference for

- [0182] synchronizing a PAN/WLAN discovery and advertisement times to save battery life;
- [0183] doing the same in a synchronized way among multiple devices;
- [0184] while coordinating the timing information utilizing the WWAN and a central server available commonly to the devices, such as by
- [0185] Synchronizing identifier transmission timing to save power from WWAN network parameters obtained for the server;
- [0186] Coordinating any identifier updates to this same timing source; and/or
- [0187] Using a pool of identifiers available to the central server to assign identifiers to devices changing the identifiers at some time interval derived for the common time reference

[0188] 8. In another embodiment,

- [0189] A central server uses an identity manager to assign identifiers to devices using a WWAN cellular data link, and wherein

[0190] identifiers are occasionally changed

[0191] identifiers are assigned from a pool of identifiers available to the servers;

[0192] identifiers are used as 48 bit media access control (MAC) addresses of the short range wireless network adapter

[0193] identifiers are optionally used as

- [0194] an SSID in a IBSS in IEEE-802.11 network beacons
- [0195] a BSSID of the IEEE802.11 network adapter;

[0196] in a IEEE802.15.1 Inquiry Response Message as the BD_ADDR

[0197] a device name in a Bluetooth name response packet; or

[0198] listed in a services list as provided in a LMP_features_req message or LMP_features_req_ext message for a Bluetooth device

[0199] While this invention has been particularly shown and described with references to example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.

Claims

What is claimed is:

1. A method comprising:

receiving, by a server, from a first mobile wireless device, a first location reporting message, wherein the first location reporting message comprises information derived from a particular beacon transmission associated with a beacon location service, the particular beacon transmission having been transmitted by a second mobile wireless device and detected by the first mobile wireless device, wherein the first location reporting message includes:

i) a unique identifier of the particular beacon transmission or information derived from the unique identifier of the particular beacon transmission, and

ii) a location of the first mobile wireless device associated with the detection of the particular beacon transmission by the first mobile wireless device;

sending, by the server, a message so as to enable an entity associated with the second mobile wireless device to be informed of the location associated with the detection of the particular beacon transmission by the first mobile wireless device;

wherein the detection of the particular beacon transmission by the first mobile wireless device associated with the beacon location service includes the particular beacon transmission having been received by the first mobile wireless device utilizing a Bluetooth wireless protocol and transmitted by the second mobile wireless device, wherein the particular beacon transmission was unsolicited and includes (a) a MAC address, (b) a unique identifier wherein the unique identifier of the particular beacon transmission is a numeric value which does not directly identify a location at which the particular beacon transmission occurred, and (c) a beacon service identifier identifying a service not accessible via the Bluetooth wireless protocol, and wherein the beacon service identifier of the particular beacon transmission had the value of the beacon service identifier equal to a particular beacon service identifier identifying the beacon location service; and,

wherein the particular beacon service identifier identifies the beacon location service in which a detecting device:

a) filters beacon transmissions which were received having the particular beacon service identifier;

b) sends at least one location reporting message to the server associated with the beacon location service utilizing a cellular communications protocol or wireless local area communications protocol, based upon at least one of the filtered beacon transmissions, in which the at least one location reporting message comprises:

i) a unique identifier of the at least one filtered beacon transmission or information derived from the unique identifier of the at least one filtered beacon transmission, and

ii) a location of a detecting mobile wireless device associated with the detection of the at least one filtered beacon transmission by the detecting mobile wireless device, and

wherein both the MAC address and the unique identifier values for beacon transmissions having the particular beacon service identifier value from a particular transmitting device change values over time, while the particular beacon service identifier value remains the same.

2. The method of claim 1, wherein the first mobile wireless device is a cellular phone.

3. The method of claim 1, wherein the MAC address is a pseudorandom value.

4. The method of claim 1, wherein the MAC address is not usable as an address in transmissions to be received by the second mobile wireless device using the Bluetooth wireless protocol.

5. The method of claim 1, wherein the second mobile wireless device is configured to operate in a broadcast only mode of operation in connection with the beacon location service.

6. The method of claim 1, wherein the beacon service identifier of each filtered beacon transmission identifies a wireless beacon service in which the unique identifier is relevant to stored information relating to an entity or object associated with a transmitter of a filtered beacon transmission.

7. The method of claim 6 further comprising storing the stored information at the server.

8. The method of claim 1, wherein the first mobile wireless device further comprises:

a first radio for at least one of cellular communications and wireless local area communications and a second radio for communications using the Bluetooth wireless protocol; and wherein the method further comprises:

receiving, by the server, from a second detecting mobile wireless device, a second location reporting message comprising second information derived from a second particular beacon transmission associated with the beacon location service, the particular beacon transmission having been transmitted by the first mobile wireless device and detected by the second detecting mobile wireless device, wherein the second location reporting message includes:

i) a unique identifier of the second particular beacon transmission or information derived from the unique identifier of the second particular beacon transmission, and

ii) a location of the second detecting mobile wireless device associated with the detection of the second particular beacon transmission by the second detecting mobile wireless device;

wherein the second radio of the first mobile wireless device operates as a beacon transmitter;

the first mobile wireless device being further configured to perform:

transmitting from the beacon transmitter of the second radio, using the Bluetooth wireless protocol, a second plurality of beacon transmissions each of the beacon transmissions including (a) a MAC address, (b) a unique identifier wherein the unique identifier of each respective beacon transmission is a numeric value which does not directly identify a location of the second mobile wireless device, and (c) a second beacon service identifier, and wherein one or more of the beacon transmissions of the second plurality of beacon transmissions have the value of the second beacon service identifier equal to a second particular beacon service identifier;

wherein the second particular beacon service identifier identifies the beacon location service.

9. The method of claim 8 wherein,

during a first time period, a first plurality of the beacon transmissions including the particular beacon service identifier includes a first MAC address and a first unique identifier;

during a second time period, a second plurality of the beacon transmissions including the particular beacon service identifier includes a second MAC address in place of the first MAC address, and a second unique identifier in place of the first unique identifier; and,

the server providing a first location information report during the first time period based upon the first unique identifier and a second location information report during the second time period based upon the second unique identifier, so as to enable the entity associated with the second mobile wireless device to be informed by the server of the locations associated with detection of beacon transmissions associated with the particular beacon service during each of the first time period and the second time period.

10. The method of claim 9, wherein the second radio of the first mobile wireless device is configured to operate in a broadcast only mode of operation.

11. The method of claim 10, wherein the first mobile wireless device is further configured to transmit at least one additional beacon transmission containing at least one additional beacon service identifier, wherein the at least one beacon service identifier of is associated with at least one of the following services:

a) a file transfer service to a device in proximity associated with an entity, and

b) a service to provide access to a device located in proximity to the mobile wireless device.

12. The method of claim 1, wherein the first mobile wireless device is further configured to transmit at least one additional beacon transmission containing at least one additional beacon service identifier, wherein the at least one additional beacon service identifier of is associated with at least one of the following services:

a) providing an access code; and

b) a service to provide stored information, wherein the service includes receiving a request for approval to share stored information, and, upon approval of the request to share stored information, sharing the stored information, wherein the information comprises an access code.

13. The method of claim 1 further comprising:

determining, by the server, that the second mobile wireless device is being detected by the first mobile wireless device for the first time; and

performing, by the server, a first action based on a determination that the detection is for the first time.

14. A method comprising:

receiving, by at least one server of a particular beacon location service which is configured to receive location reporting messages from a detecting mobile device and provide location information reports, so as to enable an entity associated with a mobile wireless device to be informed by the at least one server of a location associated with detection of beacon transmissions associated with the particular beacon location service from the mobile wireless device;

providing, by the at least one server of the particular beacon location service, a first location information report during a first time period based upon a first unique identifier and a second location information report during a second time period based upon a second unique identifier, so as to enable the entity associated the mobile wireless device to be informed by the at least one server of the locations associated with detection of beacon transmissions associated with the particular beacon location service during each of the first time period and the second time period;

wherein the mobile wireless device comprises:

a first radio for providing reception and transmission of data utilizing a Bluetooth wireless protocol;

one or more processors; and

one or more memory devices coupled to the one or more processors;

wherein the first radio is configured as a beacon transmitter;

wherein the beacon transmitter is configured to transmit, using the Bluetooth wireless protocol, a plurality of beacon transmissions each of the beacon transmissions including (a) a MAC address, (b) a unique identifier wherein the unique identifier of each respective beacon transmission is a numeric value which does not directly identify a location of the mobile wireless device, and (c) a beacon service identifier, and wherein one or more of the beacon transmissions of the plurality of beacon transmissions have the value of the beacon service identifier equal to a particular beacon service identifier in which the unique identifier is relevant to stored information relating to an entity or object associated with a transmitter of a respective beacon transmission;

wherein the value of the MAC address and the value of the unique identifier changes over time for beacon transmissions having a same particular beacon service identifier value from the beacon transmitter using the Bluetooth wireless protocol;

wherein the particular beacon service identifier is configured to identify the particular beacon location service in which:

a) the detecting mobile device associated with the particular beacon location service is configured to filter the plurality of beacon transmissions which were received having the particular beacon service identifier;

b) the detecting mobile device associated with the particular beacon location service is further configured to send one or more location reporting messages to a server associated with the particular beacon location service comprising a respective unique identifier of the filtered beacon transmissions or information derived from the respective unique identifier and a respective location of the detecting mobile device;

wherein the first unique identifier and the second unique identifier are transmitted by the mobile wireless device within the plurality of beacon transmissions; and

wherein the beacon transmissions are unsolicited transmissions.

15. A method comprising:

receiving, by at least one server of a particular beacon location service, at least one location reporting message from a detecting mobile device associated with the particular beacon location service;

providing, by the at least one server, location information reports, so as to enable an entity associated with a mobile wireless device to be informed by the at least one server of a location associated with detection of beacon transmissions associated with the particular beacon location service from the mobile wireless device,

wherein the mobile wireless device comprises a first radio for providing reception and transmission of data utilizing a Bluetooth wireless protocol;

one or more processors; and

one or more memory devices coupled to the one or more processors;

wherein the first radio is configured as a beacon transmitter;

wherein the value of the MAC address and the value of the unique identifier changes over time for beacon transmissions having a same particular beacon service identifier value from a particular beacon transmitter device using a Bluetooth wireless protocol;

wherein the particular beacon service identifier is configured to identify the particular beacon location service which enables the entity associated with the mobile wireless device to be informed by the at least one server of the location of the mobile wireless device;

wherein the particular beacon location service identified by the particular beacon service identifier is one in which:

16. The method of claim 15, wherein the mobile wireless device is capable of operating in a broadcast only mode of operation.

17. The method of claim 15, further comprising,

receiving, by the at least one server, location reporting messages from the detecting mobile device utilizing a second radio, wherein the location reporting messages comprise a unique identifier or information derived from the unique identifier derived from the beacon transmissions of the mobile wireless device, and a location of the detecting mobile device, so as to enable an entity associated with the mobile wireless device to be informed by the server, of a location associated with detection of beacon transmissions associated with the particular beacon service from the detecting mobile device;

the detecting mobile device being further configured to:

utilize the second radio for at least one of cellular communications and wireless local area communications and wherein the detecting mobile device being further configured to receive beacon transmissions utilizing the first radio and including the particular beacon service identifier transmitted from a second mobile wireless device utilizing the Bluetooth wireless protocol.

18. The method of claim 15, wherein the detecting mobile device is further configured to transmit at least one additional beacon transmission containing at least one additional beacon service identifier, wherein the at least one additional beacon service identifier of is associated with at least one of the following services:

a) a file transfer service to a device in proximity associated with an entity, and

b) a service to provide access to a device located in proximity to the mobile wireless device.

19. The method of claim 17 further comprising:

determining, by the at least one server, that the mobile wireless device is being detected by the detecting mobile device for the first time; and

performing, by the at least one server, a first action based on a determination that the detection is for the first time.

20. The method of claim 19 further comprising:

performing, by the at least one server, a second action based on a determination that the detection is not for the first time.

Patent Citations (619)

Patent	Date	Inventor	Cited By
US5121126(A)	1992-06-01	Clagett	Applicant
US5541604(A)	1996-07-01	Meier	Applicant
US5671525(A)	1997-09-01	Fidalgo	Applicant
US5690773(A)	1997-11-01	Fidalgo et al.	Applicant
US5745037(A)	1998-04-01	Guthrie et al.	Applicant
US5767503(A)	1998-06-01	Gloton	Applicant
US5804803(A)	1998-09-01	Cragun et al.	Applicant
US5815811(A)	1998-09-01	Pinard et al.	Applicant
US5901303(A)	1999-05-01	Chew	Applicant
US5977877(A)	1999-11-01	McCulloch et al.	Applicant
US5987011(A)	1999-11-01	Toh	Applicant
US6002918(A)	1999-12-01	Heiman et al.	Applicant
US6043747(A)	2000-03-01	Altenhofen	Applicant
US6049711(A)	2000-04-01	Ben-Yehezkel et al.	Applicant
US6067297(A)	2000-05-01	Beach	Applicant
US6081629(A)	2000-06-01	Browning	Applicant
US6091342(A)	2000-07-01	Janesch et al.	Applicant
US6151647(A)	2000-11-01	Sarat	Applicant
US6163771(A)	2000-12-01	Walker et al.	Applicant
US6188681(B1)	2001-02-01	Vesuna	Applicant
US6199048(B1)	2001-03-01	Hudetz et al.	Applicant
US6233565(B1)	2001-05-01	Lewis et al.	Applicant
US6236674(B1)	2001-05-01	Morelli et al.	Applicant
US6259898(B1)	2001-07-01	Lewis	Applicant
US6422462(B1)	2002-07-01	Cohen	Applicant
US6439345(B1)	2002-08-01	Recktenwald et al.	Applicant
US6446208(B1)	2002-09-01	Gujar et al.	Applicant
US6487540(B1)	2002-11-01	Smith et al.	Applicant
US6487601(B1)	2002-11-01	Hubacher et al.	Applicant
US6493550(B1)	2002-12-01	Raith	Applicant
US6553006(B1)	2003-04-01	Kalliokulju et al.	Applicant
US6580700(B1)	2003-06-01	Pinard et al.	Applicant
US6587034(B1)	2003-07-01	Heiman et al.	Applicant
US6601040(B1)	2003-07-01	Kolls	Applicant
US6615804(B2)	2003-09-01	Matthews et al.	Applicant
US6616049(B1)	2003-09-01	Barkan et al.	Applicant
US6629149(B1)	2003-09-01	Fraser et al.	Applicant
US6675017(B1)	2004-01-01	Zellner et al.	Applicant
US6675153(B1)	2004-01-01	Cook et al.	Applicant
US6700535(B2)	2004-03-01	Gilkes et al.	Applicant
US6712274(B2)	2004-03-01	Dvorkis et al.	Applicant
US6715681(B2)	2004-04-01	Dvorkis	Applicant
US6716101(B1)	2004-04-01	Meadows et al.	Applicant
US6738808(B1)	2004-05-01	Zellner et al.	Applicant
US6788702(B1)	2004-09-01	Garcia-Luna-Aceves et al.	Applicant
US6791997(B2)	2004-09-01	Beyer et al.	Applicant
US6799049(B1)	2004-09-01	Zellner et al.	Applicant
US6837436(B2)	2005-01-01	Swartz et al.	Applicant
US6845338(B1)	2005-01-01	Willins et al.	Applicant
US6857021(B1)	2005-02-01	Schuster et al.	Applicant
US6868079(B1)	2005-03-01	Hunt	Applicant
US6901270(B1)	2005-05-01	Beach	Applicant
US6909399(B1)	2005-06-01	Zegelin et al.	Applicant
US6909721(B2)	2005-06-01	Ekberg et al.	Applicant
US6928263(B2)	2005-08-01	Blake	Applicant
US6929149(B2)	2005-08-01	Selfridge et al.	Applicant
US6934535(B2)	2005-08-01	Pyhaelammi	Applicant
US6965914(B2)	2005-11-01	Dowling	Applicant
US6970850(B1)	2005-11-01	Freeny, Jr.	Applicant
US6978165(B2)	2005-12-01	Martinez et al.	Applicant
US6990587(B2)	2006-01-01	Willins et al.	Applicant
US6993049(B2)	2006-01-01	Davies	Applicant
US7000001(B2)	2006-02-01	Lazaridis	Applicant
US7003283(B2)	2006-02-01	Hiltunen et al.	Applicant
US7005968(B1)	2006-02-01	Bridgelall	Applicant
US7010267(B2)	2006-03-01	Vanluijt et al.	Applicant
US7016336(B2)	2006-03-01	Sorensen	Applicant
US7020106(B2)	2006-03-01	Barnard et al.	Applicant
US7030761(B2)	2006-04-01	Bridgelall et al.	Applicant
US7030812(B2)	2006-04-01	Bekritsky et al.	Applicant
US7039027(B2)	2006-05-01	Bridgelall	Applicant
US7039358(B1)	2006-05-01	Shellhammer et al.	Applicant
US7065559(B1)	2006-06-01	Weiss	Applicant
US7126926(B1)	2006-10-01	Bjorklund et al.	Applicant
US7127236(B2)	2006-10-01	Khan et al.	Applicant
US7142120(B2)	2006-11-01	Charych et al.	Applicant
US7142527(B2)	2006-11-01	Garcia-Luna-Aceves	Applicant
US7151764(B1)	2006-12-01	Heinonen et al.	Applicant
US7156311(B2)	2007-01-01	Attia et al.	Applicant
US7158756(B2)	2007-01-01	Palin et al.	Applicant
US7167487(B2)	2007-01-01	Herrmann	Applicant
US7173922(B2)	2007-02-01	Beach	Applicant
US7173923(B2)	2007-02-01	Beach	Applicant
US7174031(B2)	2007-02-01	Rhoads et al.	Applicant
US7177594(B2)	2007-02-01	Burr	Applicant
US7181521(B2)	2007-02-01	Knauerhase et al.	Applicant
US7185204(B2)	2007-02-01	Narayanaswami et al.	Applicant
US7194438(B2)	2007-03-01	Sovio et al.	Applicant
US7197326(B2)	2007-03-01	Acampora	Applicant
US7200132(B2)	2007-04-01	Twitchell, Jr.	Applicant
US7206820(B1)	2007-04-01	Rhoads et al.	Applicant
US7207480(B1)	2007-04-01	Geddes	Applicant
US7209468(B2)	2007-04-01	Twitchell, Jr.	Applicant
US7213742(B1)	2007-05-01	Birch et al.	Applicant
US7213743(B2)	2007-05-01	Carlson et al.	Applicant
US7221668(B2)	2007-05-01	Twitchell, Jr.	Applicant
US7233801(B2)	2007-06-01	Winn	Applicant
US7233960(B1)	2007-06-01	Boris et al.	Applicant
US7245602(B2)	2007-07-01	Skubic et al.	Applicant
US7246149(B2)	2007-07-01	Dowling	Applicant
US7249182(B1)	2007-07-01	Heinonen et al.	Applicant
US7254406(B2)	2007-08-01	Beros et al.	Applicant
US7280836(B2)	2007-10-01	Fuccello et al.	Applicant
US7280847(B2)	2007-10-01	Goldthwaite et al.	Applicant
US7289810(B2)	2007-10-01	Jagadeesan et al.	Applicant
US7302256(B1)	2007-11-01	O'Hara, Jr. et al.	Applicant
US7305245(B2)	2007-12-01	Alizadeh-Shabdiz et al.	Applicant
US7313120(B2)	2007-12-01	Ekberg et al.	Applicant
US7315944(B2)	2008-01-01	Dutta et al.	Applicant
US7322043(B2)	2008-01-01	Letsinger	Applicant
US7324824(B2)	2008-01-01	Smith et al.	Applicant
US7324957(B2)	2008-01-01	Boys	Applicant
US7327701(B2)	2008-02-01	Fong	Applicant
US7330112(B1)	2008-02-01	Emigh et al.	Applicant
US7339909(B2)	2008-03-01	Kotzin	Applicant
US7340438(B2)	2008-03-01	Nordman et al.	Applicant
US7340439(B2)	2008-03-01	Burger et al.	Applicant
US7342876(B2)	2008-03-01	Bellur et al.	Applicant
US7343564(B2)	2008-03-01	Othmer	Applicant
US7346341(B2)	2008-03-01	Costa-Requena et al.	Applicant
US7349871(B2)	2008-03-01	Labrou et al.	Applicant
US7359674(B2)	2008-04-01	Markki et al.	Applicant
US7363494(B2)	2008-04-01	Brainard et al.	Applicant
US7376433(B1)	2008-05-01	Hose	Applicant
US7379920(B2)	2008-05-01	Leung et al.	Applicant
US7386878(B2)	2008-06-01	Fernando et al.	Applicant
US7403120(B2)	2008-07-01	Duron et al.	Applicant
US7403762(B2)	2008-07-01	Morgan et al.	Applicant
US7412246(B2)	2008-08-01	Lewis et al.	Applicant
US7414988(B2)	2008-08-01	Jones et al.	Applicant
US7433649(B2)	2008-10-01	Toulis et al.	Applicant
US7433694(B2)	2008-10-01	Morgan et al.	Applicant
US7434723(B1)	2008-10-01	White et al.	Applicant
US7436831(B2)	2008-10-01	Miller et al.	Applicant
US7440781(B2)	2008-10-01	Beach et al.	Applicant
US7471954(B2)	2008-12-01	Brachet et al.	Applicant
US7492254(B2)	2009-02-01	Bandy et al.	Applicant
US7502933(B2)	2009-03-01	Jakobsson et al.	Applicant
US7509131(B2)	2009-03-01	Krumm et al.	Applicant
US7515914(B2)	2009-04-01	Herrod et al.	Applicant
US7522058(B1)	2009-04-01	Light et al.	Applicant
US7545784(B2)	2009-06-01	Mgrdechian et al.	Applicant
US7546141(B2)	2009-06-01	Leon et al.	Applicant
US7580699(B1)	2009-08-01	Shaw et al.	Applicant
US7590086(B2)	2009-09-01	Olkkonen et al.	Applicant
US7590246(B2)	2009-09-01	Calmels et al.	Applicant
US7616124(B2)	2009-11-01	Paessel et al.	Applicant
US7620026(B2)	2009-11-01	Anschutz et al.	Applicant
US7630986(B1)	2009-12-01	Herz et al.	Applicant
US7647024(B2)	2010-01-01	Wang et al.	Applicant
US7647055(B2)	2010-01-01	Gum et al.	Applicant
US7661132(B2)	2010-02-01	Ohkubo et al.	Applicant
US7702108(B2)	2010-04-01	Amon et al.	Applicant
US7711100(B2)	2010-05-01	Dennis	Applicant
US7711620(B2)	2010-05-01	Abifaker	Applicant
US7714712(B2)	2010-05-01	Emigh et al.	Applicant
US7716484(B1)	2010-05-01	Kaliski, Jr.	Applicant
US7729326(B2)	2010-06-01	Sekhar	Applicant
US7756467(B2)	2010-07-01	Bent et al.	Applicant
US7768415(B2)	2010-08-01	Blackadar	Applicant
US7773995(B2)	2010-08-01	Rappaport et al.	Applicant
US7774231(B2)	2010-08-01	Pond et al.	Applicant
US7775430(B2)	2010-08-01	Lin	Applicant
US7822000(B2)	2010-10-01	Sekhar	Applicant
US7826425(B2)	2010-11-01	Sekhar	Applicant
US7836512(B2)	2010-11-01	Mizuki et al.	Applicant
US7848765(B2)	2010-12-01	Phillips et al.	Applicant
US7876701(B2)	2011-01-01	Li et al.	Applicant
US7877082(B2)	2011-01-01	Eagle et al.	Applicant
US7886962(B2)	2011-02-01	Vawter	Applicant
US7904952(B2)	2011-03-01	Yeap et al.	Applicant
US7936736(B2)	2011-05-01	Proctor, Jr. et al.	Applicant
US7942337(B2)	2011-05-01	Jain	Applicant
US7952481(B2)	2011-05-01	Shoarinejad et al.	Applicant
US7962369(B2)	2011-06-01	Rosenberg	Applicant
US7963441(B2)	2011-06-01	Emmons et al.	Applicant
US7965983(B1)	2011-06-01	Swan et al.	Applicant
US7991644(B2)	2011-08-01	Bryant et al.	Applicant
US7991664(B1)	2011-08-01	Stone	Applicant
US8005465(B2)	2011-08-01	Salokannel et al.	Applicant
US8014755(B2)	2011-09-01	Sun et al.	Applicant
US8024272(B2)	2011-09-01	Doran et al.	Applicant
US8073795(B2)	2011-12-01	Honisch	Applicant
US8089405(B2)	2012-01-01	Piersol et al.	Applicant
US8090359(B2)	2012-01-01	Proctor, Jr. et al.	Applicant
US8112794(B2)	2012-02-01	Little et al.	Applicant
US8116749(B2)	2012-02-01	Proctor, Jr. et al.	Applicant
US8121917(B2)	2012-02-01	Insolia et al.	Applicant
US8160495(B2)	2012-04-01	Khedouri et al.	Applicant
US8185133(B2)	2012-05-01	Billmaier et al.	Applicant
US8204039(B2)	2012-06-01	Beach et al.	Applicant
US8205240(B2)	2012-06-01	Ansari et al.	Applicant
US8229458(B2)	2012-07-01	Busch	Applicant
US8233841(B2)	2012-07-01	Griffin et al.	Applicant
US8239286(B2)	2012-08-01	Davis	Applicant
US8254338(B2)	2012-08-01	Anschutz et al.	Applicant
US8275359(B2)	2012-09-01	Drennan	Applicant
US8295819(B1)	2012-10-01	Kaplan et al.	Applicant
US8321497(B1)	2012-11-01	Steiner et al.	Applicant
US8321913(B2)	2012-11-01	Turnbull et al.	Applicant
US8332521(B2)	2012-12-01	Chang et al.	Applicant
US8352323(B2)	2013-01-01	Fisher	Applicant
US8364171(B2)	2013-01-01	Busch	Applicant
US8369842(B2)	2013-02-01	Proctor, Jr. et al.	Applicant
US8374592(B2)	2013-02-01	Proctor, Jr. et al.	Applicant
US8385896(B2)	2013-02-01	Proctor, Jr. et al.	Applicant
US8385913(B2)	2013-02-01	Proctor, Jr. et al.	Applicant
US8411662(B1)	2013-04-01	Saund	Applicant
US8478300(B2)	2013-07-01	Kuehnel et al.	Applicant
US8543500(B2)	2013-09-01	Ogilvy	Applicant
US8559968(B2)	2013-10-01	Frank et al.	Applicant
US8576846(B2)	2013-11-01	Kumar et al.	Applicant
US8599814(B1)	2013-12-01	Vleugels et al.	Applicant
US8688570(B2)	2014-04-01	Jones et al.	Applicant
US8780945(B2)	2014-07-01	Gips et al.	Applicant
US8787575(B2)	2014-07-01	Laaksonen et al.	Applicant
US8825538(B2)	2014-09-01	Insolia et al.	Applicant
US8886118(B2)	2014-11-01	Reuss	Applicant
US8959187(B2)	2015-02-01	Li et al.	Applicant
US9038129(B2)	2015-05-01	Proctor, Jr. et al.	Applicant
US9137012(B2)	2015-09-01	Bailey et al.	Applicant
US9161164(B2)	2015-10-01	Proctor, Jr. et al.	Applicant
US9264991(B1)	2016-02-01	Vleugels et al.	Applicant
US9305119(B1)	2016-04-01	Partovi et al.	Applicant
US9373091(B1)	2016-06-01	Belser et al.	Applicant
US9525968(B2)	2016-12-01	Pounds	Applicant
US9646319(B2)	2017-05-01	Hammond et al.	Applicant
US9659285(B2)	2017-05-01	Hunter et al.	Applicant
US9734198(B2)	2017-08-01	Taylor	Applicant
US9805347(B2)	2017-10-01	Hurry	Applicant
US10133527(B2)	2018-11-01	Chang et al.	Applicant
US10140072(B2)	2018-11-01	Chang et al.	Applicant
US10375060(B1)	2019-08-01	Graves	Applicant
US10387087(B2)	2019-08-01	Chang et al.	Applicant
US10489096(B2)	2019-11-01	Chang et al.	Applicant
US10639552(B2)	2020-05-01	Vock et al.	Applicant
US10642576(B2)	2020-05-01	Chang et al.	Applicant
US10873906(B2)	2020-12-01	Vleugels et al.	Applicant
US11012934(B2)	2021-05-01	Vleugels et al.	Applicant
US11074615(B2)	2021-07-01	Proctor et al.	Applicant
US11122504(B1)	2021-09-01	Vleugels et al.	Applicant
US11252659(B2)	2022-02-01	Vleugels et al.	Applicant
US2001/0003191(A1)	2001-06-01	Kovacs et al.	Applicant
US2001/0036200(A1)	2001-11-01	Nelson et al.	Applicant
US2002/0032746(A1)	2002-03-01	Lazaridis	Applicant
US2002/0061009(A1)	2002-05-01	Sorensen	Applicant
US2002/0065720(A1)	2002-05-01	Carswell et al.	Applicant
US2002/0073027(A1)	2002-06-01	Hui et al.	Applicant
US2002/0077083(A1)	2002-06-01	Zellner et al.	Applicant
US2002/0077118(A1)	2002-06-01	Zellner et al.	Applicant
US2002/0101993(A1)	2002-08-01	Eskin	Applicant
US2002/0123965(A1)	2002-09-01	Phillips	Applicant
US2002/0128932(A1)	2002-09-01	Yung et al.	Applicant
US2002/0131445(A1)	2002-09-01	Skubic et al.	Applicant
US2002/0161666(A1)	2002-10-01	Fraki et al.	Applicant
US2002/0174364(A1)	2002-11-01	Nordman et al.	Applicant
US2002/0188565(A1)	2002-12-01	Nakamura et al.	Applicant
US2002/0188656(A1)	2002-12-01	Patton et al.	Applicant
US2003/0021250(A1)	2003-01-01	Willins et al.	Applicant
US2003/0028481(A1)	2003-02-01	Flitcroft et al.	Applicant
US2003/0045272(A1)	2003-03-01	Burr	Applicant
US2003/0053484(A1)	2003-03-01	Sorenson et al.	Applicant
US2003/0074259(A1)	2003-04-01	Slyman et al.	Applicant
US2003/0100328(A1)	2003-05-01	Klein et al.	Applicant
US2003/0134650(A1)	2003-07-01	Sundar et al.	Applicant
US2003/0149874(A1)	2003-08-01	Balfanz et al.	Applicant
US2003/0158959(A1)	2003-08-01	Jayapalan et al.	Applicant
US2003/0195808(A1)	2003-10-01	Brown et al.	Applicant
US2003/0200140(A1)	2003-10-01	Hars	Applicant
US2003/0200489(A1)	2003-10-01	Hars	Applicant
US2003/0220114(A1)	2003-11-01	Langensteiner et al.	Applicant
US2003/0220835(A1)	2003-11-01	Barnes	Applicant
US2003/0224756(A1)	2003-12-01	Kallio	Applicant
US2003/0224787(A1)	2003-12-01	Gandolfo	Examiner
US2004/0019564(A1)	2004-01-01	Goldthwaite et al.	Applicant
US2004/0023640(A1)	2004-02-01	Ballai	Applicant
US2004/0030601(A1)	2004-02-01	Pond et al.	Applicant
US2004/0076136(A1)	2004-04-01	Beach	Applicant
US2004/0082343(A1)	2004-04-01	Kim et al.	Applicant
US2004/0093268(A1)	2004-05-01	Ramchandani et al.	Applicant
US2004/0097243(A1)	2004-05-01	Zellner et al.	Applicant
US2004/0137886(A1)	2004-07-01	Ross et al.	Applicant
US2004/0167837(A1)	2004-08-01	Reel	Examiner
US2004/0186768(A1)	2004-09-01	Wakim et al.	Applicant
US2004/0190468(A1)	2004-09-01	Saijonmaa	Applicant
US2004/0203895(A1)	2004-10-01	Balasuriya	Applicant
US2004/0205198(A1)	2004-10-01	Zellner et al.	Applicant
US2004/0208151(A1)	2004-10-01	Haverinen et al.	Applicant
US2004/0228319(A1)	2004-11-01	Melville et al.	Applicant
US2004/0243519(A1)	2004-12-01	Perttila et al.	Applicant
US2004/0245332(A1)	2004-12-01	Silverbrook et al.	Applicant
US2004/0248569(A1)	2004-12-01	Kondou et al.	Applicant
US2004/0260608(A1)	2004-12-01	Lewis et al.	Applicant
US2004/0264404(A1)	2004-12-01	Zegelin	Applicant
US2004/0264466(A1)	2004-12-01	Huang	Applicant
US2005/0038876(A1)	2005-02-01	Chaudhuri	Applicant
US2005/0047385(A1)	2005-03-01	Otsuka	Applicant
US2005/0054350(A1)	2005-03-01	Zegelin	Applicant
US2005/0068928(A1)	2005-03-01	Smith et al.	Applicant
US2005/0086211(A1)	2005-04-01	Mayer	Applicant
US2005/0096031(A1)	2005-05-01	Sugaya et al.	Applicant
US2005/0099291(A1)	2005-05-01	Landau	Applicant
US2005/0113090(A1)	2005-05-01	Sharony	Applicant
US2005/0114654(A1)	2005-05-01	Brackett et al.	Applicant
US2005/0124359(A1)	2005-06-01	Willins et al.	Applicant
US2005/0130634(A1)	2005-06-01	Godfrey	Applicant
US2005/0131837(A1)	2005-06-01	Sanctis et al.	Applicant
US2005/0136845(A1)	2005-06-01	Masuoka et al.	Applicant
US2005/0136891(A1)	2005-06-01	Wang et al.	Applicant
US2005/0156026(A1)	2005-07-01	Ghosh et al.	Applicant
US2005/0164717(A1)	2005-07-01	Leping	Applicant
US2005/0165667(A1)	2005-07-01	Cox	Applicant
US2005/0174975(A1)	2005-08-01	Mgrdechian	Applicant
US2005/0180367(A1)	2005-08-01	Dooley et al.	Applicant
US2005/0185615(A1)	2005-08-01	Zegelin	Applicant
US2005/0187873(A1)	2005-08-01	Labrou et al.	Applicant
US2005/0187959(A1)	2005-08-01	Jung et al.	Applicant
US2005/0188062(A1)	2005-08-01	Li et al.	Applicant
US2005/0204309(A1)	2005-09-01	Szeto	Applicant
US2005/0213553(A1)	2005-09-01	Wang	Applicant
US2005/0243737(A1)	2005-11-01	Dooley et al.	Applicant
US2005/0243781(A1)	2005-11-01	Vesuna et al.	Applicant
US2005/0250552(A1)	2005-11-01	Eagle et al.	Applicant
US2005/0266868(A1)	2005-12-01	Fuccello	Applicant
US2005/0273440(A1)	2005-12-01	Ching	Applicant
US2006/0003785(A1)	2006-01-01	Zatezalo	Applicant
US2006/0022038(A1)	2006-02-01	Hewlin et al.	Applicant
US2006/0023711(A1)	2006-02-01	Perret	Applicant
US2006/0029024(A1)	2006-02-01	Zeng et al.	Applicant
US2006/0030335(A1)	2006-02-01	Zellner et al.	Applicant
US2006/0032901(A1)	2006-02-01	Sugiyama et al.	Applicant
US2006/0045042(A1)	2006-03-01	Sethi et al.	Applicant
US2006/0046709(A1)	2006-03-01	Krumm et al.	Applicant
US2006/0047835(A1)	2006-03-01	Greaux	Applicant
US2006/0050728(A1)	2006-03-01	Sung et al.	Applicant
US2006/0069922(A1)	2006-03-01	Jelinek et al.	Applicant
US2006/0079284(A1)	2006-04-01	Lu et al.	Applicant
US2006/0085419(A1)	2006-04-01	Rosen	Applicant
US2006/0089134(A1)	2006-04-01	Moton et al.	Applicant
US2006/0089876(A1)	2006-04-01	Boys	Applicant
US2006/0094447(A1)	2006-05-01	Zellner	Applicant
US2006/0095348(A1)	2006-05-01	Jones et al.	Applicant
US2006/0095349(A1)	2006-05-01	Morgan et al.	Applicant
US2006/0099966(A1)	2006-05-01	Moton et al.	Applicant
US2006/0104200(A1)	2006-05-01	Park	Applicant
US2006/0104243(A1)	2006-05-01	Park	Applicant
US2006/0106850(A1)	2006-05-01	Morgan et al.	Applicant
US2006/0111045(A1)	2006-05-01	Orlassino et al.	Applicant
US2006/0114104(A1)	2006-06-01	Scaramozzino	Applicant
US2006/0116160(A1)	2006-06-01	Fuccello	Applicant
US2006/0125631(A1)	2006-06-01	Sharony	Applicant
US2006/0141932(A1)	2006-06-01	Lawrence et al.	Applicant
US2006/0153085(A1)	2006-07-01	Willins et al.	Applicant
US2006/0165100(A1)	2006-07-01	Huang et al.	Applicant
US2006/0171341(A1)	2006-08-01	Wang et al.	Applicant
US2006/0193258(A1)	2006-08-01	Ballai	Applicant
US2006/0200843(A1)	2006-09-01	Morgan et al.	Applicant
US2006/0217131(A1)	2006-09-01	Alizadeh-Shabdiz et al.	Applicant
US2006/0229058(A1)	2006-10-01	Rosenberg	Applicant
US2006/0234631(A1)	2006-10-01	Dieguez	Applicant
US2006/0240840(A1)	2006-10-01	Morgan et al.	Applicant
US2006/0245373(A1)	2006-11-01	Bajic	Applicant
US2006/0245393(A1)	2006-11-01	Bajic	Applicant
US2006/0245404(A1)	2006-11-01	Bajic	Applicant
US2006/0264212(A1)	2006-11-01	Sekhar	Applicant
US2006/0268746(A1)	2006-11-01	Wijting et al.	Applicant
US2006/0268765(A1)	2006-11-01	Bajic et al.	Applicant
US2006/0268834(A1)	2006-11-01	Bajic	Applicant
US2006/0270412(A1)	2006-11-01	Willins et al.	Applicant
US2006/0282738(A1)	2006-12-01	Sohn et al.	Applicant
US2006/0287813(A1)	2006-12-01	Quigley	Applicant
US2007/0001904(A1)	2007-01-01	Mendelson	Applicant
US2007/0002802(A1)	2007-01-01	Sekhar	Applicant
US2007/0002833(A1)	2007-01-01	Bajic	Applicant
US2007/0004427(A1)	2007-01-01	Morgan et al.	Applicant
US2007/0004428(A1)	2007-01-01	Morgan et al.	Applicant
US2007/0010278(A1)	2007-01-01	D'Agostino et al.	Applicant
US2007/0015549(A1)	2007-01-01	Hernandez et al.	Applicant
US2007/0025287(A1)	2007-02-01	Goren et al.	Applicant
US2007/0026818(A1)	2007-02-01	Willins et al.	Applicant
US2007/0030824(A1)	2007-02-01	Ribaudo et al.	Applicant
US2007/0032225(A1)	2007-02-01	Konicek et al.	Applicant
US2007/0043828(A1)	2007-02-01	Famolari et al.	Applicant
US2007/0049297(A1)	2007-03-01	Gopalan et al.	Applicant
US2007/0050258(A1)	2007-03-01	Dohse	Applicant
US2007/0060105(A1)	2007-03-01	Batta	Applicant
US2007/0060117(A1)	2007-03-01	Fishman et al.	Applicant
US2007/0060130(A1)	2007-03-01	Gogic et al.	Applicant
US2007/0061487(A1)	2007-03-01	Moore et al.	Applicant
US2007/0078851(A1)	2007-04-01	Grell et al.	Applicant
US2007/0081503(A1)	2007-04-01	Mower	Applicant
US2007/0091859(A1)	2007-04-01	Sethi et al.	Applicant
US2007/0094084(A1)	2007-04-01	Rau et al.	Applicant
US2007/0096909(A1)	2007-05-01	Lally	Applicant
US2007/0100651(A1)	2007-05-01	Ramer et al.	Applicant
US2007/0106612(A1)	2007-05-01	O'Brien et al.	Applicant
US2007/0117576(A1)	2007-05-01	Huston	Applicant
US2007/0118748(A1)	2007-05-01	Edney	Applicant
US2007/0121534(A1)	2007-05-01	James et al.	Applicant
US2007/0121550(A1)	2007-05-01	Wada	Applicant
US2007/0124211(A1)	2007-05-01	Smith	Applicant
US2007/0133453(A1)	2007-06-01	Sethi et al.	Applicant
US2007/0143348(A1)	2007-06-01	Rosenberg	Applicant
US2007/0161382(A1)	2007-07-01	Melinger et al.	Applicant
US2007/0173248(A1)	2007-07-01	Sekhar	Applicant
US2007/0174472(A1)	2007-07-01	Kulakowski	Applicant
US2007/0178886(A1)	2007-08-01	Wang et al.	Applicant
US2007/0178907(A1)	2007-08-01	Gopalan et al.	Applicant
US2007/0179792(A1)	2007-08-01	Kramer	Applicant
US2007/0187491(A1)	2007-08-01	Godwin et al.	Applicant
US2007/0190494(A1)	2007-08-01	Rosenberg	Applicant
US2007/0201417(A1)	2007-08-01	Malik et al.	Applicant
US2007/0204158(A1)	2007-08-01	Hatashita et al.	Applicant
US2007/0211727(A1)	2007-09-01	Sethi et al.	Applicant
US2007/0219875(A1)	2007-09-01	Toulotte	Applicant
US2007/0230441(A1)	2007-10-01	Sethi et al.	Applicant
US2007/0233367(A1)	2007-10-01	Chen et al.	Applicant
US2007/0237321(A1)	2007-10-01	Bloebaum et al.	Applicant
US2007/0242643(A1)	2007-10-01	Chandra et al.	Applicant
US2007/0242765(A1)	2007-10-01	Parizhisky et al.	Applicant
US2007/0244633(A1)	2007-10-01	Phillips et al.	Applicant
US2007/0244811(A1)	2007-10-01	Tumminaro	Applicant
US2007/0255653(A1)	2007-11-01	Tumminaro et al.	Applicant
US2007/0264968(A1)	2007-11-01	Frank et al.	Applicant
US2007/0264991(A1)	2007-11-01	Jones et al.	Applicant
US2007/0270099(A1)	2007-11-01	Le Gars	Applicant
US2007/0280269(A1)	2007-12-01	Rosenberg	Applicant
US2007/0281634(A1)	2007-12-01	Rao et al.	Applicant
US2007/0286111(A1)	2007-12-01	Corson et al.	Applicant
US2008/0002641(A1)	2008-01-01	Hong et al.	Applicant
US2008/0008117(A1)	2008-01-01	Alizadeh-Shabdiz	Applicant
US2008/0008118(A1)	2008-01-01	Alizadeh-Shabdiz	Applicant
US2008/0008119(A1)	2008-01-01	Alizadeh-Shabdiz	Applicant
US2008/0008120(A1)	2008-01-01	Alizadeh-Shabdiz	Applicant
US2008/0008121(A1)	2008-01-01	Alizadeh-Shabdiz	Applicant
US2008/0009307(A1)	2008-01-01	Sekhar et al.	Applicant
US2008/0010190(A1)	2008-01-01	Rackley III et al.	Applicant
US2008/0025282(A1)	2008-01-01	Hong	Applicant
US2008/0036653(A1)	2008-02-01	Huston	Applicant
US2008/0037487(A1)	2008-02-01	Li et al.	Applicant
US2008/0039020(A1)	2008-02-01	Eskin	Applicant
US2008/0045181(A1)	2008-02-01	Suzuki	Applicant
US2008/0045236(A1)	2008-02-01	Nahon et al.	Applicant
US2008/0051033(A1)	2008-02-01	Hymes	Applicant
US2008/0051059(A1)	2008-02-01	Fisher	Applicant
US2008/0052109(A1)	2008-02-01	Boys	Applicant
US2008/0056215(A1)	2008-03-01	Kopikare et al.	Applicant
US2008/0070593(A1)	2008-03-01	Altman et al.	Applicant
US2008/0071874(A1)	2008-03-01	Roodman et al.	Applicant
US2008/0080397(A1)	2008-04-01	Niranjan et al.	Applicant
US2008/0089519(A1)	2008-04-01	Ekberg	Applicant
US2008/0097851(A1)	2008-04-01	Bemmel et al.	Applicant
US2008/0097879(A1)	2008-04-01	Sadowski et al.	Applicant
US2008/0099552(A1)	2008-05-01	Grillion	Applicant
US2008/0102856(A1)	2008-05-01	Fortescue et al.	Applicant
US2008/0104227(A1)	2008-05-01	Birnie et al.	Applicant
US2008/0108308(A1)	2008-05-01	Ullah	Applicant
US2008/0109302(A1)	2008-05-01	Salokannel et al.	Applicant
US2008/0109741(A1)	2008-05-01	Messing et al.	Applicant
US2008/0109843(A1)	2008-05-01	Ullah	Applicant
US2008/0114647(A1)	2008-05-01	Singer et al.	Applicant
US2008/0114699(A1)	2008-05-01	Yuan et al.	Applicant
US2008/0114834(A1)	2008-05-01	Miyazaki	Applicant
US2008/0119136(A1)	2008-05-01	Khazi	Applicant
US2008/0132170(A1)	2008-06-01	Alizadeh-Shabdiz et al.	Applicant
US2008/0132223(A1)	2008-06-01	Lin et al.	Applicant
US2008/0132252(A1)	2008-06-01	Altman et al.	Applicant
US2008/0133336(A1)	2008-06-01	Altman et al.	Applicant
US2008/0133403(A1)	2008-06-01	Hamzeh	Applicant
US2008/0134052(A1)	2008-06-01	Davis et al.	Applicant
US2008/0136621(A1)	2008-06-01	Malik et al.	Applicant
US2008/0136845(A1)	2008-06-01	Nakanishi	Applicant
US2008/0139114(A1)	2008-06-01	Ranganathan	Applicant
US2008/0139217(A1)	2008-06-01	Alizadeh-Shabdiz et al.	Applicant
US2008/0140714(A1)	2008-06-01	Rhoads et al.	Applicant
US2008/0167961(A1)	2008-07-01	Wentker et al.	Applicant
US2008/0167988(A1)	2008-07-01	Sun et al.	Applicant
US2008/0176583(A1)	2008-07-01	Brachet et al.	Applicant
US2008/0177668(A1)	2008-07-01	Delean	Applicant
US2008/0181154(A1)	2008-07-01	Sherman	Applicant
US2008/0182591(A1)	2008-07-01	Krikorian	Applicant
US2008/0182592(A1)	2008-07-01	Cha et al.	Applicant
US2008/0188261(A1)	2008-08-01	Arnone	Applicant
US2008/0189394(A1)	2008-08-01	Ross et al.	Applicant
US2008/0195621(A1)	2008-08-01	Tedesco et al.	Applicant
US2008/0205340(A1)	2008-08-01	Meylan et al.	Applicant
US2008/0208762(A1)	2008-08-01	Arthur et al.	Applicant
US2008/0214116(A1)	2008-09-01	Leung et al.	Applicant
US2008/0214166(A1)	2008-09-01	Ramer et al.	Applicant
US2008/0220746(A1)	2008-09-01	Ekberg	Applicant
US2008/0222711(A1)	2008-09-01	Michaelis	Applicant
US2008/0248815(A1)	2008-10-01	Busch	Applicant
US2008/0249928(A1)	2008-10-01	Hill et al.	Applicant
US2008/0255947(A1)	2008-10-01	Friedman	Applicant
US2008/0259836(A1)	2008-10-01	Beach	Applicant
US2008/0261526(A1)	2008-10-01	Suresh	Applicant
US2008/0261564(A1)	2008-10-01	Logan	Applicant
US2008/0262928(A1)	2008-10-01	Michaelis	Applicant
US2008/0288408(A1)	2008-11-01	Jacobsen	Applicant
US2008/0301102(A1)	2008-12-01	Liang	Applicant
US2008/0305738(A1)	2008-12-01	Khedouri et al.	Applicant
US2008/0306825(A1)	2008-12-01	Schick et al.	Applicant
US2008/0313079(A1)	2008-12-01	Van et al.	Applicant
US2008/0313082(A1)	2008-12-01	Van et al.	Applicant
US2009/0016248(A1)	2009-01-01	Li et al.	Applicant
US2009/0016250(A1)	2009-01-01	Li et al.	Applicant
US2009/0016255(A1)	2009-01-01	Park	Applicant
US2009/0016315(A1)	2009-01-01	Laroia et al.	Applicant
US2009/0016353(A1)	2009-01-01	Li et al.	Applicant
US2009/0016524(A1)	2009-01-01	Park et al.	Applicant
US2009/0019168(A1)	2009-01-01	Wu et al.	Applicant
US2009/0022096(A1)	2009-01-01	Walley et al.	Applicant
US2009/0028082(A1)	2009-01-01	Wynn et al.	Applicant
US2009/0029691(A1)	2009-01-01	Shen	Applicant
US2009/0037286(A1)	2009-02-01	Foster	Applicant
US2009/0059878(A1)	2009-03-01	Tamura	Applicant
US2009/0061901(A1)	2009-03-01	Arrasvuori et al.	Applicant
US2009/0063624(A1)	2009-03-01	Nordstrom et al.	Applicant
US2009/0085806(A1)	2009-04-01	Piersol et al.	Applicant
US2009/0099961(A1)	2009-04-01	Ogilvy	Applicant
US2009/0143104(A1)	2009-06-01	Loh et al.	Applicant
US2009/0149197(A1)	2009-06-01	Morgan et al.	Applicant
US2009/0170559(A1)	2009-07-01	Phillips	Applicant
US2009/0177530(A1)	2009-07-01	King et al.	Applicant
US2009/0197681(A1)	2009-08-01	Krishnamoorthy	Examiner
US2009/0219132(A1)	2009-09-01	Maytal et al.	Applicant
US2009/0234728(A1)	2009-09-01	Willuns et al.	Applicant
US2009/0239467(A1)	2009-09-01	Gulin et al.	Applicant
US2009/0245142(A1)	2009-10-01	Want	Applicant
US2009/0270120(A1)	2009-10-01	Park	Applicant
US2009/0271211(A1)	2009-10-01	Hammad	Applicant
US2009/0281904(A1)	2009-11-01	Pharris	Applicant
US2009/0282130(A1)	2009-11-01	Antoniou et al.	Applicant
US2009/0285119(A1)	2009-11-01	Horn et al.	Applicant
US2009/0287827(A1)	2009-11-01	Horn et al.	Applicant
US2009/0288012(A1)	2009-11-01	Hertel et al.	Applicant
US2009/0291909(A1)	2009-11-01	Henderson et al.	Applicant
US2009/0298514(A1)	2009-12-01	Ullah	Applicant
US2009/0303250(A1)	2009-12-01	Phillips	Applicant
US2009/0303926(A1)	2009-12-01	Den et al.	Applicant
US2009/0307132(A1)	2009-12-01	Phillips	Applicant
US2009/0307133(A1)	2009-12-01	Holloway et al.	Applicant
US2009/0310517(A1)	2009-12-01	Narayanan et al.	Applicant
US2009/0311963(A1)	2009-12-01	Haverty	Applicant
US2009/0313105(A1)	2009-12-01	Magnusson	Applicant
US2009/0323647(A1)	2009-12-01	Park et al.	Applicant
US2009/0323648(A1)	2009-12-01	Park et al.	Applicant
US2009/0325601(A1)	2009-12-01	Park et al.	Applicant
US2010/0020746(A1)	2010-01-01	Zaks	Applicant
US2010/0030638(A1)	2010-02-01	Davis, III et al.	Applicant
US2010/0030651(A1)	2010-02-01	Matotek et al.	Applicant
US2010/0041402(A1)	2010-02-01	Gallagher et al.	Applicant
US2010/0049615(A1)	2010-02-01	Rose et al.	Applicant
US2010/0051685(A1)	2010-03-01	Royyuru et al.	Applicant
US2010/0054138(A1)	2010-03-01	Gips et al.	Applicant
US2010/0062758(A1)	2010-03-01	Proctor, Jr. et al.	Applicant
US2010/0063867(A1)	2010-03-01	Proctor, Jr. et al.	Applicant
US2010/0096450(A1)	2010-04-01	Silverbrook et al.	Applicant
US2010/0113001(A1)	2010-05-01	Tenbrook	Applicant
US2010/0124196(A1)	2010-05-01	Bonar et al.	Applicant
US2010/0138481(A1)	2010-06-01	Behrens	Applicant
US2010/0141437(A1)	2010-06-01	Karam et al.	Applicant
US2010/0201536(A1)	2010-08-01	Robertson et al.	Applicant
US2010/0250673(A1)	2010-09-01	Laroia et al.	Applicant
US2010/0274859(A1)	2010-10-01	Bucuk	Applicant
US2010/0284447(A1)	2010-11-01	Gore et al.	Applicant
US2011/0039592(A1)	2011-02-01	Haddad et al.	Applicant
US2011/0119733(A1)	2011-05-01	Proctor, Jr. et al.	Applicant
US2012/0066043(A1)	2012-03-01	Carmichael et al.	Applicant
US2012/0066199(A1)	2012-03-01	Ramer et al.	Applicant
US2013/0217332(A1)	2013-08-01	Altman et al.	Applicant
US2015/0200811(A1)	2015-07-01	Kasslin et al.	Applicant
US2015/0249637(A1)	2015-09-01	Lawson-Brown et al.	Applicant
US2015/0257104(A1)	2015-09-01	Choi et al.	Applicant
US2015/0281939(A1)	2015-10-01	Li et al.	Applicant
US2015/0296347(A1)	2015-10-01	Roth	Applicant
US2016/0025837(A1)	2016-01-01	Hillier	Applicant
US2016/0093184(A1)	2016-03-01	Locke et al.	Applicant
US2017/0011425(A1)	2017-01-01	Proctor, Jr. et al.	Applicant
US2017/0131994(A1)	2017-05-01	Middleton et al.	Applicant
US2017/0289779(A1)	2017-10-01	Postrel	Applicant
US2019/0236578(A1)	2019-08-01	Hultberg et al.	Applicant
US2019/0250239(A1)	2019-08-01	Samuelsson	Applicant
CA2235002(A1)	1998-12-01		Applicant
CA2218268(C)	2007-01-01		Applicant
CA2564287(C)	2010-08-01		Applicant
CA2506121(C)	2010-09-01		Applicant
CA2766184(C)	2016-04-01		Applicant
CA2766024(C)	2017-03-01		Applicant
CA2688189(C)	2018-08-01		Applicant
CN1759620(A)	2006-04-01		Applicant
CN101036061(A)	2007-09-01		Applicant
CN101233722(A)	2008-07-01		Applicant
EP156856(B1)	1989-04-01		Applicant
EP837406(A2)	1998-04-01		Applicant
EP1296155(B1)	2006-11-01		Applicant
EP1207654(B1)	2008-01-01		Applicant
EP1098477(B1)	2009-12-01		Applicant
EP2332126(A1)	2011-06-01		Applicant
EP1908235(B1)	2018-01-01		Applicant
FR2752347(B1)	2001-02-01		Applicant
FR2798749(A1)	2001-03-01		Applicant
JP2005012973	2005-01-01		Applicant
SE702686(L)	2009-06-01		Applicant
SG134837	2007-10-01		Applicant
WO1985001373	1985-03-01		Applicant
WO158098(A2)	2001-08-01		Applicant
WO1/73575(A1)	2001-10-01		Applicant
WO2006028640(A2)	2006-03-01		Applicant
WO2006103387	2006-10-01		Applicant
WO2007047181(A2)	2007-04-01		Applicant
WO2007/081356(A2)	2007-07-01		Applicant
WO2007/084973(A2)	2007-07-01		Applicant
WO2008069446(A1)	2008-06-01		Applicant
WO2008076827	2008-06-01		Applicant
WO2008132241(A2)	2008-11-01		Applicant
WO2009050322(A1)	2009-04-01		Applicant
WO2009063272(A1)	2009-05-01		Applicant
WO2010028182(A1)	2010-03-01		Applicant

Non-Patent Literature (454)

Samsung's Answer and Defenses to Secure Communication Technologies LLC's Original Complaint for Patent Infringement; Secure Communication Technologies LLC v. Samsung Electronics Co., Ltd., et al.; Case No. 2:24-cv-484 (E.D. Tex., Nov. 19, 2024) (24 pages).Applicant
Mandate dated Oct. 27, 2023, United States Court of Appeals, Federal Circuit, Target Corporation v. Proxicom Wireless LLC.Applicant
Judgment dated Sep. 20, 2023, Document 42, United States Court of Appeals, Federal Circuit, Target Corporation v. Proxicom Wireless LLC.Applicant
Judgment dated Sep. 20, 2023, Document 41, United States Court of Appeals, Federal Circuit, Target Corporation v. Proxicom Wireless LLC.Applicant
Order dated Dec. 4, 2020, Case No. IPR2020-00978, United States Patent trial and Appeal Board, Target Corporation v. Proxicom Wireless LLC.Applicant
Duflot, et al., “A Formal Analysis of Bluetooth Device Discovery”, School of Computer Science, University of Birmingham, 1-16.Applicant
Feldmann, S., et al., “An indoor Bluetooth-based positioning system: concept, Implementation and experimental evaluation,” Institute of Communications Engineering.Applicant
Fernandez, T., et al., “Bluetooth Sensor Network Positioning System with Dynamic Calibration,” Dept. of Electronics and Systems, University of Coruna, Spain, IEEE 2007, pp. 45-49.Applicant
File History for U.S. Pat. No. 8,369,842.Applicant
File History for U.S. Pat. No. 8,370,955.Applicant
File History for U.S. Pat. No. 8,374,592.Applicant
File History for U.S. Pat. No. 8,385,896.Applicant
File History for U.S. Pat. No. 8,385,913.Applicant
File History for U.S. Pat. No. 8,849,698.Applicant
File History for U.S. Pat. No. 9,038,129.Applicant
File History for U.S. Pat. No. 9, 161, 164.Applicant
File History for U.S. Pat. No. 8,090,359.Applicant
File History of U.S. Appl. No. 60/814,254, filed Jun. 16, 2006, 44 pages.Applicant
File History of U.S. Pat. No. 7,936,736.Applicant
Final Office Action received for U.S. Appl. No. 17/366,826, dated Dec. 13, 2021, 42 pages.Applicant
Final Office Action; U.S. Appl. No. 12/364,819; dated Jun. 28, 2011.Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 30, 2021, IPR2020-00934, U.S. Pat. No. 8,385,896 B2, Target Corporation v. Proxicom Wireless, L.L.C. (55 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 30, 2021, IPR2020-00977, U.S. Pat. No. 8,369,842 B2, Target Corporation v. Proxicom Wireless, L.L.C. (45 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 30, 2021, IPR2020-00979, U.S. Pat. No. 9,161,142 B2, Target Corporation v. Proxicom Wireless, L.L.C. (51 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 30, 2021, IPR2020-00980, U.S. Pat. No. 8,385,913 B2, Target Corporation v. Proxicom Wireless, L.L.C. (47 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 8, 2021, IPR2020-00904, U.S. Pat. No. 7,936,736 B2, Target Corporation v. Proxicom Wireless, L.L.C. (48 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 8, 2021, IPR2020-00931, U.S. Pat. No. 8,090,359 B2, Target Corporation v. Proxicom Wireless, L.L.C. (51 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 8, 2021, IPR2020-00932, U.S. Pat. No. 8,090,359 B2, Target Corporation v. Proxicom Wireless, L.L.C. (40 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 8, 2021, IPR2020-00933, U.S. Pat. No. 8,374,592 B2, Target Corporation v. Proxicom Wireless, L.L.C. (38 pages).Applicant
Final Written Decision per 35 U.S.C. 138 dated Nov. 8, 2021, IPR2020-00903, U.S. Pat. No. 9,038,129 B2, Target Corporation v. Proxicom Wireless, L.L.C. (41 pages).Applicant
Gao et al., The Advanced Health and Disaster Aid Network: A Light-Weight Wireless Medical System for Triage, ArticlE in IEEE Transactions on Biomedical Circuits and Systems Oct. 2007, 15 pages.Applicant
Gao, J., et al., “P2P Paid: A Peer-to-Peer Wireless Payment System,” Proceedings of the 2005 Second IEEE International Workshop on Mobile Commerce and Services (WMCS05), 10 pp. (2005).Applicant
Giaglis, G., et al., “On the Potential Use of Mobile Positioning Technologies in Indoor Environments,” 15th Bled eCommerce Conference eReality: Constructing the eEconomy, Bled, Slovenia, Jun. 17-19, 2002, 18 pp.Applicant
Golle et al. “Universal re-encryption for mixnets”. In: Topics in Cryptology—CT-RSA 2004. Springer, 2004, pp. 163-178.Applicant
Hallberg, J., et al., “Positioning with Bluetooth,” Lulea University of Technology, Dept. of Computer Science and Electrica Engineering, IEEE 2003.Applicant
Hari Balakrishnan, et al. “Cricket Location System” “Cricket Presentation”, 31 pages (2005).Applicant
Harrison, B. et al., “Bridging Physical and Virtual Worlds with Tagged Documents, Objects and Locations,” Xerox PARC, CHI 99 May 1-20, 1999, pp. 29-30.Applicant
Heeger, David, “Signal Detection Theory Handout,” University of Stanford, 1998, www.psych.stanford.edu/.about.lera/psych115s/notes/signal/, 7 pages.Applicant
Hochmair, H., “1 PDA-Assisted Indoor-Navigation with Imprecise Positioning: Results of a Desktop Usability Study,” Dept. of Geography, St. Cloud State University.Applicant
Honkanen et al., “Low End Extension for Bluetooth,” Radio and Wireless Conference, 2004 IEEE, pp. 199-202.Applicant
http://www.ietf.org/rfc/rfc4793.txt; The EAP Protected One-Time Password Protocol (EAP-POTP); 77 pages, Feb. 2007; retrieved from Internet Mar. 21, 2012.Applicant
http://www.smartcardalliance.org/resources/lib/Proximity.sub.--Mobile.sub.- --payments.sub.--200709.pdf; Smart Card Alliance 39 pages, Sep. 2007; retrieved from Internet Mar. 21, 2012.Applicant
Hunn, Nick, Ezurio An Introduction to Wibree Nov. 2006, 7 pages.Applicant
Huomo et al., PowerPoint Presentation Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs), Submission Tille: [Nokia MAC Proposal for IEEE802.15 TG4], Jul. 2001, 50 pages.Applicant
IEEE Standard for Information Technology Part 11: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications, IEEE SID 802.11, (2007) 1232 pages.Applicant
IEEE Standard for Information Technology Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (LR-WPANs), IEEE Std 802.15.4, Oct. 1, 2003, 679 pages.Applicant
Iftode, L., et al., “Smart Phone: An Embedded System for Universal Interactions,” Rutgers University Dept. of computer Sciences, pp. 1-12 (2004).Applicant
International Search Report and Written Opinion dated May 11, 2018 for Related PCT/US18/12277.Applicant
Ismail Guvenc, et al., Enhancements to RSS Based Indoor Tracking Systems Using Kalman Filters, Global Signal Processing Expo (2003).Applicant
Jakobsson et al., “Security Weaknesses in Bluetooth,” D. Naccache (Ed.): CT-RSA 2001, LNCS 2020, 2001. c Springer-Verlag Berlin Heidelberg 2001, 16 pages.Applicant
James Bickers, A Giant of a Self-Service Rollout, Kiosk Marketplace (Nov. 28, 2005), https://www.kioskmarketplace.com/articles/a-giant-of-a-self-service-rollout-3/.Applicant
Exhibit B7 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. 2005/0250552 (“Eagle”) (29 pages).Applicant
Exhibit B8 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Pat. No. 7,545,784 (“Mgrdechian”) (41 pages).Applicant
Exhibit B9 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2010/0138481 (“Behrens”) (63 pages).Applicant
Exhibit B10 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent No. 8,886,118 (“Reuss”) (34 pages).Applicant
Exhibit B11 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2009/0029691 (“Shen”) (36 pages).Applicant
Exhibit B12 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Pat. No. 8,239,286 (“Davis”) (33 pages).Applicant
Exhibit B13 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. 2009/0245142 (“Want”) (53 pages).Applicant
Exhibit B14 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Pat. No. 10,375,060 (“Graves”) (38 pages).Applicant
Exhibit B15 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on Japanese Patent App. 2005-012973 (“Watanabe”) (38 pages).Applicant
Exhibit B16 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Pat. No. 6,928,263 (“Blake”) (30 pages).Applicant
Exhibit B17 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2009/0298514 (“Ullah”) (95 pages).Applicant
Exhibit B18 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. 2005/0130634 (“Godfrey”) (56 pages).Applicant
Exhibit B19 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Pat. No. 9,525,968 (“Pounds”) (31 pages).Applicant
Exhibit B20 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2006/0023711 (“Perret”) (45 pages).Applicant
Exhibit B21 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2008/0045181 (“Suzuki”) (26 pages).Applicant
Exhibit B22 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on International Publication No. WO 2008/076827 (“Krikorian”) (25 pages).Applicant
Exhibit B23 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Pat. No. 7,000,001 (“Lazaridis”) (29 pages).Applicant
Exhibit B24 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2007/0030824 (“Ribaudo”) (34 pages).Applicant
Exhibit B25 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “344 Patent”) Invalidity Chart Based on Samsung Products that ran the Google Fast Pair Service (“Fast Pair”) prior to Mar. 13, 2020 (“Pre-2020 Samsung Products With Fast Pair”) (98 pages).Applicant
Exhibit C1 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 8,090,359 (“Proctor '359”) (65 pages).Applicant
Exhibit C2 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. 9,161,164 (“Proctor '164”) (63 pages).Applicant
Exhibit C3 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. 2017/0289779 (“Postrel”) (56 pages).Applicant
Exhibit C4 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on International Publication No. 2006/103387 (“Turnbull”) (32 pages).Applicant
Exhibit C5 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2006/0287813 (“Quigley”) (31 pages).Applicant
Exhibit C6 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. 2010/0113001 (“Tenbrook”) (46 pages).Applicant
Exhibit C7 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. 2005/0250552 (“Eagle”) (28 pages).Applicant
Exhibit C8 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 7,545,784 (“Mgrdechian”) (38 pages).Applicant
Exhibit C9 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2010/0138481 (“Behrens”) (66 pages).Applicant
Exhibit C10 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 8,886,118 (“Reuss”) (30 pages).Applicant
Exhibit C11 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2009/0029691 (“Shen”) (34 pages).Applicant
Exhibit C12 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 8,239,286 (“Davis”) (32 pages).Applicant
Exhibit C13 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. 2009/0245142 (“Want”) (53 pages).Applicant
Exhibit C14 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 10,375,060 (“Graves”) (37 pages).Applicant
Exhibit C15 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on Japanese Patent App. 2005-012973 (“Watanabe”) (33 pages).Applicant
Exhibit C16 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 6,928,263 (“Blake”) (29 pages).Applicant
Exhibit C17 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2009/0298514 (“Ullah”) (58 pages).Applicant
Exhibit C18 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. 2005/0130634 (“Godfrey”) (58 pages).Applicant
Exhibit C19 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 9,525,968 (“Pounds”) (33 pages).Applicant
Exhibit C20 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2006/0023711 (“Perret”) (40 pages).Applicant
Exhibit C21 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2008/0045181 (“Suzuki”) (22 pages).Applicant
Exhibit C22 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on International Publication No. WO 2008/076827 (“Krikorian”) (23 pages).Applicant
Exhibit C23 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Pat. No. 7,000,001 (“Lazaridis”) (25 pages).Applicant
Exhibit C24 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2007/0030824 (“Ribaudo”) (30 pages).Applicant
Exhibit C25 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,687,971 (the “'971 Patent”) Invalidity Chart Based on Samsung Products that ran the Google Fast Pair Service (“Fast Pair”) prior to Mar. 13, 2020 (“Pre-2020 Samsung Products With Fast Pair”) (80 pages).Applicant
Exhibit D1 to Samsung Elec. Co., LTD's Invalidity Contentions, Grounds Of Invalidity Under Section 101 For U.S. Pat. No. 11,334,918 (28 pages).Applicant
Exhibit D2 to Samsung Elec. Co., LTD's Invalidity Contentions, Grounds Of Invalidity Under Section 101 For U.S. Pat. No. 11,443,344 (38 pages).Applicant
Exhibit D3 to Samsung Elec. Co., LTD's Invalidity Contentions, Grounds Of Invalidity Under Section 101 For U.S. Pat. No. 11,687,971 (40 pages).Applicant
Exhibit 1 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Phones (42 pages).Applicant
Exhibit 2 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Tablets (39 pages).Applicant
Exhibit 3 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Phones (25 pages).Applicant
Invalidity Contentions for U.S. Pat. No. 8,090,359 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,090,359 based on U.S. Patent App. No. 2004/0243519 A1 (“Perttila”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,090,359 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,090,359 based on U.S. Pat. No. 7,545,784 (“Mgrdechian”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,116,749 based on U.S. Pat. No. 7,545,784 (“Mgrdechian”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,116,749 based on U.S. Pat. No. 7,877,082 (“Eagle”).Applicant
Invalidity Contentions for U.S. Pat. No. 8, 116,749 based on U.S. Patent App. No. 2004/0243519 (“Perttila”).Applicant
Invalidity Contentions for U.S. Pat. No. 8, 116,749 based on U.S. Patent Application Publication No. 2010/0274859 (“Bucuk”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,116,749 based on Massachusetts Institute of Technology, Cricket System (“Cricket”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,559,968 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,559,968 based on U.S. Patent App. No. 2004/0243519 A1 (“Perttila”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,559,968 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,896 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,896 based on U.S. Patent App. No. 2004/0243519 A1 (“Perttila”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,896 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,913 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,913 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,913 based on U.S. Pat. No. 7,877,082 (“Eagle”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,385,913 based on U.S. Patent App. Pub. No. 2010/0138481 (“Behrens”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,369,842 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,369,842 based on U.S. Patent App. No. 2004/0243519 A1 (“Perttila”).Applicant
Invalidity Contentions for U.S. Pat. No. 8,369,842 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,038,129 based on U.S. Patent App. Pub. No. 2010/0138481 (“Behrens”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,038,129 based on U.S. Pat. No. 7,877,082 (“Eagle”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,038,129 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,038,129 based on U.S. Pat. No. 7,545,784 (“Mgrdechian”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,038,129 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 7,936,736 based on U.S. Patent App. Pub. No. 2010/0138481 (“Behrens”).Applicant
Invalidity Contentions for U.S. Pat. No. 7,936,736 based on U.S. Pat. No. 7,877,082 (“Eagle”).Applicant
Invalidity Contentions for U.S. Pat. No. 7,936,736 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 7,936,736 based on U.S. Pat. No. 7,545,784 (“Mgrdechian”).Applicant
Invalidity Contentions for U.S. Pat. No. 7,936,736 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,161,164 based on U.S. Pat. No. 7,877,082 (“Eagle”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,161,164 based on U.S. Pat. No. 7,545,784 (“Mgrdechian”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,161,164 based on U.S. Pat. No. 8,559,968 (“Frank”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,161,164 based on U.S. Pat. No. 6,837,436 (“Swartz”).Applicant
Invalidity Contentions for U.S. Pat. No. 9,161,164 based on Massachusetts Institute of Technology, Cricket System (“Cricket”).Applicant
Original Complaint for Patent Infringement; Secure Communication Technologies LLC v. Samsung Electronics Co., Ltd., et al.; Case No. 2:24-cv-484 (E.D. Tex., Jul. 3, 2024).Applicant
Supplemental Invalidity Contentions provided by Target Corp., Proxicom Wireless, LLC v. Target Corp.; Case No. 6:19-cv-1886 (M.D. Fla., Jun. 12, 2020).Applicant
Petition for Inter Partes Review, dated May 30, 2025, Case No. IPR2025-01049, Samsung Electronics Co., Ltd et al. v. Secure Communication Technologies, LLC (96 pages).Applicant
Petition for Inter Partes Review, dated May 30, 2025, Case No. IPR2025-01050, Samsung Electronics Co., Ltd et al. v. Secure Communication Technologies, LLC (98 pages).Applicant
Petition for Inter Partes Review, dated May 30, 2025, Case No. IPR2025-01051, Samsung Electronics Co., Ltd et al. v. Secure Communication Technologies, LLC (104 pages).Applicant
Declaration of Sundeep Rangan in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,334,918 (172 pages).Applicant
Declaration of Sundeep Rangan in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,443,344 (173 pages).Applicant
Declaration of Sundeep Rangan in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,687,971 (178 pages).Applicant
Bluetooth Specification v2.0 + EDR (Nov. 2004) (1230 pages).Applicant
Telecom Dictionary (2007) (“beacon channel,” “beaconing”) (4 pages).Applicant
Webster;s New World Telecom Dictionary (2008) (“beaconing”) (3 pages).Applicant
Wikipedia, “Radio Beacon” (5 pages).Applicant
IEEE Standard 802.15.1, Part 15.1: Wireless medium access control and physical layer (PHY) specifications for wireless personal area networks (WPANs) (600 pages).Applicant
Wayne Jansen et al., Proximity Beacons and Mobile Device Authentication NISTIR 7200 (Jun. 2005) (36 pages).Applicant
Ex. 1006 to Petition for Inter Partes Review of U.S. Pat. No. 11,334,918—Certified Translation of JP Pat. Pub. No. 2005/12973 to Watanabe (19 pages).Applicant
Yeong, J.H. et al., 802.11 a MAC layer: firmware/hardware co-design., Fourth International Conference on Information, Communications and Signal Processing, 2003 (6 pages).Applicant
Huang, L. et al., Enhancing wireless location privacy using silent period, IEEE Wireless Communications and Networking Conference, (vol. 2, pp. 1187-1192) (Mar. 2005) (7 pages).Applicant
IEEE 802 Specification IEEE Standard 802: IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture (Mar. 2002).Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Aug. 19, 2020, Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-46.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Aug. 19, 2020, Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-48.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Sep. 8, 2020, Case No. IPR2020-00934, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-49.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Sep. 8, 2020, Case No. IPR2020-00977, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-78.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Sep. 8, 2020, Case No. IPR2020-00978, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-71.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Sep. 8, 2020, Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-78.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Sep. 8, 2020, Case No. IPR2020-00980, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-73.Applicant
Patro, R.J., “Localization in Wireless Sensor Network with Mobile Beacons,” Honeywell Tech. Solution Lab, IEEE 2004, pp. 22-24.Applicant
Petition for Inter Partes Review, dated May 15, 2020, Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Exhibit 4 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Tablets (24 pages).Applicant
Exhibit 5 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Phones (51 pages).Applicant
Exhibit 6 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Tablets (47 pages).Applicant
Exhibit 7 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Phones (33 pages).Applicant
Exhibit 8 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Tablets (32 pages).Applicant
Exhibit 9 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,334,918 to the Accused Laptops (50 pages).Applicant
Exhibit 10 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Phones (45 pages).Applicant
Exhibit 11 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Tablets (45 pages).Applicant
Exhibit 12 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Phones (29 pages).Applicant
Exhibit 13 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Tablets (29 pages).Applicant
Exhibit 14 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Phones (39 pages).Applicant
Exhibit 15 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Tablets (39 pages).Applicant
Exhibit 16 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Phones (36 pages).Applicant
Exhibit 17 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Tablets (35 pages).Applicant
Exhibit 18 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,443,344 to the Accused Laptops (50 pages).Applicant
Exhibit 19 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Phones (39 pages).Applicant
Exhibit 20 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Tablets (38 pages).Applicant
Exhibit 21 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Phones (26 pages).Applicant
Exhibit 22 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Tablets (27 pages).Applicant
Exhibit 23 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Phones (34 pages).Applicant
Exhibit 24 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Tablets (35 pages).Applicant
Exhibit 25 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Phones (37 pages).Applicant
Exhibit 26 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Tablets (37 pages).Applicant
Exhibit 27 to Secure Communication Technologies' Infringement Contentions—Application of U.S. Pat. No. 11,687,971 to the Accused Laptops (37 pages).Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,116,749.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,369,842.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,385,896.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,385,913.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 9,038,129.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 9,161,164.Applicant
Declaration of Sylvia Hall-Ellis, Ph.D in Support of Patent Owners Preliminary Response; Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-66.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00934, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00977, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00978, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 14, 2020; Case No. IPR2020-00980, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00934, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00977, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00978, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Defendant's Preliminary Constructions of Proposed Terms, dated May 8, 2020; Case No. IPR2020-00980, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-22.Applicant
Office Action, U.S. Appl. No. 12/364,823, dated Dec. 28, 2010.Applicant
Office Action, U.S. Appl. No. 12/364,828, dated May 14, 2010.Applicant
Office Action, U.S. Appl. No. 12/364,828, dated Sep. 15, 2010.Applicant
Office Action, U.S. Appl. No. 12/364,938, dated May 13, 2010.Applicant
Office Action, U.S. Appl. No. 12/364,938, dated Sep. 14, 2010.Applicant
Office Action, U.S. Appl. No. 13/015,306 dated Jul. 17, 2012.Applicant
Office Action, U.S. Appl. No. 13/015,306; dated Jan. 9, 2012.Applicant
Office Action, U.S. Appl. No. 13/212,766; dated Apr. 26, 2012.Applicant
Office Action, U.S. Appl. No. 13/213,028, dated May 5, 2012.Applicant
Office Action, U.S. Appl. No. 12/364,819, dated Aug. 26, 2010.Applicant
Office Action, U.S. Appl. No. 12/364,823, dated Jun. 16, 2010.Applicant
Office Action; U.S. Appl. No. 12/364,938; dated Jul. 21, 2011.Applicant
Office Action; U.S. Appl. No. 13/015,306; dated Jun. 17, 2011.Applicant
Ondrus, J., et al., “An Architecture for Mobile Payments and Couponing in the Retail Industry,” 17th Bled eCommerce Conference eGlobal, Bled, Slovenia, Jun. 21-23, 2004, pp. 1-15.Applicant
Order dated Feb. 12, 2019, United States District Court Middle District of Florida Orlando Division.Applicant
Ortiz-Yepes, “Enhancing Authentication in eBanking with NFC enabled mobile phones”; Masters Thesis, Department of Mathematics and Computer Science, Eindhoven University of Technology; Aug. 11, 2008.Applicant
P370/470 Radio Scanner, Preliminary Symbol, Symbol Technologies, Inc., pp. 1-34 (1999).Applicant
Panos Kourouthanassis, et al., Grocery Supply-Chain Management: MyGrocer Innovative Business and echnology Framework, 17th Int'l Logistics Congress 264-73 (2001).Applicant
Panos Kourouthanassis, et al., Intelligent Cokes and Diapers: MyGrocer Ubiquitous Computing Environment, First Int'l Mobile Bus. Conf., 150-72 (2002).Applicant
Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs), IEEE Standards Board, Approved Jun. 12, 2003, The Institute of Electrical and Electronics Engineers, Inc. (New York); pp. 5, 25, 118 and 203.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Aug. 13, 2020, Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-50.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Aug. 13, 2020, Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-50.Applicant
Patent Owner Proxicom Wireless, LLC's Preliminary Response Pursuant to 37 C.F.R. 42.107; dated Aug. 13, 2020, Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.; pp. 1-48.Applicant
Mesh Dynamics MD4000 Brochure, accessed on Feb. 26, 2025 from https://meshdynamics.com/documents/MD4000_BROCHURE.pdf (5 pages).Applicant
Mesh Dynamics Security Primer, accessed on Feb. 26, 2025 from https://meshdynamics.com/documents/MDSECURITYPRIMER.pdf (24 pages).Applicant
Mesh Dynamics MD4000 Node Deployment and Trouble Shooting Guide, accessed on Feb. 26, 2025 from https://meshdynamics.com/documents/MD4000_HWMANUAL.pdf (31 pages).Applicant
Mesh Dynamics MD4000/MD6000 Multi-Radio Modular Mesh Nodes, accessed on Feb. 26, 2025 from https://www.meshdynamics.com/Multiple-Radio-Backhaul.html.Applicant
Mesh Dynamics Meshcommands Refernce Manual, accessed on Feb. 26, 2025 from https://meshdynamics.com/documents/MD4000_Meshcommands.pdf (33 pages).Applicant
For Mesh Dynamics System Integrators Channel Allocation Schemes, accessed on Feb. 26, 2025 from https://meshdynamics.com/documents/MD4000_BestPractices.pdf (50 pages).Applicant
Mesh Dyanmics Network Viewer User Guide 10.1 Network Viewer Release 10.1 Jun. 2014, accessed on Feb. 26, 2025 from https://meshdynamics.com/documents/MD4000_NMSGUIDE_101.pdf (61 pages).Applicant
Mesh Dynamics Press Release on 3-Radio Mesh for Citywide VoIP Meshdynamics Press Release Jan. 2005, accessed on Feb. 26, 2025 from https://meshdynamics.com/MDPR013105.html.Applicant
Plaintiff Secure Communication Technologies, LLC's Disclosure of Asserted Claims and Infringement Contentions, , Case No. 2:24-cv-00484-JRG, Secure Communications Technologies, LLC v. Samsung Electronic Co., LTD, et al., Nov. 25, 2024(9 pages).Applicant
WLAN 802.11a/b/g High Power mini-PCI Module, Wistron NeWeb Corporation, accessed on Feb. 26, 2025 from http://meshdynamics.com/documents/MD4000_WistronSpecs.pdf (3 pages).Applicant
FCC ID UZU-MD5, FCC ID Report for Mesh Dynamics Device, accessed on Feb. 26, 2025 from https://fcc.report/FCC-ID/UZU-MD5/.Applicant
Mesh Dynamics MD4000 Product Family Hardware Installation Instructions, accessed on Feb. 26, 2025 from https://fcc.report/FCC-ID/UZU-MD5/806334.pdf (15 pages).Applicant
IEEE 802.11-1999 IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local andvmetropolitan area networks—Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Reaffirmed Jun. 12, 2003 (528 pages).Applicant
IEEE 802.11a-1999 Supplement to IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: High-speed Physical Layer in the 5 GHz Band, Approved Sep. 16, 1999 (91 pages).Applicant
IEEE 802.11b-1999 Supplement to IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Higher-Speed Physical Layer Extension in the2.4 GHz Band, Approved Sep. 16, 1999 (96 pages).Applicant
IEEE 802.11e-2005 IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 8: Medium Access Control (MAC) Quality of Service Enhancements, Nov. 11, 2005 (211 pages).Applicant
IEEE 802.11g-2003 IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 4: Further Higher Data Rate Extension in the 2.4 GHz Band, Jun. 27, 2003 (78 pages).Applicant
IEEE 802.11i-2004 IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements, Jul. 23, 2004 (190 pages).Applicant
IEEE 802.1X-2004, IEEE Standard for Local and metropolitan area networks: Port-Based Network Access Control, Dec. 13, 2004 (179 pages).Applicant
Bluetooth Specification Version 4.2 [vol. 6, Part B], released on Dec. 2, 2014 (96 pages).Applicant
Bluetooth Specification Version 5 [vol. 6, Part B], released on Dec. 2, 2014 (150 pages).Applicant
Fast Pair Specification (Wayback Machine Internet Archive Record for Google Developers page “Google Fast Pair Service” as of Jan. 17, 2019), accessed on Mar. 5, 2025 from https://web.archive.org/web/20190117134956/https:/developers.google.com/nearby/fast-pair/spec.Applicant
Fast Pair Changelog, accessed on Mar. 5, 2025 from https://developers.google.com/nearby/fastpair/specifications/appendix/changelog.Applicant
Wayback Machine Internet Archive Record for “Google announces a new Find My Accessories feature for Fast Pair devices and a Bluetooth settings revamp for Android Q,” accessed on Mar. 5, 2025 from https://web.archive.org/web/20190520024551/https://www.xda-developers.com/android-q-bluetooth-revamp-fast-pair-find-my-accessories/.Applicant
Wayback Machine Internet Archive Record for “Google just made Bluetooth pairing easier with Fast Pair,” accessed on Mar. 5, 2025 from https://web.archive.org/web/20171101012457/https:/www.androidauthority.com/google-fast-pair-811293/.Applicant
Wayback Machine Internet Archive Record for “Fast Pair Update” accessed on Mar. 5, 2025 from https://web.archive.org/web/20181127181704/https:/android-developers.googleblog.com/2018/11/fast-pair-update.html.Applicant
Wayback Machine Internet Archive Record for “Announcing Fast Pair—effortless Bluetooth pairing for Android” accessed on Mar. 5, 2025 from https://web.archive.org/web/20171031222204/https://android-developers.googleblog.com/2017/10/announcing-fast-pair-effortless.html.Applicant
Android Version History, accessed on Mar. 5, 2025 from https://en.wikipedia.org/wiki/Android_version_history.Applicant
Defendants Samsung Electronics Co., LTD. and Samsung Electronics America, Inc's Initial Invalidity Contentions, Case No. 2:24-cv-00484-JRG, Secure Communications Technologies, LLC v. Samsung Electronic Co., LTD, et al., Feb. 18, 2025(114 pages).Applicant
Exhibit A1 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2006/0287813 (“Quigley”) (26 pages).Applicant
Exhibit A2 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on U.S. Patent App. 2005/0250552 (“Eagle”) (29 pages).Applicant
Exhibit A3 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Pat. No. 7,545,784 (“Mgrdechian”) (30 pages).Applicant
Exhibit A4 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2010/0138481 (“Behrens”) (42 pages).Applicant
Exhibit A5 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2009/0029691 (“Shen”) (23 pages).Applicant
Exhibit A6 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Pat. No. 8,239,286 (“Davis”) (23 pages).Applicant
Exhibit A7 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on UU.S. Patent App. 2009/0245142 (“Want”) (44 pages).Applicant
Exhibit A8 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on Japanese Patent App. 2005-012973 (“Watanabe”) (26 pages).Applicant
Exhibit A9 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2007/0030824 (“Ribaudo”) (18 pages).Applicant
Exhibit A10 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on International Publication No. 2006/103387 (“Turnbull”) (37 pages).Applicant
Exhibit A11 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Pat. No. 6,928,263 (“Blake”) (23 pages).Applicant
Exhibit A12 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2009/0298514 (“Ullah”) (64 pages).Applicant
Exhibit A13 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. 2005/0130634 (“Godfrey”) (45 pages).Applicant
Exhibit A14 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2006/0023711 (“Perret”) (30 pages).Applicant
Exhibit A15 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,334,918 (the “'918 Patent”) Invalidity Chart Based on U.S. Pat. No. 7,000,001 (“Lazaridis”) (14 pages).Applicant
Exhibit B1 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on U.S. Pat. No. 8,090,359 (“Proctor '359”) (69 pages).Applicant
Exhibit B2 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on U.S. Pat. No. 9,161,164 (“Proctor '164”) (65 pages).Applicant
Exhibit B3 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on U.S. Patent App. 2017/0289779 (“Postrel”) (58 pages).Applicant
Exhibit B4 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on International Publication No. 2006/103387 (“Turnbull”) (42 pages).Applicant
Exhibit B5 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on U.S. Patent App. No. 2006/0287813 (“Quigley”) (35 pages).Applicant
Exhibit B6 to Samsung Elec. Co., LTD's Invalidity Contentions, U.S. Pat. No. 11,443,344 (the “'344 Patent”) Invalidity Chart Based on U.S. Patent App. 2010/0113001 (“Tenbrook”) (40 pages).Applicant
Petition for Inter Partes Review, dated Nov. 11, 2025, Case No. IPR2026-00098, Google LLC v. Secure Communication Technologies, LLC (105 pages).Applicant
Declaration of Mark Lanning in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,995,685 (142 pages).Applicant
Office Action received in related U.S. Appl. No. 12/364,823, dated Jun. 16, 2010.Applicant
Office Action received in related U.S. Appl. No. 12/364,828, dated May 14, 2010.Applicant
Office Action received in related U.S. Appl. No. 12/364,938, dated May 13, 2010.Applicant
Office Action, U.S. Appl. No. 12/364,819, dated Apr. 16, 2012.Applicant
Office Action, U.S. Appl. No. 12/364,819, dated Nov. 15, 2010.Applicant
Petition for Inter Partes Review, dated May 15, 2020, Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated May 15, 2020, Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated May 27, 2020, Case No. IPR2020-00934, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated May 27, 2020, Case No. IPR2020-00977, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated May 8, 2020, Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated May 8, 2020, Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated Jun. 1, 2020, Case No. IPR2020-00978, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated Jun. 1, 2020, Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Petition for Inter Partes Review, dated Jun. 1, 2020, Case No. IPR2020-00980, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Priyantha et al., “The Cricket Indoor Location System,” Massachusetts Institute of Technology, pp. 1-199 (2005).Applicant
Priyantha, et al., “The Cricket Location-Support System,” 6th ACM International Conference on Mobile Computing and Networking (ACM MOBICOM), Boston, MA, MIT Laboratory for Computer Science (2000).Applicant
U.S. Appl. No. 60/758,011, filed Jan. 11, 2006.Applicant
U.S. Appl. No. 60/758,012, filed Jan. 11, 2006.Applicant
Quiqley, A., et al., “BlueStar, a privacy centric location aware system,” Telstra Research Laboratories, Melbourne, Australia, IEEE 2004, 6.Applicant
Roth, C.; Email dated Apr. 14, 2020 regarding Initial Identification of Disputed Claim Terms; Target Corporation vs. Droxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-2.Applicant
Rusli, E., “Gift card marketplace Cardpool Introduces Instand Redemption, Attracts Super Angels” [online], Sep. 7, 2010. Retrieved from the Internet URL: http://techcrunch.com/2010/09/07/gift-card-marketplace-cardpool-plasticju-ngle/, one page.Applicant
S. S. (Peter) Wang et al., E-911 Location Standards and Location Commercial Services, Nokia Research Center (2000) 5 pages.Applicant
Sarma et al., RFID Systems and Security and Privacy Implications, B.S. Kaliski Jr. et al. (Eds.): CHES 2002, LNCS 2523, 2003. c Springer-Verlag Berlin Heidelberg 2003, 16 pages.Applicant
Savvides, A., et al., “Chapter 15: Localization in Sensor Networks,” pp. 327-349.Applicant
Schiller, Jochen, et al., “Location-Based Services,” Elsevier, ISBN 9781493303786.Applicant
Shih et al., “Wake on Wireless: An Event Driven Energy Saving Strategy for Battery Operated Devices,” MOBICOM 02 Sep. 23-26, 2002, Atlanta, Georgia, USA, Copyright 2002, 12 pages.Applicant
Shruthi et al., “Wibree Using Digital Radio Technology” International Journal of Advanced Trends in Computer Science and Engineering, vol. 3, No. 1, pp. 260-264 (2014), Special Issue of ICETETS 2014 Held on Feb. 24-25, 2014 in Malla Reddy Institute of Engineering and Technology, Secunderabad-14, AP, India.Applicant
Simple Pairing Whitepaper, Bluetooth Special Interest Group, V10r00, (2006).Applicant
Social Serendipity: Mobilizing Social Software, Eagle et al., Pervasive Computing, 1536-1268, pp. 28-34 (2005).Applicant
Specification of the Bluetooth System, Bluetooth Master Table of Contents and Compliance Requirements, Covered Core Package version: 2.1 + EDR (2007).Applicant
Specification vol. 0, Specification of the Bluetooth System, Wireless Connections Made Easy, Master Table of Contents and Compliance Requirements, Covered Core Package version 3.0 + HS, Current Master TOC, Apr. 21, 2009, 1712.Applicant
Srinivasan, T., et al., “HPRS: A Hybrid P2P Reputation System using File and Peer Rating,” Third International Symposium on Information Assurance and Security, IEEE, pp. 307-312 (2007).Applicant
Subramanian, S., et al., “SBIL: Scalable Indoor Localization and Navigation Service,” University of Tubingen Dept. of Computer Engineering, IEEE 2007, pp. 27-30.Applicant
Symbol Technologies, PDT 2800 Series, Product Reference Guide, pp. 1-36 (2001).Applicant
Symbol Technologies, PDT 6800 Series, Product Reference Guide, Revision A (2001).Applicant
Symbol Technologies, PDT 8100 Series, Product Reference Guide, pp. 1-48 (2001).Applicant
Symbol Technologies, Portable Shopping System: Integration Guide (2000); Wise Marketer Staff, Giant Foods Self-service Concept Store Opens (Oct. 12, 2005), https://thewisemarketer.com/headlines/giant-foods-self-service-concept-store-opens-4-2/.Applicant
Symbol Technologies, Wireless Networker LA-5033 PCT Adapter and LA-5030 PC Card, User Guide, pp. 1-72 (2004).Applicant
Target Corporation's Preliminary Invalidity Contentions dated Mar. 16, 2020, filed in Proxicom Wireless LLC v. Target Corporation, U.S. District Court, Middle District of Florida, Orlando Division, C.A. No. 6:19-cv-1886-RBD-LRH.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00934, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00977, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00978, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Target's Initial Identification of Disputed Claim Terms; dated Apr. 10, 2020; Case No. IPR2020-00980, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Petition for Inter Partes Review, dated Jul. 2, 2025, Case No. IPR2025-01181, Google LLC v. Secure Communication Technologies, LLC (95 pages).Applicant
Petition for Inter Partes Review, dated Jul. 2, 2025, Case No. IPR2025-01182, Google LLC v. Secure Communication Technologies, LLC (95 pages).Applicant
Petition for Inter Partes Review, dated Jul. 2, 2025, Case No. IPR2025-01183, Google LLC v. Secure Communication Technologies, LLC (103 pages).Applicant
Declaration of Mark Lanning in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,334,918 (133 pages).Applicant
Declaration of Mark Lanning in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,443,344 (115 pages).Applicant
Declaration of Mark Lanning in Support of Petition for Inter Partes Review of U.S. Pat. No. 11,687,971 (137 pages).Applicant
The Wayback Machine—Assigned Numbers, Bluetooth Baseband (https://web.archive.org/web/20021214114356/http://www.bluetooth.org/assigned-numbers/baseband.htm) (5 pages).Applicant
The Wayback Machine, iPhone 3G Technical Specifications (https://web.archive.org/web/20080725084414/http://www.apple.com/iphone/specs.html).Applicant
Apple Inc., iPhone User Guide for iphone OS 3.1 Software (https://cdsassets.apple.com/live/6GJYWVAV/user/ma616_iphone_ios3_1_user_guide.pdf) (217 pages).Applicant
Joint Claim Construction Statement filed May 22, 2020 with the United States District Court, Middle District of Florida, Orlando Division.Applicant
Joint Claim Construction Statement, dated Jun. 15, 2020; Case No. IPR2020-00934, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Joint Claim Construction Statement, dated Jun. 15, 2020; Case No. IPR2020-00977, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Joint Claim Construction Statement, dated Jun. 15, 2020; Case No. IPR2020-00978, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Order dated Dec. 4, 2020, Case No. IPR2020-00978, United States Patent trial and Appeal Board, Target Corporation vs. Proxicom Wireless, L.L.C.Applicant
Joint Claim Construction Statement, dated Jun. 15, 2020; Case No. IPR2020-00979, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Joint Claim Construction Statement, dated Jun. 15, 2020; Case No. IPR2020-00980, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Joint Claim Construction Statement, dated May 22, 2020; Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Claim Construction Statement, dated May 22, 2020; Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Claim Construction Statement, dated May 22, 2020; Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Claim Construction Statement, dated May 22, 2020; Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Claim Construction Statement, dated May 22, 2020; Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Claim Regarding Claim Construction Briefing Procedure, dated Jun. 15, 2020; Case No. IPR2020-00903, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Joint Statement Regarding Claim Cnstruction Briefing Procedure, dated Jun. 15, 2020; Case No. IPR2020-00931, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Statement Regarding Claim Cnstruction Briefing Procedure, dated Jun. 15, 2020; Case No. IPR2020-00932, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Joint Statement Regarding Claim Cnstruction Briefing Procedure, dated Jun. 15, 2020; Case No. IPR2020-00933, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6: 19-cv-1886-RBD-LRH; pp. 1-6.Applicant
Joint Statement Regarding Claim Construction Briefing Procedure, dated Jun. 15, 2020; Case No. IPR2020-00904, Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-28.Applicant
Jonathan P. Munson and Vineet K. Gupta, Location-Based Notification as a General-Purpose Service, Proceedings of the 2nd International Workshop on Mobile Commerce (2002) 5 pages.Applicant
Josephson, W., et al., “Peer-to-Peer Authentication with a Distributed Single Sign-On Service,” G.M. Voelker and S. Shenker (Eds.): IPTPS 2004, LNCS 3279, pp. 250-258, 2004.Applicant
Juels, Ari, “Minimalist Cryptography for Low-Cost RFID Tags” SCN '04 Proceedings of the 4th international conference on Security in Communication Networks, Springer-Verlag Berlin, Heidelberg (Copyrights)2005, 29 Pages.Applicant
Juels, et al., “Squealing Euros: Privacy Protection in RFID-Enabled Banknotes,” 2003, 22 pages.Applicant
Jukka Reunamaki PowerPoint Presentation Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs), Submission Tille: [Nokia PHY submission to Task Group 4], Jul. 2001, 59 pages.Applicant
Kolodziej, K., et al., “In-Building Positioning: Modeling Location for Indoor World,” Proceedings of the 15th Int'l Workshop on Database and Expert Systems Applications (DEXA 04), 5 (2004).Applicant
Kolodziej, K., et al., “Local Positioning Systems, LBS Applications and Services,” Taylor and Francis Group LLC, 2006, 436.Applicant
Kortuem, G. et al., “Context-Aware, Adaptive Wearable Computers as Remote Interfaces to ‘Intelligent’ Environments” University of Oregon Computer Science Department (1998).Applicant
Krzysztof W. Kolodziej and Johan Hjelm, Local Positioning Systems (2006).Applicant
LaMarca, A., et al., “Place Lab: Device Positioning Using Radio Beacons in the Wild,” Intel Corp., 2004.Applicant
Laudon, K. “E-commerce: Business, Technology, Society,” Second Edition, (Pearson 2003).Applicant
Laudon, Kenneth C., et al., “E-commerce,” Second Edition, Pearson, ISBN No. 0-321-20056-X, 2004.Applicant
Lee, T.O., et al., “An Agent-Based Micropayment System for E-commerce,” J. Liu and Y. Ye (Eds.): E-commerce Agents, LNAI 2033, pp. 247-263, 2001.Applicant
Lim, H., et al., “Zero-Configuration, Robust Indoor Localization: Theory and Experimentation,” University of Illinois Dept. of Computer Science, Technical Report No. UIUCDCS-R-2005-2629, Aug. 2005, p. 1-12.Applicant
Liu, H., et al., “Survey of Wireless Indoor Positioning Techniques and Systems,” IEEE Transactions on Systems, Man, and Cybernetics Part C: Applications and Reviews, vol. 37, No. 6, Nov. 2007, pp. 1067-1080.Applicant
Makela, Petteri, “Local Positioning Systems and Indoor Navigation,” Licentiate of Science Thesis, Tampere University of Technology, pp. 116 (2008).Applicant
Marco, A., et al., “Location-based services for elderly and disabled people,” ScienceDirect, Computer Communications 31 (2008), pp. 1055-1066.Applicant
Mettala, R., “Bluetooth Protocol Architecture,” Bluetooth White Paper, Document No. 1.C.120/1.0, 3-20 (1999).Applicant
Molnar, David, Andrea Soppera, and David Wagner. “A scalable, delegatable pseudonym protocol enabling ownership transfer of RFID tags.” International Workshop on Selected Areas in Cryptography. Springer Berlin Heidelberg, 2005, 15 pages.Applicant
Nissanka B. Priyantha, et al., Anchor-Free Distributed Localization in Sensor Networks, LCS Tech. Report #892 (2003).Applicant
Nissanka B. Priyantha, et al., Mobile-Assisted Localization in Wireless Sensor Networks, IEEE INFOCOM Conf. (Mar. 2005).Applicant
Non-Final Office Action received for U.S. Appl. No. 14/861,563, dated May 9, 2016, 16 pages.Applicant
Non-Final Office Action received for U.S. Appl. No. 16/817,896, dated Jun. 9, 2020, 22 pages.Applicant
Non-Final Office Action received for U.S. Appl. No. 16/817,896, dated Nov. 24, 2020, 34 pages.Applicant
Non-Final Office Action received for U.S. Appl. No. 16/817,896, dated Sep. 3, 2020, 23 pages.Applicant
Non-Final Office Action received for U.S. Appl. No. 17/366,826, dated Aug. 17, 2021, 40 pages.Applicant
Notice of Allowance dated Jul. 1, 2010 for U.S. Appl. No. 12/364,828.Applicant
Notice of Allowance received for U.S. Appl. No. 16/817,896, dated Jun. 8, 2021, 17 pages.Applicant
Notice of Allowance received for U.S. Appl. No. 16/817,896, dated Jun. 28, 2021, 4 pages.Applicant
Notice of Allowance received for U.S. Appl. No. 16/817,896, dated Mar. 19, 2021, 17 pages.Applicant
Notice of Allowance, U.S. Appl. No. 13/015,306 dated Nov. 8, 2012.Applicant
Notice of Allowance, U.S. Appl. No. 13/212,723 dated Jan. 16, 2013.Applicant
Office Action received in related U.S. Appl. No. 12/364,819, dated Aug. 26, 2010.Applicant
Thongthammachart, S., et al., “Bluetooth enables in-door mobile location services,” In Proceedings of the 57th IEEE Semiannual Vehicular Technology Conference: VTC2003 (vol. 3, pp. Session 8H, paper 3) IEEE.Applicant
Transaction Receipt; Pacer Service Center, dated Aug. 6, 2020, pp. 1-3.Applicant
Transcript of Telephonic Motion Hearing, dated Jun. 3, 2020; United States District Court, Middle District of Florida, Orlando Division; pp. 1-41; Case No. IPR2020-00903; Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 5:19-cv-1886-RBD-LRH; pp. 1-41.Applicant
Transcript of Telephonic Motion Hearing, dated Jun. 3, 2020; United States District Court, Middle District of Florida, Orlando Division; pp. 1-41; Case No. IPR2020-00904; Target Corporation vs. Proxicom Wireless, L.L.C.; C.A. No. 6:19-cv-1886-RBD-LRH; pp. 1-41.Applicant
U.S. Appl. No. 60/758,010, filed Jan. 11, 2006 by Rajiv Laroia for Methods and apparatus for facilitating identification, synchronization or acquisition using beacon signals, 30 pages.Applicant
U.S. Appl. No. 60/758,011, filed Jan. 11, 2006 by Rajiv Laroia for Methods and apparatus for using beacon signals for identification, synchronization or acquisition in an ad hoc wireless network, 26 pages.Applicant
U.S. Appl. No. 60/758,012, filed Jan. 11, 2006 by Rajiv Laroia for Methods and apparatus for using beacon signals in a cognitive radio network, 24 pages.Applicant
U.S. Appl. No. 60/845,051, filed Sep. 15, 2006 by Junyi Li for Beacons in a mixed wireless communication system, 30 pages.Applicant
U.S. Appl. No. 60/845,052, filed Sep. 15, 2006 by Aleksandar Jovicic for Beacons in a mixed wireless communication system, 29 pages.Applicant
U.S. Appl. No. 60/845,052, filed Sep. 15, 2006.Applicant
U.S. Appl. No. 60/863,304, filed Oct. 27, 2006 by Rajiv Laroia for Power Allocation Scheme, 15 pages.Applicant
U.S. Appl. No. 61/054,162, filed May 18, 2008 by Mark Braverman for System and Method for Electronic Payment.Applicant
U.S. Appl. No. 61/122,240, filed Dec. 12, 2008 by Rajiv Patel for System and Method for Electronic Payment.Applicant
Using Blouetooth, MC909X User Guide, Symbol Technologies, Inc., pp. 1-66 (2005).Applicant
Using MC9094 Phone, MC909X User Guide, Symbol Technologies, Inc., pp. 1-20 (2005).Applicant
Wang, et al., “Peer2Me—Rapid Application Framework for Mobile Peer-to-Peer Applications”, Department of Compute and Information Science.Applicant
Wang, F., et al., “Bridging Physical and Virtual Worlds: Complex Event Processing for RFID Data Streams,” University of California, Los Angeles Computer Science Department, Springer-Verlag Berlin Heidelberg 2006, pp. 588-607.Applicant
Want, R., et al., “Bridging Physical and Virtual Worlds with Electronic Tags,” Xerox PARC, CHI '99 May 15-20, 1999, pp. 370-377.Applicant
Wauters, R., “TC50: Gift Card Auction Site Rackup Aims to Shake Up Market” [online], Sep. 14, 2009. Retrieved from the Internet URL: http://techcrunch.com/2009/09/14/tc50-gift-card-auction-site-rackup-aims-- to-shake-up-market/, one page.Applicant
WaveWorks Portable Shopping System Integration Guide, Integration Services Group, Pittsburgh, Pennsylvania, pp. 1-185.Applicant
Wei, G., et al., “HiPEC: A Hybrid P2P Model for Electronic Commerce,” Zhejiang Gongshang University College of Computer and Information Engineering, pp. 1-5 (2008).Applicant
Weis et al. “Security and privacy aspects of low-cost radio frequency identification systems”. In: Security in pervasive Computing. Springer, 201-212 (2004).Applicant
Weis et al., Security and Privacy Aspects of Low-Cost Radio Frequency Identification Systems, International Journal of Security and Networks, vol. 5 Issue 2/3, Mar. 2010, 12 pages.Applicant
Wg, Hid, “Device Identification Specification”, V12r00, 1-20 (2006) Need Publication Details.Applicant
Yang, H., et al., “Indoor Localization Systems—Tracking objects and personnel with sensors, wireless networks and RFID,” Measurement+ Control, vol. 42/1, Feb. 2009, pp. 18-23.Applicant
Zhang, Y., et al., “Progress in WWW Research and Development,” 1oth Asia-PacificWeb Conference, APWeb 2008, Shenyang, China, Apr. 26-28, 2008 Proceedings, pp. 331-341.Applicant
Zhou, Y., et al., “A Map Registration Localization Approach based on Mobile Beacons for Wireless Sensor Networks,” Communications Research Centre Canada, 2011 Crown, 5 pp.Applicant
Aalto, L., et al., “Bluetooth and WAP Push Based Location-Aware Mobile Advertising System,” MobiSys '04, Jun. 6-9, 2004, Boston, MA, pp. 49-58.Applicant
Adam Smith, et al., Tracking Moving Devices with the Cricket Location System, 2nd USENIX/ACM MobiSys Conf. (Jun. 2004).Applicant
Adams, Richard. “www.advertising,” Watson Guptill, ISBN 978-0823058617 (2003).Applicant
Amended Invalidity Contentions, dated Mar. 22, 2019, Case No. 6:16-cv-00064-RBK-GJK, Proxicom Wireless, L.L.C. v. Macy's, Inc. and Macy's Florida Stores, LLC.Applicant
Amendment in Response to Non-Final Office Action filed Jun. 3, 2008 for U.S. Appl. No. 11/055,310.Applicant
Aparicio, S., et al., “A Fusion Method Based on Bluetooth and WLAN Technologies for Indoor Location,” Proceedings of IEEE Int'l Conference on Multisensor Fusion and Integration for Intelligent Systems Seoul, Korea, Aug. 20-22, 2008, pp. 487-491.Applicant
Ateniese et al., “Untraceable RFID Tags via Insubvertible Encryption”, CCS'05, Nov. 7-11, 2005, Alexandria, Virginia, USA. Copyright 2005 ACM 1-59593-226-7/05/0011, 10 pages.Applicant
Bahl, P et al., “RADAR: An In-Building RF-based User Location and Tracking System,” Microsoft Research.Applicant
Balakrishnan et al., “Lessons from Developing and Deploying the Cricket Indoor Location System,” MIT Computer Science and Artificial Intelligence Laboratory, pp. 1-15 (2003).Applicant
Barahim, Z., et al., “Low-Cost Bluetooth Mobile Positioning for Location-based Application,” University of Mauritius Computer Science and Engineering Dept., 4 pp.Applicant
Bargh, M., et al., “Indoor Localization Based on Response Rate of Bluetooth Inquiries,” Melt '08, Sep. 19, 2008, San Francisco, CA, pp. 49-54.Applicant
Beacon-Stuffing: Wi-Fi Without Associations, Chandra et al., IEEE Computer Society, 1550-6193, pp. 53-57 (2007).Applicant
Bluetooth White Paper 1.1, AU-System, 1-25 (2000).Applicant
Brakman et al., “Formal model of the Bluetooth Inquiry Protocol”, 1-13 (2006).Applicant
Case Study: “Agilysys Makes a Giant Leap Toward Wireless Shopping”, CRN News (2005).Applicant
Chari, S., et al., “Security Issues in M-Commerce: A Usage-based Taxonomy,” E-commerce Agents, LNAI 2033, pp. 264-282, 2001.Applicant
Chawathe, S., “Beacon Placement for Indoor Localization using Bluetooth,” Proc. of the 119th Int'l IEEE Conference on Intelligent Transportation Systems, Beijing, China, Oct. 12-15, 2008, pp. 980-985.Applicant
Cricket v2 User Manual, Cricket Project, MIT Computer Science and Artificial Intelligence Lab Cambridge, MA (2005).Applicant
D Molnar , Privacy and Security in Library RFID Issues, Practices, and Architectures, Anonymized for submission, May 3, 2004, 19 pages.Applicant
D. Ramireddy PowerPoint Presentation—Wibree Technology, Mar. 26, 2015, 21 pages.Applicant
Dan Alaimo, Giant Eagle to Test Self-Scanning, Supermarket News (Jun. 26, 2000), https://www.supermarketnews.com/print/26715.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 7,936,736.Applicant
Declaration of David Hilliard Williams in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,090,359.Applicant
Google's Answer to First Amended Complaint for Patent Infringement; Secure Communication Technologies LLC v. Google. LLC; Case No. 1:25-cv-01207 (Nov. 17, 2025) (35 pages).Applicant
Petition for Inter Partes Review, dated Jan. 9, 2026, Case No. IPR2026-00099, Google LLC v. Secure Communication Technologies, LLC (93 pages).Applicant
Declaration of Mark Lanning in Support of Petition for Inter Partes Review of U.S. Pat. No. 8,116,749 (98 pages).Applicant
Defendant's Answer and Counterclaims (Redacted Version), Secure Communication Technologies, LLC v. Apple Inc., Case No. 1:25-cv-01579DAE, Dated Jan. 20, 2026 (94 pages).Applicant
Petitioner's Opposition to Patent Owner's Discretionary Denial Brief, IPR2026-00099, Dated Apr. 4, 2026 (24 pages).Applicant