​Interface specifications and specification methodology​

(Continuation of Question 7/2)

Motivation

There are several interfaces between network management systems, including both intra-domain and inter-domain interfaces. The intra-domain interfaces are essential for the interoperability between management systems within one organization. The inter-domain interfaces ensure the exchange of management information between systems from different organizations, which can be business to business (B2B), custom to business (C2B) or business to government (B2G) interfaces. Standardized interface specifications can bring prompt, reasonable cost, automated, time effective communication processes to business enterprises, customers and government. This Question is responsible for the specification of the management requirements, both the protocol-neutral and protocol-specific versions of information models for both intra-domain and inter-domain interfaces.
The Question is further responsible for the generic information models (e.g., the ITU-T M.3100 series Recommendations) and the common management services (e.g., the ITU-T M.3700 series). The management information models may need to be extended to address the required enhancements to support future telecommunication/ICT architectures, capabilities, technologies, applications and services.
Besides the generic management information models and management functionalities, the Question is also responsible for the management interface specifications for specific network technologies, including transport (e.g., Ethernet), access (e.g., PON), and core network (e.g., signalling and packet switching network elements), NGN (including Telecommunications for Disaster Relief, TDR), SDN (Software Defined Network) / NFV (Network Function Virtualization), DLT (Distributed Ledger Technology), smart maintenance, and other areas or technologies as specified in the work of Question 5/2.
The essence of management standardization is in the specification of management functionality and associated management information for communication across management interfaces. The specification of a management interface is composed of interface requirements in the form of management functionality, the analysis and identification of the information to be communicated independent of the implementation means (termed an information model), and the transformation of the protocol-neutral information into a protocol-specific format (termed a data model). This process is generally referred to as requirements, analysis, and design (RAD).
The RAD process defines a methodology which provides a unified approach for all work on management interface specifications, including requirements capture, information analysis and design. Central to the methodology is protocol-neutral modelling.
This Question is responsible for the definition and maintenance of the management interface methodology (Recommendation ITU-T M.3020) and the frameworks specifying the use of management technologies, including UML, CORBA, XML-based Web-services, and REST/HTTP, and collaborating with other SDOs and forums to harmonize interface methodologies and where possible produce common management interface methodology. This Question is broadly responsible for the generation of any methodologies concerning the communication of management information within, between, and outside of management networks (such as for human-machine interfaces).
This Question is also responsible for management protocol profiles. With the application of future telecommunication/ICT architectures, capabilities, technologies, applications and services in network management, it is required to provide protocol support for exchanging management information, especially for Web services and XML technologies.

Question

Study items to be considered include, but are not limited to:
1) What enhancements and extensions are needed for the Requirements, Analysis and Design (RAD) methodology defined in Recommendation ITU-T M.3020, including support for service-oriented architecture concepts? What additional frameworks are needed for timely support of future management technologies, such as REST/HTTP, including methodologies for definition of representations and concepts and the mappings between them?
2) What collaboration inside and outside ITU-T is required to support the generation of both generic and specialized information models?
3) What general protocol-neutral and protocol-specific information models (including the common management services) are required to support further development of management interfaces (e.g., Q, B2B/B2C)?
4)  What enhancements are required to ITU-T M.1400 series and M.3100 series Recommendations to support future technologies?
5)  What enhancements and extensions to the generic and specialized information models are required to support cloud computing, energy saving, future telecommunication/ICT architectures, capabilities, technologies, applications and services identified by Question 5/2?
6)  What enhancements to the information model definition are required if AI/ML is applied in network management.
7)  What protocol support is required to exchange information for REST/HTTP based management?
8)  What maintenance of existing Recommendations is required?

Tasks

Tasks include, but are not limited to:
1) Enhancements to ITU-T M.3020 (jointly with 3GPP) based on future requirements.
2) Enhancements to ITU-T M.3020 for design phase, including support protocol-specific information modelling (especially for REST/HTTP based designs), by collaborating with other SDOs.
3) Development of additional frameworks and guidelines to support future management technologies, especially for the REST/HTTP based management technology.
4) Enhancements to Recommendations ITU-T M.1400 series and M.3100 series to support future network technologies.
5) Development of the information models to support the management of cloud computing, energy saving, future telecommunication/ICT architectures, capabilities, technologies, applications and services.
6) Extend Recommendations ITU-T Q.811 and Q.812 to support REST/HTTP based management.
7) Maintenance of Recommendations ITU-T G.850 Series, M.1400 series, M.1520, M.1530, M.1532, M.1535, M.1537, M.1539, M.3020, M.3100 series, M.3320, M.3340 series, M.3350 series, M.3600 series, M.3700 series, Q.751, Q.816 series, Q.820 series, Q.830 series, Q.840 series, X.160, X.161, X.162, X.163, X.170 and X.171, X.700, X.701, X.702, X.720 Series, X.730 Series, X.740 Series, X.750 Series, X.780 series and X.790 Series; X.710, X.711, Q.811 and Q.812.
An up-to-date status of work under this Question is contained in the SG2 work programme (https://www.itu.int/ITU-T/workprog/wp_search.aspx?sg=2).
Recommendations and Supplements under responsibility of this Question: ITU-T G.850 Series, G.8010, G.8011, M.1400 series, M.1520, M.1530, M.1532, M.1535, M.1537, M.1539, M.3020, M.3100 series, M.3320, M.3340 series, M.3350 series, M.3600 series, M.3700 series, ITU-T Q.751, Q.811, Q.812, Q.816 series, Q.818, Q.820 series, Q.830 series, Q.840 series, ITU-T X.160, X.161, X.162, X.163, X.170 and X.171, X.700, X.701, X.702, X.710, X.711, X.720 Series, X.730 Series, X.740 Series, X.750 Series, X.760, X.780 series and X.790 Series.
Texts under development: M.immbs, Q.rest, X.rest, X.rest-ics.

Relationships

WSIS Action Lines