Call Related Protocol Control and GFT-Control Requirements
Item | Question/Feature | Reference | Status | N/A | Support |
---|---|---|---|---|---|
A1 |
Can the implementation act as a Source PINX for APDUs? |
7.1.1.1 |
o |
Yes[X] No [ ] |
|
A3 |
Sending the Facility information element |
7.1.1.1 |
m |
Yes [X] |
|
A4 |
Receiving the Facility information element |
7.1.1.2 |
m |
Yes [X] |
|
A5 |
Actions at a Source PINX |
7.1.2.1 |
A1:m |
[ ] |
Yes [X] |
A6 |
Actions at a Receiving PINX |
7.1.2.2 |
m |
Yes [X] |
|
A7 |
Can the PINX act as an Originating, Terminating, Incoming or Outgoing Gateway PINX as defined in ECMA-143? |
4 & ECMA-143 |
o.1 |
Yes[X] No [ ] |
|
A8 |
End PINX actions |
7.1.2.2.1 |
A7:m |
[ ] |
Yes [X] |
A9 |
Actions at a Destination PINX |
7.1.2.3 |
m |
Yes [X] |
|
A10 |
Can the PINX act as a Transit PINX as defined in ECMA-143 ? |
4 & ECMA-143 |
o.1 |
Yes[X] No [ ] |
|
A11 |
Transit PINX actions |
7.1.2.2.2 |
A10:m |
[ ] |
Yes [X] |
A12 |
Can the implementation generate notification information ? |
7.4 |
o |
Yes[ ] No [X] |
|
A13 |
Sending notification information |
7.4.2.1 |
A12:m |
[X] |
Yes [ ] |
A14 |
Receiving notification information |
7.4.2.2 |
m |
Yes [X] |
|
A15 |
Actions at a PINX which generates notifications |
7.4.3.1 |
A12:m |
[X] |
Yes [ ] |
A16 |
Actions at a Transit PINX |
7.4.3.2 |
A10:m |
[ ] |
Yes [X] |
A17 |
Actions at a Receiving End PINX |
7.4.3.3 |
A7:m |
[ ] |
Yes [X] |