TIA-1137 300-2009 QoS Support for Converged Access Network Specification《融合接入网络规范的QoS支持》.pdf

《TIA-1137 300-2009 QoS Support for Converged Access Network Specification《融合接入网络规范的QoS支持》.pdf》由会员分享，可在线阅读，更多相关《TIA-1137 300-2009 QoS Support for Converged Access Network Specification《融合接入网络规范的QoS支持》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-1137.300-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.300 June 2009QoS Support for Converged Access Network Specification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers

2、and purchasers, facilitating interchangeability and 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-me

3、mber of TIA from manufacturing or selling products 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

4、in accordance with the American National Standards 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 p

5、roblems associated with its use or all applicable 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-0291.300-RF1, formula

6、ted under the cognizance of the TIA TR-45 Mobile (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

7、or practice of contents of this Document 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 applicatio

8、ns are claimed and called to TIAs attention, 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 pa

9、rty to discussions of any licensing terms 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 provid

10、ed in the Manual have been complied with 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 stan

11、dard, specification, recommendation or otherwise), whether 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 letter

12、s of assurance relating to any such Normative Reference; (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 publicat

13、ions 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 or

14、 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 MERCHANTABILI

15、TY 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 SAFE

16、TY 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 WITHOUT

17、 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 O

18、F 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. X.S0054-300-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

19、 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 ContentsQoS Support for Converged Access Network Specification CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References2 3 QoS Architecture4 4 Subscriber QoS

20、Profile.6 4.1 Subscriber QoS Profile Attributes6 4.1.1 Maximum Authorized Aggregate Bandwidth6 4.1.2 Authorized FlowProfileIDs for the User .6 4.1.3 Inter-User Priority6 4.1.4 Allowed Differentiated Service Markings.7 4.2 AGW Requirements.7 4.2.1 RADIUS 8 4.2.2 Diameter 9 4.3 AAA Requirements9 4.3.1

21、 RADIUS 9 4.3.2 Diameter 10 5 Backhaul QoS Management.11 5.1 AGW Requirements.11 5.2 eBS Behavior .11 6 Diffserv Support for CMIP/PMIP Traffic 12 6.1 AGW Requirements.12 6.2 HA Requirements 12 6.3 AT Requirements.12 X.S0054-300-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

22、 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 List of Figures ii LIST OF FIGURES Figure 1 QoS Architecture in CAN System 5 X.S0054-300-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

23、 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 iii List of TablesLIST OF TABLES Table 1 Additional RADIUS Attributes between SRNC and AGW for Subscriber QoS Profile .8 Table 2 Additional RADIUS Attributes between AGW and AAA for Subscriber QoS Profile .8 Table 3 Additional

24、Diameter AVPs between SRNC and AGW for Subscriber QoS Profile.9 Table 4 Additional Diameter AVPs between AGW and AAA for Subscriber QoS Profile 9 X.S0054-300-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

25、49 50 51 52 53 54 55 56 57 58 59 60 Revision History iv REVISION HISTORY Revision Date Remarks 0 December 2007 Initial release X.S0054-300-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 5

26、5 56 57 58 59 60 v ForewordFOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This document is a new specification. This document is part of a multi-part document consisting of multiple parts that together describes Converged Access Network. This docume

27、nt is subject to change following formal approval. Should this document be modified, it will be re-released with a change of release date and an identifying change in version number as follows: X.S0054-300-X version n.0 where: X an uppercase numerical or alphabetic character 0, A, B, C, that represe

28、nts the revision level. n a numeric string 1, 2, 3, that indicates an point release level. This document uses the following conventions: “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Should” and “should no

29、t” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not pr

30、ohibited. “May” and “need not” indicate a course of action permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. X.S0054-300-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

31、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 1.1 Scope 1 1 Introduction1 Introduction This document defines the stage-3 requirements for QoS support in the Converged Access Network (CAN). 1.1 Scope This document is part of a multi-part d

32、ocument consisting of multiple parts that together describes Ultra Mobile BroadbandTM1Wireless IP Network operation. The scope of this document covers support for over-the-air, backhaul and IP Quality of Service for Converged Access Networks. 1Ultra Mobile BroadbandTMand (UMBTM) are trade and servic

33、e marks owned by the CDMA Development Group (CDG). X.S0054-300-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 2.1 Normative References 2 References 2 2 References 2.1 No

34、rmative References This section provides references to other specifications and standards that are necessary to implement this document. 1 3GPP2: C.S0084-0 v2.0, “Ultra Mobile Broadband (UMB) Air Interface”, September 2007. 2 3GPP2: A.S0020-0 v1.0, “Interoperability Specification (IOS) for Ultra Mob

35、ile Broadband (UMB) Radio Access Network Interfaces”, November 2007. 3 3GPP2: X.S0054-100-0 v1.0, “Basic IP Service for Converged Access Network Specification”, December 2007. 4 3GPP2: C.R1001-F, “Administration of Parameter Value Assignments for cdma2000 Spread Spectrum Standards”, January 2007. 5

36、3GPP2: X.S0054-910-0 v1.0, “CAN Data Dictionary”, December 2007. 6 IETF: RFC2474, Nichols, et.al., “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers”, December 1998. 7 IETF: RFC2597, Heinanen, et.al., “Assured Forwarding PHB Group”, June 1999. 8 IETF: RFC2598,

37、Jacobson, et.al., “An Expedited Forwarding PHB”, June 1999. 9 IETF: RFC2983, Black, “Differentiated Services and Tunnels”, October 2000. 10 IETF: RFC2475, Blake, et.al., “An Architecture for Differentiated Services”, December 1998. 2.2 Informative References This section provides references to other

38、 documents that may be useful for the reader of this document. 3GPP2: X.S0054-000-0 v1.0, “CAN Wireless IP Network Overview and List of Parts”, December 2007. 3GPP2: X.S0054-102-0 v1.0, “Multiple Authentication and Legacy Authentication Support for CAN”, December 2007. 3GPP2: X.S0054-110-0 v1.0, “MI

39、P4 Specification in Converged Access Network Specification”, December 2007. 3GPP2: X.S0054-210-0 v1.0, “CMIP based Inter-AGW Handoff”, December 2007. 3GPP2: X.S0054-220-0 v1.0, “Network PMIP Support”, December 2007. 3GPP2: X.S0054-300-0 v1.0, “QoS Support for Converged Access Network Specification”,

40、 December 2007. X.S0054-300-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 2.2 Informative References 3 2 References3GPP2: X.S0054-400-0 v1.0, “Converged Access Network

41、Accounting Specification”, December 2007. X.S0054-300-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 2.2 Informative References 3 QoS Architecture 4 3 QoS Architecture C

42、AN system allows QoS differentiated IP services (such as VoIP and other data services) to be defined and specified independently within the confines of the UMB air interface (see 0). The UMB air interface supports multiple IP flows per AT. An IP flow is a series of packets that share a specific inst

43、antiation of IETF protocol layers. For example, an RTP flow may consist of the packets of an RTP/UDP/IP protocol instantiation, all of which share the same source and destination IP addresses and UDP port numbers. One or more IP flows can be mapped onto a single reservation identified by Reservation

44、Label and direction. One or more reservations are mapped to an over the air stream (see 0). As specified in 2 and 3, the eBS exchanges data with the AGW via a RAN PMIP4 GRE tunnel. The eBS and AGW establish a per-AT GRE tunnel to transport data packets between the AT and the AGW. This per-AT GRE tun

45、nel supports all IP sessions for the AT. If the AGW supports multiple RAN PMIP4 bindings per AT, the AGW may have a per-AT GRE tunnel with multiple eBSs 3, each tunnel using the same GRE key for the same AT. Figure 1 illustrates the QoS architecture in CAN system. It is a graphical illustration of t

46、he relationship between IP flows, GRE Tunnel, and over-the-air reservations. On the forward link, the AGW copies the DSCP contained in the inner IP header to the DSCP field of the outer IP header with consideration for DSCP marking specified by local policy. Upon receiving IP packets from an AGW, th

47、e eBS uses the packet filters received from the AT to map forward traffic to the corresponding over the air streams which may have different over the air QoS treatment. On the reverse link, the eBS either copies the DSCP contained in the inner IP header to the DSCP field of the outer IP header, assi

48、gns a DSCP value in the outer IP header based on over-the-air QoS (e.g., QoS FlowProfileID) and local backhaul policy (see 2). The AGW may modify the DSCP markings of the IP packet header based on the subscriber QoS profile and local policy. X.S0054-300-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

49、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 2.2 Informative References 5 3 QoS ArchitectureFigure 1 QoS Architecture in CAN System X.S0054-300-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 4.1 Subscriber QoS Profile Attributes 4 Subscriber QoS Profile 6 4 Subscriber QoS Profile 4.1 Subscriber QoS Profile Attribute