|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Selective Disabling of
3GPP User Equipment Capabilities (SDoUE)
Management Object (MO)
(3GPP TS 24.305 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 1 ETSI TS 124 305 V15.1.0 (2018-09)
Reference
RTS/TSGC-0124305vf10
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 2 ETSI TS 124 305 V15.1.0 (2018-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 3 ETSI TS 124 305 V15.1.0 (2018-09)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
1 Scope . 5
2 References . 5
3 Definitions, symbols and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Selective Disabling of 3GPP UE Capabilities Management Object . 6
5 Management Object parameters . 7
5.1 General . 7
5.2 Node: . 7
5.3 //Name . 7
5.4 //CS_Calls . 8
5.5 // CS_EmergencyCalls . 8
5.5A //CS_EmergencyCalls/ . 9
5.5B //CS_EmergencyCalls//Country . 9
5.5C //CS_EmergencyCalls//Country/Network . 9
5.6 //SupplementaryServices . 9
5.7 //CS_SMS . 10
5.8 //PS_SMS . 10
5.9 //CS_LCS . 10
5.10 //PS_LCS . 11
5.11 //GPRS_SM_PDP . 11
5.12 //GPRS_SM_MBMS . 12
5.12A //EPS_SM_EPS . 12
5.12B //APN . 13
5.12C //TrafficMappingInfo . 13
5.12D //NumberOfPacketFilters . 13
5.12E //PacketFilterList . 13
5.12F //5GS_SM_PDU . 14
5.13 //IMS . 14
5.14 //Text . 15
5.15 //CustomerCareNumbers/ . 15
5.16 //CustomerCareNumbers/ . 15
5.17 //CustomerCareNumbers//CustomerCareNumber . 16
5.17A //AlertServerID . 16
5.18 // IMS_EmergencyCalls . 16
5.19 //IMS_EmergencyCalls/ . 17
5.20 //IMS_EmergencyCalls//Country . 17
5.21 //IMS_EmergencyCalls//Country/Network . 17
5.22 //Ext . 17
Annex A (informative): Management Object DDF . 19
Annex B (informative): Change history . 29
History . 30
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 4 ETSI TS 124 305 V15.1.0 (2018-09)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 5 ETSI TS 124 305 V15.1.0 (2018-09)
1 Scope
The present document specifies a mobile device Selective Disabling of 3GPP UE Capabilities (SDoUE) Management
Object (MO) and the rules and corresponding behaviour of the UE with regard to the selective disabling of 3GPP UE
capabilities, for example, when services or functions are disabled/enabled.
The SDoUE MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and
upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release
Definition OMA-ERELD-DM-V1_2 [8].
The SDoUE MO consists of the relevant parameters that can be managed for selective disabling of 3GPP UE
capabilities.
The SDoUE MO defines a repository of data into the ME.
The service requirements for selective disabling of 3GPP UE capabilities are defined in 3GPP TS 22.011 [2].
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.011: "Service accessibility".
[2A] 3GPP TS 23.003: "Numbering, addressing and identification".
[3] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[4] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General
aspects".
[5] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[6] 3GPP TS 24.030: "Location Services (LCS); Supplementary service operations; Stage 3".
[7] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3".
[7A] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS);
Stage 3".
[7B] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[8] OMA-ERELD-DM-V1_2: "Enabler Release Definition for OMA Device Management".
[9] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[10] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and
mobile users".
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 6 ETSI TS 124 305 V15.1.0 (2018-09)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] apply.
3.2 Abbreviations
ACL Access Control List
CS Circuit Switched
DDF Device Description Framework
DM Device Management
EPS Evolved Packet System
ESM EPS Session Management
IMS IP Multimedia core network Subsystem
MBMS Multimedia Broadcast/Multicast Service
MCC Mobile Country Code
MNC Mobile Network Code
ME Mobile Equipment
MO Management Object
OMA Open Mobile Alliance
PDP Packet Data Protocol
PS Packet Switched
SDoUE Selective Disabling of 3GPP UE Capabilities
SM Session Management
UE User Equipment
4 Selective Disabling of 3GPP UE Capabilities
Management Object
The Selective Disabling of 3GPP UE Capabilities (SDoUE) Management Object (MO) is used to manage settings of the
UE for remotely disabling selected UE capabilities.
The Management Object Identifier is: urn:oma:mo:ext-3gpp-sdoue:1.0.
The OMA DM Access Control List (ACL) property mechanism as standardized (see Enabler Release Definition OMA-
ERELD-DM-V1_2 [8]) may be used to grant or deny access rights to OMA DM servers in order to modify nodes and
leaf objects of the SDoUE MO.
The following nodes and leaf objects are possible under the SDoUE node:
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 7 ETSI TS 124 305 V15.1.0 (2018-09)
Name ?
CS_Calls ?
Country
CS_EmergencyCalls ? +
SupplementaryServices ?
Network ?
CS_SMS ?
PS_SMS ?
CS_LCS ?
PacketFilterList
PS_LCS ?
NumberOfPacketFilters
GPRS_SM_PDP ?
TrafficMappingInfo ?
GPRS_SM_MBMS ?
APN ?
EPS_SM_EPS ?
5GS_SM_PDU?
Text ?
CustomerCareNumber
CustomerCareNumbers ? +
AlertServerID ?
Country
IMS_EmergencyCalls ? +
Network ?
Ext ?
Figure 1: The SDoUE Management Object
5 Management Object parameters
5.1 General
This clause describes the parameters for the SDoUE Management Object (MO).
5.2 Node:
This interior node acts as a placeholder for zero or one accounts for a fixed node.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get
- Values: N/A
5.3 //Name
The Name leaf is a name for the SDoUE MO settings.
- Occurrence: ZeroOrOne
- Format: chr
- Access Types: Get
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 8 ETSI TS 124 305 V15.1.0 (2018-09)
- Values:
5.4 //CS_Calls
The CS_Calls leaf indicates an operator’s preference to enable or disable mobile-originated Call Control (CC)
procedures except for emergency calls.
The CC procedures are specified in 3GPP TS 24.008 [3].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated CS calls are enabled.
1 – Indicates that mobile-originated CS calls are disabled.
When the CS_Calls leaf value is set to "1", the UE shall initiate the signalling procedure for release of all calls except
for emergency calls (see 3GPP TS 24.008 [3]). Furthermore, the UE shall not use mobile-originated call control
procedures except for emergency calls and customer care service number(s) until the CS_Calls leaf value is set to "0".
NOTE: Customer care service number(s) is(are) provided by the CustomerCareNumbers leaf (see sub-clauses
5.15, 5.16 and 5.17).
5.5 // CS_EmergencyCalls
The CS_EmergencyCalls interior node indicates an operator’s preference to enable or disable emergency call control
procedures.
NOTE 1: Disabling of emergency call control procedures is subject to regional regulatory requirements. Therefore,
emergency call control procedures cannot be disabled in regions where support of them is required (see
3GPP TS 22.011 [2]).
The emergency call control procedures are specified in 3GPP TS 24.008 [3].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that CS emergency calls are enabled.
1 – Indicates that CS emergency calls are disabled.
When the CS_EmergencyCalls node value is set to "1" and the UE detects being under coverage of a PLMN (identified
by Mobile Country Code (MCC) and Mobile Network Code (MNC)) as indicated by any of the stored Country and
Network pairs of nodes (see sub-clauses 5.5A, 5.5B and 5.5C), then the UE shall initiate the signalling procedure for
release of all emergency calls that use call control procedures. Furthermore, the UE shall not use call control procedures
to establish emergency calls until the CS_EmergencyCalls node value is set to "0" or the UE detects a change of Mobile
Country Code (MCC) and Mobile Network Code (MNC) that does not match any of the stored Country and Network
pairs of nodes.
NOTE 2: As described by the definition and structure of the SDoUE MO the Country and Network nodes, if exist,
constitute a pair of nodes. However, it is possible to indicate only a country/region by means of only
setting the value of the Country node.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 9 ETSI TS 124 305 V15.1.0 (2018-09)
5.5A //CS_EmergencyCalls/
This run-time node acts as a placeholder for one or more Country nodes. Furthermore, this node provides a means for
the operator to indicate where emergency call control procedures are disabled (i.e. The CS_EmergencyCalls value is set
to "1").
- Occurrence: ZeroOrMore
- Format: node
- Access Types: Get
- Values: N/A
5.5B //CS_EmergencyCalls//Country
The Country interior node represents one Mobile Country Code (MCC). This node provides a means for including
information that can be used to indicate in which MCC the emergency call control procedures are disabled (i.e. The
CS_EmergencyCalls value is set to "1").
The Country node value shall be a Mobile Country Code (MCC) as specified by ITU-T E.212 [10].
- Occurrence: One
- Format: chr
- Access Types: Get
- Values:
The UE shall only use the information stored in the Country node when emergency call control procedures are disabled
(i.e. The CS_EmergencyCalls value is set to "1").
5.5C //CS_EmergencyCalls//Country/Network
The Network leaf represents one Mobile Network Code (MNC). This leaf provides a means, together with the Country
leaf, for including information that can be used to indicate in which MCC and MNC the emergency calls procedures are
disabled.
The Network leaf value shall be a Mobile Network Code (MNC) as specified by ITU-T E.212 [10].
- Occurrence: ZeroOrOne
- Format: chr
- Access Types: Get
- Values:
The UE shall only use the information stored in the Network leaf when emergency call control procedures are disabled
(i.e. The CS_EmergencyCalls value is set to "1"). Furthermore, the UE shall interpret the information stored in the
Network leaf, if exists, in conjunction with the corresponding Country node.
5.6 //SupplementaryServices
The SupplementaryServices leaf indicates an operator’s preference to enable or disable mobile-originated
Supplementary services operations.
The Supplementary service operations are specified in 3GPP TS 24.010 [4].
NOTE: The functionality indicated by the SupplementaryServices leaf does not include the Location Service
(LCS) supplementary service operations.
- Occurrence: ZeroOrOne
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 10 ETSI TS 124 305 V15.1.0 (2018-09)
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated Supplementary service operations are enabled.
1 – Indicates that mobile-originated Supplementary service operations are disabled.
When the SupplementaryServices leaf value is set to "1", the UE shall initiate the signalling procedure for release of all
ongoing supplementary service operations (transactions). Furthermore, the UE shall not invoke mobile-originated
supplementary service operation procedures until the SupplementaryServices leaf value is set to "0".
5.7 //CS_SMS
The CS_SMS leaf indicates an operator’s preference to enable or disable mobile-originated Short Message Service
(SMS) via CS.
The SMS procedures are specified in 3GPP TS 24.011 [5].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated SMS via CS are enabled.
1 – Indicates that mobile-originated SMS via CS are disabled.
If the CS_SMS leaf value is "1", the UE shall not use the CS domain for mobile-originated SMS transfer until the
CS_SMS leaf value is set to "0". The UE may use the PS domain instead of the CS domain for mobile-originated SMS
transfer when the CS_SMS leaf value is "1".
5.8 //PS_SMS
The PS_SMS leaf indicates an operator’s preference to enable or disable mobile-originated Short Message Service
(SMS) via PS.
The SMS procedures are specified in 3GPP TS 24.011 [5].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated SMS via PS are enabled.
1 – Indicates that mobile-originated SMS via PS are disabled.
If the PS_SMS leaf value is "1", the UE shall not use the PS domain for mobile-originated SMS transfer until the
PS_SMS leaf value is set to "0". The UE may use the CS domain instead of the PS domain for mobile-originated SMS
transfer when the PS_SMS leaf value is "1".
5.9 //CS_LCS
The CS_LCS leaf indicates an operator’s preference to enable or disable mobile-originated Location Service (LCS)
operations via CS.
The LCS Supplementary service operations are specified in 3GPP TS 24.030 [6].
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 11 ETSI TS 124 305 V15.1.0 (2018-09)
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated LCS via CS enabled.
1 – Indicates that mobile-originated LCS via CS disabled.
If the CS_LCS leaf value is "1", the UE shall not use the CS domain for mobile-originated LCS service operations until
the CS_LCS leaf value is set to "0". The UE may use the PS domain instead of the CS domain for mobile-originated
LCS service operations when the CS_LCS leaf value is "1".
5.10 //PS_LCS
The PS_LCS leaf indicates an operator’s preference to enable or disable mobile-originated Location Service (LCS)
operations via PS.
The LCS Supplementary service operations are specified in 3GPP TS 24.030 [6].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated LCS via PS are enabled.
1 – Indicates that mobile-originated LCS via PS are disabled.
If the PS_LCS leaf value is "1", the UE shall not use the PS domain for mobile-originated LCS service operations until
the PS_LCS leaf value is set to "0". The UE may use the CS domain instead of the PS domain for mobile-originated
LCS service operations when the PS_LCS leaf value is "1".
5.11 //GPRS_SM_PDP
The GPRS_SM_PDP leaf indicates an operator’s preference to enable or disable mobile-originated GPRS Session
Management (SM) procedures for PDP contexts, e.g. PDP context activation, deactivation and modification.
The GPRS SM procedures for PDP contexts are specified in 3GPP TS 24.008 [3].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that mobile-originated GPRS SM procedures for PDP contexts are enabled.
1 – Indicates that mobile-originated GPRS SM procedures for PDP contexts are disabled.
When the GPRS_SM_PDP leaf value is set to "1", the UE shall initiate the signalling procedure for PDP context
deactivation of all PDP contexts (see 3GPP TS 24.008 [3]). Additionally, the UE shall not use mobile-originated GPRS
SM procedures for PDP contexts until the GPRS_SM_PDP leaf value is set to "0". The UE is however allowed to use
mobile-originated GPRS SM procedure for PDP context activation in the following cases:
- upon receipt of an OMA DM notification message indicating that the UE shall initiate an OMA DM session to
the OMA DM server that either had set the disable value of the GPRS_SM_PDP leaf or is the one stored in the
AlertServerID leaf;
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 24.305 version 15.1.0 Release 15 12 ETSI TS 124 305 V15.1.0 (2018-09)
- when the mobile-originated PDP context activation procedure is necessary in order to either establish an
emergency call over IMS (if the IMS_EmergencyCalls value is set to "0") or send an OMA DM generic alert
message according to the sub-clause 5.17A.
5.12 //GPRS_SM_MBMS
The GPRS_SM_MBMS leaf indicates an operator’s preference to enable or disable GPRS Session Management (SM)
procedures for MBMS contexts, i.e. MBMS context activation and deactivation.
The GPRS SM procedures for MBMS contexts are specified in 3GPP TS 24.008 [3].
- Occurrence: ZeroOrOne
- Format: bool
- Access Types: Get
- Values: 0, 1
0 – Indicates that GPRS SM procedures for MBMS contexts are enabled.
1 – Indicates that GPRS SM procedures for MBMS contexts are disabled.
When the GPRS_SM_MBMS leaf value is set to "1", the UE shall locally release all resources allocated for MBMS
contexts and it shall erase the MBMS context data. Furthermore, the UE shall not use GPRS SM procedures for MBMS
contexts until the GPRS_SM_MBMS leaf value is set to "0".
5.12A //EPS_SM_EPS
The EPS_SM_EPS interior node indicates an operator’s preference to enable or disable mobile-requested EPS Session
Management (SM) procedures for EPS contexts, e.g. UE requested PDN connectivity, UE requested bearer resource
modification, UE requested PDN disconnect, as
...