7.9A Feature-capability indicators defined within the current document

24.2293GPPIP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Release 18Stage 3TS

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

7.9A.1 General

This subclause describes the feature-capability indicators definitions, according to RFC 6809 [190], that are applicable for the 3GPP IM CN subsystem.

7.9A.2 Definition of feature-capability indicator g.3gpp.icsi-ref

Feature-capability indicator name: g.3gpp.icsi-ref.

Summary of the feature indicated by this feature-capability indicator: Each value of the Service Reference feature-capability indicator indicates the software applications supported by the entity. The values for this feature-capability indicator equal the IMS communication Service Identifier (ICSI) values supported by the entity.

Multiple feature-capability indicator values can be included in the Service Reference feature-capability indicators.

When included in the Feature-Caps header field, according to RFC 6809 [190], the value of this feature-capability indicator contains the IMS communication service identifier (ICSI) of the IMS communication service supported for use:

– in the standalone transaction (if included in a request for a standalone transaction or a response associated with it); or

– in the dialog (if included in an initial request for dialog or a response associated with it);

by the entity which included the Feature-Caps header field.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

When used in a Feature-Caps header field, the g.3gpp-icsi-ref feature-capability indicator is encoded using the feature-cap header field rules specified in clause 6.3 of RFC 6809 [190], where the feature-capability indicator value is an instance of fcap-value-list, listing one or more token values, as specified in RFC 6809 [190].

Examples of typical use: Indicating support of IMS Communication Services to other network entities.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.3 Definition of feature-capability indicators g.3gpp.trf

Feature-capability indicator name: g.3gpp.trf

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 [190] in a SIP INVITE request, indicates that in a roaming scenario, the visited network supports a transit and roaming functionality in order to allow loopback of session requests to the visited network from the home network. When used, it may indicate the URI of the transit and roaming functionality.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

None or string with an equality relationship. When used in a Feature-Caps header field, the value is string and follows the syntax as described in table 7.9A.1 for g-3gpp-trf. The value of g-3gpp-trf parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809 [190].

Table 7.9A.1: ABNF syntax of values of the g.3gpp.trf feature-capability indicator

g-3gpp-trf = "<" SIP-URI ">"

The feature-capability indicator is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This feature-capability indicator is used to indicate visited network support of the roaming architecture for voice over IMS with local breakout and to transport the TRF address.

Examples of typical use: A visited network indicating the presence and support of a TRF in a visited network to the home network.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.4 Definition of feature-capability indicator g.3gpp.loopback

Feature-capability indicator name: g.3gpp.loopback

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 [190] in a SIP INVITE request, indicates the support of the roaming architecture for voice over IMS with local breakout.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

None or a string with an equality relationship.

When used in a Feature-Caps header field, the value is a string identifying the home network and follows the syntax as described in table 7.9A.4-1 for g-3gpp-loopback. The value of g-3gpp-loopback parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809 [190].

Table 7.9A.4-1: ABNF syntax of values of the g-3gpp-loopback feature-capability indicator

g-3gpp-loopback = "<" 1*(qdtext / quoted-pair) ">"

The feature-capability indicator is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This feature-capability indicator is used to indicate support of the roaming architecture for voice over IMS with local breakout and that the INVITE request is a loopback request.

Examples of typical use: The home network indicating when a loopback INVITE request is sent to a visited network.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.5 Definition of feature-capability indicator g.3gpp.home-visited

Feature-capability indicator name: g.3gpp.home-visited

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 [190] in a SIP INVITE request, indicates that the home network supports loopback to the identified visited network for this session. The loopback is expected to be applied at some subsequent entity to the insertion point. The feature-capability indicator carries a parameter value which indicates the visited network.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

String with an equality relationship. When used in a Feature-Caps header field, the value follows the syntax as described in table 7.9A.2 for g-3gpp-home-visited. The value of g-3gpp-home-visited parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809 [190].

Table 7.9A.2: ABNF syntax of values of the g.3gpp.home-visited feature-capability indicator

g-3gpp-home-visited = "<" 1*(qdtext / quoted-pair) ">"

The value follows that used in the P-Visited-Network-ID header field.

The feature-capability indicator is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This feature-capability indicator is used to indicate the home network supports loopback to the identified visited network for this session. The loopback is expected to be applied at some subsequent entity to the insertion point. The feature-capability indicator carries a parameter which indicates the visited network.

Examples of typical use: A home network indicating the home network supports loopback to the identified visited network for this session.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.6 Definition of feature-capability indicator g.3gpp.mrb

Feature-capability indicator name: g.3gpp.mrb

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator when included in a Feature-Caps header field as specified in RFC 6809 [190] in a SIP INVITE request indicates that in a roaming scenario, the visited network supports media resource broker functionality for the allocation of multimedia resources in the visited network. When used, it indicates the URI of the visited network MRB.

Feature-capability indicator specification reference:

3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

String with an equality relationship. When used in a Feature-Caps header field, the value is string and follows the syntax as described in table 7.9A.3 for g-3gpp-mrb. The value of g-3gpp-mrb parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809 [190].

Table 7.9A.3: ABNF syntax of values of the g.3gpp.mrb feature-capability indicator

g-3gpp-mrb = "<" SIP-URI ">"

Examples of typical use: Indicating the URI of the visited network MRB to the home network.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of draft-ietf-sipcore-proxy-feature [190].

7.9A.7 Void

7.9A.8 Definition of feature-capability indicator g.3gpp.registration-token

Feature-capability indicator name: g.3gpp. registration-token

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 [190], indicates the support of using a token to identify the registration used for the request.

This feature-capability indicator can be included in an originating initial request for a dialog or a request for a standalone transaction to identify which registration was used for this request by setting the indicator to the same value as in the g.3gpp.registration-token media feature tag in the Contact header field of the REGISTER request.

This feature-capability indicator can be included in 1xx or 2xx response to a terminating initial request for a dialog or a 2xx response to a request for a standalone transaction to identify which registration was used for the response by setting the indicator to the same value as in the g.3gpp.registration-token media feature tag in the Contact header field of the REGISTER request.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

String with an equality relationship.

When used in a Feature-Caps header field, the value is a string identifying the used registration and follows the syntax as described in table 7.9A.8-1 for g-3gpp-registration-token. The value of g-3gpp-registration-token parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809 [190].

Table 7.9A.8-1: ABNF syntax of values of the g.3gpp.registration-token feature-capability indicator

g-3gpp-registration-token = "<"qdtext">"

Examples of typical use: The S-CSCF includes a media feature tag in a third-party REGISTER request to indicate support of this feature. The value is a unique value identifying this registration among the set of registrations for the registered URI. The S-CSCF includes this token with an identical value as in the previous REGISTER request in subsequent initial requests and responses to indicate its continuous support. An AS supporting this feature can use the value of the token to identify the used registration.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.9 Definition of feature-capability indicator g.3gpp.thig-path

Editor’s note: [IMSProtoc7, CR#5313] this feature-capability indicator is to be registered with IANA when the release 13 is completed.

Feature-capability indicator name: g.3gpp.thig-path

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator when included in a Feature-Caps header field as specified in RFC 6809 [190] in a 200 (OK) response to the REGISTER request indicates that in a roaming scenario, the visited network IBCF supports topology hiding of a Path header field.

Feature-capability indicator specification reference:

3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

String with an equality relationship. When used in a Feature-Caps header field, the value is string and follows the syntax as described in table 7.9A.y for g-3gpp-thig-path. The value of g-3gpp-thig-path parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809 [190].

Table 7.9A.9-1: ABNF syntax of values of the g.3gpp.thig-path feature-capability indicator

g-3gpp-thig-path = "<" SIP-URI ">"

The feature-capability indicator is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This feature-capability indicator is used to indicate that the visited network IBCF supports topology hiding of a Path header field and to pass to the P-CSCF a SIP URI of the visited network IBCF which applied topology hiding on the Path header field.

Examples of typical use: The visited network IBCF includes the g.3gpp.thig-path feature-capability indicator in a 200 (OK) response to the REGISTER request to pass to the P-CSCF a SIP URI of the visited network IBCF which applied topology hiding on the Path header field contained in the REGISTER request.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.10 Definition of feature-capability indicator g.3gpp.priority-share

Feature-capability indicator name: g.3gpp.priority-share.

Summary of the feature indicated by this feature-capability indicator: When included in a Feature-Caps header field in SIP requests or SIP responses the sender indicates that priority sharing is supported.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

When used in a Feature-Caps header field, the g.3gpp.priority-share feature-capability indicator is encoded using the feature-cap header field rules specified in subclause 6.3 of RFC 6809 [190], where the feature-capability indicator value is an instance of fcap-value-list, listing one or more token values, as specified in RFC 6809 [190].

Examples of typical use: Indicating support of priority sharing to other network entities.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

7.9A.11 Definition of feature-capability indicator g.3gpp.verstat

Feature-capability indicator name: g.3gpp.verstat

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 in a 200 (OK) response to a REGISTER request, indicates that the home network supports calling party number verification, as described in RFC 8224.

Feature-capability indicator specification reference:

3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator: Not applicable.

Examples of typical use: Indicating the support of calling number verification in the home network.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809.

7.9A.12 Definition of feature-capability indicator g.3gpp.anbr

Feature-capability indicator name: g.3gpp.anbr

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 in a 200 (OK) response to a REGISTER request, indicates that the network supports ANBR as specified in 3GPP TS 26.114 [9B].

Feature-capability indicator specification reference:

3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator: Not applicable.

Examples of typical use: Indicating the support of ANBR.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809 [190].

Editor’s note (CR#6328, WID: TEI16 + 5G_MEDIA_MTSI_ext): The feature-capability indicator "g.3gpp.anbr" is to be registered with IANA after this CR has been approved at CT#84 and a version of TS 24.229 containing the CR has been published. IANA registration has to happen via the General Protocol Registry Form at http://www.iana.org/cgi-bin/assignments.pl

7.9A.13 Definition of feature-capability indicator g.3gpp.in-call-access-update

Editor’s note: [TEI17, CR#6411] this feature-capability indicator is to be registered with IANA when release 17 is completed.

Feature-capability indicator name: g.3gpp.in-call-access-update

Summary of the feature indicated by this feature-capability indicator:

This feature-capability indicator, when included in a Feature-Caps header field as specified in RFC 6809 [190] in a SIP INVITE request or a response to a SIP INVITE, indicates that the entity supports in-call access update procedure specified in 3GPP TS 24.229. The value of this feature capability indicator is a SIP URI to where the entity can be reached.

Feature-capability indicator specification reference: 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

Values appropriate for use with this feature-capability indicator:

String with an equality relationship. When used in a Feature-Caps header field, the value follows the syntax as described in table 7.9A.13-1 for g-3gpp-in-call-access-update. The value of the g-3gpp-in-call-access-update parameter is an instance of fcap-string-value of Feature-Caps header field specified in RFC 6809.

Table 7.9A.13-1: ABNF syntax of values of the g.3gpp.in-call-access-update feature-capability indicator

g-3gpp-in-call-access-update = "<" SIP-URI ">"

The feature-capability indicator is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This feature-capability indicator is used to indicate that an entity reached by the URI in the value supports mid call updates of e.g. location. The mid-call update is performed by a downstream entity when needed.

Examples of typical use: A network entity indicating support for mid-call updates. A downstream network entity performs the update.

Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of RFC 6809.