Web Services
for Justice Information Sharing
NCJA National Forum 2003
Steve Correll, Executive Director, NLETS
Bob Slaski, AISLE Co-Principal Investigator
1
NLETS Mission Statement
The mission of the National Law Enforcement Telecommunication
System is to provide, within a secure environment, an international
criminal justice telecommunications capability that will benefit to the
highest degree, the safety, security, and the preservation of human life
and the protection of property. NLETS will assist those national and
international governmental agencies and other organizations with
similar missions who enforce or aid in enforcing local, state, federal, or
international laws or ordinances.
2
NLETS
 Non-profit corporation chartered by the States – funded
by user fees collected from membership
 Members are all States and most Federal Agencies –
30,000 Agencies and 410,000 access devices in the U.S.
alone, over 500,000 with Canada – 34M trans/mo.
 NLETS Board of Directors is composed of State Police
Executives
 All members make up the NLETS Council, 50 states,
federal agencies, territories.
 Low bureaucracy factor = nimble organization
3
NLETS Services
 Access to key State databases, particularly, Mv
and DL/DMV records, criminal histories, etc.
 Access to special databases, e.g. Canadian files,
Hazmat, GSA Fleet, INS, FAA registrations,
NDPIX, vehicle impounds, import/export files
 Message delivery – Terminal-to-terminal
messaging and broadcast messages, e.g.
National “Alert”, APB, Amber Alerts
 7x24x365
4
NLETS Evolution
 Evolved from an operator-to-operator network
 Responses are not standard, i.e. state specific
 Officers need simple standard response plus
images
 Answer: Define standard XML responses
5
Accelerated Information Sharing
for Law Enforcement (AISLE)
National Institute of Justice
National Law Enforcement Telecommunication
System
Wisconsin Crime Information Bureau
Advanced Technology Systems
6
AISLE Project Goals
 Accelerate info sharing for the entire U.S. law
enforcement community by adopting and
deploying XML Web Services technology for
interstate inquiry/responses
 Facilitate integrated justice info exchanges by
promoting common standards
 Contribute operational experience with XML Web
Services to the standards process
7
Public Safety Challenges
 Sharing information
 Lowering costs
 Streamlining justice processes
 Maintaining mission critical services
 Improving security
 Supporting a technologically diverse community
8
NLETS XML Resolution
“Resolved that [NLETS] recommends XML
as the future for all new NLETS
transactions …”
Resolution of the NLETS Operational Procedures
Committee Meeting on September 12-13, 2000
9
What are Web Services?
 Web Services is a specific set of standards for
data exchange – not a name for general operation
on the World Wide Web
 Web Services is to data transfer
what XML is to data format
 Web Services Interoperability Organization
 Founding members – IBM, Microsoft, HP
 Over 100 industry leaders http://www.ws-i.org/
10
Web Services Standards
 XML defines the detailed Web Service data
 Web Service Definition Language (WSDL)
describes the Web Service interface
 Simple Object Access Protocol (SOAP) transports
Web Service information
 Universal Description, Discovery, and Integration
(UDDI) provides a Web Service directory
11
Why Web Services?
 Standard approach for connecting diverse systems
 Easy to program
 No licensing fee, open systems
 Ideal for exchanging integrated justice data (XML)
 Leverages industry investment in web services
evolution, e.g. security, attachments, etc.
12
XML Web Services Benefits
 All benefits of standardized Internet technologies
 Lower cost, greater options, more services
 Dramatically simplified multi-media/images
 Greater flexibility for new information
requirements, e.g. Homeland information sharing
 Facilitate standard wireless services
13
Open Standard Protocols
OSI Layer
Today
Web Service
Application
Applications
Applications
Presentation
Native Messages
XML, WSDL, MIME
Session
Proprietary
Web Services (SOAP)
Transport
Bisync
TCP
TCP
Network
Bisync
IP
IP
Data Link
Frame Relay
Frame Relay
Physical
Frame Relay
Frame Relay
Proprietary protocols can be replaced with open,
widely available standards (XML Web Services)
14
Role of XML and Web Services
 Distributed service model – NLETS connects users
to databases and other users
 Web Services for reliable messaging
 Reliable messaging standard underway
15
AISLE Standards
OSI Layer
NLETS
AISLE Web Service
Application
NLETS Applications
NLETS Applications
Presentation
NLETS Native Messages
XML, WSDL, MIME
Session
NLETS TCP/IP Protocol Web Services (SOAP)
Transport
Bisync
TCP
TCP
Network
Bisync
IP
IP
Data Link
Frame Relay
Frame Relay
Physical
Frame Relay
Frame Relay
Proprietary protocols can be replaced with open,
widely available standards (XML Web Services)
16
Technical Approach
 Message oriented Web Services
 XML Message Router
 Web Services Description
 Image attachments
17
Message Oriented Web Services
 Initial Web Services provide asynchronous
guaranteed message delivery service
 Peer Web Services in each direction
 Future prospect of synchronous Web Services to
access remote data
18
NLETS XML Message Router
NLETS can continue to perform its traditional role
as a transparent message “broker” to facilitate the
deployment of XML Web Services
19
Web Service Description
 Simple transaction format – self-defining XML
transactions plus optional images
 Early WSDL compatibility problems
20
Image Attachments
 Web Services image attachments supported by
NLETS
 WS-Attachment standard being used
 Simple web service definition for DIME formatted
image attachments
21
XML Standards/Deployment
Standards Definition
K
K
C
BA
D
E
FE
XML
C
BA
D
E
FE
Tech Deployment
Early
Adoption
AISLE
Pilot
NLETS AISLE Proposal
RESULTS
Integrated
Justice
Specification
Use XML with current messages while developing
future standards
22
Implementation Strategy
 Deploy enabling TCP/IP infrastructure
 Use open standards
 Provide “procurement level” documentation
 Insure full legacy protocol interoperability
 Provide compatibility with industry standard
“mainframe” solutions
23
NLETS User and Technical Guide
 XML references and detailed XML Appendix
 Facilitates project team understanding
 Creates broad community benefit and “buy in”
 Community training/education resource
 Critical prerequisite to mainstream deployment –
procurement
24
Immediate AISLE Next Steps
 Complete router infrastructure upgrade
 Participate as an XML Validation Project
 Drive Justice Web Services Security efforts
 Support XML Web Services testing in additional
states
 Move NLETS directory services and transaction
history to new XML platform
25
AISLE II Partners
New York State Police
Kansas Bureau of Investigation
Wisconsin Crime Information Bureau
National Institute of Justice
Advanced Technology Systems
National Law Enforcement Telecommunication System
26
AISLE II
 AISLE provided full legacy system interoperability

XML-legacy interoperability
 AISLE II is at the proposal stage
 AISLE II will provide multi-state XML data
exchange
27
AISLE II – NLETS
 Standardized XML responses for key transactions


User Manual updates for standardized responses
JXDDS 3.0 compliance
 NLETS XML Message Router enhancements


Multi-state XML distribution
XML auditing
 Voice over IP
28
AISLE II – Wisconsin Crime Bureau
 Electronic mail interface

NLETS administrative message SMTP gateway
 Initial node for multi-state exchange
29
AISLE II – New York State Police
 NYSP Information Network XML capability
 Upstate New York Regional Intelligence Center


NLETS data (IAQ, RQ, DQ)
NCIC data (VGTOF, wanted)
 NYS Mug Shot System (Web Services images)
 NYSP Records Management System data
 Integration with NYSP Portal
30
AISLE II – KBI
 KBI Information Systems XML capability
 Web Services security standards and pilot
implementation
31
Supplemental
Slides
AISLE Web Services
XML
Message
Router
(XMR)
Wisconsin
NLETS
Switch
NLETS
Web
Services
Server
Web Services
using existing T1
33
NLETS Vehicle Registration Query
34
AISLE Web Services Pilot
Wisconsin
NLETS
RQ.TQ0000000.AZ.*TERM000000.TXT
LIC/XML4U.LIY/2002.LIT/PC
<nlets>
<nletsContent>
<nletsHeader>
<initiatingAgency>
<agencyOri>TQ0000000</agencyOri>
</initiatingAgency>
<destinationAgency>
<agencyOri>VA</agencyOri>
</destinationAgency>
<controlField>0000000001</controlField>
</nletsHeader>
<request>
<vehicleSearch>
<vehicleLicense>
<plateNumber>XML4U</plateNumber>
<expirationYear>02</expirationYear>
<plateType>PC</plateType>
</vehicleLicense>
</vehicleSearch>
</request>
</nletsContent>
</nlets>
35
<Pyramid>
<Transaction>
<nlets>
<nletsContent>
<nletsHeader>
<initiatingAgency>
<agencyOri>VAMVDPX00</agencyOri>
</initiatingAgency>
<receivedTime>16:12</receivedTime>
<receivedDate>06/04/02</receivedDate>
AISLE Web Services Pilot
Wisconsin
NLETS
RR.AZMVDPX00
16:12 06/04/02 00148
16:12 06/04/02 03169 TQ0000000
*TERM000000
TXT LIC/NLETS
.LIY/2002.LIT/PC.LIC:XML4U 041 TAB:
EXPIRE: 06/30/2002
VIN:1G3VA478VBC101112 VYR:1998
VMA:FORD VMO:EXPLORER VST:4D
NAM:SLASKI, BOB CUST#:B14558564
ADR:7915 JONES BRANCH DRIVE
•CTY:MCLEAN ST:VA ZIP:22102 DTE:
01/27/1999
<receivedLineMsgCount>00148</receivedLineMsgCount>
<sendTime>16:12</sendTime>
<sendDate>06/04/02</sendDate>
<sendLineMsgCount>03169</sendLineMsgCount>
<destinationAgency>
<agencyOri>TQ0000000</agencyOri>
</destinationAgency>
<controlField>TERM000000</controlField>
</nletsHeader>
<vehicleRegistration>
<text><![CDATA[
TXT LIC/NLETS .LIY/2002.LIT/PC.LIC:XML4U 041 TAB:
EXPIRE: 06/30/2002 VIN:1G3VA478VBC101112 VYR:1998
VMA:FORD VMO:EXPLORER VST:4D NAM:SLASKI, BOB
CUST#:B14558564 ADR:7915 JONES BRANCH DRIVE
•CTY:MCLEAN ST:VA ZIP:22102 DTE: 01/27/1999
]]></text>
</vehicleRegistration>
</nletsContent>
</nlets>
</Transaction>
</Pyramid>
36
Next Steps
 Web Services Security
 Synchronous Web Services
 Distributed Web Services
 Object oriented Web Services
 New applications
37
Web Services Security
 Early stages – tracking standards progress
 Web Services Security Task Force established
 Initial report in August
38
Synchronous Web Services
 Distributed systems (NLETS) and centralized
system (NCIC) can use a common model
 Common service models reduce cost and simplify
delivery
 NLETS could mask asynchronous nature of
underlying services and provide apparent
synchronous interface
39
Object Oriented Approach
 Previous systems used transaction view
 New transactions need not be constrained by
legacy transaction content
 Object view, e.g. person or vehicle, is easier to
understand
40
Distributed Web Services
 Potential to bypass switch for improved
performance or contingency
 Web Services standards make plug and play
easier
41
Standardized Responses
 Interpreting NLETS response formats is difficult for
officers
 Solution: XML and standardized stylesheets
 Initial project: standardized driver history
42
Future Web Services
 Centralized wireless services
 Centralized weather services
 Amber Alert system
 Homeland Defense
43
Descargar

Slide 1