WiBroWiBro AccessAccess NetworkNetwork InterworkingInterworking
2006. 6. 28
Telecommunication R&D Center SAMSUNG ELECTRONICS CO., LTD.
원 정 재 ([email protected]) Index
u Overview
- Trend (Motivation, Deployment Scenario, etc.)
- Standardization (IEEE 802.21, 3GPP (UMA, VCC), IETF)
u Vertical Handover (VHO) Classification
- CS-to-PS VHO
- PS-to-PS VHO
u WiBro Access Network Interworking
- VCC based WiBro to 3G HO Procedure
- MIPv6/MIH based WLAN to WiBro HO Procedure
1/47 KRnet 2006 Handovers u Need for Handovers - Users are Mobile - Services are Transparent to Networks u Homogeneous (Horizontal) Handovers - Within Single Network (Localized Mobility) - Limited overlapping coverage u Heterogeneous (Vertical) Handovers
- Across Different Networks (Global Mobility) Complexity Level - More Opportunistic u Multiple Interface Management - Simultaneous use of multiple interfaces and access networks. - Association of an application with an interface u Multiple Flow Management - Ability to split individual flows between links with respect to the requirements of the flows and the user preferences
2/47 KRnet 2006 Motivation: HO between Heterogeneous Networks
In the era of BcN/NGN, users/terminals move across heterogeneous access networks such as 802.3, 802.11, 802.16 and cellular networks
MMoIP/VoIP Broadcast, Multicast IP-TV Push-to-Talk VoD/EoD Game Messaging, Presence E-Commerce
Softswitch IMS QoS/Session Controller Next Generation 3G IP Network 3G+ Network Network WLAN Wibro Network Ethernet-based Network Wired Network
Movement across Heterogeneous Network However, Seamless Service ?
3/47 KRnet 2006 Deployment Scenario
u Operator type - Single operator / multiple networks - Multiple operators / multiple networks u Overlapping type - Partially overlapped Out of Town WiBro ? connectivity In the office - Fully overlapped Wi-Fi ? optimization
u Coupling type In the car - Tight coupling - Loose coupling Cellular
4/47 KRnet 2006 Handover Architecture and Important Issues
Handover
HO Architectures HO Decision algorithms
Parameter User Mobility Management Admission Control Adoptions Preference:
Bandwidth, RSS, Price, bandwidth, Channel Assignment: Delay, Power, Velocity, power, Horizontal Vertical Call blocking, Traffic, etc. Etc. HO blocking, HO HO Call dropping. Context: Decision algorithm HO protocol design QoS, Security, Billing WWAN, WMAN, WLAN…
Lower Layer Support Interface selector
IEEE JSAC, VOL.23, NO.11, NOV 2005 Lee et al.: Framework of Handoffs in Wireless Overlay Networks based on MIPv6 5/47 KRnet 2006 Analysis of Customer Needs
WLAN Wireless Internet (1x+EVDO) Limited Mobility Low Data Speed Limited Coverage Expensive Price Needs for Enhanced Mobility, Coverage, Speed & Price advantage
Mobile WiMAX
Wireless Internet Wired B.B. Internet * WLAN * Mobile WiMAX ** (EVDO)* 1. Home (90 %) 1. School/Work (72 %) 1. Home (41 %) 1.Enterprise Place 2. Company (30 %) 2. Home (26 %) 2. School/Work (31 %) 2.Home residential consumer 3. PC Cafe (22 %) 3. Airport ( 1 %) 3. In Movement (26 %) 3.Lap top users, Multimedia 1. Information Search Similar with Broadband 1. Ring-tone/Melody 1. Commerce / Government Service 2. Game Internet Service 2. Game 2. Media / Public Safety 3. e-mail 3. Music 3. VOIP / LBS/ Gaming Mobility - None Mobility - Low Mobility - High Mobility - High Price -low Price - Low Price - High Price - Low Comparison Security – Good Security - Low Security - Fair Security - Good Data Speed - High Data Speed - High Data Speed - Low Data Speed - Fair
* Source: NIDA (’04.10) ** Anticipated 6/47 KRnet 2006 ISP’s Plan for Wireless Access
Wibro 망 구축 계획 망 커버리지 계획
Not under the full coverage of Wibro !
서울
인천 WiBro
대전
대구 울산
광주 부산 이종망 간 이동성,, QoS 관리 ?
음성위주의 광역서비스 협대역 데이터 1단계 : 서울, 인천, 수원 등 10개시 § 2G/3G : , 2단계 : 5대 광역시, 경기 등 15개시 § 휴대인터넷 : 도심지 위주의 광대역 데이터 서비스 3단계 : 전국 59개시 § WLAN : 공항, Hot Spot 등 특정지역 서비스
이종 무선망간 seamless service 제공을 위한 기술 필요 !!! à One of them, IEEE 802.21 Media Independent Handover (MIH) 7/47 KRnet 2006 Standardization
u IEEE 802.21 MIH
- IEEE 802.21 MIH Key Services
- Relationship between MIH SAPs
? Media Dependent SAPs
? Media Independent SAPs
u 3GPP
- UMA (Unlicensed Mobile Access)
- VCC (Voice Call Continuity)
u IETF
- MIPSHOP
- MONAMI 6
8/47 KRnet 2006 Handover Standards
802.11r VCC I-WLAN 802.11u 802.16e SAE-LTE UMA 802.16g IEEE 3GPP IEEEIEEE 802.21802.21 Horizontal Inter-working & Handover Handovers Signaling
MIP MONIMI6 SIP NETLMM FMIP HIP MIPSHOP DNA IP Mobility & Handover IETF Signaling
802.21 Complements other Handover Standards
9/47 KRnet 2006 IEEE 802.21 MIH Key Services
u IEEE 802.21 defines three services to make inter-RAT handover faster, more efficient, and more Higher layers intelligence. IP, SIP, MIP (or FMIP), HIP, Transport, Application, etc. u These services may be used to facilitate the operations of MIP/FMIP. Media Independent SAP Event Service
802.21 MIH Function State Change Event Command Information Command Service Parameter Change Service Service Service Predictive Link Transmission Link Synchronous L2 Trigger Handover Information Client Initiated (Event) Command Service Network Initiated IEEE 802.21 Resource Reservation Media Dependent SAP
General Network Info Access Network Info WLAN Cellular WMAN POA Specific Info Neighbor Net Info Link Layer Technologies
Information Service
10/47 KRnet 2006 Relationship between MIH SAPs
MIH User (Application, Transport, Network)
Media Independent SAP MIH_SAP
MIH_NMS_SAP Network MIH Function Management Entity SAP - Media Dependent SAPs LSAP LSAP CS_SAP MLME MIH_3GLINK_SAP MIH_3GLINK_SAP CS_SAP, M_SAP 802.2 (LLC) 802.11 802.16 3GPP 3GPP2 802.3
11/47 KRnet 2006 Media Dependent SAPs u MLME_SAP (IEEE 802.11u) - System configuration - Link state change notifications/triggers u M_SAP (IEEE 802.16g) - System configuration - Monitoring Statistics - Notifications/Triggers u C_SAP (IEEE 802.16g) - Handovers ( e.g, notification of HO request from MS, etc.) - Idle mode mobility management (e.g. Mobile entering idle mode) - Subscriber and session management (e.g. Mobile requesting session setup) - Radio resource management - AAA server signaling (e.g. EAP payloads) - Media Independent Function Services)
12/47 KRnet 2006 Link Events
No Link Event Type Link Event Name Description 1 State Change Link Up L2 connection is established and link is available for use 2 State Change Link Down L2 connection is broken and link is not available for use 3 Predictive Link Going Down Link conditions are degrading & connec tion loss is imminent 4 State Change Link Detected New link has been detected 5 Link Parameters Link Parameters Change Link parameters have crossed specified threshold 6 Administrative Link Event Rollback Previous link event needs to be rolled back 7 Link Transmission Link SDU Transmit Status Indicate transmission status of all PDU segments 8 Link Synchronous Link Handover Imminent L2 handover is imminent based on changes in link conditions 9 Link Synchronous Link Handover Complete L2 link handover to a new PoA has been completed
13/47 KRnet 2006 C_SAP Primitives
No Primitives Description
1. M_Ranging Upper layers may control ranging procedure with these primitives. Upper layers shall commence 802.16 link setup procedure by sending M_Ranging.request primitive through NCMS. Note: M_Ranging.request primitive with ranging type: "initial" is an 802.16 Link Switch Link Com–mand (link setup) which corresponds to Link Switch MIH command
2. M_Registration Upper layers may control registration procedure with these primitives. Upper layers are notified of link setup by M_Registration.confirmation. Note: M_Registration.confirmation primitive is an 802.16 Link_Up Link Event. 3. M_Neighbor When 802.16 MAC receives neighbor advertisement (MOB_NBR-ADV), this primitive is used to deliver the information to upper layers. Upper layers may schedule scanning period with BS. During scanning period BS may buffer downlink traffic to the mobile node. 4. M_ScanScheduling When 802.16 MAC receives neighbor advertisement (MOB_NBR-ADV), this primitive is used to deliver the information to upper layers. Upper layers may schedule scanning period with BS. During scanning period BS may buffer downlink traffic to the mobile node. 5. M_Scanning Upper layers may command autonomous scanning with these primitives. Note: These primitives are Scan Link Command for MIH Scan command in 802.21.
14/47 KRnet 2006 C_SAP Primitives
No Primitives Description 6. M_ScanReport Delivery of the primitives shall be based on the pre-registration procedure between upper layer management entities and NCMS. Scan report may be made remotely to the BS or locally to the upper layer entity depending on the report target value in M_ScanReport.request. 7. M_MACHandover Upper layers may control handover procedure by using these primitives. Note: These primitives may be used as link commands for MIH_Handover_initiate.request/response. For remote command service, 802.16 MAC management messages shall be used. (MOB_MSHO-REQ/ MOB_BSHO- REQ/MOB_BSHO-RSP) Currently only parameters relevant to 802.16 handover are included. Parameters for Media Independent Han–dover shall be identified and added. 8. M_HOIND.reqyest An MS transmits a MOB_HO-IND message for final indication that is about / confirmation performing a HO. Note: This primitive is a Link Command of MIH_Handover_Commit.request/response MIH Command in the .21 draft. For remote service, 802.16 MAC management message shall be used. (MOB_HO-IND). Currently only parameters relevant to 802.16 handover are included. Parameters for Media Independent Handover shall be identified and added. 9. M_Management These primitives are used to manage the status of mobile node. Upper layer may change the status of mobile node into power on/down/hold/de-register, etc. Note: These may be mapped to MIH Configure MIH Command Service. For remote service, 802.16 MAC management messages may be used. (RES- CMD/ DREG- CMD
15/47 KRnet 2006 Media Independent SAPs: MIH_SAP
Service No Primitives Description Category 1 MIH Capability Discover System Discover list of Events and Commands supported Management by MIH Function. 2 MIH Event Register Event Register for MIH event notifications 3 MIH Event DeRegister Event Deregister for MIH event notifications 4 MIH Link Up Event L2 connection has been established 5 MIH Link Down Event L2 connectivity is lost 6 MIH Link Going Down Event L2 connectivity is predicted to go down 7 MIH Link Event Rollback Event Predicted event has not occurred and hence event indication must be rolled back 8 MIH Link Parameters Report Event Link parameters have crossed specified threshold 9 MIH Link SDU Transmit Status Event Indicate transmission status of all PDU segments 10 MIH Link Handover Imminent Event L2 handover is imminent
16/47 KRnet 2006 Media Independent SAPs: MIH_SAP
Service No Primitives Description Category 11 MIH Link Handover Complete Event L2 handover has been completed 12 MIH Get Status Command Get the status of link 13 MIH Switch Command Switch session between specified links 14 MIH Configure Command Configure link parameters and parameter thresholds 15 MIH Configure Thresholds Command Configure thresholds for Link events 16 MIH Scan Command Scan the network 17 MIH Handover Initiate Command Initiate handover 18 MIH Handover Prepare Command Prepare for handover and query available resources 19 MIH Handover Commit Command Mobile node has committed to handover 20 MIH Handover Complete Command Handover has been completed 21 MIH Network Address Command Obtain network address on new link Information 22 MIH Get Information Information Request to get information from repository
17/47 KRnet 2006 3GPP: UMA (Unlicensed Mobile Access) (1/2) u UMA (Unlicensed Mobile Access) Technology - Initiated by a number of leading operators and vendors in January 2004 - Enables access to GSM and GPRS mobile services over unlicensed spectrum using Bluetooth and WiFi - Seamless delivery of mobile voice and data services over wireless networks - Transparent to existing, standard CPE devices (e.g. access points, routers and modems)
u 3GPP approved UMA specifications for 3GPP Release 6 (2005. 4) u 3GPP TS43.318 - Generic access to the A/Gb interface
18/47 KRnet 2006 3GPP: UMA (2/2)
u UNC (UMA Network Controller) - GANC (Generic Access Network Controller): 3GPP - Security Gateway (SGW): mutual authentication & encryption, data integrity - Broadband IP network: connectivity between AP and UNC u Interface - A-interface for circuit switched services - Gb-interface for packet switched services - Up interface between AP and UNC 19/47 KRnet 2006 3GPP: Voice Call Continuity (VCC)
2005.10/11 2006.01 2006.07 2006.09 2007 2007.03 2008
u TS 23.206,Stage2 (2006년 9월 목표) - The functional architecture and information flows of the VCC feature between 3GPP CS systems and IMS, and vice versa. u TS 24.206,Stage3 (2007년 3월 목표) - Protocol details for VCC u TR 23.806 is report from study on VCC. u There are still many of issues outstanding for VCC - Issue of distributed versus centralised service control not resolved for release 7 (retrogressive step and previous agreement of distributed service control for release 7). - Many other contentious issues
20/47 KRnet 2006 VCC Architecture u Implemented VCC user’s Home Network u VCC application gsmSCF - A set of functions required for a VCC UE to establish voice calls and switch the VCC UE’s access Leg between CS and IMS u Functional Entities used by VCC application - Domain Transfer Function (DTF) (FE-A) - Domain Selection Function (DSF) (FE-D) - CS Adaptation Function (CSAF) (FE- B) : collaboration with CAMEL service - CAMEL Service (FE-C) VCC UE’s proxy into IMS
21/47 KRnet 2006 VCC UE/Procedure
u VCC UE - Storage of domains selection policies for originating calls and domain transfer restrictions - Selection of domain for originating calls based on domain selection policies - Initiation of Domain transfer Procedures u VCC Procedure - Registration (not defined yet) ? CS domain registration ? IMS registration - UE originated calls ? CS call originating procedure ? IMS session originating procedure - UE terminated calls ? CS terminating procedure ? IMS terminating procedure - Domain transfer ? IMS to CS 22/47 ? CS to IMS KRnet 2006 VCC Call Flow (CS to CS) : Control plane
Visited CS HOME IMS HOME IMS Visited CS VCC AS VCC AS
2. IDF: CAMEL(MSISDN)
3. Connection (IMRN with 6. INVITE[IMRN) original called ID) VMSC MGCF CSCF CSCF MGCF VMSC 4. IAM(IMRN) 5. INVITE[IMRN)
CS IMS IMS CS 1. Setup (B party DN) 1. Setup (B party DN): MSISDN 3. IMRN: Anchoring을 위한 Destination address (VCC AS) 5. INVITE (IMRN) : Tel URI (MSISDN @URI)
Call Originating Side Call Terminating Side UE A UE B IAM: Initial Address Message IDP: Initial Detection Point IMRN: IP Multimedia Routing Number 23/47 KRnet 2006 VCC Call Flow : CS to CS
Visited CS Home IMS Home IMS Visited CS
VCC AS VCC AS ② ⑤ ⑦ ③ ④ ⑥ ⑧ ⑨ VMSC MGCF S-CSCF S-CSCF MGCF VMSC
P-CSCF P-CSCF
MGW MGW RTP GGSN GGSN
⑩ ① Call Originating Side Call Terminating Side
CS-UE IMS-UE IMS-UE CS-UE
24/47 KRnet 2006 VCC Call Flow : IMS to IMS
Visited PS Home IMS Home IMS Visited PS
VCC AS VCC AS
③ ⑤
VMSC MGCF S-CSCF S-CSCF MGCF VMSC ④ ⑥ ② P-CSCF INVITE (SIP URI or Tel URI) P-CSCF
MGW MGW
GGSN GGSN
① ⑦ Voice Call Originate (SIP) Call Originating Side Call Terminating Side
IMS-UE CS-UE CS-UE IMS-UE
25/47 KRnet 2006 VCC Domain Transfer : CS to IMS
Visited PS Home IMS Home IMS Visited CS
VCC AS VCC AS
VMSC MGCF S-CSCF S-CSCF MGCF VMSC
P-CSCF P-CSCF MGW MGW
GGSN RTP GGSN
Call Originating Side Call Terminating Side
•CS bearer는 MGW에서 anchoring되어 설정 CS-UE IMS-UE •IMS bearer는 UE의 IP address를 통해 설정 IMS-UE CS-UE
26/47 KRnet 2006 VCC Domain Transfer : IMS to CS
Visited PS Home IMS Home IMS Visited PS
VCC AS VCC AS
VMSC MGCF S-CSCF S-CSCF MGCF VMSC
P-CSCF P-CSCF MGW MGW
GGSN GGSN
Call Originating Side Call Terminating Side
•CS bearer는 MGW의 IP를 통해 설정 CS-UE IMS-UE •IMS bearer는 UE의 IP를 통해 설정 CS-UE IMS-UE
27/47 KRnet 2006 IETF
u MIPHSHOP WG MIPSHOP에서 중점적으로 다루는 부분
IETF 표준화 영역 MIPv4 MIPv6 … SIP Media Independent Handover User
MIH MIH Information Events Commands IEEE 802.21표준화 영역 Media Independent Handover Function Link Link Information Events Commands
IEEE 802 표준화 영역 802.3 802.11 … 802.16
- Work on areas of mutual interest to IEEE 802.21 and MIPSHOP ? protocol enhancements or specifications for IP-based support of Media-Independent Information, Command and Event Services. Ex) Discovery Capability, Security Protocol, Requirements
28/47 KRnet 2006 IETF
u MONAMI6: Mobile Nodes and Multiple Interfaces in IPv6 - Based on Mobile IPv6, NEMO basic Support
- Multiple network prefixes and interfaces
- Multiple tunnels b/w HoAs and CoAs
- Focus on not selection for multiple tunnels but multiple CoAs registration
- Information RFC
? Scenarios where it may end up with multiple global addresses on its interfaces
? Limitations for mobile hosts using multiple simultaneous Care- of Addresses and Home Agent addresses using Mobile IPv6
29/47 KRnet 2006 Vertical Handover 분류 u Vertical Handover의 분류 - CS ↔ PS 핸드오버
? 2G/3G CS 망 ↔ WiBro UMA 기반 Solution VCC (IMS) 기반 Solution ? 2G/3G CS 망 ↔ WiFi
? 2G/3G CS 망 ↔ 3G LTE
- PS ↔ PS 핸드오버
? WiBro ↔ WiFi Mobile IP 기반 Solution ? WiBro ↔ 3G LTE
? WiFi ↔ 2G/3G PS
? WiFi ↔ 3G LTE
30/47 KRnet 2006 WiBro Access Network Interworking
u Network Architecture
u CS to PS scenario: WiBro to 3G
- VCC based Scenario
u PS to PS scenario: MPv6/MIH based VHO support (WLAN to
WiBro)
- Phase 1: only MIH Local Events/Commands
- Phase 2: with MIH Server
31/47 KRnet 2006 Network Architecture
IMS VCC Core PSTN Network
ID C IPv6 AAA HA Connectivity IMS Servers Internet 802.21 MGC Information HSS MGW Server
Global Network Map
WLAN •List of Available Networks WiBro WWAN - 802.11, 802.16, GSM, UMTS •Link Layer Information - Neighbor Maps •Higher Layer Services - ISP, MMS, … .
32/47 KRnet 2006 Media Specific Changes
Mobile IEEE 802.21 Network Terminal Measurements, Triggers, Network Information Side Side
IEEE 802.11u for 802.11
IEEE 802.16g for 802.16
IETF MIPv6/FMIPv6
VCC for 3G/802.11/802.16
Media specific changes closely follow base protocol
33/47 KRnet 2006 PS(IMS)-to-CS scenario : WiBro to 3G
IMS Server (CSCF) Internet (CSCF) IMS- VCC AS MGCF CDMA Circuit Call Control
SIP ACR (ASN-GW) MSC MGW
IP Network BSC
RAS BTS (BS) BTS
Vertical HO
34/47 KRnet 2006 PS-to-PS scenario: WiBro to WLAN
u Mobile IP (MIP) and Fast Mobile IP (FMIP) - Basically, MIP is a path update protocol rather than a handover management protocol. MIP makes no assumptions as to the link layer, resulting in both L2 and L3 operating independent of one another. - FMIP is based on reliable prediction of handover, thus the availability of L2 triggers determines whether the handover optimization takes place. - L3 handover mechanisms lack the ability to adapt to network conditions and are unaware of user preferences, security, accounting issues, etc. u Optimization of MIP/FMIP based Mobility Mechanisms - Availability of link layer trigger provided to IP layers - Ability of IP layer to control link layer - Availability of extensive information to make more intelligent handover. u IEEE 802.21WG is defining a standard for these optimization mechanisms.
35/47 KRnet 2006 MIH and MIP based VHO support
MIPv6 802.21802.21 or MIH MIH FMIPv6
Handover Handover Handover Initiation Preparation Execution
Scope of 802.21
Search New Link Setup New Link Transfer Connection Network Discovery Layer 2 Connectivity Handover Signaling Network Selection IP Connectivity Context Transfer Service Discovery Packet Reception
To Optimize Vertical Handovers 36/47 KRnet 2006 EXAMPLE : WiBro to WLAN
u Network reference Architecture
u Example 1 : MIH Local Events/Command and MIPv6 based WLAN
to WiBro Handover Procedure
u Example 2 : WLAN to WiBro Handover procedure with MIH
Server
37/47 KRnet 2006 Example : Network Reference Model
0,+86(5 HJ 0XOWLPHGLD6WUHDPLQJ (PDLO :HE%URZVLQJ 6LQJDOLQJ 9RLFH 0,3 RU) 0,3 7UDQVSRUW 0,+
:/$1$3 :/$1$5
:/$1$1 0,+ 0,,67UDQVSRU3W URWRFRO
0,,66HUYHU
6LQJDOLQJ 7UDQVSRUW 0,+ :/$1 :L%UR ,QWHUIDFH ,QWHUIDFH :L%UR5$6 :L%UR$&5
007 :L%UR$1
38/47 KRnet 2006 Example 1 : MIH Local E/C and MIPv6 based WLAN to WiBro Handover Procedure
u The following procedures illustrate the usage of MIH Local Events/Commands without MIH server to facilitate the MIP
based handovers from 802.11 to 802.16.
u Handover Scenarios from 802.11 WLAN to 802.16 WMAN
- Multi-Mode Terminal (MMT) is connected to WLAN AN, with only
one interface active. WMAN interface is power-off, or in power-
saving mode. When MMT goes out of the coverage area of WLAN
hot-spot, the WLAN link drops and it connects to WMAN BS while
maintaining the session.
39/47 KRnet 2006 Procedure 1: MIH Local E/C facilitated HO Detection
40/47 KRnet 2006 Procedure 2: MIH Local E/C facilitated HO Initiation and Preparation
0XOWL 0RGH7HUPLQDO 007 :/$1$1 :0$1$1
:/$1 :0$1 $3 %6 / 0,3 0,+ 2OG$5 1HZ$5 0$& 0$& 0$& 0$&
6HOHFWVX JJHVWHG FDQGLGDWH%6
'HFLVLRQWR KDQGRYHUI URP :/$1WR:0$1
0,+ B6ZLWFK UHTXHVW
1HZ/LQN& RQQHFW 0 B5DQJLQJ UHTXHVW
0 B5DQJLQJ FRQILUPDWLRQ 3HUIRUP5DQJLQJ 1HJRWLDWH%DVLF&DSDELOLWLHV $XWKHQWLFDWLRQ DQG5HJLVWHU6 HUYLFHDQG6) &6&DSDELOLWLHV HWF 0 B5HJLVWUDWLRQUHTXHVW
0 B5HJLVWUDWLRQ FRQILUPDWLRQ :0$10HGLD6SHFLILF /LQNB8S(YHQW
0,+B6ZLWFK UHVSRQVH
Q&R$*HQHUDWLRQ
41/47 KRnet 2006 Procedure 3: MIH Local E/C facilitated HO Execution
0XOWL 0RGH7HUPLQDO :/$1$1 :0$1$1
:/$1 :0$1 $3 %6 0,+8VHU 0,+ 2OG$ 5 1HZ$5 0$& 0$& 0$& 0$&
0,+ B+DQGRYHUB&RPPLWUHTXHVW 0 B+2,1' UHTXHVW
02%B+2 ,QGLFDWLRQ
0 B+2,1' FRQILUPDWLRQ :0$1/LQNB+DQGRYHUB&RPSOHWH(YHQW
0,+ B/LQNB+DQGRYHUB&RPSOHWH LQGLFDWLRQ
:/$1'LVDVVRFLDWLRQ
/LQNB'RZQLQGLFDWLRQ
0,+ B+DQGRYHUB&RPPLWUHVSRQVH
0,35HJLVWUDWLRQ %LQGLQJ8SGDWH PRUHQHWZRUNHQWLWLHVPD\EHLQYRYOHG
42/47 KRnet 2006 Example 2 : WLAN to WiBro Handover procedure with MIH Server
u The following procedures illustrate the usage of MIHS to facilitate the MIP based handovers from 802.11 to 802.16. Similar usage of MIHS may refer to the document [1].
u Handover Scenarios from 802.11 WLAN to 802.16 WMAN - Multi-Mode Terminal (MMT) is connected to WLAN AN, with only one interface active. WMAN interface is power-off, or in power- saving mode. When MMT goes out of the coverage area of WLAN hot-spot, the WLAN link drops and it connects to WMAN BS while maintaining the session.
[1] 21-06-0656-00-0000-WLAN_WMAN_HO_Procedures.doc
43/47 KRnet 2006 Procedure 1: MIHS facilitated HO Detection
44/47 KRnet 2006 Procedure 2: MIHS facilitated HO Initiation and Preparation
45/47 KRnet 2006 Procedure 3: MIHS facilitated HO Execution
46/47 KRnet 2006 Q & A
47/47 KRnet 2006