Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 32.102  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   7…   7.3…   7.3.3…   7.4…   8…   9…   11…   14   A…   B…

 

7  TM Architectural aspectsp. 15

7.1  Architectural relationshipp. 15

The basic aspects of a TM architecture, which can be, considered when planning and designing a TM network are:
  • The functional architecture.
  • The information architecture.
  • The physical architecture.
The management requirements - from the business needs - will be the base for the functional architecture, which will describe the functions that have to be achieved. The information architecture defines what information that has to be provided so the functions defined in the functional architecture can be achieved. The physical architecture has to meet both the functional architecture and the information architectures. Other constraints from realty will also have impact to the physical architecture as cost, performance, legacy systems and all preferences any operator will have on a big capital investment as a TM network.
Copy of original 3GPP image for 3GPP TS 32.102, Fig. 7.1: Architectural relationship
Figure 7.1: Architectural relationship
(⇒ copy of original 3GPP image)
Up

7.2  Architectural constraintsp. 16

Large software systems, such as a network management system, are a capital investment that operators cannot afford to scrap every time its requirements change. Operators are seeking cost-effective solutions to their short-term needs. All these reality-related issues are vital constraints that should be addressed in the definition of the architecture.
The standardisation of 3GPP systems will bring new and different services that will add new demands on telecommunications management. Every PLMN organisation will include different functionality depending on the role-played and the equipment used by that entity. Regulation may force some of the roles that shall be taken. The need to link systems across corporate boundaries will be a consequence of this.
The rapid evolution of new services and technologies will also put requirements on the PLMN physical management architecture to accommodate market and technology trends. To future-proof investments and continuously be able to take advantage of new technologies are important constraints to the physical architecture.
A PLMN TMN should also adopt an architecture that will achieve scalability and extensibility of systems and networks so the TMN can grow as the services expand over time. To start with a small TMN and easily be able to expand the TMN after new requirements will be important issues for most PLMN operators.
The Telecom Management Network will be just one part of the overall business of a company. System management, general security issues and development strategies can be the target for company policies. System architectures and technology choices, as well as the availability of off-the-shelf commercial systems and software components that fulfil the requirements established in the present document, may be critical to an operator's implementation of the specified management architecture.
Up

Up   Top   ToC