Configurable access controllers and access control systems

Abstract

An access control device and a system including the access control device are described herein. The access control device may be configurable / reconfigurable so that the access control device can communicate with a variety of keyless entry systems. Such keyless entry systems may control access to a vehicle, building, facility, container, or other target resource where access is controlled by a device for securing, for example, doors, windows, gates, and covers, but not limited thereto.

Description

[0001] Priority declaration

[0002] This application claims the benefit of the filing date of U.S. Provisional Patent Application No. 62 / 866,542, filed on June 25, 2019, and entitled “Configurable Access Controller, and Related Systems, Methods and Devices,” and claims the benefit of the filing date of pending U.S. Patent Application Serial No. 16 / 654,807, filed on October 16, 2019, and entitled “Configurable Access Controller, and Related Systems, Methods and Devices,” the disclosures of each of which are hereby incorporated by reference herein in their entirety. Technical Field

[0003] Embodiments disclosed herein relate generally to access control systems, and more particularly, some embodiments relate to a configurable / reconfigurable access controller that can be used with a variety of different access control systems. Background Art

[0004] A keyless entry system is an access control system that uses an electronic key instead of a traditional mechanical key. In a typical arrangement, when an electronic key associated with the system is within a predetermined distance of the access control system, the user can push a button or manipulate the electronic key in some other predefined manner associated with locking or unlocking. This causes the electronic key to wirelessly transmit a coded message that includes a unique identifier associated with the electronic key. If the access control system recognizes the coded message, the access control system controls the electronic lock to lock or unlock (as appropriate).

[0005] An electronic key is typically a standalone device (e.g., a processor, a battery, a transceiver contained in a housing that may or may not have a button, but is not limited thereto) and is removable, meaning that the electronic key may be carried, for example, in a pocket or purse away from an access control system. Additionally or alternatively, to press a button on the electronic key, a user may press a button connected to the access control system (e.g., on a door handle, but is not limited thereto). In an envisioned use case, when a user presses a button connected to an access control system of a car, the access control system sends an interrogation signal that powers on the electronic key and causes the electronic key to send a coded message. As non-limiting examples, keyless entry systems are used to lock / unlock doors and / or trunks of vehicles; and lock / unlock doors, windows, and / or elevators of buildings (residential and commercial). BRIEF DESCRIPTION OF THE DRAWINGS

[0006] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which the element is first introduced.

[0007] Figure 1 A block diagram of a system for configuring / reconfiguring an access controller to operate with a keyless entry system is shown according to one or more embodiments.

[0008] Figure 2 A flow diagram of a process for configuring / reconfiguring a configurable access controller is shown in accordance with one or more embodiments.

[0009] Figure 3 A block diagram of a system including a configurable access controller configured to communicate with a keyless entry system is shown according to one or more embodiments.

[0010] Figure 4 An embodiment of a process for controlling a keyless entry system using a configurable access controller is shown in accordance with one or more embodiments.

[0011] Figure 5 A block diagram of a system for unlocking a vehicle trunk access-controlled by a keyless entry system using a configurable access controller installed on the vehicle is shown according to one or more embodiments.

[0012] Figure 6 A schematic diagram showing a configuration file according to one or more embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0013] In the following detailed description, reference is made to the accompanying drawings which form a part of the present disclosure, and in the accompanying drawings are shown by way of example specific examples of embodiments in which the present disclosure may be implemented. These embodiments are described in sufficient detail to enable one of ordinary skill in the art to practice the present disclosure. However, other embodiments may be utilized, and changes in structure, material, and process may be made without departing from the scope of the present disclosure.

[0014] The illustrations presented herein are not intended to be actual views of any particular method, system, device, or structure, but are merely idealized representations for describing embodiments of the present disclosure. The drawings presented herein are not necessarily drawn to scale. For the convenience of the reader, similar structures or components in the various drawings may retain the same or similar numbering; however, the similarity of numbering does not mean that the structures or components must be identical in size, composition, configuration, or any other attribute.

[0015] The following description may include examples to help those skilled in the art practice the embodiments disclosed in the present invention. The use of the terms "exemplary", "by way of example" and "for example" means that the relevant description is illustrative, and although the scope of the present disclosure is intended to cover examples and legal equivalents, the use of such terms is not intended to limit the scope of the embodiments or the present disclosure to the specified components, steps, features or functions, etc.

[0016] It should be readily understood that the components of the embodiments as generally described herein and shown in the accompanying drawings may be arranged and designed in a variety of different configurations. Therefore, the following description of various embodiments is not intended to limit the scope of the present disclosure, but is merely representative of various embodiments. Although various aspects of the embodiments may be presented in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

[0017] In addition, the specific embodiments shown and described are examples only and should not be construed as the only way to implement the present disclosure, unless otherwise specified herein. Elements, circuits, and functions can be shown in block diagram form so as not to obscure the present disclosure with unnecessary details. On the contrary, the specific embodiments shown and described are exemplary only and should not be construed as the only way to implement the present disclosure, unless otherwise specified herein. In addition, the partitioning of logic between block definitions and individual blocks is an example of a specific embodiment. It will be apparent to those of ordinary skill in the art that the present disclosure can be practiced through many other partitioning solutions. In most cases, details about timing considerations, etc. have been omitted, where such details are not required to obtain a complete understanding of the present disclosure and are within the capabilities of those of ordinary skill in the relevant art.

[0018] Those of ordinary skill in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced throughout this specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof. For clarity of presentation and description, some of the accompanying drawings may show signals as single signals. Those of ordinary skill in the art will appreciate that a signal may represent a signal bus, where the bus may have a variety of bit widths, and the present disclosure may be implemented on any number of data signals, including a single data signal.

[0019] The various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or implemented with a general purpose processor, a special purpose processor, a digital signal processor (DSP), an integrated circuit (IC), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof designed to implement the functions described herein. A general purpose processor (which may also be referred to herein as a "host processor" or simply "host") may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. A general purpose computer including a processor is considered a special purpose computer when the general purpose computer is configured to execute computing instructions (e.g., software code) associated with the embodiments disclosed herein.

[0020] Embodiment can be described according to the process that is depicted as flow chart, flow diagram, structure diagram or block diagram.Although flow chart can describe operation action as sequential process, many of these actions can be performed in another sequence, in parallel or substantially simultaneously.In addition, the order of action can be rearranged.Process can correspond to method, thread, function, procedure, subroutine or subprogram without limitation.In addition, the method disclosed herein can be realized by hardware, software or both.If realized in software, these functions can be stored or transmitted to computer readable medium as one or more instructions or codes.Computer readable medium includes both computer storage medium and communication medium, and this communication medium includes any medium that is conducive to transferring computer program from one location to another location.

[0021] Unless such limitations are explicitly stated, any reference to elements herein using names such as "first," "second," etc. does not limit the number or order of those elements. Instead, these names may be used herein as a convenient method of distinguishing between two or more elements or instances of elements. Thus, reference to a first element and a second element does not mean that only two elements can be employed there, or that the first element must precede the second element in some manner. Furthermore, unless otherwise indicated, a group of elements may include one or more elements.

[0022] As used herein, the term "substantially" in reference to a given parameter, attribute, or condition refers to and includes the degree to which a person of ordinary skill in the art would understand that the given parameter, attribute, or condition is satisfied with a small degree of variance, such as, for example, within acceptable manufacturing tolerances. By way of example, depending on the specific parameter, attribute, or condition that is substantially satisfied, the parameter, attribute, or condition may be satisfied by at least 90%, at least 95%, or even at least 99%.

[0023] As used herein, "configurable" means both configurable and reconfigurable.

[0024] A keyless entry system (KES) is typically configured for a specific communication protocol and is tuned to specific radio frequency (RF) characteristics. Thus, an electronic key sends a message to the KES according to the communication protocol of the KES, and the electronic key wirelessly transmits the message on a carrier signal that exhibits the RF characteristics of the KES. A KES that uses a specific communication protocol and is tuned to specific RF characteristics of a carrier signal should not respond to messages from an electronic key that sends messages using a different communication protocol or different RF characteristics. Therefore, unless the electronic key sends a message to the KES using the communication protocol and RF characteristics of the KES, the KES will not learn the identifier of the electronic key (in the case of initially setting up the electronic key to work with the KES), nor will the KES respond to control messages (e.g., lock, unlock, open the door, but not limited to) sent by a known electronic key.

[0025] In order to implement a robust electronic key that can operate with a KES that implements various communication protocols and is tuned to various RF characteristics, one option for the electronic key is to include a memory that is large enough to store the configuration information of multiple KES. However, even with a large memory, such an electronic key is still limited to operating with those KESs for which the configuration information is stored. Some or all of the stored configuration information may eventually become obsolete for the corresponding KES. In addition, a large memory may require physical space for the memory to reside and / or expensive high-density memory.

[0026] One or more embodiments generally relate to a configurable access controller configured to interface with a keyless entry system, and a system for configuring and / or operating the access controller so that, as non-limiting examples, an authorized party can access a vehicle, building, container, facility, room, or other access-controlled resource (each referred to herein as a "target resource" for ease of description, but not limitation), where access to the target resource is controlled by the keyless entry system.

[0027] Figure 1 and Figure 3 A block diagram of a system including a configurable access controller is shown according to one or more embodiments.

[0028] Figure 1 A block diagram of an embodiment of a system 100 for configuring a configurable access controller (eg, configurable access controller 102) to operate with a keyless entry system (eg, keyless entry system 128) is shown in accordance with one or more embodiments. Figure 1 In the scenario shown, the configurable access controller 102 has not yet been configured to communicate with the keyless entry system 128 , and the keyless entry system 128 has not yet learned the configurable access controller 102 .

[0029] Figure 3 A block diagram of an embodiment of a system 300 is shown that includes a configurable access controller (e.g., configurable access controller 302) that has been configured to communicate with a keyless entry system (e.g., keyless entry system 328), and more specifically, to send a control message (e.g., control message 332) to the keyless entry system (e.g., to keyless entry system 328), according to one or more embodiments. Figure 3 In the scenario shown, the configurable access controller 302 has been configured to communicate with the keyless entry system 328 , and the keyless entry system 328 has learned the identifier of the configurable access controller 302 .

[0030] Figure 1 and Figure 3 The envisioned scenario involves access to a vehicle, but as noted above, the disclosed embodiments are not so limited and may be used, for example, to access any target resource, such as, but not limited to, buildings, containers, and fenced areas.

[0031] exist Figure 1 In the illustrated embodiment, system 100 includes a configurable access controller 102 , a keyless entry system 128 , a setup device 126 , and a configuration server 120 .

[0032] The setup device 126 may generally be configured to enable a user to configure the configurable access controller 102 so that the configurable access controller 102 can communicate with the keyless entry system 128. As non-limiting examples, the user may be a person, a controller, an automated software process, an artificial intelligence (AI) process, and combinations thereof. As non-limiting examples, the setup device 126 may be a general-purpose computing device such as a smartphone, a tablet computer, a laptop computer, a desktop computer, or a wearable device configured to perform various functions of the disclosed embodiments of the setup device 126, but is not limited thereto.

[0033] like Figure 1 As shown, the setup device 126 and the configuration server 120 may be configured to communicate with each other via a communication link including the communication network 130. The setup device 126 may also be configured to communicate with the configurable access controller 102 via another communication link. The setup device 126 and the configurable access controller 102 may be configured to communicate using any of a variety of wireless communication protocols including Bluetooth, near field communication, cellular communication, and WiFi, and / or any of a variety of wired communication protocols such as, but not limited to, one or more versions and form factors of Universal Serial Bus (USB), FireWire, optical data transmission, Ethernet, and High Definition Multimedia Interface.

[0034] The setup device 126 may be configured to provide prompts (e.g., a graphical user interface (GUI) provided at a display of the setup device 126, the GUI including one or more GUI elements for providing instructions and for inputting information (e.g., fields, menus, but not limited thereto)) to the user to enter information that may be used to identify a target resource (e.g., target identification information) and / or the keyless entry system 128. The setup device 126 may be configured to generate requests including the target identification information entered at the setup device 126 and send these requests to the configuration server 120. These requests may be requests for a configuration file that defines rules for communicating with the keyless entry system.

[0035] exist Figure 1 In the embodiment, the setup device 126 sends a request 136 for a configuration file 132 to the configuration server 120 via the communication network 130. The request 136 may include any information suitable for identifying the keyless entry system 128 so that the configuration server 120 can search for and retrieve a configuration file (here, the configuration file 132) associated with the keyless entry system 128. The setup device 126 is further configured to forward the received configuration file 132 to the configurable access controller 102.

[0036] In a vehicle access scenario, the information used to identify the keyless entry system 128 may include a vehicle brand and / or a vehicle model. In another embodiment, the information used to identify the keyless entry system 128 may include a specific identifier that identifies the brand or model of the keyless entry system 128.

[0037] The configuration server 120 may generally be configured to store the keyless entry system profiles 124 and associate the keyless entry system profiles 124 with the customer accounts 122. As a non-limiting example, upon receiving a request for a profile 132 (theoretically, one of the profiles of the keyless entry system profiles 124) along with target identification information, the configuration server 120 may be configured to search for and retrieve a specific keyless entry system profile 132 associated with the target identification information from the stored keyless entry system profiles 124. The configuration server 120 may be configured to send the retrieved keyless entry system profile 132 to the setup device 126. In various embodiments, the user may also enter customer profile information at the setup device 126 and send the customer profile information to the configuration server 120. When the configuration server 120 determines that there is no customer account in the customer accounts 122 for the provided customer profile information, the configuration server 120 may create a new customer account using the customer profile information and the keyless entry profile 132 associated with the new customer account. When the configuration server 120 determines that a customer account exists in the customer accounts 122 for the provided customer profile information, the configuration server 120 may add the associated keyless entry profile 132 from the stored keyless entry system profiles 124 with the existing customer account.

[0038] In one embodiment, the corresponding keyless entry system profiles 124 may contain RF characteristics and communication (COM) protocols associated with keyless entry systems used with various makes, models, and years of vehicles, and the customer accounts 122 may store the makes, models, and years of vehicles associated with a particular customer account.

[0039] The configurable access controller 102 may include a memory 104, a processor 114, an encryption element 116, and an RF transceiver 118. The memory 104 may be configured to store various modules, including one or more of an application 106, an installation program 108, and a communication module. Figure 1 In the envisioned scenario, no communication module is installed at the configurable access controller 102, but space in the memory is reserved as the COM protocol space 110. Space is also reserved to store RF characteristics, here RF characteristics space 112. Figure 1Only two code spaces are shown in the figure to highlight the functional independence, but it is worth noting that the COM protocol space 110 and the RF characteristic space 112 may be located at predetermined locations on the same storage device, on different storage devices, or at overlapping or interlaced locations on the same storage device, but are not limited to this.

[0040] As non-limiting examples, the memory 104 may be or include one or more of the following: flash memory, electrically erasable programmable read-only memory, electrically erasable programmable read-only memory (EEPROM) and read-only memory (ROM), random access memory (RAM), but is not limited thereto. In one embodiment, the application 106 and the COM protocol space 110 may be stored on the flash memory or RAM, the RF characteristic space 112 may be stored on the EEPROM, and the installation program 108 may be stored on the ROM.

[0041] As a non-limiting example, the RF characteristics that may be stored at the RF characteristics space 112 (such as the RF characteristics stored at the configuration server 120 and Figure 3 The RF characteristics 312 of the keyless entry system 120 (e.g., RF characteristics 312 of the keyless entry system 120, but not limited thereto) may include one or more of frequency, modulation type (e.g., amplitude shift keying modulation or frequency shift keying modulation, but not limited thereto), data rate, and output power. As a non-limiting example, the communication protocol instructions that may be stored at the COM protocol space 110 (e.g., the communication protocol stored at the configuration server 120 and the COM protocol 310) may include rules for formatting messages sent to the keyless entry system 128. As a non-limiting example, the rules for formatting the message may include rules for the content of the data packet that includes the message. The content may include identifiers, command codes, such as command codes for locking, unlocking, opening, and error correction (e.g., checksum, cyclic redundancy check, but not limited thereto).

[0042] exist Figure 1 In the embodiment, the COM protocol space 110 and the RF characteristic space 112 are depicted as having a boundary including a dashed line. In the expected scenario, the dashed line indicates that no instructions and / or parameters are currently stored. In another expected scenario, the dashed line indicates that the instructions and / or parameters stored at the COM protocol space 110 and the RF characteristic space 112 will be replaced.

[0043] The installer 108 may generally be configured to enable the configurable access controller 102 (and more specifically, the processor 114 executing the installer 108) to receive a configuration file 132 including COM protocols and RF characteristics, and store such RF characteristics and COM protocols in the COM protocol space 110 and the RF characteristics space 112, respectively.

[0044] The application 106 may generally be configured to enable the configurable access controller 102 (and more specifically, the processor 114 executing the application 106) to send messages, such as control messages 134 (e.g., unlock, lock, open, or close a door, but not limited to) to the keyless entry system 128 using the COM protocols and RF characteristics (once installed) stored at the memory 104. The configurable access controller 102 may be configured to access and use the COM protocols and RF characteristics stored at the COM protocol space 110 and the RF characteristics space 112, respectively, to format the message and configure the RF signal carrying the message.

[0045] The cryptographic element 116 may generally be configured to perform an authentication process with the provisioning device 126, such as, by way of non-limiting example, a challenge-response process using a public key and / or a private key. The cryptographic element 116 may include one or more memories for storing a unique identifier associated with the configurable access controller 102, and the cryptographic element 116 may be configured to provide such an identifier to a process at the configurable access controller 102, such as a process for pairing the configurable access controller 102 with the keyless entry system 128, or a process for sending an instruction to the keyless entry system 128 to unlock or lock.

[0046] The RF transceiver 118 may generally be configured to transmit RF signals exhibiting RF characteristics stored in the RF characteristics space 112 and carrying messages sent using a COM protocol stored at the COM protocol space 110 .

[0047] The keyless entry system 128 may be configured to use a specific COM protocol and tuned to specific RF characteristics of the carrier signal, and will not respond to messages that do not conform to the COM protocol or RF characteristics.

[0048] The configurable access controller 102 may be configured to send a control message 134 to the keyless entry system 128, including when the keyless entry system 128 is in a learning mode of operation (i.e., a mode of operation in which the keyless entry system 128 may add devices to its authorized device list). In one embodiment, the control message 134 may include an encoded message that includes an identifier associated with (i.e., uniquely identified by) the configurable access controller 102 and / or a command (e.g., open, close, lock, unlock), but not limited thereto.

[0049] In one or more embodiments, as a non-limiting example, the keyless entry system 128 can be placed in a learning mode of operation by a user by activating a button or switch. When in the learning mode of operation, the keyless entry system 128 can be configured to store identifiers sent in control messages (e.g., control messages 134) that are properly formatted and / or encoded messages (i.e., using the COM protocol stored at COM protocol 310) at a list of approved identifiers.

[0050] Figure 2 An embodiment of a configuration / reconfiguration process 200 performed by the setup device 126 , the configurable access controller 102 , and the keyless entry system 128 of the system 100 is shown.

[0051] In operation 202 , the setup device 126 and the configurable access controller 102 are paired, for example, through an authentication process involving the use of public / private keys.

[0052] In operation 204 , the configurable access controller 102 enters a configuration mode of operation in response to pairing with the setup device 126 in operation 202 .

[0053] In operation 206, as a non-limiting example, the user selects an identifier of the target keyless entry system 128 by providing a vehicle make and vehicle model at the setup device 126. In one embodiment, the setup device 126 may provide a prompt on its display that includes a field for entering text for the vehicle make or vehicle model.

[0054] In operation 208, the setup device 126 receives the configuration file (eg, Figure 1 The configuration file may include instructions for the COM protocol and information about RF characteristics. Figure 1 As shown, in one embodiment, setup device 126 may retrieve configuration file 132 from configuration server 120 .

[0055] In operation 210 , the setup device 126 sends the configuration file to the configurable access controller 102 for installation.

[0056] In operation 212 , the configurable access controller 102 configures itself to use the COM protocol and RF features in the configuration file received in operation 210 .

[0057] In operation 214, the keyless entry system 128 enters the learn mode of operation. In one embodiment, the keyless entry system 128 may enter the learn mode of operation in response to execution of a pre-specified interaction with the keyless entry system 128, such as, by way of non-limiting example, pressing and holding a button connected to the keyless entry system 128.

[0058] In operation 216, the configurable access controller 102 sends a control message to the keyless entry system 128 according to the COM protocol and RF characteristics stored at the configurable access controller 102. As a non-limiting example, the control message may include an identifier of the configurable access controller 102.

[0059] In operation 218, the keyless entry system 128 “learns” the configurable access controller 102 so that the keyless entry system 128 will respond to control messages that include commands received from the configurable access controller 102. Learning the configurable access controller 102 may include setting up / configuring the keyless entry system 128 to respond to control messages from the configurable access controller 102. As a non-limiting example, the keyless entry system 128 may update an internal list of learned access controllers to include an identifier of the configurable access controller 102.

[0060] exist Figure 3 In the illustrated embodiment, system 300 may include a configurable access controller 302, a keyless entry system 328, an access server 320, and an interface 326. As described above, in Figure 3 In the envisioned scenario, the configurable access controller 302 has been configured to communicate with the keyless entry system 328. More specifically, the COM protocol 310 and the RF feature 312 are installed at the memory 304, and the configurable access controller 302 can use the COM protocol 310 and the RF feature 312 to send control messages to the keyless entry system 328 and / or receive control messages from the keyless entry system.

[0061] For example, during intended communication from configurable access controller 302 to keyless entry system 328 , configurable access controller 302 may format control message 332 according to COM protocol 310 and control RF transceiver 316 such that a carrier signal transmitted from RF transceiver 316 carrying control message 332 exhibits one or more RF characteristics 312 .

[0062] The configurable access controller 302, and more specifically, the processor 314 executing the application 306, may be configured to send control messages in response to requests received from the interface 326. As a non-limiting example, the interface 326 may be a general-purpose computing device programmed to perform the various functions of the embodiments of the interface 326 described herein. Figure 3In the example of , the configurable access controller 302 is configured with a COM protocol 310 and an RF characteristic 312, which enables the configurable access controller to communicate with a keyless entry system 328. In one embodiment, the configurable access controller 302 is configured to send a control message 332 to the keyless entry system 328 in response to receiving an access request 334 from the interface 326. In one embodiment, the configurable access controller 302, and more specifically, the cryptographic element 318, is configured to authenticate the interface 326 and, if the authentication is successful, send the control message 332 in response to the access request 334. In one embodiment, the cryptographic element 318 is configured to authenticate the interface 326, for example, using a challenge-response sequence involving a public key and / or a private key.

[0063] Notably, the installer 308 is stored at the memory 304. Thus, as a non-limiting example, the configurable access controller 302 can be reconfigured via the installer 308 to communicate with a keyless entry system using a different COM protocol, or to be tuned to different RF characteristics than the keyless entry system 328, or if the COM protocol and / or tuned RF characteristics of the keyless entry system 328 are changed.

[0064] The interface 326 can be configured to communicate with the configurable access controller 302, for example, via one or more communication links between the configurable access controller 302 and the interface 326. To communicate with the configurable access controller 302, in some embodiments, the interface 326 is configured to communicate using a configuration file 336. Figure 3 , interface 326 sends a request 338 for access configuration information to access server 320 via a communication link including communication network 330. In response to request 338, access server 320 sends configuration file 336 to interface 326, which includes instructions that enable interface 326 to establish a communication link and communicate with configurable access controller 302.

[0065] In a vehicle access scenario, request 338 may include an identifier of the customer or vehicle (e.g., name, address, account number, license plate number, but not limited thereto). In one embodiment, the identifier of the customer or vehicle may be provided to interface 326 by a user interface included at interface 326 (not shown), such as, but not limited to, a touch screen, a keyboard, a pointer device, or a natural language processor.

[0066] The access server 320 may be configured to retrieve the requested configuration information included in the access controller profile 324 associated with the particular customer of the customer account 322 based at least in part on the identifier in the request 338 received from the interface 326. The access server 320 may also be configured to send the profile 336 including such configuration information to the interface 326. The configuration information in the profile 336 may include access configuration information, i.e., information that enables the interface 326 to communicate with the configurable access controller 302. The information used to enable the interface 326 to communicate with the configurable access controller 302 may include, for example, credentials for authenticating the interface 326 to the configurable access controller 302.

[0067] Figure 4 An embodiment of a process 400 performed by the interface 326 , the configurable access controller 302 , and the keyless entry system 328 is shown.

[0068] In operation 402, a customer profile is selected at interface 326. As a non-limiting example, the customer profile may be associated with a vehicle or other restricted resource, access to which is controlled by keyless entry system 328. In the use case contemplated herein, selecting a customer profile may involve a user selecting the customer profile at interface 326. In another use case contemplated herein, interface 326 may autonomously send location information to access server 320, which may match the location information to an address and match the address to a customer profile. Non-limiting examples of location information include an address, global satellite navigation system coordinates, longitude and latitude, and media access control data (e.g., MAC ID or MAC address, but not limited thereto).

[0069] In operation 404, an access configuration file is received at interface 326 (eg, downloaded from access server 320), wherein the access configuration file (eg, Figure 3 The access profile 336 (eg, but not limited to, the access profile 336) is associated with the customer profile selected in operation 402. As non-limiting examples, the access profile may include one or more of instructions for communication protocols, RF characteristics, and authentication.

[0070] In operation 406 , a request to access a vehicle controlled by the keyless entry system 328 is received at the interface 326 . In one embodiment, when the access configuration file is successfully received in operation 404 , the access request may be initiated from within the customer profile selected in operation 402 .

[0071] In operation 408, the interface 326 pairs with the configurable access controller 302 using the instructions in the access profile 336 received in operation 404, thereby establishing a communication link between the interface 326 and the configurable access controller 302, and the interface 326 and the configurable access controller 302 can communicate via such established communication link. In one embodiment, the pairing in operation 408 can be performed using a challenge / response pair involving a public key and / or a private key. The instructions in the access profile received in operation 404 can include credentials for performing such authentication.

[0072] In operation 410 , the interface 326 sends a request (eg, access request 334 , but not limited thereto) to the configurable access controller 302 to access the vehicle controlled by the keyless entry system 328 . The request is sent via the communication link established in operation 408 .

[0073] In operation 412, in response to the request sent in operation 410, the configurable access controller 302 sends an unlock request to the keyless entry system 328. The unlock request is a control message (e.g., Figure 3 A control message 332 is sent using the COM protocol and RF features installed at the configurable access controller 302.

[0074] In operation 414, the keyless entry system 328 unlocks the doors and / or trunk of the vehicle in response to the unlock request sent in operation 412. In this scenario, the COM protocol and RF characteristics used to send the unlock request in operation 412 match the COM protocol and RF characteristics expected by the keyless entry system 328, and the identification information included in the request matches the identification information of the learning device stored at the keyless entry system 328. In another scenario, if the COM protocol and / or RF characteristics used to send the request (particularly, if the received message does not conform to the COM protocol and exhibits the RF characteristics expected by the keyless entry system 328, and the identification information included in the request matches the identification information of the learning device stored in the keyless entry system 328) are not those COM protocols and / or RF characteristics expected by the keyless entry system 328, and / or if the identification information does not match the identification information of the learning device stored at the keyless entry system 328, then the keyless entry system 328 may not respond to the request sent in operation 412.

[0075] Figure 5 A block diagram of a system 500 for unlocking a trunk of a vehicle 504 to which access is controlled by a keyless entry system 508 using a vehicle configurable access controller 506 is shown.

[0076] exist Figure 5In the envisioned scenario, delivery person 502 intends to deposit package 518 in vehicle 504, and more specifically, in the trunk of vehicle 504. However, the means of access to vehicle 504 (i.e., windows, doors, and trunk) are locked and under the control of keyless entry system 508.

[0077] exist Figure 5 In the envisioned scenario, delivery person 502 uses mobile device 510 (e.g., a smartphone or custom device, but not limited thereto) as an interface (e.g., Figure 3 The mobile device 510 may be used to communicate with the vehicle configurable access controller 506. A first communication link (here, a wireless communication link) has been established between the mobile device 510 and the vehicle configurable access controller 506 (as discussed herein), and the mobile device 510 may send messages (e.g., requesting to unlock, lock, and open, but not limited thereto) to the vehicle configurable access controller 506 via the first communication link. In order to unlock the trunk of the vehicle 504, the delivery person 502 may use the mobile device 510 to send a message including an access request to the vehicle configurable access controller 506 via the first communication link.

[0078] It is worth noting that the vehicle configurable access controller 506 can be physically located anywhere in the vehicle 504 as long as the vehicle configurable access controller is able to form a communication link with the mobile device 510 and a communication link with the keyless entry system 508 .

[0079] A second communication link (herein wired or wireless) is established between the vehicle configurable access controller 506 and the keyless entry system 508. The second communication link may be hardwired so as to be always available, or established in response to the establishment of the first communication link. In response to the access request from the mobile device 510 sent on the first communication link, the vehicle configurable access controller 506 may send a control message to the keyless entry system 508 via the second communication link. In this scenario, the control message may include a trunk unlock / open command, in response to which the keyless entry system 508 unlocks and / or opens the trunk of the vehicle 504 (the trunk opening is not performed in the vehicle 504). Figure 5 ).

[0080] When storing package 518 in the trunk of vehicle 504, delivery person 502 may use mobile device 510 to send a message including a close and / or lock request to vehicle configurable access controller 506 via a first communication link. In response to the lock request, vehicle configurable access controller 506 may send a control message including a close and / or lock command to keyless entry system 508 via a second communication link. In response to the lock command, keyless entry system 508 closes and / or locks the trunk of vehicle 504.

[0081] The mobile device 510 also communicates with a vehicle access server 514 including an access server (eg, access server 320, but not limited thereto) via a third communication link including a communication network 516. Figure 5 In the envisioned scenario, the delivery person 502 may use the mobile device 510 to select a customer profile associated with the package 518 (e.g., the delivery address or recipient of the package 518). The mobile device 510 may send a request for authentication information required to communicate with the vehicle configurable access controller 506 to the vehicle access server 514 via the third communication link. The vehicle access server 514 may confirm the authorization of the delivery person 502 or the mobile device 510 and download an access code to the mobile device 510. The mobile device 510 may transmit the access code to the vehicle configurable access controller 506 via the first communication link. The vehicle configurable access controller 506 may verify the authenticity of the received access code, for example, via a public / private key, and upon confirming the authenticity, may command the keyless entry system 508 to provide access to the trunk of the vehicle 504.

[0082] Figure 5 A configuration server 512 is also shown, and although not used in the above scenario, during the process of setting up the vehicle configurable access controller 506 to work with the keyless entry system 508, a configuration file having instructions for the COM protocol and information about RF characteristics can be downloaded from the configuration server 512 and stored at the vehicle configurable access controller 506 so that the vehicle configurable access controller 506 can set up a communication link with the keyless entry system 508.

[0083] Figure 6 A diagram illustrating an embodiment of a configuration file 602 (ie, a computer-readable electronic file) that may be used to configure a configurable access controller, such as a Figure 1 The configurable access controller 102 can create Figure 3 The configuration file 132 of the configurable access controller 302 is not limited thereto.

[0084] exist Figure 6In the illustrated embodiment, the configuration file 602 includes fields for instructions for radio frequency characteristics and instructions for the communication protocol. The fields for radio frequency characteristics include a field for frequency 604, a field for modulation type 606, a field for data rate 608, and a field for output power 610. The modulation type may be one or more of amplitude shift keying modulation or frequency shift keying modulation, but is not limited thereto. The fields for the communication protocol instructions include a field for message format 612 (e.g., a description of the fields that should be included in the message, but is not limited thereto), a field for header rules 614 (e.g., rules for formatting information in the header (such as identifiers), but is not limited thereto), a field for content format rules 616 (e.g., rules for formatting the contents of various fields in the message defined in the message format 612, such as, but not limited to, command code 618, and / or rules for the contents of the data packet that includes the message), and a field for command code 618 (e.g., a code for representing commands such as lock, unlock, open, close, but is not limited thereto). During a setup operation, an installer (e.g., installer 108, but not limited thereto) may parse configuration file 602, read one or more contents of a field, and store the contents at a configurable access controller (e.g., at COM protocol space 110 and / or RF characteristic space 112 of configurable access controller 102, but not limited thereto).

[0085] According to embodiments of the present disclosure, various networks may be implemented, such as communication network 330 and communication network 130. Such networks may include wired paths, wireless paths, and combinations of wired and / or wireless paths. Such networks may include the Internet, an extranet, an intranet, an Ethernet, or any other system capable of communication.

[0086] One or more embodiments are generally directed to an electronic key that includes a configurable access controller according to one or more disclosed embodiments (eg, configurable access controller 102 , configurable access controller 302 , and vehicle configurable access controller 506 , but not limited thereto).

[0087] One or more embodiments are generally directed to a microcontroller-type embedded system that includes one or more aspects of a configurable access controller (eg, configurable access controller 102 , configurable access controller 302 , and vehicle configurable access controller 506 , but not limited thereto) according to one or more disclosed embodiments.

[0088] It is worth noting that a transceiver can be a device configured as a transmitter, a receiver, or both. In addition, a transceiver can be a device configured to receive and / or transmit RF signals, or a transceiver can be multiple devices, for example, a device configured to receive RF signals and another device configured to transmit RF signals.

[0089] As used in this disclosure, the term "module" or "component" may refer to a specific hardware implementation that is configured to perform the actions of a module or component and / or software object or software routine that may be stored on and / or executed by general hardware of a computing system (e.g., a computer-readable medium, a processing device, etc.). In some embodiments, the different components, modules, engines, and services described in this disclosure may be implemented as objects or processes executed on a computing system (e.g., as separate threads). Although some of the systems and methods described in this disclosure are generally described as being implemented in software (stored on and / or executed by general hardware), specific hardware implementations or combinations of software and specific hardware implementations are possible and contemplated.

[0090] The terms used in this disclosure, especially in the appended claims (e.g., the bodies of the appended claims) are generally intended to be “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” and the term “comprising” should be interpreted as “including but not limited to”).

[0091] Additionally, if a specific number of an introduced claim recitation is intended, such intent will be expressly recited in the claim, and in the absence of such recitation, no such intent is present. For example, to aid understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that a claim recitation introduced by the indefinite article "a" or "an" will limit any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article, such as "a" or "an" (e.g., "a" and / or "an" may be construed to mean "at least one" or "one or more"); this is also true of the use of definite articles used to introduce claim recitations.

[0092] Furthermore, even if specific numbers of introduced claim recitations are explicitly recited, those skilled in the art will recognize that such recitations should be interpreted as referring to at least the recited number (e.g., a bare recitation of "two recitations" without other modifiers refers to at least two recitations or two or more recitations). Furthermore, in those instances where a conventional phrase similar to "at least one of A, B, and C, etc." or "one or more of A, B, and C, etc." is used, such construction is generally intended to include A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together.

[0093] In addition, any discrete word or phrase presenting two or more additional terms, whether in the specification, claims or drawings, should be understood to include the possibility of one of the terms, either of the two terms, or both of the two terms. For example, the phrase "A or B" should be understood to include the possibility of "A" or "B" or "A and B".

[0094] Additional non-limiting embodiments of the present disclosure include:

[0095] Embodiment 1: A configurable access controller comprises: a processor; a radio frequency (RF) transceiver; and one or more memories, wherein the one or more memories store: first processor executable instructions, wherein the first processor executable instructions, when executed by the processor, enable the configurable access controller to store communication protocol instructions and radio frequency (RF) characteristics at the one or more memories; and second processor executable instructions, wherein the second processor executable instructions, when executed by the processor, enable the configurable access controller to send a message configured to identify the configurable access controller to a keyless entry system using a communication protocol associated with the communication protocol instructions and exhibiting at least one RF characteristic of the RF characteristic.

[0096] Embodiment 2: A configurable access controller as described in embodiment 1, wherein the message includes an identifier associated with the configurable access controller.

[0097] Embodiment 3: The configurable access controller according to any one of Embodiments 1 and 2 further includes: an encryption element configured to authenticate a device attempting to establish a communication link with the configurable access controller.

[0098] Embodiment 4: A configurable access controller according to any one of Embodiments 1 to 3, wherein the RF characteristics include one or more of the following: frequency, modulation type, data rate, and output power.

[0099] Embodiment 5: A configurable access controller according to any one of Embodiments 1 to 4, wherein the modulation type is one or more of: amplitude shift keying modulation or frequency shift keying modulation.

[0100] Embodiment 6: A configurable access controller according to any one of Embodiments 1 to 5, wherein the first processor executable instructions are further configured to enable the configurable access controller to receive one or more configuration files including instructions for communication protocols and RF characteristics.

[0101] Embodiment 7: A configurable access controller as in any one of Embodiments 1 to 6, wherein a control message in the message includes a command for the keyless entry system.

[0102] Embodiment 8: The configurable access controller of any one of Embodiments 1 to 7, wherein the command is one of unlock, lock, open, and close.

[0103] Embodiment 9: A configurable access controller according to any one of Embodiments 1 to 8, wherein the one or more memories include a first code space for storing communication protocol instructions.

[0104] Embodiment 10: A configurable access controller as described in any of Embodiments 1 to 9, wherein the one or more memories include a second code space for storing the RF characteristics.

[0105] Embodiment 11: The configurable access controller of any one of Embodiments 1 to 10, wherein the communication protocol instructions include rules for formatting messages.

[0106] Embodiment 12: A configurable access controller as described in any of Embodiments 1 to 11, wherein the rules for formatting messages include rules for the content of a data packet comprising the message.

[0107] Embodiment 13: A system comprising: a configurable access controller; and an interface, wherein the interface is configured to: receive target identification information via a prompt; send a request for a configuration file, the request including the target identification information received via the prompt; receive a configuration file, the configuration file including instructions for communicating with a keyless entry system; and send the instructions to the configurable access controller.

[0108] Embodiment 14: The system according to Embodiment 13 further includes: a configuration server, wherein the configuration server is configured to provide the requested configuration file.

[0109] Embodiment 15: The system of any of Embodiments 13 and 14, wherein the instructions for communicating with the keyless entry system include one or more of radio frequency (RF) characteristics and instructions for a communication protocol.

[0110] Embodiment 16: A system according to any one of Embodiments 13 to 15, wherein the configurable access controller is configured to locally store the communication protocol and the RF characteristics.

[0111] Embodiment 17: The system according to any one of embodiments 13 to 16 further includes a keyless entry system, wherein the keyless entry system is configured to operate in a learning operation mode, and the configurable access controller that communicates with the keyless entry system is learned when the keyless entry system operates in the learning operation mode.

[0112] Embodiment 18: The system of any one of Embodiments 13 to 17, further comprising a keyless entry system, wherein the keyless entry system is configured to use a specific communication protocol and is tuned to specific RF characteristics.

[0113] Embodiment 19: The system of any one of Embodiments 13 to 18, further comprising a keyless entry system, wherein the keyless entry system is configured to control access to a vehicle, a residential building, a commercial building, a facility, a fenced area, a container, or a room.

[0114] Embodiment 20: A system according to any one of Embodiments 13 to 19, wherein the target identification information is one or more of a make and model of a vehicle.

[0115] Embodiment 21: A system according to any one of Embodiments 13 to 20, wherein the target identification information is selected from the group including: vehicle brand, vehicle model, address, global satellite navigation system coordinates, longitude and latitude, and media access control data.

[0116] Although the present invention is described herein with respect to certain illustrated embodiments, those of ordinary skill in the art will recognize and appreciate that the present invention is not so limited. Rather, many additions, deletions, and modifications may be made to the illustrated embodiments and the described embodiments without departing from the scope of the present invention as claimed below and its legal equivalents. Furthermore, features from one embodiment may be combined with features of another embodiment while still being included within the scope of the present invention as contemplated by the inventor.

Claims

1. A configurable access controller, comprising: processor; Radio frequency (RF) transceiver; and One or more memories, wherein the one or more memories store: first processor-executable instructions, wherein the first processor-executable instructions, when executed by the processor, enable the configurable access controller to store instructions for a communication protocol and radio frequency (RF) characteristics at the one or more memories, wherein the first processor-executable instructions are further configured to enable the configurable access controller to receive one or more configuration files including the instructions for a communication protocol and the radio frequency (RF) characteristics; and second processor-executable instructions, wherein the second processor-executable instructions, when executed by the processor, enable the configurable access controller to send a message configured to identify the configurable access controller to a keyless entry system using a communication protocol associated with the instructions for a communication protocol, wherein the message configured to identify the configurable access controller to the keyless entry system is transmitted on a carrier signal, the carrier signal being configured by the radio frequency (RF) characteristics such that the radio frequency (RF) characteristics exhibited by the carrier signal match radio frequency (RF) characteristics expected by the keyless entry system, and The radio frequency (RF) characteristics of the communication protocol include all of the following: frequency, modulation type, data rate, and output power.

2. The configurable access controller of claim 1, wherein the message includes an identifier associated with the configurable access controller.

3. The configurable access controller of claim 1 , further comprising: A cryptographic element configured to authenticate a device attempting to establish a communication link with the configurable access controller.

4. The configurable access controller of claim 1, wherein the modulation type is one or more of: amplitude shift keying modulation or frequency shift keying modulation.

5. The configurable access controller of claim 1, wherein a control message in the message comprises a command for the keyless entry system.

6. The configurable access controller of claim 5, wherein the command is one of unlock, lock, open, and close.

7. The configurable access controller of claim 1, wherein the one or more memories include a first code space for storing the instructions for a communication protocol.

8. The configurable access controller of claim 7, wherein the one or more memories include a second code space for storing the radio frequency (RF) characteristics.

9. The configurable access controller of claim 1, wherein the instructions for the communication protocol include rules for formatting messages.

10. A configurable access controller as claimed in claim 9, wherein the rules for formatting a message include rules for the content of a data packet comprising the message.

11. An access control system comprising: Configurable access controller; and An interface, wherein the interface is configured to: receiving target identification information via a prompt; sending a request for a configuration file, the request including the target identification information received via the prompt; receiving a configuration file including instructions for communicating with a keyless entry system, wherein the instructions for communicating with the keyless entry system include radio frequency (RF) characteristics and instructions for a communication protocol, and wherein the radio frequency (RF) characteristics include all of the following: frequency, modulation type, data rate, and output power; and sending the instructions for communicating with the keyless entry system to the configurable access controller, The configurable access controller uses a communication protocol to send a message configured to identify the configurable access controller to the keyless entry system, the message being transmitted on a carrier signal, the carrier signal being configured with the radio frequency (RF) characteristics so that the radio frequency (RF) characteristics exhibited by the carrier signal match the radio frequency (RF) characteristics expected by the keyless entry system.

12. The access control system of claim 11, further comprising: A configuration server is configured to provide the requested configuration file.

13. The access control system of claim 11, wherein the configurable access controller is configured to locally store the communication protocol and the radio frequency (RF) characteristics.

14. The access control system of claim 11 further comprising a keyless entry system, wherein the keyless entry system is configured to operate in a learning mode of operation and learn the configurable access controller in communication with the keyless entry system when the keyless entry system operates in the learning mode of operation. 15 . The access control system of claim 11 , further comprising a keyless entry system, wherein the keyless entry system is configured to use a specific communication protocol and is tuned to specific radio frequency (RF) characteristics.

16. The access control system of claim 11, further comprising a keyless entry system, wherein the keyless entry system is configured to control access to a vehicle, a residential building, a commercial building, a facility, a fenced area, a container, or a room.

17. The access control system of claim 11, wherein the target identification information is one or more of a make and model of a vehicle.

18. The access control system of claim 11, wherein the target identification information is selected from the group consisting of: a make of vehicle, a model of vehicle, an address, a global satellite navigation system coordinate, longitude and latitude, and media access control data.

Images