Facility IE - Networking extensions protocol data unit (NE PDU)
Network facility extension component (NFE) (ISO/IEC 11582)
Network-Facility-Extension
{iso (1) standard (0) pss1-generic-procedures (11582) network-facility-extension (2)}
DEFINITIONS ::=
BEGIN
EXPORTS NetworkFacilityExtension;
IMPORTS PartyNumber FROM Addressing-Data-Data elements
{ iso (1) standard (0) pss1-generic-procedures (11582)
addressing-data-data elements(9)};
NetworkFacilityExtension ::= [10] IMPLICIT SEQUENCE
{ sourceEntity [0] IMPLICIT EntityType,
sourceEntityAddress [1] AddressInformation OPTIONAL,
destinationEntity [2] IMPLICIT EntityType,
destinationEntityAddress [3] AddressInformation OPTIONAL}
EntityType ::= ENUMERATED
{ endPINX(0),
anyTypeOfPINX(1)}
AddressInformation ::= PartyNumber
END -- of Network Facility Extension
Network protocol profile component (NPP) (ISO/IEC 11582)
The NPP component provides a means whereby the originator can identify the protocol that is being signalled via the Facility IE. This may optionally be included when the protocol profile is encoded to "networking extensions". To indicate
"ROSE", the NPP component shall be excluded. If this is not included, the receiver shall assume "ROSE".
The interpretation of the Service components field depends on the coding of the NPP component. If the receiving entity does not recognize or support the indicated NPP coding, the receiving destination entity shall discard the entire Facility IE.
Network-Protocol-Profile-component
{ iso (1) standard (0) pss1-generic-procedures (11582) network-protocol-profile-component (8) }
DEFINITIONS ::=
BEGIN
EXPORTS NetworkProtocolProfile;
NetworkProtocolProfile ::= [18] IMPLICIT INTEGER
{ acse (19),
dse (32)
} (0..254)
END -- of Network-Protocol-Profile-component
Interpretation component (IC) (ISO/IEC 11582)
The Interpretation component provides a means whereby the originator can include optional instructions to the receiving destination entity in the event that the receiver does not understand the operation value of an Invoke component (see Figure D.3).
The network or user may send the IC if the protocol profile field of the Facility information element is coded "networking extensions". Individual ISDN Supplementary Services will specify the conditions under which the network includ
es this component in the Facility IE.
When the network or user receives the Facility information with the protocol profile field coded to "networking extensions", the receiving entity shall be able to accept and act on the Interpretation component if the receiving entity does not understand o
ne of the ROSE Invoke components carried within the Facility IE as follows:
- If the IC is coded to "discardAnyUnrecognisedInvokeComponent", then the receiving entity shall discard any unrecognized Invoke component contained within the Facility information element. It shall process all recognized compo
according to the specific Supplementary Service procedures defined in other ITU-T Recommendations.
- If the IC is coded to "clearCallIfAnyInvokeComponent NotRecognised", the receiving entity shall clear the call if there is at least one Invoke component that is not recognized within the Facility information element and retur
eject component with the Invoke-Problem-Value unrecognized operation.
- If the IC is coded to "rejectAnyUnrecognisedInvokeComponent", then the receiving entity shall discard any unrecognized Invoke component contained within the Facility information element. In addition, for each Invoke component
is unrecognized, the receiving entity shall send the sending entity a Reject component. The receiving entity shall process all recognized components according to the specific Supplementary Service procedures defined in other ITU-T Recommendations.
Interpretation-component
{ iso (1) standard (0) pss1-generic-procedures (11582) interpretation-component (3) }
DEFINITIONS ::=
BEGIN
EXPORTS InterpretationComponent;
InterpretationComponent ::= [11] IMPLICIT ENUMERATED
{discardAnyUnrecognisedInvokePdu(0),
clearCallIfAnyInvokePduNotRecognised(1),
rejectAnyUnrecognisedInvokePdu(2)
-- this coding is implied by the absence of an
-- Interpretation Component.
}
END -- component