Ieee p802. 21m Media Independent Services Framework Project


Mappings from MIS_LINK_SAP to media-specific SAPs



Download 3.39 Mb.
Page23/33
Date18.10.2016
Size3.39 Mb.
1   ...   19   20   21   22   23   24   25   26   ...   33

Mappings from MIS_LINK_SAP to media-specific SAPs

IEEE Std 802.3


LSAP, defined in the IEEE Std 802.2, provides the interface between the MISF and the Logical Link Control sublayer in IEEE 802.3 network. This SAP is used for local MIS exchanges between the MISF and the lower layers of the IEEE 802.3 interface (as the IEEE 802.3 instantiation of the MIS_LINK_SAP) and for the L2 transport of MIS messages across IEEE 802.3 access links.

802.11


The MISF uses MSGCF_SAP for interfacing with the link layer of IEEE 802.11 networks. The MIS_LINK_SAP defines additional primitives that map to MSGCF_SAP. These primitives are recommended as enhancements to IEEE 802.11 link-layer SAPs. MSGCF_SAP is defined by IEEE P802.1 1u/D3.0 and it includes, but is not limited to primitives related to the following:

System configuration

Link state change notifications/triggers

MIS frame transport through control or management frames

LSAP, defined in the IEEE Std 802.2, provides the interface between the MISF and the Logical Link Control sublayer in IEEE 802.11. This SAP is used for the L2 transport of MIS messages across IEEE 802.11 access links. The MIS messages are carried in IEEE 802.11 data frames.

Table E.2 lists this mapping.


IEEE Std 802.16


The MISF uses C_SAP and M_SAP for interfacing with the Control and Management planes of the IEEE 802.16 network.

C_SAP is defined by IEEE Std 802.16gTM-2007 [B21] and it includes primitives related to the following:

Handovers [e.g., notification of HO request from mobile station (MS)]

Idle mode mobility management (e.g., Mobile entering idle mode)

Subscriber and session management (e.g., Mobile requesting session setup)

Radio resource management

Authentication, Authorization, and Accounting (AAA) server signaling (e.g., EAP payloads)

Media independent function services

M_SAP is defined by IEEE Std 802.16g-2007 [B21] and it includes primitives related to the following:

System configuration

Monitoring statistics

Notifications triggers

Multi-mode interface management

CS_SAP, defined in the IEEE Std 802.16, provides the interface between the MISF and the service-specific Convergence Sublayer in IEEE 802.16 networks. This SAP is used for the L2 transport of MIS messages through data frames across IEEE 802.16 access links.

Table E. 1 lists this mapping.

3GPP and 3GPP2


This SAP defines MIS_3GLINK_SAP interface between the MISF and the different protocol elements of the 3G system.

3GPP and 3GPP2 service primitives for GERAN, UMTS, long term evolution (LTE), cdma2000, cdma2000-HRPD and UMB are used to access MIS services. This is done by establishing a relationship between the 3GPP/3GPP2 primitives and MIS primitives.

Table E.3 lists this mapping. Note that a 3GPP primitive group can be mapped to more than one MIS primitive, as shown in Table E.3.


(normative)
Data type definition

General


This annex defines data types used in the IEEE 802.21 standard. Any variable-length data type in this specification contains information needed for determining the end of data.

Basic data types


The data types defined in this subclause are used as the basis for defining any other data types. All basic data types are for general purpose. The “Binary Encoding Rule” column in Table F. 1 describes the encoding rules used when the data types are carried in MIS protocol messages.

Table F.—Basic data types

Data type name

Definition

Binary encoding rule

BITMAP(size)

A bitmap of the specified size. Usually used to represent a list of IDs.

Range: Each bit has a value of '0' or '1'.



A BITMAP(N), where N must be a multiple of 8, is made up of an N/8 octet values and encoded in network byte order.

CHOICE(

DATATYPE1, DATATYPE2[,... ])



A data type that consists of only one of the data types listed:

DATATYPE1,DATATYPE2[,... ].



A one-octet Selector field, followed by a variable length Value field. The Selector value determines the data type. If Selector==i, (i+1)-th data type in the list of data types DATATYPE1,DATATYPE2[,... ] is selected. The Selector value is encoded as UNSIGNED_INT(1). The Value field is encoded using the encoding rule for the selected data type.

INFO_ELEMENT

A binary encoded structure for Informa- tion Elements.

See 6.5.6.

INTEGER(size)

A signed integer of the specified size in number of octets.

Range: Each octet has a value of 0x00 to 0xff.



Each octet of an INTEGER(N) value [N=1,2,...] is encoded in network-byte order into an N-octet field.

The most significant bit of the first octet is the sign bit. If the sign bit is set, it indicates a negative integer. Otherwise, it indicates a non-negative integer.

A negative integer is encoded as 2s complement.


LIST(DATATYPE)

A list of values of DATATYPE

See F.2 for details.

NULL

A data type with empty data.

No octet is encoded for this data type. This data type is used to define an optional data type.


Table F.1—Basic data types (continued)

Data type name

Definition

Binary encoding rule

OCTET(size)

An array of octets. The size specifies the length.

The octets are encoded in network byte order.

SEQUENCE( DATATYPE1, DATATYPE2[,...])

A data type that consists of two or more data types.

DATATYPE1,DATATYPE2[,... ] are encoded in the order of appearance. Each data type is encoded using the encoding rule for the data type.

UNSIGNED_INT(size)

An unsigned integer of the specified size in number of octets.

Range: Each octet has a value of 0x00 to 0xff.



Each octet of an UNSIGNED_INT(N) value [N=1,2,...] is encoded in network-byte order into an N-octet field.

The encoding rule for LIST(DATATYPE) is a variable length Length field followed by a variable length Value field. The Length field shall be interpreted as follows:

Case 1: If the number of list elements in the Value field is less than 128, the size of the Length field is always one octet and the MSB of the octet is set to the value ‘0’. The values of the other seven bits of this octet indicate the actual number of list elements in the Value field.

Case 2: If the number of list elements in the Value field is exactly 128, the size of the Length field is one octet. The MSB of the Length octet is set to the value '1' and the other seven bits of this octet are all set to the value ‘0’.

Case 3: If the number of list elements in the Value field is greater than 128, then the Length field is always greater than one octet. The MSB of the first octet of the Length field is set to the value ‘1’ and the remaining seven bits of the first octet indicate the number of octets that are appended further. The number represented by the 2nd and subsequent octets of the Length field, when added to 128, indicates the total number of list elements in the Value field.

For example, an attribute of type LIST(LINK_ID) with two elements is encoded as shown in Figure F. 1 (LINK_ID is defined in F.3.4):

fig f1

Figure F.—Encoding example of a LIST with two LINK_ID elements



Download 3.39 Mb.

Share with your friends:
1   ...   19   20   21   22   23   24   25   26   ...   33




The database is protected by copyright ©ininet.org 2020
send message

    Main page