hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.1.6 SIP option tags | No SIP option tags are defined for the g.3gpp.current-location-discovery info package. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.1.7 INFO message body parts | The MIME type of the body is application/vnd.3gpp.current-location-discovery+xml. The application/vnd.3gpp.current-location-discovery+xml MIME type is defined in 3GPP TS 24.229.
When associated with the g.3gpp.current-location-discovery info package, the Content-Disposition value of the body is "info-package". |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.1.8 Info package usage restrictions | No usage restrictions are defined for the g.3gpp.current-location-discovery info package. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.1.9 Rate of INFO requests | No maximum rate or minimum rate is defined for sending INFO requests associated with the g.3gpp.current-location-discovery info package. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.1.10 Info package security considerations | The security of the g.3gpp.current-location-discovery info package is based on the generic security mechanism provided for the underlaying SIP signalling.
As the location information is a sensitive information, unless the location information is requested from a UA who initiated an emergency session, the UA requested to provide the location information needs to authorize the request with the user at the UA. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.2 Request-for-current-location body | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.2.1 General | The request-for-current-location body is of "application/vnd.3gpp.current-location-discovery+xml" MIME type.
The request-for-current-location body is an XML document compliant to the XML schema defined in subclause 7.12.2.2.2, compliant to the additional syntax rules in subclause 7.12.2.2.3, with semantic defined in subclause 7.12.2.2.4. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.2.2 XML schema | The XML Schema, is defined in table 7.12.2.2.2.1.
Table 7.12.2.2.2.1: XML schema of application/vnd.3gpp.current-location-discovery+xml MIME type
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:element name="requestForLocationInformation"
type="requestForLocationInformationType"/>
<xs:complexType name="requestForLocationInformationType">
<xs:sequence>
<xs:choice>
<xs:element name="oneShot" type="anyExtType"/>
<xs:element name="anyExt" type="anyExtType"/>
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
<xs:element name="anyExt" type="anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
</xs:schema> |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.2.3 Additional syntax rules | The <requestForLocationInformation> element is the root element.
The <requestForLocationInformation> root element contains:
1) one of the following elements:
a) the <oneShot> element;
b) the <anyExt> element;and
c) an element from another namespace for the purposes of extensibility;
2) zero or one <anyExt> element;and
3) zero or more elements from other namespaces for the purposes of extensibility; and
4) zero or more attributes from any namespaces for the purpose of extensibility.
The <oneShot> element contains:
1) zero or more elements from any namespaces for the purposes of extensibility; and
2) zero or more attributes from any namespaces for the purpose of extensibility.
The <anyExt> element contains:
1) zero or more elements from any namespaces for the purposes of extensibility; and
2) zero or more attributes from any namespaces for the purpose of extensibility. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.2.4 Semantic | The <oneShot> child element of the <requestForLocationInformation> root element indicates that the receiving entity is requested to send the location information once.
The <anyExt> element contains elements defined in future version of this specification.
The receiving entity ignores any unknown XML element and any unknown XML attribute. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.12.2.2.5 IANA registration | Your name:
<MCC name>
Your email address:
<MCC email>
Media type name:
application
Subtype name:
vnd.3gpp.current-location-discovery+xml
Required parameters:
none.
Optional parameters:
1) "charset" - the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303 [247].
Encoding considerations:
binary.
Security considerations:
same as general security considerations for application/xml media type as specified in section 9.1 of RFC 7303 [247]. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from RFC 3261 [26] apply.
The information transported in this MIME media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type includes provisions for directives that institute actions on a recipient's files or other resources. The action is providing the location information. The action is providing the location information of the entity receiving the body. Except when sent a part of an emergency session, the entity receiving the body needs to request the user at the entity to authorize the action.
This media type includes provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way. The action is providing the location information of the entity receiving the body. Except when sent a part of an emergency session, the entity receiving the body needs to request the user at the entity to authorize the action.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303 [247].
Published specification:
3GPP TS 24.229, (http://www.3gpp.org/ftp/Specs/html-info/24229.htm)
Applications which use this media type:
This MIME type is used for a MIME body within SIP INFO requests.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 [247] applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1) Deprecated alias names for this type: none
2) Magic number(s): none
3) File extension(s): none
4) Macintosh file type code(s): none
5) Object identifier(s) or OID(s): none
Intended usage:
Common.
Person to contact for further information
1) Name: <MCC>
2) Email: <MCC email>
3) Author/change controller:
i) Author: 3GPP CT1 Working Group/[email protected]
ii) Change controller: <MCC name>/<MCC email address> |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13 JSON Web Token claims defined within the present document | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.1 General | This subclause contains definitions for JSON Web Token claims RFC 7519 [235] usage in the 3GPP IM CN subsystem.
NOTE: The claim names are defined as private claim names, and do not require registration, as defined in RFC 7519 [235]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.2 3GPP-WAF | The 3gpp-waf claim is used to transport the identity of the WAF.
Claim name: 3gpp-waf
Claim value: String
Claim description: WAF identity |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.3 3GPP-WWSF | The 3gpp-wwsf claim is used to transport the identity of the WAF.
Claim name: 3gpp-wwsf
Claim value: String
Claim description: WWSF identity |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.4 identityHeader | The identityHeader claim is used to transport a SIP Identity header field.
Claim name: identityHeader
Claim value: String
Claim description: Contents of an Identity header field |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.5 verstatValue | The verstatValue claim is used to transport the value of a verstat tel URI parameter.
Claim name: verstatValue
Claim value: String
Claim description: The value of a verstat tel URI parameter. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.6 identityHeaders | The identityHeaders claim is used to transport one or more SIP Identity header field(s).
Claim name: identityHeaders
Claim value: Array of strings
Claim description: Array of Identity header fields needed to verify diverting users. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.7 divResult | The divResult claim is used to transport the result for the verified div claims and related identities.
Claim name: divResult
Claim value: Array of one or more [div, verstatValue] tuples
Claim description: The value of a verstat tel URI parameter. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.13.8 verstatPriority | The verstatPriority claim is used to transport the verification value of the Resource-Priority header field and optionally the header field value "psap-callback" of the Priority header field.
Claim name: verstatPriority
Claim value: String
Claim description: Indicates the result of the verification of the Resource-Priority header field and optionally the header field value "psap-callback" of the Priority header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.14 Dialog event package extensions defined within the present document | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.14.1 General | This subclause describes the dialog event package extensions that are applicable for the IM CN subsystem. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.14.2 Dialog event package extension to transport UE identity information | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.14.2.1 Structure and data semantics | This subclause defines an extension to the dialog event package (RFC 4235 [171]) to transport UE identity information for UEs belonging to the same subscription.
In order to include UE identity information in the dialog event package, the notifier shall
1. in the <dialog-info> element add one or more <ue-instance> elements defined in subclause 7.14.2.2 and 3GPP TS 24.174 [8ZH], each element containing:
a) an "identity" attribute set to an identifier of the UE as specified in 3GPP TS 24.174 [8ZH]; and
b) an "alias" attribute set to a user friendly name of the UE as specified in 3GPP TS 24.174 [8ZH]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.14.2.2 XML Schema | Table 7.14.1 in this subclause defines the XML Schema describing the extension to include UE identity information which can be included in the dialog event package sent from the TAS in NOTIFY requests.
Table 7.14.1: UE identity information, XML Schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:extDEN:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ss="http://uri.etsi.org/ngn/params/xml/simservs/xcap"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="XCAP.xsd"/>
<ss:ue-instance/>
</xs:schema> |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8 SIP compression | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.1 SIP compression procedures at the UE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.1.1 SIP compression | If 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", then the UE shall support:
- SigComp as specified in RFC 3320 [32] and as updated by RFC 4896 [118]; and
- the additional requirements specified in RFC 5049 [79], with the exception that the UE shall take a State Memory Size of at least 4096 bytes as a minimum value.
If 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", then the UE may support:
- the negative acknowledgement mechanism specified in RFC 4077 [65A].
When using SigComp the UE shall send compressed SIP messages in accordance with RFC 3486 [55]. When the UE will create the compartment is implementation specific, but the compartment shall not be created until a set of security associations or a TLS session is set up if signalling security is in use. The UE shall finish the compartment when the UE is deregistered. The UE shall alow state creations and announcements only for messages received in a security association.
NOTE: Exchange of bytecodes during registration will prevent unnecessary delays during session setup.
If the UE supports SigComp:
- the UE shall support the SIP dictionary specified in RFC 3485 [42] and as updated by RFC 4896 [118]. If compression is enabled, the UE shall use the dictionary to compress the first message; and
- if the UE supports the presence user agent or watcher roles as specified in table A.3A/2 and table A.3A/4, the UE may support the presence specific dictionary specified in RFC 5112 [119].
The use of SigComp is not re-negotiated between initial registration and deregistration. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.1.2 Compression of SIP requests and responses transmitted to the P-CSCF | In normal operation the UE should send the generated requests and responses transmitted to the P-CSCF:
- compressed according to subclause 8.1.1, if the P-Access-Network-Info header field of the initial registration message includes a value of "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "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";
- uncompressed, if the P-Access-Network-Info header field of the initial registration message includes a value of "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-NR-ProSe-L2UNR", "3GPP-NR-ProSe-L3UNR", "3GPP‑NR‑REDCAP".
In other cases where SigComp is supported, the UE need not compress the requests and responses.
NOTE 1: Compression of SIP messages is an implementation option. However, compression is strongly recommended.
NOTE 2: In an IP-CAN where compression support is mandatory the UE can send even the first message compressed. Sigcomp provides mechanisms to allow the UE to know if state has been created in the P-CSCF or not. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.1.3 Decompression of SIP requests and responses received from the P-CSCF | If the UE supports SigComp, then the UE shall decompress the compressed requests and responses received from the P-CSCF according to subclause 8.1.1.
NOTE: According to RFC 3486 [55], the UE not supporting SigComp or not indicating willingness to receive compressed messages never receives compressed SIP messages.
If the UE detects a decompression failure at the P-CSCF, the recovery mechanism is implementation specific. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.2 SIP compression procedures at the P-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.2.1 SIP compression | The P-CSCF shall support:
- SigComp as specified in RFC 3320 [32] and as updated by RFC 4896 [118]; and
- the additional requirements specified in RFC 5049 [79], with the exception that the P-CSCF shall take a State Memory Size of at least 4096 bytes as a minimum value.
The P-CSCF may support:
- the negative acknowledgement mechanism specified in RFC 4077 [65A].
When using SigComp the P-CSCF shall send compressed SIP messages in accordance with RFC 3486 [55]. When the P-CSCF will create the compartment is implementation specific, but the compartment shall not be created until a set of security associations are set up. The P-CSCF shall finish the compartment when the UE is deregistered. The P-CSCF shall allow state creations and announcements only for messages received in a security association.
The P-CSCF:
- shall support the SIP dictionary specified in RFC 3485 [42] and as updated by RFC 4896 [118]. If compression is enabled, the P-CSCF shall use the dictionary to compress the first message; and
- may support the presence specific dictionary specified in RFC 5112 [119].
NOTE: Exchange of bytecodes during registration will prevent unnecessary delays during session setup. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.2.2 Compression of SIP requests and responses transmitted to the UE | For all SIP transactions on a specific security association where the security association was established using a REGISTER request from the UE containing a P-Access-Network-Info header field which included a value of "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-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-E-UTRAN-FDD", "3GPP-E-UTRAN-TDD", "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", and the UE has indicated that it supports SigComp and is willing to receive compressed messages in accordance with RFC 3486 [55], then the P-CSCF should compress the requests and responses transmitted to the UE according to subclause 8.2.1. In other cases where SigComp is supported, it need not.
NOTE: Compression of SIP messages is an implementation option. However, compression is strongly recommended. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 8.2.3 Decompression of SIP requests and responses received from the UE | The P-CSCF shall decompress the compressed requests and responses received from the UE according to subclause 8.2.1.
If the P-CSCF detects a decompression failure at the UE, the recovery mechanism is implementation specific. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 9 IP-Connectivity Access Network aspects when connected to the IM CN subsystem | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 9.1 Introduction | A UE accessing the IM CN subsystem and the IM CN subsystem itself utilises the services supported by the IP-CAN to provide packet-mode communication between the UE and the IM CN subsystem. General requirements for the UE on the use of these packet-mode services are specified in this clause.
Possible aspects particular to each IP-CAN is described separately for each IP-CAN. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 9.2 Procedures at the UE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 9.2.1 Connecting to the IP-CAN and P-CSCF discovery | Prior to communication with the IM CN subsystem, the UE shall:
a) establish a connection with the IP-CAN;
b) obtain an IP address using either the standard IETF protocols (e.g., DHCP or IPCP) or a protocol that is particular to the IP-CAN technology that the UE is utilising. The UE shall fix the obtained IP address throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the last deregistration; and
c) acquire a P-CSCF address(es).
The UE may acquire an IP address via means other than the DHCP. In this case, upon acquiring an IP address, the UE shall request the configuration information (that includes the DNS and P-CSCF addresses) from the DHCP server.
The methods for acquiring a P-CSCF address(es) are:
I. Employ Dynamic Host Configuration Protocol for IPv4 RFC 2131 [40A] or for IPv6 (DHCPv6) RFC 3315 [40]. Employ the DHCP options for SIP servers RFC 3319 [41] or, for IPv6, RFC 3361 [35A]. Employ the DHCP options for Domain Name Servers (DNS) RFC 3646 [56C].
The UE shall either:
- in the DHCP query, request a list of SIP server domain names of P-CSCF(s) and the list of Domain Name Servers (DNS); or
- request a list of SIP server IP addresses of P-CSCF(s).
II. Obtain the P-CSCF address(es) by employing a procedure that the IP-CAN technology supports. (e.g. GPRS).
III. The UE may use pre-configured P-CSCF address(es) (IP address or domain name). For example:
a. The UE selects a P-CSCF from the list stored in ISIM or IMC;
b. The UE selects a P-CSCF from the list in IMS management object.
NOTE 1: Access-specific annexes provide additional guidance on the method to be used by the UE to acquire P-CSCF address(es).
When acquiring a P-CSCF address(es), the UE can freely select either method I or II or III.
NOTE 2: In case a P-CSCF address is provisioned or received as a FQDN, procedures according to RFC 3263 [27A] will provide the resolution of the FQDN.
The UE may also request a DNS Server IP address(es) as specified in RFC 3315 [40] and RFC 3646 [56C] or RFC 2131 [40A].
When:
- the UE obtains a connection with the IP-CAN by performing handover of the connection from another IP-CAN;
- IP address of the UE is not changed during the handover; and
- the UE already communicates with the IM CN subsystem via the connection with the other IP-CAN, e.g. the UE determines that its contact with host portion set to the UE IP address (or FQDN of the UE) associated with the connection with the other IP-CAN has been bound to a public user identity;
the UE shall continue using the P-CSCF address(es) acquired in the other IP-CAN. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 9.2.2 Handling of the IP-CAN | The means to ensure that appropriate resources are available for the media flow(s) on the IP-CAN(s) related to a SIP session is dependant on the characteristics for each IP-CAN, and is described separately for each IP-CAN in question.
GPRS is described in annex B. xDSL is described in annex E. DOCSIS is described in annex H. EPS is described in annex L. cdma2000® packet data subsystem is described in annex M. EPC via cdma2000® HRPD is described in annex O. cdma2000® Femtocell network is described in annex Q. Evolved Packet Core (EPC) via WLAN is described in annex R. DVB-RCS2 is described in annex S. 5GS is described in annex U. If a particular handling of the IP-CAN is needed for emergency calls, this is described in the annex for each access technology.
9.2.2A P-CSCF restoration procedure
The UE may support P-CSCF restoration procedures.
An IP-CAN may provide means for detecting a P-CSCF failure.
An UE supporting the P-CSCF restoration procedure should either use the keep-alive procedures described in RFC 6223 [143] or the procedure provided by a IP-CAN for monitoring the P-CSCF status.
NOTE 1: The UE can use other means to monitor the P-CSCF status, e.g. ICMP echo request/response. However, those other means are out of scope of this document.
NOTE 2: A UE registered through the procedures described in RFC 5626 [92] can use the keep-alive mechanism to monitor the status of the P-CSCF. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 9.2.3 Special requirements applying to forked responses | Since the UE does not know that forking has occurred until a second provisional response arrives, the UE will request the radio/bearer resources as required by the first provisional response. For each subsequent provisional response that may be received, different alternative actions may be performed depending on the requirements in the SDP answer:
- the UE has sufficient radio/bearer resources to handle the media specified in the SDP of the subsequent provisional response, or
- the UE must request additional radio/bearer resources to accommodate the media specified in the SDP of the subsequent provisional response.
NOTE 1: When several forked responses are received, the resources requested by the UE is the "logical OR" of the resources indicated in the multiple responses to avoid allocation of unnecessary resources. The UE does not request more resources than proposed in the original INVITE request.
NOTE 2: When service-based local policy is applied, the UE receives the same authorization token for all forked requests/responses related to the same SIP session.
When an 199 (Early Dialog Terminated) response for the INVITE request is received for an early dialogue, the UE shall release reserved radio/bearer resources associated with that early dialogue.
When the first final 200 (OK) response for the INVITE request is received for one of the early dialogs, the UE proceeds to set up the SIP session using the radio/bearer resources required for this session. Upon the reception of the first final 200 (OK) response for the INVITE request, the UE shall release all unneeded radio/bearer resources. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10 Media control | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.1 General | The choice of which media control methods below to use is service specific, it depends on the functionality required and physical deployment architectures.
Combinations of the capabilities below are supported by the use of the control channel framework RFC 6230 [146] with associated media control packages.
For security, the principles and protocols described in 3GPP TS 33.210 [19A] shall take precedence over those specified in the referenced specifications in this clause.
For codecs, those described in access specific specifications shall take precedence over those specified in the referenced specifications in this clause. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2 Procedures at the AS | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.1 General | An AS requesting charging information and authorisation for specific media operations and media usage controlled by the MRFC shall use RFC 6230 [146] together with appropriate packages.
NOTE: This is in addition to the charging related procedures in clause 5 and to the charging information and authorisation requests, defined in 3GPP TS 32.260 [17] which provide charging information and authorisation for SIP session and SDP information.
An AS may support delegation of an XML (such as CCXML or SCXML) script execution to an MRFC. An AS supporting delegation of XML script execution shall use RFC 6230 [146] together with appropriate packages.
The packages, or extensions to existing packages using RFC 6230 [146] framework are not specified in this release.
The AS may support the media server resource consumer interface as defined by RFC 6917 [192]. If supported the AS can support either the in-line mode or the query mode or both. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2 Tones and announcements | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2.1 General | An AS may support control of the MRFC for tones and announcements. An AS supporting control of the MRFC for tones and announcements shall support one or more of the following methods:
- RFC 4240 [144] announcement service;
- RFC 5552 [145]; or
- RFC 6230 [146] and RFC 6231 [147]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2.2 Basic network media services with SIP | The AS may support control of the MRFC for basic announcements by the use of RFC 4240 [144] and the announcement service described in RFC 4240 [144] subclause 3.
The media control commands are carried between the AS and the MRFC either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The AS shall provide remote prompts to the MRFC using the AS-MRFC Cr interface. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.