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 Optimal Media Routeing (OMR) attributes | |
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 med... |
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 R... |
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 allow... |
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 ... |
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... |
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... |
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 t... |
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 ... |
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 ... |
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 by... |
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 by... |
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 tha... |
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" ":" m... |
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... |
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.... |
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 interwo... |
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 interwork... |
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 WebR... |
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 ... |
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... |
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... |
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... |
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:cho... |
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 t... |
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 ... |
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 (... |
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:
"char... |
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 va... |
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 ... |
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) val... |
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) val... |
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 ... |
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, w... |
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: B... |
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 registr... |
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
targetName... |
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=... |
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
tar... |
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... |
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... |
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 ... |
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 a... |
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 ... |
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... |
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... |
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 trans... |
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 se... |
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 consi... |
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-... |
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.... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.1.4 Info package name | Info package name is: g.3gpp.current-location-discovery |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.