(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2016/0192403 A1
`
` GUPTA et al. (43) Pub. Date: Jun. 30, 2016
`
`
`US 20160192403A1
`
`(54) MECHANISM TO PROVIDE LTE VOICE,
`INTERNET AND EMBMS SERVICES OVER
`ETHERNET FOR CONNECTED HOME
`ARCHITECTURE
`
`(71) Applicant: QUALCOMM Incorporated, San
`Diego, CA (US)
`
`(72)
`
`Inventors: Siddharth GUPTA, San Diego, CA
`(US); Rohit TRIPATHI, San Diego, CA
`(US); Kuo-Chun LEE, San Diego, CA
`(US)' Sivaramakrishna
`VEEREPALLI, San Diego, CA (US);
`Tyler Byron WEAR, San Diego, CA
`(US); Vaibhav KUMAR, San Diego,
`CA (US)
`
`(21) Appl. No.: 14/586,878
`
`(22)
`
`Flled:
`
`Dec. 30’ 2014
`Publication Classification
`
`(51)
`
`Int. Cl.
`H04 W 76/00
`H04L 29/06
`
`(2006.01)
`(2006.01)
`
`(2006.01)
`(2006.01)
`
`H04W 12/06
`H04L 12/18
`(52) us, c1,
`CPC ............. H04W 76/002 (2013.01); H04L 12/18
`(2013.01); H04L 63/166 (2013.01); H04L
`63/0876 (2013.01); H04W12/06 (2013.01);
`H04W 84/12 (2013.01)
`
`(57)
`
`ABSTRACT
`
`A method, an apparatus, and a computer program product for
`communication in a 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 mes sage when the first
`response message is 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
`
`100\‘
`
`
`
`
`
`
`
`MME
`
`E-UTRAN
`10_4
`
`
`U ser
`Equipment
`
`
`PDN
` Serving
`
`Gateway
`Gateway
`
`
`
`
`Other
`
`‘1‘
`
`eNodeBs
`
`MBMS GW
`
`BM-SC
`
`
`
`1
`
`SAMSUNG 1008
`
`SAMSUNG 1008
`
`1
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 1 of 19
`
`US 2016/0192403 A1
`
`:53
`
`£22
`
`H22
`
`ha>»3w0
`
`mfitmm_
`
`>90£252
`
`.550
`
`£2829
`
`£3373
`
`lamb
`
`EuEgEcm
`
`A
`E:
`
`593$
`
`
`
`3x23323%
`
`2
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 2 of 19
`
`US 2016/0192403 A1
`
`New
`
`can
`
`3
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 3 0f 19
`
`US 2016/0192403 A1
`
`~580_:‘UFE99m
`
`N330Mmay:gem
`
`m:32,gemN93
`
`m:32Em
`
`EN550a=onnew
`
`mm.UHm
`
`THEN$60a$092QEm:0:04
`$02SVSUSE
`
`$330.22
`
`Oa85052
`
`Qsmutz
`
`858.2
`
`A328.2
`
`$02A_Viv—>5
`
`4m.Ufim
`
`4
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 4 0f 19
`
`US 2016/0192403 A1
`
`412
`
`%
`
`413 s\
`37')
`
`420
`
`422
`
`408
`
`Interface
`
`404
`
`FIG.4
`
`\
`400
`
`A
`v
`
`N
`~Q
`V
`
`5
`
`5
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 5 of 19
`
`US 2016/0192403 A1
`
`com
`
`#838Z1804
`
`£252
`
`@3050
`
`$68.
`%S2.
`£2920
`2352
`838m
`
`OUdemwd:
`
`c255252
`
`
`
`
`
`.....Imauvfiwmm2,_.\uoE3£
`
`IIIIIEa75:00ago
`
`
`
`.....I38—meEmZmZo
`
`
`
`EEmflow—amp15:00DQO
`
`303
`
`Siam
`
`WNW,
`
`a.0.23350
`
`owwwmmSiammsoflaozga/x
`
`DOC
`
`6.5200
`
`§650v.
`
`mam535S:
`
`$93:
`
`Hobccu
`
`53cm
`
`www
`
`a35m
`
`
`
`
`
`
`
`Gem
`
`mew
`
`m.95—
`
`6
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 6 0f 19
`
`US 2016/0192403 A1
`
`38%mOH
`
`225:329:04mm
`
`
`
`oxmamwcn:53%4mm
`
`
`
`
`
`>3“35%qu”oxmamfiafi.4mm
`
`
`
`
`
`Saar;09:30S8.HuxwamwgsAmm
`
`
`
`33358$556ch
`
`
`
`
`
`H23609:23uxmsmwgm
`
`
`
`REESEmxnsmnzmz
`
`
`
`@BogwEMBEBEE
`
`2.6
`
`awe
`
`waw
`
`wmc
`
`mac
`
`nmo
`
`vmc
`
`wmw
`
`wmw
`
`3c
`
`58:38@on
`
`Eozu
`
`c3
`
`
`
`E23muralfifiw
`
`
`
`A|omqoaw853E:
`
`
`
`ommmmufi$3322
`
`:3
`
`N3
`
`m5
`
`ASHmom33$
`
`
`
`$2me8258
`
`
`
`32:50murrjiziv
`
`wmm
`
`com35325030
`
`FjiiL
`
`850m$56
`
`cmH._r
`
` 4Em{boo
`Em0gmEg
`
`7)
`
`ace
`
`
`
`omcommmm
`
`evw
`
`
`
`EEUH55$8333280DQO
`
`
`
`
`
`ommmmmESEED
`
`7
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 7 0f 19
`
`US 2016/0192403 A1
`
`700
`
`
`
`Initialize ODU “V 702
`
`Detect Ethernet
`Connection
`
`
`
`
`
`
`
`
`
`~ 704
`
`
`
`
`
`
`
`Start Inuiticast
`server
`
`Listen for
`multicast
`
`messages
`
`
`
`
`
`
`
` ' Iessage from
`the. Gateway?
`
`
`
`
`Send UDP
`
`Response
`Message
`
`Send link status
`Wail, for TCP
`
`
`
`check message
`
`connect signal
`
`
`from Gateway
`
`
`
`connect signal From
`Gateway?
`
`TCP
`
`
`
`
`
`Close TCP SSL
`connection
`
`FIG. 7
`
`SSL handshake
`
`SSL
`
`
`connection
`active?
`
`
`8
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 8 0f 19
`
`US 2016/0192403 A1
`
`800
`
`\‘1
`
`802
`
`Initialize
`
`Gateway
`
`Ethernet
`
`connection
`
`available?
`
`804
`
`806
`
`Send multicast
`
`message
`
`
`
`
`received?
`UDP \
`response
`
`810 Shut down
`
`multicast client
`
`Initiate TCP
`
`
`connection with
`
`
`
`
`
` ls TCP
`
`connection
`established?
`
`
`
`connection
`active?
`
`FIG. 8
`
`9
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 9 of 19
`
`US 2016/0192403 A1
`
`Connection Established
`
`906
`
`908
`
`Ethemet Down
`
`910
`
`Ethernet Up
`
`912
`
`Multicast client
`
`Multicast message
`
`Unieast messagc~m>
`
`924
`
`Stop inulticast
`client
`
`926
`
`Start TCP client
`
`;
`E
`;
`
`9] 4
`
`920
`
`922
`
`928
`
`Wait for TCP
`
`
`
`connection
`
`TCP connect
`930
`
`‘J
`
`932
`
`TCP aecept—>
`
`SSL client handshake
`
`SSL server handshak
`
`934
`
`936
`
`~——-—-¢-——-SSL handshake: certificate, key
`938
`WSSL handshake: key, change cipher
`
`_r’
`
`940
`
`942
`
`944
`
`Handshake completed
`
`Handshake change cipher
`
`Handshake completed
`
`FIG. 9
`
`10
`
`10
`
`

`

`Patent Application Publication
`
`HJ
`
`2
`
`1tee
`
`US 2016/0192403 A1
`
`%93.68%
`
`wmsommuou.ma.63.:0:50th
`
`
`
`ma5338:8500mmoogfiopfi
`
`n.wen:
`
`“mags—32M:30EEG23:32
`Uowcmmofi
`
`z.camSm
`«3390DOG
`
`monmzsfimm
`
`8:82:00 m2:
`
`
`
`2::Ffiofl552$
`
`S.0:—
`
`.53
`
`11
`
`11
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 11 of 19
`
`US 2016/0192403 A1
`
`2:
`
`3:ma:
`
`>330sz
`
`3:
`
`myszv
`
`
`
`£352uuvfium
`
`
`
`we:
`
`
`
`
`
`
`
`.....|£865m2§oEBE
`
`|||||32m.8250EEO
`
`|.....|3835EmEmEv
`
`NEEE333cmHob—EUDOC
`
`mofiufifi
`
`22553$2
`
`2:.
`
`e5#350M
`
`
`
`E_$53.5«Na:
`
`
`
` M:HHmzccmozag<Emc
`
`DQO
`
`3I35:00
`
`593I
`
`ofH15:00
`
`
`
`
`
`
`
`Ne: we:
`
`
`
`
`
`
`
`
`8252
`
`as:
`
`12
`
`:.U—m
`
`12
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 12 of 19
`
`US 2016/0192403 A1
`
`
`
`8:358:25Bow.328098083%06fight83%£930:_on“2message;
`
`
`
`
`
`
`
`_02.2%#536:.ES3>55meofiyo3:33:35“03280:
`
`
`
`
`
`_2:.5555QOmEmEuansmzpfimu8_9216c€035:2:2ommmmoE3.38agem
`
` _oomfifiaI._8525cmcased:5:82:008:03.2:._so83%«.533:9.::5:3E:m3:2:._._0Oman:Hog—0:“:Dan—goMSG«mag95D>MOOOMHrIN:lllll
`
`
`
`
` snag#9:30:28i053:32anwsoht_m5use“32E8Saw@29202:mamw“
`
`
`
`
`
`
`
`
`
`
`
`uufltEE823ngan550533:53va
`
`New—
`
`2&—
`
`
`
`
`
`60¢3282flowwwmofi0388..5.2mas:
`
`8E6#859:8:
`
`
`
`2:«3%5:00:5095onafizpfimm
`
`
`
`
`
` $2353835.35%2:mam:union€956:
`
`
`
`<3.Umm
`
`93%E83%x55»:2:933:00
`
`
`
`8.5%€950:m2$332:“32:58agum
`
`
`$832:of8emaommfiE83%£552.2:So:
`owmmmoE
`
`3282a%%3&322:85.6m5.30:30885qu
`
`
`
`€959:mayo$825E2:ocizfium
`
`
`
`22?owwmmoS085%th$52:50.:83%
`
`13
`
`13
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 13 0f 19
`
`US 2016/0192403 A1
`
`
`
`
`
`
`
`
`
`Hanoi—SCHo—t _we:__moEtnaEonmohfiofE63»@0288Ho:__myowmmmoE320%3358m2%E5383%__#23506:2‘3Opowwmmog6Com_iiiiiiiiL
`
`
`
`
`
`_.1V.!!!!!
`
`
`
` _IIIopwfloEmgyammalaanmalI|__owammuex85mESmVE:2:EomcoamfiE__036%€0.38:2:£ch@03823owwwmuE__3:093;950%aH.222?»uEEBEQ_
`
`
`
`
`
`
`
`
`
`85%.“: £3a05:mo60.2320:539:E5;~3238Ho:fl99$qu
`
`
`
`
`828mof335.5%~3588~2%5Eȣ28258
`
`
`
`$280582303.or:@58583%x8365.2t8umcmmoEx02?£53m4::a95m.rim:iiiiiiiiiiii..
`
`
`
`NNNH
`
`as:
`
`ms.UA—m
`
`14
`
`14
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 14 of 19
`
`US 2016/0192403 A1
`
`_
`
`__
`
`_
`
`_
`
`
`Wcocoocccu0.503of$5commmom
`
`wmEmEQSW:332932333“3:3st
`
`£2a
`
`m3:,5was:6833(.828“£2agem
`
`
`FIN.3333333333333
`
`_.oufiSEm8565m—_3mm:msmacks:
`
`
`
`E585502332:so_E3959awashm3:0%Hocums:625::
`
`
`
`2:?oneEmu.5mg:“338%2:Eorcmb
`
`
`
`wbgfimwon“88.“@332:_«mflomfijfiswCUfiTUzQ—am050$32um.926qu
`
`
`
`
`
`Nam—
`
`
`
`ommmmufi$832:wH8Con55m83:02
`
`beg/HawaSea
`
`camu
`
`
`
`Ngaemwon”.8ownmmufi3:09,“:5%asnow
`
`
`
`
`
`
`
`
`
`<m~.U—ra
`
`
`
`Uo>mvomfimmOm‘mmwofi:$53.51;?“0:“£033
`
`
`
`amoEufifinnfimuBEESo.Emmiwofiooom
`
`togvacuumano90:00:28833
`
`
`
`2:2:320:82:000.56%95smzpfimm
`
`ask/2%
`
`15
`
`15
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 15 0f 19
`
`US 2016/0192403 A1
`
`_
`
`r-
`
`r.
`
`
`
`Moose_038mE5:8588382:98@3508__fl8392:53:3":2:5:3xg/Bmw‘_2t8owfimofi£53mvi:m25m_
`
`
`
`
`
`cam—
`
`mmm—%_IIIIIIIIIIIIIIII_
`
`...Nt3333333333333
`
` 3:8_uE5302538332:Snag,oEESED_I.INIIIIIIIIIIIIII
`
`:62
`
`£2a
`
`
`
`
`
`
`
`
`
`
`
` _2::mococoaEofiofi:m55:3@9382J_E:m."omamme38:099%vi:9:8_rumaogwnwh\m.tQOMHOUSCOUDHSUDmby:OHMHJEHMHQrI..\..!!!!!
`
`omsommfl6.58,»asnow_ _ommmmofi38:38__E25823w83:0ngEzmafimw__088ommmmoE
`
`
`
`
`
`
`
`
`
`m—mw.Uum
`
`16
`
`16
`
`

`

`Patent Application Publication
`
`91f061te
`
`US 2016/0192403 A1
`
`
`n....53¢mEEEEEQDQOhmzmzo
`09EOEOQQEOU
`3“Mu—45.3)335;
`
`
`
`
`
`
`
`
`—2353
`
`
`
`
`
`'3“
`
`2::
`
`
`
`335253:33.fishnet:
`
`x338ZE25
`
`
`
`2.:qu:Emmgmzih
`
`
`
`E.Uer
`
`
`
`2352m.3250mm:M£2.83
`
`
`m«2:32“322,gigVvS#5332mfigov
`
`
`
`a332
`
`17
`
`
`
`17
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 17 0f 19
`
`US 2016/0192403 A1
`
`
`
`w:€a:=e2
`
`2352
`
`
`
`Em—3mg
`
`
`
`
`
`3.3,Soto—2
`o=c‘Qs_c2
`
`
`
`3E8.55532
`
`5.58550
`
`unis—Fauna.
`
`2:ch
`
`QBQEU
`
`
`
`258223.32mawcauwmagma;
`
`
`
`
`
`
`
`2:ch555.33%
`
`
`
`
`
`mfi.05“.
`
`
`
`
`
`23.325.233%859.8:—
`
`=2§£==E=SU
`
`2:ch
`
`cc":
`
`18
`
`18
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 18 0f 19
`
`US 2016/0192403 A1
`
`aim—Swansagaaco
`
`23:32\5::on
`
`hcwmuucgn—
`
`h0>muuwflflhrfi
`
`3 9
`
`5H
`
`.25—
`
`$588.5
`
`Eflmxm
`
`=9:
`
`19
`
`19
`
`

`

`Patent Application Publication
`
`Jun. 30, 2016 Sheet 19 0f 19
`
`US 2016/0192403 A1
`
`5.UHm
`
`g:
`
`mimwouem
`
`593$
`
`BfiummzifinaEcU
`
`F5822\55:52
`
`kcmmmuchh
`
`yufiuumgfil
`
`20
`
`EfinuEsfifioU
`
`235:
`
`SKA
`
`.82
`
`.5:
`
`20
`
`
`
`
`
`
`

`

`US 2016/0192403 A1
`
`Jun. 30, 2016
`
`MECHANISM TO PROVIDE LTE VOICE,
`INTERNET AND EMBMS SERVICES 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 home architecture.
`
`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.
`
`[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 (3GPP). LTE is designed to better
`support mobile broadband Internet access by improving spec-
`tral efficiency, lowering costs, improving services, making
`use of new spectrum, and better integrating with other open
`standards using OFDMA on the downlink (DL), SC-FDMA
`on the uplink (UL), and multiple-input multiple-output
`(MIMO) antenna technology. However, as the demand for
`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
`
`In an 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,
`where the Internet Protocol (IP) address ofthe network device
`is unknown, determining whether a first response message is
`received from the network device in response to the multicast
`message, determining the IP address of the network device
`from the first response message when the 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 message to a net-
`work device. The multicast message facilitates discovery of
`
`the network device, where the IP address of the network
`device is unknown. 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 ofthe network device from the first response mes sage
`when the first response message is received from the network
`device. The apparatus establishes a secure connection with
`the network device using the determined IP address.
`[0008]
`In an aspect of the disclosure, a method, a computer
`program product, and an apparatus are provided. For
`example, the method may be performed by a network device.
`The method includes monitoring a first port for a multicast
`message from a gateway, sending a first response message to
`the gateway when the multicast message is received, receiv-
`ing a signal to initiate establishment ofa secure connection on
`a second port, and establishing the secure connection with the
`gateway. The apparatus is configured to receive MBMS data,
`Internet traffic, and/or IMS traffic from a base station.
`[0009] The apparatus monitors a first port for a multicast
`message from a gateway and sends a 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 second port 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 ofa Mul-
`[0013]
`ticast Channel Scheduling Information Media Access Con-
`trol control element.
`
`FIG. 4 is a diagram illustrating an example network
`[0014]
`in accordance with various aspects of the disclosure.
`[0015]
`FIG. 5 is a diagram illustrating a network architec-
`ture in accordance with various aspects of the disclosure.
`[0016]
`FIG. 6 is a diagram illustrating data flow of the
`network architecture in accordance with various aspects of
`the disclosure.
`
`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 is a diagram illustrating a network architec-
`ture in accordance with various aspects of the disclosure.
`[0022]
`FIGS. 12A and 12B are a flow chart ofa method of
`communication.
`
`FIGS. 13A and 13B are a flow chart ofa 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
`
`

`

`US 2016/0192403 A1
`
`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 intended as a description
`of various configurations and is not intended to 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 may be practiced without these
`specific details. In some instances, well known structures 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 upon the particular applica-
`tion and design constraints imposed on the overall system.
`[0030] By way of example, an element, or any portion of an
`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 configured to per-
`form the various functionality described throughout this 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 implemented in 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 be any 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 used to 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 UMTS Terrestrial 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 can inter-
`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 networks pro-
`viding circuit-switched services.
`[0033] The E-UTRAN includes the 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-
`mines the radio configuration (e. g., a modulation and coding
`scheme (MCS)) for the eMBMS. In the present disclosure,
`the term MBMS refers to both MBMS and eMBMS services.
`
`The MCE 128 may be a separate entity or part ofthe eNB 106.
`The eNB 106 may also be referred 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.,
`MP3 player), a camera, a game console, a tablet, or any other
`similar functioning device. The UE 102 may also be referred
`to by those skilled in 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 some other suitable terminology.
`[0034] The eNB 106 is connected to the EPC 110. The EPC
`110 may include a Mobility Management Entity (MME) 112,
`a Home Subscriber Server (H88) 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 A1
`
`Jun. 30, 2016
`
`Multimedia Subsystem (IMS), a PS Streaming Service (PSS),
`and/or other IP services. The BM-SC 126 may provide func-
`tions for MBMS user service provisioning and delivery. The
`BM-SC 126 may serve as an entry point for content provider
`MBMS transmission, may be used to authorize and initiate
`MBMS Bearer Services within a PLMN, and may be used to
`schedule and deliver MBMS transmissions. The MBMS
`
`Gateway 124 may be used to distribute MBMS traffic 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 number of
`cellular regions (cells) 202. One or more lower power class
`eNBs 208 may have cellular 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 for all 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
`employed by the access network 200 may vary depending on
`the particular telecommunications standard being deployed.
`In LTE applications, OFDM is 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 UMB are air interface standards promulgated by the
`3rd Generation Partnership Project 2 (3GPP2) as part of the
`CDMA2000 family of standards and employs CDMA to pro-
`vide broadband Internet 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
`GSM are described in documents from the 3GPP organiza-
`tion. CDMA2000 and UMB are 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 MIMO technology. The use of MIMO technology enables
`the eNBs 204 to exploit the spatial domain to support spatial
`multiplexing, beamforming, and transmit diversity. Spatial
`multiplexing may be used to 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
`streams arrive 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 channel conditions are 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 network will be described with reference
`to a MIMO system supporting OFDM on the DL. OFDM is a
`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 symbol to
`combat inter-OFDM-symbol interference. The UL may use
`SC-FDMA in the form of a DFT—spread OFDM signal to
`compensate for high peak-to -average power ratio (PAPR).
`[0040]
`FIG. 3A is a diagram 350 illustrating an example of
`an evolved MBMS (eMBMS) channel configuration in an
`MBSFN. The eNBs 352 in cells 352' may form a first MBSFN
`area and the eNBs 354 in cells 354' may form a second
`MBSFN area. The eNBs 352, 354 may each be associated
`with other MBSFN areas, for example, up to a total of eight
`MBSFN areas. A cell within an MBSFN area may be desig-
`nated a reserved cell. Reserved cells do not provide multicast/
`broadcast content, but are time-synchronized to the cells 352',
`354' and may have restricted power on MBSFN resources in
`order to limit interference to the MBSFN areas. Each eNB in
`
`an MBSFN area 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 service is a service that may be received by a group of
`users, e.g., a subscription video service.Abroadcast service 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 eMBMS broadcast service, such as by provid-
`ing a particular news broadcast to UE 370. The second
`MBSFN area may support a second eMBMS broadcast ser-
`vice, such as by providing a different news broadcast to UE
`360. Each MBSFN area supports one or more physical mul-
`
`23
`
`23
`
`

`

`US 2016/0192403 A1
`
`Jun. 30, 2016
`
`ticast channels (PMCH) (e.g., 15 PMCHs). Each PMCH cor-
`responds to a multicast channel (MCH). Each MCH can
`multiplex a plurality (e.g., 29) of multicast logical channels.
`Each MBSFN area 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 LTE cell to discover the
`availability of eMBMS 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 MCH scheduling information (MSI) MAC control
`element. The SIB13 may include (1) an MBSFN area identi-
`fier of each MBSFN area supported by the cell; (2) informa-
`tion for acquiring the MCCH such as an MCCH repetition
`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 subframes ofthe radio frame as indicated by repetition
`period and offset can transmit MCCH; and (3) an MCCH
`change notification configuration. There is one MBSFN Area
`Configuration message for each MBSFN area. The MBSFN
`Area Configuration message may indicate (1) a temporary
`mobile group identity (TMGI) and an optional session iden-
`tifier of each MTCH identified by a logical channel identifier
`within the PMCH, and (2) allocated resources (i.e., radio
`frames and subframes) for transmitting each PMCH of the
`MBSFN area and the allocation period (e.g., 4, 8,
`.
`.
`.
`, 256
`frames) of the allocated resources for all the PMCHs in the
`area, and (3) an MCH scheduling period (MSP) (e.g., 8, 16,
`32, .
`.
`.
`, or 1024 radio frames) over which the MSI MAC
`control element is transmitted.
`
`FIG. 3B is a diagram 390 illustrating the format of
`[0042]
`an MSI MAC control element. The MSI MAC control ele-
`
`ment may be sent once each MSP. The MSI MAC control
`element may be sent in the first subframe of each scheduling
`period of the PMCH. The MSI MAC control element can
`indicate the stop frame and subframe of each MTCH within
`the PMCH. There may be one MSI per PMCH per MBSFN
`area.
`
`[0043] An out-door unit (ODU) and a gateway may be
`deployed to enable eMBMS, voice and Internet control and
`data plane functionality from a WWAN network to an end
`nod