# US 10,122,833 B2 · Time stamp conversion in an interface bridge > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,122,833 B2 - Document ID: US10122833B2 - Status: Granted - Kind: B2 - Application number: 15/048,752 - Filed: 2016-02-19 - Published: 2017-08-24 - Granted: 2018-11-06 - Earliest claimed: 2016-02-19 - Assignees: Raytheon Company - Applicants: Raytheon Company - Inventors: Bradley Bomar Hammel - Web page: https://patentgrep.com/patent/US10122833B2 ## CPC - H04L 69/08: Protocols for interworking; Protocol conversion - B64D 7/00: Arrangement of military equipment, e.g. armaments, armament accessories or military shielding, in aircraft; Adaptations of armament mountings for aircraft (dropping bombs or the like B64D1/00) - B64D 47/02: Arrangements or adaptations of signal or lighting devices - G06F 1/14: Time supervision arrangements, e.g. real time clock - G06F 13/102: {where the program performs an interfacing function, e.g. device driver (G06F13/105 takes precedence; contention policies within device drivers G06F9/4881; scheduling within device drivers G06F9/52)} - G06F 13/20: for access to input/output bus - G06F 13/4027: {using bus bridges (G06F13/4022 takes precedence)} - H04L 47/562: {Attaching a time tag to queues} - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 69/28: Timers or timing mechanisms used in protocols - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - B64D: EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENT OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A technology is described for converting a time tag in a message. The message can be received from a military standard-1760 (MIL-STD-1760) bus controller. The message can include a time tag in accordance with a first time stamping technique. The time tag in the message can be detected as being in accordance with the first time stamping technique based on contents of the message. A recomputed time tag for the message can be determined in accordance with a second time stamping technique. The message with the recomputed time tag can be transmitted to a Universal Armament Interface (UAI) remote terminal. ## Claims ### Claim 1 An interface bridge positioned between a military standard-1760 (MIL-STD-1760) bus controller of a legacy platform and a Universal Armament Interface (UAI) remote terminal of a UAI weapon to convert a time tag derived using a first time stamping technique that is within a message sent by the legacy platform to a time tag that uses a second time stamping technique that is compatible with the UAI weapon, the interface bridge comprising one or more processors and memory configured to: receive, at the interface bridge, a message that includes the time tag from the MIL-STD-1760 bus controller, wherein the time tag in the message is derived in accordance with the first time stamping technique which is incompatible with the UAI remote terminal; detect, at the interface bridge, that the time tag in the message is derived in accordance with the first time stamping technique based on contents of the message; and determine, at the interface bridge, a recomputed time tag for the message in accordance with a second time stamping technique when the time tag in the message is derived in accordance with the first time stamping technique, wherein the recomputed time tag is determined by: reading a value of a real time clock (RTC) upon receiving the message from the MIL-STD-1760 bus controller at the interface bridge and storing the value of the RTC as a message receipt time, wherein the message from the MIL-STD-1760 bus controller includes a latency value, computing a clock value that corresponds to the recomputed time tag of the message to be sent by the interface bridge to the UAI remote terminal, and at least one of subtracting the latency value from the message receipt time in order to determine the recomputed time tag, or subtracting the latency value from the clock value that corresponds to a rollover reset value of the RTC and adding the message receipt time in order to determine the recomputed time tag. ### Claim 2 (depends on 1) The interface bridge of claim 1, wherein the one or more processors and memory are further configured to transmit the message with the recomputed time tag to the UAI remote terminal. ### Claim 3 (depends on 2) The interface bridge of claim 2, wherein the message with the time tag is received at a remote terminal (RT) side of the interface bridge and the message with the recomputed time tag is transmitted from a bus controller (BC) side of the interface bridge to the UAI remote terminal. ### Claim 4 (depends on 1) The interface bridge of claim 1, wherein the clock value that corresponds to the recomputed time tag is a 16-bit clock value. ### Claim 5 (depends on 1) The interface bridge of claim 1, wherein the one or more processors and memory are further configured to transmit a mode code 17 (MC-17) message that contains a value of the RTC at the time of transmission to the UAI remote terminal. ### Claim 6 (depends on 1) The interface bridge of claim 1, wherein the time tag is a 16-bit value that indicates an age or latency of the message when received at the interface bridge. ### Claim 7 (depends on 1) The interface bridge of claim 1, wherein the interface bridge is configured to determine the recomputed time tag in the message in accordance with the second time stamping technique when the UAI remote terminal is configured to reject messages that are not time tagged in accordance with the second time stamping technique. ### Claim 8 (depends on 1) The interface bridge of claim 1, wherein the MIL-STD-1760 bus controller is onboard an aircraft and the UAI remote terminal is associated with a weapon platform. ### Claim 9 (depends on 1) The interface bridge of claim 1, wherein the MIL-STD-1760 bus controller operates as a standard 1553 bus controller and the UAI remote terminal operates as an enhanced bit rate (EBR)-1553 remote terminal. ### Claim 10 (depends on 1) The interface bridge of claim 1, wherein the first time stamping technique is a data latency technique and the second time stamping technique is a time-tag technique. ### Claim 11 (depends on 1) The interface bridge of claim 1, wherein the message received from the MIL-STD-1760 bus controller is one of a periodic transfer alignment message, a time message and a target data message. ### Claim 12 (depends on 1) The interface bridge of claim 1, wherein the interface bridge is configured to convert messages in a MIL-STD-1760 data format received from the MIL-STD-1760 bus controller to messages in a UAI data format for transmission to the UAI remote terminal. ### Claim 13 A method for converting a time tag derived using a first time stamping technique that is within a message sent by a legacy platform to a time tag that uses a second time stamping technique that is compatible with a Universal Armament Interface (UAI) weapon, the method comprising: receiving, at an interface bridge positioned between a military standard-1760 (MIL-STD-1760) bus controller of the legacy platform and a UAI remote terminal of the UAI weapon, a message from the MIL-STD-1760 bus controller that includes the time tag that is derived in accordance with the first time stamping technique which is incompatible with the UAI remote terminal; determining, at the interface bridge, a recomputed time tag for the message in accordance with the second time stamping technique when the time tag is derived in accordance with the first time stamping technique, wherein determining the recomputed time tag comprises: reading a value of a real time clock (RTC) upon receiving the message from the MIL-STD-1760 bus controller at the interface bridge and storing the value of the RTC as a message receipt time, wherein the message from the MIL-STD-1760 bus controller includes a latency value, computing a clock value that corresponds to the recomputed time tag of the message to be sent by the interface bridge to the UAI remote terminal, and at least one of subtracting the latency value from the message receipt time in order to determine the recomputed time tag, or subtracting the latency value from the clock value that corresponds to a rollover reset value of the RTC and adding the message receipt time in order to determine the recomputed time tag; and transmitting, from the interface bridge to the UAI remote terminal, the message with the recomputed time tag. ### Claim 14 (depends on 13) The method for claim 13, further comprising detecting that the time tag in the message received from the MIL-STD-1760 bus controller is derived in accordance with the first time stamping technique based on contents of the message. ### Claim 15 (depends on 13) The method of claim 13, further comprising transmitting a mode code 17 (MC-17) message that contains a value of the RTC at the time of transmission to the UAI remote terminal. ### Claim 16 A method for conversion of a time tag within a message sent by a legacy platform to a time tag that is compatible with a Universal Armament Interface (UAI) weapon, the method comprising: receiving a message, from a military standard-1760 (MIL-STD-1760) bus controller of the legacy platform, that includes a time tag in accordance with a first time stamping technique which is incompatible with the UAI weapon; detecting that the time tag in the message is in accordance with the first time stamping technique based on contents of the message; determining a recomputed time tag for the message in accordance with a second time stamping technique, wherein determining the recomputed time tag comprises: reading a value of a real time clock (RTC) upon receiving the message from the MIL-STD-1760 bus controller and storing the value of the RTC as a message receipt time, wherein the message from the MIL-STD-1760 bus controller includes a latency value, computing a clock value that corresponds to the recomputed time tag of the message to be sent to the UAI weapon, and at least one of subtracting the latency value from the message receipt time in order to determine the recomputed time tag, or subtracting the latency value from the clock value that corresponds to a rollover reset value of the RTC and adding the message receipt time in order to determine the recomputed time tag; and transmitting the message with the recomputed time tag to a UAI remote terminal of the UAI weapon. ### Claim 17 (depends on 16) The method of claim 16, further comprising converting the message received from the MIL-STD-1760 bus controller from a MIL-STD-1760 data format received to a UAI data format prior to transmission of the message to the UAI remote terminal. ### Claim 18 (depends on 16) The method of claim 16, wherein the recomputed time tag is determined using an interface bridge that is positioned in line between the MIL-STD 1760 bus controller and the UAI remote terminal. ### Claim 19 (depends on 16) The method of claim 16, wherein the MIL-STD-1760 bus controller is onboard an aircraft and the UAI remote terminal is associated with a weapon platform. ### Claim 20 (depends on 16) The method of claim 16, further comprising transmitting the rollover reset value of the RTC to the UAI remote terminal. ### Claim 21 (depends on 13) The method of claim 13, wherein the first time stamping technique is a data latency technique and the second time stamping technique is a time-tag technique. ### Claim 22 (depends on 13) The method of claim 13, further comprising transmitting, from the interface bridge to the UAI remote terminal, the rollover reset value of the RTC. ### Claim 23 (depends on 13) The method of claim 13, wherein the rollover reset value is a maximum value before the RTC is reset to zero.