32581a00.docx

32581a00.docx

《32581a00.docx》由会员分享，可在线阅读，更多相关《32581a00.docx（13页珍藏版）》请在冰豆网上搜索。

32581a00

3GPPTS32.581V10.0.0（2010-06）

TechnicalSpecification

3rdGenerationPartnershipProject;

TechnicalSpecificationGroupServicesandSystemAspects;

Telecommunicationmanagement;

HomeNodeB（HNB）

Operations,Administration,MaintenanceandProvisioning

（OAM&P）;

ConceptsandRequirementsforType1interfaceHNBtoHNBManagementSystem（HMS）

（Release10）

Thepresentdocumenthasbeendevelopedwithinthe3rdGenerationPartnershipProject（3GPPTM）andmaybefurtherelaboratedforthepurposesof3GPP.

Thepresentdocumenthasnotbeensubjecttoanyapprovalprocessbythe3GPPOrganizationalPartnersandshallnotbeimplemented.

ThisSpecificationisprovidedforfuturedevelopmentworkwithin3GPPonly.TheOrganizationalPartnersacceptnoliabilityforanyuseofthisSpecification.

Specificationsandreportsforimplementationofthe3GPPTMsystemshouldbeobtainedviathe3GPPOrganizationalPartners'PublicationsOffices.

Keywords

HomeNodeB,management

3GPP

Postaladdress

3GPPsupportofficeaddress

650RoutedesLucioles-SophiaAntipolis

Valbonne-FRANCE

Tel.:

+33492944200Fax:

+33493654716

Internet

http:

//www.3gpp.org

CopyrightNotification

Nopartmaybereproducedexceptasauthorizedbywrittenpermission.

Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.

©2010,3GPPOrganizationalPartners（ARIB,ATIS,CCSA,ETSI,TTA,TTC）.

Allrightsreserved.

UMTS™isaTradeMarkofETSIregisteredforthebenefitofitsmembers

3GPP™isaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners

LTE™isaTradeMarkofETSIcurrentlybeingregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners

GSM®andtheGSMlogoareregisteredandownedbytheGSMAssociation

Contents

Foreword4

Introduction4

1Scope5

2References5

3Definitionsandabbreviations5

3.1Definitions5

3.2Abbreviations6

4Conceptsandbackground6

5Businesslevelrequirements6

5.1Requirements6

5.1.1ConfigurationManagement6

5.1.2PerformanceManagement7

5.1.3FaultManagement7

5.1.4SecurityManagement7

5.2Actorroles7

5.3Telecommunicationsresources7

5.4Highlevelusecases7

6Specificationlevelrequirements7

6.1Requirements7

6.1.1ConfigurationManagement7

6.1.2PerformanceManagement8

6.1.3FaultManagement9

6.1.4SecurityManagement10

6.2Actorroles10

6.3Telecommunicationsresources10

6.4Usecases10

AnnexA（informative）:

Changehistory11

Foreword

ThisTechnicalSpecificationhasbeenproducedbythe3rdGenerationPartnershipProject（3GPP）.

ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithintheTSGandmaychangefollowingformalTSGapproval.ShouldtheTSGmodifythecontentsofthepresentdocument,itwillbere-releasedbytheTSGwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:

Versionx.y.z

where:

xthefirstdigit:

1presentedtoTSGforinformation;

2presentedtoTSGforapproval;

3orgreaterindicatesTSGapproveddocumentunderchangecontrol.

ytheseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.

zthethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthedocument.

Introduction

ThepresentdocumentispartofaTS-familycoveringthe3rdGenerationPartnershipProjectTechnicalSpecificationGroupServicesandSystemAspects,TelecommunicationManagement;asidentifiedbelow:

3GPPTS32.581:

"Telecommunicationsmanagement;HomeNodeB（HNB）Operations,Administration,MaintenanceandProvisioning（OAM&P）;ConceptsandrequirementsforType1interfaceHNBtoHNBManagementSystem（HMS）".

3GPPTS32.582:

"Telecommunicationsmanagement;HomeNodeB（HNB）Operations,Administration,MaintenanceandProvisioning（OAM&P）;InformationmodelforType1interfaceHNBtoHNBManagementSystem（HMS）".

3GPPTS32.583:

"Telecommunicationsmanagement;HomeNodeB（HNB）Operations,Administration,MaintenanceandProvisioning（OAM&P）;ProcedureflowsforType1interfaceHNBtoHNBManagementSystem（HMS）".

3GPPTS32.584:

"Telecommunicationsmanagement;HomeNodeB（HNB）Operations,Administration,MaintenanceandProvisioning（OAM&P）;XMLdefinitionsforType1interfaceHNBtoHNBManagementSystem（HMS）".

1Scope

ThepresentdocumentdescribestheconceptsandrequirementsofOAMforHomeNodeB（HNB）.TherequirementscapturedinthisdocumentshallbemetviaType1interfacebetweenHNBandHMS.

2References

Thefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.

∙Referencesareeitherspecific（identifiedbydateofpublication,editionnumber,versionnumber,etc.）ornonspecific.

∙Foraspecificreference,subsequentrevisionsdonotapply.

∙Foranon-specificreference,thelatestversionapplies.Inthecaseofareferencetoa3GPPdocument（includingaGSMdocument）,anon-specificreferenceimplicitlyreferstothelatestversionofthatdocumentinthesameReleaseasthepresentdocument.

[1]3GPPTR32.821:

"StudyofSelf-OrganizingNetwork（SON）relatedOAMforHomeNodeB".

[2]3GPPTS25.467:

"UTRANarchitecturefor3GHomeNodeB,stage2".

[3]TR-069Amendment2,CPEWANManagementProtocolv1.1,BroadbandForum

[4]TR-106Amendment2DataModeltemplateforTR-069-EnabledDevicesv1.1,BroadbandForum.

[5]TR-196FAPAccessPointServiceDataModelv1.00,BroadbandForum.

[6]3GPPTS32.435:

"PerformanceMeasurement,eXtensibleMarkupLanguage（XML）fileformatdefinition".

[7]3GPP TS 32.111-2:

"Telecommunicationmanagement;FaultManagement;AlarmIntegrationReferencePoint（IRP）:

InformationService（IS）".

[8]3GPPTS32.101:

"Telecommunicationmanagement;Principlesandhighlevelrequirements".

[9]3GPPTS32.102:

"Telecommunicationmanagement;Architecture".

[10]3GPPTR21.905:

"Vocabularyfor3GPPSpecifications".

[11]3GPPTS22.220:

"ServicerequirementsforHomeNodeB（HNB）andHomeeNodeB（HeNB）".

3Definitionsandabbreviations

Forthepurposesofthepresentdocument,thetermsanddefinitionsgiveninTS32.101[8],TS32.102[9]andTS 21.905 [10]andthefollowingapply.Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,inTS32.101[8],TS32.102[9]andTS 21.905 [10],inthatorder.

3.1Definitions

Forthepurposesofthepresentdocument,thetermsanddefinitionsgiveninTR 21.905 [10]andthefollowingapply.Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,inTR 21.905 [10].

3.2Abbreviations

Forthepurposesofthepresentdocument,thefollowingabbreviationsapply:

HMSHomeNodeBManagementSystem

HNBHomeNodeB

4Conceptsandbackground

HomeNodeBhasthefollowingcharacteristics:

ØThequantityofHomeNodeBsislikelytobelarge

ØTheremaybemanyHomeNodeBvendors

ØHomeNodeBmaybepurchasedeasilybyendusersinmarket

ØThelocationofHomeNodeBcouldbeinaprivateresidencewhichmaynotbeaccessibleforfrequenton-sitemaintenance

Basedontheabovecharacteristics,thisspecificationdefinesthefunctionalitiesneededforthemanagementofHomeNodeBoveraType1interface.

5Businesslevelrequirements

5.1Requirements

REQ-OAMP-CON-001TheHNBshallbeabletobemanagedinallmanagementdomainaspectsdefinedbelowasConfigurationmanagement,Securitymanagement,PerformancemanagementandFaultmanagement,withouttheuseofvendor-specificoroperator-specificextensioncapability.

5.1.1ConfigurationManagement

REQ-OAMP_CM-CON-001TheHNBshallbeabletoautomatically,i.e.withouthumanoperatoron-lineinteractionorattention,configureitselftobereadyforservicewhenpoweredupandconnectedtoHMS.

REQ-OAMP_CM-CON-002TheHNBshallbeabletoautomatically,i.e.withouthumanoperatoron-lineinteractionorattention,configureitselftobeinservicewhenpoweredupandconnectedtoHMS.

REQ-OAMP_CM-CON-003TheHNBshallbeabletoautomatically,i.e.withouthumanoperatoron-lineinteractionorattention,upgradeitssoftware/firmwareandconfiguration.

REQ-OAMP_CM-CON-004TheHNBauto-configurationshallbedoneinsuchwaythattheperformanceofthesurroundingmacrocellsisnotadverselyaffected.

REQ-OAMP_CM-CON-005TheHNBauto-configurationfunctionshouldbeadaptivetoreacttochangeinthenetworkandchangesintheradioenvironment.

REQ-OAMP_CM-CON-006TheoperatorshallbeabletoremotelyreboottheHNB.

REQ-OAMP_CM-CON-007Theoperatorshallbeabletoremotelystart/stoptheradiotransmissionoftheHNB.

REQ-OAMP_CM-CON-008IncaseIPsecisused,thesystemshouldbeengineeredtoensurethattheHNBIPaddresschangesasminimallyaspossible.

REQ-OAMP_CM-CON-009TheoperatorshallbeabletoremotelyreconfiguretheHNBtoadapttochangesintheradioenvironment.

5.1.2PerformanceManagement

REQ-OAMP_PM-CON-001TheHNBmayhavethecapabilitytocollectitsperformancerelateddata.

REQ-OAMP_PM-CON-002TheHNBshallsendperformancedatabasedonoperatorconfiguredpolicy.

REQ-OAMP_PM-CON-003OperatorshallbeabletoretrieveperformancedatafilefromtheHNB.

5.1.3FaultManagement

REQ-OAMP_FM-CON-001TheHNBshallsupportFaultManagementtoenabletheoperatortomonitorandmanagetheHNB.

REQ-OAMP_FM-CON-002TheHNBshallprovidealarmrelatedinformationonlyondemandbytheoperatororbasedonoperatorconfiguredpolicy.

5.1.4SecurityManagement

REQ-OAMP_SM-CON-001TheHNBshallhavethecapabilitytoprotectitselfagainstDenialofServiceattackovertheType1interface.

5.2Actorroles

Notdefinedinthisversion.

5.3Telecommunicationsr