throbber
as) United States
`a2) Patent Application Publication 10) Pub. No.: US 2016/0192403 Al
`GUPTAetal.
`(43) Pub. Date:
`Jun. 30, 2016
`
`
`US 20160192403A1
`
`(54) MECHANISM TO PROVIDE LTE VOICE,
`INTERNET AND EMBMSSERVICES OVER
`ETHERNET FOR CONNECTED HOME
`ARCHITECTURE
`
`(71) Applicant: QUALCOMMIncorporated, San
`Diego, CA (US)
`
`(2006.01)
`(2006.01)
`
`HOAW 12/06
`HOAL 12/18
`(52) U.S. CL.
`CPC wee HO4W 76/002 (2013.01); HO4E 12/18
`(2013.01); HO4L 63/166 (2013.01); HO4L
`63/0876 (2013.01); HO4W 12/06 (2013.01);
`HO4W 84/12 (2013.01)
`
`(72)
`
`Inventors: Siddharth GUPTA, San Diego, CA
`(US); Rohit TRIPATHI, San Diego, CA
`(US); Kuo-Chun LEE, San Diego, CA
`(US); Sivaramakrishna
`VEEREPALLL,San Diego, CA (US);
`Tyler Byron WEAR, San Diego, CA
`(US); Vaibhav KUMAR,San Diego,
`CA (US)
`
`(21) Appl. No.: 14/586,878
`(22)
`Filed:
`Dec. 30. 2014
`,
`o_—
`Publication Classification
`
`(51)
`
`Int. Cl.
`HO4W 76/00
`HOAL 29/06
`
`(2006.01)
`(2006.01)
`
`(57)
`
`ABSTRACT
`
`A method, an apparatus, and a computer program product for
`communication ina network. The apparatus sends a multicast
`message to a network device. The multicast message facili-
`tates discovery of an unknown IP address of the network
`device. The apparatus determines whether a first response
`message is received from the network device in response to
`the multicast message and determines the IP address of the
`network device from the first response message whenthefirst
`response messageis received from the network device. The
`apparatus establishes a secure connection with the network
`device using the determined IP address. The apparatus sends
`a link status check message to the network device to detect a
`failed end-to-end link between the apparatus and the network
`device.
`
`Evolved Packet
`System
`oN
`
`User
`Equipment
`
`E-UTRAN
`104
`
`106
`
`MME
`
`
`
`
`
`
`
` PDN
`
`
`
`108
`
`Serving
`Gateway
`
` Gateway
`
`.
`‘.
`
`Other
`eNodeBs
`
`MBMS GW
`
`BM-SC
`
`APPLE 1008
`
`1
`
`APPLE 1008
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 1 of 19
`
`US 2016/0192403 Al
`
`cetqeapona
`
`IIS}
`
`yuowdinby
`
`LO
`
`SINANiOr
`
`Ndd
`
`ABMoqesy
`
`SUIALIS
`
`ABAIJCX)
`
`MADSING
`
`10
`
`sqapona
`
`TO
`
`NVULo-“d
`
`bor
`
`
`
`JOyIVYPrapoay
`
`‘\
`o0T
`
`wrayskg
`
`2
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 2 of 19
`
`US 2016/0192403 Al
`
`COT
`
`00¢
`
`3
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 3 of 19
`
`US 2016/0192403 Al
`
`7HOLWdosZalot
`
`ZPROTHOLLdais
`
`UXTPC8HOLINdors ZHOLWdog
`
`a¢‘OLAmon[oa
`
`@@
`
`;VeOLA
`
`6e6@ee
`
`4
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30,2016 Sheet 4 of 19
`
`US 2016/0192403 Al
`
`412SB
`
`413 &SQ)
`
`420
`
`422
`
`408
`
`404
`
`interface
`
`FIG.4
`
`o~
`pee
`
`at
`Ne SBS
`+
`
`\
`400
`
`5
`
`5
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 5 of 19
`
`US 2016/0192403 Al
`
`
`
`
`
`_—.oa.—spYyV,S|[Jeusoqay
`
`50S
`
`a[Npojn,
`
`sWaWe
`
`
`
`TapPayy
`
`PZSjatuay
`
`BegsianVd
`
`=_—tOccsOcSBisOTE
`
`QeWsyTyo1gS)OES£0S
`JOMIS
`aovpIayJONI
`
`
`
`
`JNpo|JaAlagTOAIOSsuoneorddyjonue)
`DOTAIaSGoMdOHGWdAOado
`
`
`
`
`
`
`jouw083)sos
`
`
`
`-----MOLT[OL0DCO
`
`
`
`Ea£3E38E]seypegtomonao
`
`
`
`a—siaxoeddlSWINE$“OL
`
`
`
`‘n
`
`00S
`
`((°))
`
`6
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 6 of 19
`
`US 2016/0192403 Al
`
`_-4-----+--+--069wea
`
`<¢—$$_____________________osuodsaijseony),
`
`Joydiaaduryo‘haycayeyspueyFSSaAay
`
`
`‘ayeotyyi190‘ayeyspuey[Ss809
`Joydisasueyssyeyspuezy
`
`
`
`ABMOTESo]eONUANY.s.5€9
`osuodsay7-8c9
`ayeyspuryIaAIas[SS
`
`
`
`pajoyduuooayeyspuey
`
`pojajdiuooayeyspuryy
`SyeYspueyPOS"TSS
`}Q9UUO9I),
`
`OSeSSOULISVOTITNIAY
`.ceo
`
`3da028GOL
`Z19~|TOLORHRAN
`
`yeusis4DSUuuo3
`
`aportent
`
`odessajO.NUO?
`
`Plo
`
`svardos
`
`quis
`
`919
`
`WayGOLMeas
`
`809
`
`019
`
`89
`
`079
`
`Zz9
`
`79
`
`979
`
`ges
`
`SIAIOu3O1NWOS|wapoe
`
`CoUJ905~semaqen
`1os~Qd0
`
`
`
`nH
`
`009
`
`
`
`
`
`
`
`PEO
`
`ovo
`
`
`
`f
`
`
`
`
`
`dY/dDIJaosjayordJonesYdIOZEO
`
`7
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30,2016 Sheet 7 of 19
`
`US 2016/0192403 Al
`
`700
`
`Initialize ODU [~ 782
`
`
`
`
`
`
`Detect Ethernet
`~ 704
`Connection
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Start multicast
`server
`
`
`
`Listen for
`multicast
`
`messages
`
`
`Send UDP
`Response
`Message
`
`
`
`
`Send link status
`Wail for TCP
`
`
`
`check message
`connect signal
`from Gateway
`
` TCP
`
`connect signal from
`Gateway?
`
`Close TCP SSL
`connection
`
`FIG. 7
`
`SSL handshake
`
`
`SSL
`
`connection
`active?
`
`
`8
`
`

`

`Patent Application Publication
`
`Jun. 30,2016 Sheet 8 of 19
`
`US 2016/0192403 Al
`
`800
`me|
`
`Initialize
`Gateway
`
`802
`
`804
`
`
`
`Ethernet
`connection
`available?
`
`806
`
`Send multicast
`
`message
`
`810 Shut down
`
`multicast client
`
`
`
`Initiate TCP
`~ $12
`connection with
`
` Is TCP
`connection
`established?
`
`
`
`
`
`
`
`
`connection
`active?
`
`FIG. 8
`
`9
`
`

`

`Patent Application Publication
`
`Jun. 30,2016 Sheet 9 of 19
`
`US 2016/0192403 Al
`
`Connection Established
`
`906
`
`908
`
`Ethernet Down
`
`910
`
`Ethernet Up
`
`912
`
`Multicast client
`
`Multicast message
`
`Unicastmessage
`
`924
`
`Stop multicast
`chient
`
`926
`
`Start TCP client
`
`:
`|
`
`914
`
`920
`
`922
`
`928
`
`
`
`Wait for TCP
`connection
`
`TCP connect
`930
`
`a
`
`932
`
`TCP accept
`
`SSL chent handshake
`
`934
`
`SSL server handshake
`
`936
`SSL handshake:certificate, key
`938
`
`+————~“FinSSE handshake: key, change cipher 2
`
`940
`
`942
`
`944
`
`Handshake completed
`
`Handshake change cipher
`
`Handshake completed
`
`FIG. 9
`
`10
`
`10
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 10 of 19
`
`US 2016/0192403 Al
`
`
`
`
`
`poysyqeysqwonssuu07
`
`ABMAYRL)
`
`90S
`
`10s
`
`do
`
`SOOT
`
`0001
`
`
`
`yUaTTDIRINA
`
`qnooUT|,
`
`asuodsayON)
`
`(paatiasay
`
`OLOT
`
`
`
`HOTMPOTUNTUMODssaoordiaiy,
`
`8001
`
`9001
`
`WAKOWAY
`
`11
`
`
`
`SessaISVITINY
`
`PIOL
`
`OlOld
`
`11
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 11 of 19
`
`US 2016/0192403 Al
`
`crit
`
`PITTSTILT
`
`sae
`
`
`
`IMPOY]SAIS
`
`
`
`
`
`ABMIIOH
`
`OLT
`
`(emoo1gS)
`
`sovpIo]
`
`
`
`
`
`
`
`
`
`_—-—sjoyorgSTATMOWaq]
`
`
`
`
`
`
`OCTTPuy
`
`CELSOALTWal
`
`suoyeoyddyao
`
` Stl
`
`Ado
`
`yoqEeD
`
`OTT
`
`
`
`Joprayy
`
`joe
`
`OMTpm
`
`
`
`
`
`TOUT
`
`9eTl
`
`
`
`
`
`
`
`ULApojy
`
`12
`
`SOTT
`
`TOrl
`
`ZOlL
`
`FOTL
`
`OOTT
`
`
`
`TTMOLTJODNAO
`
`am—SeeddiSWINGS
`
`
`
`
`
`feES]EAEE]sieyoedjonuopado
`
`IlOl
`
`12
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 12 of 19
`
`US 2016/0192403 Al
`
`
`
`
`
`
`
`UOY}ROUAYINRYroMIOU|94}©}VoTTeUUTOJUToY]FOUOTTBOUOIINopQeudO1f|WoIDIUUOS3IOAYOU|fayyAqABMS bepee|PICT|DOTADP yromauayywosugen|aovypsaqul||jowaypgueySnompuoNsenU0samoasay||voaoraapswramp||JOHPJRI]puss—f
`
`laolaapyomyatlarp)01afessaurjoruOStpuas
`
`
`
`
`
`
`
`
`
`
`aINdasoy)YSNOIYYsOTAIP
`
`JOVIJOPUTBY}JOBUOJSV9]JVAATIOIY
`|ayJaA0WOIssasSaUeYsi[quise07
`
`
`[BIO]BYSnormgy|Af]auoysva]We01BIePSIP?am)puas|j
`
` Oc7TtUOWISUUODYiomyau
`
`
`
`
`
`S}a8essaurasuodsarIsiqyBIOTOYMouTULEIOq
`
`
`
`SASPYIOMIAUBO}2BessatuisesyfNw puas
`
`
`
`asdodsalUT2d1AapYIOMIJAUJY}OL]PAAlgoal
`
`
`
`
`UOYMadessautasuodsasJsMyIY]WOT]AdTAAp
`
`
`
`WOITPIAIIIAL$3ABESSOUISUOESIISAYOY
`JOMISYYYULaayouruAq—||QAT}OBSIO1AaPYowauoyoFpajdnoo—|JdRpOIUL
`
`
`
`
`YIOMJOTIYIJOssaippeq]oq)suru9}aq,
`
`
`d]poulunayepay)SuIsnsa1A9pyo.Mjou
`
`dU}TIMMONAUUODaIMoasBYSTEQusy
`
`oBessairsvaryNsy)0}
`
`OTL
`
`13
`
`b—p~—-—-—--——
`
`
`
`DaLAapyIOMIOU3u3
`
`ssalppe
`
`VelOM
`
`13
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 13 of 19
`
`US 2016/0192403 Al
`
`cCCh
`
`
`
`
`
`
`
`YOOYDsBIsYU]VpUogyjUOLOOULODO1NDISOY]YSNSaLASpPYLOANOUy,eyoOBESsoUL—>naeeeaeeemeeeenceae4
`puosas8JaqjayLMYAOAAJOUOY]WOATauTIA}IG|yooyoPAAjoIaLS]oBessous|| asuiodsar |SulJopouiadproysauyeuri|o8essouwsnyeysYU]OY)O}aSuOdsOIUI||SNAIP
`
`
`
`
`
`
`
`tf}0}aavssawasuodsarpuooasat)wayaataop||YAOAYOU |aunty||jopovadproysaiqioy)urgiMpaatsoarjou||SLafpssatuJSVST[NUoY}Puss|weeeeeal
`
`
`
`
`
`
`
`a1d989]ayeUltuta|j pyoysa.ryyay)ULIiPoeAlad9I1JOUSIaspssoulpuogoaasiOY]USMUSIOAUUOSasuodsar
`
`
`
`
`realtatu]Joporred
`
`
`
`
`
`|.zor
`
`b0ZT
`
`
`
`acl“Old
`
`14
`
`14
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 14 of 19
`
`US 2016/0192403 Al
`
`
`
`
`
`UOHOBUUODBINIOSUJJOAOUOISSES
`
`AemoyedBWOIt
`
`
`
`
`
`ABLSSOWJSLII][NW&JOJJOdIsuyBIONTIOYYme
`
`ZOLT
`
`oocl
`
`
`
` ijABAMO1KSOY)WOT]WBRSSAUT
`
`
`
`AY)YIMUONISUTIONaINdasayYST|QRIsT
`
`Apmayed
`
`
`
`VelOl
`
`
`|“DOBPIONUL
`
`
`
`PUIG|oySf2ysnosy)woysauuosanaesay)uo
`
`L—5eeneee
`SWIJOoYZeI]youIa]U]JOsuosv9]18pus
`
`
`9Telt
`
`BJOJUOUYST[GejsdIVYIGL01[VUBIsvaAaIaY
`
`
`
`OU}JODUOsezyeayy‘ABMayeSoyyOFNYEY
`
`
`
`podpaosas&UOWOI}OOUODANDAs
`
`
`
`PeAtaoalSIOSRSSOULJSRONNUyou}ToyM
`
`15
`
`
`
`Abmoyeday]0)agessaurosuadsarjsfBpudas
`
`
`
`
`
`15
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 15 of 19
`
`US 2016/0192403 Al
`
`
`
`Peelt
`
`
`
`
`
`
`
`
`
`
`
`
`
`OZCT
`
`eo”
`
`
` ||2AN198SIUoMSTIUODS1Nd—asay]PuPasladasi|SVSSOU yooyoAaINDes94}areUun|bampe |stmJoporiodppoysampyeBurYyyIMpoatooos7|jousfa8essoursnguysyu]oy}0}|lasuodsarBFTUOTMAUNOD[SVANoy)UYABMS—|
`
`
`
`
`asuodsa1puosas&puag|ifOtel uwAvanos||at0,oessatu|aSessaruysvonpnur||juanbasqnsv0}asuodsai
`
`
`
` Tielt|SAijoe|SIHORISUTODSINS9H]JOYIOYMSULULIDDC
`—ayeeea
`
`0oET
`
`del“Ol
`
`16
`
`16
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 16 of 19
`
`US 2016/0192403 Al
`
`9TFL
`
`PIAL
`
`ampow
`
`[es0'7
`
`YAOMION
`
`ZOFAPOFAL
`
`
`
`apo,
`
`IBUSSIFAT
`
`
`
`J{NPO|!VOTsstusURsF,
`
`PIDT
`
`
`
`
`SUIVIBLIIIIGado
`Surpuas(9)
`StnPOwror
`
`
`IPOUORNdssay
`
`jeoo'y
`
`YAOMIDN
`
`[oynpoy
`
`DIBIOJUZ
`
`BTPI
`
`
`
`
`
`O0FT
`
`17
`
`17
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 17 of 19
`
`US 2016/0192403 Al
`
`
`
`post|.
`
`
`
`a[Mpoy!Uotsstusues
`
`St‘Old
`
`
`
`97S]
`
`css]
`
`aA
`a=
`
`xw
`
`aad
`
`cst
`
`aupoyy
`
`
`
`PrstSUNIyULLOI9qABMOyEr)
`
`PSsl?
`
`WaPo
`
`dNPOW
`
`UOLIIULOD
`
`jonuey
`
`apnpoy;w
`
`
`
`
`
`INPOTAGUIPUASasessayA]
`
`ScsT
`
`18
`
`(<9))
`
`
`?cost
`
`
`
`
`
`SuOyUOWampolyHonearnuUO,wandaneysORH9UT
`spoINP
`~PIS91S]
`
`
`
`
`
`00ST
`
`18
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 18 of 19
`
`US 2016/0192403 Al
`
`ISUBLE
`
`OT
`OW
`
`POST
`
`SUSSAIOIg
`
`wa3sks
`
`aqepeay-sayndw0y
`
`ALOUIATA,/UENTPITA]
`
`AOSSIIONf
`
`AAP
`
`RN
`
`0091
`
`19
`
`19
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 19 of 19
`
`US 2016/0192403 Al
`
`ajqupeay-49yndw07)
`
`ADSSIIOAT
`
`FOLT ALOUA]/UNIPIIA!
`LIDI
`
`SUISSII0Ag
`
`waysks
`
`WOHBTUUILOD
`
`anpowy
`
`FILI
`
`20
`
`20
`
`
`
`
`
`
`

`

`US 2016/0192403 Al
`
`Jun. 30, 2016
`
`MECHANISM TO PROVIDE LTE VOICE,
`INTERNET AND EMBMSSERVICES OVER
`ETHERNET FOR CONNECTED HOME
`ARCHITECTURE
`
`BACKGROUND
`
`1. Field
`[0001]
`[0002] The present disclosure relates generally to commu-
`nication systems, and more particularly, to a mechanism to
`provide Long Term Evolution (LTE) Voice, Internet and
`evolved Multimedia Broadcast Multicast Service (EMBMS)
`services over Ethernet for connected homearchitecture.
`
`2. Background
`[0003]
`are widely
`[0004] Wireless
`communication systems
`deployed to provide various telecommunication services
`such as telephony, video, data, messaging, and broadcasts.
`Typical wireless communication systems may employ mul-
`tiple-access technologies capable of supporting communica-
`tion with multiple users by sharing available system resources
`(e.g., bandwidth, transmit power). Examples of such mul-
`tiple-access technologies include code division multiple
`access (CDMA) systems,
`time division multiple access
`(TDMA)
`systems,
`frequency division multiple access
`(FDMA)systems, orthogonal frequency division multiple
`access (OFDMA)systems, single-carrier frequency division
`multiple access (SC-FDMA)systems, and time division syn-
`chronous code division multiple access (TD-SCDMA)sys-
`tems.
`
`the network device, where the IP address of the network
`device is unknown. The apparatus determines whethera first
`response message is received from the network device in
`response to the multicast message and determines the IP
`address ofthe network device from thefirst response message
`whenthefirst response message 1s received from the network
`device. The apparatus establishes a secure connection with
`the network device using the determined IP address.
`[0008]
`Inan aspect ofthe disclosure, a method, a computer
`program product, and an apparatus are provided. For
`example, the method may be performed by a networkdevice.
`The method includes monitoring a first port for a multicast
`message from a gateway, sendinga first response message to
`the gateway when the multicast message is received, receiv-
`ing a signalto initiate establishmentofa secure connection on
`a secondport, and establishing the secure connection with the
`gateway. The apparatus is configured to recetve MBMSdata,
`Internet traffic, and/or IMStraffic from a basestation.
`[0009] The apparatus monitors a first port for a multicast
`message from a gateway and sendsa first response message to
`the gateway when the multicast message is received. The
`apparatus receives a signal to initiate establishment of a
`secure connection on a secondport and establishes the secure
`connection with the gateway.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a diagram illustrating an example of a
`[0010]
`network architecture.
`
`FIG. 2 is a diagram illustrating an example of an
`[0011]
`access network.
`
`FIG. 3A is a diagram illustrating an example of an
`[0012]
`evolved Multimedia Broadcast Multicast Service channel
`configuration in a Multicast Broadcast Single Frequency Net-
`work.
`
`FIG. 3B is a diagram illustrating a format of a Mul-
`[0013]
`ticast Channel Scheduling Information Media Access Con-
`trol control element.
`
`[0005] These multiple access technologies have been
`adopted in various telecommunication standards to provide a
`common protocol that enables different wireless devices to
`communicate on a municipal, national, regional, and even
`global level. An example of an emerging telecommunication
`standard is Long Term Evolution (LTE). LTE is a set of
`enhancements to the Universal Mobile Telecommunications
`System (UMTS)mobile standard promulgated by Third Gen-
`eration Partnership Project (GPP). LTE is designedto better
`FIG. 4is a diagram illustrating an example network
`[0014]
`support mobile broadbandInternet access by improving spec-
`in accordance with various aspects of the disclosure.
`tral efficiency, lowering costs, improving services, making
`
`[0015] FIG.5is a diagram illustrating a network architec-
`use of new spectrum, andbetter integrating with other open
`ture in accordance with various aspects of the disclosure.
`standards using OFDMAon the downlink (DL), SC-FDMA
`on the uplink (UL), and multiple-input multiple-output
`[0016]
`FIG. 6 is a diagram illustrating data flow of the
`(MIMO)antenna technology. However, as the demand for
`network architecture in accordance with various aspects of
`the disclosure.
`mobile broadband access continues to increase, there exists a
`need for further improvements in LTE technology. Prefer-
`ably, these improvements should be applicable to other multi-
`access technologies and the telecommunication standards
`that employ these technologies.
`
`SUMMARY
`
`Inan aspect of the disclosure, a method, a computer
`[0006]
`program product, and an apparatus are provided. The method
`includes sending a multicast message to a network device,
`wherethe Internet Protocol (IP) address ofthe network device
`is unknown, determining whethera first response messageis
`received from the network device in responseto the multicast
`message, determining the IP address of the network device
`from the first response message whenthe first response mes-
`sage is received from the network device, and establishing a
`secure connection with the network device using the deter-
`mined IP address.
`
`[0007] The apparatus sends a multicast messageto a net-
`work device. The multicast message facilitates discovery of
`
`FIG. 7 is a flow chart of a method for an ODU in
`[0017]
`accordance with various aspects of the disclosure.
`[0018]
`FIG. 8 is a flow chart of a method for a gateway in
`accordance with various aspects of the disclosure.
`[0019]
`FIG. 9 is a diagram illustrating a message flow
`between an ODU and gateway in accordance with various
`aspects of the disclosure.
`[0020]
`FIG. 10 is a diagram illustrating a message flow
`between an ODU and gateway in accordance with various
`aspects of the disclosure.
`[0021]
`FIG. 11 isa diagram illustrating a network architec-
`ture in accordance with various aspects of the disclosure.
`[0022]
`FIGS. 12A and 12Bare a flow chart of a method of
`communication.
`
`FIGS. 13A and 13B are a flow chart of a method of
`[0023]
`communication.
`
`FIG. 14 is a conceptual data flow diagram illustrat-
`[0024]
`ing the data flow between different modules/means/compo-
`nents in an exemplary apparatus.
`
`21
`
`21
`
`

`

`US 2016/0192403 Al
`
`Jun. 30, 2016
`
`FIG. 15 is a conceptual data flow diagram illustrat-
`[0025]
`ing the data flow between different modules/means/compo-
`nents in an exemplary apparatus.
`[0026]
`FIG. 16 is a diagram illustrating an example of a
`hardware implementation for an apparatus employing a pro-
`cessing system.
`[0027]
`FIG. 17 is a diagram illustrating an example of a
`hardware implementation for an apparatus employing a pro-
`cessing system.
`
`DETAILED DESCRIPTION
`
`[0028] The detailed description set forth below in connec-
`tion with the appended drawings is intendedas a description
`of various configurations and is not intendedto represent the
`configurations in which the concepts described herein may be
`practiced. The detailed description includes specific details
`for the purpose of providing a thorough understanding of
`various concepts. However,it will be apparent to those skilled
`in the art that these concepts maybepracticed without these
`specific details. In someinstances, well knownstructures and
`components are shown in block diagram form in order to
`avoid obscuring such concepts.
`[0029]
`Several aspects of telecommunication systems will
`now be presented with reference to various apparatus and
`methods. These apparatus and methods will be described in
`the following detailed description and illustrated in the
`accompanying drawings by various blocks, modules, compo-
`nents, circuits, steps, processes, algorithms, etc. (collectively
`referred to as “elements”). These elements may be imple-
`mented using electronic hardware, computer software, or any
`combination thereofWhether such elements are implemented
`as hardware or software depends uponthe particular applica-
`tion and design constraints imposed on the overall system.
`[0030] By way of example, an element, or any portion ofan
`element, or any combination of elements may be imple-
`mented with a “processing system”that includes one or more
`processors. Examples ofprocessors include microprocessors,
`microcontrollers, digital signal processors (DSPs), field pro-
`grammable gate arrays
`(FPGAs), programmable logic
`devices (PLDs), state machines, gated logic, discrete hard-
`ware circuits, and other suitable hardware configuredto per-
`form the various functionality described throughoutthis dis-
`closure. One or more processors in the processing system
`may execute software. Software shall be construed broadly to
`mean instructions, instruction sets, code, code segments, pro-
`gram code, programs, subprograms, software modules, appli-
`cations, software applications, software packages, routines,
`subroutines, objects, executables, threads of execution, pro-
`cedures, functions, etc., whether referred to as software, firm-
`ware, middleware, microcode, hardware description lan-
`guage, or otherwise.
`[0031] Accordingly, in one or more exemplary embodi-
`ments, the functions described may be implementedin hard-
`ware, software, firmware, or any combination thereof. If
`implemented in software, the functions may be stored on or
`encoded as one or more instructions or code on a computer-
`readable medium. Computer-readable media includes com-
`puter storage media. Storage media may beany available
`media that can be accessed by a computer. By way of
`example, and not limitation, such computer-readable media
`can comprise a random-access memory (RAM),a read-only
`memory (ROM), an electrically erasable programmable
`ROM (EEPROM), compact disk ROM (CD-ROM)or other
`optical disk storage, magnetic disk storage or other magnetic
`
`storage devices, or any other medium that can be usedto store
`desired program code in the form of instructions or data
`structures and that can be accessed by a computer. Combina-
`tions ofthe above should also be included within the scope of
`computer-readable media.
`[0032]
`FIG. 1 is a diagram illustrating an LTE network
`architecture 100. The LTE network architecture 100 may be
`referred to as an Evolved Packet System (EPS) 100. The EPS
`100 may include one or more user equipment (UE) 102, an
`Evolved UMTSTerrestrial Radio Access Network (E-UT-
`RAN) 104, an Evolved Packet Core (EPC) 110, and an Opera-
`tor’s Internet Protocol (IP) Services 122. The EPS caninter-
`connect with other access networks, but for simplicity those
`entities/interfaces are not shown. As shown,the EPS provides
`packet-switched services, however, as those skilled in the art
`will
`readily appreciate,
`the various concepts presented
`throughout this disclosure may be extended to networkspro-
`viding circuit-switched services.
`[0033] The E-UTRANincludesthe evolved Node B (eNB)
`106 and other eNBs 108, and may include a Multicast Coor-
`dination Entity (MCE) 128. The eNB 106 provides user and
`control planes protocol terminations toward the UE 102. The
`eNB 106 may be connected to the other eNBs 108 via a
`backhaul (e.g., an X2 interface). The MCE 128 allocates
`time/frequency radio resources for evolved Multimedia
`Broadcast Multicast Service (MBMS) (eMBMS), and deter-
`minesthe radio configuration (e.g., a modulation and coding
`scheme (MCS)) for the eMBMS. In the present disclosure,
`the term MBMSrefers to both MBMSand eMBMSservices.
`
`The MCE128 maybea separateentity or part ofthe eNB 106.
`The eNB 106 mayalso bereferred to as a base station, a Node
`B, an access point, a base transceiver station, a radio base
`station, a radio transceiver, a transceiver function, a basic
`service set (BSS), an extended service set (ESS), or some
`other suitable terminology. The eNB 106 provides an access
`point to the EPC 110 for a UE 102. Examples of UEs 102
`include a cellular phone, a smart phone, a session initiation
`protocol (SIP) phone, a laptop, a personal digital assistant
`(PDA), a satellite radio, a global positioning system, a mul-
`timedia device, a video device, a digital audio player(e.g.,
`MP3player), a camera, a game console, a tablet, or any other
`similar functioning device. The UE 102 mayalso be referred
`to by those skilledin the art as a mobile station, a subscriber
`station, a mobile unit, a subscriber unit, a wireless unit, a
`remote unit, a mobile device, a wireless device, a wireless
`communications device, a remote device, a mobile subscriber
`station, an access terminal, a mobile terminal, a wireless
`terminal, a remote terminal, a handset, a user agent, a mobile
`client, a client, or someother suitable terminology.
`[0034] TheeNB 106 is connected to the EPC 110. The EPC
`110 may include a Mobility Management Entity (MME) 112,
`a HomeSubscriber Server (HSS) 120, other MMEs 114, a
`Serving Gateway 116, a Multimedia Broadcast Multicast Ser-
`vice (MBMS) Gateway 124, a Broadcast Multicast Service
`Center (BM-SC) 126, and a Packet Data Network (PDN)
`Gateway 118. The MME 112 is the control node that pro-
`cesses the signaling between the UE 102 and the EPC 110.
`Generally, the MME 112 provides bearer and connection
`management. All user IP packets are transferred through the
`Serving Gateway 116, which is connected to the PDN Gate-
`way 118. The PDN Gateway 118 provides UE IP address
`allocation as well as other functions. The PDN Gateway 118
`and the BM-SC 126 are connected to the IP Services 122. The
`
`IP Services 122 may include the Internet, an intranet, an IP
`
`22
`
`22
`
`

`

`US 2016/0192403 Al
`
`Jun. 30, 2016
`
`Multimedia Subsystem (IMS), a PS Streaming Service (PSS),
`and/or other IP services. The BM-SC 126 mayprovide func-
`tions for MBMSuserservice provisioning and delivery. The
`BM-SC 126 mayserve as an entry point for content provider
`MBMStransmission, may be used to authorize andinitiate
`MBMSBearer Services within a PLMN,and maybeusedto
`schedule and deliver MBMStransmissions. The MBMS
`
`Gateway 124 maybeusedto distribute MBMStraffic to the
`eNBs (e.g., 106, 108) belonging to a Multicast Broadcast
`Single Frequency Network (MBSFN)area broadcasting a
`particular service, and may be responsible for session man-
`agement
`(start/stop) and for collecting eMBMS related
`charging information.
`
`FIG. 2 is a diagram illustrating an example of an
`[0035]
`access network 200 in an LTE network architecture. In this
`
`example, the access network 200 is divided into a numberof
`cellular regions (cells) 202. One or more lower powerclass
`eNBs 208 may havecellular regions 210 that overlap with one
`or more ofthe cells 202. The lower power class eNB 208 may
`be a femto cell (e.g., home eNB (HeNB)), pico cell, micro
`cell, or remote radio head (RRH). The macro eNBs 204 are
`each assigned to a respective cell 202 and are configured to
`provide an access point to the EPC 110 for all the UEs 206 in
`the cells 202. There is no centralized controller in this
`example of an access network 200, but a centralized control-
`ler may be used in alternative configurations. The eNBs 204
`are responsible forall radio related functions including radio
`bearer control, admission control, mobility control, schedul-
`ing, security, and connectivity to the serving gateway 116. An
`eNB may support one or multiple (e.g., three) cells (also
`referred to as a sectors). The term “cell” can refer to the
`smallest coverage area of an eNB and/or an eNB subsystem
`serving a particular coverage area. Further, the terms “eNB,”
`“base station,’ and “cell” may be used interchangeably
`herein.
`
`scheme
`[0036] The modulation and multiple access
`employedby the access network 200 may vary depending on
`the particular telecommunications standard being deployed.
`In LTE applications, OFDM 1s used on the DL and SC-FDMA
`is used on the UL to support both frequency division duplex
`(FDD) and time division duplex (TDD). As those skilled in
`the art will readily appreciate from the detailed description to
`follow, the various concepts presented herein are well suited
`for LTE applications. However, these concepts may be readily
`extended to other telecommunication standards employing
`other modulation and multiple access techniques. By way of
`example, these concepts may be extended to Evolution-Data
`Optimized (EV-DO)or Ultra Mobile Broadband (UMB). EV-
`DO and UMBareairinterface standards promulgated by the
`3rd Generation Partnership Project 2 (3GPP2)as part of the
`CDMA2000 family of standards and employs CDMAtopro-
`vide broadbandInternet access to mobile stations. These con-
`
`cepts may also be extended to Universal Terrestrial Radio
`Access (UTRA) employing Wideband-CDMA (W-CDMA)
`and other variants of CDMA, such as TD-SCDMA;Global
`System for Mobile Communications (GSM) employing
`TDMA;and Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-
`Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM
`employing OFDMA. UTRA, E-UTRA, UMTS, LTE and
`GSMare described in documents from the 3GPP organiza-
`tion. CDMA2000 and UMBare described in documents from
`the 3GPP2 organization. The actual wireless communication
`standard and the multiple access technology employed will
`
`depend on the specific application and the overall design
`constraints imposed on the system.
`[0037] The eNBs 204 may have multiple antennas support-
`ing MIMOtechnology. The use of MIMOtechnology enables
`the eNBs 204 to exploit the spatial domain to support spatial
`multiplexing, beamforming, and transmit diversity. Spatial
`multiplexing maybe usedto transmit different streams ofdata
`simultaneously on the same frequency. The data streams may
`be transmitted to a single UE 206 to increase the data rate or
`to multiple UEs 206 to increase the overall system capacity.
`This is achieved by spatially precoding each data stream (i.e.,
`applying a scaling of an amplitude and a phase) and then
`transmitting each spatially precoded stream through multiple
`transmit antennas on the DL. The spatially precoded data
`streamsarrive at the UE(s) 206 with different spatial signa-
`tures, which enables each of the UE(s) 206 to recover the one
`or more data streams destined for that UE 206. On the UL,
`each UE 206 transmits a spatially precoded data stream,
`which enables the eNB 204 to identify the source of each
`spatially precoded data stream.
`[0038]
`Spatial multiplexing is generally used when channel
`conditions are good. When channelconditionsare less favor-
`able, beamforming may be used to focus the transmission
`energy in one or more directions. This may be achieved by
`spatially precoding the data for transmission through multiple
`antennas. To achieve good coverage at the edges of the cell, a
`single stream beamforming transmission may be used in
`combination with transmit diversity.
`[0039]
`In the detailed description that follows, various
`aspects of an access networkwill be described with reference
`to a MIMOsystem supporting OFDM on the DL. OFDM isa
`spread-spectrum technique that modulates data over a num-
`ber of subcarriers within an OFDM symbol. The subcarriers
`are spaced apart at precise frequencies. The spacing provides
`“orthogonality” that enables a receiver to recover the data
`from the subcarriers. In the time domain, a guard interval
`(e.g., cyclic prefix) may be added to each OFDM symbolto
`combat inter-OFDM-symbolinterference. The UL may use
`SC-FDMA in the form of a DFT-spread OFDMsignal to
`compensate for high peak-to-average powerratio (PAPR).
`[0040]
`FIG. 3A isa diagram 350 illustrating an example of
`an evolved MBMS (eMBMS)channel configuration in an
`MBSEN.The eNBs 352in cells 352' may form a first MBSFN
`area and the eNBs 354 in cells 354' may form a second
`MBSENarea. The eNBs 352, 354 may each beassociated
`with other MBSFNareas, for example, upto a total of eight
`MBSENareas. A cell within an MBSFNarea may bedesig-
`nated a reserved cell. Reserved cells do not provide multicast/
`broadcast content, but are time-synchronizedto the cells 352',
`354' and may haverestricted power on MBSFNresources in
`order to limit interference to the MBSFNareas. Each eNB in
`
`an MBSFNarea synchronously transmits the same eMBMS
`control information and data. Each area may support broad-
`cast, multicast, and unicast services. A unicast service is a
`service intended for a specific user, e.g., a voice call. A mul-
`ticast serviceis a service that may be received by a group of
`users, e.g., asubscription video service. A broadcastservice is
`a service that may be received by all users, e.g., a news
`broadcast. Referring to FIG. 3A, the first MBSFN area may
`support a first eMBMSbroadcastservice, such as by provid-
`ing a particular news broadcast to UE 370. The second
`MBSENarea may support a second eMBMSbroadcastser-
`vice, such as by providing a different news broadcast to UE
`360. Each MBSENarea supports one or more physical mul-
`
`23
`
`23
`
`

`

`US 2016/0192403 Al
`
`Jun. 30, 2016
`
`ticast channels (PMCH)(e.g., 15 PMCHs). Each PMCHcor-
`responds to a multicast channel (MCH). Each MCH can
`multiplex a plurality (e.g., 29) of multicast logical channels.
`Each MBSENarea may have one multicast control channel
`(MCCH). As such, one MCH may multiplex one MCCH and
`a plurality of multicast traffic channels (MTCHs) and the
`remaining MCHs may multiplex a plurality of MTCHs.
`[0041] A UE can camp on an LIEcell to discover the
`availability ofe€MBMS service access and a corresponding
`access stratum configuration. Initially, the UE may acquire a
`system information block (SIB) 13 (SIB13). Subsequently,
`based on the SIB13, the UE may acquire an MBSFN Area
`Configuration message on an MCCH. Subsequently, based on
`the MBSFN Area Configuration message,
`the UE may
`acquire an MCHscheduling information (MSI) MAC control
`element. The SIB13 may include (1) an MBSFNareaidenti-
`fier of each MBSFNarea supported by the cell; (2) informa-
`tion for acquiring the MCCH such as an MCCHrepetition
`period (e.g., 32, 64,..., 256 frames), an MCCH offset(e.g.,
`0, 1,..., 10 frames), an MCCH modification period (e.g.,
`512, 1024 frames), a signaling modulation and coding
`scheme (MCS), subframe allocation information indicating
`which subframesofthe radio frame as indicated by repetition
`period and offset can transmit MCCH; and (3) an MCCH
`changenotification configuration. There is one MBSFN Area
`Configuration message for each MBSFNarea. The MBSFN
`Area Configuration message may indicate (1) a temporary
`mobile group identity (TMGI) and an optional session iden-
`tifier of each MTCHidentified by a logical channelidentifier
`within the PMCH, and (2) allocated resources (i.e., radio
`frames and subframes) for transmitting each PMCHof the
`MBSENarea and the allocation period (e.g., 4, 8,..., 256
`frames) of the allocated resources for all the PMCHsin the
`area, and (3) an MCHscheduling period (MSP)(e.g., 8, 16,
`32,..., or 1024 radio frames) over which the MSI MAC
`control elementis transmitted.
`
`gateway 408, and UEs 412, and 413. The ODU 404 may
`establish a communication link 414 with the BS 402 and may
`send and receive communications to and from the BS 402
`over the communication link 414. For example, the commu-
`nication link 414 may be established using a WAN radio
`access technology (RAT), such as LTE. In an aspect, the BS
`402 may be configured to transmit and receive eMBMStraf-
`fic, IP Multimedia Subsystem (IMS)traffic, and/or Internet
`tra

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket