7 Barring of Supplementary Services Configuration and Invocation
24.3153GPPIP Multimedia Subsystem (IMS) Operator Determined Barring (ODB)Release 17Stage 3: protocol specificationTS
7.1 Barring of Management of supplementary service settings and invocation
7.1.1 General
Barring of supplementary services access is invoked in the AS that provides the supplementary service and include management of settings of a supplementary service and user invocation of supplementary services.
Barring of Supplementary Services Access includes the following category:
– Barring of supplementary services management.
NOTE: Supplementary services management can utilize mechanisms such as web-based provisioning which are not standardized in 3GPP. Application of ODB to such mechanisms is out of the scope of this specification.
7.1.2 XCAP Procedures in the Application Server
When an AS that provides an XCAP based interface for configuration of a supplementary service as described in 3GPP TS 24.623 [9], and supporting ODB receives an XCAP request it needs to determine whether the XCAP request is to be rejected due to ODB. In order to do so, the AS shall:
1) identify the served user as specified in 3GPP TS 24.623 [9]; and
2) determine whether the subscription profile for the served user contains the ODB category for barring of supplementary services configuration access.
When the AS decides to reject the XCAP request, the AS shall send a HTTP 403 (Decline) response.
7.1.3 SIP Procedures for service configuration in the Application Server
When an AS that provides a SIP based interface for configuration of a supplementary service, and supporting ODB receives an INVITE SIP request for service configuration set as specified in 3GPP TS 24.238 [8], it needs to determine whether the SIP request is to be rejected due to ODB. In order to do so, the AS shall:
1) identify the served user as specified in 3GPP TS 24.229 [2]; and
2) determine whether the subscription profile for the served user contains the ODB category for barring of supplementary services configuration access.
When the AS decides to reject the SIP request, the AS shall send an indication to the originating UE by sending a SIP 603 (Decline) response.
7.1.4 Barring of user invocation of supplementary service
Except for the barring of the invocation of certain kinds of communication transfer described in subclause 7.3, the barring of user invocation of supplementary services is out of the scope of this specification.
NOTE: The Barring of invocation of a supplementary service can be achieved through the deactivation of the subscription of the user to that service. ODB cannot apply to a supplemantary service that is not subject to user subscription (i.e. the service is provided to all users).
7.2 Barring of manipulation of communication diversion settings
7.2.1 General
Barring of manipulation of communication diversion settings is provided in an AS that provides the communication diversion services as described in 3GPP TS 24.604 [10].
Barring of manipulation of communication diversion comprises the following categories:
– Barring of registration of any communication diverted-to address;
– Barring of registration of any international communication diverted-to address;
– Barring of registration of any international communication diverted-to address except to an address within the HPLMN country.
When determining whether an ODB category applies for a request for setting the registration of a communication diversion, following applies:
1) registration of any communication diverted-to address: this evaluates to true for all registrations for a communication diversion.
2) registration of any international communication diverted-to address: this evaluates to true when the diverted-to address:
a) corresponds to a telephone number, i.e. a SIP URI with a "user" URI parameter set to "phone" or a tel URI; and
b) does not point to a destination served by a network within the country where the originating user is located when initiating the call.
3) registration of any international communication diverted-to address except to an address within the HPLMN country: this evaluates to true when the diverted-to address
a) corresponds to a telephone number, i.e. a SIP URI with a "user" URI parameter set to "phone" or a tel URI;
b) does not point to a destination served by a network within the country where the originating user is located when initiating the call; and
c) does not point to a destination served within the served users home network.
When a barring category for communication diversion registration is set all the previously registered communication diversions that overlap with this category shall be deactivated.
7.2.2 XCAP Procedures in the Application Server
When an AS that provides an XCAP based interface for configuration of communication diversion as described in 3GPP TS 24.238 [8] and 3GPP TS 24.604 [10], and supporting ODB receives an XCAP request it needs to determine whether the XCAP request is to be rejected due to ODB. In order to do so, the AS shall:
1) identify the served user as specified in 3GPP TS 24.623 [9]; and
2) determine whether the subscription profile for the served user contains ODB categories as listed in subclause 7.2.1 and whether these categories apply to the received XCAP request.
When the AS decides to reject the XCAP request, the AS shall send a HTTP 403 (Decline) response.
7.2.3 SIP Procedures in the Application Server
When an AS that provides a SIP based interface for configuration of communication diversion as described in 3GPP TS 24.604 [10] and supporting ODB receives a SIP request it needs to determine whether the SIP request is to be rejected due to ODB. In order to do so, the AS shall:
1) identify the served user as specified in 3GPP TS 24.229 [2]; and
2) determine whether the subscription profile for the served user contains ODB categories as listed in subclause 7.2.1 and whether these categories apply to the received SIP request.
When the AS decides to reject the SIP request, the AS shall send an indication to the originating UE by sending a SIP 603 (Decline) response.
7.3 Barring of invocation of call transfer
7.3.1 General
Barring of invocation of communication transfer is provided in an AS serving that provides the explicit communication transfer service as described in 3GPP TS 24.629 [15].
Barring of invocation of communication transfer includes one of the following categories:
– Barring of invocation of communication transfer;
– Barring of invocation of communication transfer where at least one of the two communications is a communication charged to the served subscriber; i.e. the communication is either an outgoing communication or an incoming communication when the served subscriber roams outside the HPLMN;
– Barring of invocation of communication transfer where at least one of the two communications is a communication charged to the served subscriber at international rates, i.e. the communication is either an outgoing international communication or an incoming communication when the served subscriber roams outside the HPLMN country;
and one of the following categories:
– Barring of invocation of communication transfer where both communications are communications charged to the served subscriber, i.e. both communications are either outgoing communications or incoming communications when the served subscriber roams outside the HPLMN;
and one of the following categories:
– Barring of further invocation of communication transfer if there is already one ongoing transferred communication for the served subscriber.
7.3.2 SIP Procedures in the Application Server
When an AS that provides the explicit communication transfer service as described in 3GPP TS 24.629 [15], and supporting ODB receives a SIP REFER request for initiating a Call Transfer as defined 3GPP TS 24.629 [15] it needs to determine whether the SIP REFER request is to be rejected due to ODB. In order to do so, the AS shall:
1) identify the served user as specified in 3GPP TS 24.229 [2]; and
2) determine whether the subscription profile for the served user contains ODB categories as listed in subclause 7.3.1 and whether these categories apply to the received SIP REFER request.
When the AS decides to reject the SIP REFER request, the AS shall send an indication to the originating UE by sending a SIP 603 (Decline) response.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2012-10 |
Initial version- contains agreed P-CRs from CT1#80: C1-124219, C1-124220, C1-124108, C1-124109, C1-124221 |
0.0.0 |
0.0.1 |
||||
|
2012-11 |
Contains agreed P-CRs from CT#81: C1-124512, C1-124857, C1-124858, C1-124859, C1-124860, C1-124861, C1-125011 |
0.0.1 |
0.1.0 |
||||
|
2012-12 |
CT-58 |
CP-120708 |
Version 1.0.0 created by MCC for presentation for information and approval |
0.1.0 |
1.0.0 |
||
|
2012-12 |
CT-58 |
Version 11.0.0 created by MCC after approval at CT-58 |
1.0.0 |
11.0.0 |
|||
|
2013-03 |
CT-59 |
CP-130122 |
0001 |
ODB: AS determination of action to perform for barred calls |
11.0.0 |
11.1.0 |
|
|
2013-03 |
CT-59 |
CP-130122 |
0002 |
1 |
Check of barring for incoming communication |
11.0.0 |
11.1.0 |
|
2013-03 |
CT-59 |
CP-130122 |
0003 |
2 |
Interaction between ODB and Emergency calls |
11.0.0 |
11.1.0 |
|
2014-06 |
CT-64 |
CP-140316 |
0006 |
3 |
Barrring of premium number |
11.1.0 |
12.0.0 |
|
2014-12 |
CT-66 |
CP-140864 |
0008 |
1 |
Reference Update: RFC7315 |
12.0.0 |
12.1.0 |
|
2015-12 |
CT-70 |
Upgrade to Rel-13 |
12.1.0 |
13.0.0 |
|||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CT-75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-06 |
SA-80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
|
2020-07 |
SA-88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-03 |
CT-95e- |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |