5.2 IMS CC test model

34.229-33GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 3: Abstract test suite (ATS)Release 17TSUser Equipment (UE) conformance specification

The test model over E-UTRA is shown in Figure 5.2-1a, the test model over UTRAN is shown in figure 5.2-1b, the test model over WLAN is shown in figure 5.2-1c, the test model over fixed access is shown in figure 5.2-1d (NOTE: the IPsec is not used by this model), and the test model over NR5GC is shown in Figure 5.2-1e.

The IMS CC test cases are executed on top of the multi-testers test model according to TS 36.523-3 [30] for E-UTRA, TS 34.123-3 [4] clause 6A for UTRAN and TS 38.523-3 [54] for NR5GC.

Figure 5.2-1a: Multi-TestersTest Model to support E-UTRA SS interface

Figure 5.2-1b: Multi-Testers Test Model to support UTRAN SS interface

Figure 5.2-1c: Multi-Testers Test Model to support WLAN SS interface

Figure 5.2-1d: Multi-Testers Test Model to support fixed access SS interface

Figure 5.2-1e: Multi-Testers Test Model to support NR5GC SS interface

The IMS CC test cases run on the IMS-PTC which controls the IPCanEmu and the IP-PTC. IPCanEmu is responsible for cell setup and DRB/RAB establishment and the IP-PTC controls the IP related configurations. IPCanEmu and IP-PTC interface to the SS according to TS 36.523-3 [30] or TS 34.123-3 [4] or TS 38.523-3 [54].

Clauses 4.2.4, 4.2.5 and 4.4.1.1 of TS 36.523-3 [30] describe the common handling of IP data in the multi-testers model regarding IMS signalling. In addition to support HTTP over TLS a TCP server may be established with additional parameters for TLS which may be required for XCAP (depending on the authentication mechanism to be applied for XCAP test case).

The test model extensions for support of XCAP are shown in Figure 5.2-2. Clause 5.5 provides further information regarding support of XCAP.

Figure 5.2-2: Extended IP model to handle HTTP/XCAP data

NOTE: Figure 5.2-2 is just an example; further details are SS implementation dependent.