DOC

Ref TD 214 (PLEN4) Management Specification Harmonization

By Jack Lee,2014-05-07 12:32
5 views 0
Ref TD 214 (PLEN4) Management Specification Harmonization

    INTERNATIONAL TELECOMMUNICATION UNION COM 4 LS 72 E

    TELECOMMUNICATION

    STANDARDIZATION SECTOR

     Original: English STUDY PERIOD 2005-2008

    6/4, 8/4, 9/4, 10/4, 11/4 Beijing, 24 May-2 June 2006 Question(s):

    Ref. : TD 214 (PLEN/4)

    ITU-T Study Group 4 meeting (Beijing, 24 May-2 June 2006) Source:

    Management Specification Harmonization Status Report Title:

    LIAISON STATEMENT To: SG15 (Q.14/15), TeleManagement Forum, ETSI TISPAN (WG8), 3GPP SA5,

    3GPP2 TSG-S (WG5), ATIS TMOC, IETF O&M Area, NGNMFG Approval: Agreed to at SG 4 meeting, Beijing, 24 May 2 June 2006 For: Information and Action

    Deadline: 1 October 2006

    Tel: +47 90 10 18 10 Knut Johannessen, Q9/4 Rapporteur Contact: Fax: +47 940 53 977 Telenor Email: Norway knut-hakon.johannessen@telenor.com

SG4 is pleased to note significant interest and also a number of ongoing activities to achieve

    harmonization of management specifications, e.g. expressed at the Workshop on

    Telecommunication Management and Operation Support System in Beijing, 22-23 May 2006.

    This document is an updated summary of the status of management specification harmonization.

    1. Status

    1.1 NGN Management Architecture

    SG4 has published Rec. M.3060 to address the architecture for Management of Next Generation

    Networks.

    ETSI TISPAN WG8 has approved an update of TS 188 001 on NGN Management Architecture.

    This work requires harmonisation between ETSI, ITU-T Q.8/4, TMF, and 3GPP SA5.

    Key (input) specifications are:

    - Rec. M.3060

    - ETSI TS 188 001

    Attention: Some or all of the material attached to this liaison statement may be subject to ITU copyright. In such a case this will be

    indicated in the individual document.

    Such a copyright does not prevent the use of the material for its intended purpose, but it prevents the reproduction of all or part of it in a

    publication without the authorization of ITU.

    - 2 -

    COM 4 LS 72 E 1.2 Management Methodology

    Based on input from ETSI TISPAN, 3GPP SA5 has extended the definitions of IRP so that the

    specifications may also be used for other management interfaces (e.g. in TMN terminology: the

    interface between NML and SML) than the Itf-N as previously the scope of IRP.

    3GPP SA5 has work in progress on Solution Set templates and style guides and will share these

    documents for review as soon as they become available.

    3GPP SA5 have in response to SG4 indicated that the requirements specifications could benefit

    from improved methods but cautions that templates (tools) may become overly prescriptive and that

    the tools must be helpful.

    SG4 has progressed the work on revised M.3020 as described in the last report (see also A.3). The

    plan forward is work with SA5 and SG4 for development of common text to form the basis for

    updated draft SG 4 Recommendation and updates to SA5 32.150 series specifications, thus meeting

    the needs of both SA5 and SG4.

    SG4 is planning of consent of the revised M.3020 by October 2006 in order to support development

    of protocol-neutral specifications within SG4.

    1.3 Common Management Services

    The need of protocol-neutral Common Management Services has been identified by several

    organizations, e.g. 3GPP (through development of Information Services), ITU-T (e.g. as

    represented by Rec. Q.827.1 and also X.733.1 (or X.733.neutral)) and the TMF (through initiation

    of work on Management Functions).

    Question 9/4 has adopted the combination of 3GPP IRP specifications and ITU-T

    Recommendations as base text for alignment of requirements and analysis:

    Areas Input documents

    Non-ITU input (3GPP, ITU-T input

    TMF, …)

    Object Management 3GPP 32.661, 32.601 X.730, X.730, Q.827.1

    3GPP 32.662, 32.602

    TMF GB922 (Shared Information

    and Data model) and appropriate

    Addenda

    State Management 3GPP 32.671, 32.672 X.731, Q.827.1

    MTNM

    TMF GB922 Addenda 4SO

    (service overview), 4S-QoS

    (QoS), 5LR (logical resource),

    5PR (physical resource) and 5RO

    (resource overview) ITU-T\COM-T\COM04\LS\72E.DOC

    - 3 -

    COM 4 LS 72 E Alarm Management 3GPP 32.111-1, 32.111-2 X.733, X.736, X.733.1, Q.821,

    Q.827.1, X.733.1 (or X.733.neutral) MTNM

    TMF GB922 Addenda 4SO

    (service overview), 4S-QoS

    (QoS), 5LR (logical resource),

    5PR (physical resource) and 5RO

    (resource overview) Notification Management 3GPP 32.301, 32.302 Q.827.1, Q.821

    MTNM

    Log Management 3GPP 32.331, 32.332 Q.821 (Log Control), X.735

    MTNM

    TMF GB922 Addenda 4SO

    (service overview), 4S-QoS

    (QoS), 5LR (logical resource),

    5PR (physical resource) and 5RO

    (resource overview) Test Management 3GPP 32.321, 32.322 X.745, X.737

    Performance Management 3GPP 32.411, 32.412 X.738, X.739, Q.822, Q.827.1

    TMF GB922 Addenda 4SO

    (service overview), 4S-QoS

    (QoS), 5LR (logical resource),

    5PR (physical resource) and 5RO

    (resource overview)

Current draft text is found in TDXX-PLEN and results and potential for harmonization on Common

    Management Services will be liaised.

    1.4 Management of Ethernet

    Management of Ethernet is being progressed by MEF (Metro Ethernet Forum), TMF MTNM and

    SG4 (Question 10/4).

    At the September 2005 meeting, Question 10/4 decided to harmonize the current draft Q.840.1 with

    MEF D00051 (MEFLS002E) in response to a MEF request.

    Work is also ongoing in TMF as part of MTNM v3.5 to address management of Ethernet (“Ethernet

    Flow Domain Management”).

    TMF is requested to consider participation of MTNM Experts in the harmonization work between

    SG4 and MEF.

    The following TMF documents are considered relevant for management of Ethernet: GB922,

    Addendum 5LR (logical resource); GB926 Addendum 5LR (system view of logical resource);

    GB936 (SID-MTNM-MTOSI harmonisation).

    1.5 Charging and Billing

    Key (input) specifications are:

    ITU-T\COM-T\COM04\LS\72E.DOC

    - 4 -

    COM 4 LS 72 E - 3GPP 32.260 (IMS charging)

    - 3GPP 32.240 (charging architecture)

    - 3GPP 32.299 (Diameter)

    - ATIS-0300075 (TMOC-AIP-2005-024R10) - ATIS-0300075.1-2005 (TMOC-AIP-2005-046R6) ETSI TISPAN have decided to endorse the following 3GPP specifications for offline charging in

    TISPAN NGN Release 1:

    - TS 32.240

    - TS 32.260

    - TS 32.297

    - TS 32.298

    - TS 32.299

    The latest draft of the ETSI Charging specification DTS 282 010 (Work Item 02032) can be

    downloaded from the ETSI TISPAN Latest Drafts folder.

    1.6 Use of XML for management

    TISPAN WG8 plans to participate, with 3GPP SA5 and TMF MTOSI, in discussions on the

    possibility of agreeing a consistent approach to the use of XML/SOAP for Service Interfaces.

    1.7 Security

    The following specifications are relevant to harmonization of security specifications:

    - Draft 3GPP 32.372 (Security Information Service) http://www.3gpp.org/ftp/Specs/html-

    info/32372.htm

    - Existing ITU-T Recommendations in this area :

    o X.740 Security Audit Trail Function (1992)

    o X.741 Objects and attributes for access control (1993)

    o Q.815 Specification of a security model for whole message protection (2000)

    o Q.817 TMN PKI - Digital certificates and certificate revocation lists profiles (2001)

    - Draft 3GPP 32.373 (CORBA solution) http://www.3gpp.org/ftp/Specs/html-

    info/32373.htm

    - Draft 3GPP 32.375 (File Integrity solution) http://www.3gpp.org/ftp/Specs/html-

    info/32375.htm

2. Request for action

    Question 9/4 has been appointed as the focal point within SG4 for tracking harmonization status

    We welcome comments and input to the status report, both with regard to ongoing work not

    recorded and the need for cooperation within other areas.

ITU-T\COM-T\COM04\LS\72E.DOC

    - 5 -

    COM 4 LS 72 E

    Annex Supplementary information

    A.1 Goal of Harmonization

    SG4 has received requests for clarification of the concrete objectives of harmonization. Based on

    the discussion in a joint interim meeting of Question 7/4 and Question 9/4 with participation of

    3GPP Experts, is was agreed that the goal (or vision) of the effort on harmonization can be stated in

    terms of

    ? Single Convergent Solutions for new work

    o This objective is believed to be achievable through alignment and division of work

    between involved SDOs and Fora. As such, the challenge is believed to be

    organizational and to a lesser extent technical. ? Not re-invent existing specifications

    o This objective requires an understanding of the relationship between existing

    specifications. Work on relationship/correspondence between requirements from

    involved SDOs and Fora is needed, as well as e.g. relationship/correspondence between

    analysis from involved SDOs and For a. As an example: between ITU-T requirements

    and 3GPP Requirements and between ITU-T analysis and 3GPP Information Services. ? Conflict resolution

    o This objective is believed to be achievable through a focus on XML based design and

    other new management technologies.

    o Some alignment between methodologies is also believed to be necessary to meet this

    objective.

    A.2 Implications of Harmonization

    It is believed that existing management specifications (including ITU-T Recommendations) must

    evolve in order to support alignment of requirements. Although the focus of harmonization is on

    new designs (specifically XML), the work on harmonization of protocol-neutral specifications

    should seek to minimize the impact on existing designs.

    For this purpose, it should be investigated if enhanced mapping techniques between protocol-

    neutral analysis and protocol-specific designs are needed.

    A.3 Management Methodology

    3GPP has suggested to SG4 that in order to achieve the first goal (single convergent solutions for

    new work), that the first step of the harmonization process should be focused on methodology

    alignment (M.3020 and the 3GPP 32.150 series) notably by considering the adoption by SG4 of the

    SA5 IRP concept.

    Question 9/4 has revised Rec. M.3020 based on the following approach:

    - Enhancements to the requirements phase, including adaptation of the 3GPP use case template

    (from 32.803)

    - Enhancements to the analysis (protocol-neutral) phase, including adaptation of the 3GPP

    Information Service (from 32.151)

    - Adoption of the 3GPP UML repertoire (from 32.152)

    ____________

    ITU-T\COM-T\COM04\LS\72E.DOC

Report this document

For any questions or suggestions please email
cust-service@docsford.com