B.6 INFO 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 INFO method over the II-NNI is based on bilateral agreement between the operators.

The table B.6.1 lists the supported header fields within the INFO request.

Table B.6.1: Supported header fields within the INFO request

Item	Header field	Ref.	RFC status	II-NNI condition
1	Accept	[13], [39]	o	do
2	Accept-Encoding	[13], [39]	o	do
3	Accept-Language	[13], [39]	o	do
4	Allow	[13], [39]	o	do
5	Allow-Events	[20]	o	IF table 6.1.3.1/23 THEN do (NOTE)
6	Authorization	[13], [39]	o	IF table 6.1.3.1/7 THEN do (NOTE)
7	Call-ID	[13], [39]	m	dm
8	Call-Info	[13], [39]	o	do
9	Cellular-Network-Info	[5]	n/a	IF table 6.1.3.1/117 THEN do (NOTE)
10	Content-Disposition	[13], [39]	o	IF dc1 (AOC: clause 12.22) THEN dm ELSE do
11	Content-Encoding	[13], [39]	o	do
12	Content-ID	[216]	o	IF table 6.1.3.1/122 THEN do
13	Content-Language	[13], [39]	o	do
14	Content-Length	[13], [39]	o	do
15	Content-Type	[13], [39]	*	d*
16	CSeq	[13], [39]	m	dm
17	Date	[13], [39]	o	do
18	From	[13], [39]	m	dm
19	Geolocation	[68]	o	do
20	Geolocation-Routing	[68]	o	do
21	Info-Package	[39]	m*	IF table 6.1.3.1/17 THEN do (NOTE)
22	Max-Breadth	[79], [39]	n/a	dn/a
23	Max-Forwards	[13], [39]	o	do
24	MIME-Version	[13], [39]	o	do
25	P-Access-Network-Info	[24], [24B]	o	IF table 6.1.3.1/36 THEN do (NOTE)
26	P-Charging-Function-Addresses	[24]	o	dn/a
27	P-Charging-Vector	[24]	o	IF table 6.1.3.1/38 THEN do (NOTE)
28	Privacy	[34], [39]	o	do
29	Proxy-Authorization	[13], [39]	o	IF table 6.1.3.1/7 THEN do (NOTE)
30	Proxy-Require	[13], [39]	o	do
31	Reason	[48], [39]	o	IF table 6.1.3.1/40 THEN do (NOTE)
32	Record-Route	[13], [39]	o	do
33	Referred-By	[53], [39]	o	do
34	Relayed-Charge	[5]	n/a	dn/a
35	Request-Disposition	[51], [39]	o	do
36	Require	[13], [39]	o	do
37	Resource-Priority	[78], [39]	o	IF table 6.1.3.1/73 THEN do (NOTE)
38	Route	[13], [39]	o	do
39	Security-Client	[47], [39]	o	dn/a
40	Security-Verify	[47], [39]	o	dn/a
41	Session-ID	[124]	m	IF table 6.1.3.1/94 THEN dm (NOTE)
42	Subject	[13], [39]	o	do
43	Supported	[13], [39]	o	do
44	Timestamp	[13], [39]	o	do
45	To	[13], [39]	m	dm
46	User-Agent	[13], [39]	o	do
47	Via	[13], [39]	m	dm
dc1: request invoked due to AOC AND home-to-visited request on roaming II-NNI
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.6.2 lists the supported header fields within the INFO response.

Table B.6.2: Supported header fields within the INFO response

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