Ericsson CPP Survey

1、other boardsother boardsother boardset-m1et-m1et-m1gpb active core mpgpb active core mpgpb passive core mpgpb passive core mp - 298 copyright ericsson ab, 2003en/lzt 123 6795 r2a lms lms bp xx repertoire: a group of loadmodules that are going to be executed in the same processor. software allocation

2、 1 core mps core_mp software allocation xx software allocation 2 bps lms cpp survey software allocation links the repertoires to the correct processor figure 9-13 phase 1 - software allocation vs. repertoires when creating the upgrade packet the load modules have to be linked with the boards in the

3、node in the upgrade control file. this file is created in the software manager of the element manager. the tools for this are: software repertoires software allocations software repertoires a software repertoire is a group of loadmodules that will execute on the same processor. for example, all load

4、modules that will execute on the core mps will be grouped together in the same repertoire (ex. core_mps). software allocations the repertoires define the loadmodules that will execute in all the processors. however, they will not define where the processor is. contentdescription product data history

5、 part ftp server infoip address of the ftp server compability data product data upgrade case this part of the file describes which earlier deliveries that are compatible with this delivery. example: earlier ups: a,b,c and d this up is e and is contain information about how to upgrade from b, c and d

6、. piu typesall types of piu to be used repertoirescontains lms and relations to piu upgrade sequencedescribes what will happen during the upgrade (restarts, upgrades etc) and in which sequence it will happen. lm infoall info about the loadmodules. for example memory allocation (heap, pool, date) en/

7、lzt 123 6795 r2acopyright ericsson ab, 2003 - 299 9 operation and maintenance the software allocation links the correct set of repertoires to the correct set of boards. example, the core mps in a rnc is located on slot 10 and 11. the software allocation links the repertoire, core mps, to these slots

8、. upgrade control file (ucf.xml) this file contains the information that the node needs to perform the upgrade. see the table below. table 9-1 the content of the ucf.xml file - 300 copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey software installation /plnh /d gpb all other gpbs /plnh /d gp

9、b all other gpbs /c /d gpb active core gpb upgrade packet distribution of loadmodules figure 9-14 phase 2 - installation the software installation process aims to install the upgrade package at the file system at the network element. the process is performed manually using the cpp element manager, i

10、.e. the software manager. the software (up) is downloaded from a central ftp server. the software manager will guide the operator step by step through the process. once the installation phase is finished, the new software is pre-loaded into the memories and the node is ready for the upgrade phase. s

11、oftware upgrade the sw upgrade procedure provides functionality to activate new sw previously installed using the sw installation system function, and creates a new current configuration version (cv). a precondition for the sw upgrade function is that the correct sw and hw are successfully installed

12、 on the network element during the software installation phase. from the sw upgrade graphical user interface (gui) the operator will be able to perform the following tasks. select an upgrade package update network element software confirm new software en/lzt 123 6795 r2acopyright ericsson ab, 2003 -

13、 301 software manager 9 operation and maintenance the upgrade needs a manual confirmation by the operator in order to remain active. if no confirmation is made within a certain time, the network element will automatically roll back to previous configuration version (with previous software). gpb data

14、base ram upgrade packet up rebuilding of database confirm cv1 cv2 software backup flashdisk disabled part upgrade install new entry figure 9-15 phase 3 software upgrade the upgrade flow can be summarised as the following steps: 1) a new upgrade package is stored on the node. 2) the cpp is ordered to

15、 download the new upgrade package. 3) the cpp node interprets the upgrade information (xml) and retrieves the missing load modules. 4) the cpp node is ordered to upgrade the node. 5) a new cv is created. 6) the new program objects are distributed to the processors. 7) board restart is made one board

16、 at the time. 8) a new cv is created. the operator must confirm the successful upgrade. - 302 copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey configuration version concept the configuration version (cv) concept in cpp is used both for software management and backup/restore. the cv mainly i

17、ncludes a database export. since the database contains the managed object model (mom), represented as database tables, all information about cpp is included. pointers to load modules e.g. information about name and version, hardware configuration and reference to an upgrade package is also included.

18、 the cv does not include the actual load modules or the upgrade package. (note that on-line documentation is regarded as a load module). a new cv can be created automatically (every 24 hours) or on operator command and is stored locally on the cpp flash disk (a.k.a. cv backup). technically 50 cvs ca

19、n be stored. however the current flash disk space will limit number of cvs to about 3-8, depending on node size. restore of a cv (a.k.a.cv restore) is done locally on the network element and requires that necessary load modules (correct upgrade package) are already installed. the cvs on the flash di

20、sk can be retrieved and stored on an external ftp server used as external backup device. this is done from an ftp client and it is up to the administrator to keep track of the cvs, which upgrade package it refers to and to which node they belong, for instance by having a file system that correspond

21、to the nodes. the upgrade package is never retrieved from the network element to the ftp server, because it already exists on a server. however, it can be deleted on the network element to save space. deletion must then be done from an ftp client. it is not recommended to remove old upgrade packages

22、 (and load modules) until a verified upgrade is done, because it must always be possible to restore previous version without transferring configuration version and upgrade package from an ftp server. if it is necessary anyway to restore to a previous upgrade package that is no longer installed on th

23、e node (this should be an exception) then the following is done: 1) there are one “holy” minimal lms and cvs that must not be removed. the network element is restarted using this minimal configuration. 2) when the network element is started, a software installation is done. i.e. an installation of o

24、ld software is done on the disk. 3) when the node has the correct upgrade package stored, the administrator transfers the configuration to be used by using an ftp client. en/lzt 123 6795 r2acopyright ericsson ab, 2003 - 303 9 operation and maintenance 4) a normal cv restore is done, from local flash

25、 disk to ram, by selecting active cv in a list and restarting the network element. when a normal software installation (upgrade) is performed, the restart to the minimal configuration is usually not necessary. in other words, a normal software upgrade will not affect the traffic so much. the softwar

26、e manager (em) in this case also supports the operator with step-by-step instructions of the complete upgrade flow. fault management general when a fault occurs in the network element, it is possible to issue two different types of alarms, a primary alarm and secondary alarms. the primary alarm cont

27、ains information about the original fault (the root cause) and the secondary alarms about the consequences the fault generates. all current alarms in the network element, i.e. the active alarm list, and the alarm log can be viewed from the element management application implemented in the network el

28、ements. whenever a fault is detected in the network element an alarm is raised and the active alarm list is updated. the alarm disappears from the active alarm list when it is cleared. it is then moved to the alarm log. there exists an alarm log within a network element where all alarms are stored.

29、the alarm log is persistent and the size of the alarm log can be altered. the alarm log provides all alarm information, like alarm state changes. when an alarm is ceased, the state change will be logged, but the alarm will not be removed from the alarm log. it is possible to view the content of the

30、alarm log. in each alarm there is unambiguous information that points to the fault objects. there is an operation procedure documentation on-line connected to each alarm with suggested repair actions. alarm suppression an overall goal with fault management functionality is to reduce the amount of al

31、arms that are issued from the network. to support that, cpp provides support for alarm suppression. the majority of - 304 copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey fault situations will produce only one primary alarm and when applicable also a secondary alarms. alarm subscription in

32、the network elements only simple subscription of alarms is supported. it allows for either subscription to all alarms or switch off the alarm subscription completely. alarm handling figure 9-16 the element manager alarm list the fault management service includes active alarm list administration, ala

33、rm log. the notification service handles subscriptions for alarms and sends notifications to all clients that have subscribed to the alarms. the actual alarm is created in the management adaptation layer where a fault indication is tagged with the following information: event type. the event type id

34、entifies an alarm type in the alarm record, en/lzt 123 6795 r2acopyright ericsson ab, 2003 - 305 9 operation and maintenance e.g. communication, environmental, equipment, processing error and quality of service. probable cause. each alarm will have a probable case value. it qualifies an alarm and pr

35、ovides further information than the event type defined above. severity level. there will be a perceived severity value for each alarm in the node. it indicates the relative urgency for operator attention, e.g. critical, major, minor and warning. specific problem additional text (optional) additional

36、 information (optional) the alarm handling within a network element relies on the itu x.733 alarm reporting function and supports the alarm irp specified by 3gpp (ts 32.111-2). these documents provide information about the content of the alarm reports and alarm transfer protocols that can be used. t

37、he alarm handling feature includes the following functions: active alarm list administration. the active alarm list contains a list of alarms, which are active in the system. the active alarm list is presented to the operator via a graphical user interface alarm log administration. the alarm log con

38、tains the history of alarms, which have been generated in the system. the alarm log is viewable for the operator. alarm subscription. the alarm subscription sub-function is responsible for the set-up and maintenance of alarm subscriptions in the system. an alarm is notified to a subscriber after the

39、 subscriber has made a subscription for that alarm. alarm manipulation the operator can acknowledge/un-acknowledge alarms and write a comment to a particular alarm. alarm distribution distribution of alarms to a sub-network manager or overall network management system. cpp supports corba as solution

40、-set for the alarm irp (ts 32.111-3). - 306 copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey logs there are different logs defined in the cpp system in which different information can be retrieved. the following logs exits: historical alarm log: one alarm log per network element. all alarm

41、status changes are logged in the alarm log. event log. one log per network element. all events, which are not alarms i.e. they dont have any state, are stored in this log. an example of an event is the restart event. all the logs are using the “round-robin” principle, i.e. when they are full the old

42、est information will be overwritten. it is possible to handle the logs as files and export them to any external media if they need to be stored for a long time for some reason. it is however not recommended, because they cannot be viewed outside the node without special tools. the logs on the networ

43、k element can be viewed from the element manager. en/lzt 123 6795 r2acopyright ericsson ab, 2003 - 307 9 operation and maintenance intentionally blank - 308 copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey intentionally blank en/lzt 123 6795 r2acopyright ericsson ab, 2003 - 309 10 questions

44、 10 questions - 310 copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey chapter 1 cpp introduction 1. why did ericsson start to develop cpp? 2. what is the idea behind the layered architecture in umts networks? 3. what is the role of the tag? 4. what is the difference of the role between cpp a

45、nd tsp? en/lzt 123 6795 r2acopyright ericsson ab. 2003 - 311 0 10 questions 5. which five system areas make up the cpp platform? chapter 2 cade 6. what is cade? chapter 3 cpp execution platform 7. what is the main processors (mp) used for? 8. where can the bps be found? - 312 copyright ericsson ab,

46、2003en/lzt 123 6795 r2a cpp survey 9. what is ipc used for? 10. what is the difference between reliable and non-reliable programs? 11. give three examples of applications that run on the core mps? 12. what is the purpose of the cluster interface (cli)? en/lzt 123 6795 r2acopyright ericsson ab. 2003

47、- 313 0 10 questions 13. what is the name server used for? 14. what is found in the local partitions of the file system? chapter 4 platform administration 15. what does the system manager respectively the board manager supervise? 16. how can the node protect itself from cyclic restarts? - 314 copyri

48、ght ericsson ab, 2003en/lzt 123 6795 r2a cpp survey 17. what parts in the node can be restarted? 18. when is the armament file used? 19. where is the trace trx-dig referers to the digital part of the trx, trx-tc to the control part and trx-ana to the analogue part of the trxb. fpgas perform the digi

49、tal signal processing on the trx board. it includes pulse shaping, interpolation filtering, digital modulation, gain compensation on tx and digital demodulation, decimation filtering, matched filtering and automatic gain control on rx. for the analog processing trxb performs channel filtering, ad/da

50、 conversion and rf modulation/demodulation. the board includes two transmitters and receivers, which operate on two independent duplex frequency pairs. functionality trxb rf demod. rf demod. channel filtering rf modu- lation channel filtering channel filtering a/d conversion a/d conversion figure 11

51、-35 rbs functionality in the trxb - 52 -copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey the following functions must be implemented on the trx board: downlink functions: digital filtering and digital i/q modulation d/a conversion up conversion and analog channel filtering tx output power c

52、ompensation over frequency and temperature output power supervision uplink functions: analog channel filtering and down conversion a/d conversion digital i/q demodulation and digital filtering automatic gain control rx gain accuracy control over frequency and temperature antenna near parts introduct

53、ion depending on the rbs configuration, the anp subsystem consists of 1-12 independent anp sub-blocks (anpb) and 1-6 antenna system controllers (asc) (optional). an asc contains a double dual duplex tma (3d tma) and communication/control support for the antenna system, e.g. the remote electrical ant

54、enna tilt (ret). each anpb consists of one aiu (csu&fcu), and one to two mcpas. one anpb serves 1-2 antennas in one cell. the rf subrack can hold 3 anpbs. for 3 and 4 carrier configurations two anpbs are needed for each sector. if an asc is used, these two anpbs then share one asc. the antenna inter

55、face unit comprises rf parts, such as rf filters, low noise amplifier and splitters. for some configurations the aiu combines rf signals from two mcpa to one antenna. the aiu also supplies power to the asc and ret. en/lzt 123 6795 r2acopyright ericsson ab, 2003- 53 - 11 appendix 1: current configura

56、tions of cpp nodes duplex filters allow both receiver and transmitter path connections to a common antenna. the duplex filter minimizes the number of required feeders and antennas. alarm and control communication with the asc and ret are handled by the mp via the aiu. the filters in aiu have high mt

57、bf and thereby no redundancy is needed for these functions. the anp provides power amplification of the tx signals and low noise amplification of the rx signals, between the trxs and antenna. configurations with or without asc/tma are supported. aiu rx trp tx fcu csu asc ret anpb anp rx/tx mcpa figu

58、re 11-36 functional overview of the anp - 54 -copyright ericsson ab, 2003en/lzt 123 6795 r2a cpp survey aiu functionality trxbaiub hp combin- ing pow er ampli- fier mcpa low noise amplifier low noise amplifier fre- quency combin- ing and splitting pow er split pow er split figure 11-37 rbs functiona

59、lity in the anp boards the anpb performs the following functions: transmitter part (tx, dl): carrier frequency combining rf dl amplification dl gain adjustment rf dl filtering output power measurement (rfpm) antenna supervision the anpb performs the following functions for the receiver part (rx, ul)

60、: rf ul filtering rf ul amplification 11 appendix 1: current configurations of cpp nodes en/lzt 123 6795 r2acopyright ericsson ab, 2003- 55 - received power splitting (rps) miscellaneous: lightning protection power external equipment over feeder communication to external equipment over feeder start-