Question 7/4 -Requirements for Business to Business and Customer to Business Management interfaces
(Continuation of Questions 9/4 and 11/4 (2001-2004), with revised wording. Specification of the requirements specific to the needs of the X interface)
- Motivation
The telecommunications industry has recognized the
benefits of TMN for the
communications of management
information between the
Service Provider to Service
Provider, Service Provider to
Network Operator, and Service
Provider to Service Customer,
via the X interface. This
Question is also responsible
for the definition of the
Customer Network Management
service and Network-Network
management, based on the TMN
X-interface framework.
Communications requirements
need to be specified for the
BML to BML, SML to SML, and
NML to NML X interfaces. It
is important to specify the
management functionality and
associated management
information to be
communicated across these
interfaces. In particular,
with the rapid introduction
of Internet Protocol, many
Network Operators and Service
Providers are planning to
shift their networks to
packet-based networks. There
is a need to interconnect
current PDH and SDH networks
with newer IP-based
technologies but there are no
current Recommendations to
guide the management of
end-to-end Quality of
Service. Question 7/4 is the
lead question in SG4 for tML.
- Question
Study items to be considered include, but are not limited to:
- What additional TMN principles and architecture are required for the X interface to support the Service Life-cycle?
- What additional TMN management services, function sets, and functions, specific to the needs of the BML X interface,
are required to support SLA management of hybrid circuit-switched/packet-switched networks (HCPN)?
- What additional TMN management services, function sets, and functions, specific to the needs of the SML X
interface, are required to support Pre-Ordering, Ordering, Provisioning (including Bandwidth on Demand),
Connection Management, Trouble Administration and Billing management of HCPN?
- What additional TMN management services, function sets, and functions, specific to the needs of the NML X interface, are required to support Performance and Maintenance management of HCPN?
- What are the requirements for tML to support the use of XML for communications over the TMN X-Interface?
- What additional communication requirements and services, including those for security, need to be specified to support the X interface in support of legal and regulatory requirements for Administrations?
- What information is needed to be exchanged to support the management of the GoS in HCPN-based and IP-based networks?
- What information must be exchanged between service providers to support SLAs for end-to-end QoS?
- What maintenance is required for Recommendation M.3320, M.1500 Series, X.160 Series, and X.170 Series?
- What terminology is required in each new and revised Recommendation?
- What service management functions and management information is necessary to exchange across the X-Interface to
meet the requirement of E.106 to manage the Telecommunications for Disaster Relief for IP and HCPN networks?
- What are the new and additional requirements of the Customer Network Management (CNM)? The CNM service allows
customers of a public network to access management information or functions of the network to facilitate each customer's
own management of his telecommunications within the framework of the TMN-X interface. What revisions or extensions to
Recommendations X.160, X.161, X.162, or X.163 or new Recommendations dealing with architectural extensions are
required?
- What are the requirements for a Network-to-Network Management interface (NNM)? The NNM service allows network
operators to exchange management information or to perform management functions within the framework of the TMN-X
interface. What revisions or extensions to Recommendations X.170 or X.171 or new Recommendations dealing with
architectural extensions are required?
- Tasks
Tasks include, but are not limited to:
- Specify the X interface security requirements to support the interconnection needs of the SP to SP, SP to
NO, and SP to SC interfaces.
- Specify the protocol and interconnection requirements to support the needs for interconnection across the
X-Interface.
- Update the X Interface requirements documents as appropriate, (e.g., Recommendations M.3320, M.3341 for
QoS, and M. 3350 for ETS).
- Generate a high level requirements document for the X interface management information exchange to support BML,
SML, and NML functions.
- Formulate other X interface requirements document in support of TMN Management Services.
- Maintain Recommendations M.1520, M.1530, M.1532, M.1535, M.1537, and M.1539.
- Relationships
- ITU-T Study Group 2: Responsible for E.QOS-VOIP, E.106
- ITU-T Study Group 12: speech quality on IP-based Networks
- ITU-T Study Group 13: Lead ITU-T SG for IP Aspects
- ITU-T Study Group 16: responsible for H.323, including VOIP
- ETSI: responsible for TIPHON activity in support of VOIP telephony
- TM Forum: Projects on SLA/QoS Management, Shared Information/Data Model (SID), Value-Chain Market Center
(VCMC) |
