<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Billy Chan</title>
    <description>Hi, this is billychan from hongkong, you may contact me  at &quot;bill0930 at gm@il.com&quot;
</description>
    <link>https://bill0930.github.io//</link>
    <atom:link href="https://bill0930.github.io//feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Sun, 02 Jun 2019 18:28:00 +0000</pubDate>
    <lastBuildDate>Sun, 02 Jun 2019 18:28:00 +0000</lastBuildDate>
    <generator>Jekyll v3.8.5</generator>
    
      <item>
        <title>Chapter 99 - Question Revision</title>
        <description>&lt;h3 id=&quot;spread-spectrum&quot;&gt;Spread Spectrum&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Spread-spectrum is designed to trade bandwidth efficiency for reliability, integrity, and security&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;FHSS&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Frequency Hopping Spread Spectrum&lt;/li&gt;
      &lt;li&gt;Spectrum is divided into many subchannels&lt;/li&gt;
      &lt;li&gt;two communicating systems hop on same frequency&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;DSSS&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Direct Sequence spread spectrum
        &lt;ul&gt;
          &lt;li&gt;stations are assigned orthogonal codes&lt;/li&gt;
          &lt;li&gt;use these code for transmission&lt;/li&gt;
          &lt;li&gt;other stations transmissions appears an noise&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/UbF8Pr0.png&quot; alt=&quot;fhss-dsss&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;arq&quot;&gt;ARQ&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Automatic Repeat reQuest&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Reactive&lt;/strong&gt; protocol&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;control protocols&lt;/strong&gt; for transmission of data over noisy or unreliable communication network.&lt;/li&gt;
  &lt;li&gt;Use &lt;strong&gt;ACK&lt;/strong&gt; and &lt;strong&gt;timeouts&lt;/strong&gt; to acheive reliable data transmission&lt;/li&gt;
  &lt;li&gt;Stop-and-wait ARQ, Go-Back-N ARQ&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;aloha-vs-slotted-aloha&quot;&gt;Aloha VS slotted Aloha&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Aloha&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;a terminal transmits whenever the user data is ready&lt;/li&gt;
      &lt;li&gt;if the sender finds that the packet get collided
        &lt;ul&gt;
          &lt;li&gt;it &lt;strong&gt;waits for a random period of time&lt;/strong&gt;&lt;/li&gt;
          &lt;li&gt;send the packet again&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Throughput : $S_{pure} = Ge^{-2G}$&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Slot-Aloha&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;time is slotted&lt;/li&gt;
      &lt;li&gt;length on the slot is the time to transmit a packet&lt;/li&gt;
      &lt;li&gt;node starts transmission in the beginning of the slots only&lt;/li&gt;
      &lt;li&gt;if collision occurs
        &lt;ul&gt;
          &lt;li&gt;sender &lt;strong&gt;waits for a random number of slots&lt;/strong&gt;&lt;/li&gt;
          &lt;li&gt;transmit Packets agains&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Throughput:  $S_{slotted} = Ge^{-G}$&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://upload.wikimedia.org/wikipedia/commons/thumb/a/a5/Aloha_PureVsSlotted.svg/1024px-Aloha_PureVsSlotted.svg.png&quot; alt=&quot;Throughput vs. Traffic Load of Pure Aloha and Slotted Aloha.&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;why-does-ieee-standardize-only-two-lower-layers-for-wlans&quot;&gt;Why does IEEE standardize only two lower layers for WLANs&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;only standardize PHY and MAC lyaer&lt;/li&gt;
  &lt;li&gt;Interfaces to higher layer is the same as those in iEEE 80.2x standards&lt;/li&gt;
  &lt;li&gt;The upper layers is still the same as normal LAN&lt;/li&gt;
  &lt;li&gt;what the different is the medium for tranmission , it is in wireless now.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;beb-works-in-ieee-80211-wlan&quot;&gt;BEB works in IEEE 802.11 WLAN.&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Binary Exponential Backoff&lt;/li&gt;
  &lt;li&gt;When multiple entities attempt to gain access to a shared resource, only one of them will succeed.&lt;/li&gt;
  &lt;li&gt;Those who fail wait til the resoure becomes available then retry.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Binary Exponential Backoff (BEB)&lt;/strong&gt; is an algorithm to determine how long entities should backoff before they retry.&lt;/li&gt;
  &lt;li&gt;With every unsuccessful attempt, the &lt;strong&gt;maximum backoff interval is doubled&lt;/strong&gt;.&lt;/li&gt;
  &lt;li&gt;BEB &lt;strong&gt;prevents congestion&lt;/strong&gt; and &lt;strong&gt;reduces the probability&lt;/strong&gt; of entities &lt;strong&gt;requesting access at the same time&lt;/strong&gt;,&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;why-rts-cts-needed&quot;&gt;Why RTS-CTS needed&lt;/h3&gt;

&lt;p&gt;​	- to solve hidden terminal problem&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://pic.pimg.tw/oilcut123/1393228354-2638627403.png&quot; alt=&quot;é±èç¯é»&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;hidden terminal problem&lt;/strong&gt; occurs when a node can communicate with a wireless access point (AP), but cannot directly communicate with other nodes that are communicating with that AP.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;RTS-CTS&lt;/strong&gt;&lt;/p&gt;
    &lt;ul&gt;
      &lt;li&gt;the senders A sends RTS to receiver B&lt;/li&gt;
      &lt;li&gt;once the receiver B get RTS, it starts to send CTS to all other terminals, indicating that sender A is going to communicate with receiver B. After the this handshake, they can start send data.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;network-allocation-vector&quot;&gt;Network allocation vector&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Shared Medium Access&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Carrier Sensing&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;&lt;strong&gt;Virtual Carrier Sensing&lt;/strong&gt;
            &lt;ul&gt;
              &lt;li&gt;provided by the &lt;u&gt;Network Allocation Vector (NAV)&lt;/u&gt;&lt;/li&gt;
              &lt;li&gt;NAV Indicates &lt;u&gt;how long the medium is reserved&lt;/u&gt;&lt;/li&gt;
              &lt;li&gt;NAV is set &lt;strong&gt;acccrdoing to fields (Duration ) indicated in most frames&lt;/strong&gt;&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;It is a virtual carrier sensing mechanism.&lt;/li&gt;
  &lt;li&gt;The station listens to &lt;em&gt;duration&lt;/em&gt; field to set their NAV&lt;/li&gt;
  &lt;li&gt;It is a indicator for a station on how long it must defer from accessing the medium&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;ess-and-infrastruture-bss-difference&quot;&gt;ESS and Infrastruture BSS difference&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Basic Service Set (BSS)&lt;/strong&gt; : a set of stations communicating with each other&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Extended Service Set (ESS)&lt;/strong&gt;: linking BSS using backbone network&lt;/p&gt;

&lt;p&gt;​&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Infrastructure BSS (Infracstruture mode)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Terminals communicate via  AP&lt;/li&gt;
  &lt;li&gt;centralized&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;http://4.bp.blogspot.com/_mx1N_ZN8DgU/Sm6wcnWhGGI/AAAAAAAAAWs/5OslarklpWs/s400/2.jpg&quot; alt=&quot;ãInfrastructure BSSãçåçæå°çµæ&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Extended Service Set (ESS)&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;provide larger service areas&lt;/li&gt;
  &lt;li&gt;does not specify pariticular technology&lt;/li&gt;
  &lt;li&gt;requires backbone to provide a specific set of service&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;http://4.bp.blogspot.com/_mx1N_ZN8DgU/Sm6wcnWhGGI/AAAAAAAAAWs/5OslarklpWs/s400/2.jpg&quot; alt=&quot;ãInfrastructure BSSãçåçæå°çµæ&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;bluetooth-topology&quot;&gt;Bluetooth topology&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://www.researchgate.net/profile/Farhat_Saleemi2/publication/228990705/figure/fig1/AS:393606675353600@1470854552026/A-typical-Bluetooth-Piconet.png&quot; alt=&quot;A typical Bluetooth Piconet Â &quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://www.researchgate.net/profile/Xu_Cheng23/publication/4162479/figure/fig2/AS:667607342538754@1536181402464/A-Bluetooth-scatternet.png&quot; alt=&quot;A Bluetooth scatternet&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Piconet&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;master and slaves architecture&lt;/li&gt;
      &lt;li&gt;maximum up to 7 slaves&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;scatternet&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;a group of piconet&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;main-appilcation-of-zigbee&quot;&gt;&lt;strong&gt;Main Appilcation of ZigBee&lt;/strong&gt;&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;Low Data-rate radio services&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;
        &lt;p&gt;Remote control,&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;Joystick&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;Personal Health care&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;sensors&lt;/p&gt;

        &lt;p&gt;&lt;img src=&quot;https://i.imgur.com/DtCu7G3.png&quot; alt=&quot;ZigBee application&quot; /&gt;&lt;/p&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;zigbee-mesh-topology&quot;&gt;ZigBee Mesh Topology&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;http://ptgmedia.pearsoncmg.com/images/chap2_9780137134854/elementLinks/02fig05.jpg&quot; alt=&quot;02fig05.jpg (500Ã417)&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;mission-of-3gpp&quot;&gt;MIssion of 3gpp&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;The 3rd Generation Partnership Project (3GPP)&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;developing globally acceptable specifications for third generation (3G) mobile systems.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;shortcomings-of-csmacd-in-wireless-networks&quot;&gt;shortcomings of CSMA/CD in wireless networks&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;collisions in wirerless channels are harder to detect&lt;/li&gt;
  &lt;li&gt;colisions leads to usage of bandwidth which is scarce&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;which-layers-ieee-80211-specify-in-their-standards-why&quot;&gt;Which layers IEEE 802.11 specify in their standards? Why?&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;only standardize PHY and MAC lyaer&lt;/li&gt;
  &lt;li&gt;Interfaces to higher layer is the same as those in iEEE 802.x standards&lt;/li&gt;
  &lt;li&gt;The upper layers is still the same as normal LAN&lt;/li&gt;
  &lt;li&gt;what the different is the medium for tranmission , it is in wireless now.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;what-are-two-principle-operation-modes-of-80211abgn-systems&quot;&gt;What are two principle operation modes of 802.11a/b/g/n systems?&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;ad-hoc mode&lt;/li&gt;
  &lt;li&gt;infrastructure mode&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;briefly-explain-evolution-of-air-interface-technology-from-gsm-towards-lte&quot;&gt;Briefly explain evolution of air interface technology from GSM towards LTE.&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;GSM&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;TDMA and CDMA&lt;/li&gt;
  &lt;li&gt;FSK digital modulation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;GPRS&lt;/p&gt;

&lt;p&gt;EDGE&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Why is ad-hoc networking useful in militaristic applications?&lt;/li&gt;
&lt;/ol&gt;

</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-99-Questions.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-99-Questions.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 14 - Public Protection and Disaster Relief Communications</title>
        <description>&lt;h1 id=&quot;public-protection-and-disaster-relief-communications&quot;&gt;Public Protection and Disaster Relief Communications&lt;/h1&gt;

&lt;h2 id=&quot;definition&quot;&gt;Definition&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;PPDR communications can be distinguished in those
    &lt;ul&gt;
      &lt;li&gt;used by agencies and organizations responsible for dealing with
        &lt;ul&gt;
          &lt;li&gt;maintenance of law and order&lt;/li&gt;
          &lt;li&gt;protection of life and property , and emergency situations&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;and in those used by agencies and organisations dealing with
        &lt;ul&gt;
          &lt;li&gt;a serious disruption of the functioning of society,&lt;/li&gt;
          &lt;li&gt;posing a significant, widespread threat to human life, health ,&lt;/li&gt;
          &lt;li&gt;property or the environment&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;whether caused by
        &lt;ul&gt;
          &lt;li&gt;accident, human activity and ,&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;whether developing suddenly or as a result of complex, long term processes&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;users-and-types-communication&quot;&gt;Users and types communication&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Emergency response as multi-agent system&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;
        &lt;p&gt;Public safety agency should be always (24/7) ready for emergency response&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;A multi-agent system is a system composed of multiple interacting intelligent agents.&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;Rescue teams are in fact multi-agent systems where coordination is critical&lt;/p&gt;

        &lt;ul&gt;
          &lt;li&gt;to improve coordination such missions often rely on coordination centers that needs to be provided information in real-time;&lt;/li&gt;
          &lt;li&gt;the more information about the context of a mission is provided the more precise/efficient coordination is.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;Communication technologies is a significant factor of multi-agent systems’ performance&lt;/p&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;PPDR USERS&lt;/strong&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Regular Police&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;Fire Brigades&lt;/li&gt;
  &lt;li&gt;Emergency Medical Services (EMS)&lt;/li&gt;
  &lt;li&gt;Part-time Fire&lt;/li&gt;
  &lt;li&gt;Special police Functions&lt;/li&gt;
  &lt;li&gt;EMS civilian support&lt;/li&gt;
  &lt;li&gt;Police Civilian support&lt;/li&gt;
  &lt;li&gt;Fire civilian Support&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Genreal Government Personnel&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Types of communication&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;human-to-human
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/KsMefq8.png&quot; alt=&quot;H2H&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;humah-to-machine
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/D487Jig.png&quot; alt=&quot;H2M&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;machine-to-machine
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/yTHtUJ5.png&quot; alt=&quot;M2M&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;application-and-services&quot;&gt;Application and services&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;PPDR application&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/A0cEtiL.png&quot; alt=&quot;PPDR_APP1&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;PPDR application 2&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/P5Tgl6S.png&quot; alt=&quot;PPDRAPP_2&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;PPDR Broadband&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/AW07aJR.png&quot; alt=&quot;PPDR_BROADBAND&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Capabilities provided under Localized Communication Services&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/uxalOwr.png&quot; alt=&quot;LCS&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;obejctives-according-to-itu&quot;&gt;Obejctives according to ITU&lt;/h2&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Objective&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;&lt;strong&gt;to support the integration&lt;/strong&gt; of voice, data, video and image communications as part of a multimedia capability;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;&lt;strong&gt;to provide additional level(s) of priority, availability and layered security&lt;/strong&gt; associated with the source, destination and type of information carried over the communication channels used by various PPDR applications and operations;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;&lt;strong&gt;to provide each PPDR agency and organization with user authentication (&lt;/strong&gt;e.g. public key cryptography) among PPDR agencies and organizations and for their devices prior to granting access to their applications or network resources;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to support operation in &lt;strong&gt;extreme&lt;/strong&gt; or &lt;strong&gt;adverse environments&lt;/strong&gt; (high mobility, heat, cold, dust, rain, water, noise, shock, vibration, extreme temperature, and extreme electromagnetics, etc.);&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to suppor&lt;strong&gt;t robust equipment&lt;/strong&gt; (e.g. hardware, software, operational and maintenance aspects, long battery life). Equipment (handheld or transportable) that functions while the user is in motion is also required. Equipment may also require unique accessories, which could include special microphones;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to &lt;strong&gt;accommodate the use of repeaters for covering long distances between terminals and base stations&lt;/strong&gt; in rural and remote areas and also for intensive on- scene localized areas;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to provide &lt;strong&gt;fast call set-up, one-touch broadcasting (PTT to group) and group call&lt;/strong&gt; features;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to provide for &lt;u&gt;emergency calls, one-touch emergency alert&lt;/u&gt; (emphasizing that this function is used in life threatening situations and should receive the highest level of priority), emergency voice PTTs, and emergency data PTTs (e.g. sending images, real-time video) during PPDR events;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to support information &lt;strong&gt;pull, push and subscription&lt;/strong&gt; with prioritization;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to provide for &lt;strong&gt;strong multi-national/multi-agency&lt;/strong&gt; technical interoperability over multi-network and device technologies in a seamless fashion&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to provide &lt;strong&gt;Localized Communication Services (LCS),&lt;/strong&gt; &lt;strong&gt;Relayed Device Mode Communications (RDM)&lt;/strong&gt; , &lt;strong&gt;Direct Mode Operation (DMO&lt;/strong&gt;);&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to provide for &lt;strong&gt;the ability of PPDR communication systems to interface with other dedicated PPDR&lt;/strong&gt; and/or commercial systems;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to be &lt;strong&gt;scalable in order to suit small and large agencies&lt;/strong&gt;, without sacrificing the ability to interoperate;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to provide for &lt;strong&gt;quick deployment of temporary infrastructure&lt;/strong&gt; and services as well as recovery from failure;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to support &lt;strong&gt;continuous use of basic PPDR services in case of infrastructure collapse or failur&lt;/strong&gt;e, e.g. loss of backhaul link between base station and core network;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to support &lt;strong&gt;the need for high level of security&lt;/strong&gt; without compromising the response time;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;to &lt;strong&gt;provide audio quality&lt;/strong&gt; that ensures the listener is able to understand without repetition, identify the speaker, detect stress in a speaker’s voice, and hear background sounds without interfering with the primary voice communications.&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;&lt;strong&gt;Low Latency –&lt;/strong&gt; very short call &lt;strong&gt;set up times (&amp;lt; 500 ms)&lt;/strong&gt; and very limited end to end &lt;strong&gt;voice/data transmission delay (&amp;lt; 1 s)&lt;/strong&gt;.&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;h2 id=&quot;spectrum-requriements&quot;&gt;Spectrum requriements&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;How to calculate for it&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Determine busy hour call attempts per PDDR user for each service in each environment&lt;/li&gt;
      &lt;li&gt;Determine effective call/session duration&lt;/li&gt;
      &lt;li&gt;Determine activity factor&lt;/li&gt;
      &lt;li&gt;Calculate busy hour traffic per PPDR user&lt;/li&gt;
      &lt;li&gt;Calculate offered traffic/cell for each service in each environment&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/nALQjsP.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Unique PPDR requirement&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Blocking = less than 1%&lt;/li&gt;
      &lt;li&gt;Modularity= ~20 channels per cell per network&lt;/li&gt;
      &lt;li&gt;Frequency reuse cell format
        &lt;ul&gt;
          &lt;li&gt;12 for like power mobile or personal stations&lt;/li&gt;
          &lt;li&gt;21 for mixture of high/low power mobile and personal stations.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Determine number of service channels needed for each service in each “service” environment (NB, WB, BB).&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;existing-and-future-ppdr-communication&quot;&gt;Existing and future PPDR communication&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Exisiting PPDR communication&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;EU(380-400Mhz)&lt;/li&gt;
      &lt;li&gt;The network deployment and relevant infrastructure is usually built for nationwide coverage and is owned by state agencies that permit network utilisation among public protection and disaster relief (public) organisations.&lt;/li&gt;
      &lt;li&gt;These networks satisfy the security and reliability requirements.&lt;/li&gt;
      &lt;li&gt;However, they can support a limited number of multimedia services.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Metrics of interest&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;mean throughput per node&lt;/li&gt;
      &lt;li&gt;fraction of time when at least one node is disconnected&lt;/li&gt;
      &lt;li&gt;mean number of disconnected nodes&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Emerging PPDR applications utilize heavy-traffic services, which can not be served by existing PPDR communication systems&lt;/li&gt;
  &lt;li&gt;Millimeter wave technologies may &lt;strong&gt;address wireless demands of heavy traffic application&lt;/strong&gt;s, however, &lt;strong&gt;the reliability of mmW&lt;/strong&gt; communication &lt;strong&gt;doesn’t satisfy the reliability requirements&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;The reliability of mmW communication can be enhanced by using mesh technology and AI&lt;/li&gt;
  &lt;li&gt;Development of technologies which improve the reliability of mmW is a relevant research challenge&lt;/li&gt;
&lt;/ul&gt;

</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-14-Public-Protection-and-Disaster-Relief-Communicaton.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-14-Public-Protection-and-Disaster-Relief-Communicaton.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 13 - Vehicular and Aerial Communication</title>
        <description>&lt;h1 id=&quot;vehicular-and-aerial-communication&quot;&gt;Vehicular and Aerial Communication&lt;/h1&gt;

&lt;h3 id=&quot;networks-in-5g-era-and-beyond&quot;&gt;Networks in 5G era and Beyond&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;The “Big Three” 5G technologies
    &lt;ul&gt;
      &lt;li&gt;Ultra-densification
        &lt;ul&gt;
          &lt;li&gt;Leads to &lt;strong&gt;gross over-provisioning&lt;/strong&gt; and more complex &lt;strong&gt;interference management&lt;/strong&gt;&lt;/li&gt;
          &lt;li&gt;requires &lt;strong&gt;massive investment&lt;/strong&gt; by mobile operators&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;mmWave radios&lt;/li&gt;
      &lt;li&gt;Massive MIMO&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;emerging-research-vision-beyond-5g-b5g&quot;&gt;Emerging Research Vision Beyond 5G (B5G)&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;High-bandwidth&lt;/li&gt;
  &lt;li&gt;Large number&lt;/li&gt;
  &lt;li&gt;Very realiable&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/33HAJxm.png&quot; alt=&quot;b5g&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Intelligent connected and moving machines
    &lt;ul&gt;
      &lt;li&gt;Massive mobile AR/VR/MR galsses&lt;/li&gt;
      &lt;li&gt;Very large fleets of autonomous vehicles&lt;/li&gt;
      &lt;li&gt;Cooperating drone swarms&lt;/li&gt;
      &lt;li&gt;Collabortive moving robots&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;research-challenges-beyond-5g&quot;&gt;Research Challenges Beyond 5G&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Access supply has been well-studied in the past
    &lt;ul&gt;
      &lt;li&gt;but implication of &lt;strong&gt;user demand remain largely unexplored&lt;/strong&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Rethink wireless system design and content delivery for better matching the irregular user demand with the network access suplly in 5G systems&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Proposed solution&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;dynamic and mobile network infrastructures&lt;/strong&gt; that intelligently leverage provisional and personal radio access equipment
        &lt;ul&gt;
          &lt;li&gt;Offer truly flexible and &lt;em&gt;on-demand&lt;/em&gt; network architecture &lt;strong&gt;by involving operator&lt;/strong&gt;- and user-owned connected machines without the associated high costs&lt;/li&gt;
          &lt;li&gt;Employ &lt;strong&gt;mobile base stations&lt;/strong&gt; equipped with high-rate (e.g., mmWave) radio access capabilities&lt;/li&gt;
          &lt;li&gt;Leverage multi-radio uplink, downlink, direct device-to-device (D2D) links, as well as &lt;strong&gt;vehicle- and drone-assisted access&lt;/strong&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;expected-impact&quot;&gt;Expected Impact&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;u&gt;Breakthrough goal&lt;/u&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;reliable people-aware connectivity&lt;/strong&gt; where  space-time supply and demand may be shaped &lt;em&gt;opportunistically&lt;/em&gt;
        &lt;ul&gt;
          &lt;li&gt;User-owned machines (high-end wearables, cars, drones, etc.)&lt;/li&gt;
          &lt;li&gt;take  a more active role in &lt;strong&gt;5G+ service provisioning&lt;/strong&gt; (especially in &lt;em&gt;partial coverage&lt;/em&gt; situations
            &lt;ul&gt;
              &lt;li&gt;Functional disparity between the network and the user equipment is rapidly becoming blurred&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;u&gt;Theoretical benefits&lt;/u&gt;
    &lt;ul&gt;
      &lt;li&gt;Orders of magnitude better &lt;strong&gt;network capacity scaling&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;Number of base stations: K&lt;/li&gt;
          &lt;li&gt;Min number of antennas : n&lt;/li&gt;
          &lt;li&gt;Avaliable bandwidth : W&lt;/li&gt;
          &lt;li&gt;Network capacity = $K \times n \times W \times log(SNR)$&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;u&gt;Practical benefits&lt;/u&gt;
    &lt;ul&gt;
      &lt;li&gt;clearly noticeable more stable and smoother &lt;strong&gt;user connectivity experience&lt;/strong&gt;&lt;/li&gt;
      &lt;li&gt;This research accentuates the &lt;strong&gt;importance of people&lt;/strong&gt; as an integral component of beyond-5G system infrastructure with multiple impacts in &lt;strong&gt;&lt;em&gt;industry&lt;/em&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;em&gt;education&lt;/em&gt;&lt;/strong&gt;, and &lt;strong&gt;&lt;em&gt;community outreach&lt;/em&gt;&lt;/strong&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;
</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-13-Vehicular-and-Aerial-Communications.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-13-Vehicular-and-Aerial-Communications.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 12 - Ad hoc networks</title>
        <description>&lt;h1 id=&quot;ad-hoc-networks&quot;&gt;Ad hoc networks&lt;/h1&gt;

&lt;h2 id=&quot;cellular-and-ad-hoc-wireless-networks&quot;&gt;Cellular and ad-hoc wireless networks&lt;/h2&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Cellular networks&lt;/th&gt;
      &lt;th&gt;Ad-hoc wireless network&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;Fixed infrastructure&lt;/td&gt;
      &lt;td&gt;No infrastructure&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Single-hop wireless links&lt;/td&gt;
      &lt;td&gt;Multi-hop wireless links&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Guaranteed CBR bandwidth (voice traffic)&lt;/td&gt;
      &lt;td&gt;Shared radio channel (data traffic)&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Initially, circuit-switched&lt;/td&gt;
      &lt;td&gt;Initially, packet-switched&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;High cost and time of deployment&lt;/td&gt;
      &lt;td&gt;Very quick and cost-effective&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Reuse of frequency via channel reuse&lt;/td&gt;
      &lt;td&gt;Dynamic frequency sharing&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Bandwidth reservation is achieved easily&lt;/td&gt;
      &lt;td&gt;Complex MAC layer&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Nowadays applications: civilian, commercial&lt;/td&gt;
      &lt;td&gt;Nowadays applications: military, rescue&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;High cost of network maintenance&lt;/td&gt;
      &lt;td&gt;Maintenance operations are built-in&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Low complexity of mobile devices&lt;/td&gt;
      &lt;td&gt;Intelligent mobile devices are required&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Widely deployed, evolves&lt;/td&gt;
      &lt;td&gt;Still under development in commercial sector&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;h2 id=&quot;application-of-ad-hoc-wireless-network&quot;&gt;Application of ad-hoc wireless network&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;applications
    &lt;ul&gt;
      &lt;li&gt;military applications&lt;/li&gt;
      &lt;li&gt;collaborative and distributed computing&lt;/li&gt;
      &lt;li&gt;emergency and rescue operations&lt;/li&gt;
      &lt;li&gt;mesh networks&lt;/li&gt;
      &lt;li&gt;wireless sensor networks&lt;/li&gt;
      &lt;li&gt;hybrid cellular / ad-hoc wireless networks&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;why ?
    &lt;ul&gt;
      &lt;li&gt;quick depolyment&lt;/li&gt;
      &lt;li&gt;inexpensive deployment and operation&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;technical-challenges&quot;&gt;Technical challenges&lt;/h2&gt;

&lt;h3 id=&quot;medium-access-scheme&quot;&gt;Medium Access Scheme&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;MAC usded for shared use of the transmission medium&lt;/li&gt;
  &lt;li&gt;performance depends on MAC protocol&lt;/li&gt;
  &lt;li&gt;chanllenges
    &lt;ul&gt;
      &lt;li&gt;distribution operation&lt;/li&gt;
      &lt;li&gt;maximum throughput&lt;/li&gt;
      &lt;li&gt;minimum access delay&lt;/li&gt;
      &lt;li&gt;fairness&lt;/li&gt;
      &lt;li&gt;real-time trafiic support&lt;/li&gt;
      &lt;li&gt;power control capabilities&lt;/li&gt;
      &lt;li&gt;use of directional antennas&lt;/li&gt;
      &lt;li&gt;hidden/exposed terminal problems&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;routing&quot;&gt;Routing&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;responsible for
    &lt;ul&gt;
      &lt;li&gt;determining a feasible path&lt;/li&gt;
      &lt;li&gt;discovering, storing, and exchanging routing information&lt;/li&gt;
      &lt;li&gt;gathering information about a path breaks and updating route information accordingly&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Challenges
    &lt;ul&gt;
      &lt;li&gt;Mobility&lt;/li&gt;
      &lt;li&gt;Bandwidth constraints&lt;/li&gt;
      &lt;li&gt;Resource constraints&lt;/li&gt;
      &lt;li&gt;Errorneous transmission  medium&lt;/li&gt;
      &lt;li&gt;Location-dependent contention&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;requirements on a routing protocol in ad-hoc networks
    &lt;ul&gt;
      &lt;li&gt;minimum route acquisition delay&lt;/li&gt;
      &lt;li&gt;Quick route configuration&lt;/li&gt;
      &lt;li&gt;loop-free&lt;/li&gt;
      &lt;li&gt;distributed routing&lt;/li&gt;
      &lt;li&gt;low overhead&lt;/li&gt;
      &lt;li&gt;scalabiltiy&lt;/li&gt;
      &lt;li&gt;privacy&lt;/li&gt;
      &lt;li&gt;support for time-sensitive traffic&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;multicasting&quot;&gt;Multicasting&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;http://www.steves-internet-guide.com/wp-content/uploads/Unicast-Broadcast-Multicast.jpg&quot; alt=&quot;Unicast-Broadcast-Multicast&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Multicasting is an important feature in wireless ad-hoc networks:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;search and rescue operations: distribution of commands&lt;/li&gt;
      &lt;li&gt;military applications: distribution of command&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Why not to adapt something from fixed networks (CBT, PIM, DVMRP)&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;core base trees (CBT), distance vector multicast routing protocol (DVMRP), etc.&lt;/li&gt;
      &lt;li&gt;mobility of nodes changes the topology of the network! Trees are unstable!&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;There are following challenges in ad-hoc environment for multicasting:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Fast recovery;&lt;/li&gt;
      &lt;li&gt;Control overhead;&lt;/li&gt;
      &lt;li&gt;Efficient group management;&lt;/li&gt;
      &lt;li&gt;Scalability;&lt;/li&gt;
      &lt;li&gt;Security.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;transport-layer-protocol&quot;&gt;Transport Layer Protocol&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Major function of connection-based transport layer protocol:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;setting up and maintaining end-to-end connection&lt;/li&gt;
      &lt;li&gt;reliable end-to-end delivery of data packets&lt;/li&gt;
      &lt;li&gt;flow control&lt;/li&gt;
      &lt;li&gt;congestion control&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Why not to go with UDP&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;does not perform &lt;em&gt;flow and congestion control&lt;/em&gt; and &lt;em&gt;reliable&lt;/em&gt; end-to-end transfer;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Performance degradation stems from&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;high error rate&lt;/li&gt;
      &lt;li&gt;frequent path breaks&lt;/li&gt;
      &lt;li&gt;presence of ‘old’ routing information&lt;/li&gt;
      &lt;li&gt;network partitioning&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;quality-of-service-provisioning&quot;&gt;Quality of Service provisioning&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;QoS&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;traffic performance in the network&lt;/li&gt;
      &lt;li&gt;service support performance&lt;/li&gt;
      &lt;li&gt;service operability performance&lt;/li&gt;
      &lt;li&gt;service security performance&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;To satisfy QoS&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;use values of traffic engineering variables that constitute the so-called Grade of Service (GoS)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Provision of QoS requires:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;negotiation between the host and a network&lt;/li&gt;
      &lt;li&gt;resource reservation schemes&lt;/li&gt;
      &lt;li&gt;priority scheduling&lt;/li&gt;
      &lt;li&gt;call admission control&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;self-organization&quot;&gt;Self-organization&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Self-organization is the main attractive property of ad-hoc networks.&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;To perform self-organization the following things are required:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;neighbour discovery&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;first phase when a node switches on;&lt;/li&gt;
          &lt;li&gt;a node should gather network information (transmission of reception of discovery packets).&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;topology organization&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;every nodes gathers information about the entire network (a part of);&lt;/li&gt;
          &lt;li&gt;construct and maintain the network topology.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;topology reorganization&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;when links break, nodes switch off etc&lt;/li&gt;
          &lt;li&gt;requires periodic or aperiodic exchange of topology information.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;security&quot;&gt;Security&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Ad hoc are more vlunerable to attacks because&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;lack of central coordination&lt;/li&gt;
      &lt;li&gt;shared wireless medium&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Two types of attacks&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;passive attacks&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;malicious nodes attempt to obtain information relayed in the network;&lt;/li&gt;
          &lt;li&gt;no damage to operation of the network, just capture if information&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;active attacks&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;&lt;strong&gt;external attacks:&lt;/strong&gt; attacks executed by nodes outside the network;&lt;/li&gt;
          &lt;li&gt;&lt;strong&gt;internal attacks:&lt;/strong&gt; attacks executed by nodes belonging to the same network.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Denial of Service&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Resource consumption&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Energy Depletion&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;to deplete the power of the node relaying the traffic through them.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Buffer overflow&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;fill the routing table with ’bad’ entries to consume the buffer space of the target node.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Host impersonalization&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Infomration disclosure&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Interference&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;addressing-and-service-discovery&quot;&gt;Addressing and service discovery&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Addresses&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Global unique address&lt;/li&gt;
      &lt;li&gt;autoconfiguration of address&lt;/li&gt;
      &lt;li&gt;Duplicate address detection mechanism&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Meaningful features for ad-hoc network&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;automatic service advertisement mechanism
        &lt;ul&gt;
          &lt;li&gt;should allow to identify the &lt;strong&gt;current&lt;/strong&gt; location of the service&lt;/li&gt;
          &lt;li&gt;it is not possible to assume static service locations in ad hoc networks.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;integration of service discovery protocols and routing protocols
        &lt;ul&gt;
          &lt;li&gt;may allow to easily find the necessary service in a networ&lt;/li&gt;
          &lt;li&gt;may violate the traditional design objectives of the routing protocol&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;energy-management&quot;&gt;Energy management&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;can be done&lt;/li&gt;
  &lt;li&gt;shaping the energy discharge pattern&lt;/li&gt;
  &lt;li&gt;use routes with minimal total energy consumption&lt;/li&gt;
  &lt;li&gt;use special task scheduling schemes&lt;/li&gt;
  &lt;li&gt;proper handling the processor and interface devices&lt;/li&gt;
  &lt;li&gt;can be achieved by
    &lt;ul&gt;
      &lt;li&gt;Transmission power management&lt;/li&gt;
      &lt;li&gt;Battery energy management&lt;/li&gt;
      &lt;li&gt;Processor power management&lt;/li&gt;
      &lt;li&gt;Interface power management&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;scalability&quot;&gt;Scalability&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Testbeds and operational ad hoc networks made so far:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;contain only a limited number of nodes&lt;/li&gt;
      &lt;li&gt;may not be good examples of ad hoc performance&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;What we may expect in real implementations&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;performance of ad-hoc network degrades drastically with the increase of the number of nodes&lt;/li&gt;
      &lt;li&gt;one may expect commercial realization of, at least, thousands of nodes&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;deployment&quot;&gt;Deployment&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Low cost&lt;/strong&gt; : no cables, no configuration, no maintenance&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Incremental&lt;/strong&gt; : functioning starts immediately after minimum configuration is done&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;short time&lt;/strong&gt; : no cables, no configuration, no maintenance&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;reconfigurability&lt;/strong&gt; :   no cables, no configuration, no maintenance&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;example--data-linknetworktransport&quot;&gt;Example : data-link/network/transport&lt;/h2&gt;

&lt;h3 id=&quot;data-link-layer-maca&quot;&gt;Data-link layer MACA&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;MACA&lt;/strong&gt;:
    &lt;ul&gt;
      &lt;li&gt;stands for MAC protocol for ad hoc networks.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;major facts&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;contention-based without reservation and scheduling&lt;/li&gt;
      &lt;li&gt;MACA was prposed as an extension for CSMA/CA protocol&lt;/li&gt;
      &lt;li&gt;was further extended and adopted for IEEE 802.11&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;CSMA
    &lt;ul&gt;
      &lt;li&gt;the sender sense the channel for the carrier signal;&lt;/li&gt;
      &lt;li&gt;if the carrier is present it retries to sense the channel after some time (exp. back-off);&lt;/li&gt;
      &lt;li&gt;if not, the sender transmits a packet&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Shortcoming for CSMA/CA
    &lt;ul&gt;
      &lt;li&gt;hidden terminal problem leading to frequent collisions;&lt;/li&gt;
      &lt;li&gt;exposed terminal problem leading to worse bandwidth utilization&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;MACA avoids hidden and exposed terminal problems using the RTS-CTS.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/w88AJEK.png&quot; alt=&quot;RTS-CTS&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;RTS and CTS packets carry the expected duration of transmission;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;a node near the sender&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;that hearing RTS do not transmit for a time to receive CTS;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;a node near the receiver&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;after hearing CTS differs its transmission&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;if the neighbor hears the RTS only&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;it is free to transmit&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;network-layer-location-aided-routing-lar&quot;&gt;Network layer: Location Aided routing (LAR)&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;use the location information&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;reactive protocol&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;Two zones
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Expected Zone&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;a geographical zone in which the location of the terminal is predicted based on:
            &lt;ul&gt;
              &lt;li&gt;location of the terminal in the past&lt;/li&gt;
              &lt;li&gt;mobility information of the terminal&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Request Zone&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;a geographical zone within which control packets are allowed to propagate
            &lt;ul&gt;
              &lt;li&gt;area is determined by the sender of the data packet&lt;/li&gt;
              &lt;li&gt;control packets are forwarded by node within a RequestZone only&lt;/li&gt;
              &lt;li&gt;if the node is not found using the first RequestZone, the size of RequestZone is increased.&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Nodes decide whether to forward or discard packets based on two algorithms:
    &lt;ul&gt;
      &lt;li&gt;LAR type 1
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/ihS9gNr.png&quot; alt=&quot;type1&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;LAR type 2
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/Dqz46uQ.png&quot; alt=&quot;type2algo&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;transport-layer-protocols-split-tcp&quot;&gt;Transport-layer protocols: Split TCP&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;TCP major problems&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;degradation of throughput with increase of path length&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/ylD7NOK.png&quot; alt=&quot;TCP-1&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;unfairness among TCP flows&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/xs3DqE4.png&quot; alt=&quot;TCP2&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;split-tcp provides the solution by splitting the TCP functionality into two part
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;congestion control&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;local phenomenon due to high contention for resources&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;end-to-reliability&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;end-to-end phenomenon&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/opQoko0.png&quot; alt=&quot;split-tcp&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Split TCP:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;splits the connection into a set of concatenated TCP connections
    &lt;ul&gt;
      &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/8zJ5w0g.png&quot; alt=&quot;SPLIT-TCP-2&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;proxy node&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;terminating the connection from the sender/precessor proxy node;&lt;/li&gt;
      &lt;li&gt;setting up a connection with receiver/successor node.&lt;/li&gt;
      &lt;li&gt;are chosen using the distributed algorithm
        &lt;ul&gt;
          &lt;li&gt;packet traversed n hops - behave as a proxy&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Transmission control at the TCP sender window is split&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;end-to-end CW
        &lt;ul&gt;
          &lt;li&gt;updated according to arrival of end-to-end ACKs&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;local CW: (local CW ≤ end-to-end CW)
        &lt;ul&gt;
          &lt;li&gt;updated according to arrival of local ACKs (LACKs) from the next node.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Proxy node behaves&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;it maintains local CW governing transmission in a segment;&lt;/li&gt;
      &lt;li&gt;when packet arrives from predecessor the LACK is sent back;&lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;arrived packet is buffered;&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;the buffered packet is forwarded to the next node.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/eVyNi82.png&quot; alt=&quot;split-tcp-flow&quot; /&gt;&lt;/p&gt;
</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-12-Ad-hoc-networks.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-12-Ad-hoc-networks.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 11 - WPANWBANs:Bluetooth and BLE</title>
        <description>&lt;h1 id=&quot;wpanwbansbluetooth-and-ble&quot;&gt;WPANWBANs:Bluetooth and BLE&lt;/h1&gt;

&lt;h2 id=&quot;panban&quot;&gt;PAN/BAN&lt;/h2&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/4r8hX15.png&quot; alt=&quot;PAN/BAN&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/3latrrV.png&quot; alt=&quot;range&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/E17GF0L.png&quot; alt=&quot;Usage Scenarios of ban/pan&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;ieee-80215&quot;&gt;IEEE 802.15&lt;/h2&gt;

&lt;p&gt;Discussed in Chapter10&lt;/p&gt;

&lt;h2 id=&quot;banpan-technical-challenges-and-design-issues&quot;&gt;BAN/PAN technical challenges and design issues&lt;/h2&gt;

&lt;h3 id=&quot;technical-challenges&quot;&gt;Technical challenges&lt;/h3&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Problems&lt;/th&gt;
      &lt;th&gt;Detail&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;Address is not a physical location&lt;/td&gt;
      &lt;td&gt;The station is not always stationary. The address does not give an information about location&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Dynamically changed topology&lt;/td&gt;
      &lt;td&gt;The network connectivity is partial at times&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Medium boundaries are soft&lt;/td&gt;
      &lt;td&gt;The communication range cannot be determined precisely.&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Erroneous medium&lt;/td&gt;
      &lt;td&gt;BER in wireless network is about 10&lt;sup&gt;-4&lt;/sup&gt;compared to 10&lt;sup&gt;-9&lt;/sup&gt; in fixed networks&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Hidden terminal problem&lt;/td&gt;
      &lt;td&gt;Some nodes should (not) be allowed to communicate at a certain time&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;h3 id=&quot;design-issues&quot;&gt;Design Issues&lt;/h3&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Ceriteria to be meet&lt;/th&gt;
      &lt;th&gt;Detail&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;Operational simplicity: BAN/PAN&lt;/td&gt;
      &lt;td&gt;Mobile use MUST be able to quickly set up and access network services in a SIMPLE manner&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Power efficienct operation: BAN/PAN&lt;/td&gt;
      &lt;td&gt;The main resource of MT is the power: power saving features&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Licence-free operation: PAN&lt;/td&gt;
      &lt;td&gt;Lost cost installation is required for widespread usage, e.g., ISM band&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Tolerance to interference: BAN/PAN&lt;/td&gt;
      &lt;td&gt;There are a lot of technologies operating in ISM band causing interference between them.&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Security: PAN&lt;/td&gt;
      &lt;td&gt;PAN is vulnerable to different attacks&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Compatibility: BAN/PAN&lt;/td&gt;
      &lt;td&gt;Compatibility with other technologies and applications is required for a commercial success.&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;h2 id=&quot;bluetooth-general-description&quot;&gt;Bluetooth general description&lt;/h2&gt;

&lt;h3 id=&quot;what-bluetooth-appears&quot;&gt;What bluetooth appears?&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;the need for personal services to communicate directly without infrastructure&lt;/li&gt;
  &lt;li&gt;PAN/BAN paradigms have appeared&lt;/li&gt;
  &lt;li&gt;Bluetooth is the most successful standard for BAN/PAN&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;bluetooth-specifications&quot;&gt;Bluetooth specifications&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Basic structure&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Core specifications&lt;/strong&gt; : DL and PHY PROTOCOLS&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Profiles&lt;/strong&gt; : applications&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Functions performed by the stack&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;locating/connecting devices,exchanging data&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Functions Logically divided into three groups&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;transport protocol group&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;RF: radio and antenna;&lt;/li&gt;
          &lt;li&gt;baseband sublayer&lt;/li&gt;
          &lt;li&gt;ling mangager, logical link control and adaptation sublayers&lt;/li&gt;
          &lt;li&gt;host controller interface&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;middleware protocol group&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;RFCOMM, SDP, TCS&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;application group&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;profiles&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/9ndvvPL.png&quot; alt=&quot;Protocol stack of Bluetooth &quot; /&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;network-topologies&quot;&gt;Network Topologies&lt;/h2&gt;

&lt;h3 id=&quot;transport-protocol-grouptpg&quot;&gt;Transport Protocol Group(TPG)&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;locating services: allows devices to locate each other&lt;/li&gt;
  &lt;li&gt;creating, configuring, and managing wireless link&lt;/li&gt;
  &lt;li&gt;TPG aims
    &lt;ul&gt;
      &lt;li&gt;low power consumption&lt;/li&gt;
      &lt;li&gt;simplicity of operation&lt;/li&gt;
      &lt;li&gt;low cost of the communicating entity&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Three genreral choices were made for bluetooth
    &lt;ul&gt;
      &lt;li&gt;master-slave architecture (simplicity)&lt;/li&gt;
      &lt;li&gt;frequency hopping communication (tolerence to interference)&lt;/li&gt;
      &lt;li&gt;gateway-based large newtorking (extensions)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;piconet&quot;&gt;Piconet&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;consists of the master and slaves, initiator of the formation: master;&lt;/li&gt;
  &lt;li&gt;can have up to seven active(!!!) slaves at any time&lt;/li&gt;
  &lt;li&gt;each active slave of the piconet is a unique active member address BD_ADDR.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://www.researchgate.net/profile/Farhat_Saleemi2/publication/228990705/figure/fig1/AS:393606675353600@1470854552026/A-typical-Bluetooth-Piconet.png&quot; alt=&quot;A typical Bluetooth Piconet Â &quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;scatternets&quot;&gt;Scatternets&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Piconet may operate spatially&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;piconets can operate in the same area in the same time&lt;/li&gt;
      &lt;li&gt;each piconet is characterized by a unique master;&lt;/li&gt;
      &lt;li&gt;piconets hop independently with its own hopping sequences.&lt;/li&gt;
      &lt;li&gt;with more piconets added, probability of collision increases (frequency hopping).&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Only a few active devices in Piconet&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Bluetooth unit may operate as a slave in different piconets&lt;/li&gt;
      &lt;li&gt;Bluetooth unit may operate as a master in only one piconet!&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;DEFINITION&lt;/strong&gt;: A group of piconets between which connections exist is called a &lt;em&gt;scatternet&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://www.researchgate.net/profile/Xu_Cheng23/publication/4162479/figure/fig2/AS:667607342538754@1536181402464/A-Bluetooth-scatternet.png&quot; alt=&quot;A Bluetooth scatternet&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;transport-protocol-group&quot;&gt;Transport Protocol Group&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;It deals with
    &lt;ul&gt;
      &lt;li&gt;PHY layer&lt;/li&gt;
      &lt;li&gt;data-link layer&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Bluetooth radio
    &lt;ul&gt;
      &lt;li&gt;in ISM frequency&lt;/li&gt;
      &lt;li&gt;a variance of frequency modulation, GFSK&lt;/li&gt;
      &lt;li&gt;64Kbps voice channel&lt;/li&gt;
      &lt;li&gt;asynchronous data channel with peak rate of 1Mbps&lt;/li&gt;
      &lt;li&gt;FHSS(&lt;em&gt;Frequency-hopping spread spectrum&lt;/em&gt;) operating over the set of m = 79 channels each of width of 1MHz;&lt;/li&gt;
      &lt;li&gt;hops are made across all channels starting at 2.402GHz and stopping at 2.480GHz;&lt;/li&gt;
      &lt;li&gt;the transmit power of 1mW, extension to 100mW;&lt;/li&gt;
      &lt;li&gt;the nominal link range is up to 10m (1mW), can be extended to 100m (100mW).&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;baseband-sublayer&quot;&gt;Baseband sublayer&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;functions&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;hop selection&lt;/li&gt;
      &lt;li&gt;connection setup&lt;/li&gt;
      &lt;li&gt;medium access control&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Creating and maintaining piconets&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;the address of a device&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;three part 48 bit address
            &lt;ul&gt;
              &lt;li&gt;lower address part (LAP): used in piconet ID, error, security checking&lt;/li&gt;
              &lt;li&gt;reamining two parts are addresses assigned by manufacturer&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;the clock associated with a device&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;native clock : 28 bit clock&lt;/li&gt;
          &lt;li&gt;3200 times persecond (interval is 312.5 us)&lt;/li&gt;
          &lt;li&gt;3200 is twice the hopping rate (1600 hops/s)&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;organization-of-the-communication-channel&quot;&gt;Organization of the communication channel&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;Basic&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;the channel is divided into time slots of 625 μs&lt;/li&gt;
      &lt;li&gt;TDD &lt;em&gt;(Time-division Duplex )&lt;/em&gt;scheme is used where master and slave alternatively transmits&lt;/li&gt;
      &lt;li&gt;packet transmission is aligned with the beginning of the slot&lt;/li&gt;
      &lt;li&gt;slots are numbered according to the clock of the master&lt;/li&gt;
      &lt;li&gt;master starts its transmission in even-numbered slots, slave in odd-numbered slots only&lt;/li&gt;
      &lt;li&gt;slave is allowed to transmit only if in the preceding slot it received a packet from the master&lt;/li&gt;
    &lt;/ul&gt;

    &lt;p&gt;&lt;img src=&quot;https://i.imgur.com/4W1tE9b.png&quot; alt=&quot;Channel Organization&quot; /&gt;&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;state-operations-in-bluetooth&quot;&gt;State operations in Bluetooth&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/vDlLRJ5.png&quot; alt=&quot;State operations&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;selection-of-frequency-hopping-sequence&quot;&gt;Selection of frequency hopping sequence&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Hopping sequence: FSM&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;clock value&lt;/li&gt;
      &lt;li&gt;address&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Clock and address are different in different modes&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Connected State:&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;The clock value of unknown&lt;/li&gt;
          &lt;li&gt;the address of the device is known&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Inquiry State&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;address input to FSM is a inquiry address&lt;/li&gt;
          &lt;li&gt;at the time of inquiry, no device has information about the hopping sequence&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Paging State&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;The address of the paged device is entered in FSM&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;inquiry-state&quot;&gt;Inquiry State&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Essential state for bluetooth
    &lt;ul&gt;
      &lt;li&gt;any device which is initially in the &lt;em&gt;standby state&lt;/em&gt; enters the i&lt;em&gt;nquiry state&lt;/em&gt;&lt;/li&gt;
      &lt;li&gt;to collect &lt;em&gt;information&lt;/em&gt; about other Bluetooth devices in its neighborhood
        &lt;ul&gt;
          &lt;li&gt;infomration includes address and clock value of the master&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;The Inquiry proceeds as follows
    &lt;ul&gt;
      &lt;li&gt;master sends an inquiry packet on the inquiry hop sequence of frequencies
        &lt;ul&gt;
          &lt;li&gt;the common address is fed to the FSM&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;a device that wants to be discovered enters the inquiry state and listens for these packets&lt;/li&gt;
      &lt;li&gt;when inquiry message is received, responses with packet containing the device address.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/2GJgFAg.png&quot; alt=&quot;inquiry state&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;page-state&quot;&gt;Page State&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Why to enter and from which state&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;to invite other devices to join a piconet&lt;/li&gt;
      &lt;li&gt;to inquiry operation precedes this state&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Three substates&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;
        &lt;p&gt;&lt;strong&gt;Page sub-state&lt;/strong&gt;(master)&lt;/p&gt;

        &lt;ul&gt;
          &lt;li&gt;the master estimates the slave clock value&lt;/li&gt;
          &lt;li&gt;determines the hop sequence where the slave might be listening in the page scan mode&lt;/li&gt;
          &lt;li&gt;transmits the page message in preceding, estimated and following hop sequences&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;&lt;strong&gt;Page scan sub-state&lt;/strong&gt;(slave)&lt;/p&gt;

        &lt;ul&gt;
          &lt;li&gt;slave listens the channel for a page message&lt;/li&gt;
          &lt;li&gt;upon receiving the page message the salve enters the salve page response sub-state&lt;/li&gt;
          &lt;li&gt;slave sends page response message&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;&lt;strong&gt;Page response sub-state&lt;/strong&gt;&lt;/p&gt;

        &lt;ul&gt;
          &lt;li&gt;the master informs the salve about its clock and address&lt;/li&gt;
          &lt;li&gt;the salve calculates an offset to sychronize with the master clock&lt;/li&gt;
        &lt;/ul&gt;

        &lt;p&gt;&lt;img src=&quot;https://i.imgur.com/TNY482j.png&quot; alt=&quot;page-operation&quot; /&gt;&lt;/p&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;connected-state&quot;&gt;Connected State&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/N1Ty0bD.png&quot; alt=&quot;connceted state&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;packet-based-communication&quot;&gt;Packet-based communication&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Access code
    &lt;ul&gt;
      &lt;li&gt;contains the address of the piconet master&lt;/li&gt;
      &lt;li&gt;all packets exchanged on the channel are identified by the master’s identity&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Header
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;three bit active slave number&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;the maximum number of slaves in the piconet is 7;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;a one bit ACK/NACK field&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;to retransmit erroneously received frames;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;four bit packet type field:&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;to distinguish between payload types&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;eight bit header error check&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;to detect errors in the header&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Payload&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Depending on the payload size ONE, THREE, OR FIVE slots can be used for packet&lt;/p&gt;

    &lt;p&gt;&lt;img src=&quot;https://i.imgur.com/l7wUAmZ.png&quot; alt=&quot;Multiple slot&quot; /&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Above&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;single slots are used to transmits packets&lt;/li&gt;
      &lt;li&gt;frequencies are F(k), F(k+2), F(k+4), F(k+6) for transmission slots.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Middle&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;two slots are used to transmit a first packet&lt;/li&gt;
      &lt;li&gt;requency F(k+4), not F(k+3) is used for transmitting a packet&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Links in a piconet
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;asynchronous connectionless link (ACL)&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;default link that exists once the connection established&lt;/li&gt;
          &lt;li&gt;whenever a master would like to communicate, it does so&lt;/li&gt;
          &lt;li&gt;slave can only respond after the master’s transmission&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;syncrhonous connection-oriented link(SCO)&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;SCO link is a symmetric between master and a slave with &lt;em&gt;reserved bandwidth&lt;/em&gt;
            &lt;ul&gt;
              &lt;li&gt;&lt;em&gt;reserved bandwidth&lt;/em&gt;: just reserved time slots at regular intervals;&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
          &lt;li&gt;&lt;em&gt;why&lt;/em&gt;: high-priority and time-bound information such as video and audio.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Communication in a piconet
    &lt;ul&gt;
      &lt;li&gt;only between master and its slaves&lt;/li&gt;
      &lt;li&gt;is not possible between slaves&lt;/li&gt;
      &lt;li&gt;master does not route packets of its slaves&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;link-management-protocol&quot;&gt;Link Management Protocol&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;Functions&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;setting and maintaining the properties of the Bluetooth link&lt;/li&gt;
      &lt;li&gt;power management&lt;/li&gt;
      &lt;li&gt;security management&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Power Management&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Active mode&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;actively participates in the piconet&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Sniff mode&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;listen only certain slots&lt;/li&gt;
          &lt;li&gt;master commands the source to go to this mode&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Hold mode&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;slave temporarily does not support ACL packets on the channel&lt;/li&gt;
          &lt;li&gt;capacity is made available for paging, inquiring, or attending another piconets&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Park Mode&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;very low-power mode allowing master to have more than 7 slaves&lt;/li&gt;
          &lt;li&gt;slave is given an eight bit parked member address, remains synchronized, no active address&lt;/li&gt;
          &lt;li&gt;a message to the parked station is sent over broadcast channel&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Security&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;key management&lt;/strong&gt; : to share and distribute keys&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;authentication&lt;/strong&gt; : to know the communicating entity&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;encryption&lt;/strong&gt;: performed for packet payloads&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Error detection and correction&lt;/p&gt;
    &lt;ul&gt;
      &lt;li&gt;detect : checksum is added to a packet&lt;/li&gt;
      &lt;li&gt;correct: FEC  with two rates (1/2,1/3): flexible for payload, strict (1/3) for header;&lt;/li&gt;
      &lt;li&gt;correct: ARQ with ACKs and NACKs&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/a7F1TgJ.png&quot; alt=&quot;ARQ&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;host-controller-interface&quot;&gt;Host controller interface&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;Functionality&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;interface layer between the layers above LMP and lower layers&lt;/li&gt;
      &lt;li&gt;provides access to Bluetooth hardware capabilities&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;logical-link-control-and-adaptation-protocol-l2cap&quot;&gt;Logical Link control and adaptation protocol (L2CAP)&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Functionality
    &lt;ul&gt;
      &lt;li&gt;abstraction of higher layer protocols via multiplexing of protocols&lt;/li&gt;
      &lt;li&gt;segments and resembles packets to combot BER&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/t6mwrYI.png&quot; alt=&quot;L2CAP&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;middleware-protocols&quot;&gt;Middleware protocols&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;provides standard interface to applications&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Service discovery protocol&lt;/strong&gt;(SDP)
        &lt;ul&gt;
          &lt;li&gt;Fully automatic of request-response type&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;RFCOMM&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;virtual serial port, any application that use serial port can work seamlessly&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;IrDA interoperability protocols&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;&lt;em&gt;IrDA object exchange (IrOBEX)&lt;/em&gt; used for exchanging objects between two devices;&lt;/li&gt;
          &lt;li&gt;&lt;em&gt;Infrared Mobile Communication protocol (IrMC&lt;/em&gt;) used for synchronization&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Telephony control specification&lt;/strong&gt; (TCS)
        &lt;ul&gt;
          &lt;li&gt;audio signal are carried out over SCO at 64kbps&lt;/li&gt;
          &lt;li&gt;defines
            &lt;ul&gt;
              &lt;li&gt;call control&lt;/li&gt;
              &lt;li&gt;group management&lt;/li&gt;
              &lt;li&gt;connectionless TCS&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;bluetooth-profiles&quot;&gt;Bluetooth Profiles&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;What and Why
    &lt;ul&gt;
      &lt;li&gt;provides standard to implement a specifc user function&lt;/li&gt;
      &lt;li&gt;to allow interoperability between different Bluetooth implementations&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;13 profiles are calssifiled into
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;Generic Profiles&lt;/strong&gt;&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Telephony Profiles&lt;/strong&gt;&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Networking Profiles&lt;/strong&gt;&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Serial and object exchange profiles&lt;/strong&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;advantage-and-shortcoming-of-bt&quot;&gt;Advantage and shortcoming of BT&lt;/h2&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Advantage&lt;/th&gt;
      &lt;th&gt;Shortcomings&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;fill the gap in networking on scales shorter than WLAN&lt;/td&gt;
      &lt;td&gt;Does not provide support for routing&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;exceptionally well standardized&lt;/td&gt;
      &lt;td&gt;No support of handover&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt; &lt;/td&gt;
      &lt;td&gt;Master is a bottleneck&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt; &lt;/td&gt;
      &lt;td&gt;Bluetooth has operates in ISM band like 802.11b WLAN&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt; &lt;/td&gt;
      &lt;td&gt;Complexity grows&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt; &lt;/td&gt;
      &lt;td&gt; &lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;h2 id=&quot;bluetooth-low-energyble&quot;&gt;Bluetooth low energy(BLE)&lt;/h2&gt;

&lt;h3 id=&quot;why-ble&quot;&gt;why BLE&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;bluetooth is doing extremely well&lt;/li&gt;
  &lt;li&gt;bluetooth is good for industry&lt;/li&gt;
  &lt;li&gt;very robust to interference , frequency hopping&lt;/li&gt;
  &lt;li&gt;compete with Zigbee&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;definiition-and-benefits&quot;&gt;Definiition and benefits&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;definition
    &lt;ul&gt;
      &lt;li&gt;open, low energy and short range wireless technology&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;benefits (good for small, discrete data transfers)
    &lt;ul&gt;
      &lt;li&gt;low power consumption&lt;/li&gt;
      &lt;li&gt;small size&lt;/li&gt;
      &lt;li&gt;connectivity to mobile phone&lt;/li&gt;
      &lt;li&gt;low cost, robust, efficient&lt;/li&gt;
      &lt;li&gt;multi-vendor interoperability&lt;/li&gt;
      &lt;li&gt;global availability, license free&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;temperature, time, pressure, speed sensing&lt;/li&gt;
  &lt;li&gt;2mAh per day&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;constraints&quot;&gt;Constraints&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Imposed constraints&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;reuse as much Bluetooth RF as possible&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;only need 60% RF silicon area compared to Bluetooth&lt;/li&gt;
          &lt;li&gt;can use the same antenna as Bluetooth&lt;/li&gt;
          &lt;li&gt;can TDM with BT&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;reuse as much BluetoothL2CAP as possible&lt;/strong&gt;&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;reuse as much Bluetooth hHCI as possible&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;same HCI physicial interfaces&lt;/li&gt;
          &lt;li&gt;same HCI packet formats&lt;/li&gt;
          &lt;li&gt;same HCI drivers in OS&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Design Goals&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;lowest possible power operation&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;turning radio off for as much of the time as possible&lt;/li&gt;
          &lt;li&gt;reducing the &lt;strong&gt;&lt;em&gt;complexity&lt;/em&gt;&lt;/strong&gt; of a single mode device to almost nothing
            &lt;ul&gt;
              &lt;li&gt;reduced memeory requirement
                &lt;ul&gt;
                  &lt;li&gt;reduced leackage current
                    &lt;ul&gt;
                      &lt;li&gt;battery lifetimes !&lt;/li&gt;
                    &lt;/ul&gt;
                  &lt;/li&gt;
                &lt;/ul&gt;
              &lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
          &lt;li&gt;80% to 60% of traditional BT chips&lt;/li&gt;
          &lt;li&gt;designing a connectionless data model&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;lowest possible latency&lt;/strong&gt;&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;widest possible range of interoperable devices and application&lt;/strong&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;acheiving-low-power&quot;&gt;Acheiving low power&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;By keeping the radio off&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;lower standby time&lt;/li&gt;
      &lt;li&gt;faster connection&lt;/li&gt;
      &lt;li&gt;lower peak power&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;BLE only use 3 advertising channels(vs. 16-32channlels)&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;RF is on for 1.2ms  vs 22.5ms&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Idle current is dominated by deep sleep current&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;sensor type send data less often (0.5 to 4s)&lt;/li&gt;
      &lt;li&gt;RF current is neligible due to low duty cycles&lt;/li&gt;
      &lt;li&gt;Protocols&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Faster connections&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;a device that is advertising is able to connect to a scanning device&lt;/li&gt;
      &lt;li&gt;The devices can connect and sendand acknowledge data in &lt;em&gt;3 ms&lt;/em&gt;&lt;/li&gt;
      &lt;li&gt;vs classic BT 100ms&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Lower Peak Power&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;BLE uses relaxed RF parameters
        &lt;ul&gt;
          &lt;li&gt;GFSK modulation index increased(From 0.35 to 0.55)&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Packet length restricted
        &lt;ul&gt;
          &lt;li&gt;Together with GFSK gives lowest complexity transmitter / recevier&lt;/li&gt;
          &lt;li&gt;This results in a lower peak power&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;data-rate-and-throughput&quot;&gt;Data rate and throughput&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;NOT ABOUT data rate/ throughput&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;about 260kbps maximum data rate&lt;/li&gt;
      &lt;li&gt;concentrates more on lowest possible poewr consumption&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;ABOUT transferring state&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;small, infrequent bits of data&lt;/li&gt;
      &lt;li&gt;owest possible poewr consumption&lt;/li&gt;
      &lt;li&gt;lowest latency&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;phy-layer&quot;&gt;PHY Layer&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Split the 2.4Ghz ISM band into 40 channels&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;3 Advertising Channels&lt;/li&gt;
      &lt;li&gt;37 Data channels&lt;/li&gt;
      &lt;li&gt;$f_n = 2402+2n$Mhz&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;GFSK Modulation&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Modulation index 0.5, better range than the classic
        &lt;ul&gt;
          &lt;li&gt;allows use of fewer advertising channels&lt;/li&gt;
          &lt;li&gt;reduces power consumption&lt;/li&gt;
          &lt;li&gt;increases connection speeds&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Can reuse existing RF parts in BTchip
        &lt;ul&gt;
          &lt;li&gt;minimal additional cost in dual-mode chips&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;master-slave-topology&quot;&gt;Master/ slave topology&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Master is typically the central device&lt;/li&gt;
  &lt;li&gt;Salve is typically the peripheral device&lt;/li&gt;
  &lt;li&gt;Slave is very VEry power sensitive
    &lt;ul&gt;
      &lt;li&gt;power consumption&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Master is time sensitive
    &lt;ul&gt;
      &lt;li&gt;latency&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;separate-adveritisng-dand-data-channels&quot;&gt;Separate adveritisng dand data channels&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Data channels&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;used to transfer reliable data robustly&lt;/li&gt;
      &lt;li&gt;adaptive frequency hopping over &lt;em&gt;37 channles&lt;/em&gt;&lt;/li&gt;
      &lt;li&gt;fast acknowledgement scheme&lt;/li&gt;
      &lt;li&gt;if data doesnt get through, resent on next freqeuncy&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Advertising channels&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;402, 2426, 2480Mhz.
        &lt;ul&gt;
          &lt;li&gt;it would avoid interference with Wi-Fi traffic&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Used by peripherals to advertise presence
        &lt;ul&gt;
          &lt;li&gt;when first power on&lt;/li&gt;
          &lt;li&gt;why they have data to send - central devices connect and get data&lt;/li&gt;
          &lt;li&gt;just to broadcast data to anybody scanning&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;security&quot;&gt;Security&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;uses AES-128 with CCM encryption engine&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Use Key Distribution to share various keys&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Identity Resolving Key is used for privacy&lt;/li&gt;
      &lt;li&gt;Signing Resolving Key provides fast authentication without encryption&lt;/li&gt;
      &lt;li&gt;Long Term Key is used for encryption&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Pairing encrypts the link using a Temporary Key&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;derived from passkey, NFC pairing, public key exchange (v1.1);&lt;/li&gt;
      &lt;li&gt;then distribute keys.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Asymmetric key model:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;slave gives keys to master with a diversifier&lt;/li&gt;
      &lt;li&gt;slave can then recover keys from the diversifier&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;encryption&quot;&gt;Encryption&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;RFC 3610 based AES-128 encryption:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Counter Mode Cipher Block Chaining Message Authentication Code
        &lt;ul&gt;
          &lt;li&gt;Counter mode CBC-MAC = CCM.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Each new data packet has a Message Integrity Check:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;39 bit counter, 1 direction bit;&lt;/li&gt;
      &lt;li&gt;64 bit Initialization Vector 32 bits contributed by each device;&lt;/li&gt;
      &lt;li&gt;MIC is 32 bits in length&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;MIC is separate from the CRC&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;CRC can allow immediate acknowledgment;&lt;/li&gt;
      &lt;li&gt;packet is only sent to host after MIC checked&lt;/li&gt;
      &lt;li&gt;lowest peak power&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;survaviblity&quot;&gt;Survaviblity&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Robustness to Vital for Bluetooth&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;it must be robust against 2.4 GHz ISM band interference&lt;/li&gt;
      &lt;li&gt;Wi-Fi, 802.15.4, X-10, proprietary, etc&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Coexistence is Vital&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;should not interfere with existing Wi-Fi infrastructure/ad-hoc network;&lt;/li&gt;
      &lt;li&gt;Adaptive Frequency Hopping is needed&lt;/li&gt;
      &lt;li&gt;FCC recognizes this as the best way to avoid interference;&lt;/li&gt;
      &lt;li&gt;Discovering devices / connecting devices should not break Wi-Fi&lt;/li&gt;
      &lt;li&gt;It must not affect Bluetooth headsets&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;power-consumption&quot;&gt;Power Consumption&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Relative consumption&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Sleep time is way more longer&lt;/li&gt;
      &lt;li&gt;power mode 1 : 3us wake up time consuming 235uA;&lt;/li&gt;
      &lt;li&gt;power mode 2: wake up via sleep timer consuming 0.9uA&lt;/li&gt;
      &lt;li&gt;power mode 3: via external interrupt consuming 0.4uA&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Power consumption during the connection event:&lt;/strong&gt;&lt;/p&gt;
    &lt;ul&gt;
      &lt;li&gt;between connection events: power mode 2&lt;/li&gt;
      &lt;li&gt;turning off: voltage regulator, processor, oscillator&lt;/li&gt;
      &lt;li&gt;active: sleep timer, RAM and registers retained&lt;/li&gt;
      &lt;li&gt;going active: via I/O interrupt or expiring sleep timer&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;
</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-11-WPANWBANs-Bluetooth-and-BLE.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-11-WPANWBANs-Bluetooth-and-BLE.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 10 - WPAN/WBANs.Zigebee</title>
        <description>&lt;h1 id=&quot;wpanwbanszigebeem&quot;&gt;WPAN/WBANs.Zigebee.m&lt;/h1&gt;

&lt;h2 id=&quot;ieee-80215-wg&quot;&gt;IEEE 802.15 WG&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Specify WPAN standard&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Wireless Personal Area Network&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TG 1 802.15.1: WPAN/Bluetooth&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;defines PHY and MAC of Bluetooth&lt;/li&gt;
      &lt;li&gt;standard issued in 2002 and 2005&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TG 2: 802.15.2: coexistence&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;coexistence of WPANs with other networks in unlicensed band;&lt;/li&gt;
      &lt;li&gt;EEE 802.15.2-2003 published in 2003 and then ”hibernated”.(休眠)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;high rate WPAN&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;802.15.3-2003 is a MAC and PHY standard for high-rate (11 to 55 Mbit/s) WPANs;&lt;/li&gt;
      &lt;li&gt;802.15.3a: UWB PHY… no agreement when choosing PHY (MB-OFDM vs. DS-UWB);&lt;/li&gt;
      &lt;li&gt;802.15.3b-2005: improve implementation and interoperability of the MAC;&lt;/li&gt;
      &lt;li&gt;802.15.3b-2009: mm-wave-based PHY, 57-64Ghz unlicensed band, &amp;gt;2Gbps&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TG 4: Low Rate WPANs&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;long battery life, low data rate, low complexity;&lt;/li&gt;
      &lt;li&gt;802.15.4 standard released in May 2003;&lt;/li&gt;
      &lt;li&gt;many networks runs on top of 802.15.4: ZigBee, 6LoWPAN, WirelessHART, etc.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Enhancements of 802.15.4&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;802.15.4a-2007: additional PHYs, e.g. UWB pulsed radio;&lt;/li&gt;
      &lt;li&gt;802.15.4-2006: clarification of the original standard;&lt;/li&gt;
      &lt;li&gt;IEEE 802.15.4c: adaptation to unlicensed bands in China;&lt;/li&gt;
      &lt;li&gt;IEEE 802.15.4d: adaptation to unlicensed bands in China;&lt;/li&gt;
      &lt;li&gt;IEEE 802.15.4e: enhancements for industrial apps, e.g. channel hopping;&lt;/li&gt;
      &lt;li&gt;IEEE 802.15.4f: active RFID systems;&lt;/li&gt;
      &lt;li&gt;IEEE 802.15.4g: smart utility networks: large networks with a lot of end systems.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TG 5 Mesh networking&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;two parts: low rate and high rate mesh networks;
        &lt;ul&gt;
          &lt;li&gt;low rate: IEEE 802.15.4-2006 MAC&lt;/li&gt;
          &lt;li&gt;high rate: IEEE 802.15.3/3b MAC;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;common features: network initialization, addressing, multihop unicasting;&lt;/li&gt;
      &lt;li&gt;low rate: multicasting, broadcasting, portability, trace route and energy saving&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TG 6 Body Area Network&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;low-power short range standard, draft in 2011&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;TG 7: visible light communication&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;work in progress&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;zigbee&quot;&gt;ZigBee&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;developed by ZigBee Alliance&lt;/li&gt;
  &lt;li&gt;on top of IEEE 802.15.4&lt;/li&gt;
  &lt;li&gt;Particular implementation of those features specified in IEEE standard&lt;/li&gt;
  &lt;li&gt;Toptology in
    &lt;ul&gt;
      &lt;li&gt;Centralized star&lt;/li&gt;
      &lt;li&gt;Cluster-tree-based&lt;/li&gt;
      &lt;li&gt;full mesh(requires additional routing protocol)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Specifics:
    &lt;ul&gt;
      &lt;li&gt;low-rate (even compared to Bluetooth)&lt;/li&gt;
      &lt;li&gt;extremely low power consumption&lt;/li&gt;
      &lt;li&gt;example of applicability: sensor networks&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;comparison-with-other-technologies&quot;&gt;Comparison with other technologies&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/Tb2FbrU.png&quot; alt=&quot;Comparison&quot; /&gt;&lt;/p&gt;

&lt;h4 id=&quot;iee-80211x-technolgies&quot;&gt;IEE 802.11x technolgies&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;3x more expensive&lt;/strong&gt; than Bluetooth&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;5x the power consumption&lt;/strong&gt; of Bluetooth&lt;/p&gt;

    &lt;p&gt;&lt;img src=&quot;https://i.imgur.com/8VIrxBF.png&quot; alt=&quot;IEE 802.11x technolgies&quot; /&gt;&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;reason-for-zigbee&quot;&gt;Reason for Zigbee&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;low cost, high reliability, very long battery life&lt;/li&gt;
  &lt;li&gt;high security, self-healing properties, larger number of nodes supported&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;ease of deployment, guaranteed delivery, route optimization&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;NOT CHOOSING
    &lt;ul&gt;
      &lt;li&gt;Very specific apps&lt;/li&gt;
      &lt;li&gt;BLE Exists&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;zigbee-application&quot;&gt;ZigBee application&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/DtCu7G3.png&quot; alt=&quot;ZigBee application&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Wireless sensor networks&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;zigbee-protocol-overview&quot;&gt;ZigBee Protocol Overview&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/1EcuoD6.png&quot; alt=&quot;Zigbee protocol&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;ieee-802154-phy&quot;&gt;IEEE 802.15.4 PHY&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Three low power unlicensed radios:&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;2.4Ghz: 250Kbps(EU) 16 channels (ch11-ch26);&lt;/li&gt;
      &lt;li&gt;915Mhz: 40Kbps(US) 10 channels(ch1 - ch10)&lt;/li&gt;
      &lt;li&gt;868Mhz: 20Kbps(Europe and Japan) 1 channel (ch0)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Cahnnels and modulation in 2.4Ghz&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;16 channels , each 5Mhz wide  ch 11-26&lt;/li&gt;
      &lt;li&gt;actual throughput, 50% of 250Kbps due to overheads
        &lt;ul&gt;
          &lt;li&gt;overheads: addressing, security, error control&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;DSSS (direct sequence spread spectrum ) channel access&lt;/li&gt;
      &lt;li&gt;O-QPSK modulation&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Other responsiblities of PHY&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;detecting transmissions from new nodes&lt;/li&gt;
      &lt;li&gt;assessing quality of links with other nodes&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;ieee-802154-mac&quot;&gt;IEEE 802.15.4 MAC&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Functionlity&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;CSMA/CA&lt;/li&gt;
      &lt;li&gt;max.length of packet is 127bytes (2 bytes for CRC)&lt;/li&gt;
      &lt;li&gt;guarantees? transmissions&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Two modes of operation&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Acknowledge&lt;/li&gt;
      &lt;li&gt;Unacknowledge&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;How ACK mode is implemented&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;setting ACK bit in a forward packet&lt;/li&gt;
      &lt;li&gt;if set: receiver ACKs correct reception&lt;/li&gt;
      &lt;li&gt;if no: ACK is received with some time, retransmission&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;device-types&quot;&gt;Device types&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;FFD (Full Function Device)&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;capable of all the features and always “on”&lt;/li&gt;
      &lt;li&gt;routing/coordination/network formation&lt;/li&gt;
      &lt;li&gt;can talk to other FFDs and RFDs&lt;/li&gt;
      &lt;li&gt;FFDs require more power&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;RFD (Reduced Function Device)&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Sometimes called leaf nodes&lt;/li&gt;
      &lt;li&gt;simple netoworking functions&lt;/li&gt;
      &lt;li&gt;end systems in a sensor network&lt;/li&gt;
      &lt;li&gt;can talk to FFD only&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;logical-entities&quot;&gt;Logical entities&lt;/h3&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Full Function Device (FFD)&lt;/th&gt;
      &lt;th&gt;Reduced Function Device (RFD)&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;Found in any topology&lt;/td&gt;
      &lt;td&gt;Found only in start topology&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Can be a network co-ordinator&lt;/td&gt;
      &lt;td&gt;Cannot be a network co-ordinator&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Can talk to any type of device&lt;/td&gt;
      &lt;td&gt;Talks only to FFD&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Usually main powered&lt;/td&gt;
      &lt;td&gt;Usaully battered powered&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Network Coordinator&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;FFD, one per work&lt;/li&gt;
      &lt;li&gt;Create a network , assign channel/address&lt;/li&gt;
      &lt;li&gt;adds new devices to a network&lt;/li&gt;
      &lt;li&gt;constant power supply&lt;/li&gt;
      &lt;li&gt;sometimes serves as a gateway&lt;/li&gt;
      &lt;li&gt;a node may join if the coordinator is up&lt;/li&gt;
      &lt;li&gt;if down, already existing node may continue to network&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Router Functionality&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;FFD devices serving as a relay node&lt;/li&gt;
      &lt;li&gt;range extension&lt;/li&gt;
      &lt;li&gt;constant poewr suplly&lt;/li&gt;
      &lt;li&gt;sores packets sent to sleeping nodes&lt;/li&gt;
      &lt;li&gt;can be used to access the network&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;End Device&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;FFD/RFD&lt;/li&gt;
      &lt;li&gt;low power consumption&lt;/li&gt;
      &lt;li&gt;sleeping modes are defined&lt;/li&gt;
      &lt;li&gt;communication through routers&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;network-topologies&quot;&gt;Network Topologies&lt;/h3&gt;

&lt;h4 id=&quot;star-topology&quot;&gt;Star Topology&lt;/h4&gt;

&lt;p&gt;&lt;img src=&quot;http://ptgmedia.pearsoncmg.com/images/chap2_9780137134854/elementLinks/02fig02.jpg&quot; alt=&quot;img&quot; /&gt;&lt;/p&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Advantage&lt;/th&gt;
      &lt;th&gt;Disadvantage&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;small delay due to single hop&lt;/td&gt;
      &lt;td&gt;single point of failure(co-coodinator)&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt; &lt;/td&gt;
      &lt;td&gt;end devices cannot communicate directly&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;h4 id=&quot;cluster-tree-topology&quot;&gt;Cluster-tree Topology&lt;/h4&gt;

&lt;p&gt;&lt;img src=&quot;http://ptgmedia.pearsoncmg.com/images/chap2_9780137134854/elementLinks/02fig04.jpg&quot; alt=&quot;img&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;two levels of hierarchy&lt;/li&gt;
  &lt;li&gt;more nodes can be added via routers&lt;/li&gt;
  &lt;li&gt;large coverage areas&lt;/li&gt;
  &lt;li&gt;several paths in-between end nodes&lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;mesh-topology&quot;&gt;Mesh Topology&lt;/h4&gt;

&lt;p&gt;&lt;img src=&quot;http://ptgmedia.pearsoncmg.com/images/chap2_9780137134854/elementLinks/02fig05.jpg&quot; alt=&quot;02fig05.jpg (500Ã417)&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;extension of cluster-tree topology&lt;/li&gt;
  &lt;li&gt;connections to deveices at different layer feasible&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;RFD are still unable communicate directly&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;DELAY CAN BE REDUCED but COMPLEXITY of ROUTING is HIGH&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;access-methods&quot;&gt;Access methods&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;non-beacon access&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;transmit at anytime when channel is idle&lt;/li&gt;
      &lt;li&gt;“free-for-all” environment&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;beacon-based access&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;coordinator generates a superframe identified at beacon time&lt;/li&gt;
      &lt;li&gt;all nodes are synchronized&lt;/li&gt;
      &lt;li&gt;nodes transmit only i its designated time slot&lt;/li&gt;
      &lt;li&gt;superframe may contain common slot when stations compete&lt;/li&gt;
      &lt;li&gt;in-between: could go sleeping&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;creating-a-network&quot;&gt;Creating a network&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Initialization for coordinator&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;a node searches for coordinators on all channels;&lt;/li&gt;
      &lt;li&gt;if no coordinators, starts its own one using unique 16-bits PAN ID;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Initialization for end nodes:&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;scanning all available channels;&lt;/li&gt;
      &lt;li&gt;can detect &lt;em&gt;router&lt;/em&gt; and &lt;em&gt;coordinator&lt;/em&gt; with the same PAN ID&lt;/li&gt;
      &lt;li&gt;if yes, device with &lt;em&gt;strongest SNR&lt;/em&gt; is chosen;
        &lt;ul&gt;
          &lt;li&gt;end devices sends “can i join”&lt;/li&gt;
          &lt;li&gt;address is allocated if there is place for a new node&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Parameters set by a coordinator:&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;&lt;strong&gt;max number of &lt;em&gt;child devices&lt;/em&gt;&lt;/strong&gt; allowed per router&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;max number of &lt;em&gt;hops&lt;/em&gt;&lt;/strong&gt; from the co-ordinator to the most distant device&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;###&lt;/p&gt;

&lt;h3 id=&quot;network-example&quot;&gt;Network Example&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/fA24reI.png&quot; alt=&quot;zigbee_network&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;addressing&quot;&gt;Addressing&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Three types of IDs&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;MAC address (64-bits ID)&lt;/li&gt;
      &lt;li&gt;network address(16-bits ID)&lt;/li&gt;
      &lt;li&gt;name of device&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;unicasting-and-broadcasting&quot;&gt;Unicasting and broadcasting&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Usage of address&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;while joining: extended MAC address&lt;/li&gt;
      &lt;li&gt;while connected: short network address&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Unicast&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;network address is used as destination address in MAC header&lt;/li&gt;
      &lt;li&gt;message is routed in the network&lt;/li&gt;
      &lt;li&gt;destination accepts the message, others drop&lt;/li&gt;
      &lt;li&gt;destination answers with ACK&lt;/li&gt;
      &lt;li&gt;the process is a bit more complex: local ACKs
        &lt;ul&gt;
          &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/HmjTMdq.png&quot; alt=&quot;LOCALACK&quot; /&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Broadcasting is used when&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;joining or rejoining network&lt;/li&gt;
      &lt;li&gt;discovering routes in the network;&lt;/li&gt;
      &lt;li&gt;should be minimized&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Broadcasting&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;MAC address is 0XFFFF&lt;/li&gt;
      &lt;li&gt;all active devices receive and analyse the message.&lt;/li&gt;
      &lt;li&gt;all active FFD devices retransmit it&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;ACKing broadcast message&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;no explicit active ACKs&lt;/li&gt;
      &lt;li&gt;passive ACKing: listening whether all neighbors retransmitted
        &lt;ul&gt;
          &lt;li&gt;if not repeat the transmission&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;routing-and-route-discovery&quot;&gt;Routing and route discovery&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;General consideration&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;star topology no need routing&lt;/li&gt;
      &lt;li&gt;cluster-tree and mesh topologies need routing&lt;/li&gt;
      &lt;li&gt;more than one approach&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Cluster-tree topology&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;tree-routing
        &lt;ul&gt;
          &lt;li&gt;works fine for small networks&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;route discovery
        &lt;ul&gt;
          &lt;li&gt;work when network is unstable or large&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Mesh topology&lt;/strong&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;route discovery is only possible with AODV&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Tree routing&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;use tree hierarchial structure&lt;/li&gt;
      &lt;li&gt;first decision: whether to go up or down in hierarchy&lt;/li&gt;
      &lt;li&gt;examining
        &lt;ul&gt;
          &lt;li&gt;if destination is a descendant, the device sends the packet to a child;&lt;/li&gt;
          &lt;li&gt;otherwise, send it to a parent&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;upon reception by a node
        &lt;ul&gt;
          &lt;li&gt;accepts if the destination is a directly connected child&lt;/li&gt;
          &lt;li&gt;otherwise: sends to a parent&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;

    &lt;p&gt;BAD: path could be longer than needed&lt;/p&gt;

    &lt;p&gt;GOOD: quite stable as tree structure is guaranteed&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;sleeping-modes&quot;&gt;Sleeping modes&lt;/h3&gt;

&lt;h4 id=&quot;general-facts&quot;&gt;General facts&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;reduce power consumptions&lt;/li&gt;
  &lt;li&gt;still retain network address while sleeping&lt;/li&gt;
  &lt;li&gt;parent device buffers packets while child is asleep&lt;/li&gt;
  &lt;li&gt;upon wake up it checks whether there are some in store&lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;two-types-of-sleeping-mode&quot;&gt;Two types of sleeping mode&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Cyclic sleep&lt;/li&gt;
  &lt;li&gt;additional modes : can be controled , pin sleep&lt;/li&gt;
&lt;/ul&gt;

</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-10-WPANWBANs.Zigebee.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-10-WPANWBANs.Zigebee.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 9 - NB-IoT as enabler for mMTC</title>
        <description>&lt;h1 id=&quot;nb-iot-as-enabler-for-mmtc&quot;&gt;NB-IoT as enabler for mMTC&lt;/h1&gt;

&lt;h2 id=&quot;nb-iot&quot;&gt;NB-IoT&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Narrow Band Internt of Thing （窄帶物聯網）&lt;/li&gt;
  &lt;li&gt;is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services。&lt;/li&gt;
  &lt;li&gt;significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage&lt;/li&gt;
  &lt;li&gt;10 years battery life&lt;/li&gt;
  &lt;li&gt;Each device habing TCP/IP stack&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;iot-market-landscape&quot;&gt;IoT market landscape&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;28 billions of connected devices by 2021&lt;/li&gt;
  &lt;li&gt;IoT market USD 19 trillions by 2026&lt;/li&gt;
  &lt;li&gt;More than 10&lt;sup&gt;4&lt;/sup&gt;  companies involved by 2020&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;iot-classification&quot;&gt;IoT Classification&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;Massive IoT&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Mission-critial IoT&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;massive-iot&quot;&gt;Massive IoT&lt;/h3&gt;

&lt;h4 id=&quot;properties&quot;&gt;Properties&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Long range , link budget of 164dB&lt;/li&gt;
  &lt;li&gt;Power efficient, 10+year device battery life , 100x netowork energy efficiency&lt;/li&gt;
  &lt;li&gt;Massive Scale, 1+million devices/km^2&lt;/li&gt;
  &lt;li&gt;extreme simplicity , scaling lowest-end use cases&lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;massive-iot-enablers&quot;&gt;Massive IoT enablers&lt;/h4&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/RRfbbzZ.png&quot; alt=&quot;enablers&quot; /&gt;&lt;/p&gt;

&lt;h4 id=&quot;comparison&quot;&gt;Comparison&lt;/h4&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/16YsDqW.png&quot; alt=&quot;Comparison&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;nb-iot-implementation-and-band&quot;&gt;NB-IoT implementation and band&lt;/h2&gt;

&lt;p&gt;Implementations&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;In-band LTE&lt;/li&gt;
  &lt;li&gt;Guard band LTE&lt;/li&gt;
  &lt;li&gt;standalone&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Opeartioal frequencies&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;868 MHZ&lt;/li&gt;
  &lt;li&gt;LTE Bands&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://abm-website-assets.s3.amazonaws.com/ecnmag.com/s3fs-public/styles/content_body_image/public/embedded_image/2018/10/Fig-1-NB-IoT-operating-modes.png?itok=jHUHri5X&quot; alt=&quot;implemnentation&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;nb-iot-area&quot;&gt;NB-IoT area&lt;/h2&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/XZm3Ynk.png&quot; alt=&quot;usage&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/NBfPcuy.png&quot; alt=&quot;usage2&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;marine-cargo-iot&quot;&gt;Marine cargo IoT&lt;/h2&gt;

&lt;p&gt;https://www.marinetraffic.com/&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Container monitoring is IoT&lt;/li&gt;
  &lt;li&gt;Most cargo vessels are close coast&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;They use statellite links for IoT&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;use onshore NB-IoT infrastructure
    &lt;ul&gt;
      &lt;li&gt;direct offloading&lt;/li&gt;
      &lt;li&gt;ship-mounted relays&lt;/li&gt;
      &lt;li&gt;UAV relays&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/DWwfZk1.png&quot; alt=&quot;Marine cargo IoT&quot; /&gt;&lt;/p&gt;

&lt;h2 id=&quot;earth-curvature&quot;&gt;Earth Curvature&lt;/h2&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/I8RFgX3.png&quot; alt=&quot;Earth Curvature&quot; /&gt;&lt;/p&gt;
</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-09-NB-IoT-as-enabler-for-mMTC.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-09-NB-IoT-as-enabler-for-mMTC.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 8 - Spatially-temporal traffic dynamics and URLLC service</title>
        <description>&lt;h1 id=&quot;spatially-temporal-traffic-dynamics-and-urllc-service&quot;&gt;Spatially-temporal traffic dynamics and URLLC service&lt;/h1&gt;

&lt;h2 id=&quot;general&quot;&gt;General&lt;/h2&gt;

&lt;h3 id=&quot;service-requirement&quot;&gt;Service Requirement&lt;/h3&gt;

&lt;h4 id=&quot;3gpp-5g-service&quot;&gt;3GPP 5G Service&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;mMTC (massic Machine-Type Communication) 夠大&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Long Distance (link budge 164dB)&lt;/li&gt;
      &lt;li&gt;Power efficiency (10+ years battery lifetime)&lt;/li&gt;
      &lt;li&gt;Extremely dense (1+million devices/km&lt;sup&gt;2&lt;/sup&gt;)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;eMBB (enhanced Mobile Broadband) 夠寬&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;
        &lt;p&gt;Packet cell rate at 10Gbps&lt;/p&gt;
      &lt;/li&gt;
      &lt;li&gt;
        &lt;p&gt;Latency at air interface ~10ms&lt;/p&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;URLLC (Ultra Reliable Low Latency Communications) （夠低）&lt;/p&gt;
    &lt;ul&gt;
      &lt;li&gt;Air interface latency &amp;lt;1ms&lt;/li&gt;
      &lt;li&gt;Prbability of devliery 0.9999999&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;5g-nr-services&quot;&gt;5G NR Services&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;New bandwidth-greedy services
    &lt;ul&gt;
      &lt;li&gt;VR,AR&lt;/li&gt;
      &lt;li&gt;High-rate video application (FHD+)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;High-end IoT application
    &lt;ul&gt;
      &lt;li&gt;Inter-robot communication&lt;/li&gt;
      &lt;li&gt;V2V communcation, V stands for Vehicle&lt;/li&gt;
      &lt;li&gt;inter-UAV communications
        &lt;ul&gt;
          &lt;li&gt;&lt;em&gt;unmanned aerial vehicle&lt;/em&gt; (&lt;em&gt;UAV&lt;/em&gt;)&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;servicing-spatially-temporal-traffic&quot;&gt;Servicing Spatially-temporal traffic&lt;/h2&gt;

&lt;h3 id=&quot;traffic-anaysis&quot;&gt;Traffic Anaysis&lt;/h3&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/njBUdeS.png&quot; alt=&quot;Spatio-temporal analysis&quot; /&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Different time of day&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;solution&quot;&gt;Solution&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Locailzation(off-loading ) using D2D(devices)
    &lt;ul&gt;
      &lt;li&gt;A fraction of traffic can be localized&lt;/li&gt;
      &lt;li&gt;Offloading onto direct links&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;On-demand service provisioning
    &lt;ul&gt;
      &lt;li&gt;Mobile access points&lt;/li&gt;
      &lt;li&gt;“Cell on whieels” (CoW), UAV
        &lt;ul&gt;
          &lt;li&gt;COW: portable mobile cellular site that provides temporary network and wireless coverage to locations where cellular coverage is minimal or compromised.&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;traffic-localization-off-loading&quot;&gt;Traffic Localization (off-loading)&lt;/h3&gt;

&lt;h4 id=&quot;d2d-technologies&quot;&gt;D2D Technologies&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Wifi-direct, LTE-sidelink&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;3GPP plans to add NR-direct&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;Limitation
    &lt;ul&gt;
      &lt;li&gt;Limited communication range&lt;/li&gt;
      &lt;li&gt;Still limited support&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;d2d-meshs&quot;&gt;D2D meshs&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;interference in adhoc network&lt;/li&gt;
  &lt;li&gt;relaying a mesh&lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;blockchain&quot;&gt;Blockchain&lt;/h4&gt;

&lt;p&gt;&lt;img src=&quot;https://www.ibm.com/developerworks/community/blogs/73a1b0b2-6fe9-4c40-84b5-16c3212a7216/resource/BLOGS_UPLOADED_IMAGES/0_QAupL2jK-bAl9Gt7.jpg&quot; alt=&quot;Blockchain&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://www.researchgate.net/profile/Zheng_Yan4/publication/308806942/figure/fig1/AS:472192451387394@1489590861618/D2D-communication-application-scenarios-and-use-cases.png&quot; alt=&quot;COVERAGE&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;mobile-ap&quot;&gt;Mobile AP&lt;/h3&gt;

&lt;h4 id=&quot;3gpp-supoort&quot;&gt;3GPP Supoort&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;UAV support in 3GPP&lt;/li&gt;
  &lt;li&gt;NR relaying/sidelink&lt;/li&gt;
  &lt;li&gt;Backhauling&lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;performance&quot;&gt;Performance&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Backhaul is critial&lt;/li&gt;
  &lt;li&gt;Dynamic optimization is critical&lt;/li&gt;
  &lt;li&gt;Interplay between no. of UEs and no. of UAVs&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;urllc-service&quot;&gt;URLLC Service&lt;/h2&gt;

&lt;h3 id=&quot;high-end-iot-application&quot;&gt;High-end IoT application&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Driven by new use-cases&lt;/li&gt;
  &lt;li&gt;Driven by elecronic evolution&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;industrial-automation&quot;&gt;Industrial Automation&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Autonomous production lines&lt;/li&gt;
  &lt;li&gt;Traffic characteristics
    &lt;ul&gt;
      &lt;li&gt;Low latency (few ms)&lt;/li&gt;
      &lt;li&gt;High reliability (10&lt;sup&gt;-5&lt;/sup&gt; BLER) (Block Error Rate)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://www.analog.com/-/media/analog/en/applications%20by%20market/iat/pavilion/industry-40-infographic-v5.gif?la=en&quot; alt=&quot;Industry 4.0&quot; /&gt;&lt;/p&gt;

&lt;h4 id=&quot;autonmous-driving&quot;&gt;Autonmous Driving&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Future of car industry&lt;/li&gt;
  &lt;li&gt;Traffic characteristics
    &lt;ul&gt;
      &lt;li&gt;Huge throughput&lt;/li&gt;
      &lt;li&gt;Low latency&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://d1v86arogvust7.cloudfront.net/sites/default/files/styles/blogfeature_large/public/field/image/shutterstock_682503085.jpg?itok=f0QybLHo&quot; alt=&quot;The Future of Autonomous Vehicles and Kettering University&quot; /&gt;&lt;/p&gt;

&lt;h4 id=&quot;healthcare--remote-surgeries&quot;&gt;Healthcare : Remote surgeries&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Traffic characteristics
    &lt;ul&gt;
      &lt;li&gt;Extremely Low latency (&amp;lt;1ms)&lt;/li&gt;
      &lt;li&gt;Extremely High reliability (10&lt;sup&gt;-9&lt;/sup&gt;)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h4 id=&quot;remote-diagnosis&quot;&gt;Remote Diagnosis&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;NR+LTE&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;http://www.masmachinetools.com/foto/dalkova-diagnostika-mcu-700.jpg&quot; alt=&quot;img&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;addressing-latency&quot;&gt;Addressing Latency&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Main chanllenge
    &lt;ul&gt;
      &lt;li&gt;NR frame duration : 1ms&lt;/li&gt;
      &lt;li&gt;Latency &amp;lt;1ms&lt;/li&gt;
      &lt;li&gt;How to conform?&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Two principle ways
    &lt;ul&gt;
      &lt;li&gt;Reservation/priorities&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Non-Orthogonal multiple access (NOMA)&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;International overlapping of data&lt;/li&gt;
          &lt;li&gt;Enable by flexible NR slot numberology&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;addressing-reliability&quot;&gt;Addressing Reliability&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Bloackage may or may not lead to outage(中斷)
    &lt;ul&gt;
      &lt;li&gt;Case 1: blockage leads to lower MSC scheme
        &lt;ul&gt;
          &lt;li&gt;MSC: Mobile Switching Service Centre&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Case 2: bloackage leads to outage&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Solution
    &lt;ul&gt;
      &lt;li&gt;Case 1: provide more resources
        &lt;ul&gt;
          &lt;li&gt;Bandwidth reservation&lt;/li&gt;
          &lt;li&gt;Isolated deployments&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Case 2: find a new path
        &lt;ul&gt;
          &lt;li&gt;3GPP multi-connectivity&lt;/li&gt;
          &lt;li&gt;Dense deployments&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Multi-connectivity
    &lt;ul&gt;
      &lt;li&gt;avoiding outage!&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Bandwidth reservation
    &lt;ul&gt;
      &lt;li&gt;Alleviating lower MCSs(Modulation and Coding Scheme)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-08-Spatially-temporal-traffic-dynamics-and-URLLC-service.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-08-Spatially-temporal-traffic-dynamics-and-URLLC-service.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 7 - Massive machine-type communications technologies (MTC)</title>
        <description>&lt;h1 id=&quot;massive-machine-type-communications-technologies-mtc&quot;&gt;Massive machine-type communications technologies (MTC)&lt;/h1&gt;

&lt;h3 id=&quot;iot&quot;&gt;IoT&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Internet of Thing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://cdn-images-1.medium.com/max/1600/1*lVfJFrxmv5WYXnfm7Tbf3A.png&quot; alt=&quot;IOT&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;consumer-vs-industrial-iot-domains&quot;&gt;Consumer vs Industrial IoT domains&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Industrial IoT&lt;/strong&gt; is similar to the &lt;strong&gt;consumer IoT&lt;/strong&gt;,&lt;/li&gt;
  &lt;li&gt;but the difference is that it has this is used in a commercial area that is &lt;strong&gt;industries&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://pbs.twimg.com/media/CGRbsRcVIAImNBP.png&quot; alt=&quot;will industrial iot be bigger than consumer iot novotech&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;contemporary-iot-connectivity-solution&quot;&gt;Contemporary IoT connectivity Solution&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;img src=&quot;https://www.murata.com/~/media/webrenewal/campaign/events/asean/es/connectivity/connect_7_world.ashx?la=en-sg&amp;amp;w=600&quot; alt=&quot;img&quot; /&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;They connect with each other using different standards for different applications&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;short-range-access-technologies-for-iot&quot;&gt;Short-Range Access Technologies for IoT&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Historical&lt;/strong&gt; solutions (Bluetooth, IEEE 802.15.4, IETF stacks,…) are evolving to maintain competitiveness in growing IoT market&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;&lt;em&gt;IEEE 802.11ah&lt;/em&gt;&lt;/strong&gt;(HaLow), low-cost, large-scale connectibity across massive deployments&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;&lt;em&gt;Unlicensed Low-Power Wide Area (LPWA)&lt;/em&gt;&lt;/strong&gt; networks rapidly emerge to support early stages of the IoT development, until standardized cellular M2M solutions enter the market.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://images.techhive.com/images/article/2016/01/wi-fi-802.11ah-100636515-primary.idge.jpg&quot; alt=&quot;802.11ah&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;next-generation-wireless-iot-technology&quot;&gt;Next-Generation Wireless IoT Technology&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Fifth-generation&lt;/strong&gt; (5G) wireless technology is targeting to &lt;em&gt;offer support&lt;/em&gt; for numerous &lt;strong&gt;IoT applications&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://res.cloudinary.com/engineering-com/image/upload/w_640,h_640,c_limit,q_auto,f_auto/infographic-blazing-5G_leesa2.jpg&quot; alt=&quot;iOT_2&quot; /&gt;
&lt;img src=&quot;https://static.techspot.com/articles-info/1582/images/2018-02-25-image.png&quot; alt=&quot;5G speed&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;5g-performance-targets-are-set-clearly&quot;&gt;5G Performance Targets Are Set Clearly&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;IMT-2020&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://pbs.twimg.com/media/Dm5p_lBWwAAmwTO.jpg:large&quot; alt=&quot;Diagram of the enhancement of key capabilities from IMT-Advanced to IMT-2020&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/5cWIiq4.png&quot; alt=&quot;IMT-2020&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;tactile-internet&quot;&gt;Tactile Internet&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;The Tactile Internet will be the next evolution of the Internet of Things (IoT), encompassing human-to-machine and machine-to-machine interaction.&lt;/li&gt;
  &lt;li&gt;It will enable real-time interactive systems with a raft of industrial, societal and business use cases.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://i.imgur.com/PjUeQf0.png&quot; alt=&quot;Tactile Interent&quot; /&gt;&lt;/p&gt;
</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-07-Massive-machine-type-communications-technologies-(MTC).html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-07-Massive-machine-type-communications-technologies-(MTC).html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
      <item>
        <title>Chapter 6 - 5G Cellular and New Radio</title>
        <description>&lt;h1 id=&quot;5g-cellular-and-new-radio&quot;&gt;5G Cellular and New Radio&lt;/h1&gt;

&lt;h2 id=&quot;satisying-growing-traffic-demands&quot;&gt;Satisying growing traffic demands&lt;/h2&gt;

&lt;h3 id=&quot;is-4g-enough&quot;&gt;Is 4G enough&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;1000Mbps for all subscribers in a cell
    &lt;ul&gt;
      &lt;li&gt;Cell radius ~500m to 2Km&lt;/li&gt;
      &lt;li&gt;Density of users : city centre -0.1 to 0.1 humans/m&lt;sup&gt;2&lt;/sup&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;The traffic growth is so huge
    &lt;ul&gt;
      &lt;li&gt;&lt;img src=&quot;https://www.ericsson.com/assets/global/scaled/global-mobile-data-traffic-eb-per-month-101165crop0031251758resize1500844autoorientquality90stripbackground23ffffffextensionjpgid8_970x546_90_329667.jpg&quot; alt=&quot;Global mobile data traffic (EB per month)&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Performance metrics
    &lt;ul&gt;
      &lt;li&gt;Shannon Channel capacity
        &lt;ul&gt;
          &lt;li&gt;$C=Blog_2(1+S)$&lt;/li&gt;
          &lt;li&gt;B is  the bandwidth&lt;/li&gt;
          &lt;li&gt;S is the SINR(signal-to-interference plus noise ratio)
            &lt;ul&gt;
              &lt;li&gt;$S=\frac{P_R}{BN+I} $&lt;/li&gt;
              &lt;li&gt;$P_R$ is the signal power at the receiver&lt;/li&gt;
              &lt;li&gt;$N$ is the thermal noise, constant&lt;/li&gt;
              &lt;li&gt;I is the aggregated interference&lt;/li&gt;
            &lt;/ul&gt;
          &lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Signal power at the receiver
        &lt;ul&gt;
          &lt;li&gt;$P_r = P_TAd^{-Y}$&lt;/li&gt;
          &lt;li&gt;$P_T$ is the emitter power at the transmier&lt;/li&gt;
          &lt;li&gt;A is the constant that depends on antennas/frequency&lt;/li&gt;
          &lt;li&gt;Y is the “path loss exponent” deponds on environment&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;FINAL VERISON = $C=Blog_2{(1+\frac{P_R}{BN+I})}$
    &lt;ul&gt;
      &lt;li&gt;PHY Layer mechanisms
        &lt;ul&gt;
          &lt;li&gt;FEC,MIMO,ARQ, 90% to shannon&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Increse emitted power
        &lt;ul&gt;
          &lt;li&gt;may increase interference&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Decrease thermal noise
        &lt;ul&gt;
          &lt;li&gt;Constant up to 0.6Thz&lt;/li&gt;
          &lt;li&gt;may use superconductor&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Decrease interference&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;Logarithmic increase of C&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Increase bandwidth&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;Almost linear increase of C&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Network Mechanisms&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;Better Spatial frequency reuse&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;increasing-bandwidth&quot;&gt;Increasing bandwidth&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;buy more licenced frequencies
    &lt;ul&gt;
      &lt;li&gt;Commercial netwoks(cellular networks)&lt;/li&gt;
      &lt;li&gt;Exclusive access&lt;/li&gt;
      &lt;li&gt;Ablity to use higher transmission power &amp;gt;1mW&lt;/li&gt;
      &lt;li&gt;High costs and risks&lt;/li&gt;
      &lt;li&gt;Less than 100-500Mhz overall in a country(less than 3Ghz )&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Use the unlicensed spectrum
    &lt;ul&gt;
      &lt;li&gt;ISM bands (Industrial, scientific, medical bands)&lt;/li&gt;
      &lt;li&gt;Extreme interference from Wi-Fi-s&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Spectral Efficiency
    &lt;ul&gt;
      &lt;li&gt;the information rate that can be transmitted over a given bandwidth in a specific communication system&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Quadrature Amplitude Modulation
    &lt;ul&gt;
      &lt;li&gt;PSK+ASK :S(t)= $Acos(wt+\phi)$, modulating $w $and $\phi$&lt;/li&gt;
      &lt;li&gt;&lt;img src=&quot;https://upload.wikimedia.org/wikipedia/commons/9/90/QAM16_Demonstration.gif&quot; alt=&quot;img&quot; /&gt;&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Higher frequency then more bandwidth available&lt;/li&gt;
  &lt;li&gt;5G: millimeter wave (mmWave)
    &lt;ul&gt;
      &lt;li&gt;28Ghz&lt;/li&gt;
      &lt;li&gt;60Ghz(802.11ad)&lt;/li&gt;
      &lt;li&gt;72Ghz&lt;/li&gt;
      &lt;li&gt;&lt;img src=&quot;https://cdn.everythingrf.com/live/Millimeter%20waves%20img_636793577330675858.jpg&quot; alt=&quot;img&quot; /&gt;&lt;/li&gt;
      &lt;li&gt;Postives
        &lt;ul&gt;
          &lt;li&gt;Highly directional antennas&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Negative&lt;/li&gt;
      &lt;li&gt;Blockage by humans&lt;/li&gt;
      &lt;li&gt;Large propagation losses&lt;/li&gt;
      &lt;li&gt;Realistically up to 100m&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;B5G,6G: teraherz(sub-mmWave)
    &lt;ul&gt;
      &lt;li&gt;275-325 GHz: 50Ghz of bandwidth&lt;/li&gt;
      &lt;li&gt;IEEE 802.15 3d”100Gbps wireless”&lt;/li&gt;
      &lt;li&gt;Positive
        &lt;ul&gt;
          &lt;li&gt;Even more directivity&lt;/li&gt;
          &lt;li&gt;Hugh channel capacity&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Negative
        &lt;ul&gt;
          &lt;li&gt;Atmospheric absorption（大氣吸收）&lt;/li&gt;
          &lt;li&gt;Blockage by Human&lt;/li&gt;
          &lt;li&gt;Extreme propagation losses&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;up to 10-20m realstically
        &lt;h2 id=&quot;5g-and-new-radio-interface&quot;&gt;5G and New Radio Interface&lt;/h2&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;5g5g-systems-as-enablers&quot;&gt;5G/5G+ systems as enablers&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Resembles properties of &lt;em&gt;CPS&lt;/em&gt;
    &lt;ul&gt;
      &lt;li&gt;CPS is Technological systems where physical and cyber components are tightly integrated(smartphone)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Moves us closer to tactile Internet（觸覺互聯網） conecpt， next IoT&lt;/li&gt;
  &lt;li&gt;Has to be supoorted by 5G/5G+ mobile cellular systems&lt;/li&gt;
  &lt;li&gt;At least two of the following are required
    &lt;ul&gt;
      &lt;li&gt;High throughput&lt;/li&gt;
      &lt;li&gt;High reliability&lt;/li&gt;
      &lt;li&gt;Low latency&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Reliable service over inherently unreliable medium&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;envisioned-3gpp-5g-services&quot;&gt;Envisioned 3GPP 5G services&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Enhanced mobile broadband(eMBB)&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;data-driven use cases requiring high data rates across a wide coverage area.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Massive machine-type communications(mMTC)&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;NB-IoT technology&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Ultra-reliable low-latency services (URLLC)&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Not yet available and no dates annouced&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://www.2cm.com.tw/upload/news/N171013000720171013165542.png&quot; alt=&quot;img&quot; /&gt;&lt;/p&gt;

&lt;h3 id=&quot;5g-evolution-or-revolution&quot;&gt;5G evolution or revolution&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;5G/5G+ systems are heterogeneous(同質) in nature
    &lt;ul&gt;
      &lt;li&gt;New Radio(NR) RAT(28,38,72GHz)
        &lt;ul&gt;
          &lt;li&gt;RAT (Radio Access Technology)&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Multi Rat support,,BT,WIFI,3G,4G,LTE&lt;/li&gt;
      &lt;li&gt;Advanced features: D2D, relays, femto/micro BSs.
        &lt;ul&gt;
          &lt;li&gt;D2D : Device to Device&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;SDN/NFV capabilities for control plane
        &lt;ul&gt;
          &lt;li&gt;SDN: Software Defined Networking&lt;/li&gt;
          &lt;li&gt;NVF: Network Virtualization Function&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;NR is expected to support URLLC service&lt;/li&gt;
  &lt;li&gt;delivery up to 10Gps per AP&lt;/li&gt;
  &lt;li&gt;upper bound latency&lt;/li&gt;
  &lt;li&gt;provide reliability&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;propagation-in-mmwave-band&quot;&gt;Propagation in mmWave band&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Highly complex compared to microwaves
    &lt;ul&gt;
      &lt;li&gt;Multiple paths&lt;/li&gt;
      &lt;li&gt;Material dependent&lt;/li&gt;
      &lt;li&gt;Spatial correlation
        &lt;ul&gt;
          &lt;li&gt;the channels between different antennas are often correlated and therefore the potential multi antenna gains may not always be obtainable&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Temporal correlation&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;path-blockage-phenomenon&quot;&gt;Path blockage phenomenon&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Very small wavelengths
    &lt;ul&gt;
      &lt;li&gt;30Ghz ~1mm
        &lt;ul&gt;
          &lt;li&gt;Cannot penetrate through objects&lt;/li&gt;
          &lt;li&gt;Cannot travel around&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Blockage happens at sub-second scales
    &lt;ul&gt;
      &lt;li&gt;Models for various environments needed&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;beam-tracking波束追蹤&quot;&gt;Beam tracking（波束追蹤）&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Massive MIMO to form directional radiation patterns
    &lt;ul&gt;
      &lt;li&gt;Linear arrays HPBW～102/N&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;img src=&quot;https://i.imgur.com/XiZsbjr.png&quot; alt=&quot;directional radiation patterns&quot; /&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;Positive effects
    &lt;ul&gt;
      &lt;li&gt;Much less interference&lt;/li&gt;
      &lt;li&gt;Noise-limited regime?&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Negative effects
    &lt;ul&gt;
      &lt;li&gt;Beam alignment needed&lt;/li&gt;
      &lt;li&gt;Array swtiching time ~2us&lt;/li&gt;
      &lt;li&gt;Exhaustive vs hierarchical&lt;/li&gt;
      &lt;li&gt;Delay and loss in capacity ？&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;extreme-and-complex-path-loss&quot;&gt;Extreme and complex path loss&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;img src=&quot;https://i.imgur.com/NPiXhiv.png&quot; alt=&quot;pathloss&quot; /&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;addressing-latency&quot;&gt;Addressing Latency&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Main chanllenge
    &lt;ul&gt;
      &lt;li&gt;NR frame duration : 1ms&lt;/li&gt;
      &lt;li&gt;Latency &amp;lt;1ms&lt;/li&gt;
      &lt;li&gt;How to conform?&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Two principle ways
    &lt;ul&gt;
      &lt;li&gt;Reservation/priorities&lt;/li&gt;
      &lt;li&gt;&lt;strong&gt;Non-Orthogonal multiple access (NOMA)&lt;/strong&gt;
        &lt;ul&gt;
          &lt;li&gt;International overlapping of data&lt;/li&gt;
          &lt;li&gt;Enable by flexible NR slot numberology&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;addressing-reliability&quot;&gt;Addressing Reliability&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;Bloackage may or may not lead to outage(中斷)
    &lt;ul&gt;
      &lt;li&gt;Case 1: blockage leads to lower MSC scheme
	- MSC: Mobile Switching Service Centre
        &lt;ul&gt;
          &lt;li&gt;Case 2: bloackage leads to outage&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Solution
    &lt;ul&gt;
      &lt;li&gt;Case 1: provide more resources
        &lt;ul&gt;
          &lt;li&gt;Bandwidth reservation&lt;/li&gt;
          &lt;li&gt;Isolated deployments&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;Case 2: find a new path
        &lt;ul&gt;
          &lt;li&gt;3GPP multi-connectivity&lt;/li&gt;
          &lt;li&gt;Dense deployments&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;
</description>
        <pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate>
        <link>https://bill0930.github.io//wireless%20networking/2019/05/10/WN-06-5G-Cellular-and-New-Radio.html</link>
        <guid isPermaLink="true">https://bill0930.github.io//wireless%20networking/2019/05/10/WN-06-5G-Cellular-and-New-Radio.html</guid>
        
        
        <category>Wireless Networking</category>
        
      </item>
    
  </channel>
</rss>
