EAC Design
Click here to load reader
Transcript of EAC Design
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 1/14
1 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
RFSW
Medusa UnitOM EAC Design
© Nokia Siemens Networks
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
No part of this publication may be copied, distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language without the prior written permission of Nokia Siemens Networks.
The manufacturer has made every effort to ensure that the instructions contained in the documents are adequateand free of errors and omissions. The manufacturer will, if necessary, explain issues, which may not be coveredby the documents. The manufacturer's liability for any errors in the documents is limited to the correction of errorsand the aforementioned advisory services.
The documents have been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using them. The manufacturer welcomes customer comments as part of the
process of continual development and improvement of the documentation in the best way possible from the user'sviewpoint. Please submit your comments to the nearest Nokia Siemens Networks sales representative.
Nokia Siemens Networks and the wave logo are registered trademarks of Nokia Siemens Networks. Other company and product names mentioned herein may be trademarks or trade names of their respective owners.
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 2/14
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 3/14
3 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
13 References................................................................................................13
14 Appendix....................................................................................................14
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 4/14
4 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
1 Introduction
1.1 Purpose of the Document
This document defines functionality and design of SW component.
1.2 Location
Document Name:
Link: <link to Design Document in Sharenet>
Document Code: <unasigned>
1.3 Component Overview
External Alarm Connector (EAC) component is responsible for handling external alarms.
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 5/14
5 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
2 Revision History
Version Date Author Changes
0.1 2011-01-28 Jakub Michalski Initial ver.
3 Open Items and Known Issues
Name Description
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 6/14
6 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
4 Concepts
4.1 Abbreviations
https://sharenet-ims.inside.nokiasiemensnetworks.com/properties/396829964
Abbreviation Description
UOAM Unit Operation and Maintenance
PS Platform Services
HW Hardware
SW Software
FM Fault Management
EAC External Alarm Connector
4.2 Terms
Term Description
Alarm LTX sends indications of alarms thus alarms are received from the LTX
Fault Fault is internal to the LTX. Faults are typically mapped to an alarm and there areless alarm types than fault types. VDs typically send information about faults to theUnit O&M.
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 7/14
7 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
5 Requirements and Constrains
5.1 Scope and Compatibility
EAC component is compatible with any HW which provides required PS interfaces and UPF.
5.2 Functional Requirements
EAC component should be able to exchange data with eacVD to handle external alarms andchange output line state.
5.3 Non Functional Requirements
EAC component number of external inputs and outputs should be configurable in UPF.
5.4 Constraints
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 8/14
8 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
6 Use Cases
6.1 <Use Case 1>
Purpose
Preconditions
Trigger
Scenario
Postconditions
Exceptions
Notes
6.2 <Use Case 2>Purpose
Preconditions
Trigger
Scenario
Postconditions
Exceptions
Notes
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 9/14
9 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
7 Architecture
7.1 Decomposition View
Component Type Responsibility
EacManager Active object Entry point of EAC. Communicates with eacVD to check and/or modify actual external input/output line state.
7.2 Dependency View
Component Other Components Dependency Description
EacManager eacVD Requests eacVD to retrieve/modify actual eacVD state.
EacManager Object Manager Uses object manager to handle and manage MasterAgents (SMs)subscriptions to EacManager.
7.3 Execution View
Component Execution Context DescriptionEacManager Runs in “Rp1” task
7.4 Behavioral View
Behavioral model is described by Use Cases.
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 10/14
10 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
8 External Interfaces
8.1 EacManager::initialize( Middleware::ActivationUnit * au,
Uoam::Startup::OAM * oam )Preconditions
Parameters • au – pointer to activation unit in which context startup will be executed
• oam – pointer to instance of OAM class
Description Initializes EacManager.
Postconditions
Exceptions
Notes
9 Variability
9.1 Configuration Parameters
This section describes component variability.
Parameter Name Data Type Value /Range
Description
UPF::HW::(moduleCommon/module)::eac::
numberOfExternalInputs
Section for number of external inputs definition.
UPF::HW::(moduleCommon/module)::eac:: numberOfExternalOutputs
Section for number of external outputs definition.
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 11/14
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 12/14
12 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
12 Testing
12.1 Normal Eac Management initialization
Preconditions Proper UPF and runtime SW are loaded on the RFM/RRH.
Scenario 1. Run RFM/RRH.
2. Wait until RFM/RRH sends moduleReadyIndication message
3. Open startup log and search for “INF/LTX/ UOM_Eac”
Postconditions
Expected Results Startup log should contain “INF/LTX/UOM_Eac” entry.
Notes
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 13/14
13 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
13 References
ID Description
Copyright © 2007 Nokia Siemens Networks. All rights reserved.
7/27/2019 EAC Design
http://slidepdf.com/reader/full/eac-design 14/14
14 (14) <unasigned> RFSW0.1 Medusa UnitOM EAC Design1/31/2011Owner: Jakub Michalski For internal use only
14 Appendix
Copyright © 2007 Nokia Siemens Networks All rights reserved