<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     naa a22        4500</leader>
  <controlfield tag="001">510798268</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180411083344.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">180411e20131001xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s11277-013-1160-6</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s11277-013-1160-6</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Moon</subfield>
   <subfield code="D">Bongkyo</subfield>
   <subfield code="u">Department of Computer Science and Engineering, Dongguk Univ-Seoul, Seoul, Korea (ROK)</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Analysis of Ongoing SIP Session with Resource Reservation in Vertical Handover Scenario</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Bongkyo Moon]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Typically, WiFi-to-3G handover is time-critical depending on mobility and speed of mobile host (MH) while 3G-to-WiFi handover is optional for better quality of service and less cost. In this paper, a WiFi-to-3G vertical handover scheme is proposed in order to reduce the total handover delay and keep it within a desirable maximum limit. Our main concern is focused on MH attached currently to WiFi, which tries to move out of WLAN for switching to 3G link. Received signal strength (RSS) is actually an important decision criterion for vertical handover as well as horizontal handover. However, WiFi-to-3G vertical handover cannot be triggered by the signal decay of 3G system since there is no comparable signal strength available to aid the 3G handover decision. During WiFi-to-3G vertical handover, moreover, multimedia session initiation protocol (SIP) session re-setup with resource reservation cannot be completed before network resources along the new path via 3G are successfully reserved. Hence, RSS-based vertical handover algorithm with SIP session re-setup is proposed. From the results, we can know that well-defined or dynamically-adjusted threshold values could result in getting enough time in order to re-setup SIP session with resource reservation.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer Science+Business Media New York, 2013</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Vertical handover</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">RSS threshold</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">SIP session</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Resource reservation</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">QoS</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Wireless Personal Communications</subfield>
   <subfield code="d">Springer US; http://www.springer-ny.com</subfield>
   <subfield code="g">72/4(2013-10-01), 2481-2497</subfield>
   <subfield code="x">0929-6212</subfield>
   <subfield code="q">72:4&lt;2481</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">72</subfield>
   <subfield code="o">11277</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s11277-013-1160-6</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s11277-013-1160-6</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">100</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Moon</subfield>
   <subfield code="D">Bongkyo</subfield>
   <subfield code="u">Department of Computer Science and Engineering, Dongguk Univ-Seoul, Seoul, Korea (ROK)</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Wireless Personal Communications</subfield>
   <subfield code="d">Springer US; http://www.springer-ny.com</subfield>
   <subfield code="g">72/4(2013-10-01), 2481-2497</subfield>
   <subfield code="x">0929-6212</subfield>
   <subfield code="q">72:4&lt;2481</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">72</subfield>
   <subfield code="o">11277</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
