1 / 8

214/78 INTEROP Validation Objectives Status

SC-214 / WG-78 Plenary Meeting #10. 214/78 INTEROP Validation Objectives Status. 3/6 May 2010. Meetings. Three telecons 2nd April 13th April 26th April Participants J. Hamelink, P. Muraca, M. Niraula, F. Picard, S. Beamer, T. Courdacher, P. Rohault, C. Colling

elmo-perry
Download Presentation

214/78 INTEROP Validation Objectives Status

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. SC-214 / WG-78 Plenary Meeting #10 214/78 INTEROP Validation Objectives Status 3/6 May 2010

  2. Meetings • Three telecons • 2nd April • 13th April • 26th April • Participants • J. Hamelink, P. Muraca, M. Niraula, F. Picard, S. Beamer, T. Courdacher, P. Rohault, C. Colling • Supporting Document • INTEROP-VO-Status version 0.4

  3. Approach • Approach Taken: • Review of initial list of VOs presented in Langen • Identify the main areas requiring validation / identify areas where credit can be taken from earlier validation • Refine definition of proposed VOs, confirm suitability or delete • Why, How and Who ? • Who : Either « internal » (VSG) or « external » (VPs) validation • Identify validation scenarios for each VO • Identify validation projects involved in the realisation of the VO

  4. Main Discussed Items • Areas requiring technical validation • SPR vs. INTEROP • CPDLC/ADS/FIS Message Sets (ASN.1) • New ATN applications and Operating Methods (FIS and ADS-C) • New features: support of air-initiated applications (addressing issues, ground topologies), functional extensions of L2K • Backward Compatibility (L2K) • Extension of FANS accommodation rules • Out of scope • Operational validation • Oceanic services • Future enhancements (security, IP…) • 2 categories of INTEROP Validation Objectives • Technical VOs • Documentation VOs

  5. Agreed Technical VOs • Technical VOs: • ITVO_100: Compatibility between technical IRs (INTEROP) and operational ORs (SPR) • ITVO_200: Suitability and correctness of ATN FIS Application • ITVO_300: Suitability and correctness of ATN ADS-C Application • ITVO_400: Assurance of Interoperability with L2K Implementations • ITVO_500: Assurance of Interoperability with FANS Implementations • ITVO_600: Ensure independent implementations are able to interoperate and documents are implementation independent • ITVO_700: Ensure the technical solution does not create not acceptable (operational/safety) situations (e.g. DLIC/DOTIS addressing issue) • ITVO_800: Ensure all PDRs are resolved and enough validated (and do not impact validation so far) • ITVO_900: Ensure ASN.1 match OSD message description

  6. Agreed Documentation VOs • Documentation VOs: • IDVO_100: Assurance the technical requirements are correctly specified (identifiers, unambiguous, complete, consistent, ….) • IDVO_200: Assurance there is no redundant requirements (within INTEROP documents and with other 214/78 documents) • IDVO_300: Assurance that tools are provided to support technical capability / interoperability assessment / data link profile definition • IDVO_400: Assurance the merge Doc 9880 / DO280 / DO290 / SPR / INTEROP has been correctly done

  7. Validation Scenarios for INTEROP • Scenarios • Minimum scenario required to claim a VO is validated • Identify existing scenarios (L2K+) • Paper analysis and/or implementation • Define New Scenarios • Message/Parameter driven • Operating Method driven • Application Service driven • Document driven Msg/Param DescriptionATN ASN.1 msg LK2 ASN.1 msg FANS ASN.1 msg ACM eq. TATSU/ eq. RTATSUATN LK2 FANS CPDLC start establishmentATN LK2 FANS IR ReqOSD Req

  8. Plans for the week • Allocate resources to VOs • Review/start scenario templates

More Related