12/19/201821-08-0056-01-0000-Primitive_and_Message_Consistency.doc

Project / IEEE 802.21 MIHS

Title / Primitive and Message Consistency
DCN / 21-08-0056-01-0000-Primitive_and_Message_Consistency.doc
Date Submitted / February 22, 2008
Source(s) / Y. Alice Cheng (Telcordia Technologies), Meylemans, Marc (Intel Corporation), and Jin Lee (LG Electronics)
Re: / IEEE 802.21 Ad hoc meeting in Sata Clara Feb 2007
Abstract / This document lists the editorial fixes for the data types between MIH primitives and messages.
Purpose / Sponsor ballot comment contribution.
Notice / 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.
Release / 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 IEEE 802.2 may make this contribution public.
Patent Policy / 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

1.Introduction

There are several primitives that have data type that are inconsistent with the data types used in the TLV that carries the corresponding message. The consistency is checked between the sub-clause 7.4, sub-clause 8.6, and Table C-2.

After the consistency checking, this contribution also identifies several TLVs that are not in use anymore.

2.Detail updates

Message Updates

The following table lists the inconsistent primitive name and parameter with its corresponding message TLV and data type. The proposed resolutions are shown in word markups.

Primitve / Message
7.4.15.3.2
MIH_Link_Get_Parameters.confirm
Device States Response List: LIST(DEV_STATES_RSP) ( p96L15) / 8.6.3.2
MIH_Link_Get_Parameters response
Device States Response List:
Device States Response List TLV (p157L40)
List(DEV_STATES_RSP) (p199L57)
7.4.18.4.2
MIH_Net_HO_Candidate_Query.response
Preferred Link List:
LIST(RQ_RESULT) / 8.6.3.8
MIH_Net_HO_Candidate_Query response
Preferred Link List:
List of Link PoA List: (p159L58)Preferred Link List TLV (p200L20):
7.4.19.3.2
MIH_MN_HO_Candidate_Query.response
Preferred Candidate Link List:
LIST(RQ_RESULT) / 8.6.3.10
MIH_MN_HO_Candiddate_Query response
Preferred Link List:
List of Link PoA List TLV: (p160L59)
LIST(LINK_POA_LIST) (p200L16)Preferred Link List TLV:
7.4.20.3.2
MIH_N2N_HO_Query_Resources.response
Candidate Link List:
LIST(RQ_RESULT) / 8.6.3.12
MIH_N2N_HO_Query_Resource response
Candidate Link List:
Link Identifier List TLV (p161L63):Preferred Link List TLV:
7.4.21.2.2
MIH_Net_HO_Commit.indication
Link Type:
LINK_TYPE (p112L49) / 8.6.3.13
MIH_Net_HO_Commit request
Link Type:
Link Type TLV: (p162L21)
MISSING TLV definition in Table C-2
This applies to MIH_Net_HO_Commit response message also.
7.4.22.1.2
MIH_N2N_HO_Commit.request
MN Identifier:
MIHF_ID (p115L36) / 8.6.3.15
MIH_N2N_HO_Commit request
Mobile NodeMN Identifier:
Mobile NodeMN MIHF ID TLV (p163L22)
(same for the response message p163L55)
7.4.22.2.2
MIH_N2N_HO_Commit.request
Requested Resource Set:
REQ_RES_SET (p115L50) / 8.6.3.15
MIH_N2N_HO_Commit request
Requested Resource Set:
Requested Resource Set TLV (p163L30)
MISSING TLV definition in Table C-2
7.4.24.3.2
MIH_N2N_HO_Complete.respose
Resource Retention Status: (p123L23)
LINK_RR_STATUS
(Change the parameter name. Applies to .confirm primitive also at p124L10)
7.4.25.1.2
MIH_Get_Information.request
UnauthenticatedInformationRequest:
BOOLEAN (p125L49) / 8.6.4.1
MIH_Get_Information request (p166L21)
MISSING parameter and also TLV
Unauthenticated Information Request:
Unauthenticated Information Request TLV:
Boolean

Additional Changes

“Preferred Link List” parameter name is mapped to two types

Preferred Link List parameter in some primitives matches with LIST(RQ_RESULT) data type and sometimes matches with LIST(LINK_POA_LIST). Just to reduce ambiguity in naming,rename the LIST(LINK_POA_LIST) all to “CandidateLinkList” as in

MN_HO_Candidate_Query.

Changes are for MIH_N2N_HO_Commit Preferred Link List -> Candidate

Link List.

Not used TLVs

  • List of Network Type and Events (4).
    Data type NET_TYPE_EVTS is not used. Following are the two recommendation
  • DELETE the data type p196L6 in Table B-20, or
  • INCLUDE into MIH_Capability_Discover
  • MIH Capability Flag (24)
  • Operation Mode (29)
  • Operation Mode Status (30)
    Data type OP_MODE_STATUS is not used.
  • Link Action (37)
  • Handover Resource Response Set (39)
  • Access Router Address List (45)
  • DHCP Server Address List (46)
  • FA Address List (47)
  • Target Link Action (65)
  • Link Action Result (66)
  • Target Link Action Result (67)

1