1 / 12

P25 Completion Metrics

P25 Completion Metrics. The Industry Consensus 7-November-2005. The 4 Dimensions of Completeness. Interfaces What are the specified objects? Content What’s specified? Scope What kind of systems can be built? Functionality What can they do?. Content. Interfaces. Architectural Scope.

beth
Télécharger la présentation

P25 Completion Metrics

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. P25 Completion Metrics The Industry Consensus 7-November-2005

  2. The 4 Dimensions of Completeness • Interfaces • What are the specified objects? • Content • What’s specified? • Scope • What kind of systems can be built? • Functionality • What can they do? Content Interfaces Architectural Scope Functionality

  3. 4 Dimensions: Interfaces • The Eight Open Interfaces • Common Air Interface (U) • 2 Data Interfaces (A,Ed) • Inter(RF)-SS Interface (G) • Console Interface (Ec) • Fixed Station Interface (Ef) • PSTN Interface (Et) • Network Management Interface (En) • Plus Important Functional Interfaces • OTAR (KMF to End-Unit) • Key-Fill (KFD to End-Unit) • Plus Other Interfaces that we may discover “Internally” we know these are here, Externally, we may choose to hide them to maintain a consistent message

  4. 4 Dimensions: Content • Overview of Services/Classification • Messages (Vocabulary) • Procedures • Conformance Tests • Performance Recommendations • Performance Measurement Methods • Interoperability Tests Information that specifies the interface. “Fully Specified” Information that allows independent testing. “Certifiable”

  5. 4 Dimensions: Architectural Scope WACN WACNs Network of Networks Wide Area: Inter-System, Independent Mgmt Local Area Operation: Mixed Manufacturer, Unified Management System Systems RFSS RFSSs Radios KMFs NMS Consoles Fixed Stations PSTN GWs Vender Specific Implementation (Limited Interoperability) Radios w/Ext. KMFs NMS Consoles Fixed Stations PSTN GWs

  6. 4 Dimensions: Architectural Scope WACN Fully Interoperable Equipment with wide area roaming and independent management. Interoperable Agencies through coordinated management WACNs Network of Networks Wide Area: Inter-System, Independent Mgmt Local Area Operation: Mixed Manufacturer, Unified Management System Systems Fully Interoperable Equipment, Interoperable Agencies through coordinated management RFSS RFSSs Radios KMFs NMS Consoles Fixed Stations PSTN GWs Interoperable core functions, Interoperable Equipment to the degree that venders publish interfaces and implement each others proprietary features, Interoperable Agencies to the degree that Agencies co-operate Vender Specific Implementation: (Limited Interoperability) Radios w/Ext. KMFs NMS Consoles Fixed Stations PSTN GWs

  7. 4 Dimensions: Architectural Scope • Vender Specific Implementation – • Exists Today, Many venders can build a system that works and is fully functional with proprietary features • Local Area • Exists Partially Today (Radio Interoperability), with Venders implementing each others features • Wide Area • Specification Incomplete, Extended Identifiers, Wide-Area OTAR, etc • Network of Networks • Not considered

  8. 4 Dimensions: Functionality • Refers to what the system can do • Changes as user requirements evolve (over time) and are incorporated into the standards • We need to discuss naming (Rev, Release, Version, Slice) • We need to discuss what the names mean • Is “Thing1” the current TSB102 functionality, for example?

  9. The 4 Dimensions of Completeness P25 is truly complete when all of the interfaces are “certifiable” for Network-of-network operations and the requirements stop changing! Certifiable Content CAI ISSI etc. Specified Interfaces Net of Nets Architectural Scope But it’s “usefully” complete when the standards are accepted by industry, industry is building interoperable products, and users accept those products. Local Area Functionality

  10. Observations • This model for completeness, while accurate, is probably too complex for public display. • P25 will and should continually evolve, and so will never be “totally done”. • We as a community need a way to demonstrate continual progress and useful waypoints.

  11. Example Summary of Status • Select TSB102A Functionality, Show Progress on Content for Interfaces vs. Scope

  12. Showing Progress, Defining Waypoints, Next Steps • Develop Status Charts for Multiple Views • Choose one that is truthful, and reflects our progress in a good light • Focus on work that meets the real needs of the user community, and shows discernable progress towards filling in the chart

More Related