ETSI TS 170 016-2009 Project MESA Technical Specification Group - System Functional Requirements Definition《MESA计划 技术规范组 系统 功能要求定义(版本3 1 1)》.pdf

《ETSI TS 170 016-2009 Project MESA Technical Specification Group - System Functional Requirements Definition《MESA计划 技术规范组 系统 功能要求定义(版本3 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 170 016-2009 Project MESA Technical Specification Group - System Functional Requirements Definition《MESA计划 技术规范组 系统 功能要求定义(版本3 1 1)》.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 170 016 V3.1.1 (2009-02)Technical Specification Project MESA;Technical Specification Group - System;Functional Requirements DefinitionETSI ETSI TS 170 016 V3.1.1 (2009-02) 2 Reference DTS/MESA-SYS0070016v311 Keywords application, interoperability, network, performance, security, service, TM

2、N 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 present document can

3、 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 dispute, the

4、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 other ETSI docum

5、ents 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 by written perm

6、ission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Membe

7、rs. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and own

8、ed by the GSM Association. ETSI ETSI TS 170 016 V3.1.1 (2009-02) 3 Contents Intellectual Property Rights4 Foreword.4 Introduction 4 1 Scope 5 2 References 5 2.1 Normative references .5 2.2 Informative references5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations for Requirement Id

9、entification7 4 Functional Requirements7 4.1 Core Functional Requirements .8 4.2 Other Requirements20 History 21 ETSI ETSI TS 170 016 V3.1.1 (2009-02) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertai

10、ning to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretar

11、iat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or th

12、e updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by Public Safety Partnership Project (MESA). The contents of the present document are subject to continuing work within the Specifica

13、tion Group (SG) and may change following formal SG approval. 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 and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to SG

14、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 enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have

15、 been incorporated in the document. Introduction The functional requirements in the present document were captured through a series of collaborative workshops over several months that involved members of the Public Safety community as represented by the MESA Service Specifications Group (SSG), and i

16、nfrastructure vendors and operators in the wireless industry as represented by the MESA Technical Specifications group. Using the Statement of Requirements (TS 170 001 1) developed by the MESA SSG and using the MESA Network Architecture (MESA 70.015 i.1) as a guide, the MESA group derived the functi

17、onal requirements found in the present document. ETSI ETSI TS 170 016 V3.1.1 (2009-02) 5 1 Scope The present document give guidelines for the functional requirements required for a MESA system that is consistent with the Service Specification Groups Statement of Requirements (TS 170 001 1) and the T

18、echnical Specification Groups Network Architecture (MESA 70.015 i.1). The present document is intended to be the input into a gap analysis of existing standards and technologies with an ultimate goal to update the existing standards and technologies to be fully compliant with the functional requirem

19、ents in the present document. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part

20、 thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected loca

21、tion might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the pr

22、esent document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI TS 170 001: “Project MESA; Service Specification Group - Services and Applications; Statement of Requirements“,

23、MESA TS 70.001. 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments)

24、applies. i.1 MESA 70.015: “ Project MESA; Technical Specification Group - System; System and Network Architecture “. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: airlink resources: available throughput (voice and

25、 data) for a given location that can be shared across all users ETSI ETSI TS 170 016 V3.1.1 (2009-02) 6 authorized principal: principal with permissions to perform specific action(s) or receive specific information (Source OMA Dictionary) bandwidth: amount of spectrum required for the system NOTE: S

26、ee also Channel Bandwidth, Radio Bandwidth. channel bandwidth: amount of spectrum required for a single channel of the system components: individual parts that together make up the entire system, generally inclusive of devices NOTE: See also Nodes, Network Elements. cooperative use: system able to o

27、perate overlapped with another system with the components of each system cooperating, not interfering dynamic bandwidth: allows bandwidth to be changed to allow more capacity for priority users effective user data rate: effective throughput (voice and data) as perceived by an end user forward compat

28、ibility: ability for a system to operate with future protocols of itself logical networks: AWN, EAN, JAN, IAN, and PAN as described in the MESA System and Network Architecture Document MESA system: complete set of integrated components that provide full communication functionality meeting the MESA S

29、tatement of Requirements network elements: individual parts, that together, make up the entire system, excluding devices or clients NOTE: See also Components, Nodes. network functions: user transparent functions of the system, such as authentication proxying for single sign on, mobility support, pol

30、icy enforcement, etc. nodes: individual parts that together make up the entire system inclusive of devices and clients NOTE: See also, Components, Network Elements. Off-Net: “Off Network“, meaning the user does not have access to fixed network services, and access to services is restricted to those

31、that reside in the device or functioning wireless transmitters (vehicle or wireless site) On-Net: “On Network“, meaning the user has access to the fixed network services that reside in data or switching centers peer-to-peer: service within a device that communicates directly with other devices, and

32、does not communicate with any network component NOTE: Note that this does not preclude the communication from being carried by the network, only that application level messaging is originated and terminated by services resident on the device. principal: an entity that has an identity, that is capabl

33、e of providing consent and other data, and to which authenticated actions are done on its behalf EXAMPLE: Examples of principals include an individual user, a group of individuals, a corporation, service enablers/applications, system entities and other legal entities. (Source OMA Dictionary). radio

34、bandwidth: amount of spectrum required for the system (inclusive of all channels used) run-time: commands are executed as they are given single sign on: ability for the user to provide authentication credentials once to the system, and the system proxies those credentials to any application or servi

35、ces requiring credentials system: unless otherwise specified, system refers to the MESA system ETSI ETSI TS 170 016 V3.1.1 (2009-02) 7 untrusted connections: connections where the connecting parties have not conducted prior mutual authentication and authorization 3.2 Abbreviations for Requirement Id

36、entification Requirement format is of the form: xx-xxx-nnn (where x are letters, and n are numbers). The format structure consists of a requirement classification, which is a two letter prefix identifying how the requirement will be documented; followed by three letters identifying functional catego

37、rizations of the requirements; followed by a three digit number that allows each requirement to be uniquely identified. For the purposes of identifying requirements, the following requirement abbreviations apply: Requirement Classification (first two letter identifiers): DR Documentation Requirement

38、 DC Design Consideration Requirement IR Implementation Requirement (Requirement is incumbent upon the entities implementing the technology) FR Functional Requirement LMR Land Mobile Radio Requirement Functional Categorization (middle three letter identifiers): ASC (xx-ASC-xxx) Requirement originatin

39、g from the team looking at Applications and Services implications and interactions AWN (xx-AWN-xxx) Requirements originating from the team looking at Ancillary Wireless Network implications and interactions EUD (xx-EUD-xxx) Requirements originating from the team looking at End User Device implicatio

40、ns and interactions Implementation Requirement (Requirement is incumbent upon the entities implementing the technology) IOP (xx-IOP-xxx) Requirements originating from the team looking at interoperability implications and interactions JRA (xx-JRA-xxx) Requirements generated from the first round of Jo

41、int Reviews LOG (xx-LOG-xxx) Requirements originating from the team looking at Logical Networks implications and interactions NMC (xx-NMC-xxx) Requirements Generated by team looking at Network Control and Network Management implications and interactions Sxx (xx-Sxx-xxx) Requirements originating from

42、 the team looking at Security implications and interactions Security Subsections Categorization (xx of the Sxx identifier): SAU Authentication SAV AvailabilitySCO Confidentiality SGE General SecuritySIN Integrity SMA Management SNR Non-repudiationSTR Traceability 4 Functional Requirements The follow

43、ing tables capture the Functional Requirements for the Project MESA system. ETSI ETSI TS 170 016 V3.1.1 (2009-02) 8 4.1 Core Functional Requirements Table 1 consists of the functional requirements that would apply to developing standards and specifications for a MESA system. Table 1: Functional Requ

44、irements Functional Req. ID No. Functional Requirement Text Associated Mesa SoR Sections Associated User Seq IDs FR-ASC-001 Authorized principals shall be able to add, modify, or create and store in real-time, via an application or service, new data in database(s), files and automated systems, neede

45、d to successfully execute the application or service. MesaSoR.5.54 282 FR-ASC-002 Authorized principals shall be able to retrieve in real-time, via an application or service, any data from database(s), files and automated systems, needed to successfully execute the application or service, by the aut

46、horized principals. MesaSoR.5.54 283 FR-ASC-003 Authorized principals shall be able to modify in real-time, via an application or service, any data in database(s), files and automated systems, needed to successfully execute the application or service, by the authorized principals. MesaSoR.5.54 284 F

47、R-ASC-004 Authorized principals shall be able to add, modify or delete in real-time, via an application or service, any data in database(s), files and automated systems, needed to be removed in order to successfully execute the application or service, by the authorized principals. MesaSoR.5.54 285 F

48、R-ASC-005 Authorized principals shall be able to monitor and control features and functions of remote devices such as robotic devices, unmanned units, including but not limited to, via an application or service. MesaSoR.5.54 286 FR-ASC-006 The applications and services that involve database transact

49、ions, file downloads, file uploads, remote control, including but not limited to, shall function on the logical network, transparently to and irrespective of the different layer protocols of the logical network, below the application layer. MesaSoR.5.54 287 FR-ASC-007 1. Applications and services shall be designed in such way that they can be distributed to allow access from any end user devices. 2. Interoperable Applications and services should have a well-defined subset of mandatory features. MesaSoR.5.54 288 FR-ASC-008 The user access to applications and s