Section 33: Communicating with Mexico

From Nlets Wiki
Jump to: navigation, search

Communicating with Mexico (DQ/DR, KQ/DR & RQ/RR)

This section describes Nlets user access to Mexican Commercial Driver License (DQ/DR), Driver History (KQ/KR) and Commercial License Plate records (RQ/RR).

Overview

Effective November 21, 1991 the United States recognized the commercial driver license issued by the Secretara de Comunicaciones y Transportes (SCT), the Licencia Federal de Conductor, as being comparable to a U.S. issued commercial driver license (CDL).

U.S. enforcement officers can encounter Mexican drivers with a licencia federal legally operating a commercial motor vehicle (CMV) in the U.S., as Mexican for-hire carriers can legally operate from Mexico through the U.S. to a destination in Canada.

Though rare, such movements are legal because the carrier is not engaged in commerce in the U.S., and thus does not need U.S. operating authority issued by the U.S.DOT, Federal Motor Carrier Safety Administration (FMCSA). Such operations DO need to comply with all safety and other requirements, e.g., driver licensing, fuel taxes, registration taxes, vehicle safety.

  • In addition, Mexican based (domiciled) private carriers, principally owned by a U.S. investor, may obtain operating authority from the FMCSA to operate anywhere in the United States.

There are a number of companies which claim this is their ownership status and have obtained this type of operating authority. Although they may legally operate anywhere in the U.S., these carriers are restricted to hauling private carriage (their own products). It is also possible for a Mexican domiciled company to get similar authority for hauling exempt commodities (basically agricultural.) All such Mexican companies can use Mexican drivers with a licencia federal issued by the SCT to operate their commercial vehicles in the U.S.

Mexican Commercial Driver License

The Licencia Federal Information System (LIFIS) responds to Nlets user driver license queries (DQ & KQ), regardless of the type of ORI assigned to them, e.g. FBI or Nlets.

Users can inquire to the Licencia Federal Information System (LIFIS) to obtain license and status information about federally issued Mexican commercial driver licenses, just as such driver license queries (DQ & KQ) can be made to U.S. state driver license files for any U.S. issued license.

  • A license status inquiry to the LIFIS is made by addressing a driver license query (DQ or KQ) message to the destination address of "MX".
  • All inquiries and responses are in a fixed format.
  • At this time, the LIFIS application only supports requests using the operator license number (OLN).
  • Name and date of birth inquiries are not currently supported, but are anticipated in the future.
  • On inquiries, the current version of the Licencia Federal Information System (LIFIS) requires the driver license inquiry message (DQ) to include the class (or classes) of license(s) shown on the document at the end of the OLN field.


Section33-DQ(MX).jpg


Section33-KQ(MX).jpg


Section33-RQ(MX).jpg


Help Files

The LIFIS provides a variety of help or support functions. These are grouped into three categories:

  • Automatic application diagnostic responses,
  • On-line request-able HELP files, and
  • Person to person help.

Automatic Diagnostic Responses/Error Messages

There are a large number of analysis filters built into the LIFIS application. They assist users by identifying, in detail, whether the inquiry information may have entered incorrectly, and if so, what the user should double check.

A list of automatic diagnostics and a list of test driver's license numbers (OLNs) are given below.

On-line HELP Files

Users may access the standard help file Nlets has always supported for providing explanatory or supplementary information provided by the application. For the LIFIS application it covers highlights of Mexican federal commercial driver licenses, and the Licencia Federal Information System (LIFIS).

The HELP file is accessed by sending an Administrative Message (AM) to: MXOLNHELP

Also, the LIFIS application supports a number of detailed application specific help files that can be requested. All of these are obtained by sending a Driver License Query (DQ) to the LIFIS with the correct OLN identifying which HELP file the user wants to receive as a response.

The LIFIS application supports long explanatory HELP response messages. These are an expansion on the administrative HELP information available using the Nlets administrative message requesting help. These help responses are provided by the LIFIS application, rather than the Nlets system.

Send a standard Driver Query (DQ) message to the LIFIS application. This is done by sending a DQ addressed to MX. In the OLN field, place one of the following values:

HELP You will receive definitions of other available help messages.
HELPDEF You will receive short definitions for all Mexican categorys.
HELPOLN You will receive rules for constructing a correct OLN for an inquiry to
the LIFIS.
HELPTESTGOOD You will receive the list of test OLNs contained on this page.
HELPTESTERROR You will receive the list of test OLNs illustrating responses you
will get for different input errors.

Person to Person HELP

An 800 number is supported by the designated Federal Motor Carrier Safety Administration (FMCSA) provider, TML Information Services, for answering questions regarding responses provided by the LIFIS.

The number for LIFIS data questions is (800) 743-7891.

  • If calling during the day, the phone will be answered by an automated response unit.
  • The correct menu option to select is to press 5.

This 800 number may also be used to report requests for improvements, revisions, etc.

Decisions on changes, upgrades, etc. will primarily be made at the Federal Motor Carrier Safety Administration headquarters offices in Washington, DC. Users are encouraged to identify problems, difficulties, recommended improvements, etc.

The LIFIS contains both an identification of which version of LIFIS is responding to each inquiry, and a message reference number. Thus any user who either does not understand a response received, or has a suggestion for a change in the data received, can use the LIFIS version number and message number as part of explaining what response they received.

End system, and/or Nlets switch, service support should be coordinated through normal Nlets operations center contacts. If you need assistance in initial debugging for system implementation, TML will be glad to work with the staff at the Nlets operations center. The lead for coordinating such initial debugging calls should be through the Nlets operations center who can monitor messages when they are sent and returned.

Driver's License Query Requirements

To send a Driver License Query (DQ) or Driver History Query (KQ) to the Mexican LIFIS application the following entries are required:

  • Standard Nlets header, message type, sending ORI
  • Destination code MX
  • License number from the license document (must always include the alphabetic characters which are the beginning of the license number)
  • Category(s).

No spaces or non-alphanumeric characters are allowed.

The control field and control characters are optional.

The Driver's License Query (DQ) requirements for a Mexican licencia federal inquiry are similar to a Driver's License Query (DQ) or Driver's History Query (KQ) inquiry for a U.S. state issued driver license.

The table below provides a description of the Mexican driver's license number field requirement.

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<j:PersonDriverLicenseID>

Mexican
OLN/
plus up to 4
category(s)

8-15
plus
4 i.e.,
8-19

Alphanumeric

Combination of
DL# and
"CATEGORY"
of Mexican
driver license
in DL#/CAT
order. DL#
must begin with
alpha letters
shown as
beginning of
number on the
document. If
more than one
"category"
shown on license,
they may all be
included in OLN
field after the
DL#. This
combination
currently is the
required
equivalent of
U.S. OLN for
Mexican LIFIS.

Free form fields such as "RSTR/", "STATUS/", "OLT/", etc., are used to provide information on any restrictions, status of the license, the U.S. equivalent CDL class and explanations regarding verifications in process.

All information will be provided in English.

If there are any questions on this or any other parts of the response, consult the LIFIS HELP file by sending a DQ message addressed to MX, and with an OLN value of HELP, or send an Administrative Message (AM) to MXOLNHELP.

In the near future there are plans to begin supporting a KQ (driver history) capability. Initially this will be for convictions that result from citations issued by U.S. enforcement while the driver was operating in the U.S. This capability to respond to a KQ inquiry was expected to begin initial operations sometime in 2000.

Test Driver's License Number (OLN) and Category Values

WARNING: These test OLN values must be entered EXACTLY, or an error message likely will be received in response, instead of the expected illustrative results.

Test Driver's License Number Responses

The responses to these test Driver's License Numbers (OLNs) demonstrate what the user will receive in response to an inquiry about a license number that conforms to all the rules.

Response Code: Explanation:
FIRST123456C

The response, msg # 1, is for a driver who is not yet in the
database, and this is the first inquiry ever received for that driver.

SUBSE123456C

The response, msg # 2, is for a subsequent inquiry on a driver who
was previously inquired about, but has not yet been verified by
Mexico, and is within the currently allowed 15 day grace period.

GOOD123456AC

The response, msg # 3, is for a driver who is in the database, has a
valid license, and no restrictions.

RSEYE123456E

The response, msg # 4, is for a driver who is in the database, has a
valid license, a restriction for wearing eye glasses, and the
equivalent of an endorsement for carrying hazardous materials.

RSMEX123456B

The response, msg # 5, is for a driver who is in the database, has a
valid license, but is restricted to operating a CMV only in Mexico, i.e.
is NOT valid to operate a CMV in the U.S.

DISQU123456A

The response, msg # 6, is for a driver who is in the database as
having previously had a valid license, but has subsequently been
disqualified from operating a CMV in the U.S.

BAD123456B

The response, msg # 7, is for a driver license number that was not
issued.

EXPIR123456C

The response, msg # 8, is for a driver license number that was
confirmed by Mexico at some point in the past, but has more
recently been confirmed with Mexico to be expired.

RENEW123456B

The response, msg # 9, is for a driver license number that was
confirmed by Mexico at some point in the past, but now needs to be
reconfirmed to verify if the driver has obtained the required two
year re-validation.

MULTI123456ADE

The response, msg # 10, is for a driver who has a combination of
categorys. This example shows that category was not issued,
and that categorys A and D were issued, but on different dates.

ZCHIH2000201234C

The response, msg # 11, is for the special case of a license number
with more that six (6) digits issued by the State of Chihuahua, and
with a non-alphanumeric dash (-) shown on the license document, but
omitted from the inquiry. Note. There is a corresponding error
message shown below for this special case where the user included
the non-alphanumeric character (dash), and therefore will receive an
error message, provided the user's system will allow sending a
non-alphanumeric character in an OLN.

NORSP123456C

The response, msg # 12, is for records where the driver has been
encountered in the U.S., an inquiry made on the status of the driver,
and the record was either not in the database, or needed to be
updated, e.g. to verify whether the driver obtained the necessary
two-year re-validation, and Mexico City headquarters failed to
respond within the interim 15 days allowed.

Error Messages - Driver's License Number/Category Construction

Version 2.2 of LIFIS has seven possible error details explaining specific problems that could occur with the Driver's License Number (OLN) that was entered. The appropriate explanatory detail would be received in the section of the error message labeled as Error Details.

The error response messages are numbered consecutively, 21 through 27 as follows.

Error #: Error Message:
21

YOU DID NOT INCLUDE THE LETTERS WHICH ARE THE BEGINNING OF THE
LICENSE NUMBER.
NOTE: IF THE LICENSE DOCUMENT SAYS IT IS A LICENCIA FEDERAL, AND
DOES NOT HAVE LETTERS AS THE BEGINNING OF THE LICENSE NUMBER, THEN
THE DOCUMENT PROBABLY IS FRAUDLENT. TAKE APPROPRIATE ACTION.

22

THE LETTERS YOU INCLUDED AS THE BEGINNING OF THE LIC. No. ARE NOT
FOR A VALID MEXICAN FEDERAL OFFICE THAT ISSUES LICENCIAS
FEDERALES.
NOTE: IF THE DOCUMENT SAYS IT IS A LICENCIA FEDERAL, AND THESE
ARE THE LETTERS THAT ARE THE BEGINNING OF THE LICENSE NUMBER, THEN
THE DOCUMENT PROBABLY IS FRAUDULENT. TAKE APPROPRIATE ACTION.

23

YOU DID NOT INCLUDE A VALUE AT THE END OF THE OLN FOR A CLASS
(CATEGORY) YOU WANT TO VERIFY. THE CATEGORY(S) YOU SHOULD
INCLUDE AT THE END OF THE OLN ARE SHOWN ON THE UPPER, RIGHT
FRONT OF THE LICENSE DOCUMENT OVER THE PHOTO.
NOTE: IF THE LICENSE DOCUMENT SAYS IT IS A LICENCIA FEDERAL, AND
THERE IS NO CATEGORY OVER THE PHOTO ON THE DOCUMENT, THEN THE
DOCUMENT PROBABLY IS FRADULENT. TAKE APPROPRIATE ACTION

24

THERE ARE TOO MANY NUMERIC DIGITS IN THE NUMBER ENTERED.
NOTE: IF THE LICENSE DOCUMENT SAYS IT IS A LICENCIA FEDERAL, AND
THERE ARE THIS MANY NUMERIC DIGITS IN THE LICENSE NUMBER, THEN
THE DOCUMENT PROBABLY IS FRAUDLENT. TAKE APPROPRIATE ACTION.

25

A LICENCIA FEDERAL LICENSE NUMBER DOES NOT HAVE MORE THAN FIVE
LETTERS AS THE BEGINNING OF THE OPERATOR LICENSE NUMBER. THIS
ENTRY HAS TOO MANY LETTERS.
NOTE: IF THE LICENSE DOCUMENT HAS THIS MANY LETTERS AS THE
BEGINNING OF THE LICENSE NUMBER, THEN THE DOCUMENT IS PROBABLY
FRAUDLENT. TAKE APPROPRIATE ACTION.

26

ONLY LETTERS AND NUMBERS MAY BE ENTERED. IF THE LICENSE
NUMBER ON THE DOCUMENT CONTAINS A NON-ALPHANUMERIC
CHARACTER, RESUBMIT THE INQUIRY WITHOUT THE NON-ALPHANUMERIC
CHARACTER.

27

YOU ENTERED A LETTER IN ONE OF THE SIX NUMERIC POSITIONS WHICH
MUST CONTAIN ONLY NUMERIC DIGITS.
NOTE: IF THE LICENSE DOCUMENT SAYS IT IS A LICENCIA FEDERAL, AND
THERE IS A LETTER IN THE NUMERIC PORTION OF THE LICENSE NUMBER,
THEN THE DOCUMENT PROBABLY IS FRAUDLENT. TAKE APPROPRIATE ACTION.

The responses to these test records demonstrate the analysis information the user will receive in response to a license number (OLN) that does NOT conform to all the rules for the interim LIFIS.

Response Code: Explanation:
123456A

The response, msg # 21, is for a license number that does not
contain the required beginning letters from the license document.

WLOCA123456B

The response, msg # 22, is for a license number that begins with
letters that are not a valid combination for an existing Mexican
SCT office.

MISSC123456

The response, msg # 23, is for a license number which does not
provide at least one category at the end of the license number.

TOOMN12345678901E

The response, msg # 24, is for a license number that includes too
many digits in the number for all locations.

TOOMLETTERS12A

The response, msg # 25, is for a license number that includes too
many letters at the beginning of the license number. Currently
they generally do not exceed 5.

ZCHIH2-000223456C

The response, msg # 26, is for a license number that contains a
non-alphanumeric character. The user is advised to omit the
non-alphanumeric character and resubmit the inquiry. Some
systems contain internal edits and will not allow sending this
as a value for a license number (OLN).

LTR1234E6A

The response, msg # 27, is for a license number with a letter in
one of the 6 digit positions normally following the introductory
letters, but before the final category.

INCORR123456D

The response, msg # 30, is for what the user may receive if a test
ONL value is incorrectly entered. More likely, the user will get
a normal analysis error message.

Mexico Commercial License Plate File

The Mexico Commercial License Plate File is housed in Mexico City and is provided to Nlets through the Federal Motor Carriers Safety Administration's connection in New York. All commercial vehicles in Mexico that cross Mexican state boundaries and into the United States are required to be federally registered and included in this file. If the vehicle is commercial and you receive a "not on file", it is not registered and is in violation of US-DOT operating authority. Queries can be run by license plate only.

More information may be obtained by contacting TML Information Services 1-800-743-7891 (press 5 for Mexico check services via Nlets). This file has been available for many years so it is very possible that your message switch may already be prepared to send RQs to destination MX.

The following records can be used for testing:

  • LIC/014DD1.LIY/2002.LIT/PC
  • LIC/AAA3649.LIY/2011.LIT/PC

General notes:

  • MX responds to an RQ only on Federal License Plate Registration (Interstate CMV). Mexican State issued license plates are not in the database, thus, any query to a Mexican State Credential will result in a negative response.
  • If a MX RQ results in a "NOT ON FILE", the vehicle is not registered in Mexico and is in violation of US-DOT Operating Authority.

Possible license plate status codes:

  • ASSIGNED (ONLY POSITIVE STATUS)
  • AVAILABLE
  • CANCELLED
  • STOLEN OR LOST
  • WITHDRAWAL PER RULE
  • DAMAGED
  • WITHDRAWAL NOTICE
  • WITHDRAWAL IMPOUNDED
  • NOT RECEIVED
  • WITHDRAWAL EXCHANGED
  • WITHOUT DECAL
  • INCOMPLETE DATA ENTR
  • PREVENTIVE SEIZURE
  • MISSING
  • WITHDRAWAL NEW NAME
  • UNDER INSPECTION

Possible registrant status codes:

  • REGISTERED
  • WITHDRAWN
  • SUSPENDED
  • BANKRUPT
  • WITHDRAWN/MERGER
  • UNDER INVESTIGATION

Top

GJXDM (DEPRECATED)

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

Top

NIEM

Communicating with Mexico NIEM Specifications

This section describes NIEM format and provides NIEM examples for Mexican Driver's License queries and responses (DQ/DR) and Mexican Driver History queries and responses (KQ/KR).

Users can inquire to the Licencia Federal Information System (LIFIS) to obtain license and status information about federally issued Mexican commercial driver licenses, just as such driver license queries (DQ/KQ) can be made to U.S. state driver license files for any U.S. issued license.

  • A license status inquiry to the LIFIS is made by addressing a driver license query (DQ/KQ) message to the destination address of "MX".
  • All inquiries and responses are in a fixed format.
  • At this time, the LIFIS application only supports requests using the operator license number (OLN).
  • Name and date of birth inquiries are not currently supported, but are anticipated in the future.

Other search criteria that may also be added include the following:

  • RFC number, a number that has been used by Mexico and is somewhat similar to the U.S. social security number (SSN); and/or
  • A new identification number Mexico is planning to issue called the CURP

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: Query by Driver's License Number (DQ), Query by Driver History (KQ), Driver License Response from Mexico (DR) and Driver History Response from Mexico (KR).

Query Formats

Query by Driver's License Number (OLN) (DQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Person
  This element encapsulates the information about the person being queried.

    nc:DriverLicense
    Details about a license issued to a person granting driving privileges.

      nc:DriverLicenseIdentification
      Details about a driver license identifier or driver license permit identifier, including the number and state.

        nc:IdentificationID
        A value that identifies something.
        This element should contain the person's driver license number.

  n2:ImageIndicator
  Y if an image is being requested if available.

Query by Drivers History Number (OLN) (KQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Person
  This element encapsulates the information about the person being queried.

    nc:DriverLicense
    Details about a license issued to a person granting driving privileges.

      nc:DriverLicenseIdentification
      Details about a driver license identifier or driver license permit identifier, including the number and state.

        nc:IdentificationID
        A value that identifies something.
        This element should contain the person's driver license number.

  n2:ImageIndicator
  Y if an image is being requested if available.

Response Formats

Driver License Response from Mexico (DR)

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

  Response Text (n:ResponseText)


  This element will contain the free text 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.

Driver History Response from Mexico (KR)

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

  Response Text (n:ResponseText)


  This element will contain the free text 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.

Communicating with Mexico NIEM Examples

Example 1: Drivers License query to Mexico.

<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>DQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>MX</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DQ">
    <n2:Person>
      <nc:DriverLicense>
        <nc:DriverLicenseIdentification>
          <nc:IdentificationID>111111111</nc:IdentificationID>
        </nc:DriverLicenseIdentification>
      </nc:DriverLicense>
    </n2:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: Drivers License response from Mexico.

<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>DR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MXLIC0000</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>11234</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>61230</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="DR">
    <n2:ResponseText>
         GARCIA-MARTINEZ@JUAN
         LICENSING OFFICE/, , MEXICO.
         MAILING ADDR/USUMACINTAS, AZTECA, JUAREZ,
         JUAREZ, CHIHUAHUA 31111, MEXICO.
         SEX/M. DOB/01011950. HGT/5 10. WGT/236. EYE/. RFC/XXXX111111.
         RSTR/EYE GLASSES.
         OLN/AAAA111111.
         CATEGORY/A. EXPIRES/01012020. STATUS/VALID.
         OLT/B - TRUCK & TRACTOR WITH MORE THAN 3 AXLES, DOUBLES/TRIPLES,
         TANKS; NO HAZARDOUS MATERIAL.
 
         NOTE: MX ELICENCIA IS UP: RESPONSE COMES FROM MX ELICENCIA
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 3: Commercial License Plate query to Mexico.

<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>RQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>MX</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RQ">
    <nc:Vehicle>
      <nc:ConveyanceRegistrationPlateIdentification>
        <nc:IdentificationID>111XX1</nc:IdentificationID>
        <nc:IdentificationCategoryText>PC</nc:IdentificationCategoryText>
        <nc:IdentificationExpirationDate>2013</nc:IdentificationExpirationDate>
      </nc:ConveyanceRegistrationPlateIdentification>
      <nc:VehicleIdentification />
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 4: Commercial License Plate query response from Mexico.

<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>MXLIC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2012</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>11:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2012</nh2:MessageSendDate>
    <nh2:MessageSendTime>11:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>01239</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>81239</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="RR">
    <n2:ResponseText>
         LIC/111XX1
         TRANSPORTES JUAN GARCIA, S.A. DE C.V.
         AV. HECTOR MARTINEZ, FRACC. ALAMEDA, CD. JUAREZ, CHIH 32000.
         VIN/1XXXXXXX1XXX11111.VYR/2000.ENGINE_NO/11111111
         LIT/TRACTOR - 3 AXLES.VMA/MEXICO
         LIC_STATUS/ASSIGNED.LIC_ISSUED/01012005
         REGISTRANT_RFC/AAA1111111A1.REGISTRANT_STATUS/REGISTERED
         LIC_CLASS/FREIGHT MOTOR.VST/TRACTOR
         LIC_SERVICE/GENERAL
 
         NOTE: THIS IS A RESPONSE FROM MX AUTHORIZATIONS INFORMATION SYSTEM
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 5: Drivers History query to Mexico.

<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>KQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>MX</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="KQ">
    <n2:Person>
      <nc:DriverLicense>
        <nc:DriverLicenseIdentification>
          <nc:IdentificationID>111111111</nc:IdentificationID>
        </nc:DriverLicenseIdentification>
      </nc:DriverLicense>
    </n2:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: Drivers History response from Mexico.

<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>KR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>MXLIC0000</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>11234</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>61230</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="KR">
    <n2:ResponseText>
         GARCIA-MARTINEZ@JUAN
         LICENSING OFFICE/, , MEXICO.
         MAILING ADDR/USUMACINTAS, AZTECA, JUAREZ,
         JUAREZ, CHIHUAHUA 31111, MEXICO.
         SEX/M. DOB/01011950. HGT/5 10. WGT/236. EYE/. RFC/XXXX111111.
         RSTR/EYE GLASSES.
         OLN/AAAA111111.
         CATEGORY/A. EXPIRES/01012020. STATUS/VALID.
         OLT/B - TRUCK & TRACTOR WITH MORE THAN 3 AXLES, DOUBLES/TRIPLES,
         TANKS; NO HAZARDOUS MATERIAL.
 
         NOTE: MX ELICENCIA IS UP: RESPONSE COMES FROM MX ELICENCIA
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

Communicating with Mexico Legacy Specifications

This section describes the Legacy format and provides examples for Mexican Commercial Driver's License queries and responses (DQ/DR), Driver History queries and responses (KQ/KR) and Mexican Commercial License Plate records (RQ/RR).

Users can inquire to the Licencia Federal Information System (LIFIS) to obtain license and status information about federally issued Mexican commercial driver licenses, just as such driver license queries (DQ/KQ) can be made to U.S. state driver license files for any U.S. issued license.

  • A license status inquiry to the LIFIS is made by addressing a driver license query (DQ/KQ) message to the destination address of "MX".
  • All inquiries and responses are in a fixed format.
  • At this time, the LIFIS application only supports requests using the operator license number (OLN).
  • Name and date of birth inquiries are not currently supported, but are anticipated in the future.

Other search criteria that may also be added include the following:

  • RFC number, a number that has been used by Mexico and is somewhat similar to the U.S. social security number (SSN); and/or
  • A new identification number Mexico is planning to issue called the CURP.

Query Formats

To send a Driver Query (DQ/KQ) to the Mexican LIFIS application the following entries are required:

  • Standard Nlets header, message type, sending ORI
  • Destination code MX
  • License number from the license document (must always include the alphabetic characters which are the beginning of the license number)
  • Category(s).
  • No spaces or non-alphanumeric characters are allowed.
  • The control field and control characters are optional.

The table below provides a description of the Mexican driver's license number requirement.

Legacy
Prefix:
Field
Size:
Explanation:

Mexican
OLN/
plus up to 4
category(s)

8-15
plus
4
i.e.,
8-19

Combination of DL# and "CATEGORY" of Mexican driver license
in DL#/CAT order.
DL# must begin with the alpha letters shown as the beginning of
the number on the document.
If there is more than one "category" shown on the license, they
may all be included in the OLN field after the DL#.
This combination currently is the required equivalent of the U.S.
OLN for the Mexican LIFIS.

Free form fields such as "RSTR/", "STATUS/", "OLT/", etc., are used to provide information on any restrictions, status of the license, the U.S. equivalent CDL class and explanations regarding verifications in process.

All information will be provided in English.

If there are any questions on this or any other parts of the response:

Consult the LIFIS HELP file by sending a DQ message addressed to MX with an OLN value of HELP or send an Administrative Message (AM) to MXOLNHELP.

Mexican Driver's License Responses from LIFIS (DR)

The sections below provide examples of various possible responses to Driver's License Queries.

Driver's License Response Example - Valid License (DR)

Response indicating the queried driver is in the database, has a valid license and no restrictions.

Response (DR)

DR.MXOLN0000
01:09 11/01/2000 01572
01:09 11/01/2000 01433 GA0250300
TXT
MSG # 3. TEST RECORD. RESPONSE FROM VERSION 2.2, LIFIS.
MUESTRA-EJEMPLO, JUAN GARCIA
ORIGINAL LICENSING OFFICE/NUEVO LAREDO, TAMAULIPAS, MEXICO.
SEX/M. DOB/011546. HGT/5'10". WGT/180. EYE/BROWN. RFC/MUEJ460115.
OLN/GOOD123456.
CATEGORY/A. EXPIRES/10142001. STATUS/VALID.
OLT/A - ANY BUS.
CATEGORY/C. EXPIRES/10142001. STATUS/VALID.
OLT/C - STRAIGHT TRUCKS (MAXIMUM OF 3 AXLES INCLUDING ANY TOWED TRAILER)
EXCLUDING HAZMATS.

Driver's License Response Example - First Check/Interim (DR)

It is possible a driver can be stopped and checked who may have a valid licencia federal, but has not yet been added to the current database.

The officer will receive a response like the following example.

Response indicating this is the first inquiry ever received for that driver who may not yet in the database.

Response (DR)

DR.MXOLN0000.(standard Nlets header)
TXT
MSG # 1. RESPONSE FROM VERSION 2.2, LIFIS.
OLN/FIRST123456.
CATEGORY/C. STATUS/CHECKING.
OLT/C - THIS CATEGORY IS FOR STRAIGHT TRUCKS (MAXIMUM OF 3 AXLES INCLUDING ANY
TOWED TRAILER) EXCLUDING HAZMATS.
THIS LICENSE NUMBER IS NEW TO THE INTERIM LIFIS, AND WILL BE VERIFIED WITHIN 15
DAYS. IF THE MEXICO CITY SCT HEADQUARTERS DOES NOT SEND THE NECESSARY LICENSE
INFORMATION WITHIN 15 DAYS, THE COMPUTER WILL BEGIN ANSWERING THAT THE LICENSE
IS ASSUMED NOT VALID.
IF THE LICENSE DOCUMENT SAYS "LICENCIA FEDERAL DE CONDUCTOR," AND CONTAINS
EMBOSSMENTS ON ALL YEARS IN THE REF FIELD, UP TO AND INCLUDING THE MOST RECENT
YEAR REQUIRED, THEN ADVISE DRIVER THE COMPUTER SYSTEM IS VERIFYING THE LICENSE.

The driver should be advised that if the Mexico City SCT headquarters does not verify to the computer system within 15 days that the license is valid, he or she will then be placed out of service.

Driver's License Response Example - Subsequent Check (DR)

It is possible a subsequent inquiry could be made on a driver during the currently allowed 15 day computer validation period while waiting on the data to be obtained and placed in the database. In such cases the officer will receive a response indicating how many days remain from the original 15 days, as indicated in the following example.

Response on a subsequent inquiry on a driver who was previously inquired about, but has not yet been verified by Mexico, and is within the currently allowed 15 day grace period.

Response (DR)

DR.MXOLN0000.(standard Nlets header)
TXT
MSG # 2. TEST RECORD. RESPONSE FROM VERSION 2.2, LIFIS.
OLN/SUBSE123456.
CATEGORY/C. STATUS/CHECKING.
OLT/C - THIS CATEGORY IS FOR STRAIGHT TRUCKS (MAXIMUM OF 3 AXLES INCLUDING ANY
TOWED TRAILER) EXCLUDING HAZMATS.
THIS LICENCIA FEDERAL WAS RECENTLY INQUIRED ABOUT AND IS IN THE PROCESS OF BEING
VERIFIED. IF THE MEXICO CITY SCT HEADQUARTERS OFFICE DOES NOT RESPOND WITHIN
(x) DAYS, THE LIFIS WILL BEGIN REPORTING THE STATUS OF THIS CATEGORY AS ASSUMED
NOT VALID.
IF LICENSE DOCUMENT SAYS "LICENCIA FEDERAL DE CONDUCTOR," AND CONTAINS
EMBOSSMENTS ON ALL YEARS IN REF FIELD, UP TO AND INCLUDING THE MOST RECENT YEAR
REQUIRED, THEN ADVISE DRIVER ONLY (x) DAYS REMAIN FOR THE MEXICO CITY SCT OFFICE
TO VERIFY THIS LICENCIA FEDERAL.

The value for (x) is the number of days calculated by the program as remaining from the original 15 days, i.e., since the original inquiry was made and the computer record created.

Driver's License Response Example - No Response Within 15 Days (DR)

If the Mexican SCT/DGAF headquarters office in Mexico City does not provide the interim agreed information about a licencia federal driver license number within the agreed 15 days, the LIFIS database will be updated to show the status of that driver license number as ASSUMED NOT VALID.

When the U.S. has failed to receive a response within the agreed interim 15 days, the officer would receive a response like the following:

Response records where the driver has been encountered in the U.S., an inquiry made on the status of the driver, and the record was either not in the database, or needed to be updated, e.g. to verify whether the driver obtained the necessary two-year re-validation, and Mexico City headquarters failed to respond within the interim 15 days allowed.

Response (DR)

DR. MXOLN0000.(standard Nlets header)
TXT
MSG # 12. TEST RECORD. RESPONSE FROM VERSION 2.2, LIFIS.
OLN/NORSP123456.
CATEGORY/C. STATUS/ASSUME NOT VALID.
OLT/C - THIS CATEGORY IS FOR STRAIGHT TRUCKS (MAXIMUM OF 3 AXLES INCLUDING ANY
TOWED TRAILER) EXCLUDING HAZMATS.
THIS LICENSE NUMBER/CLASS COMBINATION WAS NOT VALIDATED BY THE MEXICO CITY SCT
HEADQUARTERS WITHIN THE 15 DAY AGREE TIME PERIOD. UNTIL THE MEXICO CITY SCT
HEADQUARTERS VALIDATES THIS LICENSE NUMBER/CLASS COMBINATION, IT SHOULD BE
TREATED AS NOT VALID IN THE U.S.
EVEN IF THE DRIVER HAS A LETTER OR DOCUMENT FROM A LOCAL SCT OFFICE TO THE
CONTRARY, THIS LICENSE SHOULD BE TREATED AS NOT VALID IN THE U.S. IT IS AGAINST
MEXICO CITY HEADQUARTERS POLICY FOR LOCAL SCT OFFICES TO ISSUE A LETTER
CONTRADICTING THE LICENSE DOCUMENT. ALL LICENCIA FEDERAL VALIDATIONS MUST COME
THROUGH MEXICO CITY HEADQUARTERS OFFICIAL CHANNELS, AND BE INCLUDED IN THE LIFIS
DATABASE TO BE VALID IN THE U.S.

Mexico Commercial License Plate File

The format for vehicle registration query on a license number is:

Entry: # Char.: Explanation:
RQ. 2 Message type followed by a period.
Message Header 13 - 24 Standard input message header may include control field.
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
LIC/ 4 Prefix to identify license plate.
License number 1-10 License number, alphanumeric only, followed by a period.
LIY/ 4 Prefix to identify license year.
License year 2-4 License year followed by a period; 2-4 numeric digits.
LIT/ 4 Prefix to identify license type.
License type 2 License type; 2 character designating type of license.

Queries can be only be run by license plate, VIN queries are currently not supported.

Communicating with Mexico Legacy Examples

Example 1: Drivers query to Mexico.

DQ.AZNLETS20.MX.TXT
OLN/AAAA111111

Example 2: Drivers response from Mexico.

DR.MXLIC0000
09:00 01/01/2012 11234
09:00 01/01/2012 61230 AZNLETS20
TXT
GARCIA-MARTINEZ@JUAN</syntaxhighlight>
LICENSING OFFICE/, , MEXICO.
MAILING ADDR/USUMACINTAS, AZTECA, JUAREZ,
JUAREZ, CHIHUAHUA 31111, MEXICO.
SEX/M. DOB/01011950. HGT/5 10. WGT/236. EYE/. RFC/XXXX111111.
RSTR/EYE GLASSES.
OLN/AAAA111111.
CATEGORY/A. EXPIRES/01012020. STATUS/VALID.
OLT/B - TRUCK & TRACTOR WITH MORE THAN 3 AXLES, DOUBLES/TRIPLES,
TANKS; NO HAZARDOUS MATERIAL.
 
NOTE: MX ELICENCIA IS UP: RESPONSE COMES FROM MX ELICENCIA

Example 3: Commercial License Plate query to Mexico.

RQ.AZNLETS20.MX.TXT
LIC/111XX1.LIY/2013.LIT/PC

Example 4: Commercial License Plate query response from Mexico.

RR.MXLIC0000
11:00 01/01/2011 01239
11:00 01/01/2011 81239 AZNLETS20
TXT
LIC/111XX1</syntaxhighlight>
TRANSPORTES JUAN GARCIA, S.A. DE C.V.
AV. HECTOR MARTINEZ, FRACC. ALAMEDA, CD. JUAREZ, CHIH 32000.
VIN/1XXXXXXX1XXX11111.VYR/2000.ENGINE_NO/11111111
LIT/TRACTOR - 3 AXLES.VMA/MEXICO
LIC_STATUS/ASSIGNED.LIC_ISSUED/01012005
REGISTRANT_RFC/AAA1111111A1.REGISTRANT_STATUS/REGISTERED
LIC_CLASS/FREIGHT MOTOR.VST/TRACTOR
LIC_SERVICE/GENERAL
 
NOTE: THIS IS A RESPONSE FROM MX AUTHORIZATIONS INFORMATION SYSTEM

Example 5: Drivers History query to Mexico.

KQ.AZNLETS20.MX.TXT
OLN/AAAA111111

Example 6: Drivers History response from Mexico.

KR.MXOLN0000


11:22 01/01/2015 00231
11:22 01/01/2015 00231 AZNLETS20
TXT
NAME: JUAN GARCIA-MARTINEZ
PRIMARY CONTACT ADDRESS: USUMACINTAS, AZTECA, JUAREZ, CHIHUAHUA 31111, MEXICO.
COUNTRY: 1
COUNTY: HUMBERTO VALDEZ RICHAUD
LOCATION COUNTY: HUMBERTO VALDEZ RICHAUD
DATE OF BIRTH: 1950-01-01
GENDER: Male


*** DRIVER LICENSE DETAILS ***
DRIVER AUTHORIZATION ID: AAAA111111
JURISDICTION AUTHORITY CODE: MX
ISSUE DATE: 2015-01-01
EXPIRATION DATE: 2016-01-01
DRIVER ENDORSEMENT: Doubles/Triples
DRIVER ENDORSEMENT: Tank
DRIVER LICENSE COMMERCIAL CLASS CODE: A
LICENSED COMMERCIAL DRIVER: YES
DRIVER LICENSE COMMERCIAL STATUS: Valid
DRIVER HISTORY CONVICTION QUANTITY: 0
DRIVER HISTORY WITHDRAWAL QUANTITY: 0

Top

Downloads

Download DQ Schema

Download DR Schema

Download DR Stylesheet

Download KQ Schema

Download KR Schema

Download KR Stylesheet

Download RQ Schema

Download RR Schema

Download RR Stylesheet

Top