1、 TIA-1196 July 2011Multimedia Priority Service (MMPS) for MMD-based Networks-Stage 1 Requirements NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability an
2、d 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
3、 not 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
4、 Institute (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
5、regulatory 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. (From Project No. 3-0404, formulated under the cognizance of the TIA TR-45 Mobile (b) there
6、 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 Document may involve the u
7、se 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 attention, a statement f
8、rom 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 terms or conditions, w
9、hich 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 with as respects the D
10、ocument 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 otherwise), whether
11、 such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) 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 any such Normative Reference; (
12、ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification
13、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 or services or any claims of compliance with the contents of
14、 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 MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUA
15、L 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 SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SER
16、VICE 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 WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR C
17、ONSEQUENTIAL 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 OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION
18、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. EDITOR 1 Anand Akundi, Telcordia 2 3 REVISION HISTORY 4 5 Revision History Version Comment Date 1.0 Initial publication June 29th, 2006 Rev A v1.0 Revisio
19、n to support Data Services October 28th, 2010 S.R0117-A v1.0 Multimedia Priority Service (MMPS) for MMD-based Networks i Table of Contents 1 2 1 Introduction .1 3 1.1 Normative References1 4 1.2 Definitions and Abbreviations .1 5 2 General Description 1 6 3 High Level System Requirements 2 7 3.1 Gen
20、eral .2 8 3.2 MMPS Session Origination 3 9 3.3 MMPS Session Establishment .3 10 3.4 MMPS Session Progression .3 11 3.5 Priority Radio Resource Queuing .3 12 3.6 Priority for Data Services 4 13 3.7 MMPS Service User Priority Levels 4 14 3.8 Invocation on Demand 5 15 3.9 Roaming .5 16 3.10 Handoff 5 1
21、7 3.11 Charging Data Record .5 18 3.12 Queuing for Network Bearer Resources .5 19 3.13 Authorization 5 20 3.14 MMPS Invocation 6 21 4 Use Cases 7 22 4.1 Use Case 1 Mobile to Mobile Voice Call .7 23 4.2 Use Case 2 Mobile to PSTN Voice Call .7 24 4.3 Use Case 3 Streaming Video .8 25 4.4 Use Case 4 VoI
22、P .8 26 27 S.R0117-A v1.0 Multimedia Priority Service (MMPS) for MMD-based Networks ii Foreword 1 This standard was prepared by Technical Specification Group S of the Third Generation 2 Partnership Project 2 (3GPP2). 3 4 1 1 Introduction 1 Communication during times of disaster/crisis is critical to
23、 ensure that needed 2 resources are deployed to mitigate the effects of a disaster. Unfortunately, times of 3 disaster are when network resources are strained and it becomes difficult to access the 4 public network. During times such as this, it is important to provide capabilities in the 5 network
24、to allow a certain class of subscribers access to the scarce network resources. 6 This would enable the public emergency and safety agencies to appropriately respond to 7 the situation at hand. Wireless Priority Service for CDMA-based networks has already 8 been defined by TIA 1. It is important to
25、ensure that priority service continue to be 9 offered as networks evolve. Authorized users that respond to disaster or crisis 10 situations should have priority access to network communication resources in MMD-11 based Networks. Multimedia Priority Service (MMPS) will provide the needed priority 12
26、capabilities for voice, data, video, messaging and multimedia services to these 13 authorized users. MMPS allows qualified and authorized users to obtain access to 14 resources on a priority basis before all other PLMN users, subject to national/regional 15 regulations. This document defines the req
27、uirements to enable MMPS in MMD-based 16 Networks. 17 18 1.1 Normative References 19 1 TIA-917. Wireless Priority Service. 2004. 20 21 1.2 Definitions and Abbreviations 22 1. MMD Multimedia Domain 23 2. MMPS Service User An individual (or organization) who (or which) has received 24 a user priority
28、level assignment from a regional authority (i.e., government 25 agency authorized to issue priority assignments) and has a subscription to a 26 wireless service with a Commercial Mobile Radio Service (CMRS) provider that 27 provides MMPS. 28 3. PSTN Public Service Telephone Network 29 4. QoS Quality
29、 of Service 30 5. SC Service Code 31 6. VoIP Voice over Internet Protocol 32 33 2 General Description 34 Governmental, military, civil authorities and other essential users of public 35 telecommunications networks have a need for essential telecommunication services 36 including voice, data, video,
30、and multimedia in crisis and disaster situations. These 37 telecommunication services will be needed at the same time that access to the public 38 networks might be restricted due to damage, congestion, or faults. This situation 39 warrants mechanisms that provide secure and manageable ways to ident
31、ify authorized 40 users, and provide priority communications from access and session set up, through 41 session completion. Priority is established by the session originator, and will only apply 42 to terminating parties when the originating party has invoked priority. Any network 43 mechanisms defi
32、ned should provide priority treatment to authorized users. In addition 44 to priority treatment for radio system access, priority treatment includes, but is not 45 S.R0117-A v1.0 Multimedia Priority Service (MMPS) for MMD-based Networks 2 limited to, high probability of session completion, quality o
33、f service assurances, and 1 exemption from restrictive network management controls. While mechanisms have been 2 defined to provide priority service in traditional circuit-switched voice networks, it is 3 crucial that priority services continue to be provided in MMD-based Networks. 4 The need for me
34、chanisms to provide MMPS is global in scope. Several industry bodies, 5 of similar scope as 3GPP2, are currently involved in defining mechanisms in support of 6 Priority Service. The scope of this requirements document is to define the requirements 7 for MMPS for MMD-based Networks. The focus of thi
35、s MMPS effort will be on session 8 based services using MMD incorporating packet data and IP transport. 9 10 3 High Level System Requirements 11 3.1 General 12 SYS001 - MMPS Service Users shall be capable of using any service to which they have 13 subscribed and authorized. 14 Subscription to MMPS s
36、hould not preclude a subscriber from accessing services 15 available to non-MMPS subscribers. 16 17 SYS002 An MMPS Service User shall be capable of using any terminal supporting 18 MMD to initiate MMPS. 19 MMPS Service Users should not have to use special terminals or be assigned special 20 identiti
37、es/phone numbers to invoke MMPS. It is expected that the terminal will have 21 mechanisms (e.g., feature codes) to identify to the network that an MMPS session is 22 being attempted. 23 24 SYS003 An MMPS Service User shall be capable of invoking priority services for all 25 applications provisioned
38、to support the MMPS subscriber. These include, but are not 26 limited to voice calls, data, video conferencing, text messaging, and email. 27 An MMPS Service User should be able to invoke any service offered by the network and 28 have their traffic get priority services at the priority level assigne
39、d to the MMPS 29 subscriber. 30 31 SYS004 An MMPS Service User shall be capable of invoking more than one priority 32 session simultaneously if this capability is offered by the network. For example, making 33 a voice call and sending video simultaneously with both sessions receiving the same 34 pri
40、ority. 35 36 SYS005 An MMPS session shall be exempt from restrictive network management 37 controls. The network shall support policy controls to enable exemption of network 38 restrictions for MMPS Service Users. 39 Restrictive network management control such as call gapping in overloaded networks
41、40 shall not be used for MMPS sessions unless those controls are critical for network 41 survivability. 42 43 S.R0117-A v1.0 Multimedia Priority Service (MMPS) for MMD-based Networks 3 SYS006 Subject to regional/national regulatory policy, a Public Wireless Network 1 offering MMPS should have the ca
42、pability to retain public access as a fundamental 2 function. It shall be possible to limit MMPS traffic volume, so that it does not exceed a 3 specified percentage of any concentrated network resource usage (such as base station 4 capacity). 5 6 SYS007 -,A Public Wireless Network offering MMPS shal
43、l assign MMPS users the 7 highest priority level within their network with the exception of network management 8 users, unless precluded by national/regional policies. 9 10 3.2 MMPS Session Origination 11 PSO001 A session shall receive priority radio treatment (priority access to voice or 12 traffic
44、 channels) on the originating network when the session is originated by an MMPS 13 Service User. The radio access network shall apply the priority level assigned to the 14 MMPS subscriber. 15 16 3.3 MMPS Session Establishment 17 PST001 A session shall receive priority treatment (priority access to v
45、oice or traffic 18 channels) in the terminating mobile network, when the session is originated by an 19 MMPS Service User. The terminating radio access network shall apply the priority level 20 assigned to the originating MMPS subscriber 21 Since MMPS is invoked by an explicit user request, it can o
46、nly be initiated by the 22 originator of a service. It only applies to terminations when the originator is an MMPS 23 Service User. The priority of the terminating party is irrelevant. 24 25 3.4 MMPS Session Progression 26 PCP001 An MMPS Service User shall receive priority treatment as the users ses
47、sion 27 progresses through the mobile network(s). Under congestion conditions, an authorized 28 MMPS session shall be given priority over normal sessions in the originating mobile 29 networks, and in the terminating mobile network. In case the MMPS session traverses 30 or terminates in other network
48、s (e.g., the PSTN), the network shall support the 31 capability to indicate to the other network that this is an MMPS session. MMPS 32 sessions should not be preempted. 33 34 3.5 Priority Radio Resource Queuing 35 PRP001 When an MMPS Service User encounters a “no resource available” condition 36 in
49、the session origination, the MMPS session request shall be: 37 Queued in the cell serving the calling party, 38 Processed for the next available radio resources in that cell in accordance 39 with the MMPS Service Users priority level and session initiation time. 40 41 PRP002 When an MMPS Service User encounters a “no resource available” condition 42 in the session path in the terminating mobile network at session establishment, the 43 MMPS session shall be: 44 S.R0117-A v1.0 Multimedia Priority Service (MMPS) for MMD-based Network
