4 Provision of telecommunication services
22.0013GPPPrinciples of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)Release 17TS
Specifications 3GPP TS 22.101[4] and 3GPP TS 22.011 [13] define some aspects of the provisions of telecommunication services by a 3GPP system.
The provision of telecommunication services implies:
– subscription of basic services and possibly subscription to supplementary services;
– registration into a service directory;
– compatibility between terminals;
– interworking capabilities (see 3GPP TS 29 series of specifications).
The user’s subscription to a Basic or Supplementary service is normally verified by the network prior to completion of Call Establishment and/or Supplementary Service operation. This subscription checking shall be performed in accordance with the following subclauses.
4.1 Subscription checking for Basic Services
General
Subscription checking is the function/process to ascertaining whether a subscriber has the authorization to use the particular Basic Service deduced from the call set-up parameters. It is the responsibility of the HPLMN to transfer, to the VPLMN, only the subscription data corresponding to those services a given subscriber is entitled to use in that VPLMN.
For mobile originated calls, subscription checking is performed in the VLR, whilst for mobile terminated calls it is performed in either the HLR or the VLR (determined as described below). The prerequisite for executing the subscription check is a successful deduction of a Basic Service from the Compatibility Information contained in the call set up, i.e. Bearer Capability Information Element and, in some cases, also the Low Layer and High Layer Compatibility Information elements.
For mobile originated calls an UE shall indicate the requested service by appropriate compatibility information elements according to 3GPP TS 27.001 [8]. This information is mapped to an individual Basic Service code (i.e. the MAP representation) by the MSC in order to be compared with the subscriber data available in the VLR.
An equivalent process is required in the HLR for mobile terminated calls, where the caller’s requested service is indicated to the HLR (by the ISDN) by exhaustive compatibility information consisting of ISDN Bearer Capability Information Elements and in some cases – depending on the service requested – also of Low Layer and High layer Compatibility information elements. In case the compatibility information is not exhaustive, e.g. when the call is originated/transited by a PSTN, no Basic Service can be deduced and subscription checking cannot be performed in the "normal" way. Instead, rules for the Single and Multi Numbering Schemes apply.
In the Multi Numbering Scheme the Basic Service can be deduced by information stored in the HLR against the called number and hence an implicit subscription check is performed. In the Single Numbering Scheme, the Basic Service cannot be deduced until the UE has responded to the set up and therefore the HLR cannot perform subscription check. Instead, the VLR/MSC will perform the subscription check or calls are passed "unfiltered" (as regards subscription check), at the network operators’ discretion.
Bearer Services
3GPP TS 22.002 [5] lists the Bearer Services, each of them with a specific "BS number". Single services defined independent of the fixed network user rate are called General Bearer Services. These distinct [numbered] services may individually be provided to a subscriber. Whichever the subscription arrangements are, all PLMNs (MSCs, VLRs and HLRs) shall be able to allow – as regards subscription checking – the use of individually subscribed-to Basic Services, within the range of services supported by the PLMN. That is, whenever it is possible to deduce the Basic Service from a call set up, subscription check shall be performed at the granularity of that particular Basic Service or the group to which it belongs.
TeleServices
3GPP TS 22.003 [6] lists the TeleServices, each of them with a specific "TS number". These may be provided to subscribers individually or combined, to the operators’ discretion, however TS 12 (Emergency calls) and TS 23 (CBS) are not subscribable. But, as for Bearer Services, networks shall be able to handle subscription checking at the granularity of individual TeleServices.
Table 2 summarizes the basis on which a successful subscription checking will result. It also describes on which basis Supplementary Service handling for a given call set-up should be performed.
Table 2
|
Set Up |
Subscription Check |
SS handling |
|
BS 20 |
BS 20 |
BS Group 2x |
|
BS 30 |
BS 30 |
BS Group 3x |
|
TS 11 |
TS 11, TS Group 1x or TS Group All |
TS Group 1x |
|
TS 12 |
N.A. |
|
|
TS 21 |
TS 21, TS Group 2x or TS Group All |
TS Group 2x |
|
TS 22 |
TS 22, TS Group 2x or TS Group All |
TS Group 2x |
|
TS 23 |
N.A. |
|
|
TS 61 |
TS 61, TS Group 6x or TS Group All |
TS Group 6x |
|
TS 62 |
TS 61, 62, Group 6x or TS Group All |
TS Group 6x |
|
TS 91 |
TS 91, TS Group 9x or TS Group All |
TS Group 9x |
|
TS 92 |
TS 92, TS Group 9x or TS Group All |
TS Group 9x |
|
Legend: – set-up: The Basic Service which is set up for the call; – subscription check: Required VLR or HLR data for successful subscription check; – SS handling: Against which VLR or HLR data SS handling should be performed. For example; a call set-up indicating BS61 and Asynchronous mode should be treated for SS purposes in |
||
When TS61 is requested in a call set-up and the subscription check for TS61 is negative, but a subscription check for TS62 is positive, then the call shall proceed according to the TS 22.003 [6]and TS 27.001 [8]. If a subscription check for both TS61 and TS62 is negative, then the call shall be released.
4.2 Subscription checking for Supplementary Services
This is described in 3GPP TS 22.004 [7].
Annex A (normative):
List of definition of attributes and values used for bearer services