B.14 REGISTER method

29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS

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

As described in table 6.1, the REGISTER method is supported only over the roaming II-NNI.

The table B.14.1 lists the supported header fields within the REGISTER request.

Table B.14.1: Supported header fields within the REGISTER request

Item	Header field	Ref.	RFC status	II-NNI condition
1	Accept	[13]	o	do
2	Accept-Encoding	[13]	o	do
3	Accept-Language	[13]	o	do
4	Allow	[13]	o	do
5	Allow-Events	[20]	o	IF table 6.1.3.1/23 THEN do (NOTE)
6	Authorization	[13]	o	IF using IMS AKA OR using SIP digest THEN dm ELSE do
7	Call-ID	[13]	m	dm
8	Call-Info	[13]	o	do
9	Cellular-Network-Info	[5]	n/a	IF table 6.1.3.1/117 THEN do (NOTE)
10	Contact	[13]	o	dm
11	Content-Disposition	[13]	o	do
12	Content-Encoding	[13]	o	do
13	Content-ID	[216]	o	IF table 6.1.3.1/122 THEN do
14	Content-Language	[13]	o	do
15	Content-Length	[13]	t	dt
16	Content-Type	[13]	*	d*
17	CSeq	[13]	m	dm
18	Date	[13]	o	do
19	Expires	[13]	o	do
20	Feature-Caps	[143]	o	IF table 6.1.3.1/103 THEN do (NOTE)
21	From	[13]	m	dm
22	Geolocation	[68]	o	do
23	Geolocation-Routing	[68]	o	do
24	History-Info	[25]	o	IF table 6.1.3.1/50 AND request outside an existing dialog THEN do (NOTE)
25	Max-Breadth	[79]	o	do
26	Max-Forwards	[13]	m	dm
27	MIME-Version	[13]	o	do
28	Organization	[13]	o	do
29	P-Access-Network-Info	[24]	o	IF table 6.1.3.1/36 THEN do (NOTE)
30	P-Charging-Function-Addresses	[24], [24B]	o	dn/a
31	P-Charging-Vector	[24]	o	dm
32	P-User-Database	[60]	o	dn/a
33	P-Visited-Network-ID	[24]	o	dm
34	Path	[43]	o	dm
35	Privacy	[34]	o	dn/a
36	Proxy-Authorization	[13]	o	do
37	Proxy-Require	[13]	o	do
38	Reason	[48]	o	IF table 6.1.3.1/40 THEN do (NOTE)
39	Recv-Info	[39]	o	IF table 6.1.3.1/17 THEN do (NOTE)
40	Referred-By	[53]	o	do
41	Relayed-Charge	[5]	n/a	dn/a
42	Request-Disposition	[51]	o	do
43	Require	[13]	c	dm
44	Resource-Priority	[78]	o	IF table 6.1.3.1/73 THEN do (NOTE)
45	Resource-Share	[5]	n/a	IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/116 THEN do (NOTE)
46	Route	[13]	c	dn/a
47	Security-Client	[47]	o	dn/a
48	Security-Verify	[47]	o	dn/a
49	Session-ID	[124]	m	IF table 6.1.3.1/94 THEN dm (NOTE)
50	Supported	[13]	o	dm
51	Timestamp	[13]	o	do
52	To	[13]	m	dm
53	User-Agent	[13]	o	do
54	Via	[13]	m	dm
NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2.

The table B.14.2 lists the supported header fields within the REGISTER response.

Table B.14.2: Supported header fields within the REGISTER response

Item	Header field	SIP status code	Ref.	RFC status	II-NNI condition
1	Accept	2xx	[13]	o	do
1	Accept	415	[13]	c	dc
2	Accept-Encoding	2xx	[13]	o	do
2	Accept-Encoding	415	[13]	c	dc
3	Accept-Language	2xx	[13]	o	do
3	Accept-Language	415	[13]	c	dc
4	Accept-Resource-Priority	2xx 417	[78]	o	IF table 6.1.3.1/73 THEN do (NOTE)
5	Allow	405	[13]	m	dm
5	Allow	others	[13]	o	do
6	Allow-Events	2xx	[20]	o	IF table 6.1.3.1/23 THEN do (NOTE)
7	Authentication-Info	2xx	[13]	o	do
8	Call-ID	100 others	[13]	m	dm
9	Call-Info	r	[13]	o	do
10	Contact	2xx	[13]	o	dm
10	Contact	3xx 485	[13]	o	do
11	Content-Disposition	r	[13]	o	do
12	Content-Encoding	r	[13]	o	do
13	Content-ID	r	[216]	o	IF table 6.1.3.1/122 THEN do
14	Content-Language	r	[13]	o	do
15	Content-Length	100 others	[13]	t	dt
16	Content-Type	r	[13]	*	d*
17	CSeq	100 others	[13]	m	dm
18	Date	100 others	[13]	o	do
19	Error-Info	3xx-6xx	[13]	o	IF table 6.1.3.1/13 THEN do (NOTE)
20	Feature-Caps	2xx	[143]	o	IF table 6.1.3.1/103 THEN do (NOTE)
21	Flow-Timer	2xx	[65]	o	do
22	From	100 others	[13]	m	dm
23	Geolocation-Error	424	[68]	m	dm
23	Geolocation-Error	others	[68]	o	do
24	History-Info	r	[25]	o	IF table 6.1.3.1/50 AND response to request outside an existing dialog THEN do (NOTE)
25	MIME-version	r	[13]	o	do
26	Min-Expires	423	[13]	m	dm
27	Organization	r	[13]	o	do
28	P-Access-Network-Info	r	[24], [24A], [24B]	o	IF table 6.1.3.1/36 THEN do (NOTE)
29	P-Associated-URI	2xx	[24]	o	dm
30	P-Charging-Function-Addresses	r	[24], [24A]	o	dn/a
31	P-Charging-Vector	100	[24], [24A]	o	dn/a
		18x, 2xx		o	dm
		3xx-6xx		o	do
32	Path	2xx	[43]	o	dm
33	Privacy	r	[34]	o	do
34	Proxy-Authenticate	401	[13]	o	do
34	Proxy-Authenticate	407	[13]	m	dm
35	Relayed-Charge	r	[5]	n/a	dn/a
36	Require	r	[13]	c	dc
37	Response-Source	3xx-6xx	[5]	n/a	IF table 6.1.3.1/121 THEN do (NOTE)
38	Retry-After	404 413 480 486 500 503 600 603	[13]	o	do
39	Security-Server	2xx 401	[47]	n/a	dn/a
39	Security-Server	421 494	[47]	o	dn/a
40	Server	r	[13]	o	do
41	Service-Route	2xx	[45]	o	dm
42	Session-ID	r	[124]	m	IF table 6.1.3.1/94 THEN dm (NOTE)
43	Supported	2xx	[13]	o	do
44	Timestamp	r	[13]	o	do
45	To	100 others	[13]	m	dm
46	Unsupported	420	[13]	m	dm
47	User-Agent	r	[13]	o	do
48	Via	100 others	[13]	m	dm
49	Warning	r	[13]	o	do
50	WWW-Authenticate	401	[13]	m	dm
50	WWW-Authenticate	407	[13]	o	do
NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2.