Ieee p802. 21m Media Independent Services Framework Project



Download 3.39 Mb.
Page12/33
Date18.10.2016
Size3.39 Mb.
1   ...   8   9   10   11   12   13   14   15   ...   33

When generated

This primitive is generated by the MISF on receiving an MIS_Get_Information request message from a peer MISF. The order of the queries in each of InfoQueryBinaryDataList, InfoQueryRDFDataList, and InfoQueryRDFSchemaList parameters identifies the priority of the query. The first query has the highest priority to be processed by MIIS. Thus the order of the queries is maintained as indicated by the request message.

Effect on receipt

The recipient interprets the query request and retrieves the specified information. Once the information is retrieved, the recipient replies with the MIS_Get_Information.response primitive.

MIS_Get_Information.response

Function


This primitive is used by an MIS user (i.e., MIIS Server) to respond to an MIS_GET_Information.indication primitive.

Semantics of service primitive

MIS_Get_Information.response (

DestinationIdentifier,


Status,
InfoResponseBinaryDataList,
InfoResponseRDFDataList,
InfoResponseRDFSchemaURLList,
InfoResponseRDFSchemaList
)
Parameters:

Name

Data type

Description

DestinationIdentifier

MISF_ID

The local MISF or a remote MISF that will be the destination of this response.

Status

STATUS

Status of operation.

The response lists contains meaningful data if and only if the status is ‘0’.



InfoResponseBinaryDataList

LIST(IR_BIN_DATA)

(Optional) A list of TLV query responses. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDFDataList

LIST(IR_RDF_DATA)

(Optional) A list of RDF query responses. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDFSchemaURLList

LIST(IR_SCHM_URL)

(Optional) A list of RDF Schema URL. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDFSchemaList

LIST(IR_RDF_SCHM)

(Optional) A list of RDF schema query responses. The list will be sorted from most preferred first to least preferred last.

When generated

This primitive is generated by an MIS user in response to a received MIS_Get_Information.indication primitive. When the size of the Info Response parameters exceeds the maximum size specified in the MaxResponseSize parameter from MIS_Get_Information.indication primitive, one or more of the lower order list elements in Info Response parameters must be oMISed.

Effect on receipt

The recipient will return an MIS_Get_Information response message to the designated MIIS client.

MIS_Get_Information.confirm

Function


This primitive is used by the MISF to respond to an MIS_GET_Information.request primitive.

Semantics of service primitive

MIS_Get_Information.confirm (

SourceIdentifier,


Status,
InfoResponseBinaryDataList,
InfoResponseRDFDataList,
InfoResponseRDFSchemaURLList,
InfoResponseRDFSchemaList
)
Parameters:

Name

Data type

Description

SourceIdentifier

MISF_ID

Specifies the MISF ID of the node that invoked MIS_GET_Information.response.

Status

STATUS

Status of operation.

The response lists contains meaningful data if and only if the status is ‘0’.



InfoResponseBinaryDataList

LIST(IR_BIN_DATA)

(Optional) A list of TLV query responses. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDFDataList

LIST(IR_RDF_DATA)

(Optional) A list of RDF query responses. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDFSchemaU- RLList

LIST(IR_SCHM_URL)

(Optional) A list of RDF Schema URL. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDFSchemaList

LIST(IR_RDF_SCHM)

(Optional) A list of RDF schema query responses. The list will be sorted from most preferred first to least preferred last.

When generated

This primitive is generated by the MISF on receiving an MIS_Get_Information Response message from a peer MISF.

Effect on receipt

The MIS user that requested the information utilizes the Info Response parameters and takes suitable action. However, if Status does not indicate “Success,” the recipient ignores any other returned values and, instead, performs appropriate error handling.

When the size of the Info Response parameters exceeds the maximum size specified in the MaxResponseSize parameter from MIS_Get_Information.request primitive, one or more of the lower order list elements in Info Response parameters must be oMISed.

MIS_Push_Information

MIS_Push_Information.request

Function


This primitive is used by an MIS user (i.e., MIIS Server) to push information to the MN. MIS_Push_Information is generated by the MIIS Server to update policy information following a successful registration. This primitive can be generated at any time during the life time of the registration.

Semantics of service primitive

MIS_Push_Information.request (

DestinationIdentifier,


InfoResponseBinaryDataList,
InfoResponseRDFDataList,
InfoResponseRDFSchemaURLList,
InfoResponseRDFSchemaList
)
Parameters:

Name

Data type

Description

DestinationIdentifier

MISF_ID

The remote MISF, which is the destination of this request.

InfoResponseBinary- DataList

LIST(IR_BIN_DATA)

(Optional) A list of binary representations of Information Elements. This list will be sorted from most preferred first to least preferred last. This list can include vendor specific IE’s for representing network policies.

InfoResponseRDF- DataList

LIST(IR_RDF_DATA)

(Optional) A list of network information in RDF. The list will be sorted from most preferred first to least preferred last. This list can include operator specific RDF data that can be used to represent operator policies.

InfoResponseRDF- SchemaURLList

LIST(IR_SCHM_URL )

(Optional) A list of RDF Schema URL supported by the network. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDF- SchemaList

LIST(IR_RDF_SCHM)

(Optional) A list of RDF Schema content supported by the network. The list will be sorted from most preferred first to least preferred last.

At least one of the following parameters is specified: — InfoResponseBinaryDataList

InfoResponseRDFDataList

InfoResponseRDFSchemaURLList

InfoResponseRDFSchemaList

When generated

This primitive is generated by the MIIS server to update any policies on the MN or to update any other IEs from the MIIS on to the MN.

Effect on receipt

The recipient will return an MIS_Push_Information indication message.

MIS_Push_Information. indication

Function


This primitive is used by the MISF to notify MIS users of the information. This primitive is the result of receipt of an MIS_Push_information indication message from a remote MISF.

Semantics of service primitive

MIS_Push_Information.indication (

SourceIdentifier,


InfoResponseBinaryDataList,
InfoResponseRDFDataList,
InfoResponseRDFSchemaURLList,
InfoResponseRDFSchemaList
)
Parameters:

Name

Data type

Description

SourceIdentifier

MISF_ID

The remote MISF, which is the source of this request.

InfoResponseBinary- DataList

LIST(IR_BIN_DATA)

(Optional) A list of binary representations of Information Elements. This list will be sorted from most preferred first to least preferred last. This list can include vendor specific IEs for representing network policies.

InfoResponseRDF- DataList

LIST(IR_RDF_DATA)

(Optional) A list of network information in RDF. The list will be sorted from most preferred first to least preferred last. This list can include operator specific RDF data that can be used to represent operator policies.

InfoResponseRDF- SchemaURLList

LIST(IR_SCHM_URL )

(Optional) A list of RDF Schema URL supported by the network. The list will be sorted from most preferred first to least preferred last.

InfoResponseRDF- SchemaList

LIST(IR_RDF_SCHM)

(Optional) A list of RDF Schema content supported by the network. The list will be sorted from most preferred first to least preferred last.

When generated

This primitive is generated by the MISF upon receiving an MIS_Push_Information indication message.

Effect on receipt

Upper layer entities take different actions upon notification.



7.4.27 MIS_Push_Key
7.4.27.1 MIS_Push_key.request
7.4.27.1.1 Function
This primitive is used to request a remote MISF (PoS) to install a key(s) in a target PoA(s).
7.4.27.1.2 Semantics of service primitive



MIS_Push_key.request (
DestinationIdentifier, LinkTupleIdentifierList

)

Parameters:





Name


Data type


Description

DestinationIdentifier

MISF_ID

This identifies a remote MISF that will be the destination of this request.

LinkTupleIdentifierList

LIST(LINK_TUPLE_ID)

This identifies a list of links of tar- get PoAs for which keys are pushed.


7.4.27.1.3 When generated
This primitive is generated by an MIS user in the MN to request a remote MISF in the serving PoS to install a key in a target PoA.
7.4.27.1.4 Effect on receipt
The local MISF shall generate an MIS_Push_Key request message to the remote MISF.
7.4.27.2 MIS_Push_key.indication
7.4.27.2.1 Function
This primitive is used to pass a key to the corresponding MIS user on the serving PoS.




7.4.27.2.2 Semantics of service primitive
MIS_Push_key.indication ( SourceIdentifier, KeyMapping

) Parameters:




Name


Data type


Description

SourceIdentifier

MISF_ID

This identifies the invoker, which is a remote MISF.

KeyMapping

KEY_MAPPING

This specifies a mapping of a link identifier for which the key is pushed and a lifetime.


7.4.27.2.3 When generated
This primitive is generated by the local MISF after receiving an MIS_Push_Key request message from the remote MISF.
7.4.27.2.4 Effect on receipt
A media specific key is delivered to the corresponding MIS user.
7.4.27.3 MIS_Push_key.response
7.4.27.3.1 Function
This primitive is used to indicate that the key installation request has been received and MIS user has executed it.
7.4.27.3.2 Semantics of service primitive



MIS_Push_key.response (
DestinationIdentifier, LinkTupleIdentifierList, Status

)

Parameters:





Name


Data type


Description

DestinationIdentifier

MISF_ID

This identifies a remote MISF that will be the destination of this response.

LinkTupleIdentifierList

LIST(LINK_TUPLE_ID)

This identifies a list of links for which keys are pushed.

Status

STATUS

This represents the operation result.






7.4.27.3.3 When generated
This primitive is generated by an MIS user after receiving an MIS_Push_Key.indication primitive.
7.4.27.3.4 Effect on receipt
The local MISF shall generate an MIS_Push_Key response message to the remote MISF.
7.4.27.4 MIS_Push_Key.confirm
7.4.27.4.1 Function
This primitive is used to notify the MIS user (in MN side) about the status of the requested operation.
7.4.27.4.2 Semantics of service primitive



MIS_Push_key.confirm (
SourceIdentifier, LinkTupleIdentifierList, Status

)

Parameters:





Name


Data type


Description

SourceIdentifier

MISF_ID

This identifies the invoker, which is a remote MISF.

LinkTupleIdentifierList

LIST(LINK_TUPLE_ID)

This identifies a list of links for which keys are pushed.

Status

STATUS

This represents the operation result.


7.4.27.4.3 When generated
This primitive is generated after receiving an MIS_Push_Key response message.
7.4.27.4.4 Effect on receipt
A media specific key must be installed in the link layer.
7.4.28 MIS_LL_Auth
The primitives defined are to carry out a proactive authentication over MIS between the MN and the PoS using link layer frames. The authentication is conducted with the media specific authenticator that serves the target PoA.
7.4.28.1 MIS_LL_Auth.request
7.4.28.1.1 Function
This primitive carries link-layer frames for authentication purposes.




7.4.28.1.2 Semantics of service primitive
MIS_LL_Auth.request ( DestinationIdentifier, LinkIdentifier, LLInformation

) Parameters:




Name


Data type


Description

DestinationIdentifier

MISF_ID

This identifies a remote MISF that will be the destination of this request.

LinkIdentifier

LINK_TUPLE_ID

This identifies a PoA that is also the authenticator.

LLInformation

LL_FRAMES

This carries link layer frames.


7.4.28.1.3 When generated
This primitive is generated by an MIS user to start an authentication process based on link-layer frames.
7.4.28.1.4 Effect on receipt
The local MISF shall generate an MIS_LL_Auth request message to the remote MISF.

Download 3.39 Mb.

Share with your friends:
1   ...   8   9   10   11   12   13   14   15   ...   33




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

    Main page