throbber

`0 35067868 
`   
`
 
`
 

`
`
 
` 

`  
 !
`
`
`"#$#
`%&'()&*'+,&*-./)(*/
` 0 #
1##21
`34 #
1##
`<=>

`9!0 3:0;:0 3
`; #
 ??#@##A
`7 ?#"?BCDEFGGHIJFKLMGFMDNMOPIFNQRHKFSFKT
`UVWXYZ[VW\]^^_`^ab
`cMDNHRDPIMHDPEdKHIFOIMHDPSPMEPeEFfghijhkjhljhmj
`hnjhojhpjhqj.hj..j.kj.rj.sj.tj.uj.vj
` # ##21A
`.qjwhjwrjwljwsjwnjwtjwpjwqjxijxyjxmj
`zwo{p|}~€{~~€€‚
`xnjxqjiwjiijikji|jƒ%jk.jkxjkijkrjkmjkoj
` #„##"A
`rsjrtjrpj%xj%lj%sj%tj%|j…zjyijykjysjyzjytj
`yqjlhjlwjlyjltjl|jlojlpjlvjmhjmxjmij
`†s,‡(ˆ‰()}~€Š†‹‹}~€Œ
`mkjmyjmsjmujmjmvjmqjshjskjs%jsnjsqj
`; „##" ""A
`i&Ž-+
`nmjzhjzijzkjzrjzljzoj‘hjtnjt|jtpjtuj|hj
`|wj|xj|ij|kj|yj|lj|mj|oj|’j|vjorjo…jomj
`8
1## ""A
`i&Ž-+
`osjotjoojoqjphjpkjp|jpqj’wj’sjqhjqmj
`40
##!A
`qu‹
`“{}“j‚†s,‡(ˆ‰()}~}Š†‹‹}~}Œ
`p|73 ?#"?BCDEFGGHIJFKLMGFMDNMOPIFNQRHKFSFKT
`6 #A”

` ”•
`cMDNHRKF–MHDPEdKHIFOIMHDPSPMEPeEFfght%znŠ.ujkrj
` :—p|{p|˜™}~~.(--(‡/(z*)š›*œj|/+'(€~~ju+-ˆ
`kmjyijltjl|jmujmqjshjtuj|xj|lj|qjoqj
`+&Ž',&jxi‚~ž€}Šp|Œ‹
`pkjqmjquŒji/)*+*&Šhmjhqj.vjykjyqjtpjo…j
`omŒji/),Ÿ(*&Šhljhoj.ij.kjwrjwvjwqjxijxyj
`6  ?A9 •¡? ¢•9:£}h-(œx)+‡(j
`iiji|jƒ%jƒtjk.jktjrtjrpj%ij%|j¤¤jlojlpjl’j
`|¥›(&š‡+--(jzh¦€Šp|Œ‹„ •9#£€
`mwjmyjmojsljsnjzljzojtnjt|j|ij|%j|yj|mj
`x/w*‰()&('jl*‡*-j‘wrh~h‚ŠwhŒ‹
`otŒjnhz%Š.ƒj.…jwƒjwkjw%jwmjkhjksjk‘jkuj
`63 "?A
`  •§#¡:('*-™w,&¨,t,¥¥+*llzj
`ymjmljmtjsij|sjoxjokŒ‹
`n&(l+‰()'œz-*¥(j|/+'(}}~~j“†~m*)š('|')(('jz+-
`*¨(-Ÿ+*jzh~€Šp|Œ‹
`©ªHDIMDCFNHDDF«IdP–F¬
`;3 #Awrhssili’hwpho%nsztnwixpti|ƒntu%tili||siounty|xizlnvix%sxvshm%w|rhtix
`|ziwotpm
`;6 1?A|œ'(ˆjˆ(',¨j*&¨+&')/ˆ(&'*-+'+(*)(¨(¥)+‰(¨­,)
`¥*&&(-(‡*¥/*'+,&,­**)(¨Ÿ(¥')/ˆ¥*&&(-h(¥,&¨*)œ/()‰*(
`'*'+,&ˆ*œŸ),‡+¨(,&(,)ˆ,)((¥,&¨*)œ/()›+)(-(')*&ˆ+')(¥(+‡(
`/&+'ŠuotpŒ*¥¥(',**)(¨Ÿ(¥')/ˆ¥*&&(-‹o((¥,&¨*)œ/()
`‰*('*'+,&ˆ*œ)(¥(+‡(*&(‡*¥/*'+,&ˆ(*Ž(+&¨+¥*'+&Ž*&((¨­,)'(
`(¥,&¨*)œ/()uotp',(‡*¥/*'('(*)(¨Ÿ(¥')/ˆ¥*&&(-‹o((¥
`,&¨*)œ/()‰*('*'+,&ˆ*œ¥,,)¨+&*'(¥*&&(-(‡*¥/*'+,&,­'(*)(¨
`Ÿ(¥')/ˆ¥*&&(-+&)(Ÿ,&(','((‡*¥/*'+,&ˆ(*Ž(‹h(¥,&¨*)œ/()
`uotpˆ*œ¨('(¥'*&+&¥/ˆ‰(&'/()‹o((¥,&¨*)œ/()uotpˆ*œ)(
`¥(+‡(*&+&¥/ˆ‰(&'¨('(¥'+,&ˆ(*/)(ˆ(&'¥,&­+Ž/)*'+,&‹o((¥,&¨*)œ
`/()uotpˆ*œ¨('(¥'›('()*&+&¥/ˆ‰(&'/()+Ÿ)((&',&**)(¨
`Ÿ(¥')/ˆ¥*&&(-*&¨ˆ*œ(&¨*¨('(¥'+,&ˆ(*Ž(/Ÿ,&¨('(¥'+,&,­'(
`+&¥/ˆ‰(&'/()‹o((¥,&¨*)œ/()uotpˆ*œ)(¥(+‡(*)(¥,&­+Ž/)*'+,&
`ˆ(*Ž(+&)(Ÿ,&(','(¨('(¥'+,&ˆ(*Ž(‹
`
`1
`
`APPLE 1009
`
`

`

`w o 2014/078676 A2 |IMINIMVIM INIIN INTACTATCA
`
`—_without international search report and to be republished
`upon receipt ¢ that report (Rule 48.2(g))
`
`    
`
`

`
` !"#$%#% !$
`#"#&#'( )*+,'-..
`
`Published:
`
`2
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`CHANNEL EVACUATION PROCEDURES FOR WIRELESS NETWORKS
`
`DEPLOYED IN DYNAMIC SHARED SPECTRUM
`
`  
`

` 

`

 
`

`  
`    
  

`

`

 
`
   
` 
` !"# $%$"$& !&'()(*+!,!"* $" - !".!(
`
`/0123/4520&$6.!,$#%$+07438034 $!" $" !&9+$$+$%:"!+!+ $6%:+$&$+$"$
`$+$"(;<

`
`>$"9+$$: $#!$+ $"$!"6+:&!""6:"#+$6
`=
`$ +?#@A))B4 #:!9?C$!& $$ +?# !: $#9C$+?C$
`+!+ :&!+ $$ +?#()?C$++!+ :: $##:"?6$+#+:?$+@*'B"
`$$,!"> $)$@D>)B4!+E$"$6)+$6-$@E)-B"?#%$" "$!& $
`$ +?#?"6$+ $E)-+$C#$(
`!!$+ $"A))?D>)4 $6$,$@$(C(4!#:"C9 +$C? !+:
`F
`+$G?+$#$" B#:%$"$& %:C""C$ !&+$$""$(H"#I!+ $  ,$# $6
`!+"!D>)""$,%$4$""C!":!$+ !"#:%$!#$$$" #$" !C"
`$ !#!+$""$(J$!9+!!&"$6$!:#$" 4&!+$K#$4#:%$"$& &+!# $
`! !"%+!?C %: $?+%""6$&+!# $6C D@ADB +"# $+(L?+ $+4
`"6!!+6$!:#$" #:%$"$& &+!# $"6!!+$"$ + !"!(H" !" $K 4$""C!":
`!$+ !"#:!#:9 $&+$G?+$#$" !")$ +?#)$""C!9"C#$
`"$ 9!+M !#M$?$!&*'NC"$6""$($*'N-C"$6""$@$(C(4C"$6 !
`+#+:?$+B#:+$G?+$$!"6+:?$+@)'B !$,$ $""$4& $+#+:?$+
`6$ $ $6()#+:4 $E)-+$C#$#:$"?+$ $+! $ !"!& $E)-"?#%$" !
`" $+&$+$"$&+!# $E)-$"$$49$C?+" $$  $E)-"?#%$" 
`+!+ O$6$ ! $$ +?#  $"?#%$" !9""6?%$"$($!""$ $6
`
`CROSS REFERENCE TO RELATED APPLICATIONS
`
`[0001]
`
`This application claims the benefit of U.S. Provisional Patent Application No.
`
`61/726,871 filed November 15, 2012, the contents of which are hereby incorporated by reference
`
`herein.
`
`BACKGROUND
`
`[0002]
`
`When a wireless system operates in a secondary fashion in dynamic shared
`
`spectrum (DSS), it may allow usage of the spectrum to a system which has a higher usage
`
`priority for the spectrum. Such higherpriority systems may include primary users (PU) in
`
`Television White Space (TVWS), or Licensed Shared Access (LSA) incumbents in case of the
`
`spectrum under the LSA regime.
`
`[0003]
`
`To operate in DSS such as TVWS,the devices(e.g., complying with regulatory
`
`requirements) may benefit by gaining access to free channels.
`
`In majorcities that have limited
`
`or no TVWSchannels available, sensing only operation may becomeessential as a means to gain
`
`access to more channels. Below roofline deployments, for example, may benefit from the
`
`isolation brought by the urban landscape from the digital TV (DTV)transmitters. Further,
`
`indoor deployments may benefit from the indoor penetration loss.
`
`In this context, sensing only
`
`operation may comply with specific requirements on Spectrum Sensing allowing a smallcell
`
`network to make use of a PU-assigned channel. The PU-Assigned channel(e.g., assigned to a
`
`primary user) may require a secondary user (SU) to leave the channel, if the primary useris
`
`detected. Similarly, the LSA regime mayensure the protection of the LSA incumbentto
`
`interference from the LSAlicensee, as well as a guarantee that the LSA incumbent has
`
`prioritized access to the spectrum that the incumbent ownsand sublicenses. The connected
`
`-|f-
`
`3
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`mode mechanisms maybe neededto provide support for PU detection, reporting and/or channel
`
`evacuation, e.g., when a system operates on DSSspectrum in a secondary fashion.
`
`SUMMARYOFTHE INVENTION
`
`[0004]
`
`Systems, methods, and instrumentalities are described for channel evacuation of a
`
`shared spectrum channel. In shared spectrum, a secondary user system may use spectrum. The
`
`spectrum may beutilized and/or controlled by an incumbent system. A secondary user base
`
`station may provide one or more secondary user wireless transmit receive unit (WTRUs) access
`
`to a shared spectrum channel. The secondary user base station may include, but not limited to, a
`
`licensed shared access (LSA)licensee base station, a TVWSbasestation, a dynamic shared
`
`spectrum access point and/orthe like.) The secondary user base station may receive an
`
`evacuation message indicating a need for the secondary userbase station and WTRUsto
`
`evacuate the shared spectrum channel. The evacuation message may include an alternate
`
`channel for use by the secondary user WTRUs. The evacuation message may include a system
`
`evacuation message. The secondary userbasestation may receive the evacuation message from
`
`a database entity or a broker entity. The secondary user base station may checkthe status of a
`
`shared spectrum channel with a database or a broker to determine the need to evacuate the shared
`
`   
`   
   
 

  
  
` 
   
`

 
  
`  
` !"#$%&'()&($'"(
`
`

  
 

       
  
`*+++,-
`   
 .   
  
` 
`

` 
/
`
` 

` 
0   
  
` 

`
1  
`  
`

 
`       
`  
 
   
23/4 5
`
   
 /  
`  

 
`  




`     2615  

 /73 

 
`  
`
` 
 
 
 8 5/  
`  

 
`   
` 
   
  
  
`  

 3/4

` 
   
 / 
   
` 


`  
`
  
` 3/4 / 
   
` 
`

` 
   /  
`  

 
`  
 
   
`
  


`   8  


`/  
`  

 
` 8


 
`   
 

    8 


  

  
`
` 
 /  
` 
`    
    

`   
 

  8
`/  
`  

 
`  
 
    
`*+++9-
` 



`      :
   
 
 /  :
`
   
 
 
`    
  

`
`

  
`  
/     
  
`

`  
`
`

`  / 
 
 
` :    
 /
`  :
  
 
 
`     
  
  
  
`
` 
 
`
  
` 3/4 /   
 
` 61
` 
`/  
`  

 
` 
  
  
  
`*+++;-
`
` 
  
 
   /  
`  

 
`
`  
  

 
 2  


 5
`/  
 
`
 
` 25/ 
  
 
`
`
  
 

 
  
   
  
` 
/
`

   
`  <=     <=
`
 /  
`  

 
`  


     
 
 
`
`spectrum channel. The secondary user may receive an evacuation messagein response to the
`
`shared spectrum channelstatus check.
`
`[0005]
`
`The secondary user base station may receive the evacuation message from a
`
`managemententity, e.g., based on a pre-determined channel evacuation time. The pre-
`
`determined channel evacuation time may be based on an agreement between an incumbent
`
`system operator and a secondary user operator. The allowable use of the channel by the
`
`secondary system maybe periodic. The evacuation time may re-occur one or more times. The
`
`pre-determined evacuation time may be based on an allowed time for the use of the shared
`
`spectrum channel by the secondary user WTRUs. The shared spectrum channel may be an LSA
`
`channel.
`
`[0006]
`
`The secondary user base station may coordinate channel evacuation of the shared
`
`spectrum channelin response to the evacuation message. The secondary userbase station may
`
`send an evacuation complete message to an incumbentuser(e.g., an incumbentbasestation).
`
`The incumbent user maybe the primary user (PU). The evacuation complete message may
`
`indicate to the incumbentuser that the evacuation of the shared spectrum channel has been
`
`completed. The system evacuation message may comprise an X2 messagereceived via an X2
`
`interface. The secondary userbase station may selecta targetcell, e.g., based on at least one of
`
`-2-
`
`4
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`an event notification, a secondary user WTRU measurementreport, or an neighborrelational
`
`table (NRT) entry. The secondary user base station may send a handoverrequestto the target
`
`cell.
`
`[0007]
`
`The secondary user base station may send a measurement event configuration to
`
`the secondary user WTRUs. The measurement event configuration may includeat least one of a
`
`    
`

`

`
 

 

 
` 

`

`

`
` 
`   

`

` !
`
`

`

`
` 
` 
`
    
 
`
`

`

`
`
    
    
` 
`  "
#  
$%&'(

`


 $%&
`

`
`

`
 
`  $%&'($%&'(
`
 
`
`
` "   
`

`

`
)
` 
`# 


`    
`

`

`
`  " $%&'(
` 
`"  
 
`
   *   
`
` 
  
`

`
`  
`*
`

`
    
`
 
  
`+!
`
`

`
 
`

`

     
`
`
  
     
`
  
    
`     
'(  


`  
$,'
$%&
`'(
`
` "  
`

`
`

`
 "
  
`

`

` 
`-!
`
`

`
   
`      
`
  
 
`
`

`

`  
`
`    
`

`  
`
` 
`    #  
`
  
`
` 

`&*, 
 ,.



`
 
,
`
` 
`
`
`              

` 
`  
`

`

`

    
`
`

`
`

`

`
` 

`
`  
`
`
`
`

`

 
 
 
`
`

`
`
`/!
`  
`
`
 
 
`
`       

`
`

`
  
`


`
 
 
`  
`
 
 
 
`
`
`

`

`
 

`
`
`

`//!
`

`

`

"    
`  
`
 
 
`
`  
`" 
`
 
`

`
`

`

`  

`

`0


`
`public land mobile network identifier (PLMN ID) or a request for performing a PLMN search on
`
`the shared spectrum channel based on the PLMN ID. The PLMN IDto be search may be
`
`associated with an incumbent user. The secondary user WTRU’s maybeaskedto trigger an
`
`event notification to the secondary userbasestation, e.g., when the PLMNIDis detected
`
`following configuration of the measurement event. An evacuation message maybereceived in
`
`responseto the notification.
`
`.
`
`[0008]
`
`A secondary user WTRU maydetect an incumbentuser(e.g., operating on the
`
`shared spectrum channel). The secondary user WTRU mayreceive an incumbent detection
`
`measurementconfiguration. The incumbent detection measurement configuration may include
`
`an incumbentcell identifier (ID) (e.g., one or more of a physicalcell identifier (PCT) or a PLMN
`
`ID) associated with the incumbentuser.
`
`[0009]
`
`The secondary user WTRU maydetect whether an incumbentuseris present on a
`
`shared spectrum channel, e.g., based on the incumbent detection measurementconfiguration.
`
`The secondary user WTRU maysenda detection message upon detection of the incumbentuser.
`
`The detection message maybesent via an uplink incumbentuser detection media access control
`
`(MAC)control element (CE)or via a radio resource control (RRC) message. The detection
`
`message may include an event notification. The event notification may indicate the presence of
`
`the incumbent user. The secondary user WTRU mayreceive an evacuation message from the
`
`secondary userbasestation in response to the detection message.
`
`[0010]
`
`The secondary user WTRU mayreceive a reconfiguration message in response to
`
`the detection message. The reconfiguration message may include anidentification of a target
`
`cell. The secondary user WTRU mayupdate its radio resource configuration based on the
`
`received reconfiguration message. The secondary user WTRU maysenda reconfiguration
`
`complete messageto the target cell.
`
`[0011] The secondary user WTRU maystart a timer with a value upon the detection of the
`
`incumbent user. The value of the timer maybe assigned in such a way to stagger the connection
`
`request. The secondary user WTRU maysend a connection request to a target cell upon an
`
`expiry of the timer.
`
`5
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`[0012]
`
`The secondary user WTRU maystart a timer with a value upon the detection of
`
`the incumbent user. The secondary user WTRU maystop the timer, e.g., upon a condition that a
`
`handover commandora release commandis received before an expiry of the timer. The
`
`secondary user WTRU mayattemptto establish a connection based on the handover commandor
`
`the release command. Different timer values may be used to stagger the re-establishment
`
`attempts for the secondary user WTRUs.
`
`[0013]
`
`The secondary user WTRU mayreceive a connection release message(e.g., via a
`
`downlink MAC CE)in responseto the evacuation message. The connection release message
`
`may indicate the presence of the incumbentuseras a release cause.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0014]
`
`FIG. 1A is a system diagram of an example communications system in which one
`
`or more disclosed embodiments may be implemented.
`
`[0015]
`
`FIG. 1B is a system diagram of an example wireless transmit/receive unit
`
`(WTRU)that may be used within the communications system illustrated in FIG. 1A.
`
`[0016]
`
`FIG. 1C is a system diagram of an example radio access network and an example
`
`core network that may be used within the communications system illustrated in FIG. 1A.
`
`[0017]
`
`FIG. 1D is a system diagram of another example radio access network and
`
`another example core network that may be used within the communications system illustrated in
`
`FIG. 1A.
`
`[0018]
`
`FIG. 1E is a system diagram of another example radio access network and another
`
`
`
     
` 
 
`
`
`  
`  
`
 
`
`
`

`  
`

`
`

`  
`
 

`  
`
`
`
  
` 
`  
`  

` 

`
`

`
` 
`
!   

` "  
` 
`
`

`
`
  
`  
`   $
` #
`

`  %&'(()* 
` 
`  
`  
`  
`   
` 
  
`      
`+,-./0.12,-34-565/47.0,89-6:1
`<=>?' 
  
`  
`  
`   
` 
` ;
`
`
`
 
`

`
   

`<=>?A 
  
`   B  
` @
`$*  
 
`  
`  
 <=>?'
`<=>?( 
  
`  

`  
`%
 
` C
`
` 
`%  
 
`  
`  
 <=>?'
`<=>?! 
  
`
` 

`  
`%

` D
`
`
` 
` 
`%  
 
`  
`  

`<=>?'
`<=>?) 
  
`
` 

`  
`%

`
` E
` 
` 
`%  
 
`  
`  
 <=>
`?' F
`<=>?<   
` )
`
   

`' 
`G
`%$)"'G*   
`<=>?>   
` 
` 
` H
` 
` 
`<=>?I   
`   
`   $&&)*
` 
`
`
B
`   $J">*

`$IK*
`<=>?=   
`  

`
` 
` 
`$(*
` 
`
`  
` "  
`<=>?L   
`M 
`
`(
`  
` "  
` #
`<=>?N   
` (
`  
`  
` ;
`<=>?O   
` 
`  
` 
` $'G*
` %
` @
`
  
`
`example core network that may be used within the communications system illustrated in FIG.
`1A.
`
`[0019]
`
`FIG 1F illustrates an example of an Evolved Universal Terrestrial Radio Access
`
`Network (E-UTRAN)architecture.
`
`[0020]
`
`[0021]
`
`FIG. 1G illustrates an example of system information acquisition.
`
`FIG.
`
`1H illustrates an example of an intra mobile management entity (MME)
`
`and/or serving gateway(S-GW) handover (HO).
`
`[0022]
`
`FIG. 11 illustrates an example of a successful radio resource control (RRC)
`
`connection re-establishment.
`
`[0023]
`
`[0024]
`
`[0025]
`
`diagram.
`
`FIG. 1J illustrates an example of rejection of RRC connection re-establishment.
`
`FIG. 1K illustrates an example of an RRC connectionrelease.
`
`FIG. 1L illustrates an example of automatic neighbor relation (ANR) block
`
`-4-
`
`6
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`[0026]
`
`FIG. 1M illustrates an example ofutilization of the automatic neighborrelation
`
`(ANR)function.
`
`[0027]
`
`[0028]
`
`FIG. 1N illustrates an example of the TV band spectrum usage.
`
`FIG.2 illustrates an example of an architecture that may be used for evacuation at
`
`a knowntimeinstant.
`
`[0029]
`
`FIG.3 illustrates an example of system evacuation,e.g., signaled by a licensed
`
`shared access (LSA) incumbent.
`
`[0030]
`
`FIG.4 illustrates an example of system evacuation, e.g., using synchronization
`
`channel (SCH)/ reference signal (RS) transmission.
`
`[0031]
`
`FIG.5 illustrates an example of system evacuation, e.g., using a modified random
`
`access channel (RACH)procedure.
`
`[0032]
`
`FIG.6 illustrates an example of system evacuation, e.g., triggered by an active
`
`database or broker.
`
`[0033]
`
`FIG.7 illustrates an example of system evacuation, e.g., triggered by a passive
`
`database or broker.
`
`[0034]
`
`(IE).
`
`[0035]
`
`FIG.8 illustrates an example of a frequency information information element
`
`FIG. 9 illustrates an example of an uplink primary user (UL PU)detection
`
`medium access control (MAC) control element (CE).
`
`
`

 
    
 
`  
` !"  
`

$%&  
` #
`(

  ) &*  
` '
`+,  
`.

)*  // 
&)
&
` -
`&01"  
`3

)*  //  )  
` 2 
`
145"6 
!1"  
`8

)*  //  &  &&
` 27
`
!45"& 
`9

)*  // &) *
` 2
`&+
`:

)*  // &) *
` 22
`&+
`<

= )    

` 2;
`>" 2?
`@

 
+ ) A0BA"& 
`& 

`4"

4>"
` C

&  &)  
+1D"//
` 2 
`1D( 2#
`

!45E&BA& 
` (

F$!A
*  * &*
` 2'
`5G" 2-
` .

F$!A
*  * !!4
` E

, 5G

` 3

F$!A
*  * !!4 
` ; 
`
 ;7
` 8

  
 &  

`  ;
` 9

& 
*  
` :

&    /
` ;2
`    /& * *  
`
`reporting the presence of the incumbentuser, and receiving an evacuation message.
`
`[0036]
`
`SIB2.
`
`[0037]
`
`[0038]
`
`(HO).
`
`[0039]
`
`FIG. 10 illustrates an example of a modified system information block (SIB), e.g.,
`
`FIG. 11 illustrates an example of a RACH-based PU detection.
`
`FIG. 12 illustrates an example of a WTRU channel evacuation via handover
`
`FIG. 13 illustrates an example of a WTRU channel evacuation via RRC
`
`connection re-establishment following HO failure.
`
`[0040]
`
`release.
`
`[0041]
`cause.
`
`[0042]
`
`[0043]
`
`FIG. 14 illustrates an example of WTRU channel evacuation via RRC connection
`
`FIG. 15 illustrates an example of an information elementindicating a release
`
`FIG. 16 illustrates an example of a shared spectrum channel evacuation.
`
`FIG. 17 illustrates an example of detecting the presence of an incumbentuser,
`
`7
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`DETAILED DESCRIPTION
`
`    
`
` ! ""!!"#
`
`

`#$%#$##& 
`!  '#!##!& (
`"( ##%)'#$ ("#'
`"## !& (%*# !  (!%+## $
`
` (!"#%,$ (! ''"
`
` (!%
`.)/%0$ &  ( 011"##
`
-
` !  (!  %+# ( 011 (!
`
`
` ( #'#''' $$'!'
`%' "%+# ( 011 (! "
`##$###$( '$"
`!"#%.& '# ( 011 ( ( #
` #'# 234,5'  
`2+4,5'6( 2.4,5'#$.4,2*.4,5'$7
`.4,2837.4,5'#9%
`#".)/%0'# ( 011 ("
`
:
` ;2<+=>501?'01?!'01?';01?2"##$((
`
` (!<+=>01?5'"92=@501A;01B;01C'"9
`01D;01E;01F'!"##"92G8+@501H'#)001'#
`"900?'#$#"!## !  (
` !<+=>'!'"9';"9 %I##<+=>01?'
`01?!'01?'01? (!(($; 
`" %J("(& '#<+=>01?'01?!'01?'01? (!
`$ ;"$ (6 2>I5'
`!'& !!!'$'#'$
`
`2G45' #''!9' '"'
` '#9%
`+# ( 011 (!00B!
`
K
`00B!%I##!00B'00B! (!(($
`"("##<+=>01?'01?!'01?'01?
`  "9'##"901D;01E;01F'#)001'
`
`wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102dto facilitate access to
`
`[0044]
`
`A detailed description of illustrative embodiments will now be described with
`
`reference to the various figures. Although this description provides a detailed example of
`
`possible implementations, it should be noted that the details are intended to be exemplary and in
`
`no waylimit the scope of the application.
`
`In addition, the figures mayillustrate flow charts,
`
`which are meant to be exemplary. Other embodiments may be used. The order of the messages
`
`may be varied where appropriate. Messages may be omitted if not needed, and, additional flows
`
`may be added.
`
`[0045]
`
`FIG. 1A is a diagram of an example communications system 100 in which one or
`
`more disclosed embodiments may be implemented. The communications system 100 may be a
`
`multiple access system that provides content, such as voice, data, video, messaging, broadcast,
`
`etc., to multiple wireless users. The communications system 100 may enable multiple wireless
`
`users to access such content through the sharing of system resources, including wireless
`
`bandwidth. For example, the communications systems 100 may employ one or more channel
`
`access methods, such as code division multiple access (CDMA),time division multiple access
`
`(TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA),single-
`
`carrier FDMA (SC-FDMA),andthelike.
`
`[0046]
`
`As shownin FIG. 1A, the communications system 100 may include wireless
`
`transmit/receive units (WTRUs) 102a, 102b, 102c, and/or 102d (which generally or collectively
`
`maybereferred to as WTRU 102), a radio access network (RAN) 103/104/105, a core network
`
`106/107/109, a public switched telephone network (PSTN) 108, the Internet 110, and other
`
`networks 112, though it will be appreciated that the disclosed embodiments contemplate any
`
`number of WTRUs,basestations, networks, and/or network elements. Each of the WTRUs102a,
`
`102b, 102c, 102d maybe any type of device configured to operate and/or communicate in a
`
`wireless environment. By way of example, the WTRUs102a, 102b, 102c, 102d may be
`
`configured to transmit and/or receive wireless signals and may include user equipment (UE), a
`
`mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personaldigital
`
`assistant (PDA), a smartphone,a laptop, a netbook, a personal computer, a wireless sensor,
`
`consumerelectronics, and thelike.
`
`[0047]
`
`The communications systems 100 may also include a basestation 114a and a base
`
`station 114b. Each ofthe base stations 114a, 114b may beanytype of device configured to
`
`one or more communication networks, such as the core network 106/107/109, the Internet 110,
`
`-6-
`
`8
`
`

`

`WO2014/078676
`
`PCT/US2013/070338
`
`and/or the networks 112. By way of example, the base stations 114a, 114b may be a base
`
`transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B,a site
`
`controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a,
`
`114b are each depicted as a single element, it will be appreciated that the base stations 1 14a,
`
`114b may include any numberofinterconnected base stations and/or network elements.
`
`[0048]
`
`The base station 114a may bepart of the RAN 103/104/105, which may also
`
`(BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base
`
`station 114b may be configured to transmit and/or receive wireless signals within a particular
`
`geographic region, which maybereferred to as a cell (not shown). The cell may further be
`
`dividedinto cell sectors. For example, the cell associated with the base station 114a may be
`
`divided into three sectors. Thus, in one embodiment, the base station 114a may include three
`
`transceivers, i.e., one for each sector of the cell.
`
`In another embodiment, the basestation 114a
`
`may employ multiple-input multiple output (MIMO)technology and, therefore, may utilize
`
`multiple transceivers for each sectorofthe cell.
`
`[0049]
`
`The base stations 114a, 114b may communicate with one or more of the WTRUs
`
`102a, 102b, 102c, 102d overanair interface 115/116/117, which maybe any suitable wireless
`
`communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV),
`
`visible light, etc.). The air interface 115/116/117 may be established using any suitable radio
`
`include other base stations and/or network elements (not shown), such as a basestation controller
`
`    
`
   

 
`    !  " "  
`    #$  % 
`&  

`
  '    

`
 %  %        
`  
`
`  
-#
./
.
.0  
`())*+,
` %      
`      %     
`1  
` - 1    
   
` 
 '%     '   %
`'''      %
`   2    

`   %      
 %
`    3    

`%! %%%%4345 ' %6
`%   
`
`  

%   &-8
`())*7,
`
. 
. 
. 
.   
0
9
:   % 
`%  
`';% -2  3-%8<
` ' 
0
9
:  %  '  %
`  '-#
`4  %   
..
`())=),
`%  

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