1 analysis of ngmn requirements req 2: automatic software management

7
1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Upload: audra-lawson

Post on 25-Dec-2015

213 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

1

Analysis of NGMN Requirements

REQ 2: Automatic Software Management

Page 2: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Slide title :32-35pt Color: R153 G0 B0

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

Slide text :20-22ptBullets level 2-5:

18pt Color:Black

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

2

Specifications

Related 3GPP SA5 specifications• Software management Integration Reference Point (IRP)

TS 32. 531/32.532/32.533/32.535

Current Status of the specifications• The software management specifications include automatic

software management and non-automatic software management functionalities.

• Automatic software management was completed in Rel-8.• Non-automatic software management was completed in Rel-9.

Page 3: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Slide title :32-35pt Color: R153 G0 B0

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

Slide text :20-22ptBullets level 2-5:

18pt Color:Black

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

3

Automatic Software Management

SA5 Software Management operations (from TS 32.532)

SwMOperations_2

changeSwMProfile()

<<Interface>>

SwMNotifications_4

notifyInstal lNESwStatusChanged()

<<Notification>>SwMOperations_4

installNESw()

<<Interface>>

SwMNotifications_2

notifySwMProfileChange()

<<Notification>>

SwMOperations_1

createSwMProfile()deleteSwMProfi le()listSwMCapabili ties()listSwMProcesses()listSwMProfiles()resumeSwMProcess()terminateSwMProcess()

<<Interface>>SwMNotifications_1

notifyNewSwMCapabil itiesAvai labili ty()notifySwMProcessCreation()notifySwMProcessDeletion()notifySwMProcessStage()notifySwMProfileCreation()notifySwMProfileDeletion()

<<Notification>>

SwMOperations_3

downloadNESw()activateNESw()

<<Interface>>

SwMNotifications_3

notifyDownloadNESwStatusChanged()notifyActivateNESwStatusChanged()

<<Notification>>

NotificationIRP(from TS 32.302)

<<InformationObjectClass>>

SwManagementIRP<<SupportIOC>><<may real ize>>

<<real ize>> <<use>>

<<real ize>>

<<may real ize>>

<<may use>>

<<may use>>

<<use>>

<<agent-internal-usage>>

Page 4: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Slide title :32-35pt Color: R153 G0 B0

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

Slide text :20-22ptBullets level 2-5:

18pt Color:Black

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

4

Automatic Software ManagementShort Term Requirements

Requirements Existing 3GPP Standards Status

“NE health-check”

OSS system has to be able to verify automatically that network elements are ready for software upgrade. The health-check (e.g. faulty HW Modules, critical alarms, free disk space) has to be executed during the dayshift to ensure the correct behavior and preconditions of the NE itself.

This is not explicitly mentioned in TS 32.53x, but could be easily introduced. Possible solutions could be an additional step/stop point and an extension / addition of a notification

Automated software download

The software download to the NEs should work in parallel with a minimum of unavoidable manual steps. A result overview list must be provided.

Supported by TS 32.53x Software Management IRP.

1. The profile configuration allows multiple network elements to download the software in parallel. For the network elements which meet the profile condition, they will initiate the software change accordingly.

2. The availability of new software in NE can be monitored by (5.5.6 Notification notifyNewSwAvailability (M)) (TS 32.532).

3. Manual operations (downLoadNESw, installNESw, ActivateNESw are also supported (TS 32.532).

Page 5: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Slide title :32-35pt Color: R153 G0 B0

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

Slide text :20-22ptBullets level 2-5:

18pt Color:Black

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

5

Automatic Software ManagementShort Term Requirements

Requirements Existing 3GPP Standards Status

One-click NE software activation

Software activation should also work in parallel with a minimum of unavoidable manual steps. The NE health-check should support also the wrap-up activities for urgent issues.

Supported by TS 32.53x Software Management IRP.

1. The profile configuration allows multiple network elements to activate the software in parallel automatically.

2. The resumeSwMProcess operation can work for one-click NE software activation when a stop point has been configured in the profile.

3. Manual operations (downLoadNESw,installNESw,ActivateNESw can be used for urgent issues on individual NE (TS 32.532).

Automatic rollback

Only if the software activations fail completely an automatic rollback should be initiated.

1. No automatic rollback supported.

2. Manual operation (swFallback) has been designed for individual NE (TS 32.532).

Page 6: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Slide title :32-35pt Color: R153 G0 B0

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

Slide text :20-22ptBullets level 2-5:

18pt Color:Black

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

6

Automatic Software ManagementLong Term Requirements

Requirements Existing 3GPP Standards Status

SW package is made available on OSS, and NEs are tagged on OMC for upgrade. Policies for software activation are set.

Supported by TS 32.53x Software Management IRP.

1. The profile configuration allows operators configured software management policies.

All necessary activities (NE-health check, SW download, SW activation, corrective actions) are carried out policy controlled by the software management application.

Supported by TS 32.53x Software Management IRP.

1. The profile configuration allows operators configured software management policies.

A final upgrade report is provided that will be used as basis for the final wrap up phase.

Supported by TS 32.53x Software Management IRP.

1. The availability of new software in NE can be monitored by (5.5.6 Notification notifyNewSwAvailability (M)) (TS 32.532).

Page 7: 1 Analysis of NGMN Requirements REQ 2: Automatic Software Management

Slide title :32-35pt Color: R153 G0 B0

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

Slide text :20-22ptBullets level 2-5:

18pt Color:Black

Corporate Font :FrutigerNext LT Medium

Font to be used by customers and

partners : Arial

7

Automatic Software ManagementLong Term Requirements

Requirements Existing 3GPP Standards Status

It is understood that with the long term approach the operator looses detailed control of each single step necessary for a software upgrade. A policy controlled bulk software upgrade is expected to be less error prone than today’s solutions

The policy management has been defined in TS 32.53x.