IE_CONTAINER_NETWORK—contains all the information depicting an access network, as shown in Table 13. When more than one PoA Container is provided in this IE, they should be prioritized in the order of preference from the information server’s perspective with first PoA Container as the top priority and with decreasing priority going down the list. This would enable the receiving entity to utilize this information in the same way as provided in this list for network selection or handover decisions. —IE_CONTAINER_NETWORK definition Information element ID = (see Table G.1) Length = variable IE_NETWORK_TYPE IE_OPERATOR_ID IE_SERVICE_PROVIDER_ID (optional) IE_COUNTRY_CODE (optional) IE_NETWORK_ID (optional) IE_NETWORK_AUX_ID (optional) IE_ROAMING_PARTNERS (optional) IE_COST (optional) IE_NETWORK_QOS (optional) IE_NETWORK_DATA_RATE (optional) IE_NET_REGULAT_DOMAIN (optional) IE_NET_FREQUENCY_BANDS (optional) IE_NET_IP_CFG_METHODS (optional) IE_NET_CAPABILITIES (optional) IE_NET_SUPPORTED_LCP (optional) IE_NET_MOB_MGMT_PROT (optional) IE_NET_EMSERV_PROXY (optional) IE_NET_IMS_PROXY_CSCF (optional) Table 13—IE_CONTAINER_NETWORK definition (continued) IE_NET_MOBILE_NETWORK (optional) IE_CONTAINER_POA #1 (optional) IE_CONTAINER_POA #2 (optional) … IE_CONTAINER_POA #k (optional) Vendor Specific Network IE (optional) IE_CONTAINER_POA—contains all the information depicting a PoA and optionally one or more Vendor Specific PoA IEs, as shown in Table 14.
Semantics of service primitive MIS_Capability_Discover.indication ( SourceIdentifier LinkAddressList, SupportedMisEventList, SupportedMisCommandList, SupportedIsQueryTypeList, SupportedTransportList, MBBHandoverSupport, SupportedSecurityCapList ) Parameters: Name Data type Description SourceIdentifier MISF_ID This identifies the invoker of this primitive, which is a remote MISF. LinkAddressList LIST (NET_TYPE_ADDR) (Optional) A list of network type and link address pair on the remote MISF. SupportedMISEventList MIS_EVT_LIST (Optional) List of supported events on the remote MISF. SupportedMISCommandList MIS_CMD_LIST (Optional) List of supported commands on the remote MISF. SupportedISQueryTypeList MIS_IQ_TYPE_LST (Optional) List of supported MIIS query types on the remote MISF. SupportedTransportList MIS_TRANS_LST (Optional) List of supported transport types on the remote MISF. MBBHandoverSupport LIST (MBB_HO_SUPP) (Optional) This is used to indicate if a make before break handover is supported on the remote MISF. Break before make handover is always supported. SupportedSecurityCapList MIS_SEC_CAP (Optional) List of supported MIS security capabilities on the remote MISF. When generated This primitive is used by an MISF to notify an MIS user when an MIS_Capability_Discover request message is received. This primitive is optional since the MISF can immediately return an MIS_Capability_Discover response message without generating this primitive to the MIS user. Effect on receipt The MIS user responds with an MIS_Capability_Discover.response primitive when an indication is received. MIH_Capability_Discover.response Function This primitive is used by an MIS user to convey the locally supported MIS capabilities to the MIS user that invoked the MIS_Capability_Discover request.
Effect on receipt The remote MIS user will perform necessary actions to process the registration request and respond with an MIS_Register.response. MIS_Register.response Function This primitive is used by an MIS user to send the processing status of a received registration request. Semantics of service primitive MIS_Register.response ( DestinationIdentifier, Status, ValidTimeInterval ) Parameters: Name Data type Description DestinationIdentifier MISF_ID This identifies a remote MISF, which will be the destination of this response. Status STATUS Status of operation. ValidTimeIntervala UNSIGNED_INT(4) Time interval in seconds during which the registration is valid. Parameter applicable only when the status parameter indicates a successful operation. A value of 0 indicates an infinite validity period. aThis parameter is not included if Status does not indicate “Success.” When generated This primitive is invoked by the MIS user to report back the result after completing the processing of a registration request. Effect on receipt Upon receipt, the local MISF sends an MIS_Register response message to the destination MISF. MIS_Register.confirm Function This primitive is used by the local MISF to convey the result of a registration request to an MIS user. Semantics of service primitive MIS_Register.confirm ( SourceIdentifier, Status, ValidTimeInterval ) Parameters:
EAP Peer MN EAP Authenticator PoS Capability Discovery Phase MIS Capability Discovery Request MIS Capability Discovery Response Trigger MIS Auth Request (EAP, Ciphersuite) MIS Service Access Authentication Phase (EAP, Ciphersuite) ... MIS Auth Request (EAP-success, SAID, AUTH) MIS Auth Response (AUTH) Service Access Phase Termination Phase ... MIS Termination Request MIS Termination Response h
— K - key derivation key. It is truncated from a master session key (MSK) or re-authentication MSK (rMSK). The length of K is determined by the pseudorandom function (PRF) used for key derivation. If HMAC-SHA-1 or HMAC-SHA-256 is used as a PRF, then the full MSK or rMSK is used as key
SA MIS header (S=0) Source MISF Identifier TLV Destination MISF Identifier TLV Service Specific TLVs or a fragment yes no Encryption applied? Service Specific TLVs yes AES-CCM? no Service Specific TLVs yes protected? no AES-CCM Encryption Encrypted Service Specific TLVs Service Specific TLVs Encrypted Service Specific TLVs Security TLV MIC Algorithm Encrypted MIC Algorithm Fail Service Specific TLVs MIC Security TLV Plaintext Service Specific TLVs MIC Security TLV Set S bit in the Header and add SAID TLV MIS header (S=1) Source MISF Identifier TLV Destination MISF Identifier TLV SAID TLV Security TLV Figure 37 M
The flags are formed by the following data: — 1 reserved bit, which is set to zero; — 1 bit flag for the associated data, which is zero; — 3 bits to represent (t-2)/2, which is 101 (t =12); — 3 bits to represent q-1, which is 001 (q = 2). The counter Ctr(i), i = 0, 1, ..., r, is formed with 1-octet flags; 13-octet nonce N; and 2-octet integer i. The format of Ctr(i) is illustrated in Figure 40 Flags (1 octet) Nonce (13 octets) i (2 octets) Figure 40 The flags for Ctr(i) is 00000001. The encapsulation of an MIS PDU consists of the following steps: a) Fetch Transaction ID and FN from the MIS header. b) Increment a positive number of SN to update the SN. c) Construct the nonce, N, as described in 9.3.3.2. d) Input N and P to AES-CCM generation-encryption process as specified in SP 800-38C. The B0 and all the counter numbers are formed as described in Figure 39 and Figure 40, respectively. e) Obtain the output, C, of AES-CCM. 9.3.3.3.2 Decapsulation For a given SA, the prerequisites for AES-CCM decapsulation includes an encryption key MIEK, AES block cipher encryption block, the parameters t, n, and q. The decapsulation of a protected MIS PDU consists of the following steps. a) Fetch Transaction ID and FN from the MIS header. b) Fetch SN from the security TLV. c) Construct the nonce, N, as described in 9.3.3.2. d) Input N and C to AES-CCM decryption-verification process as specified in SP 800-38C. The B0 and all the counter numbers are formed as described in 9.3.3.3.1. e) Obtain the output, P, or “INVALID”. 9.3.3.4 Format of security TLV
CoS packet loss rate QoSTransmittedFragmentCount (See NOTE) QoSFailedCount QoSRetryCount QoSMultipleRetryCount QoSFrameDuplicateCount QoSRTSSuccessCount QoSRTSFailureCount QoSACKFailureCount (See NOTE) QoSReceivedFragmentCount QoSTransmittedFrameCount QoSDiscardedFrameCount QoSMPDUsReceivedCount QoSRetriesReceivedCount STA Statistics Report Transmitted MSDU Count (See NOTE) MSDU Discarded Count MSDU Failed Count (See NOTE) MSDU Multiple Retry Count QoS Lost Count Transmit Stream/ Category Mea- surement Report Trigger (Option) (only to specific STA) NOTE—This parameter is most likely to be used to directly derive IEEE 802.21 LinkQoSParameters. See B.3 for example derivations. Table B.2 and Table B.3 show example mappings for IEEE 802.21 QoS link parameters and other link specific parameters for IEEE 802.16, 3GPP, and 3GPP2. For these technologies control is usually by means of a base station, not an individual station, since the media is controlled using asymmetric access. Table B.2—QoS parameter mapping for IEEE 802.16 and 3GPP2 IEEE 802.21 link QoS parameters IEEE 802.16 3GPP2 Throughput Maximum Sustained Traffic Rate Peak_Rate Packet loss rate Packet error rate Packet Error Rate CoS minimum packet transfer delay CoS average packet transfer delay CoS maximum packet transfer delay Maximum Latency Max_Latency CoS packet delay jitter Tolerated Jitter Delay_Var_Sensitive Table B.3—QoS parameter mapping for 3GPP IEEE 802.21 link QoS parameters Related 3GPP parameters
Supported number of CoS 4 Conversational Streaming Interactive Background Throughput Peak throughput Mean throughput Maximum bit rate for uplink/downlink Guaranteed bit rate for uplink/downlink Link packet error rate SDU Error Ratio Residual Bit Error Rate CoS minimum packet transfer delay Transfer delay CoS average packet transfer delay Transfer delay CoS maximum packet transfer delay Maximum Transfer delay CoS packet transfer delay jitter Delay Variation CoS packet loss rate Residual Bit Error Rate SDU Error Ratio Deriving generic IEEE 802.21 QoS parameters General The following subclauses describe how to derive generic QoS parameters from IEEE Std 802.11 link measurement parameters. This derivation relies on incremental values of counters as specified in the IEEE Std 802.11. Note that the parameters are unicast parameters that are unrelated to multicast traffic. Packet loss rate To calculate the packet loss rate (PLR), one uses Equation (1). (1) According to IEEE Std 802.11, a packet is a MAC user data packet or MAC service data unit (MSDU). The PLRMSDU can be derived from the Transmit Stream/Category Measurement Report using Equation (2). (2) = Packet error rate The packet error rate (PER) can be calculated using Equation (3).
Timers Item number Item description References Status Support Allowed values Supported values M.8.6.1 TransactionLifeTime Timer 8.2.3.5 M Yes [ ] No [ ] 1–255 M.8.6.2 RetransmissionInterval Timer 8.2.3.8.2 M Yes [ ] No [ ] 1–255 M.8.6.3 ReassemblyTimer 8.4.2.3 M Yes [ ] No [ ] 1–255