1、 TIA-4973.211 August 2014Requirements for the Mission Critical Priority and QoS Control Service NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and
2、improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products n
3、ot conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards I
4、nstitute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable re
5、gulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an
6、endorsement by TIA or this committee of the products or services of the company. (From Project No. TIA-PN-4973.211, formulated under the cognizance of the TIA TR-8 Mobile and Personal Private Radio TR-8.8 Subcommittee on Broadband Data Systems). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION T
7、echnology (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Documen
8、t may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs atten
9、tion, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing ter
10、ms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied wit
11、h as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or
12、otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to
13、any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publica
14、tions of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs o
15、r services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABIL
16、ITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAF
17、ETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOU
18、T LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED
19、OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-4973.211 i Foreword (This foreword is not part of this standard.) This document is being pr
20、omulgated and will be maintained by the TR-8.8 Private Radio Technical Standards committee, responsible subcommittees, and working groups under the sponsorship of the Telecommunications Industry Association. It describes requirements for a mission critical Priority and QoS Control Service specifical
21、ly intended to operate over LTE and other broadband networks. TIA-4973.211 ii Patent Identification The readers attention is called to the possibility that compliance with this document may require the use of one or more inventions covered by patent rights. By publication of this document no positio
22、n is taken with respect to the validity of those claims or any patent rights in connection therewith. The patent holders so far identified have, we believe, filed statements of willingness to grant licenses under those rights on reasonable and nondiscriminatory terms and conditions to applicants des
23、iring to obtain such licenses. The following patent holders and patents have been identified in accordance with the TIA intellectual property rights policy: No patents have been identified. TIA shall not be responsible for identifying patents for which licenses may be required by this document or fo
24、r conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Trademark Identification The following trademarks are referenced in this specification: 3GPP and LTE are registered trademarks of the European Telecommunications Standards Institute (ETSI). TI
25、A-4973.211 iii TABLE OF CONTENTS Foreword i Patent Identification ii Trademark Identification ii 1 Introduction . 1 1.1 Scope (Informative) 1 1.2 Scope (Normative) 2 1.3 Abbreviations 4 1.4 Definitions. 5 1.5 References . 8 1.6 Nomenclature 9 2 Priority and QoS Service Requirements Model (Informativ
26、e) . 10 2.1 System Model . 10 2.2 Priority Model . 11 2.3 Context Diagrams . 15 2.3.1 Service Context . 15 2.3.1.1 Qu Reference Point 16 2.3.1.2 Gpri Reference Point 16 2.3.1.3 MA Reference Point 16 2.3.1.4 MS Reference Point . 17 2.3.1.5 Rbs Reference Point . 17 2.3.2 Application Client Context . 1
27、7 2.3.2.1 Au Reference Point 18 3 Broadband Transport Service Requirements (Normative) . 19 3.1 Priority and QoS Control Service Requirements 19 3.1.1 General Priority and QoS Control Service Requirements 19 3.1.2 Access Priority Requirements . 20 3.1.3 Default Admission Priority Requirements 20 3.1
28、.4 Dynamic Admission Priority Requirements . 22 3.1.4.1 Responder Emergency 22 3.1.4.2 Immediate Peril . 23 3.1.4.3 Incident Priority 24 3.1.5 Scheduling Priority Requirements 24 3.1.6 Pre-emption Requirements 25 3.1.7 Bandwidth Management Requirements 25 3.1.8 Group Admission Priority Requirements
29、26 3.1.9 Transport Network Requirements . 27 3.1.10 End-to-End Requirements . 27 3.1.11 Provisioning Requirements . 28 3.1.12 Usage Record Requirements . 29 3.1.13 Service Discovery Requirements 30 3.1.14 Security Requirements 30 3.1.15 Wireless Transport Network Specific Requirements 31 3.1.15.1 Re
30、quirements for 3GPP LTE as the Wireless Transport Network . 31 3.1.15.1.1 General Requirements for 3GPP LTE . 32 3.1.15.1.2 Access Priority for 3GPP LTE 32 TIA-4973.211 iv 3.1.15.1.3 Scheduling Priority for 3GPP LTE . 32 3.1.15.1.4 Pre-emption for 3GPP LTE . 33 3.1.15.1.5 Bandwidth Management for 3G
31、PP LTE . 33 TIA-4973.211 v LIST OF TABLES Table 1: Document Revision History vi Table 2: PQCS Subscriber Attributes for Each Priority Step . 14 LIST OF FIGURES Figure 1: Priority and QoS Control Service System Model . 10 Figure 2: Priority and QoS Steps 11 Figure 3: Priority Model . 12 Figure 4: Ser
32、vice Context . 15 Figure 5: Application Client Context 18 TIA-4973.211 vi DOCUMENT REVISION HISTORY Table 1: Document Revision History Version Date Description TR88-14-011-R6 7-August-2014 Initial publication. TIA-4973.211 1 1 Introduction This specification identifies requirements for a Priority an
33、d QoS Control Service (PQCS) intended to operate over wireless broadband networks, including, particularly, the National Public Safety Broadband Network. This specification comprises a portion of the requirements of the TIA-PN-4973 suite of standards. This specification identifies requirements for a
34、 PQCS over Broadband Networks in the context of the Broadband Data Protocol Standards Overview 5, and this section provides an introduction, including the scope of the specification, abbreviations and references. To facilitate the analysis and understanding of the requirements, a set of informative
35、models of the standardized services is presented in Section 2. Section 0 enumerates the normative requirements that are the basis of the standards to be developed. 1.1 Scope (Informative) Priority and QoS refers to the access and control of system resources; especially with respect to a wireless bro
36、adband network. While the lions share of attention is paid in this specification to wireless broadband network resources, this specification is not limited thereto. Transport network, backhaul, and interconnected systems are all considered. The public safety broadband network is a challenging enviro
37、nment. Various types of users (e.g., first responders, second responders, etc.) with various disciplines (police, fire, EMS , etc.) and all types of applications (voice, video, data) all share the same resources. This creates an unprecedented environment for the management of resources for a public
38、safety system. Conventional LMR systems have dedicated resources for Push-to-Talk, and there is traditionally only limited sharing of a system between disciplines. Trunked LMR systems improve sharing between disciplines, but still dont have to share resources like LTE all-IP users. Priority, as used
39、 herein, refers to the ability for a given user to access and obtain resources from the broadband network. Once a user has been granted resources by the system, quality of service (QoS) refers to the specific attributes (e.g., latency, packet loss rate) that govern the experience of content exchange
40、 with the user. Users of the public safety broadband network need a consistent and deterministic service for real-time management of priority and QoS. Commercial cellular network operators typically offer elevated priority to premium customers on a statically assigned basis (i.e., the customers prio
41、rity only changes with changes in their subscription level). While this is sufficient for commercial use, public safety users require priority services that are situational. The sheriff at a traffic stop does not require the same priority on the broadband network as a patrolman exchanging gunfire at
42、 a bank robbery. Pre-emption of lower-priority resources is essential in order to provide resources to the highest priority incidents. Mission critical communications require immediate access to resources. Many factors can impact the resources available to a given traffic flow: number of users, numb
43、er of incidents, distance to cell antenna, interference, etc. Further, many factors can contribute to wireless congestion at a cell. For this reason, Priority and QoS capabilities for public safety need to consider the dynamic situational aspects of responders. It is insufficient to statically assig
44、n a priority to a given responder that will be sufficient for all situations. TIA-4973.211 2 Another important aspect of priority and QoS is that it is based on the user and not a given device. In the commercial cellular world, users obtain a personal device and that device and its telephone number
45、are assumed to be associated with a user. In the public safety world, devices are re-used across shifts (e.g., tablets, radios, fire trucks, etc.). It is not realistic to assume that all public safety broadband devices are personally issued. For example, an incident commander can pick up a shared la
46、ptop belonging to her agency and sign-in, or can be assigned to a vehicle having a fixed-mount laptop in the vehicle. Therefore, public safety priority and QoS needs to be derived for a user also taking into account the application(s) that he/she is currently invoking, and applied to the devices cur
47、rently being used by the user. The type of user is one of many factors affecting a Subscribers overall priority and QoS state. See sections 3.1.3 and 3.1.4 for more information. Responders are trained today with procedures that have taken decades to perfect. Any service provided to responders has to
48、 complement their existing workflow. This service attempts to avoid distracting a user from the mission by requiring him/her to enter a broadband maintenance terminal or to become aware of the broadband networks detailed prioritization parameters. In this specification, prioritization is integrated
49、into usage patterns familiar to the user (e.g., the emergency button). Applications can be deployed by various domains utilizing the network. For example, telephony might be deployed nationally and push-to-talk might be deployed regionally by a state (e.g., in a separate APN). The priority and QoS capabilities described herein are intended to consistently govern resources for all applications, regardless of the entity (national, regional, local) that is operating the application. This specification defines a Priority and QoS Control Service (PQCS) to address these complex and va
