Commit ecc51c04 authored by Bostjan Pintar's avatar Bostjan Pintar
Browse files

PSAP TP ACK and MESSAGE added. References updated

parent 675a2d13
Loading
Loading
Loading
Loading
+70 −14
Original line number Diff line number Diff line
@@ -52,6 +52,7 @@ Package NG112_PSAP {
                - isRequestedtoConnect // The PSAP is connecting yet to the ESInet
                - isRequestedtoDisconnect // The PSAP is disconnecting from the ESInet
                - acceptingIncomingCalls // PSAP ready to receive incoming calls
                - acceptingIM // PSAP ready to receive IM(Instant messaging)
                - receives // for packets coming from the network to the IUT
                - sends // for packets sent by the IUT to the network
                - establishesIncomingCall // [ref psap.txt:establishesIncomingCall] The IUT establishes the incoming call
@@ -329,7 +330,7 @@ Package NG112_PSAP {
            "Next Generation 112 LTD [2], clause 4.7",
            "RFC3261 [6]",
            "RFC5301 [7]",
            "RFC5301 [10]"
            "RFC6442 [10]"
        Config Id CFG_PSAP_01
        PICS Selection S_SIP_UDP1 and E_SIP_URN3 and B_SDP_ULA1 and S_SIP_REGISTRATION
        Initial conditions with {
@@ -355,6 +356,33 @@ Package NG112_PSAP {
            }
    } // End of TP_PSAP_SIP_INVITE_BV_08

    Test Purpose {
        TP Id TP_PSAP_SIP_ACK_BV_01
        Test objective 
            "IUT after sending 200 OK INVITE successfully handles an incoming SIP ACK to accept the emergency call" 
        Reference 
            "ETSI TS 103 479 [1], clause 5.4, 6.1.1 and 6.1.2.2",
            "Next Generation 112 LTD [2], clause 4.7",
            "RFC3261 [6]",
            "RFC5301 [7]"
        Config Id CFG_PSAP_01
        PICS Selection S_SIP_UDP1 and E_SIP_URN3 and  S_SIP_REGISTRATION
        Initial conditions with {
            the IUT entity isRegistered to the ESRP entity and
            the IUT entity acceptingIncomingCalls
        }
        Expected behaviour
            ensure that {
                when {
                    the IUT entity sends a SIP_200OK_INVITE
                }
                then {
                    the IUT entity receives a UDP SIP_ACK and
                    the IUT entity establishesIncomingCall
                }
            }
    } // End of TP_PSAP_SIP_ACK_BV_01

    Test Purpose {
        TP Id TP_PSAP_SIP_BYE_BV_01
        Test objective 
@@ -376,7 +404,7 @@ Package NG112_PSAP {
                    the IUT entity receives a SIP_BYE 
                }
                then {
                    the IUT entity sends a SIP_OK
                    the IUT entity sends a SIP_200OK_BYE
                }
            }
    } // End of TP_PSAP_SIP_BYE_BV_01
@@ -401,7 +429,7 @@ Expected behaviour
            the IUT entity sends a SIP_BYE 
        }
        then {
            the IUT entity receives a SIP_OK
            the IUT entity receives a SIP_200OK_BYE
        }
    }
}  //End of TP_PSAP_SIP_BYE_BV_02
@@ -415,23 +443,51 @@ Expected behaviour
            "Next Generation 112 LTD [2], clause 4.7",
            "RFC3261 [6]"
        Config Id CFG_PSAP_01
        PICS Selection M_SIP_URN1 and S_SIP_NO_REGISTRATION
        PICS Selection M_SIP_URN1 and S_SIP_REGISTRATION
        Initial conditions with {
            the IUT entity acceptingIncomingCalls
            the IUT entity acceptingIM
        }
        Expected behaviour
            ensure that {
                when {
                    the IUT entity receives a SIP_MESSAGE 
                    the IUT entity receives a UDP SIP_MESSAGE containing
                        Request_URI indicating value PX_SERVICE_URN ; //"urn:service:sos.police", 
                }
                then {
                    the IUT entity sends a SIP_OK
                    the IUT entity sends a SIP_200OK_MESSAGE
                }
            }
    } // End of TP_PSAP_SIP_MESSAGE_BV_01

    Test Purpose {
        TP Id TP_PSAP_SIP_OPTION_BV_01
        TP Id TP_PSAP_SIP_MESSAGE_BV_02
        Test objective 
            "IUT successfully handles an incoming SIP MESSAGE with Call-info and Geolocation header fields" 
        Reference 
            "ETSI TS 103 479 [1], clause 5.4  and 6.1.2.2 and 6.1.2.3",
            "Next Generation 112 LTD [2], clause 4.7",
            "RFC3261 [6]"
        Config Id CFG_PSAP_01
        PICS Selection M_SIP_URN1 and S_SIP_REGISTRATION
        Initial conditions with {
            the IUT entity acceptingIM
        }
        Expected behaviour
            ensure that {
                when {
                    the IUT entity receives a UDP SIP_MESSAGE containing
                        Request_URI indicating value PX_SERVICE_URN, //"urn:service:sos.police",
                        Geolocation indicating value PX_GEOLOCATION, //"cid:target@example.com"
                        Call_Info indicating value PX_CALL_INFO; //"urn:emergency:uid:callid:..."
                }
                then {
                    the IUT entity sends a SIP_200OK_MESSAGE
                }
            }
    } // End of TP_PSAP_SIP_MESSAGE_BV_02

    Test Purpose {
        TP Id TP_PSAP_SIP_OPTIONS_BV_01
        Test objective 
            "IUT successfully handles an incoming SIP OPTIONS" 
        Reference
@@ -441,7 +497,7 @@ Expected behaviour
        Config Id CFG_PSAP_01
        PICS Selection S_SIP_OPT1 and S_SIP_NO_REGISTRATION
        Initial conditions with {
            the IUT entity acceptingIncomingCalls
            the IUT entity isDisconnected
        }
        Expected behaviour
            ensure that {
@@ -449,10 +505,10 @@ Expected behaviour
                    the IUT entity receives a SIP_OPTIONS 
                }
                then {
                    the IUT entity sends a SIP_OK
                    the IUT entity sends a SIP_200OK_OPTIONS
                }
            }
    } // End of TP_PSAP_SIP_OPTION_BV_01
    } // End of TP_PSAP_SIP_OPTIONS_BV_01
Test Purpose {
TP Id TP_PSAP_SIP_CANCEL_BV_01
Test objective 
@@ -472,8 +528,8 @@ Expected behaviour
            the IUT entity receives a SIP_CANCEL 
        }
        then {
            the IUT entity sends a SIP_OK and
            the IUT entity sends a SIP_487
            the IUT entity sends a SIP_200OK_CANCEL and
            the IUT entity sends a SIP_487_INVITE
        }
    }
}  //End of TP_PSAP_SIP_CANCEL_BV_01
@@ -498,7 +554,7 @@ Expected behaviour
            the IUT entity receives a SIP_INFO 
        }
        then {
            the IUT entity sends a SIP_OK
            the IUT entity sends a SIP_200OK_INFO
        }
    }
}  //End of TP_PSAP_SIP_INFO_BV_01
+3 −2
Original line number Diff line number Diff line
ETSI TS 103 479 [1], [LINK]
ETSI TS 103 479 [1], Core elements for network independent access to emergency services [LINK]
Next Generation 112 LTD [2], http://www.eena.org/uploads/gallery/files/pdf/2013-03-15-eena_ng_longtermdefinitionupdated.pdf
RFC5985 [3], HTTP-Enabled Location Delivery (HELD),  https://tools.ietf.org/html/rfc5985
RFC6753 [4], A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD), https://tools.ietf.org/html/rfc6753
@@ -8,3 +8,4 @@ RFC5301 [7], A Uniform Resource Name (URN) for Emergency and Other Well-Known Se
RFC5491 [8], GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification
RFC5808 [9], Requirements for a Location-by-Reference Mechanism
RFC6442 [10], Location Conveyance in SIP
ETSI TS 103 498 [11], Lightweight Messaging Protocol for Emergency Service Accessibility (LMPE)
 No newline at end of file