7.9 Media feature tags 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

7.9.1 General

This subclause describes the media feature tag definitions that are applicable for the 3GPP IM CN subsystem.

7.9.2 Definition of media feature tag g.3gpp.icsi-ref

Media feature-tag name: g.3gpp.icsi-ref.

ASN.1 Identifier: 1.3.6.1.8.2.4

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

The Service Reference media feature tag is defined to fulfil the requirements for forking to an appropriate UE when multiple UEs are registered and dispatch to an appropriate application within the UE based upon the IMS communication Service Identifier (ICSI) values as stated in 3GPP TS 23.228 [7].

Multiple tag-values can be included in the Service Reference media feature-tag.

Values appropriate for use with this feature-tag: Token with an equality relationship.

The feature-tag is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms:

This feature-tag is most useful in a communications application, for describing the capabilities of a device, such as a phone or PDA.

Examples of typical use: Routeing an IMS Communication Session to a device that supports a particular software application or understands a particular service.

Related standards or documents:

3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), stage 3"

Security Considerations: Security considerations for this media feature-tag are discussed in subclause 11.1 of RFC 3840 [62].

7.9.3 Definition of media feature tag g.3gpp.iari-ref

Media feature-tag name: g.3gpp.iari-ref.

ASN.1 Identifier: 1.3.6.1.8.2.5

Summary of the media feature indicated by this tag: Each value of the Application Reference media feature-tag indicates the software applications supported by the agent. The values for this tag equal IMS Application Reference Identifier (IARI) values supported by the agent

The Application Reference media feature tag is defined to fulfil the requirements for forking to an appropriate UE when multiple UEs are registered and dispatch to an appropriate application within the UE based upon and IMS Application Reference Identifier (IARI) values as stated in 3GPP TS 23.228 [7].

Multiple tag-values can be included in the Application Reference media feature-tag.

Values appropriate for use with this feature-tag: Token with an equality relationship.

The feature-tag is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms:

This feature-tag is most useful in a communications application, for describing the capabilities of a device, such as a phone or PDA.

Examples of typical use: Routeing an IMS Application Session to a device that supports a particular software application or understands a particular application.

Related standards or documents:

3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), stage 3"

Security Considerations: Security considerations for this media feature-tag are discussed in subclause 11.1 of RFC 3840 [62].

7.9.4 Void

7.9.5 Void

7.9.6 Void

7.9.7 Definition of media feature tag g.3gpp.registration-token

Media feature tag name: g.3gpp.registration-token

ASN.1 Identifier: 1.3.6.1.8.2.27

Summary of the media feature indicated by this media feature tag:

This media feature tag, when included in a third party SIP REGISTER request, indicates the support of using a token to identify the registration used for the request. The mediafeature tag is assigned a value that can be used by the receiving AS to later identify the used registration for initial requests from an originating user or dialog forming responses from a terminating user.

Media feature tag 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 media feature tag:

String with an equality relationship.

Table 7.9.7-1: ABNF syntax of values of the g.3gpp.registration-token media feature tag

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

The media feature tag is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This media feature tag is used to indicate support of using a token to identify the registration used for the current request or response among the set of registrations for the registered URI. As the token is unique per URI, different URIs for different users can have the same value of the token.

Examples of typical use: The S-CSCF includes this 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 a token with identical value in subsequent initial requests and responses. An AS supporting this feature can use the value of the token to identify the used registration.

Security Considerations: Security considerations for this media feature-tag are discussed in subclause 11.1 of RFC 3840 [62].

7.9.8 Definition of media feature tag g.3gpp.ps-data-off

Media feature tag name: g.3gpp.ps-data-off.

ASN.1 Identifier: 1.3.6.1.8.2.35

Summary of the feature indicated by this media feature tage: This media feature tag when included in a Contact header field in a REGISTER request indicates the status of the 3GPP PS data off for the registration time.

This media feature tag, when included in the Contact header field in a REGISTER request indicates that the UE supports the 3GPP PS data off. The g.3gpp.ps-data-off media feature tag can take a value that indicates whether the 3GPP PS data off has been activated or deactivated by the user at the UE.

Media feature tag 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 media feature tag:

String with an equality relationship

Table 7.9.8-1: ABNF syntax of values of the g.3gpp.ps-data-off media feature tag

g-3gpp-ps-data-off = "active" / "inactive" / token

Examples of typical use: Indicating support and activation status of the 3GPP PS data off function to IMS network entities.

Security Considerations: Security considerations for this media feature tag are discussed in clause 9 of RFC 6809 [190].

7.9.9 Definition of media feature tag g.3gpp.rlos

Media feature-tag name: g.3gpp.rlos

ASN.1 Identifier: 1.3.6.1.8.2.x

Editor’s note: : [WID PARLOS, CR#6326] the ASN.1 Identifier will need to be updated once the IANA registration is completed.

Editor’s note: [WID PARLOS, CR#6326] this media feature tag is to be registered with IANA when the release 16 is completed.

Summary of the media feature indicated by this tag: This feature-tag when used in a SIP REGISTER request indicates that the function sending the SIP message supports restricted local operator service.

Values appropriate for use with this feature-tag: Boolean

The feature-tag is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This feature-tag is most useful in a communications application, for describing the capabilities of a device, such as a phone or PDA.

Examples of typical use: Indicating that a mobile phone supports the restricted local operator service

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

Security Considerations: Security considerations for this media feature-tag are discussed in subclause 12.1 of IETF RFC 3840 [53].