1. 21-06-xxx-LocInfo_in_IS_request
IEEE MEDIA INDEPENDENT HANDOVER
DCN: xxx
Title: Location Information in IS Request
Date Submitted: March, 5th , 2006
Presented at IEEE session 13
Authors or Source(s):
  Wolfgang Gröting, Yoshihiro Ohba, Kalyan Koora
Abstract: Location information in IS request primitive parameter
21-06-xxx-LocInfo_in_IS_request

2. 21-06-xxx-LocInfo_in_IS_request
IEEE presentation release statements
This document has been prepared to assist the IEEE 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
The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual < and in Understanding Patent Issues During IEEE Standards Development
21-06-xxx-LocInfo_in_IS_request

3. Present MIH Info Request Primitive
Presently, the MIH information request primitive is defined in draft as follows:
MIH_Get_Information.request ( InfoQueryFilter, InfoQueryParameters )
Query Filter: controls the type and amount of info. that is retrieved
Query Parameters: indicates the type of information the client interested in
In general, it is not specified that the IS server is situated just near to the PoA or PoS
Problem:
We are also aiming at scenarios where the IS server can be deep in the network (for example a central MIIS server)
MIIS server could offer its services to different PoAs from very far location
If a request is received by IS server, it doesn’t know where the requested UE/STN/MN is presently located and thus can’t provide exact location based information
it is difficult to extract the location information just from IP or MAC
21-06-xxx-LocInfo_in_IS_request

4. Proposed InfoQueryParmeter value
Propose to use PoA location information as one of the InfoQueryParameter for TLV-type query
Change Table in Section as follows:
Type
Length
Value
Type values of IEs queried
Length of any Additional Parameters
Any other parameters required.
A PoA Location TLV (TYPE_IE_POA_LOCATION) may be included. When a PoA Location TLV is included, only information associated with the location specified in the PoA Location TLV is returned in the corresponding Response. When a PoA Location TLV is included, it must be the last parameter and the Length field of each Request TLV defined in subsequent sections must be adjusted accordingly.
21-06-xxx-LocInfo_in_IS_request