Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 22.001  Word version:  16.0.1

Top   Top   None   None   Next
0…   A…


0  ScopeWord‑p. 6

The present document covers the definition of the circuit telecommunication services supported by a PLMN. The purpose of the present document is to provide a method for the characterization and the description of these telecommunication services.
TS 22.101 describes overall service principles of a PLMN.

0.1  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.
TR 21.905: "Vocabulary for 3GPP Specifications".
ITU-T Recommendation I.221: "Common specific characteristics of services".
ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic reference model: The basic model".
TS 22.101: "Service Principles".
TS 22.002: "Bearer services supported by a PLMN".
TS 22.003: "Teleservices supported by a PLMN".
TS 22.004: "General on Supplementary Services".
TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
TS 22.030: "Man-Machine Interface (MMI) of the User equipment (MS)".
TS 22.081: "Line Identification Supplementary Services; Stage 1".
TS 22.135: "Multicall; Stage 1".
TS 24.008: "Mobile radio interface layer 3 specification".
TS 22.011: "Service accessibility".
TS 23.003: "Numbering, addressing and identification".

0.2  Abbreviations

Abbreviations used in the present document are listed in TR 21.905.

1  Framework for the description of telecommunication servicesWord‑p. 7

1.1  The attribute method of characterization of circuit telecommunication services

This characterization is made by using a set of attributes. A telecommunication service attribute is a specific characteristic of that service whole values distinguish it from other telecommunication services. Particular values are assigned to each attribute when a given telecommunication service is described and defined.
A list of definitions of attributes and values used for bearer services and teleservices is contained in, respectively, Annex A and Annex B.

2  Description of circuit telecommunication services by the attribute method

2.1  General

Telecommunication services are described by attributes which define service characteristics as they apply at a given reference point where the customer accesses the service. The description of a telecommunication service by the method of attributes is composed of:
  • technical attributes as seen by the customer; and
  • other attributes associated with the service provision, e.g. operational and commercial attributes.

2.2  Categorisation of telecommunication services

The concepts introduced in the present document are illustrated in Table 1.
Basic Bearer ServiceBasic Bearer service +
supplementary services
Basic TeleserviceBasic Teleservice +
supplementary service

3  Characterization of circuit telecommunication services

3.1  General

A telecommunication service supported by a PLMN is characterized and described by service attributes.
There are two groups of service attributes applicable to user information flow:
  • low layer attributes;
  • high layer attributes.
Bearer services are characterized only by low layer attributes. Teleservices are characterized by both low layer attributes and high layer attributes.
The basic characteristics of a telecommunication service are described by the basic service attributes.
The additional characteristics associated with a supplementary service which modify or supplement a basic telecommunication service are described in Specification TS 22.004.

3.2  Bearer servicesWord‑p. 8

Bearer services are characterized by a set of low layer attributes in Specification TS 22.002. These attributes are classified into four categories:
  • information transfer attributes;
  • access attributes;
  • interworking attributes;
  • general attributes, including operational and commercial attributes.
The bearer capability defines the technical features of a bearer service as they appear to the user at the appropriate access point. For the time being, the bearer capability is characterized by information transfer, access and interworking attributes. A bearer capability is associated with every bearer service.

3.3  Teleservices

Circuit teleservices provide the full capacity for communication by means of terminals and network functions and possibly functions provided by dedicated centres.
Circuit teleservices are specified in TS 22.003. Teleservices are characterized by a set of low layer attributes, a set of high layer attributes and operational and commercial attributes.
Low layer attributes are those used to characterize the bearer capability. High layer attributes are used in Specification TS 22.003 to describe high layer (i.e. layer 4-7) information transfer related characteristics. They refer to functions and protocols of layers 4-7 in the ITU-T Recommendation X.200 framework which are concerned with the transfer, storage and processing of user messages (provided by a subscriber's terminal, a retrieval centre or a network service centre).
Therefore, not all attributes can be applied directly at the user to terminal interface as they represent two kinds of features, the bearer capability and the terminal features, that are not directly perceived by the user.

4  Provision of telecommunication services

Specifications TS 22.101 and TS 22.011 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 ServicesWord‑p. 9

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 TS 27.001. 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 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.
3GPP TS 22.003 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.
Set Up Subscription Check SS handling
BS 20BS 20BS Group 2x
BS 30BS 30BS Group 3x
TS 11TS 11, TS Group 1x or TS Group AllTS Group 1x
TS 12N.A.
TS 21TS 21, TS Group 2x or TS Group AllTS Group 2x
TS 22TS 22, TS Group 2x or TS Group AllTS Group 2x
TS 23N.A.
TS 61TS 61, TS Group 6x or TS Group AllTS Group 6x
TS 62TS 61, 62, Group 6x or TS Group AllTS Group 6x
TS 91TS 91, TS Group 9x or TS Group AllTS Group 9x
TS 92TS 92, TS Group 9x or TS Group AllTS Group 9x
  • 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 accordance with the SS-data stored against BS group 2x.
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 and TS 27.001. If a subscription check for both TS61 and TS62 is negative, then the call shall be released.

4.2  Subscription checking for Supplementary ServicesWord‑p. 10

This is described in TS 22.004.

Up   Top   ToC