7 Processing of supplementary service operations

22.0043GPPGeneral on supplementary servicesRelease 17TS

7.1 Processing of operations containing basic service information

The network shall process a registration/erasure/activation/deactivation request indicating basic service information independent of the previous registration/activation status. As a result the network will process these requests for the indicated basic service information only, whereas other registration/activation status information remains unchanged.

Basic service information received by the network within the above supplementary service operations is in the specifications [6]-[18]. According to this definition the network may receive a combined basic service indication, e.g. for all basic services. As a result the combined basic service indication may be dissolved (note 1). This has to be taken into account when an interrogation procedure is performed.

In case the operation contains a combined basic service indication (e.g. for all bearer services) the interactions specified in the specifications [6]-[18] have to be checked subsequently for each member of the combined service indication. As a result a supplementary service request may be partly rejected due to the interaction requirements (note 2). This has to be taken into account in the acknowledgement to the supplementary service request from the Mobile Station (MS), i.e. the network shall send a notification to the MS that the SS operation request was only partially successful.

NOTE 1: Explanatory example

1. Operation:

Registration of CFU for "all basic services" to number 1.

2. Operation:

Registration of CFU for "Speech" to number 2.

Result:

Registration status for

"Speech": CFU active to number 2.

All other basic service groups: CFU active to number 1.

NOTE 2: Explanatory example

1. Operation:

Registration of CFB for "Speech" to number 1.

2. Operation:

Activation of BAOC for "Facsimile services".

3. Operation:

Registration of CFU for "all basic services" to number 2.

Result:

Registration status for

"Speech": CFU active to number 2, CFB "quiescent" to number 1.

"Facsimile services": BAOC Active, CFU rejected.

All other basic service groups: CFU active to number 2.

7.2 Processing of operations involving multiple Supplementary Services

Normally, SS operations relate to one single Supplementary Service at a time. The network reaction on such operations are described in the specifications [6]-[18] subclauses x.3 (Normal Procedures), x.4 (Exceptional Procedures) and x.6 (Interaction). Also subclause 7.1 contains information related to this area.

In addition, some groups of Supplementary Services may be controlled collectively, such as Call Forwarding and Barring services. The information contained in such "global" operation (e.g. Forwarded‑to‑number, Password, Basic Service group(s)) then applies generally to all SS concerned by the operation.

The reaction of the network when receiving such control requests is generally the same as when receiving a number of subsequent single operations to the corresponding Supplementary Services. However, in some cases the action to be taken by the network may be regarded as "exceptional", and therefore the following clarifies the only allowed operations on groups of Supplementary Services:

‑ If the group "all Call Forwarding services" is subject for a Registration or an Activation request, CFU shall become Active and Operative whilst the conditional CFs (CFC) will become Active and quiescent for the Basic Service groups concerned by the operation. I.e the network behaviour is the same as if the CFCs were Registered/Activated first, followed by Registration/Activation of CFU.

The No Reply Timer may be a part of this general operation.

If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of apply, i.e. the network ignores these parts of the request.

‑ If the group "all Conditional Call Forwarding services" is subject for a Registration or an Activation request, all CFCs shall become Active and Operative for the Basic Service groups concerned by the operation.

The No Reply Timer may be a part of this general operation.

If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of apply, i.e. the network ignores these parts of the request.

‑ If the group "all Call Forwarding services" or the group "all Conditional Call Forwarding services" is subject for a Deactivation or an Erasure request, the network shall act as normal, i.e. as if a number of subsequent Deactivations/Erasures were requested. If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of this specification apply, i.e. the network ignores these parts of the request.

‑ If any of the groups "all Barring services", "all Outgoing Barring Services" or "all Incoming Barring Services" is subject to a Deactivation request, the network shall act as normal, i.e. as if a number of subsequent Deactivations were requested.

If the Basic Service information provided in the request is not relevant to one or more of the SS involved, the principles in subclause 7.1 of this specification apply, i.e. the network ignores these parts of the request.

‑ If the user requests Password Registration for any other single or group of Barring Services than "all Barring Services" the request will be denied (as only one (common) password for the Barring services per subscriber is allowed).

‑ Interrogation of groups of Supplementary Services is not supported.

7.3 Compatibility Information and Supplementary Services

Within the Single Numbering Scheme it is possible that an incoming call (e.g. PSTN call) do not have an allocated Bearer Capability Information Element. The network cannot at this stage determine the Basic Service requirement and shall, for Supplementary Service purposes, handle the call based on a "default basic service" for the call. If the subscriber has a subscription to telephony then the network shall use telephony as the "default basic service". If the subscriber does not have a subscription to telephony the HLR shall choose a Basic Service from the set provisioned to the subscriber as the "default basic service".

When an incoming call is subject to Call Forwarding, no modifications or additions to the original BC‑IE information, present or not, received by the PLMN shall be sent with the forwarded call.