5 Barring of Communication

24.3153GPPIP Multimedia Subsystem (IMS) Operator Determined Barring (ODB)Release 17Stage 3: protocol specificationTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 Barring of outgoing Communication

5.1.1 General

Barring of outgoing communication is invoked in the AS performing ODB service.

Barring of outgoing communication includes one of the following categories:

– barring outgoing communication;

– barring outgoing international communications;

– barring outgoing international communications except those directed to the home PLMN country; or

– barring of outgoing communications when roaming outside the home PLMN country;

and one or more of the following categories:

– barring of outgoing Premium Rate Communications (Information);

– barring of outgoing Premium Rate Communications (Entertainment);

– barring of outgoing Premium Rate Communications (Information) when roaming outside the home PLMN country; or

– barring of outgoing Premium Rate Communications (Entertainment) when roaming outside the home PLMN country.

and one or more of the following categories:

– when registered in the HPLMN, Operator Specific Barring (Type 1);

– when registered in the HPLMN, Operator Specific Barring (Type 2);

– when registered in the HPLMN, Operator Specific Barring (Type 3); or

– when registered in the HPLMN, Operator Specific Barring (Type 4).

Barring of outgoing communications does not apply to emergency communications.

5.1.2 Procedures in the Application Server

The AS providing the ODB service shall operate as a routeing B2BUA as specified in subclause 5.7.5 of 3GPP TS 24.229 [2]. An AS providing the ODB service and rejecting a request shall operate as a terminating UA, as specified in subclause 5.7.2 of 3GPP TS 24.229 [2].

On reception of an initial SIP INVITE request or SIP MESSAGE request initiated by the UE, which contain in the Request-URI neither a service URN with a top-level service type of "sos" as specified in RFC 5031 [16] nor a number recognized as an emergency number based on local configuration, an AS providing the ODB service needs to determine whether ODB is applied to the SIP request. In order to do so the AS providing the ODB service shall:

1) identify the served user as specified in 3GPP TS 24.229 [2] for communication initiated by the UE;

2) determine whether the subscription profile for the served user contains ODB categories as listed in subclause 5.1.1; and

3) use the rules defined in subclause 5.1.3 to determine whether any of the categories apply to the communication.

When a barring category applies to a communication, the AS shall, based on operator local policy, either:

1) reject the SIP request, and send an indication to the originating UE by sending a SIP 603 (Decline) response. In addition, based on configuration prior to terminate the communication the AS can provide an announcement to the originating user. The procedure of invoking an announcement is described within 3GPP TS 24.628 [6]; or

2) forward the SIP request to a pre-configured destination using normal SIP procedures as defined in 3GPP TS 24.229 [2].

When a new barring category is set for a user, the AS providing the ODB shall determine whether the category applies to any communication of the served user using the rules defined in subclause 5.1.3. When a barring category applies to a communication, the AS providing ODB shall:

1) if two dialogs have been established, then simultaneously send a SIP BYE request for both dialogs managed by the AS, as specified in subclause 5.7.5.3 of 3GPP TS 24.229 [2]; or

2) if a communication is currently being established, then simultaneously send a SIP 603 (Decline) response to the served user and a SIP CANCEL request towards the called user, as specified in 3GPP TS 24.229 [2].

NOTE: In order to get the information about the ODB settings for a subscriber an AS subscribes to notification on such changes via Sh interface as specified in 3GPP TS 29.329 [12].

5.1.3 Determining whether a category applies to a communication

In order to determine whether an ODB category applies for a communication the following applies:

1) outgoing communication: this evaluates to true for all outgoing communication.

2) outgoing international communications: this evaluates to true when the request URI of the outgoing SIP request:

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) outgoing international communications except those directed to the home PLMN country: this evaluates to true when the request URI of the outgoing SIP request:

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.

4) outgoing communications when roaming outside the home PLMN country: this evaluates to true when the served user is registered from an access network other than the served user home network and when the access network is outside the home PLMN country.

NOTE: Whether the served user is registered from another network then the served users home network can be determined from the P-Visited-Network-ID header field specified in IETF RFC 7315 [17] and the P-Access-Network-Info header field specified in IETF RFC 7315 [17]. Both are provided during the registration process, see 3GPP TS 24.229 [2], subclause 5.7.1.3.

5) outgoing Premium Rate Communications (Information): this evaluates to true when the canonical form of the request URI of the outgoing SIP request matches an entry in the locally configured list of URIs for premium rate communications for information.

6) outgoing Premium Rate Communications (Entertainment): this evaluates to true when the when the canonical form of request URI of the outgoing SIP request matches an entry in the locally configured list of URIs for premium rate communications for entertainment.

7) outgoing Premium Rate Communications (Information) when roaming outside the home PLMN country: this evaluates to true when

a) the SIP request from the UE includes an indication that this communication is a Premium Rate Communication (information); and

b) the served user is registered from an access network other than the served user home network and when the access network is outside the home PLMN country.

8) outgoing Premium Rate Communications (Entertainment) when roaming outside the home PLMN country: this evaluates to true when

a) the SIP request from the UE includes an indication that this communication is a Premium Rate Communication (entertainment); and

b) the served user is registered from an access network other than the served user home network and when the access network is outside the home PLMN country.

9) when registered in the HPLMN, Operator Specific Barring (Type 1): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 1.

10) when registered in the HPLMN, Operator Specific Barring (Type 2): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 2.

11) when registered in the HPLMN, Operator Specific Barring (Type 3): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 3.

12) when registered in the HPLMN, Operator Specific Barring (Type 4): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 4.

The Operator specific barring definition for type 1, type 2, type 3, and type 4 is locally configured in the AS providing the ODB service. For operator specific barring the criteria that can be used by the operator to define conditions that are used to determine whether the category applies may be based on any signalling information from the incoming request. Examples of such criteria are:

1) destination type e.g. international numbers or specific numbers;

2) media used in the communication, e.g. audio, video, or text.

When any of the items 1) to 12) evaluates to true then the ODB category applies for a communication.

5.2 Barring of incoming Communication

Barring of incoming communication is invoked in the AS performing the ODB service.

Barring of incoming communication includes one of the following categories:

– barring incoming communications;

– barring incoming communications when roaming outside the home PLMN country;

and one or more of the following categories:

– when registered in the HPLMN, Operator Specific Barring (Type 1);

– when registered in the HPLMN, Operator Specific Barring (Type 2);

– when registered in the HPLMN, Operator Specific Barring (Type 3);

– when registered in the HPLMN, Operator Specific Barring (Type 4).

5.2.2 Procedures in the Application Server

The AS providing the ODB service shall operate as a routeing B2BUA, as specified in subclause 5.7.5 of 3GPP TS 24.229 [2]. An AS providing the ODB service and rejecting a request shall operate as a terminating UA, as specified in subclause 5.7.2 of 3GPP TS 24.229 [2].

On reception of an initial SIP INVITE request or SIP MESSAGE request terminated at the UE an AS providing the ODB service needs to determine whether the SIP request is rejected due to ODB. In order to do so the AS providing the ODB service shall:

1) identify the served user as specified in 3GPP TS 24.229 [2] for terminating communication; and

2) determine whether the subscription profile for the served user contains ODB categories as listed in subclause 5.2.1; and

3) use the rules in subclause 5.2.3 to determine whether any of the categories apply to the communication.

When a barring category applies to a communication, the AS shall, based on operator local policy, either:

2) forward the SIP request to a pre-configured destination using normal SIP procedures as defined in 3GPP TS 24.229 [2].

When a new barring category is set for a user, the AS providing the ODB shall determine whether the category applies to any communication of the served user using the rules defined in subclause 5.2.3. When a barring category applies to a communication, the AS providing ODB shall:

1) if two dialogs have been established, then send simultaneously a SIP BYE request for both dialogs managed by the AS as specified in subclause 5.7.5.3 of 3GPP TS 24.229 [2]; or

NOTE: In order to get the information about the ODB settings for a subscriber an AS subscribes to notification on such changes via Sh interface as specified in 3GPP TS 29.329 [12].

5.2.3 Determining whether a category applies to a communication

When determining whether an ODB category applies for a communication the following applies:

1) incoming communication: this evaluates to true for all incoming requests.

2) incoming communications when roaming outside the home PLMN country: this evaluates to true when the served user is registered from an access network other than the served user home network and when the access network is outside the home PLMN country.

3) when registered in the HPLMN, Operator Specific Barring (Type 1): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 1.

4) when registered in the HPLMN, Operator Specific Barring (Type 2): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 2.

5) when registered in the HPLMN, Operator Specific Barring (Type 3): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 3.

6) when registered in the HPLMN, Operator Specific Barring (Type 4): this evaluates to true when the request matches the locally configured conditions for operator specific barring type 4.

1) origination information e.g. specific numbers;

2) media used in the communication, e.g. audio, video, or text.

When any of the items 1) to 6) evaluates to true then the ODB category applies for a communication.