參考研發(fā)經(jīng)理

1、AgendaDBA release 1 progress update (Jessie/Hank, 30 min)PI/PV PlanNPT&Rampup build/FDT development planDI/PV PlanChurn in items Plan2. DBA release 1 project risk (Jessie, 30 min)next step LSI/WR delivery expectation3. DBA release 2 topics (Frank, 100 min)L2 Switch, Ethernet OAM functionalitiesGPS s

2、olution4BRD implementation options 4BRD DE review4. DBA evolution view (Frank, Huaijun, 60 min)Direct connect to RRUSPath to “DUC”O(jiān)AM evolution to manage RRUS Anaheim E2E wk31 2011IPTL: Kim Montange PM: Jessie Li/Hank Hou / Kang NaThis weekLast update (N/A)Project Scope :A CDMA product CR project, s

3、upporting a 6C3S BTS digital module by LSI ACP system (BTS 652A/662A/602A HW & FW & doc)Main Achievements :HW SW integration:Achieved build in CSM8700 1st E2E call on wk31.5. Activity completed on timeKey technical issues: 5 left, all related to LSI/WR, will have impact to product verification. (Det

4、ails in another page)HW PI/PV/SafetyPI/PV deriskEMC: dont meet class B near 190MHz, 750MHz, solution is to change faceplate to stainless steel (to be verified by wk33.2). Unit price will increase several dollar. Thermal: design derisk test passed with 1 fan fail.More test is planned wk33 for higher

5、confidence; Mechanical: vibration test planed in wk33 to avoid transportation failure;PI/PV strategy agreed by design & PI/PV/safety team: test with DO diag load & voice debug load for formal PI/PV/safety test;Schedule (wk35-wk43)Critical TC wk39Priority: 602A/652A/662A Preparation: Test plan review

6、ed, approval planed in wk33.Lab preparation in progress, on track (with M3 shortage risk);Tech Rating EC Plan still on wk41;Dependencies: HW PI/PV/safety critical TC done by wk39 & DO diagnostic load integration done by wk34 & HRCI lock down by wk33 & HW DVT by wk36; Excluding SW PV;NPT build / Ramp

7、up buildNPT build wk42 & Ramp build proposal ready (fcst 1700 DBA by Q4)Max production from 11wk45, if the yield rate in wk42-wk44 meet target.HW designer on site support on NPT build?ICT / FDT developmentICT: decision point on wk37; depending on EMC result at least;FDT: Drop 1/2/3 by wk36/wk41/wk47

8、 for B6/NPT/ramp build; Wk38 is decision point to see whether could pull in to have all FDT by wk41-44 (if not, will plan manually test); FDT fixture plan tbc;DE LEVEL : 13.9 M$Anaheim E2E wk31 2011IPTL: Kim Montange PM: Jessie Li/Hank Hou / Kang NaThis weekLast update (N/A)Project Scope :A CDMA pro

9、duct CR project, supporting a 6C3S BTS digital module by LSI ACP system (BTS 652A/662A/602A HW & FW & doc)Main Achievements :SW DT/SW DI/System PV:DT progress on track, Total: 1465, Passed: 927.Base: Plan: m:App: Code submission, plan to submit to B1804 on wk37. DI (wk35-wk46), Total: 532 TCs Design

10、 soaking and Capacity/Performance Test (wk41-wk48): Total: 182 TCsPV (wk38-wk01), Total: 850 TCsLab in CGC setup in progress, depends on B5 delivery date (on track)CR reduction plan draft readySystem (FIT/Modem Test/LAT)Availability prediction done: FEMECA FIT test start from wk37 on Beta build. LAT

11、 1st test pass: wk43-wk49Release 1 Churn in (VMFRM, 1xadv ph2)Combine VMFRM, 1xadv Ph2 DI/PV activity:2 wks plus for milestone achieved on DBU-XMU:1st Markov call on DBU-XMU in wk42; 1st Markov call on DBA-XMU on wk44;PV TF on DBU-XMU on wk3; PV TF on DBA-XMU on wk5PV TD on DBU-XMU on wk6; PV TD on

12、DBA-XMU on wk8BTS SW staffing right now, and detailed planning for integration will be ready for wk39TG4 is gated by LAT, but not gating ready for STITC/FIT lab.Lab preparation: over budget due to RRUS B25 triple the price comparing to DBU-XMU team in early this year. Now lab setup required 95.7K$ (

13、DE planed: 4.2K capital, 55.2K expense)DE LEVEL : 13.9 M$1xRTT call, M3/RRUC1xRTT call, VMFRM1xadv call, M3/RRUC1xadv call, VMFRMIssues Management HW PI/PV/Safety ScheduleHW PI/PV test strategyDepends on 1st cycle test result, if result negativeand new technical riskidentified, rerun in 2nd cycleDis

14、position:1. PI/PV will have a full cycle DBA test, and if the test result meet specification, pass the Tech Rating EC with condition on DBA2242. After DO application porting to DBA, will run cycle 2 TC. This part is budgeted in EVDO on DBABackupCR Reduction Plan IVDI in middle, PV startDI first runP

15、V in middleTG3,early dropTG4Key Factors Used for Integration PlanningKey factors usedValue1x adv Ph1 ActualDI TC execution rate (#/person. week)10DI de-risk TC failure rate0.3DI TC failure rate0.20.1PV de-risk TC failure rate0.30.3PV regression TC failure rate0.15PV TC failure rate0.140.14Design Cap

16、/Perf CR resolution rate0.5DI CR resolution rate0.6Sanity CR resolution rate0.5FIT, LAV, Modem Testing CR resolution rate0.5TE CR resolution rate0.8PV CR resolution rate0.45Average CR turnaround rate0.510.4What we should do on DBA next Phase Frank Gao2011-8-1 v1.0DBA Next Phase TAsksVoice: 1x Adv Ph

17、ase2.0 Data: DO application on DBAGPS Hold over and CRL2 switch4BRDEnhancement featuresVoice and Data application1x Adv Phase2.0Pending to 1xAdv Project progressS/W portingDO on DBAPending to DOM-E project progressS/W portingLITR FPGA firmwarePrevious DOM 600 Hz Interrupt (forward link power measure

18、ment) strategy does not work due to multi-core communication latency LITR FPGA actively programs the DO SC core memory to wake up CPU as a notification NPU firmware NCA channel for inter-core traffic communicationLayer-3 IP routing as consolidated backhaul solutionGPS holdover and CR has provided so

19、lution as GPS receiver daughter board to support multiple GPS standardsMulti-variants OCXO for 24hr/72hr/7days hold over requirementMaster and slave are identical minus the pluggable GPS receiver option as the CR wayProgress:New card form factor keeps unchangedPhase-noise is over 58 dB on some frequ

20、ency pointThe first demo card delivery to E/ is target to SepL2 switchTo support BTS Daisy-chainDownstream BTS connectivityCEEMs DOM Card Backhaul connectionSIU/RAD functionality integrationQoSVLAN tagging, DHCPEthernet OAMNPU and S/W development4 Brach receive diversity4BRD AdvantageEnables much be

21、tter phone-to-network radio receptionUtilizing multiple replicas of the same signal improves transmission performance3S Sprint requirement with 4BRD with a cost effective solution and within acceptable timelines4BRD dependenciesOn DBA: Baseband (Chipset) : Voice 8700; Data : 6850On CEEM: Pluggable 1

22、xAdv; Pluggable DOM-300External Multiplexing Unit (XMU) for Radio connectivityRadiosBNet radios RRUS RBB: 2Tx4Rx_1CPRIA2 (receive only) radiosPotential on Platform 5 radios4BRD considerationDBA is capable of 3C3S at 4BRD, with CEEM, it can support 6C3S at 4BRDDBA to XMU radio link is the key point t

23、o implement 4BRDDBA features 6 physical links with 2.5 Gbps rate per link. XMU just provides 2 linksOptions on the radio link (two physical links) to support 4BRD: A: HSSL, limits to 3C3S capacityB: CPRI, limits to 4C3S capacity In case to support 6C3S 4BRD, HSSL solution needs 4 physical links; CPR

24、I needs 3 physcial links4bRD implementationHSSL variantFirmware and m S/W change to support BB data groupingLow risk/effort CPRI variantFirmware and Base/ m S/W need changeFunctionalityPure CPRI IF is not a big job IQ sampling for data rate changeCDMA channelization and framingAGC; Rise-over-Thermal

25、(RoT)Carrier-Sector mappingTiming delay solution need to be consideredS/W workLink driver and related OAMXMU is based on Linux Need to engage XMU team ASAP to lock down the functionality partition4BRD Options4BRD DE4BRD over CPRI4BRD over HSSLHC- FPGA515.8K156.9KHC- BTS2541.7K1583.3KHC- OAM262.4K152

26、.7KHC- System976.1K849.8KHC- PV408.9K395.8KExpense1105.6K868.0KCapital00RND overhead1376.2K900.5KNon-RND1200K1200KTotal8386.7K6107.1KBackupExpected Gain from 4BRD m CSM6850In this case, the gain is easier to be expressed in capacity, i.e., uplink throughput, than in link budgetData: Courtesy of m In

27、c.LITR HSSL versionLITR CPRI ProposalRICM supported with OSE Shim layer + LINX on VxWorks.RICI for CPRI link supervision, Control and delayCPRI DBA - RICIECP/HDLC. Carries BCN, ACN, QMIP + RICI XMU functions (control plane)VMFRM3OAMTranslationCDMA Carrier-SectorMgmt SWRBS CarrierMgmt SWResource Hand

28、ling SWRUS eqpmtMonitoring SWXMU RICRICRRICMACNQMIPBCNDBAXMURURICIECPCPRIL2 & L1If power management moves to DBA, then VMFRM moves to DBA.Here assumption that Power Management stays on XMU to minimize Architecture impact/adding VMFRM onto DBAXMU data path processingAlcor FPGA impactsRequire new Alco

29、r FPGA s/w load to support CPRITwo loads 1) HSSL, 2) CPRICurrent RBS solution does not support different Firmware versions for one H/W module typeEither:Develop new RBS s/w management to support configurable s/w load for one KRCOr, use Special Delivery/ upgrade process to deliver new CPRI s/w for th

30、e XMU KRCDBA Evolution view Frank Gao2011-8-1 v1.0ScopeRUS/RRUS Native connectionTo be “DUC” DO solution evolutionOAM synergyNative connection to Rus/rrusA long term goal, BNET Radio module (RUS/RRUS) can be directly connected to DBA for CDMA serviceDBA can provide 6 CPRI links at most, but no plan to support DUL connectivityvMFRM is still necessary for radio S/W RUS/RRUS OAM functionality (in OSS-RC) need to be populated to ACPBTS S/W CPRI variant for 4BRD is very valuable step towards this goalFrom DBA to DUCDUC is DB