8.13 Communication Forwarding on Subscriber Not Reachable / 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.13.1 Test Purpose (TP)
(1)
with { UE being registered to IMS }
ensure that {
when { UE is made to activate CFNRc }
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 CFNRc }
}
(3)
with { UE having concluded activation of CFNRc }
ensure that {
when { UE is made to de-activate CFNRC }
then { UE sends HTTP request to de-activate CFNRc }
}
8.13.2 Conformance Requirements
The conformance requirements covered in the present test case are, unless otherwise stated, Rel-15 requirements.
Communication Forwarding on Subscriber Not Reachable (CFNRc)
The CFNRc service enables an user to have the network redirect all incoming communications, when the user is not reachable (e.g. there is no IP connectivity to the user’s terminal), to another user. The CFNRc service may operate on all communications, or just those associated with specified services. The user’s ability to originate communications is unaffected by the CFNRc simulation service.
As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNRc service has been activated. This indication may be provided when the user originates a communication if the CFNRc service has been activated for the user and for the service requested for the communication.
The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
8.13.3 Test description
8.13.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.13.3.2 Test procedure sequence
Table 8.13.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
UE is triggered for activation of supplementary service CFNRC |
– |
– |
– |
– |
|
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.13.3.3-2? |
– |
2 |
P |
|
|
7 |
UE is triggered for deactivation of supplementary service CFNRC |
– |
– |
– |
– |
|
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.13.3.3-3? |
– |
– |
3 |
P |
8.13.3.3 Specific message contents
Table 8.13.3.3-1: Simservs document (step 4)
|
Derivation Path: TS 24.604 clause 4.9.2 |
|
|
Content |
Further restrictions/Comments |
|
<simservs |
|
|
<communication-diversion 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> |
|
|
<not-reachable/> |
|
|
<rule-deactivated/> |
containing a <rule-deactivated> element |
|
</cp:conditions> |
|
|
<cp:actions> |
|
|
<forward-to> |
|
|
<target> px_XCAP_TargetUri</target> |
|
|
<notify-caller>true</notify-caller> |
|
|
</forward-to> |
|
|
</cp:actions> |
|
|
</cp:rule> |
|
|
</cp:ruleset> |
|
|
</communication-diversion> |
|
|
</simservs> |
|
Table 8.13.3.3-2: Simservs document (step 6)
|
Derivation Path: TS 24.604 clause 4.9.2 |
|
|
Content |
Further restrictions/Comments |
|
<simservs |
|
|
<communication-diversion 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> |
not containing a <rule-deactivated> element |
|
<not-reachable/> |
|
|
</cp:conditions> |
|
|
<cp:actions> |
|
|
<forward-to> |
|
|
<target> px_XCAP_TargetUri</target> |
|
|
<notify-caller>true</notify-caller> |
|
|
</forward-to> |
|
|
</cp:actions> |
|
|
</cp:rule> |
|
|
</cp:ruleset> |
|
|
</communication-diversion> |
|
|
</simservs> |
|
Table 8.13.3.3-3: Simservs document (step 9)
|
Derivation Path: TS 24.604 clause 4.9.2 |
|
|
Content |
Further restrictions/Comments |
|
<simservs |
|
|
<communication-diversion 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> |
|
|
<not-reachable/> |
|
|
<rule-deactivated/> |
containing a <rule-deactivated> element |
|
</cp:conditions> |
|
|
<cp:actions> |
|
|
<forward-to> |
|
|
<target> px_XCAP_TargetUri</target> |
|
|
<notify-caller>true</notify-caller> |
|
|
</forward-to> |
|
|
</cp:actions> |
|
|
</cp:rule> |
|
|
</cp:ruleset> |
|
|
</communication-diversion> |
|
|
</simservs> |
|