FCC ID: PD97262WW WWAN Module Adapter Card

IntelModel7260M2NAand7262M2WW UserGuide Revision1.2,Feb2015 DocumentNumber:N/A RevisionHistory RevisionHistory RevisionNumber Description 1.0 1.1 1,2 Initialversionofthedocument Revisetoaddmodel7260M2NA Revisetoaddmodel7262M2WW RevisionDate 17Dec2012 Nov2014 Feb2015 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 2/60 RevisionHistory Contents 1 2 Introduction................................................................................9 Software Framework.............................................................12 2.1 Driver Installation...................................................................12 2.1.1 General Considerations........................................................12 2.1.2 Intel High Speed Modem Driver (ecm200)..................14 2.1.2.1Client offset configuration..................................................19 2.1.2.2Static IP Address Configuration........................................21 2.1.3 Comneon High Speed Modem Driver..............................25 2.1.4 Flash USB driver and FTDI Driver....................................28 2.1.5 Prolific Serial to USB Driver................................................29 2.2 2.3 LTE debug UART configuration..........................................30 System Trace Box..................................................................33 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 3/60 RevisionHistory 2.3.1 Setup and Configuration......................................................33 2.3.1.1Entering AT Commands.......................................................33 2.3.1.2Board Configuration and required AT Commands.....34 2.3.2 Connecting the UE..................................................................35 2.4 AT Commands Examples.....................................................37 3 Test Cases.................................................................................42 3.1 Protocol Test (CMW500)......................................................42 3.1.1 CWM 500 Firmware...............................................................42 3.1.2 Test Scenario...........................................................................44 3.1.3 AT Commands..........................................................................45 3.1.4 The Data Application Unit....................................................45 4 5 Regulatory Notice...................................................................50 Abbreviations / Terminology..............................................51 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 4/60 RevisionHistory Appendix A...................................................Definitions/Explanations

.......................................................................................................53 Figures Figure 1. Location of the Prolific serial to USB driver, the Flash USB driver and the FTDI diver within the flash tool folder..................................................................13 Figure 2. Use the already installed driver....................15 Figure 3. Install the driver again.....................................16 Figure 4. The network modem and four COM ports are now appearing at the device manager.............16 Figure 5. Open the network connections dialog. Win XP : Start:Settings:NetworkConnectios. A new network device did pop up. It is not yet connected. .................................................................................................17 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 5/60 RevisionHistory Figure 6. On Win7: Select Start:Control Panel:Network and Sharing Center followed by Change adapter settings.............................................18 Figure 7. Open the properties dialog of the new network device (right click)...........................................18 Figure 8. Select the configuration dialog......................19 Figure 9. Set the client offset to 1 and press OK..20 Figure 10. Press OK to save these settings. Otherwise these settings get lost...............................20 Figure 11. Open the Internet Protocol TCP/IP settings..................................................................................23 Figure 12. Set the static Network IP and press OK..24 Figure 13. To close the properties dialog and save the settings press OK...................................................25 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 6/60 RevisionHistory Figure 14. Congratulations. Your ecm200 driver and its IP connection are now properly configured......25 Figure 15. Use the already installed driver..................26 Figure 16. Install the driver...............................................27 Figure 17. Comneon suspend and six COM ports are now appearing at the device manager.....................28 Figure 18. USIF1 Device Manager Prolific USB-to-

Serial COM Port..................................................................30 Figure 19. Putty configuration..........................................32 Figure 20. CMW 500..............................................................42 Tables Table 1. Terminal Port Settings........................................31 Table 2. AT Commands trace box support..............Error!

Bookmarknotdefined. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 7/60 RevisionHistory Table 3. Terminal Port Settings........................................38 Table 4. AT Commands to check ARM software version...................................................................................38 Table 5. AT Commands to Register on the Network 38 Table 6. AT Commands for an Incoming Call..............38 Table 7. AT Commands for an Outgoing Call..............39 Table 8. AT Commands for SMS Management............39 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 8/60 RevisionHistory 1 Introduction ThisdocumentprovidesabriefdescriptionoftheNGFFCarrier Boarddevelopmentkit.Including:

- HardwareinterfaceswithFIHboard

- NGFFCarrierBoardUserGuideV2.0 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 9/60 RevisionHistory Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 10/60 RevisionHistory Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 11/60 RevisionHistory 2 2.1 2.1.1 SoftwareFramework DriverInstallation GeneralConsiderations Thetwodifferenttestanddebugconfigurationsalwaysrequirea WinPCwhereuptofivedifferentdriversmustbeinstalled accurately. Thisare:

1. theIntelHighSpeedModemDriver(ecm200), 2. theComneonHighSpeedModemDriver, 3. theProlificserialtoUSBdriver(partoftheflashtool folder), 4. theFlashUSBdriver(partoftheflashtoolfolder)and 5. theFTDIdiver. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 12/60 RevisionHistory Figure1.LocationoftheProlificserialtoUSBdriver,theFlash USBdriverandtheFTDIdiverwithintheflashtool folder. Pls note that Win does not always complain if the drivers 4 to 5 are not installed. If one of these drivers is missing flashing problems are occurring. TheARMsoftwareandLTEfirmwarereleasesarelinkedto individualdriverrevisionnumbersthatwereusedforrelease testing.TheyweretypicallypublishedtogetherwiththeARM softwareandtheLTEfirmwarehere:

http://wiki.imu.imc.local/XG716_LTE_CV_Setup_versions Thelatestdriverscanbefoundhere:

\\musdsara001.imu.imc.local\SW_builds\xmm6360\tools Orifsomethingismissinghere:

\\musdsara001.imu.imc.local\SW_builds\xmm7060\Release\Tools Whichissimilarto Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 13/60 RevisionHistory M:\Software\XMM7060_toolsatIMCDRS FlashTool:

\\musdsara001.imu.imc.local\SW_builds\xmm6360\tools\flashtool Socmondll:

\\musdsara001.imu.imc.local\SW_builds\xmm7060\Release\Tools\Socmondll\socmondll_100.150.001.dll 2.1.2 IntelHighSpeedModemDriver(ecm200) Taketherecommendeddriver,seeSubsec.2.1.1,

(foldere.g.WMC_ecm200_3.61.0)andfollowthe instructionsfromtheinstallationwizard. EnabletheIPforwarding:runthe sriptenable_ip_forwarding.regfrom:

\\musdsara001.imu.imc.local\SW_builds\xmm7060\Release\Tools\Intel_High_Speed_Modem Hint:CopythefiletothelocalPCandthenrunitwithroot privileges. NowconnectthecabletotheUSBHSconnector. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 14/60 RevisionHistory WinXPasksnowitstypicalquestionsandgetsthecommon answersseebelow.Win7doesnotaskandloadsthedriver automatically. Figure2.Usethealreadyinstalleddriver. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 15/60 RevisionHistory Figure3.Installthedriveragain. Figure4.ThenetworkmodemandfourCOMportsarenow appearingatthedevicemanager. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 16/60 RevisionHistory Nowopenthenetworkmanagerandconfigurethe networksettingsofthemodem. Figure5.Openthenetworkconnectionsdialog.WinXP:

Start:Settings:NetworkConnectios.Anewnetwork devicedidpopup.Itisnotyetconnected. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 17/60 RevisionHistory Figure6.OnWin7:SelectStart:ControlPanel:Networkand SharingCenterfollowedbyChangeadapter settings. Figure7.Openthepropertiesdialogofthenewnetwork device(rightclick). Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 18/60 RevisionHistory 2.1.2.1 Clientoffsetconfiguration. ThismustbedonebeforetheIPsettings.Iftheorderisflippedthe IPsettingsgetlost. Figure8.Selecttheconfigurationdialog. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 19/60 RevisionHistory Figure9.Settheclientoffsetto1andpressOK. Figure10.PressOKtosavethesesettings.Otherwisethese settingsgetlost. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 20/60 RevisionHistory 2.1.2.2 StaticIPAddressConfiguration ThegivenexampleIPnumberatFigure12isfora simplifiedtestanddebugsetup,seeError!Reference sourcenotfound.,wheretheoctaveorjavaclient runsontheWinPCthatalsocarriesallnecessaryWin driversandisconnectedtotheDUT.Theecm200 driverrunsinasubnetthatisonlyvisiblefromthisPC. Thecompletesetup,seeError!Referencesourcenot found.,consistsoftestPCsthatwereprovided togetherwithrecommendedIPsettingsforthe ecm200driver.Thestaticroutesettingswereset typicallyITsystemwide. IncasetwoPCswereusedtorunthetests,atestPC IncasetwoPCswereusedtorunthetests,atestPC withthedriversandadesktopPCthatcarriesthe OctaveortheJavaclientastaticroutemustbesetat Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 21/60 RevisionHistory thedesktopPC.Theexamplebelowhelpstofind properstaticroutesettings:

testPCwithstaticIP:10.1.0.126 ecm200clientattestPCwithIP:172.16.126.1

(clientoffsetsetto1) runasrootatthePCwheretheOctaveisrunning on. routeprint#readoutroutesettings routeadd172.16.126.0mask255.255.255.0 10.1.0.126 testtheconfiguration:

ping172.16.126.1#responsefromtheecm200driver ping172.16.126.2#responsefromthebootedLTEIP block(L1CC) ReopentheNetworkConnectionPropertiesDialog. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 22/60 RevisionHistory Figure11.OpentheInternetProtocolTCP/IPsettings. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 23/60 RevisionHistory Figure12.SetthestaticNetworkIPandpressOK. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 24/60 RevisionHistory Figure13.Toclosethepropertiesdialogandsavethesettings pressOK. Figure14.Congratulations.Yourecm200driveranditsIP connectionarenowproperlyconfigured. Ifdesireditisnowalsopossibletorenamethe networkdevicefromWirelessConnection2to somethingmoreconveniente.g.ecm200+IPaddress. 2.1.3 ComneonHighSpeedModemDriver Taketherecommendeddriver,

\\musdsara001.imu.imc.local\SW_builds\x mm6360\tools\usb_drivers See also SMS02534274: Pleaseuse3.46 Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 25/60 RevisionHistory versionandnotWMC_comneon2_3.55.0,seeSubsec. 2.1.1,(folderComneon_High_Speed_Modem_Driver) andfollowtheinstructionsfromtheinstallation wizard. Now connect the cable to the USB-HS connector. Win XP asks now its typical questions again and gets the common answers, see below. Win 7 does not ask and loads the driver automatically. Figure15.Usethealreadyinstalleddriver. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 26/60 RevisionHistory Figure16.Installthedriver. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 27/60 RevisionHistory Figure17.ComneonsuspendandsixCOMportsarenow appearingatthedevicemanager. Congratulations,yourdriverinstallationhasfinished successfully. 2.1.4 FlashUSBdriverandFTDIDriver ThesedriversaremandatorytoflashnewARMsoftwareandLTE firmwareimagesatthemodemboard.Taketherecommended Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 28/60 RevisionHistory drivers,seeSubsec.2.1.1,(flashtoolsubfolder)andfollowthe instructionsfromtheinstallationwizards. Note:

Ifthisdriversarenotinstalledcorrectlyinstabilitiesat theflashprocessareoccurringwithoutsubstantialerror informationfromWinXPorWin7. 2.1.5 ProlificSerialtoUSBDriver TheProlificdriverismandatorytoaccessallmodemboardUART

(USIF)ports.Taketherecommendeddriver,seeSubsec.2.1.1,

(folderProlificDriver)andfollowtheinstructionsfromthe installationwizard. ConnecttheUSBcabletothedesiredUSIFportandcheckthatthe COMportappearscorrectlyintheWindevicemanager.

(Win:Settings:ControlPanel:SystemProperties:Hardware:Device Manager.ThisisquitesimilartofindatWinXPandWin7.) Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 29/60 RevisionHistory Figure18.USIF1DeviceManagerProlificUSBtoSerialCOM Port 2.2 LTEdebugUARTconfiguration Afterthepreliminarysetting,runanyATterminalapplication(e.g. HyperTerminal)onyourPCscommunicationport,withthe followingsettings. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 30/60 RevisionHistory Table1.TerminalPortSettings Datarate DataBits Parity StopBits FlowControl 115200bps 8 N 1 HW onUNIXxtermusethiswithuucp:

%docing station serial port, uucp chown uucp /dev/ttyUSB0 cu -l /dev/ttyUSB0 -s 115200 Ifputtyhttp://www.putty.orgisusedthislooks likethis:

Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 31/60 RevisionHistory Figure19.Puttyconfiguration. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 32/60 RevisionHistory 2.3 2.3.1 2.3.1.1 SystemTraceBox SetupandConfiguration EnteringATCommands TheATcommandsmentionedbelowmustbesenttotheCOM portthatcorrespondstothe IntelMobile(USB3)COMportincasetheecm200 driverisusedor totheCOMportthatcorrespondstotheComneon HighSpeedModem,seeError!Referencesourcenot found.. TheCOMportthatcorrespondstotheUSIF1USBport,seeError!

TheCOMportthatcorrespondstotheUSIF1USBport,seeError!

Referencesourcenotfound.mayalsowork. Theudp2ATservercanbeusedtoenterlocalATcommandsfrom Theudp2ATservercanbeusedtoenterlocalATcommandsfrom remotelocations,seeSubsec.Error!Referencesourcenotfound.. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 33/60 RevisionHistory 2.3.1.2 BoardConfigurationandrequiredATCommands Resettheboardinawaythatisbootingfromtheflash Enabletracingusing:at+xsystrace=0,"lte_l1_sw=4"

Resettheboardagaininawaythatisbootingfrom theflash Nowtheinitializationatcommandstoswitchto ServiceMode(thatisthemodetouseRCTTH)canbe sentifneeded:

ARMforInc2.8:at@ecal:at@ecal_init():

ARMforInc3.0:at@ephy:smon() Note:PleasecheckwiththeprovideroftheARM imagewhichcommandsarevalidfortheactual build!!!

TheATcommandsbelowaremandatorytoenabletracing:

a. Enabletracingatallsources:at+trace=1;

Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 34/60 RevisionHistory b. RoutetracesthroughUE's"OCTBlock",which createstheISTPformat:at+xsio=3;

c. Selectthetracesfromspecificsources,use at+xystracecommand.Forexample,toconfigure thetracesfromspecifictoselectONLYthe3g_sw traces:at+xsystrace=0,"3g_sw=1",,"oct=4"

d. makesureyourSIMisnotwaitingforenteringa PIN:at+cpin?Ifitis,sendthePINatat+cpin=<sim pinnumber>

e. makesure,the3Gprotocolstackissendingtraces:

at+cops=0;(thiscommandtriggersthephoneto

(re)registertothenetwork) 2.3.2 ConnectingtheUE 6. ConnecttheUEtothePCasdescribedinsection Error!Referencesourcenotfound.. 7. FindthecomportinwhichUEisconnectedusing Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 35/60 RevisionHistory 7. FindthecomportinwhichUEisconnectedusing comtesttool.Runthecommandcomtestl.Itwilllist theports.Carefullyevaluatetheportfortracingand portforcontrol. 8. TocheckwhetherPCisconnectedtoUEproperly,try connectingthecontrolportwiththeterminal emulatorandsendATcommand,Iftheresponseis OK,UEisconnectedsuccessfully.Thiscanbedonevia ATConsoleinSystemTraceTool. 9. SendthebelowATcommands:

a. Enabletracingatallsources:at+trace=1;

b. RoutetracesthroughUE's"OCTBlock",which createstheISTPformat:at+xsio=3;

c. Selectthetracesfromspecificsources,use at+xystracecommand.Forexample,toconfigure Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 36/60 RevisionHistory thetracesfromspecifictoselectONLYthe3g_sw traces:at+xsystrace=0,"3g_sw=1",,"oct=4"

d. makesureyourSIMisnotwaitingforenteringa PIN:at+cpin?Ifitis,sendthePINatat+cpin=<sim pinnumber>

e. makesure,the3Gprotocolstackissendingtraces:

at+cops=0;(thiscommandtriggersthephoneto

(re)registertothenetwork) 2.4 ATCommandsExamples Afterthepreliminarysetting,runanyATterminalapplication(e.g. HyperTerminal)onyourPCscommunicationport,withthe followingsettings Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 37/60 RevisionHistory Table3.TerminalPortSettings Datarate DataBits Parity StopBits FlowControl 115200bps 8 N 1 HW ATCommandtocheckARMSoftwareversion Table4.ATCommandstocheckARMsoftwareversion CommandsentbyDTE at+xgendata Registeronthenetwork(GSM/UMTS) ResponseofDCE Description The device will reply with the running ARM software version Table5.ATCommandstoRegisterontheNetwork CommandsentbyDTE ResponseofDCE Description AT+XRAT=1,2 AT+COPS=0 AT+CREG?

AT+COPS?

IncomingVoiceCall OK OK

+CREG:0,1 OK selectradioaccesstechnology:1=GSM/UMTSDualmode;2=UMTS Registerthephoneonthenetwork Verifyregistration

+COPS:0,0,"AT&T",0 Readoperatorname Table6.ATCommandsforanIncomingCall CommandsentbyDTE DCEResponse Description ATA OK Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 38/60 RevisionHistory OutgoingVoiceCall Table7.ATCommandsforanOutgoingCall CommandsentbyDTE DCEResponse Description AT AT+CLIP=1 ATD+862161019000;

ATH SMSManagement OK OK OK OK ActivationofCallerlineID presentation Outgoingvoicecall Voicecallisacceptfromnetwork Hangup Table8.ATCommandsforSMSManagement CommandsentbyDTE DCEResponse Description Setthetextmodeastheformatthatwillbeused.Tobesetbeforeofthefirst operation SetthePDUmodeastheformatthatwillbeused.Tobesetbeforeofthefirst operation AT+CMGF=1 AT+CMGF=0 OK OK AT+CMGS=0171112233<CR>

CMGS:<mr>[,<scts>]

Thisisthetext<ctrlZ>

CMGS:<mr>[,<ackpdu>]

OK or CMSERROR:<error>

OK ifPDUmode(+CMGF=0):

+CMGS=<length><CR>PDUis given<ctrlZ/ESC>

Testcommand AT+CMGS=?

Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 39/60 RevisionHistory Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 40/60 RevisionHistory Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 41/60 RevisionHistory 3 3.1 TestCases ProtocolTest(CMW500) Figure20.CMW500 IngeneralitneedstobecheckedthatCMW500setupare identicallytothereference.Thecomponentstobecheckedare:

Thetestscenarioconfigurations(xmlfiles)and Thefirmwareversionsforthetesterhardwareitself. 3.1.1 CWM500Firmware ThefirmwareversioncanbecheckedandmaintainedintheR&S VersionManager.Basicinformationonsoftwareupdateand installationwiththeR&SVersionManagerisgiveninthe"R&S Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 42/60 RevisionHistory CMW500ProtocolTesting"quickstartguide(1202.3857.62).The R&SVersionManagerhelpprovidesmoredetailsonR&SVersion Managerfunctionsandhandlingofsoftwareunits.Thisdocument assumesthatallrequiredsoftwareunitscanbeinstalledbythe user. TheR&SVersionManagercanbeopenedviatheSTARTmenu:

Onceopenedtherearetwowaystoverifysimilarityoffirmwareversions:

byhandviasteppingthroughthelicenseoptionsor byexportingthefirmware(softwarestatus). Thepictureshowstheversionmanagerwiththesteppingthrougheachfirmwarelicense:

Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 43/60 RevisionHistory Thenextpictureshowsthemenufromwhichthestatusexportcanbecalled:

Afterthisapopupwindowappearswiththreepossiblechoices.Onlythetoponehastobeselectedas showninthepicture:

Afterthisthelocationofthestatusexportfileneedstobechosen.Oncedonethefilecanbecomparedto thereferencefilewhichislocatedunder:

..\version\lab2\lab2_cfg.html 3.1.2 TestScenario Thetestscenarioml_002EPSBearerSetupisusedforthissetup andiscontainedbytheSWoptionKF500withMLAPIExample Scenarios. Thepathtotheconfigurationdirectoryisfollowing:

c:\Rohde Schwarz\Scenarios\16.6_callSetup_1\APPL\MLAPI\LTE_SAMPLE_S CN\1.0\ml_002\msg Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 44/60 RevisionHistory ThedirectorymsgispartoftheCDKdeliveryandcontains severalxmlfiles.Ithastobenotedthatthexmlversionofthexml filesneedstobecomplianttotheinstalledtesterfirmware. Otherwisestrangeerrorsoccurduringtestcaseexecution!

http://www2.rohde-

schwarz.com/en/products/test_and_measurement/m obile_radio/CMW500-|-Demo-|-48-|-5420.html 3.1.3 ATCommands NetworkattachinCallBoxMode,LTEband7. at+xact=6,2,1,107 at+cgdcont=1,"IP",www.rohde-schwarz.com ThisgivesOKiftheSIMcartisinsertedaccurately. at+cops=1,2,"00101",7 3.1.4 TheDataApplicationUnit InstalltheDataApplicationUnit Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 45/60 RevisionHistory TheDataApplicationUnit(DAU)packagehastobeinstalledon theCMW. IncasetheDAUhardwareispopulated,thesoftware(SW)should alreadybeinstalledaswell.Checkthisin"SetupSW/HW EquipmentInstalledsoftware". Beforeinstallation:

TerminatetheCMWBaseSWapplicationclosethe windowwithX Inthetaskmanagerkilltheprocess

"ComponentEnvironmentServer_2.5.exe". Installation:

InstalltheDAUSWpackage

"SetupCMW_DAU_Support(Release)V1.0.15.22"

directlyontheCMW. ReboottheCMWdevice. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 46/60 RevisionHistory ActivateDHCPinDataApplicationControl AftercompletestartupoftheCMWBaseSWapplication,follow thestepsbelowtoconfiguretheDAUforDHCP:

MakesureyourRouterisconnectedtothe"LANDAU"ETHportatthebacksideoftheCMW. OpentheSETUPmenuontherightside. OpentheDAUconfigurationviamenu:

DataAppl.ControlGotoconfig ConfiguretheDAUtouseDHCP Asshownonthescreenshot,chooselastcheckmark DHCPv4fromLAN(LANDAU)forIPv4AddressConfiguration ClosetheCMWBaseSW(ALT+F4)andstartitagainafterwardsbyaDoubleClickonthedesktop link"CMW1.0"

Aftertherestart,checkthe"DHCPStatus"inthesamewindow.AgreenlightindicatesthattheDAU couldacquireanIPv4addressviaDHCP. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 47/60 RevisionHistory SwitchingUPCfromPPC(SUW)toDAU InordertoletthescenariousetheUPC(=UplaneControl)onthe DAU(andnotasperdefaultonthePPC),twoXMLfileshaveto bereplacedinthetopology:

pipe.xml sequencer.xml, CopythesetwofilestoC:\Rohde Schwarz\Scenarios\16.6\APPL\MLAPI\rstopology\LTE\. NOTE:

Itisrecommendedtomakeabackupoftheoriginalfilesbefore. StarttheLTEscenario StarttheLTEscenarionow. DuringtheDefaultEPSBearerSetuptheUEwillgetanIPaddress whichwasacquiredbytheDAUbefore. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 48/60 RevisionHistory ManualDNSsettings OntheLTEhostwhichconnectstotheinternet,theDNSserverhastobeconfiguredmanually, becausetheDAUdoesnotyetsupportautomaticDNSprovisioning(askyourIT). IncaseofaLTEnotebookadapter,theDNSserverwillbeconfiguredontheIPpropertiespane:

Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 49/60 RevisionHistory 4 RegulatoryNotice Japanese Radio Law and Japanese Telecommunications Business Law Compliance. This device is granted pursuant to the Japanese Radio Law () and the Japanese Telecommunications Business Law () This device should not be modified (otherwise the granted designation number will become invalid) Manual Information to the End User :

The OEM integrator has to be aware the end user manual shall include all required regulatory information/warning as show in this manual. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 50/60 RevisionHistory 5 A AGPS AP B BB C CMOS CN D Abbreviations/Terminology AssistedGPS(GlobalPositioningSystem) ApplicationProcessor Baseband ComplementaryMetalOxideSemiconductor Comneon DigRFv4 DigRF3.09 DigitalRFinterfacev4(rmainlyusedfor4G) DigitalRFinterfacev3for(mainlyusedfor2G/3G) E ETM ESD F fps G GPIO GSM H EmbeddedTraceMacrocell Electrostaticdischarge FramesPerSecond Generalpurposeinput/output GlobalSystemforMobileCommunications USBHS HighSpeed.USB2.0(480MBit/sec) I J JPEG JTAG JointPhotographicExpertsGroup JointTestActionGroup Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 51/60 RevisionHistory L LDO LED M MIPI MMC(I) MPU O P PA PCL PMU PTI S Lowdropout(regulator) Lightemittingdiode MobileIndustryProcessorInterface MultimediaCard(Interface) Microprocessorunit PowerAmplifier PortControlLogic PowerManagementunit ParallelTraceInterface SDCard SecureDigitalCard SMTpinheader SurfaceMountTechnologypinheader SerialPeripheralinterface SMARTi4G SystemTraceMIPI SystemTraceTool Systemverificationboard Software TestAccessPort TestControlUnit UniversalSerialBus UniversalSerialInterface SPI S4G STMIPI STT SVB SW T TAP TCU U USB USIF Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 52/60 RevisionHistory AppendixA EvalBoard Lauterbach Definitions/Explanations specialprocessorsocketboardforXGOLD716componentverification SupplierofDebugandTraceenvironmentforXGOLD716(e.g.JTAG,ETM7/11,STMIPI) Modemboard MainpartofXMM7160platformhardware(seeError!Referencesourcenotfound.) XMM7160 RFEngine SMARTi4G Janusboard ProjectnameofIntelplatformwithkeycomponentXGOLD716 RFpartofplatform(RFtransceiver,Poweramplifiers,LNA,Filterbank,antennaswitchetc.). IntelRFtransceiverfor2G/3G/4G BoardwithSMARTiLUandSMARTiUE2 Carrierboard SMBneedsacarrierboardforoperation Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 53/60 RevisionHistory AppendixBRegulatoryStatements USAFCCRadioFrequencyExposure The FCC with its action in ET Docket 96-8 has adopted a safety standard for human exposure to radio frequency (RF) electromagnetic energy emitted by FCC certified equipment. The wireless adapter meets the Human Exposure limits found in OET Bulletin 65, supplement C, 2001, and ANSI/IEEE C95.1, 1992. Proper operation of this radio according to the instructions found in this manual will result in exposure substantially below the FCCs recommended limits. The following safety precautions should be observed:

Do not touch or move antenna while the unit is transmitting or receiving. Do not hold any component containing the radio such that the antenna is very close or touching any exposed parts of the body, especially the face or eyes, while transmitting. Do not operate the radio or attempt to transmit data unless the antenna is connected; this behavior may cause damage to the radio. Use in specific environments:

The use of wireless adapters in hazardous locations is limited by the constraints posed by the safety directors of such environments. The use of electronic devices equipped with wireless adapters on airplanes is governed by rules for each commercial airline operator. The use of wireless adapters in hospitals is restricted to the limits set forth by each hospital. ExplosiveDeviceProximityWarning Warning: Do not operate a portable transmitter (including this wireless adapter) near unshielded blasting caps or in an explosive environment unless the transmitter has been modified to be qualified for such use. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 54/60 RevisionHistory UseOnAircraftCaution Caution: Regulations of commercial airline operators and the FCC may prohibit airborne operation of certain electronic devices equipped with radio-frequency wireless devices (wireless adapters) including cellular devices because their signals could interfere with critical aircraft instruments. TheWirelessAdapterandYourHealth The wireless adapter, like other radio devices, emits radio frequency electromagnetic energy. The level of energy emitted by the wireless adapter, however, is less than the electromagnetic energy emitted by other wireless devices such as mobile phones. The wireless adapter operates within the guidelines found in radio frequency safety standards and recommendations. These standards and recommendations reflect the consensus of the scientific community and result from deliberations of panels and committees of scientists who continually review and interpret the extensive research literature. In some situations or environments, the use of the wireless adapter may be restricted by the proprietor of the building or responsible representatives of the applicable organization. Examples of such situations may include:

Using the wireless adapter on board airplanes, or Using the wireless adapter in any other environment where the risk of interference with other devices or services is perceived or identified as being harmful. If you are uncertain of the policy that applies to the use of wireless adapters in a specific organization or environment (an airport, for example), you are encouraged to ask for authorization to use the adapter before you turn it on. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 55/60 RevisionHistory REGULATORYINFORMATION USAFederalCommunicationsCommission(FCC) No configuration controls are provided for Intel wireless adapters allowing any change in the frequency of operations outside the FCC grant of authorization for U.S. operation. Intel wireless adapters are intended for OEM integrators only. If Intel wireless adapters are to be co-located with any other transmitter additional testing and/or approval by the FCC will be required. This wireless adapter complies with Part 15 of the FCC Rules. Operation of the device is subject to the following two conditions:

This device may not cause harmful interference. This device must accept any interference that may cause undesired operation. ClassBDeviceInterferenceStatement This wireless adapter has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This wireless adapter generates, uses, and can radiate radio frequency energy. If the wireless adapter is not installed and used in accordance with the instructions, the wireless adapter may cause harmful interference to radio communications. There is no guarantee, however, that such interference will not occur in a particular installation. If this wireless adapter does cause harmful interference to radio or television reception (which can be determined by turning the equipment off and on), the user is encouraged to try to correct the interference by taking one or more of the following measures:

Reorient or relocate the receiving antenna of the equipment experiencing the interference. Increase the distance between the wireless adapter and the equipment experiencing the interference. Connectthecomputerwiththewirelessadaptertoanoutletonacircuitdifferentfromthattowhichthe equipmentexperiencingtheinterferenceisconnected. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 56/60 RevisionHistory Consult the dealer or an experienced radio/TV technician for help. NOTE: The adapter must be installed and used in strict accordance with the manufacturer's instructions as described in the user documentation that comes with the product. Any other installation or use will violate FCC Part 15 regulations. CanadaIndustryCanada(IC) This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. Cet appareil se conforme aux normes Canada d'Industrie de RSS permis-exempt. L'utilisation est assujetti aux deux conditions suivantes: (1) cet appareil ne peut pas causer d'interfrences, et (2) cet appareil doit accepter des interfrences , y compris des interfrences qui peuvent causer desoprations non dsires de l'appareil. Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. Selon les rglements de Canada d'Industrie, cet metteur de radio peut seulement fonctionner en utilisant une antenne du type et de gain maximum (ou moindre) que le gain approuv pour l'metteur par Canada d'Industrie. Pour rduire lesinterfrences radio potentielles avec les autres utilisateurs, le type d'antenne et son gain devraient tre choisis de faon ce que la puissance Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 57/60 RevisionHistory isotrope rayonne quivalente(P.I.R.E.) ne soit pas suprieure celle qui est ncessaire pour une communication russie. SafetyApprovalConsiderations This device has been safety approved as a component and is for use only in complete equipment where the acceptability of the combination is determined by the appropriate safety agencies. When installed, consideration must be given to the following:

It must be installed into a compliant host device meeting the requirement of UL/EN/IEC 60950-1 2nd edition including the general provisions of enclosure design 1.6.2 and specifically paragraph 1.2.6.2 (Fire Enclosure). The device shall be supplied by a SELV source when installed in the end-use equipment. A heating test shall be considered in the end-use product for meeting the requirement of UL/EN/IEC 60950-1 2nd edition. INFORMATIONFOROEMsandHOSTINTEGRATORS The guidelines described within this document are provided to OEM integrators installing Intel wireless adapters in notebook and tablet PC host platforms. Adherence to these requirements is necessary to meet the conditions of compliance with FCC rules, including RF exposure. When all antenna type and placement guidelines described herein are fulfilled the Intel wireless adapters may be incorporated into notebook and tablet PC host platforms with no further restrictions. If any of the guidelines described herein are not satisfied it may be necessary for the OEM or integrator to perform additional testing and/or obtain additional approval. The OEM or integrator is responsible to determine the required host regulatory testing and/or obtaining the required host approvals for compliance. Intel wireless adapters are intended for OEMs and host integrators only. The Intel wireless adapter FCC Grant of Authorization describes any limited conditions of modular approval. The Intel wireless adapters must be operated only within countries that have been approved for operation. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 58/60 RevisionHistory Changes or modification to Intel wireless adapters by OEMs, integrators or other third parties is not permitted. Any changes or modification to Intel wireless adapters by OEMs, integrators or other third parties will void authorization to operate the adapter. SimultaneousTransmissionofIntelWirelessAdapterswithOtherIntegratedorPlugIn Transmitters Based upon FCC Knowledge Database publication number 616217 https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=33240&switch=P, when there are multiple transmitting devices installed in a host device, an RF exposure transmitting assessment shall be performed to determine the necessary application and test requirements. OEM integrators must identify all possible combinations of simultaneous transmission configurations for all transmitters and antennas installed in the host system. This includes transmitters installed in the host as mobile devices (>20 cm separation from user) and portable devices (<20 cm separation from user). OEM integrators should consult the actual FCC KDB 616217 document for all details in making this assessment to determine if any additional requirements for testing or FCC approval is necessary. 5.1.1 InformationToBeSuppliedtotheEndUserbytheOEMorIntegrator The following regulatory and safety notices must be published in documentation supplied to the end user of the product or system incorporating the Intel wireless adapter, in compliance with local regulations. Host system must be labeled with "Contains FCC ID: XXXXXXXX", FCC ID displayed on label. The Intel wireless adapter must be installed and used in strict accordance with the manufacturer's instructions as described in the user documentation that comes with the product. Intel Corporation is not responsible for any radio or television interference caused byunauthorized modification of the devices included with the wireless adapter kit or the substitution or attachment of connecting Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 59/60 RevisionHistory cables and equipment other than that specified by Intel Corporation. The correction of interference caused by such unauthorized modification, substitution or attachment is the responsibility of the user. Intel Corporation and authorized resellers or distributors are not liablefor any damage or violation of government regulations that may arise from the user failing to comply with these guidelines. Rev.1.0,September2012 HardwareUserGuide,DocumentNumber:N/A 60/60