Generating non-redundant physically, logically, and location-specific network endpoint identifiers

Abstract

The invention relates to generating a non-redundant physical, logical, and location-specific network endpoint identifier. First information identifying a first one of a target circuit or a radio frequency (RF) tag is communicated to a second one of the target circuit or the RF tag. Second information identifying the second one of the target circuit and the RF tag is then derived from the transmitted first information. The second information is then stored. In some cases, the first information is communicated through a wired interface or a wireless interface between the target circuit and the RF tag. The first information identifying the RF tag may be communicated to the target circuit, and may derive second information identifying the target circuit based on the first information identifying the RF tag by making the second information equivalent to the first information or applying a predetermined algorithm to the first information to generate the second information.

Description

Technical Field

[0001] This disclosure relates to generating non-redundant, physically, logically, and location-specific network endpoint identifiers. Background Technology

[0002] Many systems and products are heterogeneous collections of different types of devices or sensors that perform different functions within the system or product. These devices and sensors are often referred to as endpoints. A common example of a heterogeneous system is the automobile. Endpoints in an automobile typically include headlights, taillights, safety / radar sensors, LED light strips, air conditioning control vents, and many other types of devices or sensors. Summary of the Invention

[0003] According to one aspect of this disclosure, a method is provided, comprising: transmitting first information identifying a first party in a target circuit or a radio frequency (RF) tag to a second party in the target circuit or the RF tag; determining second information identifying the second party in the target circuit or the RF tag based on the transmitted first information; and storing the second information.

[0004] According to one or more embodiments, transmitting the first information includes transmitting the first information through at least one of a wired interface or a wireless interface between the target circuit and the RF tag.

[0005] According to one or more embodiments, transmitting the first information includes transmitting first information identifying the RF tag to the target circuit, and wherein deriving the second information includes deriving second information identifying the target circuit based on the first information identifying the RF tag.

[0006] According to one or more embodiments, deriving the second information includes one of the following operations: making the second information equivalent to the first information; or applying a predetermined algorithm to the first information to generate the second information.

[0007] According to one or more embodiments, the method further includes: before transmitting the first information, performing at least one of the following operations: encrypting the first information, signing the first information, or generating authentication information for the first information; and before exporting the second information, performing at least one of the following operations: decrypting the encrypted first information, verifying the signature on the first information, or authenticating the first information.

[0008] According to one or more embodiments, the method further includes: determining the location of the target circuit; and registering the location and the second information with a controller configured to provide control signals to the target circuit.

[0009] According to one or more embodiments, determining the location of the target circuit includes detecting the RF tag using a scanner, and determining the location of the target circuit based on at least one of the location of the scanner and the strength of the signal received by the scanner from the RF tag.

[0010] According to one or more embodiments, the method further includes: using the scanner to scan an area near the intended installation location of the target circuit and the RF tag; and locating or confirming the location of the target circuit in response to detecting that the RF tag is near the intended installation location.

[0011] According to a second aspect of this disclosure, an apparatus is provided, comprising: a radio frequency (RF) tag; and a target circuit coupled to the RF tag via an interface configured to transmit first information identifying a first of the target circuit or the RF tag to a second of the target circuit or the RF tag, wherein the target circuit or the second of the RF tag is configured to derive second information identifying the second of the target circuit and the RF tag from the transmitted first information.

[0012] According to one or more embodiments, the interface includes at least one of a wired interface between the target circuit and the RF tag and a wireless interface between the target circuit and the RF tag.

[0013] According to one or more embodiments, the interface is configured to transmit first information identifying the RF tag to the target circuit, and wherein the target circuit is configured to derive second information identifying the target circuit based on the first information identifying the RF tag.

[0014] According to one or more embodiments, the target circuit is configured to make the second information equivalent to the first information, or to apply a predetermined algorithm to the first information to generate the second information.

[0015] According to one or more embodiments, the RF tag is configured to perform at least one of the following operations before transmitting the first information to the target circuit via the interface: encrypting the first information, signing the first information, or generating authentication information for the first information; and wherein the target circuit is configured to perform at least one of the following operations before exporting the second information: decrypting the encrypted first information, verifying the signature on the first information, or authenticating the first information.

[0016] According to a third aspect of this disclosure, a system is provided, comprising: at least one target circuit coupled to at least one radio frequency (RF) tag via at least one interface, the at least one interface being configured to transmit first information identifying a first of the at least one target circuit or the at least one RF tag to a second of the at least one target circuit and the at least one RF tag, wherein the at least one target circuit or the second of the at least one RF tag is configured to derive second information identifying the at least one target circuit and the second of the at least one RF tag from the transmitted first information; and a controller configured to provide control signals to the at least one target circuit based on at least one location of the at least one target circuit.

[0017] According to one or more embodiments, the at least one interface includes at least one of a wired interface between the at least one target circuit and the at least one RF tag and a wireless interface between the at least one target circuit and the at least one RF tag.

[0018] According to one or more embodiments, the interface is configured to transmit first information identifying the at least one RF tag to the at least one target circuit, and wherein the at least one target circuit is configured to derive second information identifying the at least one target circuit based on the first information identifying the at least one RF tag.

[0019] According to one or more embodiments, the at least one target circuit is configured to make the second information equivalent to the first information, or to apply a predetermined algorithm to the first information to generate the second information.

[0020] According to one or more embodiments, the at least one RF tag is configured to perform at least one of the following operations before transmitting the first information to the at least one target circuit via the at least one interface: encrypting the first information, signing the first information, or generating authentication information for the first information; and wherein the at least one target circuit is configured to perform at least one of the following operations before exporting the second information: decrypting the encrypted first information, verifying the signature on the first information, or authenticating the first information.

[0021] According to one or more embodiments, the controller is configured to receive information indicating at least one location of the at least one target circuit, and to register the at least one location and the second information derived from the at least one target circuit.

[0022] According to one or more embodiments, the system further includes: a scanner configured to detect the at least one RF tag and determine the at least one location of the at least one target circuit based on at least one of the location of the scanner and the strength of a signal received by the scanner from the at least one RF tag, wherein the scanner is configured to scan an area near a intended installation location of the at least one target circuit and the at least one RF tag, and wherein the controller is configured to locate or confirm the at least one location of the at least one target circuit in response to detecting that the at least one RF tag is near the intended installation location. Attached Figure Description

[0023] This disclosure will be better understood by referring to the accompanying drawings, and the many features and advantages of this disclosure will become apparent to those skilled in the art. The same reference numerals are used in different drawings to indicate similar or identical objects.

[0024] Figure 1 A system of means or sensors, according to some embodiments, is shown, including receiving instructions from a controller to perform a function or providing sensed data to the controller.

[0025] Figure 2 A system including endpoints and radio frequency (RF) tags according to some embodiments is shown.

[0026] Figure 3 A system including endpoints and RF tags registered with a controller is shown according to some embodiments.

[0027] Figure 4 A system including a scanner is shown according to some embodiments, the scanner reading identifiers from RF tags and writing the location and identifiers to a database and / or controller via a side channel.

[0028] Figure 5 A system including a scanner is shown according to some embodiments, the scanner writing a location into an RF tag, and the location and identifier of the RF tag being propagated in-band over a network.

[0029] Figure 6 A system is shown, according to some embodiments, including endpoints and RF tags registered using a scanner and information provided by a controller.

[0030] Figure 7 A method for registering an endpoint or target circuit to a controller is illustrated according to some embodiments. Detailed Implementation

[0031] The devices, sensors, and other components of a heterogeneous system are referred to herein as “endpoints” or “target circuits.” A controller coordinates the operation of interconnected endpoints by transmitting control signals to them and, in some cases, receiving feedback from them. Multiple endpoints (or target circuits) can be implemented using substantially the same circuitry and components, yet still perform different functions depending on their location within the vehicle. For example, taillights mounted on the driver's and passenger's sides of a car can be identical, but perform different functions depending on their mounting location. The driver's side taillight signals the driver that a left turn is being made, while the same endpoint on the passenger side signals the driver that a right turn is being made. As another example, an air conditioning vent mounted near the driver's side seat can be controlled based on feedback from a temperature sensor located near the driver's side seat, while an air conditioning vent mounted near the rear passenger's side seat can be controlled based on feedback from a temperature sensor located near the rear passenger's side seat. Beyond this, the location-dependent functionality of identical endpoints is a characteristic of many systems, including smart homes, smart energy networks, smart cities, in-vehicle networks, and fully automated or “unmanned” factories.

[0032] Control circuitry systems for heterogeneous systems are typically connected to endpoints within the system via a shared medium such as a bus. Endpoints are usually pre-programmed with a unique identifier (or UID) that facilitates communication between the endpoint and the network via the bus. Each endpoint's UID is assigned and registered individually, and the registration process is time- and labor-intensive. For example, in some cases, the endpoint's UID is displayed externally on the endpoint, such as using a barcode embossed on the endpoint. To register an endpoint and its UID, the UID is read from the embossed barcode associated with the endpoint, and then this information is stored in a central database. Radio frequency identifiers (RFID or RF tags) can also be affixed to endpoints, for example, by attaching RF tags. Each RF tag has its own UID. Therefore, when an RF tag is affixed to an endpoint, two distinct, redundant UIDs are associated with the same endpoint (and location).

[0033] When endpoints are installed during system assembly, their locations are registered with the control circuitry system. After installation, the UID associated with an endpoint may be difficult or unreadable. Therefore, the registration of endpoint locations and their corresponding UIDs is performed before endpoint installation or setup. For example, a technician installing taillights on a car can register information in a database indicating that the taillights should be installed on the driver's side. The technician (or other personnel, device, or robot) can then install the taillights on the driver's side. Registering endpoints before installation can lead to errors, as endpoints may be registered in one location, then installed in a different location, or not installed at all. For example, a technician may register information in a database indicating that the taillights should be installed on the driver's side, but the technician (or other personnel, device, or robot) could install the taillights on the passenger side. After installation, errors in endpoint locations, location databases, or endpoint presence are difficult to detect and / or correct. For example, if the view of the barcode on an endpoint is obstructed, the mapping of the endpoint identifier to its location within the system (e.g., a car) cannot be verified after the endpoint has been installed. Typically, the inability to see or access the UIDs of endpoints in the system complicates the maintenance, upgrades, diagnosis, repair, and replacement of endpoints within the system.

[0034] Figure 1-7 A system and method for generating non-redundant network endpoint identifiers are described. The endpoint is coupled to a radio frequency (RF) tag to allow one device to derive its identifier (e.g., UID) from the identifier of another device. In some embodiments, the endpoint obtains the RF tag identifier from the associated RF tag via an interface between the endpoint and the RF tag. The interface may be an integrated circuit bus (Ii) between the RF tag and the radio in the endpoint. 2 C) A wired or wireless interface is used for connection. The RF tag can be implemented as an RFID, Near Field Communication (NFC) device, Ultra Wideband (UWB) device, or any other short-range or long-range wireless device. In some cases, the RF tag encrypts, signs, or authenticates the RF tag identifier before transmitting information representing the RF tag identifier through the interface. The endpoint derives its endpoint identifier from the information representing the RF tag identifier. Deriving the endpoint identifier may include making the endpoint identifier equivalent to the RF tag identifier or applying a predetermined algorithm to the RF tag identifier. In some cases, the endpoint also decrypts, verifies, and / or authenticates the RF tag identifier associated with the signature and / or authentication of the RF tag identifier before generating the endpoint identifier. The endpoint identifier may be transmitted to the controller and / or stored in the endpoint's memory.

[0035] The location of an endpoint can be determined even without a clear line of sight to it. For example, an RF reader can register an endpoint by scanning the environment to locate an RF tag. In response to detecting an RF tag, the RF reader reads the RF tag identifier and determines the location of the RF tag. In some cases, the location of the RF tag is determined based on the location of the RF reader and the signal strength of the signal received by the RF reader from the RF tag. Once the RF reader has located the RF tag associated with the endpoint and determined its location, the RF reader can transmit the RF tag identifier (or information representing the RF tag identifier) ​​and the location to a controller. The controller or other entity derives the endpoint identifier from the RF tag identifier (or information representing the RF tag identifier) ​​and registers the endpoint identifier and the endpoint's location. In some cases, the RF reader provides location information to the RF tag, which can then transmit the location information to the endpoint to register with the controller. In some cases, a tuple including the endpoint identifier and the endpoint location is stored by the endpoint, the RF reader, or a combination thereof.

[0036] An endpoint identifier derived from an RF tag identifier can be used to locate an endpoint after it has been installed, regardless of whether there is a clear line of sight to the installed endpoint. For example, an RF reader can be used to locate or confirm the location of an endpoint by scanning the RF tag of an endpoint at a given location. In response to detecting an RF tag, the RF reader transmits information representing the detected RF tag identifier to the controller. The transmitted information may represent the RF tag identifier, an endpoint identifier derived from the RF tag identifier, or an encrypted or signed version of either identifier. The controller can identify the endpoint at the location based on the RF tag identifier (or the information representing the RF tag identifier), since, as mentioned above, the endpoint identifier is equivalent to or derived from the RF tag identifier using a predetermined algorithm. The controller can then compare the location and the derived endpoint identifier with information in a database to confirm whether the endpoint is in its intended location.

[0037] Figure 1 A system 100, according to some embodiments, is illustrated, comprising means or sensors that receive instructions from a controller to perform a function or provide sensed data to the controller. The means, sensors, and other components of system 100 are implemented using a circuit system and are indicated as target circuits or endpoints 101, 102, 103, 104, 105, 106, collectively referred to herein as “endpoints 101-106” or “target circuits 101-106”. Some embodiments of system 100 are used to implement a vehicle. In this case, endpoints 101-106 represent means including, but not limited to, headlights, taillights, safety / radar sensors, LED light strips, air conditioning control vents, and other types of means or sensors.

[0038] Endpoints 101-106 communicate with controller 110 via a shared medium such as bus 115, for example, by exchanging digital signals on bus 115. Endpoints 101-106 can transmit signals indicating information generated at their respective endpoints to controller 110 via bus 115. For example, endpoints 102 and 105 may represent temperature sensors in the vehicle, and endpoints 102 and 105 can transmit information indicating the sensed temperature to controller 110. Endpoints 101-106 can also receive signals from controller 110 indicating instructions that control the operation of receiving endpoints 101-106. For example, controller 110 can generate and provide signals to illuminate taillights associated with endpoints 101 and 104 in the vehicle represented by system 100. As another example, in response to temperature information provided by endpoints 102 and 105, controller 110 can generate and provide signals to control air conditioning vents associated with endpoints 103 and 106.

[0039] The operation of endpoints 101-106 varies depending on their location within system 100. For example, in an embodiment of system 100 representing a vehicle, endpoints 101 and 104 may represent taillights mounted on the left and right sides of the car, respectively. Endpoints 101 and 104 are implemented using substantially the same circuitry and components, but perform different functions depending on their mounting location within system 100. The taillight associated with endpoint 101 illuminates to signal to the driver that a left turn is being made, and the taillight associated with endpoint 104 illuminates to signal to the driver that a right turn is being made. As another example, an air conditioning vent mounted near the left front seat (associated with endpoint 103) may be controlled based on feedback from a temperature sensor located near the right front seat (associated with endpoint 102), while an air conditioning vent mounted near the left rear seat (associated with endpoint 106) may be controlled based on feedback from a temperature sensor located near the right rear seat (associated with endpoint 105). While some embodiments disclosed herein are discussed in the context of a vehicle, system 100 can represent other systems characterized by location-dependent functionality of endpoints 101-106 implemented using substantially the same circuitry and components. Examples include, but are not limited to, smart homes, smart energy networks, smart cities, in-vehicle networks, and fully automated or “unmanned” factories.

[0040] In the illustrated embodiment, endpoints 101-106 are associated with identifiers 121, 122, 123, 124, 125, and 126 (collectively referred to herein as "identifiers 121-126") that are imprinted or affixed to the exterior of the corresponding endpoints 101-106. Identifiers 121-126, such as identifiers 121, 123, 124, and 126, may be implemented as barcodes. Identifiers 121-126, such as identifiers 122 and 125, may also be implemented as QR codes. Identifiers 121-126 may also be implemented as strings, numeric strings, other symbols, or combinations thereof. Radio frequency identifiers (RFID or RF tags) 131, 132, 133, 134, 135, and 136 are also affixed to endpoints 101-106, for example, by attaching RF tags to the endpoints. Radio frequency identifiers 131, 132, 133, 134, 135, and 136 are collectively referred to as "RF tags 131-136" in this document. RF tags 131-136 are associated with corresponding identifiers such as strings, numeric strings, other symbols, or combinations thereof. For example, RF tags 131-136 can store information representing the corresponding identifier.

[0041] System 100 includes one or more occlusion entities 135, which, when mounted in system 100 with endpoints 101-106, occlude at least a portion of one or more of the occlusion identifiers 121-126. The occlusion entity 135 may include other devices, sensors, or structural elements of system 100. The occlusion entity 135 may also include one or more of the endpoints 101-106, but the endpoints 101-106 are... Figure 1 The occlusion entity 135 is not depicted as obscuring identifiers 121-126 associated with other endpoints 101-106. This obscuring entity makes it difficult or impossible to read the obscured identifiers, such as identifier 126 of endpoint 106. Therefore, it may be difficult or impossible to determine the identity of endpoints 101-106 after installation, making it difficult or impossible to register, verify, or confirm the location of one or more of endpoints 101-106 after installation.

[0042] Identifiers for endpoints 101-106 are generated based on the identifiers associated with RF tags 131-136. RF tags 131-136 and endpoints 101-106 are connected via corresponding interfaces 141, 142, 143, 144, 145, and 146, collectively referred to herein as "interfaces 141-146". Some embodiments of interfaces 141-146 are implemented as an integrated circuit bus (I-IC) between RF tags 131-136 and the radios in endpoints 101-106. 2C) Connect to a wired or wireless interface. In some embodiments, the identifier is considered a "non-redundant" identifier because the same identifier is used to indicate both endpoints 101-106 and their corresponding RF tags 131-136. A non-redundant identifier is generated by transmitting information identifying endpoints 101-106 or their corresponding RF tags 131-136 to the other of the endpoints and RF tags. For example, endpoint 101 can transmit identification information to RF tag 131 via interface 141, or RF tag 131 can transmit identification information to endpoint 101 via interface 141.

[0043] Non-redundant information (e.g., a unique identifier, UID) identifying the endpoint or RF tag can be derived from information transmitted via the interface. For example, endpoint 101 can derive its UID from identification information transmitted by RF tag 131 via interface 141. The information identifying the endpoint or RF tag is then stored. In some embodiments, non-redundant identification information is derived by making the non-redundant information equivalent to the information received via interfaces 141-146. Non-redundant identification information can also be derived or generated by applying a predetermined algorithm to the information received via interfaces 141-146. In some embodiments, information transmitted via interfaces 141-146 is first encrypted, signed, or associated with other authentication information before being transmitted via interfaces 141-146. Therefore, the receiving entity can first decrypt, verify the signature, or authenticate the information received via interfaces 141-146 before deriving the non-redundant identification information.

[0044] The location of endpoints 101-106 can be detected or determined based on non-redundant identification information. In some embodiments, the location and non-redundant identification information of endpoints 101-106 are registered in a database 150. In the illustrated embodiment, the database 150 is connected to the controller 110. However, in some embodiments, the database 150 is integrated within the controller 110 or connected to the controller 110 via a bus 115. The location of endpoints 101-106 can be determined by detecting corresponding RF tags 131-136 using a device such as a scanner. For example, in response to detecting that one of the RF tags 131-136 is near the scanner, the location of a corresponding endpoint among endpoints 101-106 is determined based on the location of the scanner and the strength of the signal received by the scanner. The correct installation of endpoints 101-106 can be confirmed or verified after installation. In some embodiments, the scanner is used to scan the area near the expected installation location of one of the endpoints 101-106, which is located (or its location is confirmed) in response to detecting that a corresponding RF tag among the RF tags 131-136 is near the expected installation location.

[0045] Figure 2A system 200, including an endpoint 205 and an RF tag 210, is illustrated according to some embodiments. System 200 can represent... Figure 1 As shown, part of system 100, in this case, endpoint 205 represents Figure 1 One or more of the endpoints 101-106 shown, and RF tag 210 indicates Figure 1 One or more of the RF tags 131-136 shown. Connection 215 supports communication between endpoint 205 and RF tag 210. Connection 215 can be implemented as, for example, I 2 The connection of C can be wired, or implemented as a wireless or over-the-air connection. In some embodiments, endpoint 205 and RF tag 210 are implemented in a single integrated circuit or device.

[0046] Endpoint 205 includes an interface 220 to connection 215. Endpoint 205 also includes circuitry for implementing processor 222 and, in some embodiments, memory 224 configured to store instructions to be executed by processor 222, information or data provided as input to processor 222, and information or data representing the results of operations performed by processor 222. Endpoint 205 also includes an interface 226 that allows endpoint 205 to communicate with network 230. Interface 226 may be a wired interface supporting communication with network 230 via a wired connection, or a wireless interface supporting wireless communication with network 230.

[0047] RF tag 210 includes an interface 232 supporting wired or wireless communication with endpoint 205 via connection 215. RF tag 210 supports wireless transmission capabilities via antenna 234, which can be used as part of interface 232 if connection 215 is established wirelessly. In some cases, RF tag 210 can selectively enable or disable wireless transmission. Some embodiments of RF tag 210 include circuitry for implementing processor 236 and memory 238, the memory 238 being configured to store instructions to be executed by processor 236, information or data provided as input to processor 236, and information or data representing the results of operations performed by processor 236. For example, processor 236 may include circuitry for implementing a security element that performs encryption, generates authentication information, generates signatures, or combinations thereof.

[0048] The non-redundant identifier of endpoint 205 or RF tag 210 is created (or derived or generated) based on information in the other of endpoint 205 or RF tag 210. Information identifying one of endpoint 205 or RF tag 210 is transmitted to the other of endpoint 205 and RF tag 210 via connection 215. In response, information identifying the other of endpoint 205 and RF tag 210 is derived from the information received via connection 215. In some embodiments, endpoint 205 reads the identification information (e.g., UID) of RF tag 210 from memory 238 in RF tag 210. Endpoint 205 then derives its UID from the UID of RF tag 210. The UID of endpoint 205 can be set to be equivalent to the UID of RF tag 210, or the UID of endpoint 205 can be set to be equivalent to the value derived from the UID of the RF tag using a predetermined algorithm. Endpoint 205 then transmits its (non-redundant) UID to network 230. In some embodiments, endpoint 205 stores a shadow copy of its UID in its memory 224.

[0049] Figure 3 A system 300, according to some embodiments, is illustrated, including endpoints 301 and 302 registered to a controller 315 and RF tags 311 and 312. System 300 may represent... Figure 1 As shown, this is a part of system 100, in which endpoints 301 and 302 represent Figure 1 Two or more of the endpoints 101-106 shown, RF tags 311, 312 indicate Figure 1 Two or more of the RF tags 131-136 shown, and controller 315 indicates Figure 1 The controller 110 is shown. Some embodiments of endpoints 301 and 302 are implemented using substantially the same circuitry and components, and are therefore substantially the same target circuitry. Endpoints 301 and 302 and RF tags 311 and 312 are connected to each other via interfaces 321 and 322, and endpoints 301 and 302 are connected to controller 315 via interfaces 331 and 332 and network 335.

[0050] Controller 315 includes a registrar interface 340 that allows controller 315 to receive registration information associated with endpoints 301, 302, such as information indicating the location of endpoints 301, 302. In the illustrated embodiment, registrar interface 340 receives information associated with endpoints 301, 302, such as location information, via side channel 345. Therefore, registrar interface 340 can receive information from technicians, third parties, or other sources. Controller 315 also includes circuitry for implementing processor 342 and, in some embodiments, memory 344 configured to store instructions to be executed by processor 342, information or data provided as input to processor 342, and information or data representing the results of operations performed by processor 342. Controller 315 is also configured to communicate with network 335 such that controller 315 can receive registration information from endpoints 301, 302.

[0051] To register endpoints 301 and 302 with controller 315, endpoints 301 and 302 read identifiers from corresponding RF tags 311 and 312. The identifiers can be in the form of Internet Protocol (IP) addresses, Media Access Control (MAC) addresses, Control Local Area Network (CAN) addresses, etc. In some cases, in response to endpoints 301 and 302 connecting to controller 315 via network 335, endpoints 301 and 302 read the identifiers from RF tags 311 and 312. Endpoints 301 and 302 can decrypt or authenticate the identifiers if the identifiers have been encrypted or if authentication information has been included in the information received from the corresponding RF tags 311 and 312. Endpoints 301 and 302 derive their identifiers from the received information and, in some cases, store a shadow copy of their identifiers. Then, endpoints 301 and 302 transmit information representing their identifiers to controller 315.

[0052] Controller 315 associates the identifiers of endpoints 301 and 302 with additional information such as endpoint type, physical location of the endpoints, or combinations thereof. This additional information is received via a side channel connected to the registrar interface 340. In some embodiments, the additional information is provided to controller 315 as part of the installation process for endpoints 301 and 302. For example, the location information of endpoint 301 may be provided to controller 315 via registrar interface 340 before or in response to the installation of endpoint 301. Controller 315 then stores the registered identifiers and additional information in memory 344, for example, in a database containing pairs of registered identifiers and additional information.

[0053] Figure 4A system 400, according to some embodiments, is illustrated, including a scanner 418 that reads identifiers from RF tags 411, 412 and writes the location and identifiers to a database and / or controller 415 via a side channel. System 400 includes endpoints 401, 402 and may represent... Figure 1 As shown, this is a part of system 100, in which endpoints 401 and 402 represent Figure 1 Two or more of the endpoints 101-106 shown, RF tags 411, 412 indicate Figure 1 Two or more of the RF tags 131-136 shown, and controller 415 indicates Figure 1 The controller 110 is shown. Some embodiments of endpoints 401 and 402 are implemented using substantially the same circuitry and components, and are therefore substantially the same target circuitry. Endpoints 401 and 402 and RF tags 411 and 412 can be connected to each other via interfaces 421 and 422, but in some embodiments, endpoints 401 and 402 are not connected to RF tags 411 and 412. Endpoints 401 and 402 are connected to controller 415 via interfaces 431 and 432 and network 435.

[0054] Scanner 418 is configured to read identifiers 441 and 442 using signals transmitted over the air by RF tags 411 and 412. In some embodiments, identifiers 441 and 442 are radio frequency identifiers (RFID). Although Figure 4 A single scanner 418 is shown, but multiple scanners can also be used to scan identifiers 441, 442 associated with RF tags 411, 412, and... Figure 4 Other identifiers of other RF tags not shown. If RF tags 411, 412 encrypt identifiers 441, 442, or generate signatures or authentication information associated with identifiers 441, 442, then scanner 418 can decrypt the received information, verify the signatures associated with identifiers 441, 442, authenticate identifiers 441, 442 based on the authentication information, or perform other actions. As discussed herein, these operations can also be performed at other entities including endpoints 401, 402 and controller 415.

[0055] Scanner 418 uses signals transmitted via the registrar interface 445 in controller 415 to register identifiers 441 and 442 of RF tags 411 and 412. Scanner 418 also registers other information with controller 415 associated with endpoints 401 and 402, RF tags 411 and 412, or combinations thereof. For example, scanner 418 may determine the location of RF tags 411 and 412 and / or endpoints 401 and 402 based on the location of scanner 418 (when reading identifiers) and the strength of signals received from RF tags 411 and 412. In response to receiving information from scanner 418, controller 415 stores information representing identifiers 441 and 442, as well as other information such as location information. Some embodiments of controller 415 may associate identifiers 441 and 442 with corresponding identifiers of endpoints 401 and 402, such that identifiers 441 and 442 are used as non-redundant identifiers identifying the corresponding endpoints 401 and 402. For example, identifiers 441 and 442 can be MAC addresses known to controller 415.

[0056] Some embodiments of endpoints 401 and 402 can read identifiers 441 and 442 from corresponding RF tags 411 and 412. For example, if endpoint 401 is connected to RF tag 411, endpoint 401 can read identifier 441 from RF tag 411 via interface 421. Information representing identifiers 441 and 442 can also be provided to endpoints 401 and 402 by scanner 418, controller 415, or a combination thereof. Some embodiments of endpoints 401 and 402 store shadow copies of the corresponding identifiers 441 and 442 in their memory (for clarity, ...). Figure 4 (Not shown in the image).

[0057] Figure 5 A system 500 according to some embodiments is shown, including a scanner 518 that writes locations into RF tags 511, 512, and the locations and identifiers of the RF tags 511, 512 are propagated in-band via a network 535. The system 500 includes endpoints 501, 502 and can represent... Figure 1 As shown, this is a part of system 100, in which endpoints 501 and 502 represent Figure 1 Two or more of the endpoints 101-106 shown, RF tags 511, 512 indicate Figure 1 Two or more of the RF tags 131-136 shown, and controller 515 indicates Figure 1The controller 110 is shown. Some embodiments of endpoints 501 and 502 are implemented using substantially the same circuitry and components, and are therefore substantially the same target circuitry. Endpoints 501 and 502 and RF tags 511 and 512 are connected to each other via interfaces 521 and 522. Endpoints 501 and 502 are connected to controller 515 via interfaces 531 and 532 and network 535.

[0058] As this article is about Figure 4 As discussed herein, scanner 518 is configured to read identifiers 541 and 542 using signals transmitted over the air by RF tags 511 and 512. Scanner 518 can determine (or read) information associated with RF tags 511 and 512. As discussed herein, information associated with endpoints 501 and 502 may include endpoint type, physical location of the endpoints, or a combination thereof. For example, scanner 518 can determine the location of RF tags 511 and 512 based on the location of scanner 518 (when reading the identifiers) and the strength of the signals received from RF tags 511 and 512.

[0059] Figure 5 The system 500 shown is Figure 4 The system 400 shown differs from the one described because scanner 518 provides information associated with endpoints 501 and 502 to the corresponding RF tags 511 and 512. For example, scanner 518 can read identifier 541 from RF tag 511, and then determine the location of RF tag 511 based on the position of scanner 518 when reading identifier 541 and the strength of the received signal. Scanner 518 provides the location information to RF tag 511, which can store the location information and the corresponding identifier 541 in its local memory.

[0060] Endpoints 501 and 502 read identifiers 541 and 542 from their corresponding RF tags 511 and 512. For example, during initial startup of endpoint 501, endpoint 501 reads identifier 541 from RF tag 511. As discussed herein, some embodiments of endpoints 501 and 502 can decrypt, verify, confirm, or authenticate information received from RF tags 511 and 512, including information representing identifiers 541 and 542. Some embodiments of endpoints 501 and 502 store copies of identifiers 541 and 542 (or other non-redundant identifiers derived from identifiers 541 and 542) and corresponding information including location information. Endpoints 501 and 502 also transmit identifier / information pairs to controller 515, which stores the information in a memory or database.

[0061] Figure 6A system 600, according to some embodiments, is illustrated, including endpoints 601, 602 and RF tags 611, 612 registered using information provided by controller 615. System 600 may represent... Figure 1 As shown, this is a part of system 100, in which endpoints 601 and 602 represent Figure 1 Two or more of the endpoints 101-106 shown, RF tags 611, 612 indicate Figure 1 Two or more of the RF tags 131-136 shown, and controller 615 indicates Figure 1 The controller 110 is shown. Some embodiments of endpoints 601 and 602 are implemented using substantially the same circuitry and components, and are therefore substantially the same target circuitry. Endpoints 601 and 602 and RF tags 611 and 612 are connected to each other via interfaces 621 and 622. Endpoints 601 and 602 are connected to controller 615 via interfaces 631 and 632 and network 635.

[0062] In the illustrated embodiment, controller 615 provides information associated with endpoints 601 and 602 to scanner 618 (or multiple scanners). Endpoint information may include endpoint type, physical location of the endpoint, or a combination thereof. Scanner 618 may read identifiers 641 and 642 from RF tags 611 and 612, then use identifiers 641 and 642 to select the corresponding endpoint information and provide that information to the appropriate RF tags 611 and 612. For example, if controller 615 provides endpoint information for both endpoints 601 and 602 to scanner 618, scanner 618 may read identifier 641 of RF tag 611, determine that RF tag 611 is associated with endpoint 601, and then provide the endpoint information for endpoint 601 to RF tag 611, which stores the endpoint information in its local memory.

[0063] Endpoints 601 and 602 can read identifiers 641 and 642 from their corresponding RF tags 611 and 612. As discussed herein, identifiers 641 and 642 are equivalent to or used to derive non-redundant identifiers for endpoints 601 and 602. In some embodiments, endpoint information is provided to scanner 618 before endpoints 601 and 602 are installed or started. In this case, in response to the installation or start of endpoints 601 and 602, endpoints 601 and 602 can read endpoint information and corresponding identifiers 641 and 642 from their corresponding RF tags 611 and 612. Endpoints 601 and 602 also register the corresponding identifiers 641 and 642 and associated endpoint information with controller 615, which stores the information in local memory or a database.

[0064] Figure 7A method 700 for registering an endpoint or target circuit to a controller is illustrated according to some embodiments. Method 700 in... Figure 1 The system 100 shown Figure 2 The system 200 shown Figure 3 The system 300 shown Figure 4 The system 400 shown Figure 5 The system 500 shown and Figure 6 The system 600 shown is implemented in some embodiments.

[0065] At box 705, identifier information is transmitted between an endpoint and an RF tag in the system. As discussed herein, the identifier information may be transmitted via a wired or wireless interface between the endpoint and the RF tag, or via other entities including a scanner, controller, network, or a combination thereof.

[0066] At box 710, an endpoint identifier is generated based on the transmitted information, which may be referred to as a non-redundant endpoint identifier. For example, if the identifier of the RF tag is transmitted to the endpoint, the endpoint identifier may be equivalent to the identifier of the RF tag, or the endpoint identifier may be derived from the identifier of the RF tag using a predetermined algorithm.

[0067] At box 715, obtain the endpoint's location information. Location information can be obtained using a scanner, provided by the controller, manually entered, or a combination thereof. Other information associated with the endpoint can also be obtained.

[0068] At box 720, register the endpoint identifier and location information (and other information, if available) with the controller. For example, the controller may store the endpoint identifier and location information in local memory or a database. The information received and stored at the controller may also include other information associated with the endpoint, such as the endpoint type.

[0069] Embodiments of the systems and methods described herein can offer numerous advantages over conventional endpoint registration techniques. Endpoints operating according to the systems and methods disclosed herein do not require pre-programming with identifiers such as UIDs because their unique identifiers can be derived from attached RF tags. These derived unique identifiers can then be used to support endpoint logistics, including device management, procurement, transportation, installation, maintenance, and lifespan tracking. The unique identifier of an endpoint can be wirelessly read after installation for sanity checks, quality assurance, network registration, etc. Endpoint maintenance and / or replacement can be tracked, for example, by reading the RF tag with a handheld scanner. Embodiments of the registration process discussed herein can be used to register or re-register installed or replaced endpoints with the network. Network endpoint authentication can be based on a unique identifier, which can be encrypted, signed, or appended to authentication information to enhance security, and network integrity protection can be derived from the authenticated endpoint. Embodiments of the systems and methods discussed herein can also be used to perform complete physical and logical location discovery of endpoints.

[0070] In some embodiments, certain aspects of the above-described techniques are implemented by one or more processors of a processing system executing software. The software includes one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer-readable storage medium. The software may include instructions and certain data that, when executed by one or more processors, manipulate the one or more processors to perform one or more aspects of the above-described techniques. The non-transitory computer-readable storage medium may include, for example, disk or optical disk storage devices, solid-state storage devices such as flash memory, cache memory, random access memory (RAM), or other non-volatile memory devices. The executable instructions stored on the non-transitory computer-readable storage medium may be source code, assembly language code, object code, or other instruction formats that are interpreted or otherwise executable by one or more processors.

[0071] Computer-readable storage media can include any storage medium or combination of storage media that can be accessed by a computer system during use to provide instructions and / or data to the computer system. Such storage media can include, but are not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-ray disc), magnetic media (e.g., floppy disk, magnetic tape, or magnetic hard disk), volatile memory (e.g., random access memory (RAM) or cache memory), non-volatile memory (e.g., read-only memory (ROM) or flash memory), or microelectromechanical systems (MEMS) based storage media. Computer-readable storage media can be embedded in a computing system (e.g., system RAM or ROM), fixedly attached to a computing system (e.g., magnetic hard disk), removably attached to a computing system (e.g., optical disc or USB-based flash memory), or coupled to a computer system via a wired or wireless network (e.g., network accessible storage device (NAS)).

[0072] It should be noted that not all of the activities or elements described in the general description above are necessary; a particular activity or element may not be required as part of a particular activity or device, and one or more additional activities or elements may be performed or included in addition to those described. Furthermore, the listed order of activities is not necessarily the order in which the activities are performed. Concepts have been described with reference to specific embodiments. However, those skilled in the art will understand that various modifications and changes can be made without departing from the scope of this disclosure as set forth in the following claims. Therefore, the specification and figures should be considered illustrative rather than restrictive, and it is intended that all such modifications be included within the scope of this disclosure.

[0073] The benefits, other advantages, and solutions to the problems have been described above with respect to specific embodiments. However, these benefits, advantages, solutions to the problems, and any features that may make any benefit, advantage, or solution occur or become more apparent should not be construed as essential, necessary, or fundamental features of any or all claims. Furthermore, the specific embodiments disclosed above are merely illustrative, as the disclosed subject matter can be modified and practiced in different but equivalent ways, as will be apparent to those skilled in the art who have benefited from the teachings herein. No limitation is intended to be made on the details of the constructions or designs shown herein other than those described in the appended claims. Therefore, it will be apparent that changes or modifications can be made to the specific embodiments disclosed above, and all such changes are considered to be within the scope of the disclosed subject matter. Therefore, the protection sought herein is as set forth in the appended claims.

Claims

1. A method characterized by, comprising: transmitting first information identifying a first one of a target circuit or a radio frequency, RF, tag to a second one of the target circuit or the RF tag; determining second information identifying the second one of the target circuit or the RF tag from the transmitted first information; and storing the second information.

2. The method of claim 1, wherein, Transmitting the first information includes transmitting the first information over at least one of a wired interface or a wireless interface between the target circuit and the RF tag.

3. The method of claim 1, wherein, Transmitting the first information includes transmitting first information identifying the RF tag to the target circuit, and wherein deriving the second information includes deriving second information identifying the target circuit based on the first information identifying the RF tag.

4. The method of claim 3, wherein, Deriving the second information includes one of: equating the second information to the first information; or applying a predetermined algorithm to the first information to generate the second information.

5. The method of claim 1, wherein, further comprising: prior to transmitting the first information, performing at least one of: encrypting the first information, signing the first information, or generating authentication information for the first information; and prior to deriving the second information, performing at least one of: decrypting the encrypted first information, verifying a signature on the first information, or authenticating the first information.

6. An apparatus, comprising: comprising: a radio frequency, RF, tag; and a target circuit coupled to the RF tag by an interface, the interface configured to transmit first information identifying a first one of the target circuit or the RF tag to a second one of the target circuit or the RF tag, and wherein the second one of the target circuit or the RF tag is configured to derive second information identifying the second one of the target circuit and the RF tag from the transmitted first information. The interface includes at least one of a wired interface between the target circuit and the RF tag and a wireless interface between the target circuit and the RF tag.

7. The apparatus of claim 6, wherein, The interface is configured to transmit first information identifying the RF tag to the target circuit, and wherein the target circuit is configured to derive the second information identifying the target circuit based on the first information identifying the RF tag.

8. The apparatus of claim 6, wherein, comprising:

9. A system, characterized by at least one target circuit coupled to at least one radio frequency, RF, tag by at least one interface, the at least one interface configured to transmit first information identifying a first one of the at least one target circuit or the at least one RF tag to a second one of the at least one target circuit and the at least one RF tag, and wherein the second one of the at least one target circuit or the at least one RF tag is configured to derive second information identifying the second one of the at least one target circuit and the at least one RF tag from the transmitted first information; and a controller configured to provide control signals to the at least one target circuit based on at least one location of the at least one target circuit. ​ 10. The system of claim 9, wherein, The at least one interface includes at least one of a wired interface between the at least one target circuit and the at least one RF tag and a wireless interface between the at least one target circuit and the at least one RF tag.

Images