1、 ETSI TR 102 653 V3.1.1 (2007-08)Technical Report Project MESA;Technical Specification Group - System;System and Network ArchitectureETSI ETSI TR 102 653 V3.1.1 (2007-08) 2 Reference DTR/MESA-SYS0070015V311 Keywords air interface, architecture, broadband, digital, emergency, radio, safety, SAR, sate
2、llite, security ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the presen
3、t document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of
4、 dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and ot
5、her ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized b
6、y written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON l
7、ogo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 653 V3.1.1 (2007-08) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6
8、 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 Overview 7 5 Architecture7 5.1 Overview 7 5.2 Networks 8 5.2.1 Physical and virtual networks .9 5.2.1.1 IAN .9 5.2.1.2 JAN .10 5.2.1.3 EAN 10 5.2.1.4 AWN .10 5.2.2 Network types.10 5.2.2.1 Incident Area Network
9、s (IAN)10 5.2.2.2 Jurisdictional Area Networks (JAN) .10 5.2.2.3 Extended Area Networks (EAN).11 5.2.2.4 Ancillary Wireless Networks (AWN) .11 5.3 Components11 5.3.1 Public safety sensor and networked devices .11 5.3.2 Communication devices12 5.4 Overall network architecture 12 5.4.1 Interface 1 .14
10、 5.4.2 Interface 1a .14 5.4.3 Interface 2 .14 5.4.4 Interface 2a .14 5.4.5 Interface 2b .14 5.4.6 Interface 3 .14 5.4.7 Interface 4 .14 5.4.8 Interface s114 5.4.9 Interface s214 5.4.10 Interface s315 5.4.11 Interface i115 5.4.12 Interface h1 .15 5.4.13 Interface h2 .15 5.4.14 Interface h3 .15 5.4.15
11、 Interface c1 .15 5.4.16 Interface c2 .15 6 Communications device architecture .15 6.1 Common communication device15 6.2 Communications device interfaces.16 6.2.1 PSCD interfaces16 6.2.1.1 Interface 1 .17 6.2.1.2 Interface 2 .17 6.2.1.3 Interface 2b .17 6.2.1.4 Interface 3 .17 6.2.1.5 Interface 4 .1
12、8 6.2.2 PAN device interfaces 18 6.2.2.1 Interface 1 .18 6.2.2.2 Interface 1a18 ETSI ETSI TR 102 653 V3.1.1 (2007-08) 4 6.2.2.3 Interface 2 .19 6.2.2.4 Interface 2b .19 6.2.2.5 Interface 3 .19 Annex A: Public service services and core network architecture20 A.1 Overview 20 A.2 Functional component d
13、escriptions21 A.2.1 Home database .21 A.2.2 Visitor database 21 A.2.3 Mobility manager .21 A.2.4 AAA server 21 A.2.5 Operations support systems21 A.2.6 Vertical service systems .21 A.2.7 Command and control systems.21 Annex B: Public service services and system architecture views.22 B.1 Overview 22
14、B.2 User architectural view.22 B.3 Functional architectural view .24 B.4 Physical architectural view.24 B.5 Complete architectural view.24 History 26 ETSI ETSI TR 102 653 V3.1.1 (2007-08) 5 Intellectual Property Rights Project MESA is a collaborative activity whos Organizational Partners (OPs) as of
15、 the date of this document are the European Telecommunications Standards Institute (ETSI) and the Telecommunications Industry Association (TIA). It is not a legal entity. MESAs Technical Working Procedures (“Procedures“) provide that Individual Members of MESA are bound by the IPR Policy of their re
16、spective OPs. The Procedures further provide that Individual Members should declare at the earliest opportunity any IPRs that they believe to be essential or potentially essential to any work ongoing within MESA. Under the Procedures, the MESA Secretariat is required to maintain a register of IPR de
17、clarations relative to MESA, received by the OPs. Information concerning declarations of IPR relative to MESA which have been received from OPs and which have been communicated to the MESA Secretariat are available and can be found as follows: 1. as to the MESA Secretariat: www.projectmesa.org or me
18、saprojectmesa.org; 2. as to ETSI: http:/webapp.etsi.org/IPR/; 3. as to TIA: iprtiaonline.org. The use or practice of the contents of this document may involve the use of IPRs including, but not limited to, pending or issued patents, or copyrights. Pursuant to their respective policies, none of ETSI,
19、 TIA or MESA makes any search or investigation for IPRs of any nature. ETSI, TIA and MESA, and each of them, takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR which are contained in declarations or otherwise c
20、ommunicated to them, or any of them. The ETSI IPR Policy is available on the ETSI web server (http:/www.etsi.org/legal/) and the TIA IPR Policy is available on the TIA web server (http:/www.tiaonline.org) as part of the TIA Engineering Manual. Foreword This Technical Report (TR) has been produced by
21、 Public Safety Partnership Project (MESA). The contents of the present document are subject to continuing work within the Specification Group (SG) and may change. Should the SG modify the contents of the present document, it will be re-released by the SG with an identifying change of release date an
22、d an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to SG for information; 2 presented to SG for approval; 3 or greater indicates SG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enha
23、ncements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 102 653 V3.1.1 (2007-08) 6 1 Scope The present document defines a network and system architecture for public safety networks that is capable of meeti
24、ng the requirements of next-generation public service and public safety agencies. The present document elaborates an architecture consistent with the Project MESA Systems Overview and requirements that are specified in the Project MESA Statement of Requirements and defines other elements needed to d
25、evelop detailed technical requirements for MESA systems, applications and interfaces. The interfaces specified in the present document are described at a high level, in a generic fashion, to allow for detailed proposals that will provide all the specific details needed to support interoperability. T
26、hese interfaces are described in separate MESA specification documents. 2 References For the purposes of this MESA Technical Report (TR), the following references apply: NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term val
27、idity. 1 MESA 70.012: “Project MESA; Technical Specification Group - System; System Overview“. 2 MESA 70.001: “Project MESA; Service Specification Group - Services and Applications; Statement of Requirements“. 3 MESA 70.002: “Project MESA; Service Specification Group - Services and Applications; Def
28、initions, symbols and abbreviations“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: connection: entity formed when two devices communicate NOTE: A connection between two devices includes the interfaces used and th
29、e link that is formed between them. A connection can also describe the upper layer elements within the context of overall connectivity to a missions application needs. device: type of communication component differentiated from other components by its stand-alone accessibility and functionality NOTE
30、: It is physically interactive, such that an input results in an action taking place within the device, as opposed to a component which may only be accessible through the network. Devices are generally more portable than other components and may possess capabilities to access or communicate with oth
31、er devices and/or networks. interface: physical or logical link between two entities NOTE: In the present document it is used to refer to the physical interface that network components use to communicate with each other. This interface may be either wired, wireless or utilize other emerging techniqu
32、es. All software interfaces will be specifically referred to as software interfaces. When two or more interfaces communicate they form a link. This link may be wired, wireless or utilize other techniques, depending on the interfaces forming the link. The interfaces forming the link also determine th
33、e protocol of the link. Note that components or devices (i.e. NGN, converged) may be enabled to utilize and access multiple interface and link possibilities. ETSI ETSI TR 102 653 V3.1.1 (2007-08) 7 network component or simply a component: represents a physical piece of the network NOTE: This compone
34、nt may serve in creating the network, facilitating the network or to access the network. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in MESA 70.002 2 and the following apply: AAA Authentication, Authorization and Accounting AWN Ancillary Wireless Network EAN E
35、xtended Area NetworkFMC Fixed/Mobile Convergence IAN Incident Area Network ITS Intelligent Transportation System / Intelligent Transport System JAN Jurisdiction Area Network JSNCP JAN Service and network Control Point LMR Land Mobile Radio MESA Mobility for Emergency packet-data) OAN Over the Air Ne
36、tworking PAN Personal Area Network PSCD Public Safety Communication Device QoS Quality of Service SaR Search and Rescue SENTRY Federal Bureau of Prisons “SENTRY“ database (US) SOA Service Level agreements SoR Statement of Requirements 4 Overview The Project MESA Network and System Reference Architec
37、ture describes the communication components that will either be incorporated into a Project MESA system, or with which a Project MESA system will interact. The present document describes a general public safety and emergency services sector communication architecture or structure, and the common com
38、ponents in that architecture. The MESA Architecture is designed to meet the rigorous requirements of the Public Safety and Emergency Services community. Actual implementations may differ, as long as the user community requirements are met, but the overall hierarchy and architecture should be similar
39、 even if all the components are not included, thus allowing for maximum flexibility and discretion of system owners, operators and users. The flexibility of the architecture allows for a communication system that addresses many different scenarios and specialized agency or user needs. 5 Architecture
40、 5.1 Overview The overall public safety communication system architecture provides a description of the identified systems components, including the components structure and the connections formed among them. The high-level architecture also explains the design principles behind the components and t
41、heir connections. The chart below also implies a potential access or architectural relationship (interoperability, accessibility) between network types and or components. ETSI ETSI TR 102 653 V3.1.1 (2007-08) 8 5.2 Networks The MESA network hierarchy consists of Personal Area Networks (PAN), Inciden
42、t Area Networks (IAN), Jurisdictional Are Networks (JAN) and Extended Area Networks (EAN). These networks are defined to meet primarily the needs of the Public Safety user community. These networks may be interconnected with Ancillary Wireless Networks (AWN) to provide additional and/or backup cover
43、age. The AWN is a network whose primary design is for public commercial or other non-public safety services, but whose ubiquity makes availability of its services desirable for the public safety user community. The service characteristics that the public safety user receives from these networks will
44、 depend on Service Level Agreements (SOA) that may exist between a particular Public Safety Agency and the AWN network operator. The role of a MESA Network in the hierarchy is determined by its characteristics in multiple dimensions. These dimensions may include technology, service, regulatory, lega
45、l and deployment considerations. Thus on a technology front it may be possible to either have heterogeneous technologies for a single network type or a single technology across multiple network types. The MESA high level architecture is described in a manner that is flexible to allow for multiple de
46、ployment and regulatory environments without imposing any artificial constraints. Type Scope Capabilities Bandwidth Required Personal Area Network (PAN) Single subject or object. Limited applications and location. Only enough for pre-designated and localized applications. Incident Area Network (IAN)
47、 An incident or specific event. Examples include a MESA-capable ad-hoc “hot-spot“ or other temporary network. Application varied and flexible network establishment, but location limited. An IAN may or may not contain any infrastructure elements or links to external networking functions. In such a ca
48、se, PSCDs communicate amongst themselves constrained by their individual propagation characteristics. Enough to support the incident or specific mission, including ad-hoc capabilities across environmentally challenging scenarios. Jurisdiction Area Network (JAN) An entire jurisdiction. A JAN might be
49、 implemented for a given governmental entity. A JAN may be implemented to provide services for a number of governmental entities, covering well beyond the jurisdictional area of responsibility for any given entity. A JAN may be shared also be shared among government and non government users, under the management of a government entity, a non-government entity, or shared government/ non-government control. Varied applications and locations, robust, well managed. Further requirements can be found in 2. Able to provide high bandwidth throughout the coverage area
