




下載本文檔
版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報或認(rèn)領(lǐng)
文檔簡介
HUBArchitecture ematics FirstVersionforRFQ2TabledesDEFINITIONSAND EXPECTED GENERAL HUBFUNCTIONAL Service VHL/CUSTOMER/SERVICEDATA Vehicle HUBadmin&Userright TRANSVERSAL BASICTRANSACTIONS SERVICEUSE Voicebased Data STOLENVEHICLE PUSH ADMINISTRATIONUSE of nActivityStatus nchainstrategy Vehicle Automatic VIN 3Remote RemoteSoftware On OtherRequirementsforVHL/Customer/ServiceData MANAGEMENTFORALLIANCE’SSYSTEM Externalinterfaces InterfacebetweenVHL/Provisioningand InterfacebetweenVHL/ProvisioningandATB InterfacebetweenVHL/Provisioning InterfacebetweenVHL/Provisioning Vehicle Portalusers DefinitionsandAutonomousematicBox:on-boardunitinchargeofprovidingconnectivitywithinthevehicleforematicsservicesReturnOnElectricJointInVehicleInfotainment:on-boardunitinchargeofmultimedia,webandnavigationfunctionalities.Ithasalargecolorscreen.ItcanusetheATBasaroutertoexchangewithexternalresources(services,ematicsHeadematicsServiceContentVoiceAutomaticCallHigh-DemilitarizedLocationBasedDiagnositicTroubleThesupply/replenishing,return/recycleandinventorymanagementnumbersandmatching/de-matchingwithematicshardwaredevicesforwirelessconnectivityEstimatedtimeofFiniteStateThesaretheinputspecificationsfortheconstructionoftheHUBSpec.Theyarenotneededtoimplementthesystemandcanbenotavailabletother.ematics_Applicableematics_InEXPECTEDTheanswerfromtheRshouldbemadewith2:Filltheconformity:Detailatechnicalproposalforeachrequirementofthis.ThetechnicalproposalshouldfollowthesamesequenceofrequirementsasthisThisThisHUBspecisthesupplementaryoftheInthereferencearchitectureoverview,ematicgeneraldescriptioncoversthearea1:Thekeytopicscoveredin HUBUseStateInterfaceThekeytopicsnotcoveredin TheServicesIntegratedinCallCenterTechnicalRequirementsaboutInfrastrucutreandNetworkinhostHUBFUNCTIONALAVISIOrepresentationisusedtoaddvisualinformationforawholeoverviewofallthe“HUBFunctions”andneighboringFigure1.HUBfunctionalHUBsupportsmiscellaneousservices,tranditionalcommunicationssuchasSMS,GPRSoradvanceddatatransmittione.g.HSDPA,HSUPAareutilizedbyHUB,butthemessagetypesinthoseservicescanbeconstrainedasfollow:ServicetypeRequest/TserviceBulksofdataretrievingfrominternetorCPGenerally,HUBtransactstheservicetyperequest/responseandTCommandinSMS,bulksofdataretrievingreliesonHttp/Https,forfullyintegratingwith networkandadoptiontothe networkevolution,HUBspecifiestheVehicleDataGateway,aplug-inmoduletointerfacewitheachoftransportmediumsfrom RshouldmakeamapbetweenitsownarchitectureandthisTheRshoulddetailforeachcomponentthelevelofreusefromitsVEHICLEDATATheVEHICLEDATAGATEWAYisresponsibletoroutethedataexchangesbetweenthevehicleandresources.TLM-TheVEHICLEDATAGATEWAYshallmanagetheSMSandIPDataTheVEHICLEDATAGATEWAYisconnectedtotheSMS-Centerof TheVEHICLEDATAGATEWAYisconnectedtotheAPNof TheVEHICLEDATAGATEWAYisconnectedtotheAAAserverofthe PPROVIDERinordertoaccesstotheIP/IMSIpairsdynamically.TheVEHICLEDATAGATEWAYshallintegrateoptimizationslikeHTTP1.1withpersistentconnectionandpipelining.TheVEHICLEDATAGATEWAYshallintegrateacachingmechanisminordertooptimizetheresponsetimeofvehiclerequests.TheVEHICLEDATAGATEWAYshallmanagedifferenttreatmentchannelsforeachflowechangedwiththevehicles.TLM-TheVEHICLEDATAGATEWAYshallcheckthecredentialsfortheflowsthatarenotroutedtotheTheVEHICLEDATAGATEWAYshallmanagethesecuritybetweenthevehicleandtheresources.Especiallyfortheconnectiontointernet.TheVEHICLEDATAGATEWAYshallprovidemonitoringInordertooptimizethegatewaybehavior,thevehiclecanusedifferentURLsfortheservices.PORTinformationcanbeaddedintheURL.Theprotocolsdetails,thereturncodesandthedegradedmodeswillbeagreedbetweenthepartiesduringtheprojectphase.TheflowdetailsanddestinationisdescribedinthetableFlowURL(includeRemoteNGTPHUBRemoteSoftware:UpdateNGTPHUBRemoteSoftware:HTTP(s)orSWThirdPartyNGTPHUBDataNGTPHUBNGTPHUBConnectedMRNThirdParty(canbeInputbyVoiceMRNRemoteMRNNGTPHUBMRNNGTPHUBWebPortal:EngineMRNWebWebProtalHUBSIorThirdPartyWebPortal:ContentMRNWebVarious,butcanbeHUBSIand/orThirdParty(canbemultiple)MRNVarious,butmaybeHUBSIorThirdParty(canbemultiple)Figure2.FlowdetailsandIt’saneccessaycomponentintheNGTParchitecture.Itisincommunicationwiththevehicleandenablestheroutingofthedataaccordingtotheserviceneeds.Figure3.DispatcherTLM-TheDISPATCHERisnotserviceTheDISPATCHERshallmanagetheSMSBandwidthwiththeSMS-Center.Somehugeofnotificationscanbesent,theDISPATCHERshallschedulethemessagesaccordingtothebandwidthinordertoauthorizeregularserviceoperationswithoutlatency.TheDISPATCHERshallmanagethesizeoftheSMSpendingontheSMS-Center.Iftheamountistoohigh,theDISPATCHERshallreducethebandwidthtooavoidoverflowonSMS-Centerside.TLM-TheDISPATCHERshallmanagesomeretriesontheSMSfeltintimeoutaccordingtothe.TheDISPATCHERisresponsibletocodeanddecodetheHEADERoftheThemessageformatinDSPTisNGTPoriented;thecontentdescriptionisasfollowThistableshowsthestructureofavehiclemessageandcontainsfivecharacteristicsofthemessageattributesseparatedbyOneofthefivemessagepartstheattributebelongsto(MsgTheattributenameTheattributessizeinbytes(ifthesizeisnotfixbecauseitcouldermsoftheusedencodingformat,novalueisAflagtodefineanattributeasmandatory(M)oroptionalAshortdescriptionoftheattributeorpossibleThistablejustprovidesadataformatframework,obviously,thedetailedinformationincludesServicedataneedtobedefined,forrealizingit,theservicedataformatprotocolbetweenvehicleandHUBhasdefinedin TLM-TheDISPATCHERisnotserviceAccordingtotheDSPT_Route_Info,theService_TypeandtheMessage_Type,theDISPATCHERshallasktothePDPtherouteandthepriorityofthemessage.ThePDPwillalsosendanauthorizationforthisflowifarelatedcontractinfoisTheDSPT_Route_Infocanbeusedforexampleifsomecustomer’sclassificationsaredonegold,tinium).ItcanhelptoadjusttheAccordingtotherequestsfromthevehicleandtheSH,theDISPATCHERshallmanagetheEVENTTLM-AnEVENTisdentifiedbyaUniqueIdentifierinordertotrackitovertheWhenthevehiclecreatesorupdatesanEVENT,theDISPATCHERhastosendaTRIGGERNOTIFICATIONtothetargetedservice.ThisTRIGGERNOTIFICATIONissentovertheTheDISPATCHERshallmanagethematchingbetweentheEVENTIDandtheIDexchangedbytheATBandtheIVI.TLM-TheDISPATCHERshallimplementsomegarbagecollectorprocesstoavoidoverflowofunclosedThePDPshallcontainsinformationontheRoutinginbothdirection(SIcomponents,Vehiclenumber,vehicleIPaddress,…),theprioritymanagementandtheactiveservicesforaSERVICESHreferstotheNGTPItcodesanddecodestheSERVICEcontent,andoffersaunifiedinterfacetohidevehicle’saspectstotheFigure4.SHTheSERVICEHANDLERisresponsibletocode/decodetheServicepartofamessage.ThispartisdependentontheMessage_TypeparameteroftheHEADER.TheSERVICEHANDLERshallretrieveandaddtheinformationrelatedtothevehicleandcustomerinthemessage.ThedataareretrievedthroughtheVHL/Customer/ServiceDATATheSERVICEHANDLERarchitectureauthorizestoadd/removeservicesandmessageseasilybyVHL/CUSTOMER/SERVICEDATAVHL/Customer/ServiceDATAPROVIDERistherealcorecomprehensivedatarepositoryinHUB,accordingtodiagramof‘HUBfunctionalarchitecture’.根據(jù)HUB功能架構(gòu),在HUB中,(VHL/客戶/服務(wù))的數(shù)據(jù)提供商是真正的數(shù)據(jù)Thereare4importantexternalcooperativeparters:vehiclent, operator,ATBproviderandthe TheexchangesbetweenVHL/Customer/ServiceDATAPROVIDERandexternalpartnershallrespectthefollowingprinciples:SecurefiletransferAutomatesmanages,andoptimizesbusinessprocessesandworkflowsacrosssystems能通過系統(tǒng)自動化管理并且優(yōu)化業(yè)務(wù)流程和工作流程。DataFeedTrackableDataFeedValidatableEncrypteddatawhenfileistransferredTheVHL/Customer/ServiceDATAPROVIDERshallprovideprimitives(VHL/客戶/服務(wù))的數(shù)據(jù)提供方應(yīng)該為如下的功能提供所需的支持DataFeedMonitoring,AdministrationandExceptionHandling數(shù)據(jù)傳送的,LoggingoftheexchangesUsingtheseprimitives,anadministratorcanfollow-upandsolveanytroublesonVHL/Customer/ServiceDATAPROVIDERshouldhavedifferentdatabasestomanagethediferententitiesmentionedintheGeneralematics.Therelationshipbetweenthemisdynamicandcanbechangedoverthetime(ATBrecementfor(VHL/客戶/服務(wù))的數(shù)據(jù)提供方應(yīng)該有不同的數(shù)據(jù)庫來管理不同的實體,的,可以隨著時間變化(例如ATB替換)AftertheATBisassembliedintovehicleandtestsuccessfultheVehicleVINandothernecessaryVHLdatawhichassociatetoATBserialsNOwillbedelieverredtoHUBbyasystemunderJVresponsibility.ATB被集成到車輛中并且測試成功后,車輛VIN號以及其他的一些和ATB序列號相關(guān)的的VHLOperatorwillprovideIMSI,theICCID,MSISDNandtheresourceactivationinformation.電信運營提供IMSI,ICCID,MSISDN和資源激活日期信ATBrisresponsibleforATBmanufacturingandSIMChiptracing,duringtheATBisshippedtoJVorstoredintoinnerstock,theATBtraceabilitydatawillbesenttoJVHub,theprocessissameas ATB移動終端提供方負(fù)責(zé)ATB設(shè)備的制造和SIM的燒制,當(dāng)ATB設(shè)備生產(chǎn)完后,或者被安放在內(nèi)部倉庫時,該ATB設(shè)備的可識別信息將被送到JV數(shù)據(jù)中心,HUBkeepitsownservicecatalog,servicetable,contract/TparadatabasesinVHL/Provisioningthoughpossessthosesamedatabases,becausetheisaremotesystem,it’simpossibletomakearemotedatabaseaccessforeveryTservicerequest,sokeepanextractofdatabasecopyinHUBisfinesolution,aconfiguredtimeintervaliselapsed<daily>,thedataincontract/Tparaandservice/servicecatalogwillbesynchronizedbetween andHUB.Onceacustomerbookssomeserviceson ematicsB2Cportaloradealerhelpacustomerfinishasubscriptionprocessondealeronlinesystem,HUBwillsentreceiveanupdateofthecontractfrom .盡管 系統(tǒng)擁有同樣的數(shù)據(jù)庫,HUB數(shù)據(jù)中心還會在VHL/Provisioning里 ,服務(wù)表,和一些約定好的內(nèi)容,因為是一個的系統(tǒng),不可能讓一個系統(tǒng)處理每個服務(wù)交互請求。所以,保存一份數(shù)據(jù)系統(tǒng)和HUB系統(tǒng)間同步。一旦某個客戶在車輛智能化的B2C門戶上訂購購,HUB數(shù)據(jù)中心將會收到一個來自 TheAdministrationfeaturesoftheIVIandATBcanrefertotheVehicleManagement tformifsomeunexpectedsituationsaredetected.AsaresulttheVehicleManagementtformwillqueryandorupdatetheVHL/Customer/ServiceDATAPROVIDERaccordingtothesituation.一旦某些不可預(yù)見的情況唄偵測到,IVI和ATBTheexchangelogicoftheVHL/Customer/ServiceDATAPROVIDERisdescribedinfollowingfigure.VHL/客戶/服務(wù)的數(shù)據(jù)提供方的數(shù)據(jù)交換如下圖所示Figure5.ContextofFigure5.ContextofVHL VEHICLEMANAGEMENTTLM-TheVHLMANAGEMENT TFORMisastrategiccomponentintothearchitecture.ItsroleistomanagethelogictokeeptheATBandIVIalignedwiththevehicleandthecustomerBasedonthemodificationoftheVHL/Customer/ServiceDATAPROVIDER,theVHL TFORMhastocreatenstoconfiguretheATBandIVIwiththerelevantsettings.AsduringthelifetimeofthefleetofvehiclewemayfacesomeunexpecteddefectsorchangesofpartsintothevehiclesthevehiclepartscandetectthissituationandnotifytheVHLMANAGEMENT TFORM.TheVHLMANAGEMENT TFORMwillthenhavetoretrieveinformationfromtheVHL/Customer/ServiceDATAPROVIDER,prepareaconfigurationandupdatetheVHL/Customer/ServiceDATAPROVIDERTheVHLMANAGEMENT TFORMisresponsibletomanagetheATBSoftwaredownloadns.Thedownloaditselfwillbedonebyanexternalparty.TheVHLMANAGEMENT TFORMisresponsibletomanagesomespecificrequestbytheSIwithanimpactontheconfigurationoftheATBorMRN.FigureFigure6.ContextofVehicle HUBADMIN&USERRIGHTAcentralloggingsolutiontobeThemechanismhastobedescribedinr’sTheloggingaboutcomponentsystemsandtheloggingaboutoperationineveryparticipatingcomponentshouldbeclassifiedintocentralloggingdatabaseFigure7.ContextofHUBAsthe‘HUBAdmin/UserRightMgmt’contextdiagramillustrates,duringtheHUBsystemoperates,allapplicationsinHUBcomponentsarerecordingitsactivitystatusintoactivitylogDBonHUBAdmintform,threelogginglevelsaredefinedintologgingconfigurationfile,theyare:Error,Info,Debug.Error:whenwarnexceptionorerrorhappens,allcomponentsrelatedtotheexceptionwillrecordtheiractivitystatusintoactivitylog.Info:whenoperationruns,allcomponentswillrecordtheiroperationalinformationintoactivitylog,itincludesinformationofErrorlevel.Debug:includesinformationofInfolevel,alsooutputthemoduledetailedandin ctiveinformationamongthecomponentsinactivitylogforinvestigationofdeveloperandadministrator.Foradministratormonitoringconvenience,4reportingportalscanbeHubadministratingportaldisystherun-timehealthystatusorhistoricalhealthystatusofallcomponents(OSandapplicationlevel)inHUB,Servicereportingportalenableadministratortotraceeveryhistoricalserviceprovidedtocustomer,astatisticwindowe.g.thevolumeofservicesubscription,theusagefrequenceabouttheservice.Technicalreportingportalprovidesthesysteminfo(CPU,memory,HDarrayhealthy,etc)ofsubsystemsinHUB,Serviceadministrationportalprovideservicepublishstatusandservicemanipulationmethods,etc.Basedonthealldescriptionabove,hereisasharedlogging-centersolutionforallcomponents,thoughthemethodwriteCaseLogXX()isintroducedinthosecomponents,howefficientlyaggregatethoseloginfointothecentralloggingdatabase,stillneedtobedesignedcarefully.TRANSVERSALForalltheservicesandcustomershandling,HUBshallsupportdifferentprioritytreatmentaccordingtothefollowingTheHUBtformdesignshallsupporttheevolutionofthefunctionalitiesandtheprotocolsoverthetime.AsaresulttheHUBshallguarantythealignmentoftheversionningoneverycomponentofthechain.ThereferencestablesandtheconnectorsusedshallbescalableadapttofutureevolutionswithaminimumofdesignTheHUBshalluseUnicode(UTF-8/UTF-16),followingthisGlobally-deployedapplicationsneedastandardizedmechanismtosupportmultiplelanguages.Unicodeprovidesastandards-basedwaytorepresenttextforglobalcommunications.Also,thesystemdatabaseshallbeconfiguredtoaccept WhenaservicestampedahigherprioritycomparetootherservicesaccesstheTtform,TtformwillfirstlytransactthisservicedatainQueuesystem12(HighestbutafterE-I-4Connected3Data32Web4Software4Remote2Self3VIN2BASICTRANSACTIONSsdFromVHLtoDest(NewEvent|UpdateEventsdFromVHLtoDest(NewEvent|UpdateEventLiveSI/VHLMgmtTLM-SequencediagramfordatafromVHLto SequencediagramforGetVHLsdsdGetVHLEvent[EventID]:VHLLive[+]:VHLStaticData+Customer/ContractDataDataSequencediagramforServiceTerminate:TerminatebysdsdServiceTerminate(LaunchedbyCancelTriggerSequencediagramforServiceTerminate:TerminatebyservicesdsdServiceTerminate(launchedbyserviceprovEvent[Trigger]:StatusSequencediagramforsdsdChangerouteSequencediagramforDatatoSERVICEUSEVOICEBASEDThesequencesarebasedontheonescreatedinchapterTheregularflowfortheE-Call,B-Call,I-CallisthefollowingoneNew/UpdateEvent:E/B/IGetVHL(CCpickuptheNew/UpdateEvent:E/B/IGetVHLTerminatebyAnalternateflowfortheE-Call,B-Call,I-Callisthefollowingone TerminatebyThiscanarriveincaseofcancellationofthecallintheAnalternateflowfortheE-Call,B-Call,I-CallisthefollowingoneDatatoVHL:SendE/B/ICallNew/UpdateEvent:E/B/IGetVHLTerminatebyThiscanarriveincaseofrequestfromtheCCtothevehicletosengagaintheDATATheregularflowforthedataminingisthefollowingoneNew/UpdateEvent:GetVHLTerminatebyAnalternateflowforcanbetochangetheconfiguration.Inthiscase,youhavetorefertotheremoteconfigutationflow.STOLENVEHICLETheregularflowfortheSVTisthefollowingoneDatatoVHL:startNew/UpdateEvent:stolenvehicleGetVHLTerminateby DatatoVHL:stopAnalternateflowforcanbetochangetheconfiguration.Inthiscase,youhavetorefertotheremoteconfigutationflow.AnalternateflowfortheSVTisthefollowingoneNew/UpdateEvent:unpredictableGetVHLTerminatebyPUSHTheregularflowfortheSVTisthefollowingone DatatoVHL:pushADMINISTRATIONUSEHUBadministrationandVHLmanagementarenotastandloneprocess,itisrelativetocustomermanagement,servicecatalogbooking,Billing,contractchange(belongto)andATBservicestatuscontrol(ViaRemoteCofiguration),soVHLadministrationisareactivechainwithandVehicle.Inthischain,billingsystemisakeypoint,oncebillingsystemdetectsacustomerhaspaidforhisbookingservicecatalogoracontractiscreatedforthedeal,accordingtotheservicevaliditem(serviceispromptlyonlineorservicetakeeffectnextmonthafterhepay),alsowhenacustomer’scontractwillbeexpiredandhehasn’tintentiontorenewhiscontract,theHUBadminmechanismshouldprepareanactiontodisablerelativefunctionalitiesinhisvehicle,allfactorslikeabovedescribedwillconducttoanremoteconfigorremotesoftwareupgradeaction,theactionisnamedasninHUBdefinition,remotesoftwareupgradeisabatchn,remoteconfigcouldbeabatchnandalsocouldbemanipulatedasanoperationtoaspecificVehicle,nisactualmethodwhichimpacttocustomervehicle.TheadministrationinterfacesoftheHUBallowtochangesomedatabasesdata.SomenswillbeautomaticallycreatedTheadministrationinterfacesoftheHUBallowtocreatensNCategoryofCollectconfigparatemtersfromvechiclesbyremoteconfiguration(Batchoperationoranoperationtoaspecificvehicle)Enable/Disable ematicsfunctionality(BatchoperationoranoperationtoaspecificRemoteSoftwareUpgrade(BatchoperationinmostofthenActivityStatusDuringthen,becausesomeunpredictablereasons,thenprobablyfailsorbebrokenor eszombie(can’tgetfeedbackfromthevechicleonwhicha nprocessisongoing),sothe nstatusshouldbecontrolledbyHUB,the nphasescouldbeclassifiedintonning(forbatch)orrealtime,actionlaunch,actionprocessing,actionending, nbreakandbatchnnshouldbenned,forlaunchingnmoreaccurate,safe,reliableandreducethefauilerate,theoperationsneedtobefirstlycategoriedintorealtimeorbatchaccordingtriggeredcondition,thenthephasestepswillbenphasesstmstmStatusChainnBatchProcess n_ n nn_BatchProcess nExit_To_renshouldbematchedtomultiplededicatedadminapps,andnisanadministrativeactionchain,thesub-phasesinchainareassociated.nMgmtspansnsixlifephases,andmanipulatethenchainoperation,itcanreceiveeventfromoutsidesubsystemswhichareallocatedinHUB,andgetthestatusnotificationfromthosededicatedVHLAdminApps.ThosededicatedVHLAdminAppsmustprovideacontrolwaytonMgmt,enablethenMgmttomanagethoseapps.ThededicatedVHLAdminAppswillsent‘Success’,‘Failure’,‘Zombie’,‘Ongoing’statusnotificationtonMgmt,‘Zombie’and‘Ongoing’isakindoftempstatus,timeoutthresholdparameterissetforthetwostatusforavoidlongtimefeedbackwaitingbecausecomplexvehicledriveThenisstatedriving,likeFSM,sothenstrategyexecutiondependstriggerandconditionfilter,thereactstotriggerandconditionfilterareconvergedtonMgmt.Forsomesenarioswhichneednstrategy,refertochapterWhennisabatchoperation,besidestheactionsabovementioned,acampaingnreportincludesfailurerate,probablefailurereasonshouldbeprovided,andtheupdatefailurevehicleswillbeenrollednextbatchn.nchainstrategyWhenacustomerbooksaservicecatalog,butnotneedto Thecontractiscreatedwithoutanypayment.buttheservicesneedtoprovidednextmonth,HUBVHLloginadminwillmarkthesecontractsandaccumulatethem,nadateonnextmonthtodoabatchn. Thecontractiscreatedwithoutanypayment.buttheservicesneedtoprovidedatonce,apromptnislaunchedrealtimeforthatspecificcustomer. Thecontractnotneedtobecreated,theserviceisdevelopedforcustomer usage,soVHLloginadminwillnabatchn.Whenacustomerbooksaservicecatalog,needthecustomertoBillingdoesn’tdetectthepaymentfromthecustomer,butthecontractiscreated,HUBVHLloginadminwillmarkthiskindofcontractsandaccumulatethem,oncethepaymentisdetected,thebillingsystemnotifytheHUB,theVHLloginAdminlaunchnforthosecontracts.Billingdoesn’tdetectthepaymentfromthecustomer,andthecontractisnotneeded,thestrategyshouldbe,waitforbillingsysteminformHUBthecustomerhaspaidfortheservice,thenVHLloginadminpromptarealtimenforit.Thecontractiscreated,Billingdetectsthepaymentfromcustomer,billingwillnotifytheHUBwithparametersincludedservicename,customerid,contractID,theVHLloginAdminwilllauncharealtimen.Contractswillbeexpired,andthecustomersintendnottorenewtheVHLloginadmindetectsthecontractexpiredate,definedarenewalnotificationtimeline,whenthecontractsreachthetimeline,VHLloginadminwill andSMStothosecustomerstopreparetherenewal,ifthereisnotresponseorcustomerfeedbacktheywon’tre-enrollcontracts,VHLloginadminnsabatchntodisable tionsforvehiclesoncertainServicedevelopment/updatedJudgewhethertheservicewillimpactthevehiclesystem,ifit's,abatchsoftwaresystemupgradenisnned.ATB/IVIReferttoVHLdelieverydescriptionofchapter4.1 [DA2],themultipledelieverycasecouldbehappenedonthesametimeorit’sasinglecase,sometimesdelieveryprocessprobablyaredefferentfor4Sstoreswhicearelocatedintoprovinces,maybevariousnstrategyfor caseshappenedfor4Sneedtobedesigned,sothatwhenrequestsfortransactionof accesssystem,therelativenstrategywilltriggertheVHLadminappe.g.batchtyperealtimeObviously,thecasesarenotlimitedtothosedescribedabove,becausetheservicecommercialmodelandTapplicationsarevarious,sothenstrategyshouldbeconfigurableandeasytobetransactedwhensuddenchangeVEHICLETheregularflowfortheautodiagnosisisthefollowingoneNew/UpdateEvent:autoGetVHLTerminatebyVINTheregularflowforthe isthefollowingoneNew/UpdateEvent:autoGetVHLTerminatebyRemoteTheregularflowtosettheremoteconfigurationisthefollowingone DatatoVHL:configNew/UpdateEvent:configGetVHLDatatoVHL:TerminatebyNew/UpdateEvent:configGetVHLTerminatebyTheregularflowtogettheremoteconfigurationisthefollowingoneDatatoVHL:configuploadNew/UpdateEvent:configGetVHLTerminatebyRemoteSoftwareTheregularflowfortheremotesoftwareupdateisthefollowingoneDatatoVHL:softwareupdateNew/UpdateEvent:acknowledgeGetVHLTerminatebyDownloadprocessourofNew/UpdateEvent:acknowledgeGetVHLTerminatebyprovidestoHUBfortheservice/contract/customerrelatedinformationsynchronization,andalsoretrievethecustomerdatafromHUB,themain ctivefunctionalaspectsbetweenTLM ContractCatalogofStateandactivityspecificCustomerinformatinisupdatedin ,HUBcustomermgmtwillsyncthedatawith periodly.(includeanew essubscriber.)HUBmustsynchronizethecontractdatabasewiththesubscriptionmodificationdeclaredTheperiodofcontractdatabasesynchronizationbetweenHUBandcanbemodifiedbyHUBadministratorForallthecompaigntosupportthecontract(Create/Modify/Cancel),HUBmustacknowledgmenttouponthefinishofthecorrespondingOnAllowsadministratororcallcentertocheckaspecificcustomeractivity/servicesession/servicecatalogusagedetailinrealtimeAllowsadministratortosubscribeaperiodicallygeneratedactivityreporttoabatchofcustomer/service/servicecatalogFrequencyofreportgenerationcanbeperOtherRequirementsforVHL/Customer/ServiceDataTLM-FourdataaccessconnectivityinterfacestoVHLassambly operator,randaremaintained,onoperationlevel,theAPIinterfacesbetweenVHL/ProvisioningtoSH,VHLlogicadminareinactive.SolutionshallperformaudittrackingforallICCID/IMSIstatuschanges(deactivation,reactivation,andactive,orotherstatus)andhistory.Havetheabilitytosendandreceivemessagesfromthe operator,ATBManufacturer,VHLnt(real-timeandbatchsysteminterfacestothreepartnersforthedatainventoryonsecuredatatransmittion),andgenerateautomated notifications(Notificationswillbesentonallprocessingerrors).TLM-AllowtheusertoverifythecorrectICCID/IMSI/IMEIswereprogrammedintothehardwaretheyareshippedfromtheShallprovideaninterfacefordisyingerrorfilesreceivedfromthe operator,ATBManufacturer,VHL Shallberequiredtosendacknowledgementsformessagesreceivedfromoperator,ATBManufacturer,VHLnt,andalsorequireareceiveacknowledgementsformessagessendingtothose3partner.ShallhavetheabilitytoupdatethestatusofICCID/IMSIpairsforDataispersistentindepositoryafterreceiptsofICCID/IMSI,IMSI/IMEI,IMSI/VIN/IMEIATBmanufacture,ATB TLM-Whencontractisupdatedorsynchronized,themechanism<VHLLogicAdmin>inVHLtformistriggeredtoprepareservicesenable/disableactionsfortheWhenthecontractandserviceisupdated,sendanotificationtobillingsystemwhichisinCapabilitytosynccontract,CatalogofServices/offers,customerdatato ctivewithSHasProvidepersistencedataforadminIfno,Billingsystem,alspacesystem,andservicemgmtsystemincludesservicecreation/update/removing/publishwouldbedesignedanddeveloped.MANAGEMENTFORALLIANCE’SSYSTEM MainlytwokindsofexternalsystemsaccesscategoriestoHUB,thedatain ctionbetweenbusinessalliance’ssystemsandCP’ssystems,ATBprovider, Provider,TSPandJVntare ematicsalliance.CPsystemsarethesupplementsof ematicscontent.Figure:modulecatecoriesforAlliancesystemsandCPInNGTParchitectureconcepts,ServiceIntegratoristreatedtohandleintegrationofCPsystemservicebyunifyingtheCPservicedataintoinnerdataformatofTtform,andhastoneglecttoconstrainthedataflowfromematicsalliancesystembecausetheyarevariousandisolated,butforHUBimplementation,thealliancesystems’accessprocessanddatafeedsstillneedtobeconstrainedandmanaged,asuggestedsolutionnamedADFwillbedescribedbelow:Figure:UnitedDataIntegFrameworkforUnderthisarchitecture,indataacqusitionlayer,theendswillsenddataaccordingtorpcoessscheduleviapre-establishedchannels(heretheserverserviceandSFTP/FTPareassumed),theDataIntegrationlayerwouldintegrateandcleansethesourcedata.Subsequently,theDataConversionlayerwouldtransformthisdataintotheprescribedformatsandsubmitthemintorelativestoragesortosomeApps’Generally,thecomponentsinUnitedDataIntegrationFrameworkcanhandledmostofalldatafeedprocessandexceptions,thoughthedatain ctionamongHUBandalliancesystemsisnotclearyet,theprotocolexpansioniseasilytorealizedunderthisframework.SFTP/FTPAnassumptionforsecuredatatransferringbetweenHUBandexternalsystems,theresidesinDMZwillforwardfiletorealSFTPserverininternalnetworkthroughsecureWebForservingHTTP(S)requesttunnelingfromexternalpartners,inthiscase,thedata ctionisviawebservice.TokenTheallsecuresignatureinthefileswillbeauthenticatedinthisDataFeedBuilding/RunningontopofDUImgmtserver,datafeedprocessorprovidescommonframeworkfordatafeedprocessing,itconsistsofDataDataDataDataMessageDataDataFeedMonitoring,AdministrationandExceptionHandlingBuilding/RunningontopofDUImgmtserver,datafeedconfigurationandmonitoringprovidesonlinescreenforconfigurationandmanagementfacility.DataFeedexception
溫馨提示
- 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 兼職代賬合同范本
- 監(jiān)控安裝員工合同范本
- 酒店商鋪租用合同范本
- 污水站維護(hù)合同范本
- 路橋合同租賃合同范本
- 窒息患者護(hù)理措施提問
- 社區(qū)內(nèi)科護(hù)理
- 腸結(jié)病護(hù)理中醫(yī)
- 2025至2030年中國建筑鐘數(shù)據(jù)監(jiān)測研究報告
- 浙江國企招聘2024寧波象山鐵路投資有限公司招聘1人筆試參考題庫附帶答案詳解
- 生物產(chǎn)品檢驗檢疫基礎(chǔ)知識單選題100道及答案
- 江蘇省中職《英語》學(xué)業(yè)水平考試備考試題集(含歷年真題)
- 2025年合伙型公司新合伙人加入?yún)f(xié)議
- 2025年安全員之C證(專職安全員)考試題庫
- 2025城市商鋪買賣合同書
- 醫(yī)院感染及其危害
- 2025年春新北師大版物理八年級下冊課件 第六章 質(zhì)量和密度 第一節(jié) 物體的質(zhì)量及其測量
- 2024全國各省高考詩歌鑒賞真題及解析
- 《價值觀培訓(xùn)》課件
- 《臨床科研思維》課件
- GA/T 761-2024停車庫(場)安全管理系統(tǒng)技術(shù)要求
評論
0/150
提交評論