Transcript 21-05-0300-07-0000-InterDigital802_21Presentation

• IEEE 802.21 MEDIA INDEPENDENT HANDOVER
• DCN: 21-05-0300-07-0000
• Title: Proposed 802.21 Presentation for 3GPP
• Date Submitted: September, 1st, 2005
• Presented at fourth 802.21-3GPP Teleconference
• Authors or Source(s): Ulises Olvera, Alan Carlton
• Abstract:
• Provide 3GPP community with a high lever description of the 802.21 specification
21-05-0300-07-0000
1
IEEE 802.21 presentation release statements
• This
document has been prepared to assist the IEEE 802.21 Working Group. It
is offered as a basis for discussion and is not binding on the contributing
•
•
individual(s) or organization(s). The material in this document is subject to
change in form and content after further study. The contributor(s) reserve(s)
the right to add, amend or withdraw material contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate
material contained in this contribution, and any modifications thereof, in the
creation of an IEEE Standards publication; to copyright in the IEEE’s name
any IEEE Standards publication even though it may include portions of this
contribution; and at the IEEE’s sole discretion to permit others to reproduce in
whole or in part the resulting IEEE Standards publication. The contributor also
acknowledges and accepts that this contribution may be made public by IEEE
802.21.
The contributor is familiar with IEEE patent policy, as outlined in Section 6.3
of
the
IEEE-SA
Standards
Board
Operations
Manual
<http://standards.ieee.org/guides/opman/sect6.html#6.3>
and
in
Understanding Patent Issues During IEEE Standards Development
http://standards.ieee.org/board/pat/guide.html>
21-05-0300-07-0000
2
Why 802.21?
Some 3GPP mobility requirements:
•“An AIPN mobility solution must support UTRAN
and GERAN bases systems as possible access
systems beside supporting alternative existing
accesses such as WLAN” (3GPP 22.978)
•“An AIPN mobility solution should support
seamless terminal mobility across various access
systems”(3GPP 22.978)
•“It shall provide voice call continuity when the user
is moving between GSM/UMTS CS domain and
IMS”(3GPP 23.806)
•“The UE shall be able to detect and automatically
connect to the available access Network”(3GPP 23.806)
21-05-0300-07-0000
3
What do we offer 802.21?
• 802.21 is the only 802 standard that allows
interaction of 802 technologies with other
access technologies
• 802.21 offers an open interface that provides
link state event reporting in real time (Event
Service)
• 802.21 offers an open interface that provides
intersystem information, automatically and on
demand (Information Service)
• 802.21 offers an open interface that allows a
user to control handover link state (Command
Service)
4
21-05-0300-07-0000
Why are we here?
•Work actively within relevant standard
bodies in order to introduce applicable 802.21
requirements (E.g., where does 802.21 fit?)
•Update relevant 3GPP groups with latest
development in 802.21 standards
• Request your support in the determination of
the optimal placement of MIH Functions
within the 3GPP network
• Enthuse the 3GPP community about the
development of requirement on 802.21
technology
21-05-0300-07-0000
5
Some 802.21 Concepts
• Media Independent Handover Function
(MIHF): MIH is a cross-layer entity that provides
mobility support through well defined Service
Access Points offering Event, Information and
Command services
• MIH User: Any entity that avails of MIHF
services through the MIH Service Access Points
• MIH Network Entity: A remote entity that is
able to communicate with an MIHF over the MIH
protocol
21-05-0300-07-0000
6
802.21 Dos and Don’ts
802.21
• specifies procedures that facilitate handover decision making,
providing link layer state information to MIH users. Enabling
quicker handovers across multi-technology access networks
• defines the methods and semantics that facilitate the acquisition
of network information and the basic content of the this
information, thereby enabling network availability detection
• specifies command procedures that allow service continuity
across heterogeneous networks. Enabling seamless handovers
802.21
•802.21 neither executes handovers nor defines handover policies
leading to handover execution
•802.21 neither controls network detection nor specifies network
selection procedures
21-05-0300-07-0000
7
802.21 Model Terminal Side
MIH User 1
…
MIH User 2
MIH User n
Media Independent Handover User
MIH
Commands
MIH
Events
Information
Media Independent Handover Function (MIH)
Link
Events
Information
Link
Commands
3GPP
UTRAN
802.3
802.11
3GPP
GERAN
802.16
802 LINK LAYER
3GPP LINK LAYER
Link Layer
21-05-0300-07-0000
8
802.21 Model Network Side
MIH Network
Entity 1
MIH Network
Entity 2
…
MIH Network
Entity n
Wn
WAG
MIH Network Entity
MIH
Commands
MIH
Events
Information
Wp
Media Independent Handover Function
Link
Events
Link
Commands
802.3
802.11
Information
PDG
Wi
PDN
802.16
Cellular Network
802 Network
21-05-0300-07-0000
9
802.21 Model
Media
Independent
Handover
Network Entity
(E.g., MIH Server
Controller)
IS/CS over higher layer transport
(E.g., RLC,RLP)
MAC
L1
PHY
Media
Independent
Handover
Function
LLC
Events
Events
L3
Events
Media
Independent
Handover
Function
E/C/I
L2
802
Network
3GPP
Network
LLC
3GPP
Interface
IS/CS/ES
Higher Layer
Transport (E.g., IP)
Higher Layer
Transport (E.g.,IP)
E/C/I
Media
Media
Independent
Independent
Handover User
Handover User
Events
Client
Station
Wn
MAC
PHY
(E.g.,UTRAN, GERAN)
802
Interface
21-05-0300-07-0000
Information Service over L2 Transport
Remote MIH Events/MIH Commands over L2 Transport
10
Current 802.21 Scope
Current Draft defines:
• Media Independent Handover Principles
and Design Assumptions
•Supported Media Independent Services
•Service Access Points and their
Primitives
•A Media Independent Handover Protocol
21-05-0300-07-0000
11
Design Assumptions
Design Assumptions Dos:
•802.21 cross-layer entity interacting with multiple layers.
•802.21 Facilitates handover determination
•802.21 Provides a technology-independent unified
interface to upper layers and MIH users
•802.21 facilitates both station initiated and network
initiated handover determination. Both local and remote
triggers are supported
Design Assumptions Don’ts
•802.21 does not modify existing handover principles
•802.21 does not mandate handover determination based
on 802.21 events. Events are informational in nature
21-05-0300-07-0000
12
Media Independent
Services
Media Independent Services Dos:
•Mobility Management Entities access 802.21
services through well defined SAPs
•More than one user can have access to 802.21
services in order to integrate multiple mobility
protocols (E.g., Cellular –MIP)
•802.21 services could be invoked to request
operations on underlying resources
Media Independent Services Don’ts
•802.21 does not replaces existing mobility
management function and protocols already in place
21-05-0300-07-0000
13
Media Independent
Services (cont’d)
Media Independent Event Services:
•Event Service Dos
• Local and Remote Events are supported
• Events indicate changes in state behavior
• Events indicate administrative state change
• Events facilitate handover detection
• Events are delivered according to 802.21 users preferences
•Events Service Don’ts
• Events do not propagate directly between heterogeneous
stacks
• Events do not enforce actions but rather suggest them
21-05-0300-07-0000
14
Media Independent
Services (cont’d)
Media Independent Information Services:
•Information Service Dos
• Provides heterogeneous network information within a
particular geographical area
• Information might be delivered through access technology
broadcast/multicast procedures or through data base queries at
a remote server
• Information services might be dynamic or static
•Information Service Don’ts
• 802.21 does not define how the information server is
accessed, but only what information is required
• 802.21 does not specify how the information service might
be implemented in a particular technology
21-05-0300-07-0000
15
Media Independent
Services (cont’d)
Media Independent Command Services:
•Command Service Dos
• Commands might flow from the 802.21 MIH user to 802.21
MIH and from 802.21 MIH to link layer entities
• Commands might convey 802.21MIH user decision to switch
from one access technology to the other.
• Commands have both remote and local scope
• Commands might optimized existing handover mechanisms
•Command Service Don’ts
• Commands do not flow directly from one access technology
to other
• Commands do not replace existing mobility management
protocols and procedures.
21-05-0300-07-0000
16
CS to IMS
STA/UE
Client
MIH
User
AS/
NAS
AP
802.11
802.21
1.
802.21
RAN
MSC/
MGW
PDG
IMS
PSTN
802.11
CELL_DCH
Dissassociated
2.
3.
IMS
Detected
4.
LLEVENT
5.
6.
7.
MIHEVENT
MIHCOMMAND
8.
9.
LLCOMMAND
AAA REGISTRATION
10.
11.
12.
13.
14.
Associated
LLEVENT
MIHEVENT
MIHCOMMAND
LLCOMMAND
15.
16.
URA_PCH
Routing Area
21-05-0300-07-0000
17
WLAN PS to 3GPP PS
STA/UE
Client
MIH
User
AS/
NAS
AP
802.11
802.21
1.
802.21
RAN
SGSN
PDG
GGSN
CoN
802.11
URA_PCH
Associated
2.
3.
LLEVENT
4.
5.
6.
MIHEVENT
MIHCOMMAND
LLCOMMAND
7.
8.
CELL_DCH
ROUTING AREA UPDATE
9.
10.
11.
12.
13.
LLEVENT
MIHEVENT
MIHCOMMAND
14.
LLCOMMAND
15.
16.
Dissassociated
Routing Area
21-05-0300-07-0000
18