TS 32583 HNB的操作过程规范Word文件下载.docx
《TS 32583 HNB的操作过程规范Word文件下载.docx》由会员分享,可在线阅读,更多相关《TS 32583 HNB的操作过程规范Word文件下载.docx(22页珍藏版)》请在冰豆网上搜索。
3GPP
Postaladdress
3GPPsupportofficeaddress
650RoutedesLucioles-SophiaAntipolis
Valbonne-FRANCE
Tel.:
+33492944200Fax:
+33493654716
Internet
http:
//www.3gpp.org
CopyrightNotification
Nopartmaybereproducedexceptasauthorizedbywrittenpermission.
Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.
©
2009,3GPPOrganizationalPartners(ARIB,ATIS,CCSA,ETSI,TTA,TTC).
Allrightsreserved.
UMTS™isaTradeMarkofETSIregisteredforthebenefitofitsmembers
3GPP™isaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners
LTE™isaTradeMarkofETSIcurrentlybeingregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners
GSM®
andtheGSMlogoareregisteredandownedbytheGSMAssociation
Contents
Foreword5
Introduction5
1Scope6
2References6
3Definitionsandabbreviations6
3.1Definitions6
3.2Abbreviations6
4ArchitectureforHNBManagement7
4.2FunctionalElements8
4.2.1HNBManagementSystem(HMS)8
4.2.1.1InitialHNBManagementSystem(HMS)8
4.2.1.2ServingHNBManagementSystem(HMS)8
4.2.2SecurityGateway(SeGW)9
4.2.2.1InitialSecurityGateway(SeGW)9
4.2.2.2ServingSecurityGateway(SeGW)9
4.2.3HNBGateway(HNB-GW)9
5ProcedureFlows9
5.1Discoveryprocedures(Mandatory)9
5.1.1DiscoveryproceduresviaHMS(initial)accessibleontheMNOIntranet(Mandatory)9
5.1.2DiscoveryproceduresviaHMS(initial)accessibleonthepublicInternet(Mandatory)11
5.2HNBRegistration(Mandatory)12
5.2.1HNBregistrationProcedure(Mandatory)12
5.2.2HNBIPSecIPaddresschangeprocedure(Mandatory)13
5.3HNBConfigurationManagement(Mandatory)14
5.3.1HNBconfigurationmanagementbymeansoffiledownload(Optional)15
5.3.2HNBconfigurationmanagementusingRPCSetParameterValuemethod(Mandatory)16
5.4HNBDe-Provisioning(Mandatory)16
5.5AlarmReporting(Mandatory)18
5.5.1AlarmReportingMechanismConfiguration(Mandatory)18
5.5.2AlarmReportingProcedure(byRPCmethod)(Mandatory)18
5.6PMFileUpload(Mandatory)19
5.6.1PMFileUploadPeriodSetProcedure(Mandatory)19
5.6.2PMFileUploadingProcedure(Mandatory)20
AnnexA(informative):
Changehistory21
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)
Concepts
andrequirementsforType1interfaceHNBtoHNBManagementSystem(HMS)"
.
3GPPTS32.582:
InformationmodelforType1interfaceHNBtoHNBManagementSystem(HMS)"
3GPPTS32.583:
Procedure
flowsforType1interfaceHNBtoHNBManagementSystem(HMS)"
.
3GPPTS32.584:
XML
definitionsforType1interfaceHNBtoHNBManagementSystem(HMS)"
1Scope
ThepresentdocumentdescribestheprocedureflowsbetweenHNB&
HMSfortheOAMofHNBManagement.
2References
Thefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.
∙Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornonspecific.
∙Foraspecificreference,subsequentrevisionsdonotapply.
∙Foranon-specificreference,thelatestversionapplies.Inthecaseofareferencetoa3GPPdocument(includingaGSMdocument),anon-specificreferenceimplicitlyreferstothelatestversionofthatdocumentinthesameReleaseasthepresentdocument.
[1]3GPPTR21.905:
Vocabularyfor3GPPSpecifications"
[2]3GPPTS32.101:
Principlesandhighlevelrequirements"
[3]3GPPTS32.102:
Architecture"
[4]3GPPTS32.300:
ConfigurationManagement(CM);
NameconventionforManagedObjects"
[5]TR-069Amendment2,CPEWANManagementProtocolv1.1,BroadbandForum,viewableat
[6]3GPPTR25.8203GHomeNodeBStudyItemTechnicalReport
[7]3GPPTS25.401RadioAccessNetworkUTRANOverallDescription
[8]3GPPTR32.821:
StudyofSelf-OrganizingNetwork(SON)relatedOAMforHomeNodeB"
[9]3GPPTS25.467:
UTRANarchitecturefor3GHomeNodeB,stage2"
[10]3GPPTS32.582:
HomeNodeB(HNB)Operations,Administration,MaintenanceandProvisioning(OAM&
InformationmodelforType1interfaceHNBtoHNBManagementSystem(HMS)"
3Definitionsandabbreviations
Forthepurposesofthepresentdocument,thetermsanddefinitionsgiveninTS32.101[2],TS32.102[3]andTS
21.905
[1]andthefollowingapply.Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,inTS32.101[2],TS32.102[3]andTS
[1],inthatorder.
3.1Definitions
Forthepurposesofthepresentdocument,thetermsanddefinitionsgiveninTR
[1]andthefollowingapply.Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,inTR
[1].
3.2Abbreviations
Forthepurposesofthepresentdocument,thefollowingabbreviationsapply:
DNSDomainNameServer
FTPFileTransferProtocol
HMSHomeNodeBManagementSystem
HNBHomeNodeB
HNB-GWHomeNodeBGateway
HTTPHyperTextTransferProtocol
HTTPSHyperTextTransferProtocolSecure
IPInternetProtocol
LANLocalAreaNetwork
MNOMobileNetworkOperator
RNCRadioNetworkController
RPCRemoteProcedureCall
SeGWSecurityGateway
SSLSecureSocketLayer
sFTPSecureFileTransferProtocol
TLSTransportLayerSecurity
URLUnifiedResourceLocator
4ArchitectureforHNBManagement
4.1HNBOAMfunctionalarchitecture
ThissectionprovidestheHNBOAMfunctionalarchitecture.Wedistinguishthetwofollowingcases:
∙AHNBisconnectedtoaBBdevice(typicallyaresidentialgatewayprovidingconnectivityviaanaccessproviderdomain).TheBBdeviceprovidesrouting,NATandfirewallfunctionality.
∙ABBdevicewithanintegratedHNBfunctionality
TheHNBManagementSystem(HMS)maintasksaretoprovisionconfigurationdataontheHNB.Itprovidesthefollowingfunctionalentities:
∙Afileserver
∙ATR-069auto-configurationserver(ACS)
HoweverthefileservermaybeusedbyotherapplicationsintheMNOdomain.
Figure4.1.1-1:
ArchitectureforHNBManagement
4.2FunctionalElements
4.2.1HNBManagementSystem(HMS)
TheHMSiscomposedofaTR-069managerandafileserver.TheTR069managerimplementstheAuto-ConfigurationServerfunctionasdefinedinTR-069standardandperformsCM,FMandPMfunctionalitiestotheHNB.Thefileservermaybeusedforfileuploadordownload,asinstructedbyTR-069manager
4.2.1.1InitialHNBManagementSystem(HMS)
TheinitialHMSmayprovidelocationverificationofHNBandassignsappropriateservingelements(ServingHMS,SecurityGatewayandHNB-GW).
4.2.1.2ServingHNBManagementSystem(HMS)
Providesthefollowingfunctionalities:
∙TR-069Auto-configurationserver
∙Fileserverforfileuploadordownload
∙ProvisioningofconfigurationdatatotheHNB
∙Performance&
Faultupdates
∙ProvidesServingSeGWdiscovery
4.2.2SecurityGateway(SeGW)
SeGWterminatesSecuretunnellingforTR-069aswellasIuh.ItisusedforauthenticationofHNB&
providesaccesstoHMSandHNB-GW.
4.2.2.1InitialSecurityGateway(SeGW)
TheURLoftheInitialSeGWmaybefactoryprogrammedintheHNBsoastoallowinitialestablishmentofanIPSecsecurityassociationand