1、 TIA-1127 October 2011All-IP System MMD Policy Enhancements NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisti
2、ng 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 not conforming to such Standards and
3、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 Institute (ANSI) patent policy. By su
4、ch 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 regulatory requirements. It is the res
5、ponsibility 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-0278, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document wil
6、l 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 use of intellectual property rights (“I
7、PR”), 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 from the holder thereof is requested, a
8、ll 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, which are instead left to the parties i
9、nvolved, 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 Document or its contents. If the Docume
10、nt 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 such reference consists of mandatory,
11、 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; (ii) TIAs policy of encouragement of vo
12、luntary 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 to TIA of a claim of Essential Patent(
13、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 the Document. ALL WARRANTIES, EXPRESS
14、 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 INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCL
15、AIMS 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 SERVICE REFERRED TO IN THE DOCUMENT OR PR
16、ODUCED 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 CONSEQUENTIAL DAMAGES (INCLUDING DAMAGE
17、S 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 OF DAMAGES IS A FUNDAMENTAL ELEMENT OF
18、 THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Revision History Revision Description Date Rev. 0 v1.0 Initial Publication June 2008 All-IP System MMD Policy Enhancements X.S0053-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
19、22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i ContentsAll-IP System MMD Policy Enhancements CONTENTS 1 Introduction1 2 References2 2.1 Normative References2 2.2 Informative References2 3 Definitions, Symbols and Abbreviations3
20、3.1 Definitions .3 3.1.1 Symbols and Abbreviations.3 4 FUNCTIONAL OVERVIEW4 4.1 Relationship to SBBC4 4.2 Descriptions of Enhancements.4 4.2.1 Policy Contexts4 4.2.2 Admission Control.5 4.2.3 Policy Management .5 4.2.4 Authentication .5 4.2.5 Privacy.6 4.3 Functional Capabilities 6 4.3.1 Types of Po
21、licy7 4.3.2 Types of QoS Resource Reservation Scenarios.7 4.3.3 Mobility Management Policy 7 4.3.4 Coordination of Policy Across Networks 8 5 ARCHITECTURAL MODEL AND REFERENCE POINTS .8 5.1 Functional Model.8 5.1.1 Policy Management Functional Architecture (Non-roaming) .8 5.1.2 Policy Management Fu
22、nctional Architecture (Roaming) 9 5.2 Functional Entity Descriptions.10 5.2.1 Policy the H-PCRF may be applying subscriber policies in terms of what level of service is granted to a particular flow, where the V-PCRF may be using network policies to determine what level of service a roamer from their
23、 particular home network is entitled to. 4.3.2 Types of QoS Resource Reservation Scenarios The PCRF concurrently should support the following QoS resource reservation scenarios: Network initiated QoS with policy-push: Subscriber terminals do not use QoS signaling protocols (e.g., RSVP or NSIS) for n
24、etwork resource reservation. Instead, whenever a user terminal starts, modifies, or ends an application, it contacts the AF and, then, it is responsibility of the AF to request to the PCRF the appropriate QoS support in the network. User-requested QoS with policy-push-pull: Applications in the user
25、terminal are able to request network resources to accommodate their QoS need using native QoS signaling protocols. The requested QoS requires the authorization from the PCRF. User-requested QoS with policy-pull: User terminals are capable of sending QoS requests over signaling protocols for their ow
26、n QoS needs, and do not require prior authorization. Authorization for the user-requested QoS is obtained “on the fly“ at the time the request is actually signaled to the AGW and may require a policy pull operation to the PCRF so as to verify AGW resource availability during regular processing of th
27、e QoS signaling messages by the AGW. 4.3.3 Mobility Management Policy Mobility policy governs mobility management in inter-technology handoffs and roaming. The importance of mobility policy is to integrate operator and network management strategies and X.S0053-0 v1.0 All-IP System MMD Policy Enhance
28、ments 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 4 FUNCTIONAL OVERVIEW 8 5.1 Functional Modelpolicies into the handoff and roaming control in order to accommodate different
29、 access technologies and mobility scenarios. Policy-based mobility management will: ensure that the mobile handoff and roaming are managed by mobility management policies; control whether or not a mobile handoff or roaming request is allowed (under the conditions of operator domain agreements, netwo
30、rk access technologies provide a means of managing the mobile handoff and roaming priority (e.g., in a case of network failures or peak hours of a day). 4.3.4 Coordination of Policy Across Networks Coordination of policy across networks or policy peering occurs between MMD providers that have agreed
31、 to exchange and enforce policy on behalf of each other. Policy peering may happen as a result of a subscriber roaming on another providers network or as a result of a call. Policy peering allows the home network provider to be able to apply subscriber specific policy to the use of both the visited
32、and home networks. In this context, policy management in the home network takes the additional role of identifying and forwarding relevant inter-provider policy information to the visited network. Given the relevant information, policy peering enables some level of subscriber specific policy to be i
33、nstalled in the visited network, thus allowing the policy management function in the visited network to act as a “representative” of the corresponding home-network policy management function. The visited network applies its own network policies as well. In the visited network, network policy defines
34、 rules about how resources in the visited network should be available to the roaming subscriber 5 ARCHITECTURAL MODEL AND REFERENCE POINTS 5.1 Functional Model This section describes the policy management functional architecture and the functional entities impacted by the policy enhancements and the
35、 interface reference points. 5.1.1 Policy Management Functional Architecture (Non-roaming) Figure 1 illustrates the policy architecture for the non-roaming case when a subscriber is located in its home network. Note, only policy related signaling interfaces are shown. No bearer interfaces are shown.
36、 All-IP System MMD Policy Enhancements X.S0053-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 5.1 Functional Model 9 4 FUNCTIONAL OVERVIEWPolicy RepositoryPolicy & Charg
37、ing Rules Function (PCRF)Access Gateway(AGW)IMS Application Function(AF)T2Network Policy Repository(NPR)HSS -Subscriber Policy Repository (SPR)Non-IMSApplication Function(AF)Tx TxU23/TyLMA/HAU20Figure 1 Policy Management functional model (non-roaming) 5.1.2 Policy Management Functional Architecture
38、(Roaming) Figure 2 illustrates the policy architecture for the roaming case when a subscriber is in a visited network. Note, only policy related signaling interfaces are shown. No bearer interfaces are shown. X.S0053-0 v1.0 All-IP System MMD Policy Enhancements 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
39、 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 4 FUNCTIONAL OVERVIEW 10 5.2 Functional Entity DescriptionsHomePolicy & Charging Rules Function(H-PCRF)Access Gateway(AGW)VisitedPolicy & Charging Rules Function(V-PCR
40、F)Home NetworkVisited NetworkT2Home Policy RepositoryHome-Network Policy Repository(H-NPR)HSSSubscriber Policy Repository (SPR)Visited-NetworkPolicy Repository(V-NPR)T2TxIMS Application FunctionNon-IMSApplication FunctionTxU18/T3U23/TyLMA/HAU20Figure 2 Policy Management functional model (roaming) 5.
41、2 Functional Entity Descriptions This section describes the functional entities involved in policy management. 5.2.1 Policy & Charging Rules Function (PCRF) The Policy Charging & Rules Function (PCRF) acts as a Policy Decision Point (PDP) for Service Based QoS Authorization, Local Resource Based Pol
42、icy (LRBP) control and Mobility Management Policy. The PCRF makes decisions about resource requests based on local network policy. The PCRF is also responsible for providing, to the Access Gateway (AGW), operator determined dynamic charging rules. The Charging Rules Function (CRF) of the PCRF is res
43、ponsible for formulating charging rules based on provisioned information, subscription information, input from Application Functions (AF), or operator determined dynamic All-IP System MMD Policy Enhancements X.S0053-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
44、 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 5.2 Functional Entity Descriptions 11 4 FUNCTIONAL OVERVIEWcharging rules, and for providing such charging rules to the Bearer Management Function (BMF) of the AGW, which is a Policy Enforcement Point (PEP)
45、. Some PCRF functions can be associated with a home network for the purpose of representing subscription and home based application function information. Some PCRF functions can be associated with the network of the AGW for purpose of enforcement of local policy. In roaming situations where the AGW
46、is located in a visited network, there may be both a home and a visited PCRF. In this case the visited PCRF may act as a proxy or redirect agent for communications between the Access Gateway and the home PCRF (also see section 5.1.2). 5.2.2 Access Gateway The Access Gateway (AGW) is a Policy Enforce
47、ment Point (PEP) for the following policies: Mobility management Admission control management QoS management Charging management Packet flow optimization Service interaction management Privacy management Authentication management NAT traversal management Network management Security management 5.2.3
48、Application Function (AF) The Application Function (AF) is responsible for requests to the AGW for the purpose of controlling packet flows. The Application Function represents the application or service level intelligence for any service running over the IP bearer, which needs Service Based Authoriz
49、ation. This capability is not limited to IMS based services. The AF may also provide information to the PCRF to help in the determination of dynamic charging rules for specifically identified service data flows. Such information may include an application identifier, media component descriptions, charging identifier, etc. 5.2.3.1 Types of Application Functions The enhanced policy architecture considers three distinct types of applications: SIP, non-SIP, and over-the-top. IMS Application Functions, such as the P-CSCF, intera
