Authentication of multiple mobile devices by same target device in ultra-wideband system

Abstract

An ultra wide band (UWB) system, a target apparatus, and a method are disclosed. In an embodiment, the UWB system includes a UWB transceiver configured to transmit and receive signals within a particular frequency range, and a UWB processor operably connected to the UWB to process the signals. The UWB processor is configured to: broadcast a parameter associated with a first authentication value, the parameter being sufficient to derive the first authentication value at a plurality of mobile devices; receiving a plurality of second authentication values from the plurality of mobile devices; and receive, from the target secure element, a ranging dataset for each valid second authentication value, the ranging dataset for authenticating a mobile device associated with the valid second authentication value for secure communication via the UWB transceiver.

Description

Technical Field

[0001] This invention discloses an ultra-wideband (UWB) system, target device, and method. Background Technology

[0002] Currently, contactless relay applications use two-factor authentication. This enables two-way authentication and, in most scenarios, protects privacy because the user's identifier (ID) is not transmitted in plaintext.

[0003] The same requirements apply to Ultra-Wideband (UWB) relay applications, but with additional challenges. While UWB range is measured in meters rather than centimeters and throughput in mb / s rather than Kb / s, the channel is shared among multiple users and dedicated to ranging and data transmission, resulting in significantly higher latency. Therefore, the solution is to begin the initial phase of the transaction—the authentication phase—from a greater distance, but this means each gateway needs to authenticate with all devices within range. Since many of these devices will ultimately not transact with that gateway because users will pass through other gateways (or not at all), the authentication overhead becomes substantial. Summary of the Invention

[0004] An ultra-wideband (UWB) system, target apparatus, and method are disclosed. In an embodiment, the UWB system includes a UWB transceiver configured to transmit and receive signals within a specific frequency range, and a UWB processor operatively connected to the UWB to process the signals. The UWB processor is configured to: broadcast parameters associated with a first authentication value sufficient to derive the first authentication value at multiple mobile devices; receive multiple second authentication values ​​from the multiple mobile devices; and receive a ranging dataset for each valid second authentication value from a target security element, the ranging dataset being used to authenticate the mobile device associated with the valid second authentication value for secure communication via the UWB transceiver.

[0005] In one embodiment, the UWB processor is configured to broadcast parameters associated with the first authentication value in a command message.

[0006] In one embodiment, the UWB processor is configured to broadcast parameters associated with the first authentication value in a UWB scheduling control message.

[0007] In an embodiment, the UWB processor is configured to broadcast out-of-band parameters associated with the first authentication value compared to a second authentication value from a plurality of mobile devices.

[0008] In an embodiment, the parameters associated with the first authentication value include at least two of the following: a session identifier, a padding value, and an epoch value.

[0009] In embodiments, the ranging data set for each valid second authentication value includes at least a session identifier.

[0010] In embodiments, the ranging data set for each valid second authentication value additionally includes a UWB ranging session key.

[0011] In embodiments, each of the second authentication values is a value formed by concatenating at least some of the parameters associated with the first authentication value from most significant bit (MSB) to least significant bit (LSB).

[0012] In embodiments, the UWB processor is additionally configured to receive a ranging data set from a particular mobile device of the plurality of mobile devices and compare the ranging data set from the particular mobile device to a corresponding ranging data set from the target secure element for the particular mobile device.

[0013] In embodiments, a method includes broadcasting, from an ultra-wideband (UWB) system of a target device, parameters associated with a first authentication value, the parameters sufficient to derive the first authentication value at a plurality of mobile devices; receiving, at the UWB system from the plurality of mobile devices, a plurality of second authentication values; and receiving, at the UWB system from a target secure element, a ranging data set for each valid second authentication value, the ranging data set for use in authenticating a mobile device associated with the valid second authentication value for secure communication.

[0014] In embodiments, broadcasting the parameters associated with the first authentication value includes broadcasting the parameters associated with the first authentication value from an ultra-wideband (UWB) system of a target device in a command message.

[0015] In embodiments, broadcasting the parameters associated with the first authentication value includes broadcasting the parameters associated with the first authentication value from a UWB system of a target device in an ultra-wideband (UWB) schedule control message.

[0016] In embodiments, broadcasting the parameters associated with the first authentication value includes broadcasting the parameters associated with the first authentication value from an ultra-wideband (UWB) system of a target device out-of-band compared to second authentication values from the plurality of mobile devices.

[0017] In embodiments, the parameters associated with the first authentication value include at least two of a session identifier, a padding value, and an epoch value.

[0018] In embodiments, the ranging data set for each valid second authentication value includes at least a session identifier.

[0019] In embodiments, the ranging data set for each valid second authentication value additionally includes a UWB ranging session key.

[0020] In embodiments, each of the second authentication values is a value formed by concatenating at least some of the parameters associated with the first authentication value from most significant bits (MSB) to least significant bits (LSB).

[0021] In embodiments, the method additionally includes receiving a ranging data set from a particular mobile device of the plurality of mobile devices and comparing the ranging data set from the particular mobile device to a corresponding ranging data set from the target secure element for the particular mobile device.

[0022] In embodiments, the target device includes a secure element for running at least one application and storing data, and an ultra-wideband (UWB) system operably coupled to the secure element. The UWB system is configured to: transmit and receive signals in a particular frequency range; broadcast parameters associated with a first authentication value, the parameters being sufficient to derive the first authentication value at a plurality of mobile devices; receive a plurality of second authentication values from the plurality of mobile devices; and obtain a ranging data set for each valid second authentication value from the secure element, the ranging data set being used to authenticate a mobile device associated with the valid second authentication value for secure communication.

[0023] In embodiments, the UWB system is configured to broadcast the parameters associated with the first authentication value in a UWB schedule control message.

[0024] These and other aspects in accordance with embodiments will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0025] Figure 1 is a diagram of an ultra-wideband (UWB) communication system in accordance with embodiments of the present application.

[0026] Figure 2 is a flowchart of a process of authenticating a plurality of mobile devices in a UWB communication system in accordance with embodiments of the present application.

[0027] Figure 3 shows a transmission system authentication sequence for a UWB communication system in accordance with embodiments of the present application.

[0028] Figure 4 is a flowchart of a process of transmitting challenge 1 and challenge 2 values in a UWB link in a UWB communication system in accordance with embodiments of the present application.

[0029] Figure 5 shows a frame format for a ranging response message (RRM) frame in accordance with embodiments of the present application.

[0030] Figure 6 is a process flow diagram of a method in accordance with embodiments of the present application.

[0031] Throughout the description, like reference numerals can be used to denote like elements throughout the several views. DETAILED DESCRIPTION

[0032] It will be readily understood that the components of the embodiments, as generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the various embodiments, as represented in the figures, is not intended to limit the scope of the present disclosure, but is merely representative of various embodiments. While the various aspects of the embodiments are presented in the drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

[0033] The application can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the application is, therefore, indicated by the appended claims, rather than by this detailed description. All changes coming within the meaning and equivalency range of the claims are intended to be embraced in the scope of the claims.

[0034] Reference throughout this specification to a feature, advantage, or similar language does not imply that all of the features and advantages that can be achieved with the present application must be or are in any single embodiment of the application. Rather, language referring to a feature or an advantage is understood mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the application. Thus, appearances of the phrase "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0035] Furthermore, the described features, advantages, and characteristics of the application can be combined in any suitable manner in one or more embodiments. One skilled in the art will recognize that the application can be practiced without one or more of the specific features or advantages of a particular embodiment, in this case an embodiment. In other cases, additional features and advantages can be recognized in a certain embodiment that may not be present in all embodiments of the application.

[0036] As used herein, the terms "coupled" or "connected" can include a direct coupling or connection between the elements that are coupled or connected, and can also include an indirect coupling or connection through one or more intermediate elements.

[0037] Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. Accordingly, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0038] Reference will now be made to the drawings Figure 1 FIG. 1 illustrates an ultra-wideband (UWB) communication system 100 in accordance with an embodiment of the present application. The UWB communication system 100 can include one or more UWB-enabled mobile devices 102-1... 102-X that can interact with one or more UWB-enabled target devices 104-1... 104-Y using a secure ranging technique involving an authentication process. Depending on the interaction between the devices, any number of mobile devices and any number of target devices can be included in the UWB communication system.

[0039] The mobile devices 102-1... 102-X and the target devices 104-1... 104-Y of the UWB communication system 100 can be designed or programmed to perform various transactions or operations between the devices. For example, each of the target devices 104-1... 104-Y can act as a gateway for a transit system, and the mobile devices 102-1... 102-X can be user devices for performing a fare transaction to gain access to the transit system. In this example, each of the target devices 104-1... 104-Y that acts as a gateway for a transit system initiates an access control operation to provide access to a user of the mobile devices 102-1... 102-X when a particular mobile device is detected to be within a predefined range of the target device.

[0040] Each of the mobile devices 102-1... 102-X (collectively referred to as "102") includes a mobile processor 106, a mobile secure element 108, and a mobile ultra-wideband system (UWBS) 110. The mobile processor 106 of the mobile device 102 can be any type of processing device, such as a processor commonly found on a smartphone. Thus, the mobile processor 106 can run various applications, such as a transit application for the mobile device that can be used to pay a fare for a transit system.

[0041] The mobile secure element 108 of the mobile device 102 includes circuitry for performing operations related to secure ranging. In an embodiment, the mobile secure element 108 can include the hardware and / or software necessary to run small applications, such as a service provider applet (SPA), a UWB authentication applet, and a secure UWB service (SUS). The mobile secure element 108 can also include a memory for storing data required for secure ranging. For example, the mobile secure element 108 can be a single-die secure near field communication (NFC) controller, such as the SN220 chip available from NXP Semiconductors.

[0042] The mobile UWB system 110 of the mobile device 102 is configured to support UWB communication with other UWB-enabled devices, such as the target devices 104-1...104-Y. The mobile UWB system 110 can include various components for performing UWB-related operations, such as a UWB processor 112, a memory 114, and UWB communication circuitry 116 connected to a bus 118. The UWB communication circuitry 116 is configured to transmit and receive data signals using UWB. The UWB processor 112 uses data stored in the memory 114 to perform operations for transmitting and receiving data signals from the UWB communication circuitry 116, as well as other operations. The operations performed by the UWB processor 112, the memory 114, and the UWB communication circuitry 116 will be described in greater detail below.

[0043] Each of the target devices 104-1...104-Y (collectively, “104”) includes a target processor 120, a target secure element 122, and a target UWB system 124. The target processor 120 of the target device 104 can be any type of processing device, such as a processor commonly found on a computer system or a mobile device. Thus, the target processor 120 can run various applications, such as an authentication and transit application for a gateway of a transit system, which can be used to authorize entry of a user of a UWB-enabled mobile device (such as the mobile device 102) after authentication and payment of a transit fee.

[0044] The target secure element 122 of the target device 104 includes circuitry for performing operations related to secure ranging. In embodiments, the target secure element 122 can include the hardware and / or software necessary to run a small application, such as a FiRa applet. The target secure element 122 can also include memory for storing data required for secure ranging, such as UWB authentication keys and transit keys. For example, the target secure element 122 can be a secure element for secure UWB ranging in Internet of Things (IOT), such as the SE051 device available from NXP Semiconductors.

[0045] Similar to the mobile UWBS 110, the target UWBS 124 of the target device 104 is configured to support UWB communication with other UWB-enabled devices, such as the mobile devices 102-1... 102-X. The target UWB system 124 can include various components for performing UWB-related operations, such as a UWB processor 126, a memory 128, and a UWB communication circuit 130 connected to a bus 132. The UWB communication circuit 130 is configured to transmit and receive data signals using UWB. The UWB processor 126 uses data stored in the memory 128 to perform operations for transmitting and receiving data signals from the UWB communication circuit 130, as well as other operations. Operations performed by the UWB processor 126, the memory 128, and the UWB communication circuit 130 will be described in greater detail below.

[0046] In a conventional secure ranging procedure between a target device and a mobile device, the target device requests the controlled-party FiRa applet at the target device to initiate a transaction. This is done by selecting the controlled-party FiRa applet, selecting an application dedicated file (ADF), and sending an initiate transaction command. In response to the initiate transaction command, the controlled-party FiRa applet sends a select command that is transmitted over out-of-band data (OOB) to the mobile device and forwarded to the controlling-party FiRa applet at the mobile device. The response to the select command is returned over OOB to the target device and dispatched to the controlled-party FiRa applet using a dispatch command. In response, the controlled-party applet returns the next application protocol data unit (APDU) to be sent over OOB using a select ADF command that is sent over OOB and dispatched to the controlling-party FiRa applet. The response to the select ADF command is returned over OOB and again dispatched to the controlled-party FiRa applet using a dispatch command.

[0047] This process continues back and forth until a secure channel is established, i.e., until the response to the generic authentication 2 command is processed in the controlled-party FiRa applet, which is done after the response to the generic authentication 1 command is processed. This sequence is performed sequentially for authentication between any two devices.

[0048] As described below, the UWB communication system 100 is configured to overcome the close sequencing of the initiate transaction command and the generic authentication 2 command by having one initiate transaction command followed by a series of generic authentication 2 commands for multiple devices. In particular, the UWB communication system 100 allows the responses to the internal authentication (IA) command from multiple mobile devices to be received by the target device (e.g., a gateway of a transit system) over UWB and dispatched to the gateway’s FiRa applet. This results in authentication of multiple mobile devices. The result of this authentication process is the generation of a ranging data set (RDS) for each mobile device, which is used for secure communication between the authenticated mobile device and the target device.

[0049] Reference is now made to the following drawings in which Figure 2 FIG. 1 shows a process of authenticating multiple mobile devices in a UWB communication system 100, according to an embodiment of the application. Reference is made to Figure 2 and Figure 1 , Figure 2 the processes described in

[0050] The process begins with the selection of a FiRa applet running in the target secure element 122 of the target device 104 by the target UWB S 124 of the target device 104 to initiate an authentication process for multiple mobile devices (e.g., mobile devices 104-1 and 104-2), as indicated by arrow 202. In response to the selection, a confirmation message is transmitted from the FiRa applet to the target UWB S 124, as indicated by arrow 204.

[0051] Next, an ADF of the FiRa applet is selected by the target UWB S 124, as indicated by arrow 206. The ADF corresponds to a data structure within an application data structure hosting, for example, an application and application-specific data. In response to the ADF selection, a confirmation message is transmitted from the FiRa applet to the target UWB S, as indicated by arrow 208.

[0052] Next, an initiate transaction command is transmitted from the target UWBS 124 to the FiRa applet, as indicated by arrow 210. In response to the initiate transaction command, a remote internal authentication (IA) command is transmitted from the FiRa applet to the mobile devices, e.g., mobile devices 102-1 and 102-2, via the target UWBS, as indicated by arrows 212, 214, and 216. The IA command includes a challenge 1 value, which is a first authentication value transmitted from the target device 104 to the mobile devices.

[0053] In response to the remote IA command to mobile device 102-1, the FiRa mobile applet of mobile device 102-1 is selected, as indicated by arrow 218. The remote IA command is then processed by the FiRa mobile applet of mobile device 102-1, as indicated by arrow 220. After processing the command, an IA response is transmitted from mobile device 102-1 to the target UWBS 124 of the target device 104, as indicated by arrow 222. The IA response includes a challenge 2 value, which is a second authentication value transmitted from the mobile device to the target device 104.

[0054] Next, the IA response from mobile device 102-1 is dispatched from the UWBS 124 of the target device 104 to the FiRa applet of the target device 104, as indicated by arrow 224. Using the IA response, an RDS (which can include a UWB session identifier (ID) and a UWB ranging session key (URSK)) for mobile device 102-1 is generated and transmitted from the FiRa applet of the target device 104 to the target UWBS 124 of the target device 104, as indicated by arrow 226. The RDS can then be used for secure communication and / or transactions with mobile device 102-1.

[0055] Similarly, in response to the remote IA command to mobile device 102-2, the FiRa mobile applet of mobile device 102-2 is selected, as indicated by arrow 228. The remote IA command is then processed by the FiRa mobile applet of mobile device 102-2, as indicated by arrow 230. After processing the command, an IA response is transmitted from mobile device 102-2 to the target UWBS 124 of the target device 104, as indicated by arrow 232.

[0056] Next, the IA response from the mobile device 102-2 is dispatched from the UWBS 124 of the target device 104 to the FiRa applet of the target device 104, as indicated by arrow 234. Using the IA response, an RDS for the mobile device 102-2 is generated (which can include the UWB session (ID) and the URSK), and transmitted from the FiRa applet of the target device 104 to the UWBS 124, as shown by arrow 236. The RDS can then be used for secure communication and / or transactions with the mobile device 102-2. In a similar manner, other mobile devices sending an IA response can also be authenticated by the same target device.

[0057] Reference is made to Figure 3 A transmission system authentication sequence of the UWB communication system 100 according to embodiments of the application is described, Figure 3 A single target device 104 (gateway) and only one mobile device 102 are shown. The transmission system authentication sequence starts with step 0 when a mobile transit application 302 running on the mobile processor 106 of the mobile device 102 performs a static session establishment.

[0058] Next, in step 1, an authentication application protocol data unit (APDU) exchange is performed. This step contains several sub-steps. On the gateway side, in sub-step la, the authentication and transit application 304, running on the target processor 120, relying on the UWB authentication key 306 stored in the secure access module for cryptographic operations (e.g. NXP MIFARE secure access module) of the target secure element 122, initiates the UWB authentication. On the mobile device side, in sub-step lb, the APDU is received by the UWB authentication applet 308 running in the mobile secure element 108, and the responses required for the authentication are performed, which can include selecting an ADF and responding to the generic authentication 1 and generic authentication 2 commands. Additionally, in sub-step lc, the RDS is generated by the UWB authentication applets 308 on both sides from the exchanged cryptographic material. In the mobile device, once the authentication is completed, the RDS is transferred to the SUS 310 running in the mobile secure element 108.

[0059] Next, in step 2, the UWB session ID is sent by the target device 104 to the mobile device 102 as application data through a data message payload information element (IE). In particular, the UWB session ID is sent from the authentication and transit application 304 via the target UWBS 124 to the mobile UWBS 110 of the mobile device 102.

[0060] Next, in step 3, the proprietary message in the data message payload IE is decoded and the mobile UWBS 110 retrieves the UWB session ID.

[0061] Next, at step 4, the RDS is obtained by the mobile UWBS 110 from the SUS 310 using a Get_RDS (Session ID) APDU. In embodiments, a secure channel between the mobile UWBS 110 and the SUS 310 can have been opened in advance, which the mobile UWBS can use to obtain the RDS from the SUS. In the target device 104, the RDS is transmitted by the UWB authentication applet 308 to the target UWBS.

[0062] Next, at steps 5 and 6, the session key obtained from the RDS is used for secure ranging and fee transactions. Specifically, at step 5, the session key is used for secure ranging between the target UWBS 124 and the mobile UWBS 110. The session key is also used for fee transactions by the authentication and relay app 304 to the mobile relay app 302, which can depend on a relay key 312 stored in the target secure element 122, which can depend on a service provider applet (SPA) 314 running in the mobile secure element 108. This can only occur if the distance measured in the secure ranging is within a certain threshold, e.g., a fee transaction area of 1 meter by 1.5 meters around the target device 104.

[0063] Referring now to Figure 4 , Figure 4 is a flow diagram of a process for transmitting a challenge 1 value and a challenge 2 value in a UWB link in a UWB communication system 100 according to embodiments of the present application. The process begins with an authentication preparation operation. First, a FiRa applet is selected by the authentication and relay app 304 of the target device 104 to initiate an authentication process, as indicated by arrow 402. In response to the selection, a confirmation message is transmitted from the target secure element 122 to the authentication and relay app 304, as indicated by arrow 404.

[0064] Next, an application dedicated file (ADF) of the FiRa applet is selected by the target UWBS 124, as indicated by arrow 406. The ADF corresponds to a data structure within an application data structure of the target device, e.g., an application and application specific data. In response to the ADF selection, a confirmation message is transmitted from the FiRa applet to the target UWBS 124, as indicated by arrow 408.

[0065] Next, an initiate transaction command is transmitted from the authentication and relay app 304 to the target secure element 122, as indicated by arrow 410. In response to the initiate transaction command, a remote internal authentication (IA) command is generated by the target secure element 122 with some parameters needed to derive a challenge 1 value, and transmitted to, e.g., the target UWBS 124, as indicated by arrow 412. Figure 4The UWB-enabled mobile device 102, shown, transmits the IA command. However, the remote IA command with the challenge 1 parameter is not transmitted in-band from the target device 104 to the mobile device. Rather, the remote IA command is transmitted out-of-band from the target device to the mobile device. In embodiments, the IA command is transmitted in a FiRa-based hybrid UWB schedule (HUS) control message (CM Type 3). Thus, the challenge 1 parameter is transmitted as content in the HUS control message to the mobile device, which can significantly improve the link budget. Once the HUS controller (i.e., one mobile device) receives the message, the HUS controller derives the challenge 1 value with the following parameters:

[0066] a. Session ID - This is a 4 byte field of the HUS master session running on the gateway.

[0067] b. Padding - This is an 8 byte field of a known value, which is configured by the UWB command interface (UCI) programming. The padding field is composed of a 4 byte session ID and a 4 byte station name ASCII value. For example, the session ID can be 0x00010002 and the ACII can be 0x535A544E.

[0068] c. Epoch time - This is a 4 byte field composed of a time of day in the format of YYYY / MM / DD / Hr converted to a thirty-two (32) bit epoch time. The epoch time is shared through Bluetooth Low Energy (BLE) and after the mobile device receives the epoch time, the device application (e.g., mobile relay application 302) can configure the device UWB S 110 through the UCI.

[0069] Once the remote IA response is generated by the FiRa applet running on the target secure element 122 and forwarded to the authentication and relay application 304, the authentication and relay application 304 of the target device 104 configures the HUS master session and transmits the remote IA command to the target UWB S 124, as indicated by arrow 414. After the HUS master session has been configured, the HUS CM Type 3 message with the header IE containing the session ID and padding configured through the UCI is transmitted from the mobile UWB S 110 from the target UWB S 124, as indicated by arrow 416.

[0070] Upon receiving a HUS CM Type 3 message, the mobile UWBS 110 forms a challenge 1 value for a remote IA command by concatenating the session ID, padding value, and epoch value from the most significant bit (MSB) to the least significant bit (LSB). This challenge 1 value can be, for example, a 128-bit value. The mobile UWBS 110 then issues a remote IA command with the challenge 1 value, as indicated by arrow 418. In response to the remote IA command with the challenge 1 value, the mobile security element 108 generates a challenge 2 value, which can be, for example, a 128-bit value, and returns the challenge 2 value to the mobile UWBS 110, as indicated by arrow 420. The challenge 2 value, as a response to the remote IA command, is stored at the mobile device 102.

[0071] Simultaneously, target device 104 uses contention-based ranging to track the proximity of the mobile device, as indicated by arrow 422. When mobile device 102 is at a configured or predefined proximity, target device 104 adds the mobile device's device address to the ranging management list (RML). Simultaneously, ranging response messages (RRMs) with challenge 2 values ​​are sent from mobile device 102 until the device address exists as an RML entry in the RML. Therefore, the RRM with challenge 2 values ​​is ultimately transmitted from the mobile UWBS 110 that generated the RRM to the target UWBS 124, as indicated by arrow 424, and the challenge 2 values ​​are transmitted from the target UWBS 124 to the target secure element 122, as indicated by arrows 426 and 428.

[0072] In the embodiment, RRM is... Figure 5 The frame format shown is transmitted as an RRM frame 500 with a challenge 2 value. For example... Figure 5 As shown, RRM frame 500 includes various Physical Service Data Unit contents. RRM frame 500 includes Frame Control (FC) and Header IE, which are part of the Media Access Control (MAC) Header (MHR). RRM frame 500 also includes a header terminator, a fixed Measurement Reporting Message Type 3 (MRMT3) payload, MRMT3 payload content, a fixed Data IE payload, a Data IE (without application data), application data length, a Link Layer (LL) header, Challenge 2 and cipher, an enc tag, and a Frame Check Sequence (FCS).

[0073] In this embodiment, a link is created between the mobile secure element 108 and the target secure element 122 to transmit the RRM frame 500 with a challenge 2 value. Additionally, the challenge 2 value is encoded with a proprietary header value and stored by the mobile device 102 until the mobile device switches to secure ranging and fee transactions after receiving a session ID within the same band.

[0074] After the target secure element 122 has received the challenge 2 value, the RDS is transmitted from the target secure element 122 to the target UWBS 124, as indicated by arrows 430 and 432. The session ID is then transmitted from the target UWBS 124 to the mobile UWBS 110, as indicated by arrow 434. The mobile UWBS 110 then retrieves the RDS from the mobile secure element 108, e.g., using a GET command with the session ID, as indicated by arrows 436 and 438. The RDS retrieved from the mobile secure element 108 is sent from the mobile UWBS 110 to the target UWBS 124, as indicated by arrow 440. After verifying the extracted RDS against the RDS generated by the target secure element (i.e., by comparing the two RDSs to verify that the two RDSs match), the RDS_NTF message is transmitted from the target UWBS 124 to the authentication and relay application 304, as indicated by arrow 442.

[0075] In response, the appropriate UWB session key is selected by the authentication and relay application 304 from the target secure element 122, as indicated by arrow 444. Depending on the selected MOT key, a fee transaction is performed between the target secure element 122 and the mobile secure element 108 using a small program running on the secure element.

[0076] Reference Figure 6 A process flow diagram describing a method according to an embodiment of the application. At block 602, a parameter associated with a first authentication value is broadcast from an ultra-wideband (UWB) system of a target device, the parameter being sufficient to derive the first authentication value at a plurality of mobile devices. At block 604, a plurality of second authentication values are received at the UWB system from the plurality of mobile devices. At block 606, a ranging data set for each valid second authentication value is received at the UWB system from a target secure element, the ranging data set being used to authenticate a mobile device associated with the valid second authentication value for secure communication.

[0077] Although the operations of the methods are illustrated and described in a particular order, the order of the operations can be altered so that certain operations can be performed in an inverse order or so that certain operations can be performed, at least in part, concurrently with other operations. In another embodiment, instructions or sub-operations of distinct operations can be implemented in an intermittent and / or alternating manner.

[0078] It can also be noted that at least some of the operations of the methods described herein can be implemented using software instructions stored on a computer-usable storage medium for execution by a computer. For example, an embodiment of a computer program product includes a computer-usable storage medium to store a computer readable program.

[0079] The computer-usable or computer-readable storage medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device). Examples of a non-transitory computer-usable and computer-readable storage medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, and an optical disk.

[0080] Alternatively, embodiments of the application can be implemented entirely in hardware or in an implementation that includes both hardware and software elements. In embodiments that use software, the software can include, but is not limited to, firmware, resident software, microcode, etc.

[0081] While specific embodiments of the application have been described and illustrated, the application is not to be limited to the specific forms or arrangements of parts so described and shown. The scope of the application is to be defined by the claims appended hereto and their equivalents.

Claims

1. An ultra-wideband (UWB) system, characterized in that, include: UWB transceiver, the UWB transceiver being configured to transmit and receive signals within a specific frequency range; as well as A UWB processor, operatively connected to the UWB to process the signal, is configured to: Broadcast parameters associated with the first authentication value, said parameters being sufficient to derive the first authentication value at multiple mobile devices; Receive multiple second authentication values ​​from the plurality of mobile devices; and The target security element receives a ranging dataset for each valid second authentication value, the ranging dataset being used to authenticate the mobile device associated with the valid second authentication value for secure communication via the UWB transceiver.

2. The system according to claim 1, characterized in that, The UWB processor is configured to broadcast the parameters associated with the first authentication value in a command message.

3. The system according to claim 2, characterized in that, The UWB processor is configured to broadcast the parameters associated with the first authentication value in a UWB scheduling control message.

4. The system according to claim 2, characterized in that, The UWB processor is configured to broadcast out-of-band the parameters associated with the first authentication value, compared to the second authentication value from the plurality of mobile devices.

5. The system according to claim 1, characterized in that, The parameters associated with the first authentication value include at least two of the following: a session identifier, a padding value, and an epoch value.

6. The system according to claim 1, characterized in that, The ranging dataset for each valid second authentication value includes at least a session identifier.

7. The system according to claim 1, characterized in that, Each of the second authentication values ​​is a value formed by concatenating at least some of the parameters associated with the first authentication value from the most significant bit (MSB) to the least significant bit (LSB).

8. The system according to claim 1, characterized in that, The UWB processor is further configured to receive a ranging dataset from a specific mobile device among the plurality of mobile devices, and to compare the ranging dataset from the specific mobile device with a corresponding ranging dataset from the target security element for the specific mobile device.

9. A method, characterized in that, include: Parameters associated with a first authentication value are broadcast from the ultra-wideband UWB system of the target device, the parameters being sufficient to derive the first authentication value at multiple mobile devices; Receive multiple second authentication values ​​from the plurality of mobile devices at the UWB system; as well as At the UWB system, a ranging dataset for each valid second authentication value is received from the target security element. The ranging dataset is used to authenticate the mobile device associated with the valid second authentication value for secure communication.

10. A target device, characterized in that, include: A security element, which is used to run at least one application and store data; as well as An ultra-wideband (UWB) system, operatively coupled to the secure element, wherein the UWB system is configured to: Transmitting and receiving signals within a specific frequency range; Broadcast parameters associated with the first authentication value, said parameters being sufficient to derive the first authentication value at multiple mobile devices; Receive multiple second authentication values ​​from the plurality of mobile devices; and A ranging dataset is obtained from the security element for each valid second authentication value, the ranging dataset being used to authenticate the mobile device associated with the valid second authentication value for secure communication.

Images