內(nèi)容分析成果onstar bdif pvn interface spec

BDIFandProvisioningInterfaceShirleyLu Date SOSBDIFPMShiYu Date SOSProvisioningPMLiLi Date SunBDIFPMRevisionSummaryofmjorchangesAnnSunJunInitialJunModificationsaftermeetingwithProvisioningAddedprovision3.4.2Shipped_sentData3.4.3Scrap_sentData3.4.2Shipped_sentData3.4.3Scrap_sentData3.4EDI53.5CellularESNJunUpdatedafter2ndroundreviewwithProvisioningUpdatedschemaEDI5AddedPairedErrfeedUpdatedschemaEDI2UpdatedschemaCelluarESNJunUpdatedInterfaceList:sectionModifiedEDI5interfaces:sectionModifiedEDI2interfaces:sectionAddedActivatedfeedinterfaces:sectionModifiedCellular_ESNinterface:sectionModifiedExceptionHandlingapproach:sectionYongKongUpdatedActivatedSchemaUpdatedCellular_EsnfeeddescriptioninUpdatederrorhandlingruleinJunReadyforJun NumberDeactivationNotificationschemachangetoadd‘status’to‘ImsiEsnPair’CorrectedUserEnrollmentParaelementJunUpdatedCarrierNotificationServiceImplementationWSDLfile(embedded)JunUpdated,,,JohnHungAddedsection3.8forProvisioningJMSdetailsandupdatedtheWSDLfileCarrierNotificationInterface.UpdatedstagingtablesinformationinsectionJunUpdatedqueuenaming3.4.4,JunUpdatedbdif_pvn_edi5.xsdtoaddxmlnamespaceJunUpdatedPVNstagingtablesschema3.6.3UpdatedSequenceNumberdefinitionnotesJohnUpdatedXSDforSHIPPED_SENTandSCRAP_SENTandAllowemptyrecordsetinSHIPPED_SENTandRemovedSTIDUniquenessRemovedtypesandenumerationsforPairedError,whicharefromtheoldEDI5flow.JunAddedpredefinedvaluesforFeedName,SourceID,etc.–,,,,,,JunRevertedthechangetoSHIPPED_SENT/SCRAP_SENTschematonotallowzerodatarecord–,,,RitaAddedvalidvaluesforstatus–AddeddescriptionforEDIERRORCD–RitaUpdated2realtimeinterfacesaccordingtoCT’sinterfacewith3.1MDN/IMSIDeactivationReal-UpdatedminDeactivationAdded Updated 3.3UserEnrollmentReal-UpdateduserEnrollmentAddedUpdatednotifyUserEnrollmentResultAdded1realtimeinterfaceunitCancellation3.4MDN/IMSICancellationReal-AddedAddedAddedJunBDIF_PVN.wsdlsplitintotwowsdlfiles:BDIFPVNDisconnect.wsdl(section,RitaAddESN_SENTinterfaceAddCarrier_ESNUpdateActivatedNotificationinterface,addvendor_duns_numberinoutboundmessagetoindicatehardwaremanufacture.UpdateEDI5(shippedSent/scrapSent)interface,addvendor_duns_numberinoutboundmessagetoindicatehardwaremanufacture.RitaUpdatedprocessflowforEDI1andJunUpdatedprocessflowforCellular_ESN(sectionRitaAddedHFCrelatednotifyChangeSystemHFCMinutesResultrealtime NumberHFCMinutesrealtime realtimeinterfaceMDNHFCCallingDetailStagingInterfaceUpdatedInterfaceList.UpdatederrorcodeinactivatedReceivedJMSWeiBDIF_PVN_HFC.wsdlsplitintotwowsdlfiles:changeSystemHFCMinutesBDIFwsdl NumberHFCMinutesBDIFwsdlUpdatePVN_HFC.wsdlUpdateHFCrelatedinterfacesUpdateHFC_DETAILCALL_DURATIONcolumnUpdateVender_Duns_Number Interface Inteface MDN/IMSIDeactivationReal-time MDN/IMSIActivationReal-time(outofscopeforR1) minActivation UserEnrollmentReal- userEnrollment MDN/IMSICancellationReal-time unitCancellation EDI5–ShippedMIN/ESNandScrapMIN/ESNfilesBatch EDI5ProcessFlow SHIPPED_SENT SCRAP_SENT BDIF_PVN_EDI5Interface(SHIPPED_ERR/SHIPPED_APP/SCRAP_APP/ OriginalEDI2–MarriedIMSI/ESNfileBatchFeed EDI2ProcessFlow ActivatedESN/MDN/IMSIfileBatchFeed DefinitionofPVNStaging notifyActivatedSentJMSMessage notifyActivatedReceivedJMSMessage Cellular_ESNDataFeed CellularESNData OriginalEDI1–ESN_SENTfileBatch Process ESN_SENTStaging DefinitionofPVNStaging NotifyESNAPPJMSMessage CARRIER_ESNfileBatchFeed CARRIER_ESNStaging DefinitionofPVNStaging notifyCarrierEsnJMSMessage CARRIER_ESN_ERRFile ESN_APPJMSMessage MDNHFCMinutesChangeReal- MDNHFCCallingDetailQuery MDNHFCCallingDetailStaging DefinitionofPVNStaging ProvisioningJMSModule Exception/ErrorHandling ErrorNotification ThisistheprimarydetailedrequirementsdescriptionofallinterfacesbetweenBDIFsystemandPVNsystem.ThisincludesBDIFownedinterfacesexposedtoPVNsystem,forwhichthisshouldberegardedastheprimarysource.ItalsolistsPVNownedinterfacesexposedtoBDIF,totheextentasunderstoodatthistime,forcontractualandreferencepurpose,butshouldnotberegardedastheprimarysourceofthatinformation. shouldbereadandunderstoodbyallsystemstakeholderswithaninterestinthedetailedinterfacespecificationbetweenBDIFandPVN.Mostimportantly,thisincludesthosewhoarebuildingthesystemandthosewhowilluseittocarryouttheirbusinessresponsibilities.Theinterfacesspecificationoutlinedinthis describethedetailedtechnicalviewofcallinterface,elementsdefinition,error/exceptionhandlingetc.allpertinentinformationnecessarystousetheinterfaceeffectivelyandSeeDataSharingAgreement(DSA)andSystemRequirementSpecification(SRS)forthedetaileddatausage,sharingandsystemrequirements,usecasesandprojectscope.InterfaceData MDN/IMSIDeactivationReal-ESN/MDN/IMSIreal-timeESN/MDN/IMSIreal-timedeactivationordernotificationESN/MDN/IMSIreal-timedeactivationresultnotificationUserEnrollmentReal-UserESN/MDN/IMSIreal-timeUserEnrollmentordernotificationESN/MDN/IMSIreal-timeUserEnrollmentresultnotificationNumberDeactivationUserESN/MDN/IMSIreal-timedeactivationordernotificationESN/MDN/IMSIreal-timedeactivationresultnotificationUserESN/MDN/IMSIreal-timeUnitCancellationordernotificationESN/MDN/IMSIreal-timeUnitCancellationresultnotificationMDN/IMSIActivationReal-ESN/MDN/IMSIreal-timeactivation(outofscopeforR1)ESN/MDN/IMSIreal-timeactivationnotification(outofscopeforR1)ESN_SENTfileBatchLoadESN_SentESNfilefromhardwaremanufactoryintoPVSStagingNotifyESNAPPJMSMessageNotifyBDIFtheprocessingcompleteofESN_SENT,BDIFwouldforwardESN_ERRtohardwaremanufactoryandESNSENTtoCARRIER_ESNfileBatchCARRIER_ESNStagingLoadESN_ERRfilefromnotifyCarrierEsnJMSMessageNotifyPVNthefinishedloadingofNotifyESNAPPJMSMessageNotifyBDIFtheprocessingcompleteofESN_SENT,BDIFwouldforwardESN_ERRtohardwaremanufactoryandESNSENTtoEDI5–ShippedMIN/ESNandScrapMIN/ESNfilesShippedfilesentdataScrapfilesentdataProcessresponseforShipped/Scrap:SHIPPEDERRmessagesentSHIPPED_APPmessagesentSCRAP_APPmessagesentSCRAP_ERRmessagesentOriginalEDIEncryptedPairedwithA-KeyfileEncryptedPairedwithA-KeyfilewillbesenttoConti,afterPVNhasnotifiedBDIFthattheActivatedfeedisgood;theoriginalActivatedfilewillalsobesentalongsothatConticancrosscheckwiththeEncryptedfilecontentLoadActivated_SentESN/MDN/IMSIfilefromintoPVSStagingNotifyPVNtheActivated_SentloadingisGenerateACTIVATED_ERRfilefromPVNStagingforNotifyBDIFtheprocessingresultofActivated_SentStagingdata(BDIFdependsonthisnotificationtodecidewhethertoholdontheencryptedCellularESNmessgeChangedefaultandalltheHFCminutescurrentlyIN_USEutesInterfaceChangeHFCminutesofaspecifiedMDNHFCCallingDetailStagingInterfaceBDIFloadHFCcallingdetaildataintothestagingareaofPVNdatabase.IntefaceThissectiondefinesthedatafeedinterfacesbetweenBDIFandPVNMDN/IMSIDeactivationReal-minDeactivationInterfaceInterfaceSOAPUsage2500usersperday,20concurrent1KperInterfaceDefinitionWSDLSchemaminDeactivationRequestminDeactivationResponseStatusCodes- Whatarethevalidstatuscodes?StatusMessage- Whatarethevalidstatusmessages?Jma:theresponsemessageschemahereisleftunchangedfromtheoriginaldesignfortwoKeeptheinterfacedesignascoherentasForfutureextensionpurpose,wheninterfacewith goesWebServiceseventuallyCurrentlythisresponsemessageisusedmainlyjustforacknowledgement.StatusCode–0(requestreceivedOK)StatusMessage–RequestReceived -WhatarethevalidCode? -WhatarethevalidmessageEAIExtResultSet–WhyisthereanJma:theBaseResultisusedtowraptheexternalresultreturnedfrom ,incurrentcase,itwouldbeempty.ElementElementDataMandatory/Identifiesthecurrenttransaction:“mdndeactpvn2bdif”IdentifiestheSourceApplication:CountofTimestampofInputIdentifiesthe : MinDeactivationData Mandatory/Uniqueid,withfixedlength16,willbeusedtotracktherequest,generatedby接觸流水號IDKeepthesameas受理工號021Thiselementisforextendpurposelater MDNFixedlengthData ElementMandatory/IdentifiesBDIFinstanceforthetransaction,forcorrelationpurposeBDIFreturnStatus0–Success;1–Status ProcessedrecordsTimestampofData ElementFaultFault FaultInterfaceDefinitionnotifyEnrollmentDeactivationOrderInterfaceInterfaceSOAPUsage2500userperday,20concurrent1KperInterfaceDefinitionWSDLSchemaElementElementDataMandatory/IdentifiestheuniqueBDIFid,whichshouldbeusedtotracktheoriginalresponsefromCTIdentifythe ,put ThetimewhengettheElementDataMandatory/Uniquerequestid,lenthisfixedto0–Success,1–errorcodeinthecaseoffailure,maxlengthisreasonoferror,maxlengthisOrdernumberfortherequestidentifiedbyrequestid,maxlengthis20OrderIdfortherequestidentifiedbyrequestid,maxlengthis32thetimewhenrequestwasacceptedbyElementDataMandatory/0–Success1–ElementDataMandatory/0–Success1–ElementDataWebServiceFaultWebServiceFault WebServiceFaultInterfaceDefinitionnotifyEnrollmentDeactivationResultInterfaceInterfaceSOAPUsage2500userperday,20concurrent1KperInterfaceDefinitionWSDLSchemaEnrollmentDeactivationResultNotification(PVN:pleasechangethesubelementsoccurrencefromsingletomultiplicity,asalreadyreflectedinthediagrambelow):Eachdeactivationrequestmayreturndifferentstatus,somemaybesuccessfulandsomemaybefailure.Theycannotbegroupedtogether.Jma:Yestheycan,ineachpair,the‘ImsiEsnPair’and‘status’aregroupedasoneoccurrence,asalreadyupdatedbelow: eactivationNotificationFaultElementElementDataMandatory/IdentifiestheuniqueBDIFid,whichshouldbeusedtotracktheoriginalresponsefromCTIdentifythe ,put ThetimewhengettheElementDataMandatory/Uniquerequestid,lenthisfixedtoOrdernumberfortherequestidentifiedbyrequestid,maxlengthis20Directory SubscriberIdentification ElectronicSerialNumberfortheVehicleCommunication 0–Success,1–errorcodeinthecaseoffailure,maxlengthisreasonoferror,maxlengthisElementDataMandatory/0–Success1–ElementDataWebServiceFaultWebServiceFault WebServiceFaultInterfaceDefinition<CarrierNotificationServiceImplementation.wsdl>(seesectionMDN/IMSIActivationReal-time(outofscopeforminActivationInterfaceInterfaceSOAPUsage2500usersperday,20concurrent1KperInterfaceDefinitionWSDLSchemaminActivationRequestminActivationResponseElementElementDataIdentifiesthecurrenttransaction,equalsthenameoftheinterfacecallIdentifiestheSourceCountofTimestampofInputElementData路設(shè)備號ESNImsiElementDataIdentifiesBDIFinstanceforthetransaction,forcorrelationpurposeBDIFreturnStatusStatusProcessedrecordsTimestampofInterfaceDefinition<BDIF_PVN.wsdl>(seesectionnotifyNumberActivationInterfaceInterfaceSOAPUsage2500userperday,20concurrent1KperNotimplementedforreleaseInterfaceDefinitionWSDLSchemaNumberActivationNotificationAcknowledgeNumberActivationNotificationFaultElementTheElectronicSerialNumber(ESN)fortheVehicleCommunicationtform(VCP).InternationalSubscriberIdentificationDirectoryNumber.WebServiceFaultWebServiceFaultFauWebServiceFaultInterfaceDefinition<CarrierNotificationServiceInterface.wsdl>(seesectionUserEnrollmentReal-userEnrollmentInterfaceInterfaceSOAPUsage2500usersperday,20concurrent1KperInterfaceDefinitionWSDLSchemauserEnrollmentRequestuserEnrollmentResponseElementElementDataIdentifiesthecurrenttransaction:IdentifiestheSourceApplication:CountofTimestampofInputIdentifiesthe : UserEnrollmentData Mandatory/Uniqueid,withfixedlength16,willbeusedtotracktherequest,generatedby接觸流水號IDKeepthesameas受理工號021Thiselementisforextendpurposelater MDNFixedlengthData ElementMandatory/IdentifiesBDIFinstanceforthetransaction,forcorrelationpurposeBDIFreturnStatus0–Success;1–Status ProcessedrecordsTimestampofData ElementFaultFaultFauFaultInterfaceDefinition<BDIF_PVN.wsdl>(seesectionNotifyEnrollmentDeactivationOrderRefertosectionnotifyEnrollmentDeactivationResultRefertosectionMDN/IMSICancellationReal-unitCancellationInterfaceInterfaceSOAPUsage2500usersperday,20concurrent1KperInterfaceDefinitionWSDLSchemaunitCancellationRequestunitCancellationResponseElementElementDataMandatory/Identifiesthecurrenttransaction:IdentifiestheSourceApplication:CountofTimestampofInputIdentifiesthe : Data Mandatory/Uniqueid,withfixedlength16,willusedtotracktherequest,generatedby接觸流水號IDKeepthesameas受理工號021Thiselementisforextendpurposelater MDNFixedlength“其他Data ElementMandatory/IdentifiesBDIFinstanceforthetransaction,forcorrelationpurposeBDIFreturnStatus0–Success;1–Status ProcessedrecordsTimestampofData ElementFaultFaultFauFaultInterfaceDefinitionnotifyUnitCancellationOrderInterfaceInterfaceSOAPUsage2500userperday,20concurrent1KperInterfaceDefinitionWSDLSchemaNotificationFaultElementElementDataMandatory/IdentifiestheuniqueBDIFid,whichshouldbeusedtotracktheoriginalresponsefromCTIdentifythe ,put ThetimewhengettheElementDataMandatory/Uniquerequestid,lenthisfixedto0–Success,1–errorcodeinthecaseoffailure,maxlengthisreasonoferror,maxlengthisOrdernumberfortherequestidentifiedbyrequestid,maxlengthis20OrderIdfortherequestidentifiedbyrequestid,maxlengthis32thetimewhenrequestwasacceptedbyElementDataMandatory/0–Success1–ElementDataWebServiceFaultWebServiceFault WebServiceFaultInterfaceDefinition<CarrierNotificationServiceImplementation.wsdl>(seesectionnotifyUnitCancellationResultInterfaceInterfaceSOAPUsage2500userperday,20concurrent1KperInterfaceDefinitionWSDLSchema eactivationNotificationFaultElementElementDataMandatory/IdentifiestheuniqueBDIFid,whichshouldbeusedtotracktheoriginalresponsefromCTIdentifythe ,put ThetimewhengettheElementDataMandatory/Uniquerequestid,lenthisfixedtoOrdernumberfortherequestidentifiedbyrequestid,maxlengthis20Directory SubscriberIdentification ElectronicSerialNumberfortheVehicleCommunication 0–Success,1–errorcodeinthecaseoffailure,maxlengthisreasonoferror,maxlengthisElementDataMandatory/0–Success1–ElementDataWebServiceFaultWebServiceFault WebServiceFaultInterfaceDefinition<CarrierNotificationServiceImplementation.wsdl>(seesectionEDI5–ShippedMIN/ESNandScrapMIN/ESNfilesBatchEDI5ProcessFlow1EDI-864ShippedMIN/ESN1EDI-8642EDI-9972EDI-997EDI-864EDI-8644EDI-9971EDI-864ScrapMIN/ESNprocess1EDI-8642EDI-2EDI-997EDI-86444EDI-997EDI-EDI-864ProvisioningsystemisresponsibleforEDI5datafeedsinterfaceofSHIPPED_SENTandBDIFsystemisresponsibleforEDI5datafeedsinterfaceofSHIPPED_APP,SHIPPED_ERR,SCRAP_APP,SCRAP_ERR. BDIFEDI5interfaceutilizesoneunifiedinterfacedefinition.SHIPPED_SENTInterfaceInterfaceUsageDaily2500InterfaceDefinitionSchemaShippedSentschemaElementShippedSentUniqueIDfortheNumbermustbeequaltonumberofshipsentDateTimeofthisEDISenderHardwaremanufature’sdunsShippedSentIMSI–Numericalwithalengthof14–ESN–NumericalwithalengthofMDN–NumericalwithalengthofStationID–Numericalupto15ReworkTagmaxlengthofTimestampofShippedDateTheIMSI,ESN,MDN,STIDmustbeuniqueperInterfaceDefinitionSCRAP_SENTInterfaceInterfaceUsageDaily2500InterfaceDefinitionSchemaScrapSentschemaElementScrapSentUniqueIDfortheNumbermustbeequaltonumberofshipsentDateTimeofthisEDISenderFirstpartisvenderpartyid,secondpartwillbe‘_’asaconnector,thethirdpartisdunsnumberScarpSentIMSI–Numericalwithalengthof14–ESN–NumericalwithalengthofMDN–NumericalwithalengthofStationID–Numericalupto15ReworkTagmaxlengthofTimestampofShippedDateTheIMSI,ESN,MDN,STIDmustbeuniqueperInterfaceDefinition<PleaserefertoBDIF_PVN_EDI5Interface(SHIPPED_ERR/SHIPPED_APP/SCRAP_APP/InterfaceInterfaceJMSusername/passwordUsageDaily2500InterfaceDefinitionXMLschemaElementCreationSEQUENCEMessageSequenceFEEDFeedNamerequired:FEEDFeedsource:FEEDF=Full,MessageCorrelation ElectronicSerialNumber(ESN)theVehicleCommunicationtform SubscriberIdentificationDirectoryNumber.StationAuthenticationReworkErrorRECORDThecountofrecordsinthefileforthisFirstpartisvenderpartyid,secondpartwillbe‘_’asaconnector,thethirdpartisdunsnumberInterfaceDefinitionOriginalEDI2–MarriedIMSI/ESNfileBatchEDI2ProcessFlowEncryptedPairedwithA-KeyfilewillbesenttoConti,afterPVNhasnotifiedBDIFthattheActivatedfeedisgood.ActivatedESN/MDN/IMSIfileBatchInterfaceInterfaceUsageMonthlyProjectedthebatchtobe60KRecordsin5years,whichwillbe20MbytesinsizeBDIFwillloadtheActivateddataitreceivesfromintoPVNstagingtable,andnotifyPVNviaJMSmessagewhentheloadisdone.InterfacePVN_STAGEDatabaseThistablewillcontaintheheaderdescriptionforeachfeed.ThistablewillcontainthedataforeveryACTIVATEDandACTIVATEDERRORfeedThistablewillbealookuptableforthestatusDefinitionofPVNStagingUniqueSequenceNumberforeveryThisnumberissystemassignedfromanOracleSequenceSEQ_PVN_STAGE_META/ContiMessageIDUsedformessageTransactionTypeofthefeedValidvalues:ACTIVATED(whenBDIFstagesfeed)TTotalnumberofrecordsforeachfeed;ThisnumbershouldmatchtherowcountofthedatatableSENDERID:RECEIVERID:CreatedCreatedbyID:BDIF(whenBDIFstagesUpdatedbyUniqueSequenceNumberforeveryThisnumberissystemassignedfroman OnerowcorrespondingtoeverydataOnerowcorrespondingtoeverydataOnerowcorrespondingtoeverydataOnerowcorrespondingtoeverydataValidEDIstatusshouldbe0(Accepted)whenBDIFfirststagesthefeedValidprocessingstatusshouldbe10(Staged)whenBDIFfirststagesthefeedForeignKeyassociatedwithSEQUENCE_NUMBERofCreatedbyID:BDIF(whenBDIFstagesCreatedUpdatedby0DataisDetailedEDI_STATUScodesdefinition0Datais1CannotlocateESNtheESN2CannotlocateIMSItheIMSI3CannotlocateMDNtheMDN4DuplicateIMSI5DuplicateESN6DuplicateMDN7Invalid8Invalid9InvalidInvalid無效Invalid無效CannotprocessdataRECORDhasbeenRECORDhasbeenRECORDisbeingProvisioninghasbeenupdatedwithdatainthisrecordProvisioninghascompletedprocessingcycleonthisstagedrecordnotifyActivatedSentJMSMessageInterfaceInterfaceJMSUsageWhenBDIFhasdoneloadingthePVN_STAGE_ACTIVATEDstagingtable,BDIFwillnotifyPVNvianotifyActivatedSentInterfaceDefinitionXMLschemaElementFieldTypeoffeed,fromIDofthisnotificationNumberofrecordsintheSourceofDestinationofSequencenumberfromPVNSTAGEMessageCreationDateInterfaceInterfaceUsageMonthlyProjectedthebatchtobe60KRecordsin5years,whichwillbe20MbytesinsizeIncasethatthereisACTIVATED_ERR,BDIFwillreadfromPVN.InterfaceThesamestagingtablePVN_STAGE_ACTIVATEDwillbenotifyActivatedReceivedJMSMessageInterfaceInterfaceJMSUsageAfterPVNhasprocessedtheActivatedrecordsinthestagingtable,therecouldbetwocases:IfPVNfindsanyerrorintheActivateddata,itwillmarktheerroneousrecordsasACTIVATED_ERRinthestagingtable,andnotifyBDIFvianotifyActivatedReceivedJMSmessage;BDIFwillholdontheencryptedPairedfileIfthedataisgood,itwillalsonotifyBDIFnotifyActivatedReceivedJMSmessage,BDIFwillthenforwardtheencryptedPairedfiletoContiInterfaceDefinitionXMLschemaElementElementDataCreationdate,YYYY-MM-MessagesequenceForsuccesscondition,thesequencenumberisthesameofinboundsequencenumber.Forfailurecondition,thesequencenumberisthenewsequencenumber(whichisassociatedwithinboundfeedthroughBDIFmessageID)Feedname:Feedsource:Feedtype:CountofdetailFirstpartisvenderpartyid,secondpartwillbe‘_’asaconnector,thethirdpartisdunsnumberElementDataResult––ErrorErrorExtensionResultExtensionResultElementExtensionResultElementExtensionResultElementExtensionResultElementIncaseofresult=1,theerrorcodecanbethevalueslistedMultiplevendorsfoundinthewholebatchofInterfaceDefinitionCellular_ESNDataOnceBDIFhasreceivedSHIPPED_APPorSHIPPED_ERRmessagefromProvisioning,BDIFcangeneratetheCELLULAR_ESNdatafeedforGVSbasedontheSHIPPED_APPorSHIPPED_ERRdatafeed.NoadditionaldatafromProvisioningsystemisrequiredforgeneratingsuchfeed.CellularESNDataInterfaceBDIFPVNCELLULARESNInterfaceUsageDaily2500SinceeitherSHIPPED_APPorSHIPPED_ERRcontainsallofvalidatedESN/MDN/IMSIpaireddata,theCellular_ESNfeedcanbetriggeredandusethedatafromtheSHIPPEDfeed.3InterfaceDefinition3InterfaceDefinitionSeeSHIPPED_APP/SHIPPED_ERRmessageformatinsectionOriginalEDI1–ESN_SENTfileBatchProcess1EDI11EDI15Thisblockofprocessescanhappenmultiple61:BDIFwouldloadESNbyblockonreceivingfromHardware2A:BDIFwilldothebasicblocklevelvalidationatBDIF.ThevalidationitemESNformatESNHextoDecimalBlocklevelrecordcountlevelBlocklevelrecordduplication3:Normally,Thisprocessistriggeredautomaticallyonapre-defineddateforeachhardwaremanufactory.ProvisioningwouldalsoprovideaUItomanuallytriggerthisprocessasdemanded.3:Provisioningwilldothebatchlevelvalidation,validationitemsBatchlevelrecordcountBatchlevelrecordduplicationOtherbusinessrelatedThevalidationisbasedonthepartial4A&4B:ProvisioningwillsendoutESN_APPoncevalidationBDIFwouldfilteroutalltheinvalidESN,generateESN_ERRandsenttohardwareBDIFwouldfilteroutallthevalidESN,generateESN_SENTandsendtoCarrier.ESN_SENTshouldonlycontaintheESNfromthesamehardwaremanufactory. willdothevalidationontheESN_SENTfilereceivedandsendoutESN_ERRifthereisanyerrorfound,BDIFwouldpassitasCARRIER_ESNtoProvisioning6:ProvisioningwouldhandleCARRIER_ESN,deletethoseESNmarkedasinvalid,andsendoutESN_APP,theschemaisthesameastheonementionedat4A&4B.IfthereisanyerrorfoundinCARRIER_ESN,suchastheESNisnotfoundinprovisioning’sdatabase,somemanualprocesswouldtakeover,shouldresendESN_ERRaftercorrection.BeforeautomaticinterfaceisreadyatCarrierSide,BDIFisresponsibleformanuallygenerateESN_ERRandtriggertheCARRIER_ESNinterfaceatProvisioning.ESN_SENTStagingInterfaceESNSENTInterfaceUsageMonthlyProjectedthebatchtobe60KRecordsin5years,whichwill20MbytesinBDIFwillloadtheESNdatawithitsvendordunsnumberintoPVNstagingtable,PVNwilltriggertheprocessonapre-defineddateoncepermonthforeachhardwaremanufactory.ThisprocesscantriggeredmanuallyonInterfacePVN_STAGEDatabaseThistablewillcontaintheheaderdescriptionforeachfeed.ThistablewillcontainthedataforeveryESN_APPandESN_ERRfeedThistablewillbealookuptableforthestatusDefinitionofPVNStagingUniqueSequenceNumberforeveryThisnumberissystemassignedfromOracleSequence/ContiMessageIDUsedformessageTransactionTypeofthefeedValidvalues:ACTIVATED(whenBDIFstagesfeed)ESN_SENT(whenBDIFstagesCARRIER_ESN(whenBDIFstagesfeed) ESN_APPmightnotbeinpairTTotalnumberofrecordsforeachfeed;ThisnumbershouldmatchtherowcountofthedatatableSENDERID:RECEIVERID:CreatedCreatedbyID:BDIF(whenBDIFstagesUpdatedbyUniqueSequenceNumberforeveryThisnumberissystemassignedfromanOracleSequenceSEQ_PVN_STAGE_ESN––OnerowcorrespondingtoeverydataFirstpartisvenderpartyid,secondpartwillbe‘_’asaconnector,thethirdpartisdunsTheblockidoriginallysentfromhardwaremanufactory,logforCARRIER_ESN.ValidEDIstatusshouldbe0(Accepted)whenBDIFfirststagesthefeedValidprocessingstatusshouldbe10(Staged)whenBDIFfirststagesthefeedForeignKeyassociatedwithSEQUENCE_NUMBERofwhenBDIFstageESN,usedifferentsequencenumberbyeachblock.AfterPVNprocessedESN,PVNwillupdatethesequencenumber,thevalueisthesameastheoneinSHIP_APPsentfromPVN.CreatedbyID:BDIF(whenBDIFstagesCreatedUpdatedby0Datais5DuplicateESN.Canbe30Datais5DuplicateESN.Canbe3ESNisduplicatewithoneprocessforamonth,(canbemultipleblocks)ESNisduplicatewithpreviousmonths,evenitisnotpairedby ESNisduplicatewithpreviousmonths'anditisalreadypairedby ESN8InvalidCannotprocessdataRECORDhasbeenRECORDhasbeenRECORDisbeingProvisioninghasbeenupdatedwithdatainthisrecordProvisioninghascompletedprocessingcycleonthisstagedrecordNotifyESNAPPJMSMessageInterfaceInterfaceJMSUsageIfPVNfindsanyerrorintheEsndata,itwillmarktheerroneousrecordsaserrorbyerrorcodesinthestagingtable.ProvisioningwillnotifyBDIFESN_APPJMSmessage.Byreadingstagingtable,BDIFwilldothefollowing:GenerateandforwordESN_ERRtohardwaremanufacturewithalltheinvalidESN.GenerateandforwardESN_SENTtowithallthevalidESN.CleanupPVN_STAGE_ESNInterfaceDefinitionXMLschemaElementElementDataCreationdate,YYYY-MM-MessagesequenceESN_APPwillalwaysgenerateanewsequencestring,thissequencenumberwillbeusedbyBDIFtoidentifythebatchof Feedname:Feedsource:Feedtype:CountofdetailFirstpartisvenderpartyid,secondpartwillbe‘_’asaconnector,thethirdpartisdunsnumberElementDataResult–meansnoinvalid–oneormoreinvalidErrorErrorExtensionResultExtensionResultElementExtensionResultElementExtensionResultElementExtensionResultElementInterfaceDefinitionReferto<BDIF_PVN_notificationReceived.xsd>andCARRIER_ESNfileBatchCARRIER_ESNStagingInterfaceInterfaceUsageMonthlyProjectedthebatchtobe60KRecordsin5years,whichwillbe20MbytesinsizeBDIFwillloadtheESNdatafromcarrierESN_ERRintoPVNstagingtable,andnotifyPVNviaJMSmessagewhentheloadisdone.PVNwilltreatalltheESNinthisfeedasinvalid.PVNwillthensentoutESN_APP.BDIFshouldtreatitastheoneinInterfacePVN_STAGEDatabaseThistablewillcontaintheheaderdescriptionforeachfeed.ThistablewillcontainthedataforESN_APP,ESN_ERR,CARRIER_ESN,andCARRIERESNERRfeedThistablewillbealookup