hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 t... |
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 su... |
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 n... |
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
... |
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 unk... |
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 secti... |
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-Prio... |
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> elem... |
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="u... |
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... |
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"... |
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 th... |
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 acknowledg... |
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... |
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 ... |
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 thr... |
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 an... |
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 r... |
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... |
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, d... |
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.
Th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2.3 SIP interface to VoiceXML media services | The AS may support control of the MRFC for voice dialogs by the use of RFC 5552 [145].
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 and scripts to the MRFC using the AS-MRFC... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2.4 Media control channel framework and packages | The AS may support control of the MRFC for interactive voice response by the use of RFC 6231 [147] and RFC 6230 [146].
The AS shall provide remote prompts, media control commands and scripts to the MRFC using the AS-MRFC Cr interface.
The AS shall implement the control client role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3 Ad-hoc conferences | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3.1 General | An AS may support control of the MRFC for ad-hoc conferencing. An AS supporting control of the MRFC for ad-hoc conferencing shall support one or more of the following methods:
- RFC 4240 [144] conference service; or
- RFC 6230 [146] and RFC 6505 [148]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3.2 Basic network media services with SIP | The AS may support control of the MRFC for basic conferencing by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
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. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3.3 Media control channel framework and packages | The AS may support control of the MRFC for conference mixing by the use of RFC 6505 [148] and RFC 6230 [146].
An AS may support control of the MRFC for floor controlled conferences (as specified in 3GPP TS 24.147 [8B]), via the use of RFC 6230 [146] together with appropriate packages. The packages, or extensions to exi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4 Transcoding | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4.1 General | An AS may support control of the MRFC for transcoding. An AS supporting control of the MRFC for transcoding shall support one or more of the following methods:
- RFC 4240 [144] conference service; or
- RFC 6230 [146] and RFC 6505 [148]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4.2 Basic network media services with SIP | The AS may support control of the MRFC for transcoding by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
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. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4.3 Media control channel framework and packages | The AS may support control of the MRFC for transcoding by the use of RFC 6505 [148] and RFC 6230 [146].
The AS shall provide media control commands to the MRFC using the AS-MRFC Cr interface.
The AS shall implement the control client role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3 Procedures at the MRFC | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.1 General | An MRFC required to generate charging information and authorize requests from an AS for specific media operations and media usage shall support 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 re... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2 Tones and announcements | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.1 General | An MRFC may support control of tones and announcements. An MRFC supporting control of 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.3.2.2 Basic network media services with SIP | The MRFC may support control of 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 received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC shall fetch remote ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.3 SIP interface to VoiceXML media services | The MRFC may support control of voice dialogs by the use of RFC 5552 [145].
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC shall fetch via the AS-MRFC Cr interface the remote prompts and scripts from the address inclu... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.4 Media control channel framework and packages | The MRFC may support control of interactive voice response by the use of RFC 6231 [147] and RFC 6230 [146].
The MRFC shall fetch remote prompts and scripts from the MRFC using the AS-MRFC Cr interface. The MRFC shall send media control command responses and notifications to the AS using the AS-MRFC Cr interface.
The MR... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3 Ad-hoc conferences | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3.1 General | An MRFC may support control of ad-hoc conferencing. An MRFC supporting control of ad-hoc conferencing shall support one or more of the following methods:
- RFC 4240 [144] conference service; or
- RFC 6230 [146] and RFC 6505 [148]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3.2 Basic network media services with SIP | The MRFC may support control of basic conferencing by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC acts as the media serv... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3.3 Media control channel framework and packages | The MRFC may support control of conference mixing by the use of RFC 6505 [148] and RFC 6230 [146].
An MRFC may support control of floor controlled conferences (as specified in 3GPP TS 24.147 [8B]), via the use of RFC 6230 [146] together with appropriate packages. The packages, or extensions to existing packages using R... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4 Transcoding | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4.1 General | An MRFC may support control of transcoding. An MRFC supporting control of transcoding shall support one or more of the following methods:
- RFC 4240 [144] conference service;
- RFC 6230 [146] and RFC 6505 [148]; or
- RFC 4117 [166]. This is detailed in subclause 5.7.5.6. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4.2 Basic network media services with SIP | The MRFC may support control of transcoding by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC acts as the media server desc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4.3 Media control channel framework and packages | The MRFC may support control of transcoding by the use of RFC 6505 [148] and RFC 6230 [146].
The MRFC shall send media control command responses and notifications to the AS using the AS-MRFC Cr interface.
The MRFC shall implement the control server role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.4 Procedures at the MRB | The MRB shall support: a) the in-line unaware MRB interface. as defined in RFC 5917 [192]. The MRB may support: a) the media server resource publish interface; and b) the media server resource consumer interface; as defined in RFC 6917 [192]. Annex A (normative): Profiles of IETF RFCs for 3GPP usage A.1 Profiles A.1.1 ... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 1 Scope | The present document specifies the service requirements for Multimedia Priority Service (MPS).
The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered wi... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 3 Definitions and abbreviations | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
MPS session: A session for which priority treatment is applied for allocating and ma... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
DTS Data Transport Service
MMTEL Multimedia Telephony
MPS Multimedia Priori... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 4 General description | MPS is applicable in EPS and 5GS systems.
MPS provides priority treatment to increase the probability of an authorized Service User’s Voice, Video, Data and Messaging communication being successful. Some form of priority treatment is applied to the MPS invocation and session establishment, and continues to be applied u... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5 High level requirements | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.1 General | The system shall provide preferential treatment based on the subscription for MPS for:
- An authorized Service User using a UE with an MPS subscription,
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In ... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.2 Priority session treatment in originating network | When an MPS session is originated by a Service User, the session shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, data, and messaging service) in the originating PLMN based on the originating Service User priority information (i.e., priority indication and pri... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.3 Priority session progression | For an MPS session, a Service User shall receive priority session treatment/progression through the PLMN(s). In case the MPS session traverses or terminates in other networks (e.g., the PSTN), the network providing priority session treatment/progression shall support the capability to indicate to the other network that... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.4 Priority session treatment in terminating network | When a terminating network receives an incoming MPS session establishment attempt, the MPS session shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, data, and messaging service) in the terminating PLMN, based on the originating Service User priority information... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.5 Priority levels | The Service User shall be assigned one of "n" user priority levels. The priority levels are defined with 1 being the highest priority level and "n" being the lowest priority level.
The 3GPP network shall be able to support at least 5 user priority levels.
Assignment of priority levels is a matter of regional/national a... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.6 Invocation on demand | MPS priority shall be invoked only when requested by the Service User. However, certain priority treatments are provided prior to invocation as specified in Section 5.13.
MPS is applied when idle resources required for an origination session request are not available.
If idle resources are available when MPS is request... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.7 Multimedia priority service code/identifier | MPS shall be requested by including an MPS code/identifier in the session origination request, or optionally, by using an MPS input string (e.g., an MPS public user identity). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.8 Roaming | MPS shall be supported when the Service User is roaming and the visited network and home network support MPS, and roaming agreements are in place for MPS. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.8.1 Roaming within the home country | The system shall support MPS when a UE with an MPS subscription is roaming within the home country and the visited and home network support MPS, and roaming agreements are in place for MPS.
NOTE 1: Roaming within a home country is subject to national/regional rules and operator policy.
NOTE 2: The MPS subscription rela... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.8.2 Roaming outside the home country | The system shall support MPS when a UE with an MPS subscription is roaming outside of the home country and the visited and home network support MPS, and roaming agreements are in place for MPS.
NOTE 1: Roaming outside a home country is subject to national/regional rules and operator policy.
NOTE 2: The UE subscription ... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.9 Handover | MPS shall be supported during and after the handover (i.e., sessions shall continue to get priority treatment in the network during and after the handover). Resource allocation for the session during handover shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, an... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10 Interworking with CS domain | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10.1 Mobile origination in the CS domain -> MPS mobile termination | For a Priority Service voice call, as described in [2] and as specified in [3, 4, 5], originated by a Service User in the CS Domain, MPS shall support priority Mobile Termination of the session in the IMS. The priority information received from the CS domain shall be mapped and used in the IMS accordingly. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10.2 MPS mobile origination -> mobile termination to the CS domain | For an MPS voice session originated by a Service User in the IMS, MPS shall support priority delivery of the voice session to the serving CS Domain. The calling Service User priority level shall be sent to the CS Domain. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10.3 CS Fallback from LTE | Circuit Switched (CS) fallback from LTE needs to be given priority in the LTE system to support MPS voice in cells where voice is not supported in the PS domain. Priority treatment applies to both mobile originated calls and mobile terminated calls.
When an MPS Service User in LTE originates a voice call intended to be... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.11 Network Management Functions | Based on regional/national requirements and network operator policy, an MPS session shall be exempted from network management controls up to the point where further exemption would cause network instability. Congestion controls, overload controls, load balancing, and load re-balancing shall not adversely impact MPS. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.12 Policy Control | The 3GPP network shall be able to make and enforce policy decisions regarding relative treatment of MPS application services (Voice, Video, Data, and Messaging) for admission control subject to regional/national regulatory requirements and operator policy.
The 3GPP network shall be able to make and enforce policy decis... |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.13 Priority before service invocation | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.13.1 Overview of priority before service invocation | Providing priority treatment to MPS-subscribed UEs during attachment/registration for radio access and network connectivity before the MPS application service session invocation requests improves the probability of an MPS session request being successful. This involves providing priority treatment for the signalling du... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.