2 References

32.1013GPPPrinciples and high level requirementsRelease 17Telecommunication managementTS

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

– References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.

– For a specific reference, subsequent revisions do not apply.

– For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] ITU-T Recommendation M.3010 (2000): "Principles for a telecommunications management network".

[2] 3GPP TS 22.101: "Service aspects; Service Principles".

[3] 3GPP TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".

[4] IETF RFC 959: "File Transfer Protocol (FTP)"; October 1985, J. Postel, J. Reynolds, ISI.
(Status: Standard).

[5] IETF RFC 783: "Trivial File Transfer Protocol (TFTP)"; rev. 2, June 1981, K.R. Sollins MIT.
(Status: Unknown).

[6] IETF RFC 1157: "Simple Network Management Protocol (SNMP)": May 1990, J. Case, SNMP Research, M. Fedor, Performance Systems International, M. Schoffstall, Performance Systems International, J. Davin, MIT Laboratory for Computer Science. (Status: Standard).

[7] IETF RFC 2401: "Security Architecture for the Internet Protocol"; November 1998.
(Status: Proposed Standard).

[8] The Object Management Group (OMG) "The Common Object Request Broker: Architecture and Specification", Revision 2.3, June 1999. http://www.omg.org/technology/documents/vault.htm#CORBA_IIOP

[9] … [12] Void

[13] ISO 8571-1 (1988): "Information Processing Systems ‑ Open Systems Interconnection ‑ File Transfer, Access and Management ‑ Part 1: General Introduction".

[14] ISO 8571-2 (1988): "Information Processing Systems ‑ Open Systems Interconnection ‑ File Transfer, Access and Management ‑ Part 2: Virtual Filestore Definition".

[15] ISO 8571-3 (1988): "Information Processing Systems ‑ Open Systems Interconnection ‑ File Transfer, Access and Management ‑ Part 3: File Service Definition".

[16] ISO 8571-4 (1988): "Information Processing Systems ‑ Open Systems Interconnection ‑ File Transfer, Access and Management ‑ Part 4: File Protocol Specification".

[17] ISO/IEC ISP 10607-1 (1995): "Information technology – International Standardized Profiles
AFTnn – File Transfer, Access and Management – Part 1: Specification of ACSE, Presentation and Session Protocols for the use by FTAM".

[18] ISO/IEC ISP 10607-2 (1995): "Information technology – International Standardized Profiles AFTnn – File Transfer, Access and Management – Part 2: Definition of Document Types, Constraint sets and Syntaxes".

[19] ISO/IEC ISP 10607-3 (1995): "Information technology – International Standardized Profiles AFTnn – File Transfer, Access and Management – Part 3: AFT 11 – Simple File Transfer Service (Unstructured)".

[20] Void

[21] Void

[22] ITU-T Recommendation X.25 (1996): "Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating Equipment (DCE) for Terminals operating in the Packet Mode and connected to Public Data Networks by Dedicated Circuit".

[23] … [42] Void

[43] ISO/IEC 7776 (1995): "Information technology – Telecommunications and information exchange between systems – High-level data link control procedures – Description of the X.25
LAPB-compatible DTE data link procedures".

[44] ISO/IEC 8208 (2000): "Information technology – Data communications – X.25 Packet Layer Protocol for Data Terminal Equipment".

[45] ISO/IEC 8878 (1992): "Information technology – Telecommunications and information exchange between systems – Use of X.25 to provide the OSI Connection-mode Network Service".

[46] IETF RFC 1006: "ISO Transport on top of the TCP", Marshall T. Rose, Dwight E. Cass, Northrop Research and Technology Center, May 1987. Status: Standard.

[47] IETF RFC 793: "Transmission Control Protocol (TCP)", September 1981. Status: Standard.

[48] IETF RFC 791: "Internet Protocol (IP)", September 1981. Status: Standard.

[49] ITU-T Recommendation X.680 (2002): "Information Technology-Abstract Syntax Notation One (ASN.1): Specification of Basic Notation".

[50] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[51] 3GPP TS 22.115: "Service aspects; Charging and Billing".

[52] The Object Management Group (OMG) "The Common Object Request Broker: Architecture and Specification", Revision 2.1, August 1997. http://www.omg.org/technology/documents/vault.htm#CORBA_IIOP

[53] 3GPP TS 32.400-series: "Telecommunication management; Performance Management (PM)".

[54] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".

[55] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".

[56] 3GPP TR 22.121: "Service aspects; The Virtual Home Environment; Stage 1".

[57] 3GPP TS 32.140: "Telecommunication management; Subscription Management (SuM) requirements".

[58] 3GPP TS 32.141: "Telecommunication management; Subscription Management (SuM) architecture".

[59 to 99] Void

[100] TMF GB910: "Telecom Operations Map"; Approved Version 2.1 March 2000, (may be downloaded from http://www.tmforum.org.).

[101] 3GPP TS 32.102: "Telecommunication management; Architecture".

[102] ITU-T Recommendation M.3013 (2000): "Considerations for a telecommunications management network".

[103] Void.

[104] 3GPP TR 21.801: "Specification Drafting Rules".

[105] TMF GB910B: "Telecom Operations Map Application Note-Mobile Services: Performance Management and Mobile Network Fraud and Roaming Agreement Management"; Public Evaluation Version 1.1, September 2000. (May be downloaded free from http://www.tmforum.org.)

[106] OMA Service Provider Environment Requirements, OMA-RD-OSPE-V1_0-20050614-C, The Open Mobile Alliance™ (URL:http://www.openmobilealliance.org/).

[107] 3GPP TR 32.806: "Telecommunication management; Application guide for use of Integration Reference Points (IRPs) on peer-to-peer (p2p) interface".

[108] W3C SOAP Version 1.1 recommendation
(http://www.w3.org/TR/2000/NOTE-SOAP-20000508/).

[109] W3C SOAP Version 1.2 recommendation
(http://www.w3.org/TR/soap12-part1/).

[110] 3GPP TR 32.809: "Telecommunication management; Feasibility study of XML-based (SOAP/HTTP) IRP solution sets".

[111] 3GPP TS 32.150: V7.0.0"Telecommunication management; Integration Reference Point (IRP) Concept and definitions".

[112] ITU-T Recommendation M.3050.x (2006) series Enhanced Telecom Operations Map (eTOM).

[113] ITU-T Recommendation M.3050.1 (2004) Enhanced Telecom Operations Map (eTOM) – The business process framework.

[114] ITU-T Recommendation M.3050.2 (2004) Enhanced Telecom Operations Map (eTOM) – Process decompositions and descriptions.

[115] TR-069 Amendment 2, CPE WAN Management Protocol v1.1, Broadband Forum

[116] WS-I Basic Profile 1.1; http://www.ws-i.org/Profiles/BasicProfile-1.1.html

[117] W3C Web Services Description Language (WSDL) 1.1; http://www.w3.org/TR/wsdl

[118] IETF RFC 6241 Network Configuration Protocol (NETCONF); June 2011.

[119] 3GPP TS 32.107: “Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)”.