ETSI TS 101 303-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Service Independent Requirements Definition Service and Network Managem .pdf

1、 ETSI TS 101 303 V4.1.1 (2003-11) Technical Specification Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Independent Requirements Definition; Service and Network Management Framework; Overview and Introduction ETSI ETSI TS 101 303 V4.1.1 (2003-11) 2

2、Reference RTS/TIPHON-01004R4 Keywords internet, IP, management, network, service, telephony, VoIP ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-P

3、rfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such

4、 versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject

5、 to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as

6、authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand

7、the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 101 303 V4.1.1 (2003-11) 3 Contents Intellectual Property Rights5 Foreword

8、.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 Network and service management overview9 4.1 Management principles 9 4.2 Network and service management architecture9 4.2.1 Functional architecture .9 4.2.2 Information architecture .

9、11 4.2.3 Physical architecture.11 4.2.4 Relationship between the management architectures and an implementation 12 4.3 Network and service management processes .13 4.3.1 Business process model 14 4.3.2 Flow-through processes 15 5 Relationship between service and network management and the TIPHON arc

10、hitecture.16 5.1 General .16 5.2 Relationship to TIPHON application and transport plane16 5.3 Relationship to TIPHON functional layers 16 5.4 Interconnection between management plane and TIPHON planes 17 5.5 Management layers, ownership domains and management interfaces .18 5.6 Relationship to TIPHO

11、N reference configuration19 5.7 Relationship with TIPHON business role model20 5.8 Relationship between TIPHON reference configuration and business roles21 6 Comparison of management methodology and TIPHON project method .22 6.1 Management methodology.22 6.2 Comparison with TIPHON project method22 7

12、 High level requirements and assumptions23 7.1 General requirements and assumptions 23 7.1.1 Network and service management framework23 7.1.2 General assumptions.24 7.2 QoS requirements and assumptions24 7.2.1 Assumptions .24 7.2.2 Transmission planning24 7.2.3 Maintenance25 7.2.4 Monitoring and ver

13、ification 25 7.3 Subscription management requirements and assumptions .25 7.3.1 Subscription management assumptions 25 7.3.2 High level requirements25 7.3.2.1 General25 7.3.2.2 Business model requirements26 7.3.2.3 Subscription management requirements .26 7.3.2.4 Process requirements.27 7.3.2.5 Inte

14、rfaces.27 7.3.2.6 Business aspects and integration.27 7.3.2.7 Security .27 7.3.2.8 Privacy 28 7.4 Performance management requirements and assumptions .28 ETSI ETSI TS 101 303 V4.1.1 (2003-11) 4 7.4.1 Policy and capability.28 7.4.2 Routing, admission and egress28 7.4.2.1 Admission .28 7.4.2.2 Transpo

15、rt And routing.28 7.4.2.3 Egress29 7.4.2.4 Service control 29 7.4.2.5 Addressing 29 7.4.2.6 Testing and analysis 30 7.4.2.7 Usage.30 7.4.2.8 Security .30 7.5 Fault management requirements and assumptions .30 7.5.1 Alarm surveillance requirements for TIPHON.30 7.6 Emergency telecommunications service

16、 requirements and assumptions .31 7.6.1 Requirements 31 7.7 Service Level Agreements (SLAs) requirements .31 7.7.1 Requirements 31 7.8 General security policy.32 7.8.1 Bill limitations 32 7.8.2 Secure billing administration 32 7.8.3 Subscriber and terminal management .32 7.8.4 Customer hotline.33 7.

17、8.5 Security related reports to the user33 7.8.6 Secure dialogue between operators.33 7.8.7 Contractual agreements between operators.33 7.8.8 Contractual agreements between service providers and subscribers.34 7.8.9 Security related reports to the service provider.34 7.8.10 Secure subscription proce

18、ss 34 8. Managed resource models35 8.1 Service resource model 35 8.2 Service control model.35 8.3 Call control model36 8.4 Bearer control model36 8.5 Media control model 36 8.6 General manageable entities.36 9 Management role model.37 9.1 Candidate roles.37 9.1.1 Typical actors/organizations .38 9.2

19、 Examples of possible relationships between organizations (actors).39 10 Key TIPHON management processes41 10.1 Processes 41 10.1.1 Fulfilment .41 10.1.2 Assurance41 10.1.3 Billing .42 10.2 Key interactions42 10.2.1 Inter-domain .43 10.2.2 Intra-domain .43 Annex A (informative): Example scenarios .4

20、4 A.0 Subscription management 44 A.1 TIPHON subscription management use case .47 A.2 Example business role model.48 History 50 ETSI ETSI TS 101 303 V4.1.1 (2003-11) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The info

21、rmation pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the

22、 ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR

23、000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). Introduction The present

24、 document forms part of TIPHON Release 4 and provides an overview and introduction to service and network management The Definition for Release 4 including all associated deliverables is contained in TR 101 301 18 where the relationship of the present document with other TIPHON release 4 deliverable

25、s is shown. ETSI ETSI TS 101 303 V4.1.1 (2003-11) 6 1 Scope The present document establishes and defines the management principles and high-level requirements for the management of TIPHON services and networks. In particular, the present document identifies: an overview of the management architectur

26、e, including the interactions between the management plane and the TIPHON application plane and TIPHON transport plane. the end to end processes required to support the management (e.g. provision, maintenance and billing) of TIPHON service capabilities. Including the management model required to sup

27、port the interactions necessary to ensure inter-operability between customers, service providers (including Value Add service providers), network providers and Trusted Third Parties etc. high-level management requirements managed resource model(s) (i.e. candidate manageable entities, in other words,

28、 resources that can be controlled and/or monitored, within the TIPHON architectural model). The present document is intended to provide a framework for the further development of TIPHON management specifications as well as management products based on those requirements. The present document can be

29、seen as a framework for the development of all other Technical Specification addressing the management of TIPHON. TR 101 835 10 provides details of the steps involved in a TIPHON release. 2 References The following documents contain provisions which, through reference in this text, constitute provis

30、ions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which

31、are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ITU-T Recommendation M.3010: “Principles for a Telecommunications management network“. 2 ITU-T Recommendation M.3200: “TMN management services and telecommunications managed areas: ov

32、erview“. 3 ITU-T Recommendation M.3400: “TMN Management Functions“. 4 TeleManagement Forum GB910: “Telecom Operations Map (TOM)“. 5 TeleManagement Forum GB921: “enhanced Telecom Operations Map (eTOM)“. 6 Void. 7 ITU-T Recommendation I.130: “Method for the characterization of telecommunication servic

33、es supported by and ISDN and network capabilities of an ISDN“. 8 ITU-T Recommendation I.140: “Attribute technique for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN“. 9 ITU-T Recommendation I.210: “Principles of telecommunication services

34、supported by an ISDN and the means to describe them“. ETSI ETSI TS 101 303 V4.1.1 (2003-11) 7 10 ETSI TR 101 835: “Telecommunications and Internet Protocol Harmonization over Networks (TIPHON); Project method definition“. 11 ETSI TS 101 314: “Telecommunications and Internet Protocol Harmonization Ov

35、er Networks (TIPHON) Release 3; Abstract Architecture and Reference Points Definition; Network Architecture and Reference Points“. 12 ITU-T Recommendation M.3020: “TMN Interface Specification Methodology“. 13 ITU-T Recommendation M.3013: “Considerations for a telecommunications management network“.

36、14 ETSI TR 101 329-7: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; End-to-end Quality of Service in TIPHON systems; Part 7: Design guide for elements of a TIPHON connection from an end-to-end speech transmission performance point of view“. 15 ITU-T Recomm

37、endation Q.821: “Stage 2 and Stage 3 description for the Q3 interface - Alarm surveillance“. 16 ETSI TR 101 303: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Requirements definition study; Introduction to service and network management“. 17 ETSI TS 102 02

38、4-4: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; End-to-end Quality of Service in TIPHON Systems; Part 4: Quality of Service Management“. 18 ETSI TR 101 301: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Releas

39、e Definition; TIPHON Release 3 Definition“. 19 ETSI TS 101 878: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Service Capability Definition; Service Capabilities for a simple call“. 20 ITU-T Recommendation X731: “Information technology - Open Systems Inter

40、connection - Systems Management: State management function“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: actor: organization playing one or more roles administrative domain: network controlled by a single operat

41、or NOTE: It encompasses both network and management domains. management domain: collection of one or more management systems, and zero or more managed systems and management sub domains that is administered by a single operator role: activity performed by an actor (e.g. organization) NOTE: Each acto

42、r can play many roles. A role is defined by a set of properties or attributes that describe the capabilities of an entity that can be performed on behalf of other role(s). Service Level Agreement (SLA): formal negotiated agreement between two parties NOTE: It is a contract, or part of one, that exis

43、ts between the service provider and the service customer, designed to create a common understanding of services, priorities, responsibilities, etc. ETSI ETSI TS 101 303 V4.1.1 (2003-11) 8 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ALC Automatic Lev

44、el Control ATM Asynchronous Transfer Mode B2B Business to Business BC Bearer Control BPM Business Process Model CC Call Control CMIP Common Management Information Protocol CORBA Common Object Request Broker Architecture DHCP Dynamic Host Configuration Protocol DNS Domain Name Service eTOM enhanced T

45、elecommunications Operations Map ETS Emergency Telecommunication Service FCAPS Fault, Configuration, Accounting, Performance, Security IP Internet Protocol ITU International Telecommunications Union LDAP Lightweight Directory Access Protocol MC Media Control MD Mediation Device MIB Management Inform

46、ation Bases NE Network Element NEF Network Element Function NO Network Operator OAM the information architecture; and the physical architecture. The functional architecture describes the appropriate distribution of functionality within the management network, appropriate in the sense of allowing for

47、 the creation of function blocks from which a management network of any complexity can be implemented. The definition of function blocks and reference points between them leads to the requirements for the interface specifications. Figure 1 illustrates the functions and reference points in the functi

48、onal architecture. The information architecture is based on standardized open management paradigms that support the standardized modelling of the information to be communicated. telecoms management standardization activities will not develop a specific management paradigm but build upon industry-rec

49、ognized solutions, focusing primarily on object-oriented techniques. Specific management paradigms may be used in standards when judged to be adequate. The physical architecture describes interfaces that can actually be implemented and examples of physical components that make up the management network. 4.2.1 Functional architecture The management functional architecture, at its simplest, comprises functions connected by reference points. Functions include Network Element Function (NEF), Operations System Function (O