1 Introduction to telecom OSS
Every telecom operator wants to have an automatic and efficient service Introduction, service repair, and service launch.
The goal of CEN systems is to provide a variety
Stable and reliable business. The system used by telecom operators is the power of technical telecommunication networks and services.
The lifeline between telecom networks. It is precisely through this lifeline that telecom operators use different Telecom Network Technologies
It is transformed into a variety of telecom services. This system is the Operational Support System (OSS) of China Telecom)
That is, the telecommunications operation support system, generally refers to providing business management, inventory management,
Engineering, planning, and maintenance functions. 1:
Figure 1 Relationship Between Telecom OSS and telecom networks and telecom services
At present, the OSS of China's telecom operators is also a management system of telecom network equipment, supplemented
Work-based maintenance, far from meeting the requirements of the business system for telecom OSS. The growing telecom network
The conflict between the new network technology and the backward Telecom OSS is becoming more and more prominent, which has seriously affected the telecom operation
The development of new business of China Telecom. Telecom OSS has become the bottleneck of telecom business development.
2. Analysis of OSS Standards and implementation strategies
At present, many international standardization organizations are conducting standards research and development work on Telecom OSS.
Representative of the International Telecommunications Union standard Department ITU-T Telecommunications Management Network (TMN) Research,
The China Telecom Management Forum TMF is designed for telecom OSS implementation research, independent telecommunications equipment and software developers (such:
Longxun, beidian, sun, etc.) introduces the CORBA technology into the TMN system through the Object Management Organization (OMG ).
Structure. These standardization organizations have studied Telecom OSS systems from different perspectives,
The following is a detailed analysis.
Telecommunications services (telephone, Internet access, teleconference, VPN No. 800, etc)
Telecom OSS
Telecommunications Network (Exchange Network, transmission network, data network, and support network)
-78-
2.1 TMN standard and Implementation Policy Analysis
In 1988, the ITU-T of the International Telecommunication Union first put forward the concept of Telecommunication Management Network (TMN ),
It is a management architecture of telecommunication networks, including network planning, configuration, installation, maintenance, and operation.
Line and management. TMN divides the management function into different logical hierarchies, from top to bottom for the transaction
Management layer, business management layer, network management layer, Network Element Management layer, and network unit layer. TMN for telecom OSS
The contribution of the framework model is that it provides theoretical guidance for the construction of a new generation of telecom operation support system,
It also pointed out the direction for the construction of telecom OSS.
The core of TMN is the management information model, which is not only reflected in the Q3 interface, but also in the OSS master
Software. At this stage, if TMN-Based OSS can be fully implemented according to the theory and architecture of TMN
Of course it is good, but unfortunately, the TMN's layered structure and functional structure are theoretically easy, and true
Implementing the integration of upstream and downstream OSS Based on Q3 information model is quite difficult, and the cost is not high.
Easy to accept by users. The reason is nothing more than two aspects: first, TMN theory and architecture although
It is quite complete, but its protocol and standard recommendations are too complicated, which greatly increases the difficulty of implementation.
The theory of TMN lacks strong support from telecom equipment and software developers. At present, few vendors can
Fully compliant with TMN standards. We may easily find the following example: a vendor's sub-Network Management
SNC or EMS adopts non-TMN Network Management Standards, and only one workstation is required.
Yes. If TMN's Q3 interface is used at the same level, a separate workstation is required.
Q3 interface adapter. At present, the ITU-T Study of TMN 4th research group is aware of this problem, and
We have proposed to separate the general principles of TMN from the technical implementation. Although the implementation of TMN standards is complex,
However, it has made great contributions to telecom network management. In terms of concept, theory, and architecture
The understanding of information network management is theoretically unified, so that people can communicate with each other in telecom network management.
There is a unified "language ".
2.2 TMF standard and Implementation Policy Analysis
The famous Standardization Organization of China Telecom Management Forum TMF (telemanagement Forum) also
I have been focusing on the research of OSS standards and specifications. It defines the OSS system as a network management system.
Management layer, business assurance layer, customer service layer, customer service interface, and system management process. Because
TMF is composed of a series of telecom operators and system integrators, so TMF is more focused on Telecom OSS
From the implementation of TMF's telecom operation diagram (Tom) Fab (fulfillment, assurance,
Billing) structure. Although TMF is influenced by the TMN theory, it is not completely
Based on the theoretical line of TMN, TMF adopts a regional modular implementation method for telecom OSS.
-79-
Figure 2 Fab telecom operation diagram of TMF
2.3 Analysis of CORBA standards and implementation strategies
Device manufacturers of carriers also use the Object Management Organization (OMG) to introduce the CORBA technology into TMN.
The system structure of China Telecom OSS. CORBA is a software object developed by OMG.
Interface Standard System, with common and general characteristics. OMG includes the vast majority of software/
Hardware vendor, which is developed by the vendor to cultivate the Software Component market after introducing the Software Component Concept
Port standard. Therefore, the introduction of the TMN architecture by the CORBA technology breaks the Q3/CMIP Technology in the TMN
And prompted the ITU-T 4th research group (TMN principle research group)
The principles are separated from the technical implementation. The CORBA technology is a research on the telecom OSS from the perspective of interface implementation,
It mainly describes and implements the Interface Information Model in a unified manner.
3. Analysis of the composition of telecom OSS
A typical Telecom OSS system can be divided into several parts, including customers, businesses, accounts, and network management,
Next we will analyze each part from the management domain perspective.
The customer management domain mainly implements service functions related to telecom customers, such as business systems and customer services.
System and web access functions, including basic customer data management, customer order management, and customer
Service quality management.
The business management domain mainly implements business process management and telecommunications business products based on standard business processes.
Management functions, including business planning and design, business process customization, and business lifecycle Definition
.
The accounting management domain mainly provides functions such as billing processing, billing management, and billing query, including
-80-
Data collection, billing, and billing.
Network management domains can be divided into network management subdomains and Network Element Management subdomains. The Network Management subdomain is negative.
Responsible for managing network resources, network services, network planning, Network Fault Analysis, network service testing, and network
Performance issues, mainly achieve network resource data management, Network Service Management, network capacity and
Topology Management, Network Fault Analysis, network service layer testing, network service planning, network performance analysis,
Network alarm management and other functions, including various specialized network management systems; Network Element Management subdomains are responsible for handling
All questions about network elements, including network element planning, Network Element monitoring, and network element configuration.
Achieve network element configuration management, Network Element fault data management, Network Element fault analysis, Network Element planning and installation, Network
Meta-performance monitoring and analysis, subnet management, Network Element fault handling, and other functions, including Network Element Management of various manufacturers
System. The network management domain is the core of the entire Telecom OSS and also the basis for supporting telecom services.
4. How telecom operators build OSS
Although the Division of telecom OSS Management domains is clearly defined, the implementation of telecom OSS is
Different from each other, how to build a practical Telecom OSS system that meets the development direction of network management is a large number
Serious problems faced by telecom operators. Next we will follow the OSS system standards and management
Based on our practical experience in building the telecom OSS system, this paper proposes how to build the telecom OSS system.
Overall Construction ideas.
4.1 start with building the OSS Subsystem
Telecom OSS systems include a wide range of systems and involve a lot of systems. telecom operators are building
When we believe in Oss, we cannot try to build a big and comprehensive OSS System at the beginning to solve all the problems,
This is impractical. Telecom operators should build OSS subsystems (such as transmission networks, exchange networks, and access networks)
Network Management of professional networks such as network and data network), and then gradually build and plan suitable network conditions
OSS system.
An OSS system that is practical and compliant with the development direction of network management should meet the following three conditions:
First, it has a variety of well-running operation support subsystems (that is, the OSS subsystem); second, it is for various professional
Reasonable business processes; third, maintenance personnel adapted to the operation support subsystem and business process management.
From the previous analysis, we can see that the first condition is the foundation of the entire OSS.
On the basis of subsystems, carriers should standardize the information exchange between subsystems of OSS instead
Depends on the specific implementation technology (such as CORBA or Q3) or encoding method. The second condition is that the telecommunications service is valid
The basis of operation and reasonable business processes can not only improve the efficiency provided by Telecom businesses, but also
Supplement the impact caused by imperfect network management system interfaces of the vendor. The third condition is the entire OSS system and industry
To ensure the effective operation of business processes, the operator cannot require too much automation of the OSS system, blindly
The pursuit of unreasonable automatic processing will only bring about higher O & M costs, and the O & M personnel who adapt to the position
It not only improves the continuity and stability of system operation, but also greatly reduces the operating costs of the system.
-81-
4.2 correctly handle vendor device Network Management
Due to the large number of devices purchased, telecom operators inevitably have the network management of many manufacturers' devices. In
When building an OSS system, the operator should not underestimate the vendor's management system, but should add the vendor's network management system
To a unified OSS system as part of the OSS.
The vendor's network management system is designed for the vendor's own device management, which is generally located at the Network Element Management layer.
OSS has an irreplaceable role. First, the vendor network management, as the network management of a proprietary device
Backup configuration management, fault management and other aspects play an important role, because the manufacturer for their own hardware and software
The vendor network management is the most suitable for device management.
From the perspective of equipment maintenance, you can improve the self-management capability of the network element.
Therefore, when constructing an OSS system, carriers do not intend to use the construction of the OSS system to replace the vendor.
The functions of the network management, but should be implemented by yourself through reasonable arrangement, site integration and business process management.
OSS is integrated with the manufacturer's device management system.
4.3 establish "business-driven" implementation goals
No matter how the telecom OSS chooses to implement it, we should establish a "business-driven" approach to achieve the goal
To drive the construction of telecom OSS.
Because the ultimate goal of telecom operators to build OSS is to improve the efficiency and
Type to better serve your own customers. For example, OSS should promote effective use of transmission networks.
Circuit resources, shortening circuit scheduling time, and accelerating circuit leasing business development.
When building their own OSS systems, telecom operators should not place their bets on certain technologies.
Focuses on business management, and standardizes information exchange between OSS subsystems. Implementation from OSS
From the perspective of development, the diversity of technology implementations (such as CORBA, GDMO, SNMP, and Web) has become a decision,
Blindly pursuing standards and implementing technologies, regardless of the actual needs of the telecom network business, will be only half the effort.
5 conclusion
Although the telecom OSS is complex, there are still some construction ideas for its composition and implementation. China Telecom
When building their own OSS, operators should consider their own telecom networks based on their actual conditions.
In this way, not only the network operation efficiency can be improved, but also the technical
The vitality and competitiveness of enterprises.
