C.2a Generic Registration Test Procedure – GIBA – UMTS/EPS
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
The generic test procedure:
1 EPS bearer context activation according annex C.18 for UE with E-UTRA support (TS 34.229-2 A.18/1). PDP context activation according annex C.17 for UE with UTRA support (TS 34.229-2 A.18/2) only.
2 void
3 Optional P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4.
4 The UE initiates IMS registration indicating support ofGIBA. SS waits for the UE to send an initial REGISTER request.
5 The SS responds to the 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 |
Annex C.17 or C.18. |
|||
|
2 |
Void. |
|||
|
3 |
Optional P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4. |
|||
|
4 |
🡪 |
REGISTER |
The UE sends initial registration for IMS services indicating support for GIBA procedure by not including an Authorization header field. |
|
|
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.
NOTE 2: The procedure described in C.5 on PUBLISH requests can happen in parallel to steps 6-9.