8/19/2019 32593-a00

1/19

3GPP TS 32.593 V10.0.0 (2010-06)Technical Specification

3rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;Telecommunication management;

Home eNode B HeNB! "perations# Administration# $aintenanceand Provisioning "A$%P!;

Procedure &lo's for Type ( )nterface HeNB to HeNB $anagementSystem

*elease (+!

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.

The present document has not been subject to any approval process by the 3GPP  Orani!ational Partners and shall not be implemented.

This "pecification is provided for future development wor# within 3GPP   only. The Orani!ational Partners accept no liability for any use of this

"pecification."pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Orani!ational Partners$ Publications Offices.

8/19/2019 32593-a00

2/193GPP 

%eywordsHome NodeB, management

3GPP 

Postal address

3GPP support office address

650 Route de !u"#o$e - So%a 'nt#%o$#Va$onne - R'N*+

Te$. 33 92 9 2 00 a/ 33 93 65 16

&nternet

&tt%.3g%%.og

Copyright Notification

 'o part may be reproduced ecept as authori!ed by written permission.The copyriht and the foreoin restriction etend to reproduction in all media.

*+,+- 3GPP Orani!ational Partners (/&0- T&"- 11"- 2T"&- TT- TT1).

ll rihts reserved.

MT"4 is a Trade Mar# of 2T"& reistered for the benefit of its members

3GPP4 is a Trade Mar# of 2T"& reistered for the benefit of its Members and of the 3GPP Orani!ational Partners

5T24 is a Trade Mar# of 2T"& currently bein reistered for the benefit of its Members and of the 3GPPOrani!ational Partners

G"M6 and the G"M loo are reistered and owned by the G"M ssociation

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!,*elease (+

8/19/2019 32593-a00

3/19

*ontent

7oreword..........................................................................................................................................................

&ntroduction......................................................................................................................................................

, "cope......................................................................................................................................................

* /eferences..............................................................................................................................................

3 8efinitions and bbreviations................................................................................................................3., 8efinitions...........................................................................................................................................................

3.* bbreviations.......................................................................................................................................................

9 rchitecture for :e'0 Manaement......................................................................................................9., :e'0 OM 7unctional rchitecture..................................................................................................................9.,., Overview........................................................................................................................................................9.* 7unctional 2lements............................................................................................................................................

9.*., :e'0 Manaement "ystem (:eM").............................................................................................................9.*.,., &nitial :eM".............................................................................................................................................

9.*.,.* "ervin :eM"..........................................................................................................................................9.*.* :ome e'0.....................................................................................................................................................9.*.3 "ecurity Gateway ("eG;).............................................................................................................................9.*.3., &nitial "eG;.............................................................................................................................................9.*.3.* "ervin "eG;..........................................................................................................................................9.*.9 MM2

8/19/2019 32593-a00

4/19

oeod

This Technical "pecification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuin wor# within the T"G and may chane followin formalT"G approval. "hould the T"G modify the contents of the present document- it will be reAreleased by the T"G with anidentifyin chane of release date and an increase in version number as followsB

?ersion .y.!

whereB

the first diitB

, presented to T"G for informationC

* presented to T"G for approvalC

3 or reater indicates T"G approved document under chane control.

y the second diit is incremented for all chanes of substance- i.e. technical enhancements- corrections-updates- etc.

! the third diit is incremented when editorial only chanes have been incorporated in the document.

4ntodu"t#on

The present document is part of a T"Afamily coverin the 3rd Generation Partnership Project Technical "pecificationGroup "ervices and "ystem spects- Telecommunication ManaementC as identified belowB

3GPP T" 3*.=D,B ETelecommunications manaementC :ome e'ode 0 (:e'0)Operations- dministration- Maintenance and Provisionin (OMFP)C 1oncepts

and re@uirements for Type , interface :e'0 to :e'0 Manaement "ystemE.

3GPP T" 3*.=D*B ETelecommunications manaementC :ome e'ode 0 (:e'0)Operations- dministration- Maintenance and Provisionin (OMFP)C&nformation model for Type , interface :e'0 to :e'0 Manaement "ystemE.

3GPP TS 32.593: Te!e"omm#ni"ations management$ Home %o&e ' (He%')

erations* A&ministration* +aintenan"e an& Provisioning (A+,P)$ Pro"ere

f!o-s for Tye interfa"e He%' to He%' +anagement System .

3GPP T" 3*.=D9B ETelecommunications manaementC :ome e'ode 0 (:e'0)

Operations- dministration- Maintenance and Provisionin (OMFP)C M5

definitions for Type , interface :e'0 to :e'0 Manaement "ystemE.

3GPP 

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!*elease (+

8/19/2019 32593-a00

5/19

1 S"o%e

The present specification describes the procedure flows between networ# entities involved in :e'0 manaementArelated tas#s. These procedures are based on the re@uirements specified in H9I. &nformation model for manaementA

related information echaned in these procedures is specified in H=I and references therein. M5 file formats used toencapsulate the information echaned in these procedures are specified in HJI. The communication protocol used for:e'0 manaement is the T/A+JD protocol- specified in HKI.

Manaement interface affected by these procedures is the Type , interface between :e'0 and :eM". Procedures flowsover the Type * interface (between 2lement Manaement and 'etwor# Manaement layer) for the manaement of

:e'0 are outside of scope of this document

2 Reeen"e

The followin documents contain provisions which- throuh reference in this tet- constitute provisions of the presentdocument.

• /eferences are either specific (identified by date of publication- edition number- version number- etc.) or

nonAspecific.

• 7or a specific reference- subse@uent revisions do not apply.

• 7or a nonAspecific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin

a G"M document)- a nonAspecific reference implicitly refers to the latest version of that document in the same

 Release as the present document .

H,I 3GPP T/ *,.D+=B E?ocabulary for 3GPP "pecificationsE.

H*I 3GPP T" 3*.,+,B ETelecommunication manaementC Principles and hih level re@uirementsE.

H3I 3GPP T" 3*.,+*B ETelecommunication manaementC rchitectureE.

H9I 3GPP T" 3*.=D,B ETelecommunications manaementC :ome e'ode 0 (:e'0)Operations- dministration- Maintenance and Provisionin (OMFP)C1oncepts and /e@uirements for Type , interface :e'0 to :e'0 Manaement "ystemE.

H=I 3GPP T" 3*.=D*B ETelecommunications manaementC :ome e'ode 0 (:e'0)Operations- dministration- Maintenance and Provisionin (OMFP)C&nformation model for Type , interface :e'0 to :e'0 Manaement "ystemE

HJI 3GPP T" 3*.=D9B ETelecommunications manaementC :ome e'ode 0 (:e'0)Operations- dministration- Maintenance and Provisionin (OMFP)C M5definitions for Type , interface :e'0 to :e'0 Manaement "ystemE

HKI T/A+JD mendment *- 1P2 ;' Manaement Protocol v,.,- 0roadband 7orum- viewable athttpB

8/19/2019 32593-a00

6/19

3.1 e#n#t#on

7or the purposes of the present document- the terms and definitions iven in T/ *,.D+= H,I and the followin apply. term defined in the present document ta#es precedence over the definition of the same term- if any- in T/ *,.D+= H,I.

3.2 'e7#at#on7or the purposes of the present document- the followin abbreviations applyB

1M 1onfiuration Manaement8'" 8omain 'ame "erver  2P1 2volved Pac#et 1ore7M 7ault Manaement7N8' 7ully Nualified 8omain 'ame7TP 7ile Transfer Protocol

:M" :ome 'ode0 Manaement "ystem:eM" :ome e'ode0 Manaement "ystem:'0 :ome 'ode0

:e'0 :ome e'ode0:e'0AG; :e'0 Gateway:TTP :yper Tet Transfer Protocol

:TTP" :yper Tet Transfer Protocol "ecure&P &nternet Protocol5' 5ocal rea 'etwor#  MM2 Mobility Manaement 2ntityM'O Mobile 'etwor# Operator  OM Operation- dministration- Maintenance

PM Performance Manaement/P1 /emote Procedure 1all"eG; "ecurity Gateway""5 "ecure "oc#et 5ayer  

"7TP "ecure 7ile Transfer ProtocolT5" Transport 5ayer "ecurity

'"te"tue o HeNB 8anagement

.1 HeNB '8 un"t#ona$ '"te"tue

.1.1 7e7#e

This section describes the functional architecture for :e'0 manaement over Type , manaement interface and entities

involved.

The architecture is shown in 7iure 9 A, 7unctionalities of each entity are described in subse@uent subclauses. 'onAOM entities- such as "eG; and MM2 are also shown as they fiure in the procedure flows specified in thisdocument.

3GPP 

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!2*elease (+

8/19/2019 32593-a00

7/19

&igure 1(4 HeNB $anagement Architecture

.2 un"t#ona$ +$ement

.2.1 HeNB 8anagement S:tem (He8S)

The :eM" supports the procedures forB

  1onfiuration Manaement (1M)- 7ault manaement (7M) and Performance Manaement (PM) of :e'0

  &dentity and location verification of :e'0

  8iscovery and assinment of "ervin :eM"- "ervin "eG;- and MM2

  7ile upload

8/19/2019 32593-a00

8/19

Typically- "ervin :eM" is located inside the operator>s secure networ# domain and the address of the "ervin :eM"is provided to the :e'0 via &nitial :eM".

.2.2 Home eNB

The :e'0 is the manaed device.

The :e'0 loically comprises a T/A+JD ent and an file client.

T/A+JD ent corresponds to the T/A+JD 1ustomer Premise 2@uipment (1P2) function as defined in T/A+JDspecification HKI.

The file client may be used for file upload or download related to :eM" manaement- such as upload of performancemeasurement files or alarm los- as confiured by T/A+JD Manaer via T/A+JD ent. The file client may also be usedfor other purposes not related to :e'0 manaement.

:e'0 is associated with a 0roadband (00) device. This is typically a residential ateway providin transport layerconnectivity via an access provider domain. The 00 device provides routin- 'T and firewall functionality. s shown

in 7iure 9 A,- :e'0 can be connected to an eternal 00 device or a 00 device can be interated with the :e'0.

.2.3 Se"u#t: Gatea: (SeG;)

"eG; provides authentication of :e'0 secure tunnellin of communication between :e'0 and :eM" and between:e'0 and MM2.

.2.3.1 4n#t#a$ SeG;

&nitial "eG; terminates &P"ec and provides secure tunnellin of communication between :e'0 and &nitial :eM". The7N8' of the &nitial "eG; may be factory prorammed in the :e'0. &nitial "eG; can be the same as the "ervin"eG;.

.2.3.2 Se7#ng SeG;"ervin "eG; provides &P"ec association and secure communication between :e'0 and networ# elements such asMM2 and "ervin :eM" in the operator>s networ#. "ervin "eG; implements a forwardin function to allowforwardin of &P pac#ets upstream and downstreamB

  8ownstreamB pac#ets are forwarded on appropriate &P"ec tunnels towards the :e'0 based on their destination

&P addressesC

  pstreamB forwardin &P traffic to the "ervin :eM"- MM2 or other networ# elements based on destination &Paddresses.

The 7N8' of the "ervin "eG; may be provided to the :e'0 by &nitial :eM".

"ervin "eG; could be the same as the &nitial "eG;.

.2. 88+HeNB G;

MM2 terminates ", interface from :e'0. Optionally- ", interface termination can be provided by :e'0 Gateway.This is not relevant from the :e'0 point of view- since :e'0 cannot differentiate between connectin to MM2 and:e'0G;. 7rom :e'0 point of view- farAend ", interface termination point appears as MM2.

3GPP 

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!6*elease (+

8/19/2019 32593-a00

9/19

5 Po"edue $o

5.1 #"o7e: and Reg#tat#on Po"edue5.1.1 7e7#e

;hen :e'0 is powered up- it needs to establish connectivity with the "ervin :eM" for manaement purposes andwith the MM2 for 2P1 connectivity purposes. The transport layer protocol for both of these connections is &P. &Pconnectivity with "ervin :eM" is established usin "ervin :eM" discovery procedures. sin these procedures- the

:e'0 is able toB

  c@uire &P address of the :eM"

  2stablish secure &P connection with the :eM"

The &P address(es) of the ", interface is provided to the :e'0 in one of the followin waysB

  0y the &nitial :eM" durin "ervin :eM" discovery procedure

  0y the "ervin :eM" durin the reistration procedure of the :e'0 with the :eM".

Once the :e'0 has established the &P connectivity with the "ervin :eM"- the :e'0 must reister with the "ervin

:eM". This is accomplished usin the :e'0 reistration with "ervin :eM" procedure- described in "ection =.,.3. 

The reistration of the :e'0 with MM2 (", "etup procedure) is specified in HLI.

7iure = A* illustrates discovery and reistration procedures eecuted by the :e'0 upon power up.

&igure .1, 7iscovery and registration procedures

5.1.2 Se7#ng He8S d#"o7e: %o"edue

5.1.2.1 7e7#e

Operators may deploy their manaement infrastructure in different ways. "pecifically- &nitial :eM" may be accessiblewithin the operator>s secure public networ# domain or on the public internet. The followin "ervin :eM" discovery

 procedures are defined to accommodate these deployment scenariosB

  "ervin :eM" discovery via &nitial :eM" accessible inside operator>s private secure networ# domain ("ection=.,.*.*)

  "ervin :eM" discovery via &nitial :eM" accessible on the public internet ("ection =.,.*.3)

3GPP 

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!/*elease (+

8/19/2019 32593-a00

10/19

5.1.2.2 Se7#ng He8S #"o7e: 7#a 4n#t#a$ He8S a""e#$e #n#de o%eatos private secure

networ# domain- 7or such deployments the support for this procedure by :e'0 is mandatory. Otherwise- the supportfor this procedure is not mandatory.

&n this case the :e'0 is factory prorammed withB

  7N8' or &P address of the &nitial :eM"

  7N8' or &P address of the &nitial "eG;

The procedure for "ervin :eM" discovery via &nitial :eM" accessible inside operator>s private secure networ#domain is described net and illustrated in 7iure = A3.

s a preAcondition- the :e'0 establishes &P connectivity to the &nternet when it is initially powered up.

,. "teps ,.,A*.= allow :e'0 to establish a secure connection with the &ntial :eM".

,., The :e'0 initiates a process to et &P address of the &nitial "eG;. &f the :e'0 already has the &Paddress then o to step ,.3. &f the :e'0 has the 7N8'- the :e'0 performs 8'" @uery to a public8'" for the &P address correspondin to the 7N8' of the &nitial "eG;.

,.*.8'" responds to the :e'0 with the &P address of the &nitial "eG;.

,.3 secure connection via &P"ec tunnel is established between the :e'0 and &nitial "eG;.

,.9 The :e'0 initiates a process to et &P address of the &nitial :eM". &f the :e'0 already has the &Paddress then s#ip step ,.9 and step ,.=. &f the :e'0 has the 7N8'- the :e'0 performs 8'" @uery toa private 8'" for the &P address correspondin to the 7N8' of the &nitial :eM".

,.= Private 8'" responds to the :e'0 with the &P address of the &nitial :eM".

secure connection via &P"ec tunnel is now established between the :e'0 and the &nitial :eM".

*. "teps *.,A*.* allow the :e'0 to establish a T/A+JD session with &nitial :eM"- as specified in HKI.

*., The :e'0 sends to &nitial :eM" an &nform re@uest containin 8evice &8 of the :e'0 and optionallylocation information and

8/19/2019 32593-a00

11/19

J.= Private 8'" responds to the :e'0 with the &P address of the "ervin :eM".

secure connection via &P"ec tunnel is established between the :e'0 and the "ervin :eM".

&igure .134 Serving He$S 7iscovery via )nitial He$S accessi8le inside operator9s private securenet'or: domain

 'et- the :e'0 performs reistration with the "ervin :eM" procedure ("ection =.,.3).

5.1.2.3 Se7#ng He8S d#"o7e: 7#a 4n#t#a$ He8S a""e#$e on t&e %u$#" #ntenet(*ond#t#ona$ 8andato:)

This procedure applies for deployments where &nitial :eM" is accessible on the public internet. &n this case the :e'0is factory prorammed with &nitial :eM"> 7N8'- which the operator needs to publish in a public 8'". 7or suchdeployments- the support for this procedure by :e'0 is mandatory. Otherwise- the support for this procedure is not

mandatory.

The procedure for "ervin :eM" discovery via &nitial :eM" accessible on the public internet is described net andillustrated in 7iure = A9.

3GPP 

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!((*elease (+

8/19/2019 32593-a00

12/19

 &igure .1 Serving He$S 7iscovery via )nitial He$S accessi8le on the pu8lic internet

s a preAcondition- the :e'0 establishes &P connectivity to the &nternet when it is initially powered up.

,. &n steps ,.,A,.3 :e'0 establish &P connectivity with the &ntial :eM" usin ""5

8/19/2019 32593-a00

13/19

3. The :e'0 may release the T/A+JD "ession between the :e'0 and "ervin :eM"- accordin to the criteriaspecified in HKI.

9. The :e'0 initiates the ", "etup procedure (reistration with MM2) specified in HLI.

&igure .1.4 Procedure for HeNB registration 'ith Serving He$S

5.2 *on#guat#on 8anagement Po"edue (8andato:)

5.2.1 7e7#e

This section specifies the procedure flows for :e'0 confiuration manaement usin T/A+JD protocol specified in HKI.These procedure flows stem from the 1M re@uirements in H9I- which mandate that 1M can be achieved either by meansof T/A+JD /P1 methods as a mandatory feature or by means of file download as an optional feature.

The procedure for notification of the &P"ec &P address chane by the :e'0 is also specified.

5.2.2 HeNB "on#guat#on u#ng #$e don$oad %o"edue (%t#ona$)

7ollowin a reistration of the :e'0 with the "ervin :eM"- the T/A+JD Manaer in the "ervin :eM" may trierthe :e'0 to start a file download of confiuration 1M data. "ubse@uent to this initial phase- the T/A+JD Manaer maytrier this procedure at any time.

Procedure for :e'0 confiuration usin file download is shown in 7iure = AJ and described net.

3GPP 

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!(3*elease (+

8/19/2019 32593-a00

14/19

 

&igure .12 HeNB configuration using file do'nload procedure

s a preAcondition- the :e'0 must be reistered with the :eM".

,. The T/A+JD session is established asdescribed in HKI.

*. :eM" invo#es /P1 method 8ownload- specified in HKI- to cause the :e'0 to download a specified file from the

desinated location- which may be the file server in the :eM" as shown in 7iure = AJ. The aruments of the8ownload /P1 method are described in HKI and includeB

  7ile type-

  /5 specifyin the source file location

  ser name for the connection to the file server 

  Password associated to the user name

  7ile si!e

Types and values of the aruments of the 8ownload method are described in HKI.

3. The :e'0 initiates the file download usin transport protocol inferred from the /5 arument of the8ownload method.

9. The file server performs the file download. The file format is specified in HJI.

=. The :e'0 provides file download completion indication (success

8/19/2019 32593-a00

15/19

&igure .15 HeNB configuration procedure using *P SetParameter0alues method

s a preAcondition- the :e'0 must be reistered with the :eM".

,. The T/A+JD session is established asdescribed in HKI.

*. The :eM" invo#es "etParameter?alues /P1 method- specified in HKI- to confiure the parameters in the :e'0.The aruments include the list of parameters to be confiured and their values.

3. The :e'0 sends "etParameter?alue/esponse with the "tatus arument. The type and values of this arumentare described in HKI. The internal procedure that the :e'0 must follow toB

  apply new parameter values-

  determine the value of the "tatus arument- and

  send the "etParameter?alue/esponse

is described in HKI.

9. The T/A+JD session may be torn downafter "etParameter?alue/eponse is sent by the :e'0.

5.2. 4PSe" tunne$ 4P adde "&ange not##"at#on %o"edue (8andato:)

&f the inner &Psec tunnel &P address of the :e'0 chanes and :e'0 is connected to :eM" via &P"ec Tunnel then the:e'0 shall notify the :eM" about the chane of the &P"ec &P address. To this end the :e'0 shall establish a T/A+JDsession to the "ervin :eM" and use the &nform method to update the &P"ec tunnel &P address. The procedure is shownin 7iure = AL and described net.

3GPP 

:e'0 :eM"

*. "etParameter?alues (parameter list)

3. "etParameter?alues/esponse (status)

T/A+JD session establishment

/eistration procedure completed

9. T/A+JD session tearAdown

:e'0 :eM"

,. &nform re@uest (8evice &8- &P"ec &Paddress)

*. &nform/esponse

/eistration procedure completed

3. T/A+JD session tearAdown

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!(.*elease (+

8/19/2019 32593-a00

16/19

&igure .16 )P address change notification procedure

s a preAcondition- the :e'0 must be reistered with the :eM".

,. The :e'0 invo#es &nform /P1 method as soon as possible followin a chane of the &P"ec &P address. &n the

aruments of the &nform method the :e'0 shall include 8evice &8 and the new &P"ec &P address of the :e'0.

*. The :eM" ac#nowledes the receipt of the new &P"ec &P address of the :e'0 usin &nform/esponse method.

The T/A+JD session may be torn down.

5.3 '$am Re%ot#ng Po"edue

5.3.1 '$am e%ot#ng me"&an#m "on#guat#on

This procedure allows T/A+JD Manaer- usin "etParameter?alues method- to select alarm attributes (such as perceived

severity- alarm type) that :e'0 shall use to classify its alarms for purpose of reportin them to T/A+JD Manaer. .

&igure .1/ 4 Alarm *eporting $echanism onfiguration

,. T/A+JD connection is established between the :e'0 and the :eM" as described in HKI.

*. T/A+JD Manaer initiates the confiuration of the alarm reportin mechanism by usin "etParameter?alues. The parameter /eportinMechanism is defined in H=I.

3. :e'0 responds to T/A+JD Manaer by usin "etParameter?alues/esponse messae to indicate success or failureof the procedure. &n case of failure the response messae returns an error code.

7or the details of the "etParameter?alues procedure refer to HKI section .3.*.,

5.3.2 '$am e%ot#ng %o"edue o e/%ed#ted and >ueued a$am (:RP* met&od)

;hen an alarm occurs- the :e'0 reports the alarm to the T/A+JD Manaer usin the procedure that depends on the/eportinMechanism of the alarm defined in H=I-

This procedure is applicable only to alarms classified as 2pedited :andlin and Nueued :andlin with respect to the/eportinMechanism.

3GPP 

:e'0 T/A+JD

Manaer 

*. "etParameter?alues (/eportinMechanism)

3. "etParameter?alues/esponse

T/A+JD connection establishment

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!(2*elease (+

8/19/2019 32593-a00

17/19

&igure .1(+4 Alarm *eporting Procedure for ueued Alarms

,. T/A+JD connection is established between the :e'0 and the :eM".

*. :e'0 reports the alarm directly to T/A+JD Manaer by usin &nform method.

3. ;hen T/A+JD Manaer receives the alarm- it responds to :e'0 with &nform/esponse messae.

7or the details of the &nform method refer to HKI section .3.3.,

5. P8 #$e ?%$oad Po"edue

5..1 Pe#od#"?%$oad4nte7a$ %aamete "on#guat#onT/A+JD Manaer uses "etParameter?alues method to set the Periodicpload&nterval parameter to define the periodicityfor PM file upload. /efer to H=I for definition of the Periodicpload&nterval parameter.

 'oteB ;hen the Periodicpload2nable parameter is set to 75"2 A disabled- :e'0 shall not initiate PM file upload procedure. /efer to H=I for definition of the Periodicpload2nable parameter.

&igure .1((4 Periodic?pload)nterval parameter configuration

,. T/A+JD connection is established between the :eM" and the :e'0.

*. T/A+JD Manaer sets the Periodicpload&nterval parameter for a PM file upload by the :e'0 usin"etParameter?alues method.

3GPP 

:e'0 T/A+JDManaer 

*. &nform re@uest

3. &nform/esponse

T/A+JD connection establishment

:e'0 T/A+JD

Manaer 

*. "etParameter?alues(Periodicpload&nterval)

3. "etParameter?alues/esponse

T/A+JD connection establishment

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!(5*elease (+

8/19/2019 32593-a00

18/19

3. :e'0 responds to T/A+JD Manaer by "etParameter?alues/esponse to indicate success or failure of the procedure. &n case of failure- the :e'0 shall return an error code.

 'oteB 7or details of the "etParameter?alues method refer to T/A+JD mendment * HKI .3.*.,

5..2 P8 #$e u%$oad

&igure .1(,4 P$ file upload

:e'0 uploads the PM file to 7ile "erver at every Periodicpload&nterval (see H=I for parameter definition). The uploadmethod may be one of the followinB 7TP- "7TP- :TTP- :TTP" (refer to HKI section .3.*.*)

3GPP 

:e'0 7ile "erver  

,. Periodically upload performance file

sin 7TP

8/19/2019 32593-a00

19/19

 'nne/ ' (#nomat#7e)*&ange H#to:

hange history7ate TSG @ TSG 7oc- * *ev Su8jectomment "ld Ne'Se% 2009 S'@5 SP-090552 -- -- Peentat#on to S' o 4nomat#on -- 1.0.0

e" 2009 S'@6 SP-0903A -- -- Peentat#on to S' o '%%o7a$ 1.0.0 2.0.0

e" 2009 -- -- -- -- Pu$#"at#on 2.0.0 9.0.0

un 2010 S'@A SP-10026 001 -- 8od#: eo #n ae7#at#on and m#%e$ $ed SS!TT! #n 5.1.2.3. 9.0.0 10.0.0

3GPP TS 3,-./3 0(+-+-+ ,+(+1+2!(/*elease (+