hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.1 General
|
The SDP attributes associated with OMR are used to identify and select alternative media plane paths for the purpose of bypassing unneeded media functions in the network, as described in 3GPP TS 29.079 [11D].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.2 Semantics
|
The visited-realm attribute contains an IP realm identifier and transport address for a media function in the media plane that can potentially be used to bypass other allocated media functions.
The secondary-realm attribute contains an IP realm identifier and transport address for an alternate media function in the media plane that can potentially be used to bypass other allocated media functions.
The omr-s-cksum and omr-m-cksum attributes includes checksums for session level information and media level information to identify if the SDP was altered by intermediaries in such a way as to invalidate OMR information present in the SDP.
The "omr-codecs", "omr-m-att" and "omr-s-att" attributes contain codec-related SDP offer information encapsulated by a SIP-ALG in the signalling path that has modified codec related information.
The "omr-m-bw" and "omr-s-bw" attributes contain bandwidth-related SDP offer information encapsulated by a SIP-ALG in the signalling path that has modified codec related information.
Each group of zero or more versions of each of the "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw" and "omr-s-bw" attributes for a media line with the same instance number is associated with the visited-realm instance for the modified media line and represents the version of the SDP information for the media line before modifications.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.3 Syntax
|
The syntax specified in table 7.5.2 uses the augmented Backus-Naur Form as described in RFC 2234 [20G].
Table 7.5.2: Syntax OMR attributes
visited-realm = "visited-realm" ":" instance-number SP
realm SP
nettype SP ;from RFC 4566 [39]
addrtype SP ;from RFC 4566 [39]
connection-address SP ;from RFC 4566 [39]
port ;from RFC 4566 [39]
[SP rtcp-port [SP rtcp-address]]
*(SP extension-name SP extension-value)
secondary-realm = "secondary-realm" ":" instance-number SP
realm SP
nettype SP ;from RFC 4566 [39]
addrtype SP ;from RFC 4566 [39]
connection-address SP ;from RFC 4566 [39]
port ;from RFC 4566 [39]
[SP rtcp-port [SP rtcp-address]]
*(SP extension-name SP extension-value)
instance-number = 1*DIGIT
realm = non-ws-string ;from RFC 4566 [39]
rtcp-port = "rtcp-port" SP port
rtcp-address = "rtcp-address" SP connection-address
extension-name = token ;shall be different to existing tokens "previsous-fmt",
"rtcp-port" and "rtcp-address".
extension-value = non-ws-string
omr-m-cksum = "omr-m-cksum" ":" 1*HEXDIG
omr-s-cksum = "omr-s-cksum" ":" 1*HEXDIG
omr-codecs = "omr-codecs" ":" instance-number SP proto 1*(SP fmt) ;from RFC 4566 [39]
omr-m-att = "omr-m-att" ":" instance-number SP attribute ;from RFC 4566 [39]
omr-s-att = "omr-s-att" ":" instance-number SP attribute ;from RFC 4566 [39]
omr-m-bw = "omr-m-bw" ":" instance-number SP bwtype ":" bandwidth ;from RFC 4566 [39]
omr-s-bw = "omr-s-bw" ":" instance-number SP bwtype ":" bandwidth ;from RFC 4566 [39]
This grammar encodes the primary media level information about each visited-realm and secondary-realm instance: the sequence in which the realm was visited, the realm identity, its IP address and port:
<instance-number>: instance-number is a positive decimal integer which identifies the sequence in which this visited-realm was added during the forwarding of an SDP offer. If an IMS-ALG adds second-realm attribute(s), omr-codecs attribute(s), omr-m-att attribute(s), omr-s-att attribute(s), omr-m-bw attribute(s) and/or the omr-s-bw attribute(s) to an SDP offer it will assign the same instance number as assigned to the visited-realm attribute for the forwarded SDP offer. When used in the SDP answer, the instance-number, realm, nettype and addrtype uniquely identify the corresponding visited-realm or secondary-realm instance from the SDP offer.
<realm>: identifies a set of mutually reachable IP endpoints that share a common IP addressing scheme.
Effective application of OMR depends on the scope of each realm being determined by reachability and not by administrative domain. A public IPv4 or IPv6 address reachable from the open internet shall be associated with the special realm "IN". For application to OMR in IPv6 networks, a realm corresponds to an IPv6 autonomous system.
Entity operators must adhere to the following guidelines for creation of an OMR realm string to ensure the integrity of the visited-realm and secondary-realm instance information for their realm(s): 1) Realm strings must be globally unique. It is recommended that a realm string contain a hostname or domain name, following the recommendation in subclause 3.3 of RFC 7616 [286], 2) Realm strings should present a human-readable identifier that can be rendered to a user.
<nettype>, <addrtype> and <connection-address>: are taken from the connection-field (c= line) of RFC 4566 [39]. They describe the IP address associated with the visited-realm or secondary-realm instance, allowing for IPv4 addresses, IPv6 addresses and FQDNs. The connection-address can be either an IP address or an FQDN.
<port>: It is the port associated with the visited-realm or secondary-realm instance as taken from RFC 4566 [39]. Its meaning depends on the network being used for the connection-address, and on the transport protocol selected for the corresponding media line, e.g., UDP or TCP.
<rtcp-port> and <rtcp-address>: taken together are semantically equivalent to the rtcp attribute defined in RFC 3605 [37A]. They optionally encode the RTCP port and address information when the RTCP port number is not exactly one greater than the port for an RTP stream at the same address.
The previous-fmt-list may be supplied within the visited-realm if this attribute is included in an SDP offer and shall not be supplied if this attribute is included in an SDP answer.
The visited-realm and secondary-realm attributes can be extended via <extension-name> and <extension-value>. The grammar allows for new name/value pairs to be added at the end of the attribute.
<omr-m-cksum>: is a hex value calculated on the contents of the media level information per media line.
<omr-s-cksum>: is a hex value calculated on the contents of the session level information.
<omr-codecs> provides the transport format <proto> and list of media formats (e.g., payload type numbers) <fmt> supported by the visited-realm instance immediately preceding the instance identified by <instance-number>. Transport format <proto> and media format <fmt> are defined in RFC 4566 [39] for the SDP m-line.
<omr-m-att> provides a media level SDP attribute <attribute> supported by the visited-realm instance immediately preceding the instance identified by <instance-number>. Attribute <attribute> is defined in RFC 4566 [39] for the SDP a-line.
<omr-s-att> provides a session level SDP attribute <attribute> supported by the visited-realm instance immediately preceding the instance identified by <instance-number>. Attribute <attribute> is defined in RFC 4566 [39] for the SDP a-line.
<omr-m-bw> provides a media level SDP bandwidth described by <bwtype> and <bandwidth> supported by the visited-realm instance immediately preceding the instance identified by <instance-number>. <bwtype> and <bandwidth> are defined in RFC 4566 [39] for the SDP b-line.
<omr-s-bw> provides a session level SDP bandwidth described by <bwtype> and <bandwidth> supported by the visited-realm instance immediately preceding the instance identified by <instance-number>. <bwtype> and <bandwidth> are defined in RFC 4566 [39] for the SDP b-line.
The "visited-realm", "secondary-realm", "omr-m-cksum", "omr-s-cksum", "omr-codecs", "omr-m-att", "omr-s-att" "omr-m-bw" and "omr-s-bw" SDP attributes are media-level attributes.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4 IANA registration
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.1 visited-realm attribute
|
Contact Name:3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: visited-realm
Long Form: visited-realm
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. This attribute is used to identify configurations in which IP realms are re-entered when establishing an end-to-end multimedia session, so that border gateways can be bypassed without compromising their role in securing access to the networks. The attribute provides a means to identify connection information for visited IP realms to help select the most optimal available path.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.2 secondary-realm attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: secondary-realm
Long Form: secondary-realm
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. This attribute is used to identify configurations in which secondary IP realms are available to establish an end-to-end multimedia session, so that border gateways can be bypassed without compromising their role in securing access to the networks. The attribute provides a means to identify connection information for secondary IP realms to help select the most optimal available path.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.3 omr-s-cksum attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-s-cksum
Long Form: omr-s-cksum
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. This attribute is used to provide a means to verify that session level SDP information has not been modified by intermediate SIP nodes not supporting the OMR procedures. The attribute provides a checksum calculated value against the session level information. Any OMR information associated with unexpectedly modified media information will be discarded.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.4 omr-m-cksum attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-m-cksum
Long Form: omr-m-cksum
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. This attribute is used to provide a means to verify that media level SDP information has not been modified by intermediate SIP nodes not supporting the OMR procedures. The attribute provides a checksum calculated value against the media level information associated with the media stream for which the checksum is provided. Any OMR information associated with unexpectedly modified media information will be discarded.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.5 omr-codecs attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-codecs
Long Form: omr-codecs
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. The attribute provides a means to encapsulate codec related SDP information transport format and list of media formats that are applicable if a particular border gateway is bypassed.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.6 omr-m-att attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-m-att
Long Form: omr-m-att
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. The attribute provides means to encapsulate a media-level SDP attribute that is applicable if a particular border gateway is bypassed.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.7 omr-s-att attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-s-att
Long Form: omr-s-att
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. The attribute provides means to encapsulate a session-level SDP attribute that is applicable if a particular border gateway is bypassed.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.8 omr-m-bw attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-m-bw
Long Form: omr-m-bw
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. The attribute provides means to encapsulate a media-level SDP bandwidth that is applicable if a particular border gateway is bypassed.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.3.4.9 omr-s-bw attribute
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: omr-s-bw
Long Form: omr-s-bw
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks employing OMR procedures allowing to bypass border gateways in configurations in which IP realms are re-entered when establishing an end-to-end multimedia session. The attribute provides means to encapsulate a session-level SDP bandwidth that is applicable if a particular border gateway is bypassed.
Appropriate Values: See table 7.5.2.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4 Media plane optimization for WebRTC
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.1 General
|
The SDP attributes associated with media plane optimization procedures for WebRTC are used to encapsulate an SDP offer or SDP answer received from a WIC, as described in 3GPP TS 23.228 [7], annex U.2.4.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.2 Semantics
|
The "tra-m-line" and "tra-att" SDP attributes contain media-related SDP information which is applicable if optimized transparent media between WICs are selected. In the SDP offer, the attributes describe the offered transparent media which can be selected. In the SDP answer, the presence of the attributes indicates that the transparent media have been selected and the attributes which have been selected.
The "tra-SCTP-association" SDP attribute indicates for a media line that the related optimized transparent media are transported in the indicated SCTP association. The optimized transparent media related to several media lines can be transported in the same SCTP association.
The "tra-bw" SDP attribute contains bandwidth-related SDP information which is applicable if the optimized transparent media between WICs are selected. In the SDP offer, the attributes describe the bandwidths the offerer wants to receive for transparent media. In the SDP answer, the attributes describe the bandwidths the answerer wants to receive for transparent media.
The "tra-contact" SDP attribute in the SDP offer encapsulate address information which is compared with the address information in contact by the receiving eP-CSCF to detect whether intermediates that do not support switching to transparent media between WICs are in the path.
The "tra-media-line-number" SDP attribute provides the total number of media lines in the SDP, excluding any media lines with port zero, which is compared with the real number of media lines in the SDP, excluding any media lines with port zero, by the receiving eP-CSCF to detect whether intermediates have removed or dissabled media lines.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.3 Syntax
|
The syntax specified in table 7.5.4.3-1 uses the augmented Backus-Naur Form as described in RFC 2234 [20G].
Table 7.5.4.3-1: Syntax of media plane optimization for WebRTC related SDP attributes
tra-contact = "tra-contact" ":" nettype SP addrtype SP connection-address
; from RFC 4566 [39]
tra-m-line = "tra-m-line" ":" media SP port ["/" integer] proto 1*(SP fmt)
; from RFC 4566 [39]
tra-att = "tra-att" ":" attribute ; from RFC 4566 [39]
tra-bw = "tra-bw" ":" bwtype ":" bandwidth ; from RFC 4566 [39]
tra-SCTP-association = "tra-SCTP-association" ":" SCTP-association-number
tra-media-line-number = "media-line-number" ":" m-line-number
SCTP-association-number = integer
m-line-number = integer
This grammar encodes the media level information received in an initial SDP offer from a WIC.
<tra-contact>: It is the contact used in the outgoing SDP offer which contains encapsulated media information. It contains nettype, addrtype and connection-address. Nettype, addrtype and connection-address are defined in RFC 4566 [39].
<tra-m-line>: provides the media <media>, port <port>, transport format <proto> and list of media formats (e.g., payload type numbers) <fmt> in the received SDP offer. Media <media>, port <port>, transport format <proto> and media format <fmt> are defined in RFC 4566 [39] for the SDP m-line.
<tra- att> provides an encapsulated SDP attribute <attribute> supported by the sender of the offer. Attribute <attribute> is defined in RFC 4566 [39] for the SDP a-line.
<tra- bw> provides an SDP bandwidth described by <bwtype> and <bandwidth> supported by the sender of the offer. <bwtype> and <bandwidth> are defined in RFC 4566 [39] for the SDP b-line.
<tra-SCTP-association> provides the number <SCTP-association-number> of an SCTP association a media line relates to. If optimized media are selected, the media related to a media line with an "a= tra-SCTP-association" SDP attribute will be transported in that SCTP association, possibly together with media relating to other media lines with a= tra-SCTP-association" SDP attributes with the same <SCTP-association-number>. For a WIC terminating call, the eP-CSCF receiving an offer from the core network containg m-lines with "a= tra-SCTP-association" SDP attributes with the same <SCTP-association-number> will construct a single m-line related to that SCTP association in the offer towards the served WIC.
<tra-media-line-number> provides the total number <m-line-number> of media lines in the SDP, excluding any media lines with port zero.
The "tra-contact", "tra- att", "tra-bw", SDP attributes are session and media-level attributes.
The "tra-m-line" and "tra-SCTPassociation" SDP attributes are media level attributes.
The "tra-media-line-number" SDP attribute is a session level attribute.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4 IANA registration
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4.1 tra-contact
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: tra-contact
Long Form: tra-contact
Type of Attribute: session and media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks supporting WebRTC-IMS interworking. This attribute is used to encapsulate contact information received from gateways in the SDP offers and SDP answers when setting up a session that supports media plane optimization feature as specified in 3GPP TS 23.228 and 3GPP TS 24.371.
Appropriate Values: See table 7.5.4.3-1.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4.2 tra-m-line
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: tra-m-line
Long Form: tra-m-line
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks supporting WebRTC-IMS interworking. This attribute is used to encapsulate an m-line received in an SDP offer or SDP answer into an attribute in an outgoing SDP offer or SDP answer when setting up a session that supports media plane optimization feature as specified in 3GPP TS 23.228 and 3GPP TS 24.371.
Appropriate Values: See table 7.5.4.3-1.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4.3 tra-att
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: tra-att
Long Form: tra-att
Type of Attribute: session and media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks supporting WebRTC-IMS interworking. This attribute is used to encapsulate an attribute received in an SDP offer or SDP answer into an attribute in an outgoing SDP offer or SDP answer when setting up a session that supports media plane optimization feature as specified in 3GPP TS 23.228 and 3GPP TS 24.371.
Appropriate Values: See table 7.5.4.3-1.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4.4 tra-bw
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: tra-bw
Long Form: tra-bw
Type of Attribute: session and media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks supporting WebRTC-IMS interworking. This attribute is used to encapsulate bandwidth information received in the SDP offers and SDP answers when setting up a session that supports media plane optimization feature as specified in 3GPP TS 23.228 and 3GPP TS 24.371.
Appropriate Values: See table 7.5.4.3-1.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4.5 tra-SCTP-association
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: tra-SCTP-association
Long Form: tra-SCTP-association
Type of Attribute: media level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks supporting WebRTC-IMS interworking. This attribute is used to indicate that a media line relates to an SCTP association received in the SDP offers and SDP answers when setting up a session that supports media plane optimization feature as specified in 3GPP TS 23.228 and 3GPP TS 24.371.
Appropriate Values: See table 7.5.4.3-1.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.4.4.6 tra- media-line-number
|
Contact Name: 3GPP Specifications Manager, 3gppContact@etsi.org, +33 (0)492944200
Attribute Name: tra-media-line-number
Long Form: tra-media-line-number
Type of Attribute: session level
Charset Considerations: The attribute is not subject to the charset attribute.
Purpose: This attribute is used in networks supporting WebRTC-IMS interworking. This attribute is used to encapsulate the total number of media lines in the SDP, excluding any media lines with port zero, to detect a removal or dissabling of media lines by intermediate nodes when setting up a session that supports media plane optimization feature as specified in 3GPP TS 23.228 and 3GPP TS 24.371.
Appropriate Values: See table 7.5.4.3-1.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.5 Void
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.6 SDP content attribute values
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.6.1 General
|
As defined in RFC 4796 [206], the "a=content" attribute is a media level attribute in SDP.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.6.2 SDP "a=content" attribute "g.3gpp.announcement-no-confirmation" value
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.6.2.1 General
|
The SDP "a=content" attribute "g.3gpp.announcement-no-confirmation" value is used only for informative purposes during an established session, to indicate an SDP media description is for the video announcement service and the operator wishes to play the announcement stream without user confirmation.
The AS may use this value, based on the operator policy, only for the video announcement which is important or needs to be seen by the user immediately.
The UE may accept to play the video announcement without user confirmation when received this value, based on UE's local policy (e.g., local configuration on the UE).
The use of the SDP "a=content" attribute "g.3gpp.announcement-no-confirmation" value shall conform to the procedure specified in 3GPP TS 24.628 [8ZF].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.5.6.2.2 IANA registration for values of "a=content" attribute
|
IANA registration table: "content SDP Parameters" table of "Session Description Protocol (SDP) Parameters" registry.
IANA registry: A new value "g.3gpp.announcement-no-confirmation" for the SDP a=content media-level attribute defined in RFC 4796 [206].
Reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6 3GPP IM CN subsystem XML body
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.1 General
|
This subclause contains the 3GPP IM CN Subsystem XML body in XML format. The 3GPP IM CN Subsystem XML shall be valid against the 3GPP IM CN Subsystem XML schema defined in table 7.6.1.
Any SIP User Agent or proxy may insert or remove the 3GPP IM CN subsystem XML body or parts of it, as required, in any SIP message. The 3GPP IM CN subsystem XML body shall not be forwarded outside a 3GPP network.
See subclause 7.6.4 and subclause 7.6.5 for the associated MIME type definition.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.2 Document Type Definition
|
The XML Schema, is defined in table 7.6.1.
Table 7.6.1: IM CN subsystem XML body, XML Schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1">
<xs:complexType name="tIMS3GPP">
<xs:sequence>
<xs:choice>
<xs:element name="alternative-service" type="tAlternativeService"/>
<xs:element name="service-info" type="xs:string"/>
</xs:choice>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="version" type="xs:decimal" use="required"/>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="tAlternativeService">
<xs:sequence>
<xs:element ref="type"/>
<xs:element name="reason" type="xs:string"/>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<!-- root element -->
<xs:element name="ims-3gpp" type="tIMS3GPP"/>
<xs:element name="type" type="xs:string"/>
<!-- action element for //ims-3gpp//alternative-service -->
<xs:element name="action" type="xs:string"/>
</xs:schema>
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.3 XML Schema description
|
This subclause describes the elements of the IM CN subsystem XML Schema as defined in table 7.6.1.
<ims-3gpp>: The <ims-3gpp> element is the root element of the IM CN subsystem XML body. It is always present. XML instance documents of future versions of the XML Schema in table 7.6.1 is valid against the XML Schema in table 7.6.1 in this document. XML instance documents of the XML Schema in table 7.6.1 in the present document have a version attribute value, part of the <ims-3gpp> element, that is equal to the value of the XML Schema version described in the present document.
<service-info>: the transparent element received from the HSS for a particular trigger point are placed within this optional element.
<alternative-service>: in the present document, the alternative service is used as a response for an attempt to establish an emergency session within the IM CN subsystem or as a response to initiate S-CSCF restoration procedures. The element describes an alternative service where the call should success. The alternative service is described by the type of service information. A possible reason cause why an alternative service is suggested may be included.
In the present document, the <alternative-service> element contains a <type> element, a <reason> element, and an optional <action> element.
The <type> element indicates the type of alternative service. The <type> element contains only the values specified in table 7.6.2 in the present document.
Table 7.6.2: ABNF syntax of values of the <type> element
emergency-value = %x65.6D.65.72.67.65.6E.63.79 ; "emergency"
restoration-value = %x72.65.73.74.6F.72.61.74.69.6F.6E ; "restoration"
The <action> element contains only the values specified in table 7.6.3 in the present document.
Table 7.6.3: ABNF syntax of values of the <action> element
emergency-registration-value = %x65.6D.65.72.67.65.6E.63.79.2D.72.65.67.69.73.74.72.61.74.69.6F.6E ; "emergency-registration"
initial-registration-value = %x69.6E.69.74.69.61.6C.2D.72.65.67.69.73.74.72.61.74.69.6F.6E ; "initial-registration"
anonymous-emergencycall-value = %x61.6E.6F.6E.79.6D.6F.75.73.2D.65.6D.65.72.67.65.6E.63.79.63.61.6C.6C ; "anonymous-emergencycall"
The <reason> element contains an explanatory text with the reason why the session setup has been redirected. A UE may use this information to give an indication to the user.
If included in the IM CN subsystem XML body:
1. the <type> element with the value "emergency" is included as the first child element of the <alternative-service> element;
2. the <type> element with the value "restoration" is included as one of the following:
a) the first child element of the <alternative-service> element; or
b) the third or later child element of the <alternative-service> element;
3. the <action> element with the value "emergency-registration" is includes as the third child element of the <alternative-service> element;
4. the <action> element with value "initial-registration" is included as the third or later child element of the <alternative-service> element; and
5. the <action> element with value "anonymous-emergencycall" is included as the third or later child element of the <alternative-service> element.
NOTE: When included, the <action> and the second occurence of the <type> elements are validated by the <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of their parent elements.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.4 MIME type definition
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.4.1 Introduction
|
This subclause defines the MIME type for "application/3gpp-ims+xml". A 3GPP IM CN subsystem XML Document can be identified with this media type.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.4.2 Syntax
|
The following optional parameters are defined:
- "charset": the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [132].
- "sv" or "schemaversion": the syntax for the "sv" or "schemaversion" parameter is specified in table 7.6.4:
Table 7.6.4: Syntax of the "sv" or "schemaversion" parameter
m-parameter =/ ("sv" / "schemaversion") EQUAL LDQUOT [ sv-value-list ] RDQUOT
sv-value-list = sv-value-range *( "," sv-value )
sv-value-range = sv-value [ "-" sv-value ]
sv-value = number / token
number = 1*DIGIT [ "." 1*DIGIT ]
The BNF for m-parameter is taken from RFC 3261 [26] and modified accordingly.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.4.3 Operation
|
The encoding considerations for "application/3gpp-ims+xml" are identical to those of "application/xml" as described in RFC 3023 [132].
The "sv" or "schemaversion" parameter's value is used to indicate:
- the versions of the 3GPP IM CN Subsystem XML schema that can be used to validate the 3GPP IM CN subsystem XML body (if the MIME type and parameter are present in the Content-Type header field); or
- the accepted versions of the 3GPP IM CN Subsystem XML body (if the MIME type and parameter are present in the Accept header field).
If the "sv" and "schemaversion" parameter are absent, it shall be assumed that version 1 of the XML Schema for the IM CN subsystem XML body is supported.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.6.5 IANA Registration
|
NOTE: RFC 4288 [161], subclause 9, states the process that applies in case of changes to the registry of media types. Any future changes to the format or to subclause 7.6.5 would invoke this procedure.
MIME media type name:
application
MIME subtype name:
3gpp-ims+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [132].
"sv" or "schemaversion" the parameter's value is used to indicate:
- the versions of the 3GPP IP Multimedia (IM) Core Network (CN) subsystem XML schema that can be used to validate the 3GPP IM CN subsystem XML body (if the MIME type and parameter are present in the Content-Type header field); or
- the accepted versions of the 3GPP IM CN Subsystem XML body (if the MIME type and parameter are present in the Accept header field).
If the "sv" and "schemaversion" parameter are absent, it shall be assumed that version 1 of the XML Schema for the IM CN subsystem XML body is supported.
Encoding considerations:
Same as encoding considerations of application/xml as specified in RFC 3023 [132]
Security considerations:
Same as general security considerations for application/xml as specified in subclause 10 of RFC 3023 [132].
In addition, this content type provides a format for exchanging information in SIP, so the security considerations from RFC 3261 [26] apply.
Interoperability considerations:
Same as Interoperability considerations as specified in subclause 3.1 of RFC 3023 [132].
If both "sv" and "schemaversion" are specified, then the value of "schemaversion" is ignored
Published specification:
3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), stage 3", as published in subclause 7.6.5, version 8.9.0.
Available via <http://www.3gpp.org/specs/numbering.htm>.
Applications which use this media:
Applications that use the 3GPP IM CN Subsystem as defined by 3GPP.
Intended usage:
COMMON
Additional information:
1. Magic number(s): none
2. File extension(s): none
3. Macintosh file type code: none
4. Object Identifiers: none
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.7 SIP timers
|
The timers T1, T2, T4 A, B, C, D, E, F, G, H and I (defined in RFC 3261 [26]), timers L and M (defined in RFC 6026 [163]), and timer N (defined in RFC 6665 [28]) need modification in some cases to accommodate the delays introduced by the air interface processing and transmission delays. Table 7.7.1 shows recommended values for IM CN subsystem.
Table 7.7.1 lists in the first column, titled "SIP Timer" the timer names as defined in RFC 3261 [26] and RFC 6026 [163].
The second column, titled "value to be applied between IM CN subsystem elements" lists the values recommended for network elements e.g. P-CSCF, S-CSCF, MGCF, when communicating with each other i.e. when no air interface leg is included. These values are identical to those recommended by RFC 3261 [26], RFC 6026 [163], and RFC 6665 [28].
The third column, titled "value to be applied at the UE" lists the values recommended for the UE, when in normal operation the UE generates requests or responses containing a P-Access-Network-Info header field which included a value of "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "3GPP-E-UTRAN-FDD", "3GPP-E-UTRAN-TDD", "3GPP-E-UTRAN-ProSe-UNR", "3GPP-NR-FDD", "3GPP-NR-TDD", "3GPP-NR-U-FDD", "3GPP-NR-U-TDD", "3GPP-NR-SAT", "3GPP-NR(LEO)", "3GPP-NR(MEO)", "3GPP-NR(GEO)", "3GPP-NR(OTHERSAT)", "3GPP-WB-E-UTRAN(LEO)", "3GPP-WB-E-UTRAN(MEO), "3GPP-WB-E-UTRAN(GEO)", "3GPP-WB-E-UTRAN(OTHERSAT)", "3GPP-NB-IoT(LEO)", "3GPP-NB-IoT(MEO)", "3GPP-NB-IoT(GEO)", "3GPP-NB-IoT(OTHERSAT)", "3GPP-LTE-M(LEO)", "3GPP-LTE-M(MEO)", "3GPP-LTE-M(GEO)", "3GPP-LTE-M(OTHERSAT)", "3GPP-NR-ProSe-L2UNR", "3GPP-NR-ProSe-L3UNR", "3GPP‑NR‑REDCAP", "3GPP2-1X", "3GPP2-1X-HRPD", "3GPP2-UMB", "IEEE-802.11", "IEEE-802.11a", "IEEE-802.11b", "IEEE-802.11g", "IEEE-802.11n", "IEEE-802.11ac", or "DVB-RCS2". These are modified when compared to RFC 3261 [26] and RFC 6026 [163] to accommodate the air interface delays. In all other cases, the UE should use the values specified in RFC 3261 [26] or RFC 6026 [163] as indicated in the second column of table 7.7.1.
The fourth column, titled "value to be applied at the P-CSCF toward a UE" lists the values recommended for the P-CSCF when an air interface leg is traversed, and which are used on all SIP transactions on a specific security association where the security association was established using a REGISTER request containing a P-Access-Network-Info header field provided by the UE which included a value of "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "3GPP-E-UTRAN-FDD", "3GPP-E-UTRAN-TDD", "3GPP-E-UTRAN-ProSe-UNR", "3GPP-NR-FDD", "3GPP-NR-TDD", "3GPP-NR-U-FDD", "3GPP-NR-U-TDD", "3GPP-NR-SAT", "3GPP-NR(LEO)", "3GPP-NR(MEO)", "3GPP-NR(GEO)", "3GPP-NR(OTHERSAT)", "3GPP-WB-E-UTRAN(LEO)", "3GPP-WB-E-UTRAN(MEO), "3GPP-WB-E-UTRAN(GEO)", "3GPP-WB-E-UTRAN(OTHERSAT)", "3GPP-NB-IoT(LEO)", "3GPP-NB-IoT(MEO)", "3GPP-NB-IoT(GEO)", "3GPP-NB-IoT(OTHERSAT)", "3GPP-LTE-M(LEO)", "3GPP-LTE-M(MEO)", "3GPP-LTE-M(GEO)", "3GPP-LTE-M(OTHERSAT)", "3GPP-NR-ProSe-L2UNR", "3GPP-NR-ProSe-L3UNR", "3GPP‑NR‑REDCAP", "3GPP2-1X", "3GPP2-1X-HRPD", "3GPP2-UMB", "IEEE-802.11", "IEEE-802.11a", "IEEE-802.11b", "IEEE-802.11g", "IEEE-802.11n", "IEEE-802.11ac", or "DVB-RCS2". These are modified when compared to RFC 3261 [26] and RFC 6026 [163]. In all other cases, the P-CSCF should use the values specified in RFC 3261 [26] and RFC 6026 [163] as indicated in the second column of table 7.7.1.
The final column reflects the timer meaning as defined in RFC 3261 [26], RFC 6026 [163] or RFC 6665 [28].
Table 7.7.1: SIP timers
SIP Timer
Value to be applied between IM CN subsystem elements
Value to be applied at the UE
Value to be applied at the P-CSCF toward a UE
Meaning
T1
500ms default
(see NOTE)
2s default
2s default
RTT estimate
T2
4s
(see NOTE)
16s
16s
The maximum retransmit interval for non-INVITE requests and INVITE responses
T4
5s
(see NOTE)
17s
17s
Maximum duration a message will remain in the network
Timer A
initially T1
initially T1
initially T1
INVITE request retransmit interval, for UDP only
Timer B
64*T1
64*T1
64*T1
INVITE transaction timeout timer
Timer C
> 3min
> 3 min
> 3 min
proxy INVITE transaction timeout
Timer D
> 32s for UDP
>128s
>128s
Wait time for response retransmits
0s for TCP/SCTP
0s for TCP/SCTP
0s for TCP/SCTP
Timer E
initially T1
initially T1
initially T1
non-INVITE request retransmit interval, UDP only
Timer F
64*T1
64*T1
64*T1
non-INVITE transaction timeout timer
Timer G
initially T1
initially T1
initially T1
INVITE response retransmit interval
Timer H
64*T1
64*T1
64*T1
Wait time for ACK receipt.
Timer I
T4 for UDP
T4 for UDP
T4 for UDP
Wait time for ACK retransmits
0s for TCP/SCTP
0s for TCP/SCTP
0s for TCP/SCTP
Timer J
64*T1 for UDP
64*T1 for UDP
64*T1 for UDP
Wait time for non-INVITE request retransmits
0s for TCP/SCTP
0s for TCP/SCTP
0s for TCP/SCTP
Timer K
T4 for UDP
T4 for UDP
T4 for UDP
Wait time for response retransmits
0s for TCP/SCTP
0s for TCP/SCTP
0s for TCP/SCTP
Timer L
64*T1
64*T1
64*T1
Wait time for accepted INVITE
request retransmits
Timer M
64*T1
64*T1
64*T1
Wait time for retransmission of 2xx to INVITE or additional 2xx from other branches of a forked INVITE
Timer N
64*T1
64*T1
64*T1
Wait time for receipt of a NOTIFY request upon sending SUBSCRIBE
NOTE: As a network option, SIP T1 Timer's value can be extended, along with the necessary modifications of T2 and T4 Timers' values, to take into account the specificities of the supported services when the MRFC and the controlling AS are under the control of the same operator and the controlling AS knows, based on local configuration, that the MRFC implements a longer value of SIP T1 Timer.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.8 IM CN subsystem timers
|
Table 7.8.1 shows recommended values for timers specific to the IM CN subsystem.
Table 7.8.1: IM CN subsystem
Timer
Value to be applied at the UE
Value to be applied at the P-CSCF
Value to be applied at the S-CSCF
Meaning
reg-await-auth
not applicable
not applicable
4 minutes
The timer is used by the S-CSCF during the authentication procedure of the UE for registration. For detailed usage of the timer see subclause 5.4.1.2.
The authentication procedure may take in the worst case as long as 2 times Timer F. The IM CN subsystem value for Timer F is 128 seconds.
request-await-auth
not applicable
not applicable
4 minutes
The timer is used by the S-CSCF during the authentication procedure of the UE for requests different than REGISTER. For detailed usage of the timer see subclause 5.4.3.6.1.
The authentication procedure may take in the worst case as long as 2 times Timer F. The IM CN subsystem value for Timer F is 128 seconds.
emerg-reg
Configurable value between 8 seconds and 20 seconds
not applicable
not applicable
The timer is used by the UE to supervise the time from deciding that an emergency service is to be established via the IM CN subsystem until completion of the emergency registration procedure, including any required IP-CAN procedures. For detailed usage of the timer see subclause 5.1.6.1.
emerg-reg-retry
Configurable value between 3 seconds and 5 seconds
not applicable
not applicable
The timer is used by the UE to supervise the time from deciding that an emergency registration is to be attempted on a particular P-CSCF until success/failure of emergency procedure on that specific P-CSCF, including any required IP-CAN procedures. The detailed usage of the timer described in subclause 5.1.6.1 and the final value to be applied at UE for this timer is determined.
(see NOTE)
emerg-request
Configurable value between 5 seconds and 15 seconds
not applicable
not applicable
The timer is used by the UE during initial request for emergency service. For detailed usage of the timer see subclause 5.1.6.8.1.
NoVoPS-dereg
Configurable value between 0 seconds and 65535 seconds
not applicable
not applicable
The timer is used by the UE when the UE receives a VoPS not supported indication from the lower layers and indicates the time the UE needs to wait before the UE deregisters from IMS if the UE is configured with a policy to deregister, see subclause B.3.1.0a, L.3.1.0a, U.3.1.0a and W.3.1.0a
emerg-non3gpp
Configurable value between 5 seconds and 20 seconds
not applicable
not applicable
The timer is used by the UE to supervise the time for searching usable 3GPP access to setup an emergency call before attempting the emergency call via non-3GPP access.
For detailed usage of the timer see subclauses R.2.2.6.1 and W.2.2.6.1.
NOTE: The emerg-reg-retry timer value defines a minimum waiting time in seconds for the UE for a particular P-CSCF. The final value to be applied at UE for this timer is determined as described below using configured emerg-reg-retry timer value, emerg-reg timer value and number of P-CSCFs determined during session management procedures:
Final emerg-reg-retry timer value = Max (configured emerg-reg-retry timer value, configured emerg-reg timer value/number of P-CSCFs)
NOTE: The UE and the P-CSCF use the value of the reg-await-auth timer to set the SIP level lifetime of the temporary set of security associations.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.9 Media feature tags defined within the current document
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.9.1 General
|
This subclause describes the media feature tag definitions that are applicable for the 3GPP IM CN subsystem.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
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].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
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].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.9.4 Void
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.9.5 Void
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.9.6 Void
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
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].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
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].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
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
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].
7.9A Feature-capability indicators defined within the current document
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 ">"
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 URI of the media resource broker.
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 IETF RFC 6809 [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">"
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 using a token to identify the registration used for the current request or response.
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
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.
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 support of calling party number verification functionality.
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.
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 support of ANBR.
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].
7.9A.13 Definition of feature-capability indicator g.3gpp.in-call-access-update
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.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10 Reg-event package extensions defined within the current document
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.1 General
|
This subclause describes the reg-event package extensions that are applicable for the IM CN subsystem.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.2 Reg-Event package extension to transport wildcarded public user identities
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.2.1 Structure and data semantics
|
This subclause defines an extension to the event registration package (RFC 3680 [43]) to transport policy to transport wildcarded public user identities that are encoded using regular expression.
In order to include a wildcared public user identity in the event registration package, the notifier shall
1. if the registration set of the identity whose registration status is notified contains a wildcarded public user identity, add a <wildcardedIdentity> sub-element defined in subclause 7.10.2.2 of this document to the <registration> element of the wildcarded identiy;
2. for the <registration> element containing a <wildcardedIdentity> sub-element:
a) set the aor attribute to any public user identity that is represented by the wildcarded identity; and
b) set the <wildcardedIdentity> sub-element inside of the <registration> element to the wildcarded identity as received via the Cx interface.
NOTE: The public user identity that is put into the aor attribute does not have any extra privileges over any other public user identity that is represented by a wildcarded public user identity.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.2.2 XML Schema
|
Table 7.10.1 in this subclause defines the XML Schema describing the extension to transport wildcarded public user identities which can be included in the reg event package sent from the S-CSCF in NOTIFY requests.
Table 7.10.1: Wildcarded Identity, XML Schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:extRegExp:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="wildcardedIdentity" type="xs:string"/>
</xs:schema>
NOTE: Multiple wildcarded elements can be included in one registration element.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.3 Reg-event package extension for policy transport
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.3.1 Scope
|
This subclause describes coding which extends the registration event package defined in RFC 3680 [43] to transport policy associated with a public user identity.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.3.2 Structure and data semantics
|
The policy associated with a public user identity shall be encoded as follows:
1. add an <actions> element defined in the RFC 4745 [182] in the <registration> element of the public user identity in the registration information;
NOTE: The <actions> element is validated by the <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of the <registration> elements.
2. if the policy to the usage of the communication resource priority (see RFC 4412 [116]) is associated with the public user identity, then for each allowed usage:
a. include an <rph> child element in the <actions> child element of the <registration> element;
b. set the 'ns' attribute of the <rph> child element of the <actions> child element of the <registration> element to the allowed resource priority namespace as specified in RFC 4412 [116] and as registered in IANA; and
c. set the 'val' attribute of the <rph> child element of the <actions> child element of the <registration> element to the allowed resource priority value within the allowed resource priority namespace;
3. if the policy to act as privileged sender (the P-CSCF passes identities for all calls) is associated with the public user identity, then include a <privSender> child element in the <actions> child element of the <registration> element;
4. if the policy for special treatment of the P-Private-Network-Indication header field (the P-CSCF allows the UE to make private calls) is associated with the public user identity, then include a <pni> child element in the <actions> child element of the <registration> element, and shall:
a. if a P-Private-Network-Indication header field shall be forwarded, if received from the attached equipment, set the "insert" attribute of the <pni> element to a "fwd" value;
b. if a P-Private-Network-Indication header field shall be inserted in all requests received from the attached equipment, insert an "insert" attribute of the <pni> element to a "ins" value; and
c. if the value of the "insert" attribute is "ins", insert a "domain" attribute with the value of the URI to be set in the P-Private-Network-Indication header field;
5. if the policy to act as privileged sender for the calls with the P-Private-Network-Indication header field (the P-CSCF allows the UE to make private calls, and the P-CSCF passes identities only for private calls) is associated with the public user identity, then include a <privSenderPNI> child element in the <actions> child element of the <registration> element; and
NOTE: If only the <privSender> child element is sent and no <privSenderPNI> child element is sent, then the <privSender> child element applies to both public network traffic and private network traffic (i.e. that with special treatment of the P-Private-Network-Indication header field).
6. if priority is supported and if the MPS for Messaging indicator from the UDM/HSS associated with the public user identity is "active", then include a <messagingPriority> child element in the <actions> child element of the <registration> element.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.10.3.3 XML Schema
|
Table 7.10.2 in this subclause defines the XML Schema describing the individual policies which can be delivered to the P-CSCF or UE using the reg event package extension for policy transport.
Table 7.10.2: Reg event package extension for policy transport, XML Schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:extRegInfo:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="rph">
<xs:complexType>
<xs:attribute name="ns" type="xs:string"/>
<xs:attribute name="val" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="privSender">
<xs:complexType/>
</xs:element>
<xs:element name="pni">
<xs:complexType>
<xs:attribute name="insert">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="fwd"/>
<xs:enumeration value="ins"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="domain" type="xs:anyURI"/>
</xs:complexType>
</xs:element>
<xs:element name="privSenderPNI">
<xs:complexType/>
</xs:element>
<xs:element name="messagingPriority">
<xs:complexType/>
</xs:element>
</xs:schema>
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11 URNs defined within the present document
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.1 Country specific emergency service URN
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.1.1 Introduction
|
The country specific emergency service URN is intended to uniquely identify a type of emergency service for which an emergency service URN, i.e. a service URN with a top-level service type of "sos" as specified in RFC 5031 [69], registered by IANA is not available.
The country specific emergency service URN is intended to be used only when an emergency service URN for a given type of emergency service, with approximately the same caller expectation in terms of services rendered, is not registered by IANA.
The country specific emergency service URN is intended to be used only inside the country where the national regulatory authority defines emergency services only by national numbers. The country specific emergency service URN is not intended to be used by the UE except when indicated by the network.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.1.2 Syntax
|
The country specific emergency service URN is a service URN with:
1) the top-level service type of "sos" as specified in RFC 5031 [69];
2) the first sub-service of "country-specific";
3) the second sub-service indicating the country where the type of emergency service is deployed. The format of second sub-service is an ISO 3166-1 alpha-2 code as specified in ISO 3166-1 [207]; and
4) the third sub-service uniquely identifying the type of emergency service in the country where the type of emergency service is deployed. The third sub-service is defined by the national regulation of the country where the type of emergency service is deployed. The set of allowable characters for the third sub-service is the same as that for domain names (see RFC 5031 [69]) and the number of characters for the third sub-service shall be less than 64.
EXAMPLE: urn:service:sos.country-specific.xy.567 can identify a type of emergency service identified by an emergency number 567 in a country identified by "xy" ISO 3166-1 alpha-2 code as specified in ISO 3166-1 [207].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.1.3 Operation
|
Unless explicitly prohibited, wherever an emergency service URN i.e. a service URN with the top-level service type of "sos" as specified in RFC 5031 [69] can be used, the country specific emergency service URN can also be used.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.1.4 Void
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2 ICSI value for RLOS
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.1 Introduction
|
This subclause describes the IMS communications service identifier definitions that is applicable for the usage of restricted local operator service (RLOS).
NOTE: The template has been created using the headers of the table in http://www.3gpp.org/specifications-groups/34-uniform-resource-name-urn-list
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.2 URN
|
urn:urn-7:3gpp-service.ims.icsi.rlos
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.3 Description
|
This URN indicates that the device has the capabilities to support the restricted local operator service (RLOS).
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.4 Reference
|
3GPP TS 24 229: " IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3"
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.5 Contact
|
Name: <MCC name>
Email: <MCC email address>
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.6 Registration of subtype
|
Yes
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.11.2.7 Remarks
|
None
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12 Info package definitions and associated MIME type definitions
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1 DTMF info package and session-info MIME type
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1 DTMF info package
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.1 General
|
This subclause contains the information required for the IANA registration of an info package.
The digit message body and associated MIME type can also be used as defined in other specifications in a legacy manner as defined by RFC 6086 [25].
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.2 Overall description
|
DTMF tones are normally sent when a user presses a button on the terminal. Each tone, identified by a unique frequency, represents a number (0-9) or a special character. The DTMF info package is used to transport that value. In-order delivery of the DTMF digits is not controlled by the DTMF info package, this would be controlled either by queuing in the sender or by separate interaction with the human user; such mechanisms are out of scope of this registration.
The DTMF info package can be used to transport a single DTMF tone, or a series of tones. If a series of tones is transported in a single SIP INFO request, it is not possible to indicate the duration between each tone in the series.
The DTMF info package is not defined for a specific application. Any application, where sending of DTMF tones using the SIP INFO method is required, can used the DTMF info package.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.3 Applicability
|
The info package mechanism for transporting DTMF tones has been chosen because it allows SIP entities that do not have access to the user plane (where DTMF tones can also be transported) to send and receive tones. The mechanism also allows the tones to be sent inside an existing dialog, using the same signalling path as other SIP messages within the dialog, rather than having to establish a separate dialog (DTMF tones can also be transported using subscription event packages).
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.4 Info package name
|
The name of the DTMF info package is: infoDtmf
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.5 Info package parameters
|
No parameters are defined for the DTMF info package.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.6 SIP option tags
|
No SIP option tags are defined for the DTMF info package.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.7 INFO message body parts
|
The DTMF digits are carried in the Overlap digit message body, defined in subclause 7.12.1.2.
The MIME type value for the message body is "application/session-info", defined in subclause 7.12.1.2.
The Content Disposition value for the message body, when associated with the DTMF info package, is "info-package" (see RFC 6086 [25]).
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.8 Info package usage restrictions
|
No usage restrictions are defined for the DTMF info package.
If SIP entities support multiple mechanisms for sending DTMF tones they need to ensure, using negotiation mechanisms, that each entity is aware of which mechanism is used.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.9 Rate of INFO requests
|
No maximum rate or minimum rate is defined for sending INFO requests associated with the DTMF info package.
When DTMF tones are triggered by user interaction, the DTMF tones are normally generated when the user pushes a button. Specific applications can decide upon which rate DTMF tones are generated. However, the DTMF info package does not provide a feedback mechanism to indicate to the sender that the rate of DTMF tones is too slow or fast.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.1.10 Info package security considerations
|
No additional security mechanism is defined for the DTMF info package.
The security of the DTMF info package is based on the generic security mechanism provided for the underlying SIP signalling.
The mechanism should not be used for transferring any data that requires a greater level of security than the underlying SIP signalling.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.2 Overlap digit message body
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.2.1 Scope
|
This section defines a message body that shall be used for sending additional digits, which have not previously been sent, in SIP INFO messages ("legacy" mode of usage of the INFO method as defined in RFC 6086 [25]) when the in-dialog method is used for overlap dialling.
The same message body can also be used for transporting Dual Tone Multi Frequency (DTMF) tones using SIP INFO requests, using the DTMF info package (see RFC 6086 [25]) defined in subclause 7.12.1.1.
The support of this message body is a network option.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.2.2 MIME type
|
The message body defined in the present annex is registered at IANA as "application/session-info" MIME type.
If the message body is embedded in SIP INFO messages, the Content-Type header shall be set to "application/session-info" and the Content-Disposition header shall be set to "signal" with the handling parameter set to "optional".
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.2.3 ABNF
|
session-info = SubsequentDigit
SubsequentDigit = "SubsequentDigit" HCOLON phonedigits
phonedigits = 1*(HEXDIG / "*" / "#")
HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.2.4 IANA registration template
|
Within the present subclause, information required for an IANA registration at http://www.iana.org/cgi-bin/mediatypes.pl is provided.
1. Media Type Name
Application
2. Subtype name
"session-info" (Standards Tree)
3. Required parameters
none
4. Optional parameters
none
5. Encoding considerations
binary
6. Security considerations
Modifications of the MIME body by a man-in-the-middle can have severe consequences:
The overlap digits that can be transported with this MIME body influence the routeing of the SIP session that is being setup.
Dual Tone Multi Frequency (DTMF) tones that can also be transported with this MIME body will be interpreted by the application of the end points of the communication for various purposes.
However, this MIME body is used only attached to SIP INFO messages, and modifications of other parts of the SIP signalling will lead to comparable consequences. Protection of the SIP signalling will also protect the present MIME body.
The information transported in this MIME media type does not include active or executable content.
Mechanisms for privacy and intregrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
7. Interoperability considerations
none
8. Published specification
3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), stage 3".
9. Applications which use this media type
This MIME type is used as a message body within SIP INFO messages.
It is either used for sending additional digits of the callee´s number, which have not previously been sent, in SIP INFO messages ("legacy" mode of usage of the INFO method as defined in IETF RFC 6086) when the in-dialog method is used for overlap dialling.
The same message body can also be used for transporting Dual Tone Multi Frequency (DTMF) tones using SIP INFO requests, using the DTMF info package (see RFC 6086) defined in subclause 7.12.1.1.
10. Additional information
Magic number(s): none
File extension(s): none
Macintosh File Type Code(s): none
Object Identifier(s) or OID(s): none
11. Intended usage
Limited Use
12. Other Information/General Comment
none.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.1.3 Implementation details and examples
|
Examples of the DTMF info package usage can be found in the following specification:
- 3GPP TS 24.182 [8Q]: "Customized Alerting Tones; Protocol specification".
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2 g.3gpp.current-location-discovery info package and request-for-current-location body
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2.1 g.3gpp.current-location-discovery info package
| |
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2.1.1 General
|
This subclause contains information required for registration of the g.3gpp.current-location-discovery info package with IANA.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2.1.2 Overall description
|
Location of a UA participating in an INVITE-initiated dialog can change during duration of the INVITE-initiated dialog.
The g.3gpp.current-location-discovery info package enables a UA participanting in an INVITE-initiated dialog to indicate a request for location information to the other UA participating in the INVITE-initiated dialog.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2.1.3 Applicability
|
A number of solutions for the transportation of the pieces of information identified in the overall description were identified and considered:
1) Use of session related methods for transporting event and state information, e.g. re-INVITE request, UPDATE request.
2) Use of OPTIONS request.
3) Use of SIP MESSAGE method.
4) Use of media plane mechanisms.
5) Use of subscription to the presence event package as described in RFC 3856 [74].
6) Use of SIP INFO method as decribed in RFC 6086 [25], by defining a new info package.
Furthermore, each of the solutions was evaluated.
Use of session related methods was discounted since purpose of the INVITE request and the UPDATE request was to modify the dialog, or the parameters of the session or both and neither the dialog nor the parameters of the session needed to be modified.
Use of the OPTIONS request was discounted since purpose of the OPTIONS request was to query UAS for UAS' capabilites rather than requesting an information available at the UAS.
Use of the MESSAGE request was discounted since the use of the INFO method enabled negotiation of supported event packages in the INVITE transaction while the use of the MESSAGE method did not.
Use of the media plane mechanisms was discounted since the amount of information transferred between the UAs was limited and set up of media stream generated generate extra messages.
Use of the presence event package was discounted since the dialog reuse technique was deprecated accoding to RFC 6665 [28]. Thus, SUBSCRIBE request for the presence event package needed to be sent using a dialog other than any dialog established as result of a INVITE request. However, in some situation - e.g. an emergency session initiated by a UA without a prior registration, there was no way how to ensure delivery of a new initial request for a dialog to the UA. The remote target indicated in Contact header field of:
- the INVITE request; or
- the received response to the INVITE request;
sent by the UA was not necessarily globally routable (e.g. when the UA was behind NAT or when the UA was behind a SIP proxy with a firewall), and the route set indicated in the Record-Route header fields of:
- the INVITE request; or
- the received response to the INVITE request;
sent by the UA might be dedicated to the messages of dialogs established as result of the INVITE request.
Based on the above analyses, the SIP INFO method was chosen.
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2.1.4 Info package name
|
Info package name is: g.3gpp.current-location-discovery
|
d3a3ac3f64ab68e4fcef5ea9a665f70a
|
24.229
|
7.12.2.1.5 Info package parameters
|
No info package parameters are defined for the g.3gpp.current-location-discovery info package.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.