D.4 QoS Management References
32.1013GPPPrinciples and high level requirementsRelease 17Telecommunication managementTS
D.4.1 Policy Based QoS Provisioning References
The following documents apply to policy-based QoS provisioning:
[1] IETF RFC 3060: "Policy Core Information Model – Version 1 Specification", Moore et al., February 2001.
http://www.ietf.org/rfc/rfc3060.txt
[2] IETF RFC 2251: "Lightweight Directory Access Protocol (v3)", M. Wahl, T. Howes, S. Kille, December 1997. http://www.ietf.org/rfc/rfc2251.txt
[3] IETF RFC 2940: "Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients" ,. A. Smith, D. Partain, J. Seligson. October 2000. http://www.ietf.org/rfc/rfc2940.txt
[4] IETF RFC 3084: "COPS Usage for Policy Provisioning (COPS-PR)"; K. Chan, J. Seligson, D. Durham, S. Gai, K. McCloghrie, S. Herzog, F. Reichmeyer, R. Yavatkar, A. Smith. March 2001. http://www.ietf.org/rfc/rfc3084.txt
[5] IETF RFC 2748: "The COPS (Common Open Policy Service) Protocol", J. Boyle, R.Cohen, D. Durham, S. Herzog, R. Rajan, A. Sastry. January 2000, http://www.ietf.org/rfc/rfc2748.txt
[6] IETF RFC 2753: "A Framework for Policy-based Admission Control", R. Yavatkar, D. Pendarakis, R. Guerin. January 2000. http://www.ietf.org/rfc/rfc2753.txt
D.4.2 Policy Based QoS Monitoring References
The following documents apply to QoS monitoring:
[7] 3GPP TS 32.101: " Telecommunication management; Principles and high-level requirements".
[8] 3GPP TS 32.102: " Telecommunication management; Architecture".
[9] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
[10] 3GPP TS 32.200: "Telecommunication management; Charging management; Charging principles".
[11] 3GPP TS 32.205: "Telecommunications management; Charging management; 3G charging data description for the CS domain".
[12] 3GPP TS 32.215: "Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain".
[13] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concepts and high-level requirements ".
[14] 3GPP TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".
[15] IETF RFC 959: "File Transfer Protocol", J. Postel, J.K. Reynolds. Oct-01-1985. http://www.ietf.org/rfc/rfc0959.txt?number=959
[16] IETF RFC 1901: "Simple Network Management Protocol, v2", J.Case, K. McCloghrie, M. Rose, S. Waldbusser. January 1996. http://www.ietf.org/rfc/rfc1901.txt?number=1901
[17] IETF RFC 2573: "SNMP Applications", D. Levi, P. Meyer, B. Stewart. April 1999. http://www.ietf.org/rfc/rfc2573.txt?number=2573
[18] IETF RFC 1907: "Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)", SNMPv2 Working Group, J. Case, K.McCloghrie, M. Rose, S. Waldbusser. January 1996. http://www.ietf.org/rfc/rfc1907.txt?number=1907
[19] TelemanagementForum (TMF) Telecom Operations Map (TOM), GB910, Approved Version 2.1, March 2000. http://www.tmforum.org/
[20] TelemanagementForum (TMF) TOM Application Note, Mobile Services: Performance Management and Mobile Network Fraud and Roaming Agreement Management, GB910B, Public Evaluation Version 1.1, September 2000. http://www.tmforum.org/
[21] TeleManagement Forum (TMF) NGOSS specifications http://www.tmforum.org/
[22] 3GPP TS 23.207: "End to End Quality of Service QoS Concept and Architecture".
[23] 3GPP TS 29.207: "Policy Control over Go interface".
[24] 3GPP TS 52.402: "Telecommunication management; Performance Management (PM); Performance measurements – GSM".
[25] Void.
[26] 3GPP TS 32.405: "Telecommunication management; Performance Management (PM); Performance measurements – Universal Terrestrial Radio Access Network (UTRAN)".
[27] 3GPP TS 32.406: "Telecommunication management; Performance Management (PM); Performance measurements – Core Network (CN) Packet Switched (PS) domain".
[28] 3GPP TS 32.407: "Telecommunication management; Performance Management (PM); Performance measurements – Core Network (CN) Circuit Switched (CS) domain".
[29] 3GPP TS 32.408: "Telecommunication management; Performance Management (PM); Performance measurements – Teleservice".
[30] 3GPP TS 32.409: "Telecommunication management; Performance Management (PM); Performance measurements – IP Multimedia Subsystem (IMS)".
Annex E (normative):
Type 2 protocols and information model for use in Type 4a management interface
The 3GPP management detailed specification has defined protocols and information model (network resource model) for use across Itf-N, i.e. the Type 2 management interface. Some, not all, of these protocols and network resource model are applicable for use across the Itf-P2P, i.e. theType 4a management interface.
The following lists identify the Itf-N protocols and information model relevant for use across Itf-P2P. When certain part of a specific Interface IRP specification (e.g. a particular operation) is not applicable for Itf-P2P, that certain part shall be identified as Exception here.
– List of Interface IRP :
– [Names of Interface IRP, with possible Exception (see above), are included here. These are to be determined.]
– List of NRM IRP :
– [Names of NRM IRP included here. The names are to be determined.]
A particular NRM IRP may have defined IOCs that are visible across the Itf-P2P but not visible across Itf-N. In such case, a note “This IOC is visible across Itf-P2P only.” should be part of the subject IOC description.
The standard does not specify which NRM IRP or which IOCs would be invisible across Itf-P2P. That “invisibility” is determined by the two involved peer DMs and is outside the scope of standardization.
At present, the standard does not expect the need to define NRM IRP(s) that are exclusively used by Itf-P2P. In the possible event that the need is required, the standard will specify a convention how to document those NRM IRP(s).
Annex F (informative):
Change history
|
Change history |
||||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Cat |
Old |
New |
|
Mar 2006 |
SA_31 |
SP-060100 |
0027 |
— |
Inclusion of Service Level Tracing Management |
B |
6.2.0 |
7.0.0 |
|
Mar 2006 |
SA_31 |
SP-060099 |
0029 |
— |
Extension/Generalization of the IRP definition and concept |
C |
6.2.0 |
7.0.0 |
|
Jun 2006 |
SA_32 |
SP-060260 |
0030 |
— |
Update an obsolete reference related to the Rel-7 withdrawn 32.403 |
F |
7.0.0 |
7.1.0 |
|
Sep 2006 |
SA_33 |
SP-060547 |
0031 |
— |
Add the Domain Manager and its Peer-to-Peer Interface (Itf-P2P) to the Telecom Management Architecture (OAM7-NIM-COOP) |
C |
7.1.0 |
7.2.0 |
|
Dec 2006 |
SA_34 |
SP-060721 |
0032 |
— |
Add SOAP as an allowed technology for solution sets |
B |
7.2.0 |
7.3.0 |
|
Dec 2006 |
SA_34 |
SP-060721 |
0033 |
— |
Improve structure and consistency of the definitions related to the IRP concept. |
F |
7.2.0 |
7.3.0 |
|
Mar 2007 |
— |
— |
— |
— |
Updated the title of Reference [21] ITU-T, added GSM logo |
— |
7.3.0 |
7.3.1 |
|
Jun 2007 |
SA_36 |
SP-070309 |
0034 |
— |
Identify the Interface IRPs and NRM IRPs which are applicable for Itf-P2P |
B |
7.3.1 |
8.0.0 |
|
Dec 2007 |
SP-38 |
SP-070731 |
0036 |
— |
Discontinuation of CMIP Solution Sets in Release 7 |
A |
8.0.0 |
8.1.0 |
|
Jun 2008 |
SP-40 |
SP-080 |
0037 |
— |
Remove statement about the Release 7 preferred technologies |
F |
8.1.0 |
8.2.0 |
|
Sep 2008 |
SP-41 |
SP-080465 |
0038 |
— |
Update of PLMN management processes, relation to IRPs |
F |
8.2.0 |
8.3.0 |
|
Dec 2008 |
SP-42 |
SP-080846 |
0039 |
— |
Update of PLMN management processes (eTOM supersedes TOM) |
F |
8.3.0 |
8.4.0 |
|
Sep 2009 |
SP-45 |
SP-090627 |
0040 |
— |
Introduce Service Oriented Architecture (SOA) in the context of Integration Reference Point (IRP) |
B |
8.4.0 |
9.0.0 |
|
Sep 2009 |
SP-45 |
SP-090627 |
0041 |
— |
Add SOA-based representation of the 3GPP Management Reference Model |
B |
8.4.0 |
9.0.0 |
|
Mar 2010 |
SP-47 |
SP-100035 |
0042 |
– |
Add missing features and descriptions of Service Oriented Architecture (SOA) in the context of Integration Reference Point (IRP) |
B |
9.0.0 |
9.1.0 |
|
Mar 2010 |
SP-47 |
SP-100035 |
0044 |
– |
Correction of 3GPP management application layer protocols |
F |
9.0.0 |
9.1.0 |
|
Mar 2010 |
SP-47 |
SP-100035 |
0045 |
– |
Addition of SOA supporting SS Definitions |
B |
9.0.0 |
9.1.0 |
|
Sep 2010 |
SP-49 |
SP-100489 |
0046 |
– |
Clarify terms used in IRP framework and architecture |
F |
9.1.0 |
10.0.0 |
|
Dec 2011 |
SP-54 |
SP-110707 |
0047 |
– |
Recommend NETCONF as a member of Management application layer protocols |
B |
10.0.0 |
11.0.0 |
|
Dec 2012 |
SP-58 |
SP-120799 |
0048 |
1 |
R11 CR 32.101 on Enhancements for Converged Management |
B |
11.0.0 |
11.1.0 |
|
June 2014 |
SP-64 |
SP-140359 |
0054 |
– |
remove the feature support statements |
F |
11.1.0 |
11.2.0 |
|
SP-140345 |
0055 |
2 |
Include the RPT in the Management Reference Model |
B |
||||
|
Sep-2014 |
SP-65 |
SP-140571 |
0057 |
– |
Removal of the Network Management Layer Service (NMLS) in the Management Reference Model |
F |
11.2.0 |
11.3.0 |
|
0056 |
– |
Include the Network Management Layer Service (NMLS) in the Management Reference Model |
B |
11.3.0 |
12.0.0 |
|||
|
Jan-2016 |
Update to Rel-13 (MCC) |
12.0.0 |
13.0.0 |
|||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
SP-170140 |
0065 |
2 |
C |
Add management entities |
14.0.0 |
|
2017-09 |
SA#77 |
SP-170655 |
0067 |
– |
C |
Addition of management functions and entities |
15.0.0 |
|
2017-09 |
SA#77 |
SP-170655 |
0068 |
1 |
F |
Replacement of 3G term |
15.0.0 |
|
2020-07 |
SA#88-e |
SP-200494 |
0070 |
1 |
B |
Introduction of QMC |
16.0.0 |
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |