8.25 Barring of Incoming Calls / When Roaming / 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.25.1 Test Purpose (TP)
(1)
with { UE being registered to IMS }
ensure that {
when { UE is made to activate Barring of Incoming Calls When Roaming (ICB roam) }
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 ICB roam }
}
(3)
with { UE having concluded activation of ICB roam }
ensure that {
when { UE is made to de-activate ICB roam }
then { UE sends HTTP request to de-activate ICB roam }
}
8.25.2 Conformance Requirements
The conformance requirements covered in the present test case are, unless otherwise stated, Rel-15 requirements.
[TS 24.611, clause 4.2.1]:
The Incoming Communication Barring (ICB) service makes it possible for a user to have barring of certain categories of incoming communications according to a provisioned or user configured barring program and is valid for all incoming communications. A barring program is expressed as a set of rules in which the rules have a conditional part and an action part. Examples of conditions are whether the asserted originating public user identity matches a specific public user identity or whether the originating public user identity is restricted (anonymous). The action part could specify for a rule that contains a matching condition that the specific incoming communication is barred. The complete set of conditions and actions that apply to this service and their semantics is described in subclause 4.9.
[TS 24.611, clause 4.9.1.4]:
roaming: This condition evaluates to true when the served user is registered from an access network other than the served users home network.
NOTE 3: Whether the served user is registered from another network then the served users home network can be determined from the P-Visited-Network-ID header field specified in IETF RFC 7315 [15] and the P-Access-Network-Info header field specified in IETF RFC 7315 [15] both are provided during the registration process, see 3GPP TS 24.229 [2], clause 5.7.1.3.
8.25.3 Test description
8.25.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.25.3.2 Test procedure sequence
Table 8.25.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
UE is triggered for activation of supplementary service ICB roam. |
– |
– |
– |
– |
|
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.25.3.3-2? |
– |
– |
2 |
P |
|
7 |
UE is triggered for deactivation of supplementary service ICB roam. |
– |
– |
– |
– |
|
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.25.3.3-3? |
– |
– |
3 |
P |
8.25.3.3 Specific message contents
Table 8.25.3.3-1: Simservs document (step 4)
|
Derivation Path: TS 24.611 clause 4.9.2 |
|
|
Content |
Further restrictions/Comments |
|
<simservs |
|
|
<incoming-communication-barring active=true> |
the "active" attribute may not be present but if present it is set to "true" |
|
<cp:ruleset> |
|
|
<cp:rule id=rule1> |
|
|
<cp:conditions> |
|
|
<roaming/> |
|
|
<rule-deactivated/> |
containing a <rule-deactivated> element |
|
</cp:conditions> |
|
|
<cp:actions> |
|
|
<allow>false</allow> |
|
|
</cp:actions> |
|
|
</cp:rule> |
|
|
</cp:ruleset> |
|
|
</incoming-communication-barring> |
|
|
</simservs> |
|
Table 8.25.3.3-2: Simservs document (step 6)
|
Derivation Path: TS 24.611 clause 4.9.2 |
|
|
Content |
Further restrictions/Comments |
|
<simservs |
|
|
<incoming-communication-barring active="true" > |
the "active" attribute may not be present but if present it is set to "true" |
|
<cp:ruleset> |
|
|
<cp:rule id=rule1> |
list of conditions not containing a <rule-deactivated> element |
|
<cp:conditions> |
|
|
<roaming/> |
|
|
</cp:conditions> |
|
|
<cp:actions> |
|
|
<allow>false</allow> |
|
|
</cp:actions> |
|
|
</cp:rule> |
|
|
</cp:ruleset> |
|
|
</incoming-communication-barring> |
|
|
</simservs> |
|
Table 8.25.3.3-3: Simservs document (step 9)
|
Derivation Path: TS 24.611 clause 4.9.2 |
|
|
Content |
Further restrictions/Comments |
|
<simservs |
|
|
<incoming-communication-barring active=true> |
the "active" attribute may not be present but if present it is set to "true" |
|
<cp:ruleset> |
|
|
<cp:rule id=rule1> |
|
|
<cp:conditions> |
|
|
<roaming/> |
|
|
<rule-deactivated/> |
containing a <rule-deactivated> element |
|
</cp:conditions> |
|
|
<cp:actions> |
|
|
<allow>false</allow> |
|
|
</cp:actions> |
|
|
</cp:rule> |
|
|
</cp:ruleset> |
|
|
</incoming-communication-barring> |
|
|
</simservs> |
|