Section 43: LoJack Transactions

From Nlets Wiki
Jump to: navigation, search

LoJack Transactions (LE/LR)

Overview

All information about LoJack has been provided to Nlets by LoJack. More information about LoJack can be found at their web site http://www.lojack.com/. Additionally you can download their Functional Specification document Lojack State Spec (PDF File).

LoJack is a Stolen Vehicle Recovery System currently operational in 26 states. The LoJack system components include computer systems interfaced to Law Enforcement agencies in such a way that the entry of a stolen vehicle report by law enforcement will result in the activation of a LoJack Unit in the stolen vehicle so the police can quickly find and recover the stolen vehicle. When the stolen vehicle is activated, police vehicles equipped with LoJack tracking devices receive signal strength, direction, and a 5 character reply code from the stolen vehicle. When the police query on the 5 character reply code, the law enforcement system returns the stolen vehicle report so they can identify and recover the stolen vehicle. When the stolen vehicle report is canceled or cleared, the stolen vehicle signal is automatically de-activated.

The destination for a LoJack transaction is "LJ".

There are two data flows for the LoJack interface:

  • NCIC Vehicle file data messages (EV, MV, LV, XV, CV)
  • REPLY, CHECK, and QUIET messages from a police user terminal
XML Message Type: Legacy Message Type: Message Key:
n2:InquiryDescriptionText
LE LoJack Transaction

The LoJack System requires a feed of NCIC Vehicle file data (EV, MV, LV, XV and CV) from the participating state. This data is matched against a database of LoJack equipped vehicles. When there is a match by VIN, the LoJack system responds to the entering agency with LoJack information and queries NCIC to determine the Stolen/Not Stolen status.

Police agencies in the participating state need to be able to send transactions (Query, Check, and Quiet) with the LoJack Reply Code and receive the responses.

In order to meet the NCIC requirements regarding secondary dissemination and still provide the stolen vehicle information needed for officer safety, the participating state will need to query NCIC and provide the NCIC response to the originator after the VIN and LoJack status is determined.

This page does not give every combination of message formats for data to LoJack or responses from LoJack. The developer should refer to the NCIC manual or its successor for the comprehensive list of messages.

Query Notes

Below is a table of LoJack transactions.

LoJack Code: Data Requirements: Translation
EV VIN, MAKE (VMA) and YEAR (VYR) Entry of a vehicle into the database.
MV VIN, License (LIC) and NCIC number (NIC) Modify the record of a vehicle in the database.
LV VIN, License (LIC) and NCIC number (NIC) Locate the whereabouts of a vehicle. Activate or
de-activation LoJack unit.
XV VIN, License (LIC) and NCIC number (NIC) Cancel the activation or de-activation of the LoJack unit.
CV VIN, License (LIC) and NCIC number (NIC) Clear the the activation or de-activation of the LoJack unit.
REPLY 5 character reply code for the stolen vehicle

Returns the stolen vehicle information from NCIC
and the LoJack system send a Speed-up message
to the stolen vehilce for easier tracking.

CHECK 5 character reply code for the stolen vehicle

Performs an emergency update to the LoJack
database, if a vehicle is stolen before the
information can be entered normally into the
LoJack database.

QUIET 5 character reply code for the stolen vehicle

Turns off the LoJack signal, even though the
vehicle is still entered as stolen. Used mostly
for surveillance.

The LoJack system will respond to each "LE" (or "LQ") message with an "LR" response whether or not the Vehicle is a LoJack Vehicle. If the VIN matches a LoJack vehicle, there are two responses. The first says that NCIC is being queried. The second returns the NCIC result.

The LoJack system requires a copy of NCIC Stolen Vehicle messages in order to match the VIN (or VIN + Make + Year) on entry (EV) and Modify (MV), and to match the NIC, VIN, Plate, and Case # on Locate (LV), Cancel (XV) and Clear (CV). Records which match LoJack vehicles are used to Activate or Deactivate the LoJack unit in the stolen vehicle. The State system can validate the stolen vehicle file record and then send the message to LoJack, or wait for an NCIC acknowledgement before sending the record to the LoJack system.

When Entering a Stolen Vehicle (EV), the State needs to send a VIN, MAKE (VMA), YEAR (VYR). This information is needed to Activate or De-Activate the associated LoJack units. The LoJack system will query NCIC by VIN. The response is used to determine that the VIN is stolen in NCIC and to populate a NIC field to use in the Locate, Cancel, Clear transactions.

States need to send all LV, XV, and CV transactions to the LoJack system so the LoJack system can De-Activate the associated LoJack units. The LoJack system will query NCIC by VIN and determine that the VIN is no longer stolen in NCIC.

QUERY, CHECK and QUIET Reply Codes

QUERY

Query uses the word "REPLY" in the LoJack message. When a police officer in a LoJack equipped police vehicle picks up a stolen vehicle signal, it displays a unique number on the screen. A query on this reply code returns the stolen vehicle information from NCIC and the LoJack system sends a Speed-up message to the stolen vehicle for easier tracking.

CHECK

Sometimes a vehicle is stolen before the LoJack information is in the LoJack database. The easiest solution is for LoJack to add the information to the LoJack database with an emergency update. LoJack would provide the Reply Code to a police agency. Then the police can run the reply code as a "CHECK" which causes the unit in the vehicle to activate if the record is STOLEN VEHICLE in NCIC. This function should have limited availability, with a different screen or message key. It is important to NOT to have the QUERY and CHECK on the same screen. In some states the police both CHECK and REPLY because they are not sure which to run, and this causes extra messages to be sent to the towers.

QUIET

Sometimes the police want to turn the LoJack signal off, even though the vehicle is still entered as stolen. A "QUIET" command was developed for surveillance and is used by police in many jurisdictions. This function should be limited to a few agencies or stations, particularly specialized auto theft squads who would organize a surveillance. The function should NOT be available to all departments, as a mistake would cause the de-activation of a stolen vehicle transmitter.

Response Notes

LoJack uses a convention to indicate what action is required by the participating state on a LoJack response.

  • If no VIN and No "REPLY CODE" in response: Not LoJack equipped. It is not necessary to build a response to user.
  • If there is no VIN and "REPLY CODE =" in response, the State system needs to deliver the LoJack response to user.
  • VIN/ in response: Not LoJack equipped. It is not necessary to build a response to the user.
  • VIN: in response: Preliminary message from LoJack: The State system needs to deliver the LoJack response to user.
  • "VIN =" in response: Secondary message from LoJack: Participating state should query NCIC on behalf of the entering agency and return both the NCIC response and the LoJack Response to the user.

Note: This response also applies to EV and MV with short VINs that don't match on VIN + Make + Year. LoJack matches on VIN only when the length of the VIN is 8 characters or more. To avoid false activations, LoJack matching on short VINs (7 characters or less) also requires exact match of VMA and VYR.

QUERY, CHECK and QUIET response codes

  • If a LoJack Reply Code starts with "000", it is a Police Training Unit, and can be ignored by the police. This applies to Query, CHECK and QUIET commands.
  • If a LoJack Reply Code contains a "B", "I" or "Z" it is an invalid Reply Code. The letter "O" is converted to the number "0". This applies to Query, CHECK and QUIET commands.
  • If a LoJack Reply Code is not found in the database, it returns an "UNKNOWN REPLY CODE" message. This applies to Query, CHECK and QUIET commands.
  • If a LoJack Reply Code matches a LoJack vehicle, a preliminary message is sent to the user with the VIN. This applies to Query, CHECK and QUIET commands.
  • If a LoJack Reply Code matches a LoJack vehicle, and the vehicle is stolen in NCIC, a Speed Up message is sent to the user, and a speed-up command is sent to the stolen vehicle. This applies to Query ONLY.
  • If a LoJack Reply Code matches a LoJack vehicle, and the vehicle is NOT stolen in NCIC, a De-Activate message is sent to the user, and a De-Activate command is sent to the stolen vehicle. This applies to Query, CHECK and QUIET.
  • If a LoJack Reply Code matches a LoJack vehicle, and the vehicle is stolen in NCIC, an Activation message is sent to the user, and an Activate command is sent to the stolen vehicle. This applies to CHECK ONLY.
  • If a LoJack Reply Code matches a LoJack vehicle, and the vehicle is stolen in NCIC, a De-Activation by QUIET message is sent to the user, and a De-Activate command is sent to the stolen vehicle. This applies to QUIET ONLY.

Help File

There currently is no help file for a LoJack transaction.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

LoJack NIEM Specifications

This section includes format specifications and an example of a NIEM LoJack Query and Response (LE/LR).

There are no edits or requirements on a LoJack transaction, other than standard Nlets XML formatting.

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: LoJack Message Query (LE) & LoJack Message Response (LR).

Query Formats

LoJack Message Query (LE)

Inquiry Data (n2:NLETSInquiryData)
This element will contain all elements specific to this transaction.

  Query Text (n2:InquiryDescriptionText)
  This element will contain the free text message. Nlets recommends the use of


  

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the response does not contain any characters illegal in XML.

Response Formats

LoJack Message Response (LR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Response Text (n2:ResponseText)
  This element will contain the free text message response. Nlets recommends the use of


  

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the response does not contain any characters illegal in XML.

LoJack NIEM Examples

Example 1: Entry (EV) message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.EV.AZNLETS20.....111111XXX111.2000.INGS.CE.AI.BGE/ONG.20120101.
       200000000000X000...TAKEN IN BURGLARY /MODEL 185..</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: Response from LoJack on an Entry message.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MAMSP0043</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2012</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2012</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>12345</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="LR">
    <n2:ResponseText>
      <![CDATA[LOJACK.
       VEHICLE ENTERED IS FOR A KNOWN INSTALLED LOJACK UNIT
       QUERY IS BEING SENT TO NCIC TO DETERMINE VEHICLE STATUS FOR
       VIN:200000000000X000]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n:NLETS>

Example 3: Modify (MV) message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.MV.AZNLETS20.NIC/X111111111.OCA/12-000000.
       MIS/NINJA 250 WITH A BLACK GAS TANK</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 4: Modify response from LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MAMSP0043</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2012</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2012</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>12345</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="LR">
    <n2:ResponseText>
      <![CDATA[LOJACK.
       VEHICLE MODIFIED IS FOR A KNOWN INSTALLED LOJACK UNIT
         QUERY IS BEING SENT TO NCIC TO DETERMINE VEHICLE STATUS FOR
         VIN:AA1AA1AA111111111]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n:NLETS>

Example 5: Confirmation of stolen vehicle response from LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MAMSP0043</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2012</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2012</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>12345</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="LR">
    <n2:ResponseText>
      <![CDATA[LOJACK.
       MODIFIED LOJACK UNIT IS BEING ACTIVATED
         NCIC INDICATES THAT VEHICLE IS STOLEN
         VIN = AA1AA1AA111111111
         NIC = X111111111
 
 
         MKE/STOLEN VEHICLE - HOLD FOR LATENTS
         ORI/AZNLETS20
         VIN/AA1AA1AA111111111 VYR/2010
         VMA/SUZI VMO/CYL VST/MC VCO/BLK/YEL DOT/20120101
         OCA/AA11-11-11111
         VLD/20120101
         MIS/H0LD F0R FINGERPRINT PR0CESSING IN MARICOPA C0UNTY
         MIS/0NLY, VM0/XXXX111, 1X111, JOHN SMITH, RPTR JOHN SMITH, 602-555-1234,
         MIS/602-555-1234
         NIC/X111111111 DTE/20120101 1000 EDT DLU/20120101 1000 EDT
         ORI IS PHOENIX PD 602 555-1234
         IMMED CONFIRM RECORD WITH ORI]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n:NLETS>

Example 6: Locate (LV) message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.
         LV.AZNLETS20.LIC/XX11111.OCA/111111111.20120101.0900000</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 7: Cancel (XV) message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.XV.AZNLETS20.NIC/X111111111.
      OCA/11-11111.20120101</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 8: Clear (CV) message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.CV.AZNLETS20.NIC/X111111111.
       OCA/X11-11111.20120101.AZ0000000</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 9: A De-activate response sent from LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MAMSP0043</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2012</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2012</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>12345</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="LR">
    <n2:ResponseText>
      <![CDATA[LOJACK.
         LOJACK UNIT IS BEING DE-ACTIVATED
         NCIC INDICATES THAT VEHICLE IS NOT STOLEN
         VIN = 1XXXX11X11X111111
 
 
         NO RECORD VIN/1XXXX11X11X111111]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n:NLETS>

Example 10: QUERY message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.REPLY.XXX11</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 11: A Reply response from LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MAMSP0043</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2012</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2012</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>12345</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="LR">
    <n2:ResponseText>
      <![CDATA[LOJACK.
         LOJACK REPLY CODE = XXX11
         LOJACK REPLY CODE IS FOR A KNOWN UNIT
         QUERY BEING SENT TO NCIC TO DETERMINE VEHICLE STATUS FOR
         VIN:XXXXX11X111111111]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n:NLETS>

Example 12: CHECK message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.CHECK.XXX11</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 13: QUIET message sent to LoJack.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>LE</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LJ</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="LE">
    <n2:n2:InquiryDescriptionText>LOJACK.QUIET.XXX11</n2:InquiryDescriptionText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

LoJack Legacy Specifications

This section describes Legacy format specifications and provides examples for LoJack Transactions (LE/LR).

Query Formats

Enter the following to send a Legacy LoJack Message:

Legacy Prefix: Field Size: Data Requirements: Translation:
VIN/ 1-20 Alphanumeric only Vehicle identification
number
And either:
VMA/ 2-4 See NCIC Manual Vehicle make
VYR/ 2-4 See NCIC Manual Vehicle model year date
Or:
LIC/ 1-10 Alphanumeric only License number
NIC/ 1-10 See NCIC Manual NCIC number

QUERY, CHECK and QUIET transactions only require the 5 character reply code for a stolen vehicle.

LoJack Legacy Examples

Example 1: Entry (EV) message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.EV.AZNLETS20.....111111XXX111.2000.INGS.CE.AI.BGE/ONG.20120101.
200000000000X000...TAKEN IN BURGLARY /MODEL 185.

Example 2: Response from LoJack on an Entry message.

LR.MAMSP0043
09:00 01/01/12 12345
09:00 01/01/12 12345 AZNLETS20
TXT
VEHICLE ENTERED IS FOR A KNOWN INSTALLED LOJACK UNIT
QUERY IS BEING SENT TO NCIC TO DETERMINE VEHICLE STATUS FOR
VIN:200000000000X000

Example 3: Modify (MV) message sent to LoJack.

LE.NLETS20.LJ.TXT
LOJACK.MV.AZNLETS20.NIC/X111111111.OCA/12-000000.
MIS/NINJA 250 WITH A BLACK GAS TANK

Example 4: Modify response from LoJack.

LR.MAMSP0043
09:00 01/01/12 12345
09:00 01/01/12 12345 AZNLETS20
TXT
LOJACK.
VEHICLE MODIFIED IS FOR A KNOWN INSTALLED LOJACK UNIT
QUERY IS BEING SENT TO NCIC TO DETERMINE VEHICLE STATUS FOR
VIN:AA1AA1AA111111111

Example 5: Confirmation of stolen vehicle response from LoJack.

LR.MAMSP0043
09:00 01/01/12 12345
09:00 01/01/12 12345 AZNLETS20
TXT
LOJACK.
MODIFIED LOJACK UNIT IS BEING ACTIVATED
NCIC INDICATES THAT VEHICLE IS STOLEN
VIN = AA1AA1AA111111111
NIC = X111111111
 
 
MKE/STOLEN VEHICLE - HOLD FOR LATENTS
ORI/AZNLETS20
VIN/AA1AA1AA111111111 VYR/2010
VMA/SUZI VMO/CYL VST/MC VCO/BLK/YEL DOT/20120101
OCA/AA11-11-11111
VLD/20120101
MIS/H0LD F0R FINGERPRINT PR0CESSING IN MARICOPA C0UNTY
MIS/0NLY, VM0/XXXX111, 1X111, JOHN SMITH, RPTR JOHN SMITH, 602-555-1234,
MIS/602-555-1234
NIC/X111111111 DTE/20120101 1000 EDT DLU/20120101 1000 EDT
ORI IS PHOENIX PD 602 555-1234
IMMED CONFIRM RECORD WITH ORI

Example 6: Locate (LV) message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.LV.AZNLETS20.LIC/XX11111.OCA/111111111.20120101.0900000

Example 7: Cancel (XV) message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.XV.AZNLETS20.NIC/X111111111.OCA/11-11111.20120101

Example 8: Clear (CV) message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.CV.AZNLETS20.NIC/X111111111.
OCA/X11-11111.20120101.AZ0000000

Example 9: A De-activate response sent from LoJack.

LR.MAMSP0043
09:00 01/01/2012 12345
09:00 01/01/2012 12345 AZNLETS20
TXT
LOJACK.
LOJACK UNIT IS BEING DE-ACTIVATED
NCIC INDICATES THAT VEHICLE IS NOT STOLEN
VIN = 1XXXX11X11X111111
 
 
NO RECORD VIN/1XXXX11X11X111111

Example 10: QUERY message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.REPLY.XXX11

Example 11: A Reply response from LoJack.

LR.MAMSP0043
09:00 01/01/2012 12345
09:00 01/01/2012 12345 AZNLETS20
TXT
LOJACK.
LOJACK REPLY CODE = XXX11
LOJACK REPLY CODE IS FOR A KNOWN UNIT
QUERY BEING SENT TO NCIC TO DETERMINE VEHICLE STATUS FOR
VIN:XXXXX11X111111111

Example 12: CHECK message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.CHECK.XXX11

Example 13: QUIET message sent to LoJack.

LE.AZNLETS20.LJ.TXT
LOJACK.QUIET.XXX11

Top

Downloads

Download LE Schema

Download LR Schema

Download LR Stylesheet

Top