1 / 10

Kentucky Wireless Interoperability Executive Committee (KWIEC)

Kentucky Wireless Interoperability Executive Committee (KWIEC). Wireless Data Communication Interoperability. Wireless Data Infrastructure Wireless Data Exchange. Ken Born Commonwealth Office of Technology Architecture & Standards Working Group.

Télécharger la présentation

Kentucky Wireless Interoperability Executive Committee (KWIEC)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Kentucky Wireless Interoperability Executive Committee (KWIEC) Wireless Data Communication Interoperability Wireless Data Infrastructure Wireless Data Exchange Ken BornCommonwealth Office of Technology Architecture & Standards Working Group

  2. What is Required for Wireless Data Communication Interoperability? • At a minimum, the physical and logical interface components are necessary for wireless data interoperability: • Wireless Data Infrastructure • Wireless Data Exchange • When used together, these two components enable users to interoperate and exchange data communications directly between units and across networks.

  3. Process to Establish Standards

  4. Types of Standards • De-jure Standards: • Are those defined and approved by a recognized standardization body such as the TIA, ISO and IEEE. • Are open standards and ensure compatibility between different vendor’s products. • De-facto Standards: • Are developed by one or several companies that have established itself as the preponderant standard with the vast majority of users in the market place.

  5. De-jure Wireless Data Standard • Project 25 Data Interface Standard: • Open standard developed by APCO. • Allows for data transport at 9.6 KBs using digital technologies. • Enables different public safety agencies to interact with one another and to exchange critical information in emergencies even though they may be out of their own primary coverage area.

  6. De-facto Wireless Data Standard • An assessment survey was sent out to various wireless data communication vendors asking for: • Vendor Information • Public Safety Agency Information • Wireless Data Communication Interoperability • Frequency Band of Operation • Over the Air Protocol • Number of Base Stations • Number of Mobile Units • Identify the Coverage Footprint • To determine a preponderant standard with the vast majority of users in the market place.

  7. Wireless Data De-facto Standard?

  8. Identify the Standard to Use • De-jure • Is the data throughput of 9.6 KBs too limited for wireless data communications for public safety agencies? • De-facto • Is there a predominant presence of a particular vendor to establish a De-facto Standard?

  9. Working Group Findings • The Working Group believes the adoption of a De-jure standard would be inadequate for the requirements of public safety wireless data applications. • The Working Group believes it is important to adopt a De-facto standard to improve wireless data interoperability in the Commonwealth. • The Working Group believes there is a De-facto standard established by one vendor due to the “preponderant and vast majority of public safety users” in the Commonwealth and recommends the De-facto IPMobileNet Wireless Data Specification Standard to be used for the Commonwealth’s Public Safety Wireless Data Communication Infrastructure operating in the 800 MHz Frequency Band.

  10. Wireless Data Communication Interoperability usingDe-jure or De-facto Standards Questions ?

More Related