C.2b Generic Registration Test Procedure – SIP digest without TLS – EPC

34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The generic test procedure:

1. P-CSCF statically allocated to the UE or optional P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4.

2. The UE initiates IMS registration. SS waits for the UE to send an initial REGISTER request.

3. The SS responds to the initial REGISTER request with a valid 401 Unauthorized response.

4. The SS waits for the UE to send another REGISTER request,

5. The SS responds to the second REGISTER request with valid 200 OK response,

6. The SS waits for the UE to send a SUBSCRIBE request.

7. The SS responds to the SUBSCRIBE request with a valid 200 OK response.

8. The SS sends a valid NOTIFY request for the subscribed registration event package.

9. The SS waits for the UE to respond to the NOTIFY with a 200 OK response.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				P-CSCF statically allocated to the UE or optional, P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4.
2	🡪		REGISTER	The UE sends initial registration for IMS services. The UE should (as for TS 24.229 E.3.1.3) additionally populate the header with an Authorization header field (as defined in RFC 2617 [16], including the "username", "realm", "uri", "nonce" and "response") with a Contact header field (including the port value of an unprotected port where the UE expects to receive subsequent requests) and with the Via header field (including port value of an unprotected port where the UE expects to receive responses to the request).
3	🡨		401 Unauthorized	The SS responds with a 401 Unauthorized response with a WWW-Authenticate header field (containing at least one challenge applicable to the requested resource) and with the "algorithm" Authorization header field parameter set to "MD5".
4	🡪		REGISTER	The UE completes the security negotiation procedures sending another REGISTER request containing an Authorization header field populated as defined in Step 2, with the addition of the Authorization header field containing a challenge response, constructed using the stored “nonce” value for authentication for the same registration "cnonce", "qop", and "nonce-count" header field parameters as indicated in RFC 2617 [16].
5	🡨		200 OK	The SS responds with 200 OK.
6	🡪		SUBSCRIBE	The UE subscribes to its registration event package.
7	🡨		200 OK	The SS responds with 200 OK.
8	🡨		NOTIFY	The SS sends initial NOTIFY for registration event package, containing full registration state information for the registered public user identity in the XML body
9	🡪		200 OK	The UE responds with 200 OK.

NOTE 1: The default message contents in annex A are used.