1. 21-06-0658-01-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0658-01-0000 Title: Retrieval of multiple IEs and Reports with filering rule Date Submitted: :July, 16, 2006 Presented at IEEE 802.21 session #16 in San Diego Authors or Source(s): Kentaro Ishizu, Yoshia Saito, Masahiro Kuroda Abstract: This document comments on the 21-06-0674-00-0000- IE_TLV_Representation.doc and proposes an additional request/response for any combination of multiple IEs and Reports with filtering in order to simplify the retrieval and reports activities.

2. 21-06-0658-01-0000 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 and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html> Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 http://standards.ieee.org/board/pat/guide.html

3. 21-06-0658-01-0000 Summary (see next page as my proposed description) Comment to 21-06-0674-00-0000-IE_TLV_Representation.doc which was discussed at No. 3 of 21-06-0667-03-0000_Comment Assignments.doc Propose to add new section below (written in “Red”) to enable multiple retrievals in one request with filtering rules specified. Also, change the terms used in the section names below (written in “blue”) for consistency reason. 6.3.6 Retrieval of single Information Element Request for single Information Element Response for single Information Element 6.3.7 Retrieval of pre-defined Information Reports 6.3.8 Retrieval of multiple Information Elements and Reports Request for multiple Information Elements and Reports Response for multiple Information Elements and Reports

4. 21-06-0658-01-0000 Summary Addition of new section of 6.3.8 to enable multiple retrievals in one request with specified filtering rules. Updates of nomenclature for sections 6.3.6 and 6.3.7 as below in order to maintain the consistency. 1. Nomenclature change for sections 6.3.6 and 6.3.7 Current 6.3.6 title “Request for specific Information Element” should read “Retrieval of single Information Element” with updated table titles of; Request for single Information Element (From client to information server) Response for single Information Element (from information server to client) Current 6.3.7 title “Request for pre-defined Information Report” should read “Retrieval of pre-defined Information Report”

5. 21-06-0658-01-0000 Summary (cont.) 2. New section 6.3.8 entitled “Retrieval of multiple Information Elements and Reports” with updated table titles of; Request for multiple Information Elements and Reports Response for multiple Information Elements and Reports

6. 21-06-0658-01-0000 Information request in current IS In the current draft, we have following requests/responses. 6.3.6 Request for single specific information elements 6.3.7 Request for pre-defined information reports 6.3.7.1 General Information Report 6.3.7.2 Access Network Information Report 6.3.7.3 Point of Attachment Information Report

7. 21-06-0658-01-0000 Requirements for the air interface Requirements for the air interface are summarized in page 22 of the IS as below. While selecting an appropriate syntax for information exchange it is desired that: (5.4.3) (1) The information exchange should be done fast (2) The overhead in exchanging of information should be as small as possible (3) The extraction of the information at the mobile node should not include high computational complexity However, descriptions in sections 6.3.6 and 6.3.7 are inconsistent with the philosophy above. Because, The specific information elements deals with only single sets of request/response in one session. If multiple IEs are required from network side, network needs several transactions to retrieve information from a mobile device. The pre-defined report sometimes also contains IEs more than required.

8. 21-06-0658-01-0000 Short and efficient Information Query An example scenario A server sends candidate PoAs to an user entity requesting the handover Required information is not single (such as radio technology, ESSID, CH, IP address, etc) Multiple information queries are needed from time to time in the current IS. These actions should be avoided for the time sensitive queries because of delay and data size. Requirements Short information retrieval time One time query for the multiple information retrieval Small transport data size Filtering rule application to the information retrieval

9. 21-06-0658-01-0000 XML or TLV XML and TLV have their own pros and cons XML is suitable for expressing complicated data structure TLV is small in data size and light enough for hardware processing Typically, L2 transport uses TLV L2 transport wants to avoid frame fragmentation 21-06-0674-00-0000-IE_TLV_Representation.doc Conditions are made for the MIIS query to filter out unnecessary information The PoA IEs are always included in the Network IE, which increases the size of data frames and complicates the data format. For example, typically, PoA IE is over 100 bytes and Network IE is over 50 bytes. (MIHF header and optional fields also increase the data frame size.) However, long and complicated TLV format catering for the rich functions may sacrifice the advantages of TLV.

10. 21-06-0658-01-0000 Remedy (1 of 2) We propose additional request/response for any combination of multiple IEs and Reports by adding new section “6.3.8 Retrieval of multiple Information Elements and Report”. Request for multiple Information Elements and Reports “Request TLV list” is a list of any combinational requests for single Information Elements and Reports. Response for multiple Information Elements and Reports “Response TLV List” is a list of any combinational response for single Information Elements and Reports.

11. 21-06-0658-01-0000 Remedy (2 of 2) We propose “simple” filtering operation in the request for Report. Filter TLV TYPE_FILTER_OPERATION_EQUAL_TO TYPE_FILTER_OPERATION_NOT_EQUAL_TO TYPE_FILTER_OPERATION_GREATER_THAN TYPE_FILTER_OPERATION_LESS_THAN Example One time retrieval of “PoA IE” with the operator name of “blue-mobile” “PoA IE” with the radio strength of “above 50” “Network IE” with the cost of “below 3”

12. 21-06-0658-01-0000 Remedy (2 of 2 cont.) The filter TVLs setting can be specified in the 6.3.7.1 General Information Report by modifying relevant tables as below.