3gpp协议
-
2023年3月5日发(作者：宇宙的边疆)3GPP协议_25463-670AISG2.0
3GPPTS25.463V6.7.0(2007-06)
TechnicalSpecification
3rdGenerationPartnershipProject;
TechnicalSpecificationGroupRadioAccessNetwork;
UTRANIuantInterface:RemoteElectricalTilting(RET)
antennasApplicationPart(RETAP)signalling
(Release6)
Thepresentdocumenthasbeendevelopedwithinthe3rdGenerationPartnershipProject(3GPPTM)andmaybefurther
sentdocumenthasnotbeensubjecttoanyapprovalprocessbythe3GPP
OrganizationalPartnersandshallnotbeimplemented.
ThanizationalPartnersacceptnoliability
icationsandreportsforimplementationofthe3GPPTMsystemshouldbeobtained
viathe3GPPOrganizationalPartners'PublicationsOffices.
Keywords
UMTS,radio,antenna
3GPP
Postaladdress
3GPPsupportofficeaddress
650RoutedesLucioles-SophiaAntipolis
Valbonne-FRANCE
Tel.:+33492944200Fax:+33493654716
Internet
/doc/
CopyrightNotification
yrightandtheforegoingrestrictionextendto
reproductioninallmedia.
2007,3GPPOrganizationalPartners(ARIB,ATIS,CCSA,ETSI,TTA,TTC).
Allrightsreserved.
Contents
Foreword(5)
1Scope(6)
2References(6)
3Definitionsandabbreviations(6)
3.1Definitions(6)
3.2Abbreviations(8)
4General(8)
4.1Procedurespecificationprinciples(8)
4.2Forwardsandbackwardscompatibility(8)
4.3Multi-antennaunits(8)
4.4Integerrepresentation(8)
5Servicesexpectedfromsignallingtransport(9)
5.1Elementaryprocedureformat(9)
5.1.1Initiatingmessage(9)
5.1.2Responsemessage(9)
6Controlelementaryprocedures(10)
6.1Statemodel(10)
6.2Generalprocedurehandling(10)
6.2.1Alarms(10)
6.2.2Proceduremessageinterpretation(11)
6.2.3Parallelprocedurehandling(11)
6.3Overviewofelementaryprocedures(12)
6.4Descriptionofelementaryprocedures(14)
6.5Commonelementaryprocedures(15)
6.5.1ResetSoftware(15)
6.5.2GetAlarmStatus(16)
6.5.3GetInformation(16)
6.5.4ClearActiveAlarms(17)
6.5.5AlarmSubscribe(18)
6.5.6SelfTest(18)
6.5.7Void(19)
6.5.8Void(19)
6.5.9ReadUserData(19)
6.5.10WriteUserData(20)
6.5.11DownloadStart(21)
6.5.12DownloadApplication(21)
6.5.13DownloadEnd(22)
6.5.14Vendorspecificprocedure(23)
6.6Single-antennaelementaryprocedures(23)
6.6.1Calibrate(23)
6.6.2SendConfigurationData(24)
6.6.3SetTilt(25)
6.6.4GetTilt(25)
6.6.5AlarmIndication(26)
6.6.6SetDeviceData(27)
6.6.7GetDeviceData(27)
6.7Multi-antennaelementaryprocedures(28)
6.7.1AntennaCalibrate(28)
6.7.2AntennaSetTilt(29)
6.7.3AntennaGetTilt(30)
6.7.4AntennaSetDeviceData(30)
6.7.5AntennaGetDeviceData(31)
6.7.6AntennaAlarmIndication(32)
6.7.7AntennaClearActiveAlarms(32)
6.7.8AntennaGetAlarmStatus(33)
6.7.9AntennaGetNumberOfAntennas(34)
6.7.10AntennaSendConfigurationData(34)
7Unknownelementaryprocedures(35)
AnnexA(normative):Returncodesforsecondarydevices(36)
AnnexB(normative):Assignedfieldsforadditionaldata(37)
AnnexC(normative):Proceduresequencefordownloadofsoftwaretoasecondarydevice(38)
AnnexD(informative):Overviewofelementaryprocedures(39)
AnnexE(informative):Changehistory(40)
Foreword
ThisTechnicalSpecificationhasbeenproducedbythe3rdGenerationPartnershipProject(3GPP).
ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithintheTSGandmaychangefollowingformalTSG
theTSGmodifythecontentsofthepresentdocument,itwillbere-releasedbytheTSGwithanidentifying
changeofreleasedateandanincreaseinversionnumberasfollows:
Versionx.y.z
where:
xthefirstdigit:
1presentedtoTSGforinformation;
2presentedtoTSGforapproval;
3orgreaterindicatesTSGapproveddocumentunderchangecontrol.
ytheseconddigitisincrementedforallchangesofsubstance,calenhancements,corrections,updates,etc.
zthethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthedocument.
1Scope
ThepresentdocumentspecifiestheRemoteElectricalTiltingApplicationPart(RETAP)betweentheimplementationspecific
O&nestheIuantinterfaceandits
associatedsignalingprocedures.
2References
Thefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresent
document.
Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.
Foraspecificreference,subsequentrevisionsdonotapply.
Foranon-specificreference,aseofareferencetoa3GPPdocument(including
aGSMdocument),anon-specificreferenceimplicitlyreferstothelatestversionofthatdocumentinthesame
Releaseasthepresentdocument.
[1]3GPPTS25.460:"UTRANIuantInterface:GeneralAspectsandPrinciples".
[2]ISO/IEC13239(2ndEdition,March2000):"InformationTechnology–Telecommunicationsand
informationexchangebetweensystems–High-leveldatalinkcontrol(HDLC)procedures".
[3]3GPPTS25.462:"UTRANIuantInterface:SignallingTransport".
[4]3GPPTS25.461:”UTRANIuantInterface:Layer1”.
3Definitionsandabbreviations
3.1Definitions
Forthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply.
Activealarm:Analarmwhichhasanalarmstatethathasbeenraised,butnotcleared
Alarm:Persistentindicationofafault
Alarmcode:rmcodes
arelistedinannexAofthisTS
Alarmstate:tatesareraisedandcleared
ASCIIcharacter:AcharacterformingpartoftheInternationalReferenceVersionofthe7-bitcharactersetdefinedinISO/IEC
646:1991
Calibrate:Exercisetheantennadriveunitoveritsentirerangeoftraveltoensurefault-freeoperationandsynchronisethe
measuredandactualbeamtiltoftheantenna
Configurationdata:Astoredtableorfunctiondefiningtherelationshipbetweenthephysicalpositionofthedriveand
electricalbeamtilt
Datatype:Adefinlowingspecifieddatatypes
areusedinthisTS:
Elementaryprocedure:TheRETAPprotocolconsistsofelementaryprocedures(EPs).Anelementaryprocedureisaunitof
interactionbetweentheprimarydevice(NodeB)andthesecondarydevices(RETdevices)AnEPconsistsofaninitiating
messageandpossiblyaresponsemessage.
TwokindsofEPsareused:
-Class1:Elementaryprocedureswithresponse(successorfailure).
-Class2:Elementaryprocedureswithoutresponse.
ForClass1EPs,thetypesofresponsescanbeasfollows:
Successful
-Asignallingmessageexplicitlyindicatesthattheelementaryprocedurehasbeensuccessfullycompletedwiththereceiptof
theresponse.
Unsuccessful
-AsignallingmessageexplicitlyindicatesthattheEPfailed.
Class2EPsareconsideredalwayssuccessful.
Error:Deviationofasystemfromnormaloperation
Fault:Lastingerrorcondition
Littleendian:Theorderoftransmissioninwhichtheleast-significantoctetsofamulti-octetrepresentationofanumberare
endianonlyappliestobinaryintegerrepresentations
MaxDataReceiveLength:SecondaryPayloadReceiveLengthminus3octets(seesubclause4.8.1in[3])
MaxDataTransmitLength:SecondaryPayloadTransmitLengthminus3octets(seesubclause4.8.1in[3])
Procedurecode:Acodeidentifyinganelementaryprocedure
Reset:Aprocessbywhichthedeviceisputinthestateitreachesafteracompletedpower-up
Returncode:Acodewhichdefinesinformationabouttheoutcomeofanelementaryprocedureexecution
Tilt(alsodowntilt,tiltangle,beamtilt):Theelevationanglebetweenthedirectionorthogonaltotheantennaelementaxisand
iveelectricaltiltanglemeansthattheantennabeamisdirected
TSthetiltreferredtoisalwaystheelectricaltiltunless
otherwisestated
Tiltvalue:Asignedintegerusedinetvalueis
10timestheantennaelectricaltiltangleindegrees.
3.2Abbreviations
Forthepurposesofthepresentdocument,thefollowingabbreviationsapply:
EPElementaryProcedure
HDLCHigh-LevelDataLinkControl
RETRemoteElectricalTilting
RETAPRemoteElectricalTiltingApplicationPart
TCPTime-ConsumingProcedure
4General
4.1Procedurespecificationprinciples
TheprincipleforspecifyingtheprocedurelogicistospecifythefunctionalbehaviouroftheRETantennacontrolunitexactly
eBfunctionalbehaviourisleftunspecified.
Thefollowingspecificationprincipleshavebeenappliedfortheproceduretextinclause6:
-Theproceduretextdiscriminatesbetween:
1)Functionalitywhich"shall"beexecuted
Theproceduretextindicatesthatthereceivingnode"shall"performacertainfunctionYunderacertain
eceivingnodesupportsprocedureXbutcannotperformfunctionalityYrequestedinthe
REQUESTmessageofaClass1EP,thereceivingnodeshallrespondwiththemessageusedtoreport
unsuccessfuloutcomeforthisprocedure,containinganappropriatecausevalue.
2)Functionalitywhich"shall,ifsupported"beexecuted
Theproceduretextindicatesthatthereceivingnode"shall,ifsupported,"performacertainfunctionYunder
eceivingnodesupportsprocedureX,butdoesnotsupportfunctionalityY,the
receivingnodeshallproceedwiththeexecutionoftheEP,possiblyinformingtherequestingnodeaboutthe
notsupportedfunctionality.
4.2Forwardsandbackwardscompatibility
Theforwardsandbackwardscompatibilityofallversionsoftheprotocolshallbeassuredbyamechanisminwhichall
artscanalwaysbedecodedregardlessofthe
standardversion.
Newfunctionalitiesareaddedintothespecificationbyintroducingnewproceduresandthustheexistingmessagesarenot
changedinthefuture.
4.3Multi-antennaunits
TheRETAPelementaryproceduresaresplitintoasingle-antennaorientedpart,amulti-antennaorientedpartandacommon
partforbothdevicetypesiunitresponds,
uponrequest,ti-antennaorientedelementaryproceduresincludeaparameter
asarenumbered1andupwards.
4.4Integerrepresentation
integersarerepresentedas2-complementvalues.
5Servicesexpectedfromsignallingtransport
RETAPrequiresanassuredin-sequencedeliveryservicefromthesignallingtransportandnotificationiftheassuredin-
sequencedeliveryserviceisnolongeravailable.
5.1Elementaryprocedureformat
Layer2providesafull-duplexlinkforthetransmissionofRETAPmessages.
TherearetwotypesofRETAPelementaryprocedures:
Class1:Initiatingmessagesaresenteitherfromtheprimarytoasecondarydevice,orfromasecondarytotheprimary
device,erdevicesendsaresponsemessagecompleting
theprocedure.
Class2:Initiatingmessagesaresenteitherfromtheprimarytoasecondarydevice,orfromasecondarytotheprimary
onsemessageisexpected.
AllRETAPmessagesusethesamebasicformat:
Table5.1.1:BasicformatforallRETAPmessages
NOTE:mentaryprocedurecodeshallbe
thesameintheresponsemessageasintheassociatedinitiatingmessage.
5.1.1Initiatingmessage
Thedatapartofaninitiatingmessagemaycontainparametersasspecifiedinclause6ofthisTS.
5.1.2Responsemessage
Elementaryproceduresshall,unlessotherwisespecified,ponsetime
ismeasuredfromthetimethemessageframewasreceivedbythetransportlayertothetimetheresponsemessageisready
fortransferbythetransportlayer.
Iftheclass1elementaryprocedurerequestedbytheinitiatingmessagewassuccessfullyexecuted,theresponsemessage
responsemessagedatapartfromamulti-antennadevicestartswiththeantennanumberfollowedbyreturncodeand
optionaladditionalinformation.
Iftheelementaryprocedurerequestedbytheinitiatingmessagewasnotsuccessfullyexecuted,theresponsemessagedata
partfromasingle-antennadeviceshallcontainreturncode.
Thefollowingoctetshallcontainasecondreturncodewhichdescribeswhytheexecutionoftherequestedprocedurefailed.
Theresponsemessagedatapartfromamulti-antennadevicestartswiththeantennanumberfollowedbyreturncodeanda
secondreturncodewhichdescribeswhytheexecutionoftherequestedprocedurefailed.
Insomesituationsaninitiatingmessagecancauseachangeofoperatingconditions,forinstanceaSetTiltproceduremight
causeaRETdevicetodiscoverthatanad
thesecasesanalarmprocedurereportingthechangeofoperatingconditionsshallbeusedinadditiontotheregularorreturn
codesinresponsemessage.
AcompleteannotatedtableofallreturncodeswiththeircorrespondinghexadecimalnumbersisprovidedinannexAofthis
TS.
ReturncodesmarkedwithanXintheAlarmcolumnofannexAinthisTSareusedtoreportoperatingconditionsinalarm
procedures(seesubclauses6.6.5and6.7.6fordetails).
6
Controlelementaryprocedures
6.1
Statemodel
ationtothe
connectionstatemodelforlayer2canbefoundin[3].
LinkEstablishmentfromstate
AddressAssigned,seeref.[3]
DownloadEnd
Figure6.1:StatemodelfortheRETdevice
IfanapplicationsoftwareisnotmissingtheRETdeviceentersthestateOperatingMode.
Ifanapplicationsoftwareismissing,stateonlysoftwaredownload
functionalityissupportedinordertorestoretheapplicationsoftware.
TheprimarydevicewillbenotifiedthattheRETdevicehasenteredthestateDownloadModewhenaprocedurewhichonly
issupportedinthestateOperatingModefailswiththereturncodeWorkingSoftwareMissing.
Ifnosoftwaredownloadfunctionalityissupported,thenonlythestateOperatingModefortheRETdeviceissupported.
6.2
Generalprocedurehandling
6.2.1
Alarms
Whenafaultisdetected,thecorrespe
faultnolongerexists,thecorrespondingalarmstateshallbechangedtostateclearedbythesecondarydevice.
Alarmchangesarereportedthrougeran
AlarmIndicationorAntennaAlarmIndicationelementaryproceduremessageistransmitted,itshallcontainallthealarmstates
rmstatesshallbeclearedbyany
typeofreset.
6.2.2Proceduremessageinterpretation
Thefollowingmessageinterpretationrulesshallapplytoasecondarydeviceintheordermentioned:
-ofMulti-Antenna-Proceduresanymessagesshorterthan4
octetsshallbedisregarded.;
-Ifamessagehasalengthinconsistentwithits“Numberofdataoctets”fieldvalueitshallberespondedwithafailure
messagestating“FormatError”ponsemessageshallbetotheinitiatingmessageidentifiedby
theprocedurecode;
-IfasecondarydeviceintheOperatingModestateisreceivingaproceduremessagewhichisundefinedforthisdevicetype,
itshallrespondwith"UnknownProcedure";
-IfasecondarydeviceintheOperatingModestateisreceivingaproceduremessageofanoptionalprocedurenotsupported,
itshallrespondwithafailuremessagestating“UnsupportedProcedure”asthecauseoffailure;
-Ifasecondarydevicereceivesaproceduremessage,partofthesoftwaredownloadproceduresequencedescribedin
AnnexC,withouthavingreceivedthepreviousproceduremessagesinthatsequenceitshallrespondwithafailuremessage
stating“InvalidProcedureSequence”asthecauseoffailure;
-IfasecondarydeviceintheDownloadModestateisreceivingaproceduremessagenotsupportedinthatstateitshall
respondwithafailuremessagestating“WorkingSoftwareMissing”asthecauseoffailure;
-Ifamessagehasalengthinconsistentwiththedefinedmessagelengthintheproceduredefinitionitshallberesponded
withafailuremessagestating“FormatError”ponsemessageshallbetotheinitiatingmessage
identifiedbytheprocedurecode;
-IfasecondarydeviceintheOperatingModestateisreceivingaproceduremessagewhichaddresseddevicesubunitdoes
notexist“FormatError”shallbereturned.
6.2.3Parallelprocedurehandling
ThesecondarydeviceshallsupportparallelexecutionofinmaximumoneadditionalEPonlyinparalleltooneoftheTime-
ConsumingProceduresdefinedintable6.2.3.1:
Table6.2.3.1:DefinitionofTCPsandtheexecutionofproceduresinparalleltoaTCP
“yes”inthe"TCP"columnindicatesthattheprocedureisaTCP,“no“inthe"TCP"columnindicatesthattheprocedureisnot
aTCP.“mandatory”inthe"ExecutioninparalleltoaTCP"columnindicatesthattheprocedureshallbeexecutedinparallel
toanongoingTCP.“optional”inthiscolumnindicates,thatthesupportoftheexecutionoftheprocedureinparalleltoan
ongoingTCPisoptionaland“disallowed”indicatesthattheprocedureshallnotbeexecutedinparalleltoaTCP.
IfasecondarydevicereceivesaninitiatingmessageforanEPwhichcannotbeexecutedduetotheongoingexecutionof
otherEPs,thesecondarydeviceshallrespondwithafailuremessagestating“Busy”asthecauseoffailure.
ParallelexecutionofoneTCPmarked“optional”inthe"ExecutioninparalleltoaTCP"columnintable6.2.3.1maybe
AntennaSetTiltandAntennaCalibrateshallbeexecutedin
thanoneTCPisexecuted,ResetSoftwareshallbeexecutedanywayand
neverberespondedwith“Busy”.
IftheEPsGetTiltandAntennaGetTiltareexecutedinparallelwithaTCP,theirresponsemessageshalldeliveratiltvalue
sampledduringtheirexecution.
6.3Overviewofelementaryprocedures
Thesetofelementaryproceviewofthe
6.3.2
listsallelementaryproc6.3.3lists
allelementaryprouse6.4describeshow
tointerprettheelementaryproceduredefinitionsinsubclauses6.5to6.7.
SomeelementaryproceduresshallbeperformedinsequenceasdescribedinAnnexCforthesoftwaredownload.
Table6.3.1:Commonelementaryproceduresetforalldevicetypes
Table6.3.2:Elementaryproceduresetforsingle-antennadevicetype
Table6.3.3:Elementaryproceduresetformulti-antennadevicetype
6.4Descriptionofelementaryprocedures
Table6.4.1:Descriptionofelementaryprocedures
Table6.4.2:Initiatingandresponsemessageparametersandformat
Table6.4.3:Responsemessageparametersandformatforcommonclass1
elementaryproceduresuponerror
Table6.4.4:Responsemessageparametersandformatforsingle-antennaclass1elementary
proceduresuponerror
Table6.4.5:Responsemessageparametersandformatformulti-antennaclass1elementary
proceduresuponerror
NOTE:TheresponsemessageintheelementaryprocedureAntennaGetAntennaNumber,hastheformatgivenintable6.4.4,
althoughitisdefinedasamulti-antennaclass1elementaryprocedure.
Description:
Describesthepurposeoftheelementaryprocedure.
Table6.4.6:Returncodes
6.5Commonelementaryprocedures
6.5.1ResetSoftware
Table6.5.1.1:ElementaryprocedureResetSoftware
Table6.5.1.2:InitiatingmessageparametersandformatforResetSoftware
Table6.5.1.3:ResponsemessageparametersandformatforResetSoftware
Description:
Onthereceipto
theinitiatingmessageisreceivedintheOperatingModestate,thetransportlayershallremainunaffected.
IftheinitiatingmessageisreceivedintheDownloadModestate,theResetSoftwareprocedureshallresettheentiredevice
withoutactivatinganynewapplicationsoftwaredownloadedsinceenteringtheDownloadModestate.
Thedeviceshallnotexecutetheresetprocedurebeforetransportlayeracknowledgementthroughsequencenumberupdate
isreceivedfortheresponse.
Table6.5.1.4:ReturncodesforResetSoftware
6.5.2GetAlarmStatus
Table6.5.2.1:ElementaryprocedureGetAlarmStatus
Table6.5.2.2:InitiatingmessageparametersandformatforGetAlarmStatus
Table6.5.2.3:ResponsemessageparametersandformatforGetAlarmStatus
Description:
Onreceiptoftheinitiatingmessagethesecondarydevicereportsthealarmcodesoftheactivealarms.
Table6.5.2.4:ReturncodesforGetAlarmStatus
6.5.3GetInformation
Table6.5.3.1:ElementaryprocedureGetInformation
Table6.5.3.2:InitiatingmessageparametersandformatforGetInformation
Table6.5.3.3:ResponsemessageparametersandformatforGetInformation
Description:
OnreceiptoftheinitiatingmessagethesecondarydeviceshallreturntheproductnumberProdNrandtheserialnumber
n,tware
versionshouldindicatetheversionnumberofthecurrentlyexecutedsoftware.
TheparametersHWVersionandSWVersionintheresponsemessagerefertotheversiondesignatorsofthehardwareand
pplicationismissingornoHWorSWversionnumberisfound,thenan
tystringisrepresentedasalengthfieldequals0
andnooctetsintheTextStringfield.
TheresponsemessagelengthshallbelessthanorequaltotheminimumSecondaryPayloadTransmitLengthasgivenin
subclause4.8.1in[3].
Table6.5.3.4:ReturncodesforGetInformation
6.5.4ClearActiveAlarms
Table6.5.4.1:ElementaryprocedureClearActiveAlarms
Table6.5.4.2:InitiatingmessageparametersandformatforClearActiveAlarms
Table6.5.4.3:ResponsemessageparametersandformatforClearActiveAlarms
Description:
Onreceiptoftheinitiatingmessagethesecondarydeviceshallfirstclearallstoredalarminformationandthenreturna
procedureresponsemessage.
Table6.5.4.4:ReturncodesforClearActiveAlarms
6.5.5AlarmSubscribe
Table6.5.5.1:ElementaryprocedureAlarmSubscribe
Table6.5.5.2:InitiatingmessageparametersandformatforAlarmSubscribe
Table6.5.5.3:ResponsemessageparametersandformatforAlarmSubscribe
Description:
Onreceiptoftheinitiatingmessagethesecondarydeviceshallstartreportingalarmstotheprimarydevice.
Table6.5.5.4:ReturncodesforAlarmSubscribe
6.5.6SelfTest
Table6.5.6.1:ElementaryprocedureSelfTest
Table6.5.6.2:InitiatingmessageparametersandformatforSelfTest
Table6.5.6.3:ResponsemessageparametersandformatforSelfTest
Description:
Onreceiptoftheinitiatingmessagethesecondarydeviceshallexecuteatestprocedurewhichmayincludeacheckof
cificteststobeperformedareimplementationspecific,andmayincludethe
movementoftheadjuster,whichshallnotexceed+-5%oftotalavailabletiltingrangestartingfromthecurrentadjuster
position.
Theresponsemessageofthesecondarydeviceontheprocedureprovidesinformationondetectedfaultsor,ifnofaultis
detected,withconfidencethattheoperationofthedeviceisnormalinallrespects.
Duringthetesttheoperationalparametersofthedeviceshallnotchangebeyondoperationallyacceptablelimitsandon
completionallparametersshallbereturnedtotheirinitialvalues.
Inthenormalresponsemessage,aftertheselftestwasexecutedsuccessfully,thereturncodesaresettoreportpossible
ultsaredetected,thisshallbesignalledbynoreturncodesfollowingthereturn
code.
Inthecaseofafailureresponsemessage,theselftestcouldnotbeexecutedsuccessfullyandthereportedreturncode
relatestotheinabilityofthedevicetoperformtherequestedself-testoperation.
Table6.5.6.4:ReturncodesforSelfTest
6.5.7Void
6.5.8Void
6.5.9ReadUserData
Table6.5.9.1:ElementaryprocedureReadUserData
Table6.5.9.2:InitiatingmessageparametersandformatforReadUserData
NOTE:Numberofoctetstoreadshallbelessthan,orequaltoMaxDataTransmitLengthminus1.
Table6.5.9.3:ResponsemessageparametersandformatforReadUserData
Description:
Onreceiptoftheinitiatingmessagethesecondarydeviceshallsendbackuserspecificdatastoredinauserdataareatothe
primarydevice.
Theuserdataareaisintendedforstorageofuserdefineddata,oryinformation.
Table6.5.9.4:ReturncodesforReadUserData