8.4 Terminating Identification Presentation / Configuration / 5GS
34.229-53GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 5: Protocol conformance specification using 5G System (5GS)Release 16TSUser Equipment (UE) conformance specification
8.4.1 Test Purpose (TP)
(1)
with { UE being registered to IMS }
ensure that {
when { UE is made to activate TIP }
then { UE authenticates itself using GBA or Digest }
}
(2)
with { UE having started authentication }
ensure that {
when { UE receives 200 OK concluding the authentication }
then { UE sends HTTP request to activate TIP }
}
(3)
with { UE having concluded activation of TIP }
ensure that {
when { UE is made to de-activate TIP }
then { UE sends HTTP request to de-activate TIP }
}
8.4.2 Conformance Requirements
The conformance requirements covered in the present test case are, unless otherwise stated, Rel-15 requirements.
[TS 24.608 clause 4.2.1]:
The Terminating Identification Presentation (TIP) service provides the originating party with the possibility of receiving trusted information in order to identify the terminating party.
[TS 24.608 clause 4.9.1]:
The TIP service can be activated/deactivated using the active attribute of the <terminating‑identity‑presentation> service element.
8.4.3 Test description
8.4.3.1 Pre-test conditions
System Simulator:
– SS is configured with shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.
– SS is listening to SIP default port 5060 for both UDP and TCP protocols.
– At the SS, a HTTP Server is established at port 80 to simulate the XCAP server
– 1 NR Cell
UE:
– The UE contains either ISIM and USIM applications or only USIM application on UICC.
– UE is configured with the name of the XCAP root directory on the XCAP server and the user’s directory name.
– UE has activated an IPCAN bearer with SS.
Preamble:
– The steps 0a and 0b of Annex A.21 have been executed
– During these procedures the UE may request a DNS server address via NAS signalling and as parallel behaviour the UE may resolve the IP address of the XCAP server via DNS.
8.4.3.2 Test procedure sequence
Table 8.4.3.2-1: Main Behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
UE is triggered for activation of supplementary service TIP. |
– |
– |
– |
– |
2-5b |
Check: Does the UE perform steps 2-5b of the generic test procedure for activation of Supplementary Services according to annex A.21? |
– |
– |
1 |
– |
6 |
Check: Does the Simservs document stored in the SS contain the information supplied by UE as according to table 8.4.3.3-2? |
– |
2 |
P |
|
7 |
UE is triggered for deactivation of supplementary service TIP. |
– |
– |
– |
– |
8-8b |
Check: Does the UE perform steps 8-8b of the generic test procedure for activation of Supplementary Services according to annex A.21? |
– |
– |
3 |
– |
9 |
Check: Does the Simservs document stored in the SS contain the information supplied by UE as according to table 8.4.3.3-3? |
– |
– |
3 |
P |
8.4.3.3 Specific message contents
Table 8.4.3.3-1: Simservs document (step 4)
Derivation Path: TS 24.608 clause 4.9.2 |
|
Content |
Comment |
<simservs> |
|
< terminating-identity-presentation active="false"> |
|
</simservs> |
Table 8.4.3.3-2: Simservs document (step 6)
Derivation Path: TS 24.608 clause 4.9.2 |
|
Content |
Comment |
<simservs> |
|
<terminating-identity-presentation active="true"> |
the "active" attribute may not be present but if present it is set to "true" |
</simservs> |
Table 8.4.3.3-3: Simservs document (step 9)
Derivation Path: TS 24.608 clause 4.9.2 |
|
Content |
Comment |
<simservs> |
|
< terminating-identity-presentation active="false"> |
|
</simservs> |