B.9 NOTIFY 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 support of NOTIFY method over the non-roaming II-NNI is based on bilateral agreement between the operators.

The table B.9.1 lists the supported header fields within the NOTIFY request.

Table B.9.1: Supported header fields within the NOTIFY request

Item	Header field	Ref.	RFC status	II-NNI condition
1	Accept	[13], [20]	o	do
2	Accept-Contact	[51]	o	do
3	Accept-Encoding	[13], [20]	o	do
4	Accept-Language	[13], [20]	o	do
5	Allow	[13], [20]	o	do
6	Allow-Events	[20]	o	do
7	Authorization	[13], [20]	o	IF table 6.1.3.1/7 THEN do (NOTE)
8	Call-ID	[13], [20]	m	dm
9	Call-Info	[13]	o	do
10	Cellular-Network-Info	[5]	n/a	IF table 6.1.3.1/117 THEN do (NOTE)
11	Contact	[13], [20]	m	dm
12	Content-Disposition	[13], [20]	o	do
13	Content-Encoding	[13], [20]	o	do
14	Content-ID	[216]	o	IF table 6.1.3.1/122 THEN do
15	Content-Language	[13], [20]	o	do
16	Content-Length	[13], [20]	t	dt
17	Content-Type	[13], [20]	*	d*
18	CSeq	[13], [20]	m	dm
19	Date	[13], [20]	o	do
20	Event	[20]	m	dm
21	Feature-Caps	[143]	o	IF table 6.1.3.1/103 THEN do (NOTE)
22	From	[13], [20]	m	dm
23	Geolocation	[68]	o	do
24	Geolocation-Routing	[68]	o	do
25	History-Info	[25]	o	IF table 6.1.3.1/50 THEN do (NOTE)
26	Max-Breadth	[79]	o	do
27	Max-Forwards	[13], [20]	m	dm
28	MIME-Version	[13], [20]	o	do
29	P-Access-Network-Info	[24], [24B]	o	IF table 6.1.3.1/36 THEN do (NOTE)
30	P-Asserted-Identity	[44]	o	IF table 6.1.3.1/27 THEN do (NOTE)
31	P-Charging-Function-Addresses	[24]	o	dn/a
32	P-Charging-Vector	[24]	o	IF table 6.1.3.1/38 THEN dm (NOTE)
33	P-Preferred-Identity	[44]	o	dn/a
34	Privacy	[34]	o	do
35	Proxy-Authorization	[13], [20]	o	IF table 6.1.3.1/7 THEN do (NOTE)
36	Proxy-Require	[13], [20]	o	do
37	Reason	[48]	o	IF table 6.1.3.1/40 THEN do (NOTE)
38	Record-Route	[13], [20]	o	do
39	Referred-By	[53]	o	do
40	Reject-Contact	[51]	o	do
41	Relayed-Charge	[5]	n/a	dn/a
42	Request-Disposition	[51]	o	do
43	Require	[13], [20]	o	do
44	Resource-Priority	[78]	o	IF table 6.1.3.1/73 THEN do (NOTE)
45	Route	[13], [20]	c	dc
46	Security-Client	[47]	o	dn/a
47	Security-Verify	[47]	o	dn/a
48	Session-ID	[124]	m	IF table 6.1.3.1/94 THEN dm (NOTE)
49	Subscription-State	[20]	m	dm
50	Supported	[13], [20]	o	do
51	Timestamp	[13], [20]	o	do
52	To	[13], [20]	m	dm
53	User-Agent	[13], [20]	o	do
54	Via	[13], [20]	m	dm
55	Warning	[13], [20]	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.

The table B.9.2 lists the supported header fields within the NOTIFY response.

Table B.9.2: Supported header fields within the NOTIFY response

Item	Header field	SIP status code	Ref.	RFC status	II-NNI condition
1	Accept	415	[13], [20]	o	do
2	Accept-Encoding	415	[13], [20]	o	do
3	Accept-Language	415	[13], [20]	o	do
4	Accept-Resource-Priority	2xx 417	[78]	o	IF table 6.1.3.1/73 THEN do (NOTE 2)
5	Allow	405	[13], [20]	m	dm
5	Allow	others	[13], [20]	o	do
6	Allow-Events	2xx	[20]	o	do
6	Allow-Events	489	[20]	m	dm
7	Authentication-Info	2xx	[13], [20]	o	IF table 6.1.3.1/7 THEN do (NOTE 2)
8	Call-ID	100 others	[13], [20]	m	dm
9	Cellular-Network-Info	r	[5]	n/a	IF table 6.1.3.1/117 THEN do (NOTE 2)
10	Contact	2xx	[13], [20]	o	do
		3xx		m	dm
		485		o	do
11	Content-Disposition	r	[13], [20]	o	do
12	Content-Encoding	r	[13], [20]	o	do
13	Content-ID	r	[216]	o	IF table 6.1.3.1/122 THEN do
14	Content-Language	r	[13], [20]	o	do
15	Content-Length	100 others	[13], [20]	t	dt
16	Content-Type	r	[13], [20]	*	d*
17	CSeq	100 others	[13], [20]	m	dm
18	Date	100 others	[13], [20]	o	do
19	Error-Info	3xx-6xx	[13], [20]	o	IF table 6.1.3.1/13 THEN do (NOTE 2)
20	Feature-Caps	2xx	[143]	o	IF table 6.1.3.1/103 THEN do (NOTE 2)
21	From	100 others	[13], [20]	m	dm
22	Geolocation-Error	424	[68]	m	dm
22	Geolocation-Error	others	[68]	o	do
23	MIME-version	r	[13], [20]	o	do
24	P-Access-Network-Info	r	[24], [24A], [24B]	o	IF table 6.1.3.1/36 THEN do (NOTE 2)
25	P-Asserted-Identity	r	[44]	o	IF table 6.1.3.1/27 THEN do (NOTE 2)
26	P-Charging-Function-Addresses	r	[24], [24A]	o	dn/a
27	P-Charging-Vector	100	[24], [24A]	o	dn/a
		18x, 2xx		o	IF table 6.1.3.1/38 THEN dm (NOTE 2)
		3xx-6xx		o	do (NOTE 3)
28	P-Preferred-Identity	r	[44]	o	dn/a
29	Privacy	r	[34]	o	do
30	Proxy-Authenticate	401 (NOTE 1)	[13], [20]	o	do
30	Proxy-Authenticate	407 (NOTE 1)	[13], [20]	m	dm
31	Record-Route	2xx	[13], [20]	o	do
32	Relayed-Charge	r	[5]	n/a	dn/a
33	Require	r	[13], [20]	o	do
34	Response-Source	3xx-6xx	[5]	n/a	IF table 6.1.3.1/121 THEN do (NOTE 2)
35	Restoration-Info	504	[5]	n/a	IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2)
36	Retry-After	404 413 480 486 500 503 600 603	[13], [20]	o	do
37	Security-Server	421 494	[47]	o	dn/a
38	Server	r	[13], [20]	o	do
39	Session-ID	r	[124]	m	IF table 6.1.3.1/94 THEN dm (NOTE 2)
40	Supported	2xx	[13], [20]	o	do
41	Timestamp	r	[13], [20]	o	do
42	To	100 others	[13], [20]	m	dm
43	Unsupported	420	[13], [20]	o	do
44	User-Agent	r	[13], [20]	o	do
45	Via	100 others	[13], [20]	m	dm
46	Warning	r	[13], [20]	o	do
47	WWW-Authenticate	401 (NOTE 1)	[13], [20]	m	dm
47	WWW-Authenticate	407 (NOTE 1)	[13], [20]	o	do
NOTE 1: The SIP status code is only applicable over the roaming II-NNI. NOTE 2: 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.