1 / 30

PROJECT MESA Broadband M obility for E mergency and S afety A pplications

PROJECT MESA Broadband M obility for E mergency and S afety A pplications APCO International Conference Denver, August 21-25, 2005. Larry Nyberg. Motorola Secretariat of the MESA Service Specification Group Services and Applications. Summary. MESA

inara
Télécharger la présentation

PROJECT MESA Broadband M obility for E mergency and S afety A pplications

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. PROJECT MESA Broadband Mobility for Emergency and Safety Applications APCO International Conference Denver, August 21-25, 2005

  2. Larry Nyberg Motorola Secretariat of the MESA Service Specification Group Services and Applications

  3. Summary MESA Mobility for Emergency and Safety Applications Project Name Introduction Brief History, Objectives, Members, MESA structure Output of the users work State of Requirements Identification of criteria to map user requirements into system technical requirements Mapping process List of the main system requirements for the MESA system MESA system technical requirements Example of network architectures, the “System of Systems” paradigm System Reference Model Architectures Work Items, next steps Specification Development Plan Next deadlines, some figures, how to participate Final remarks

  4. Brief History • Project MESAis a transatlantic public safety partnership between ETSI(Europe) and TIA(N. America) that represents the first international initiative to involve users and organizations from the Public Protection, Disaster Response and Civil Defence sectors • In May 2000 ETSI and TIA signed in Washington DC an agreement (the PPA - Partnership Project Agreement) to work collaboratively by providing a forum in which the key players can contribute actively to the elaboration of MESA specifications • In January 2001 the current partnership agreement was ratified in the City of Mesa (Arizona) • Project’s name given in recognition of the signature city • MESA = Mobility for Emergency and Safety Applications • Project MESA also supports the ITU in its worldwide effort to harmonize PPDR communications as documented in ITU-R Report M.2033

  5. MESA Objectives MESA aims at producing globally applicable technical specifications for digital mobile broadband technology, aimed initially at the sectors of public safety and disaster response allowing a coordination of regional/international responses to emergencies, disasters and monitoring day-by-day applications

  6. Members & Activities • Project MESA membership currently comprises over 100 representatives • national public safety organizations • communications equipment users • communications industry • research organizations • Academia • Observers from Canada (TSACC) and Korea (TTA) • Full affiliation list: http://www.projectmesa.org/info/MESApeople.htm • Any interested party from around the globe can actively participate in the Project MESA specification development process • ETSI and TIA support the administrative needs while the technical work required to develop the Project MESA specifications is performed by members • Members meet every 6 months (alternating between European and North American venues) to coordinate program activities and to review project documents for approval • Between the meetings, members coordinate specification development and other activities primarily during phone conferences and through e-mail

  7. MESA Organization MESA Structure Organizational Partners MESA SC (Steering Committee) Service Specification Group Technical Specification Group Liaison Standardization bodies Services & Applications System SSG SA TSG SYS System Technical Specifications

  8. Phil Kidner BAPCO Chair of the MESA Service Specification Group Services and Applications

  9. MESA Service Specification Group • Who are we ? • What is it that we have produced ? • How has this been done ? • Who are these users ? • What are the common requirements ? • What about my requirements ? • What about my requirements ?

  10. Who are we ? • A global effort driven by: • ETSI European Telecommunications Standards Institution • TIA Telecommunications Industry Association

  11. Who are we really ? • Individuals from user organisations, regulatory/standards bodies, manufactures, suppliers and other organisations • …….. Just like you and I !

  12. What is it that we have produced ? • Statement of requirements • Common requirements • Specific requirements

  13. Statement of user Requirements (SoR) • Developed within the user-focused Service Specification Group (SSG) of MESA and approved by the Project MESA Steering Committee (SC) in 2002 • Intended to describe and define functional and operational user requirements, capabilities, applications and scenarios that involve broadband air interface data rates • documents the details of PPDR scenarios, describing the types of information that are routinely required to support PPDR activities • technology needs within Public Protection & Disaster Relief (PPDR) discipline • Emphasis on applications identified by users/agencies as key requirements, but which current applied technology may not fully deliver • To view the latest SoR document, please visit http://www.projectmesa.org/ftp/Specifications/

  14. How has this been done ? • Together ! Driven by consensus • Processes ensure that everyone can contribute • Identify common requirements • Document your requirements • Add/review/delete ……please

  15. Who are these users ? • Public Protection and Disaster Relief • Synonymous with Public Safety • First Responders – definitely but wider …. • Includes ……. • Not ….

  16. What are the common requirements ? • Fifty eight common requirements • Includes …. • User requirements not user solutions

  17. What about my requirements ? So far …….

  18. Criminal Justice Emergency management Special operations Health Services Fire services Coast Guard Search and Rescue Airport security Humanitarian assistance Hazardous materials Correctional Institutions Emergency Planning Central Government Land and natural resources Transportation Intelligent transport systems Highways Agency So far ……

  19. What aboutmyrequirements ?

  20. Jeff Bratcher ITS Chair of the MESA Technical Specification Group

  21. Mapping Process • It is the first task faced by the Technical Specification Group – System (TSG SYS) • The mapping consists in reorganizing the breadth of information provided in the SoR into a logical framework that could be used to identify the system technical requirements across the different PPDR scenarios • TSG SYS members is going to derive a generic set of MESA communications requirements (bandwidth, delay, jitter, QoS, security, priority access, scalability…) that address the requirements of all PPDR scenarios

  22. Scenarios Categories “Cube” Services have been sorted into 12 different categories resulting from the combination of identified • Indoor/Day-by-Day/Single Spot • Indoor/Emergency/Single Spot • Urban/Day-by-Day/Single Spot • Urban/Day-by-Day/Wide Area • Urban/Emergency/Single Spot • Urban/Emergency/Wide Area • Urban/Disaster/Wide Area • Rural/Day-by-Day/Single Spot • Rural/Day-by-Day/Wide Area • Rural/Emergency/Single Spot • Rural/Emergency/Wide Area • Rural/Disaster/Wide Area

  23. Main MESA Technical System Features In order to fulfil user requirements MESA system must be • reliable • able to ensure multiple levels of security and encryption • easy and fast to deploy • able to guarantee the requested QoS • flexible • adaptable • reconfigurable • scalable • self-organizing • interoperable with existing private and public infrastructures • broadband • mobile • low power consumable • able to locate nodes, sensors, robots…

  24. System Reference Model Architecture MESA as a System of Systems Other New Technology Ad-hoc Project MESA New Technology New Technology Other MESA Solution Space Cellular (2, 2+, 3G) UWB B3G, 4G New Technology Mobile Broadband New Technology Trunked New Technology • Technical Fora • Standardizationbodies Broadband MESA Search Space #7 Meeting September 2003 - Milan

  25. MESA Specification Development Plan DTR/MESA SYS0070005v311 “System Reference Document” DTR/MESA SYS0070009v311 “Deployment Strategies” DTR/MESA SYS0070010v311 “System Traffic/Service Profiles” DTR/MESA SYS0070011v311 “System Prioritized MESA Scenarios” DTR/MESA SYS0070012v311“System Reference Model” System Reference Architecture WI SYS0070012v311 Derived System Requirements WI SYS0070014v311 System Technical Requirements (draft) System Reference Model (draft) Technologies and Protocolswith Potential Applicability to Project MESA WI SYS0070008v311 Derived System Specification LiaisonStandardizationbodies System Technical Specification Iterative feedback among various tasks is assumed and is not explicitly indicated Technology Roadmap (draft) Technology Roadmap

  26. Jatin Kadakia Qualcomm Vice-Chair (U.S.) of the MESA Technical Specification Group

  27. Current Status • 10 full meetings have taken place so far • 5 in USA • Next meeting MESA #11 • 25th to 28th October 2005 in Edinburgh, Scotland hosted by BAPCO • 3 documents already approved • 10 WIs in drafting stage • 41 individual members • 21 public safety members • SSG SA work in revision phase in the light of SAFECOM SoR • TSG SYS work in full activity

  28. Participation (1) • To be a member of MESA allows organizations to fully influence the work of the project by attending meetings and taking part in the voting process • Participation in MESA is classified into 5 categories • Organizational Partnership • Organizational Partnership is open to any Standards Development Organization, irrespective of its geographical location. • Current Organizational Partners are ETSI and TIA • Individual Membership • To participate as Individual Member of Project MESA it is a pre-requisite the membership in an Organizational Partner • Public Safety Membership • Any legal entity which fulfils one of the following requisites: • is a governmental entity or • is a private entity providing public safety services under contract to a governmental entity or • is an association or consortium of governmental entities; or • is an association of representatives of governmental entities or • otherwise represents governmental entities with the further provision that it is not a manufacturer of equipment or the holder of IPR that may fall within the scope of the MESA project

  29. Participation (2) • Observership • The status of Observer may be granted by the Organizational Partners to an organization, which has the qualifications to become a future Organizational Partner (see before) • Observers are expected to contribute to the common objective of Project MESA and avoid duplication of work related to Project MESA. • Organizations may apply to obtain Observership status by writing to any of the existing Organizational Partners. • Guest • The status of Guest may be granted for a limited period, by the Organizational Partners to an organization, which has the qualifications to become a future Individual Member (see above) • Organizations may apply to obtain Guest status by writing to any of the existing Organizational Partners

  30. Thank you! Project MESA http://www.projectmesa.org http://portal.etsi.org/MESA ETSI Secretariat E-mail:mesa@projectmesa.org

More Related