ETSI TS 123 085 V14.0.0 (2017-04)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Closed User Group (CUG) supplementary service; Stage 2 (3GPP TS 23.085 version 14.0.0 Release 14)

RTS/TSGC-0423085ve00

General Information

• Status: Published
• Publication Date: 02-Apr-2017
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Completion
• Completion Date: 03-Apr-2017

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
Closed User Group (CUG) supplementary service;
Stage 2
(3GPP TS 23.085 version 14.0.0 Release 14)

R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
3GPP TS 23.085 version 14.0.0 Release 14 1 ETSI TS 123 085 V14.0.0 (2017-04)

Reference
RTS/TSGC-0423085ve00
Keywords
GSM,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 23.085 version 14.0.0 Release 14 2 ETSI TS 123 085 V14.0.0 (2017-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
rd
This Technical Specification (TS) has been produced by the ETSI 3 Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
3GPP TS 23.085 version 14.0.0 Release 14 3 ETSI TS 123 085 V14.0.0 (2017-04)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
0 Scope . 5
0.1 References . 5
0.2 Definitions . 5
0.3 Abbreviations . 6
1 Closed user group (CUG) . 6
1.1 Handling of Closed User Group . 6
1.1.1 Mobile Originated (MO) CUG call handling . 6
1.1.1.1 MO CUG call handling at the MSC . 7
1.1.1.2 MO CUG call handling at the VLR . 7
1.1.2 Mobile Terminated (MT) CUG call handling . 7
1.1.2.1 MT CUG handling at the GMSC . 7
1.1.2.2 MT CUG handling functions at the HLR . 7
1.1.2.3 MT CUG handling functions at the MSC . 8
1.1.2.4 MT CUG handling functions at the VLR . 8
1.1.3 CUG subscriber roaming requirements. 8
1.1.4 CUG interworking requirements . 9
1.1.4.1 Non-CUG GSM PLMNs . 9
1.1.4.2 Interworking to Non-CUG networks . 9
1.1.5 Supplementary service interactions . 9
1.1.5.1 Interaction with Call Forwarding . 9
1.1.5.2 Interaction with call waiting . 9
1.1.5.3 Interaction with Anonymous Call Rejection . 10
1.2 Functions and information flows . 10
1.2.1 Functions . 10
1.2.2 Information flows . 12
1.3 Information stored in the HLR . 18
1.4 Information stored in the VLR . 19
1.5 Handover . 19
1.6 Cross phase compatibility . 20
1.6.1 MSC, VLR only support phase 1 . 20
1.6.2 GMSC only supports phase 1 . 20
Annex A (informative): Change history . 21
History . 22

ETSI
3GPP TS 23.085 version 14.0.0 Release 14 4 ETSI TS 123 085 V14.0.0 (2017-04)
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 23.085 version 14.0.0 Release 14 5 ETSI TS 123 085 V14.0.0 (2017-04)
0 Scope
The present document gives the stage 2 description of the closed user group supplementary service.
The community of interest supplementary service defined is:
- closed user group (CUG) (see clause 1).
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.
[1] 3GPP TR 21.905: " Vocabulary for 3GPP Specifications ".
[2] 3GPP TS 22.085: "Closed User Group (CUG) Supplementary Services; Stage 1".
[3] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2".
0.2 Definitions
CUG terminology defined in 3GPP TS 22. 085 [2] is applicable to the present document. In addition, the following
definitions apply.
CUG Authorisation Functions: Checks performed by the network to ensure that the integrity of a CUG related call is
guarantied. CUG calls are rejected if they do not meet the criteria of these checks.
CUG call: CUG call, in signalling terms, is a call where CUG information is passed from the originating switching
entity to the destination entity.
CUG Index: Code used to select a CUG for an outgoing call, or to indicate an incoming CUG call. Indices are passed
between the user and the network and have significance only within the context of a users subscription.
CUG Interlock Code: Code which uniquely identifies a CUG within a network. The Interlock code is passed from the
point of origin to the destination in a CUG call to identify the CUG which has been invoked.
CUG Related Call Barring: CUG related call barring is call barring applied to a CUG subscriber by the home network
when roaming in a non-CUG network. The user is unable to remove CUG related call barring.
Explicit CUG Invocation: Explicit CUG invocation is where a calling user attempts to invoke a CUG by passing CUG
information to the network in a call request.
Implicit CUG Invocation: Implicit CUG invocation is where the user invokes some default characteristic of a CUG
without providing any CUG information in the call request.
Normal Call: Normal call in the context of this CUG TS is a call established from a CUG subscriber where no CUG
information is passed from the originating switching entity to the destination entity.
Outgoing Access Indicator: Indication passed from the point of origin to the destination in a CUG call to indicate that
the calling user has subscribed to the Outgoing Access inter-CUG accessibility subscription option.
ETSI
3GPP TS 23.085 version 14.0.0 Release 14 6 ETSI TS 123 085 V14.0.0 (2017-04)
0.3 Abbreviations
In addition to those listed below abbreviations used in the present document are listed in 3GPP TR 21.905 [1].
For the purposes of the present document, the following abbreviations apply:
BS Basic Service
CI CUG Index
CUG Closed User Group
IA Incoming Access
IC Interlock Code
IC(pref) Interlock code of the preferential CUG
IC+OA Interlock Code and Outgoing Access indicator.
ICB Incoming Calls Barred within the CUG
OA Outgoing Access
OCB Outgoing Calls Barred within the CUG
Pref CUG Preferential CUG
SOA Suppress OA
SPC Suppress Preferential CUG
1 Closed user group (CUG)
The responsibilities of GSM network nodes with respect to CUG are described in the CUG handling clause. The
Functions subclause 1.2.1 describes the CUG service logic and how CUG information is used. The flow of CUG
information in various call cases is shown in the Information Flows subclause 1.2.2.
1.1 Handling of Closed User Group
A GSM PLMN supporting the CUG supplementary service must guarantee the integrity of any CUG which it handles.
It is not however mandatory for a PLMN to support the CUG supplementary service.
A CUG is uniquely identified within a network by a CUG Interlock Code. The Interlock Code is transferred between
terrestrial network entities to indicate a CUG call.
A user identifies a CUG by a CUG Index. A CUG Index is used to select or indicate the use of a specific CUG in
relation to a call. The index is locally transferred between the mobile station and serving VLR and only has significance
within the context of an individual subscription.
1.1.1 Mobile Originated (MO) CUG call handling
A CUG subscriber may invoke a CUG by providing the network with a CUG Index at call establishment. This is termed
Explicit CUG invocation. Alternatively, if the subscription allows, some default characteristic of a CUG may be
invoked automatically if no CUG information is provided. This is termed Implicit CUG invocation. The network may
optionally indicate the use of an implicitly invoked CUG to the calling user.
A CUG subscriber may suppress certain CUG attributes by providing suppression indicators during call set-up. The
provision of such suppression indicators results in explicit CUG invocation.
Any non-CUG related Call Barring supplementary service requirements shall be discharged before CUG authorisation
occurs.
ETSI
3GPP TS 23.085 version 14.0.0 Release 14 7 ETSI TS 123 085 V14.0.0 (2017-04)
1.1.1.1 MO CUG call handling at the MSC
The MSC shall pass any user provided CUG information to the VLR at call establishment.
If an Interlock Code, or Interlock code with Outgoing Access indicator, is received from the VLR the MSC shall
establish a CUG call with the destination network using this information. If a CUG Index is received from the VLR the
MSC shall pass this to the calling MS.
If the CUG call authorisation is unsuccessful the MSC shall pass an indication to the mobile station.
1.1.1.2 MO CUG call handling at the VLR
Authorisation of a MO CUG call is performed by the serving VLR. Authorisation is determined by the information
provided by the user, the subscription information stored in the VLR and the MO CUG call authorisation function, see
Functions clause.
Successful authorisation may result in a normal MO call (call without CUG information transferred to the called party)
or a MO CUG call (call with CUG information transferred to the called party).
When a CUG call is to be made the VLR passes CUG information to the MSC to be used in the call establishment.
Note, the VLR may optionally pass a CUG Index to the MSC (to be passed to the calling user) to indicate that a CUG
has been implicitly invoked. This parameter is not passed to the call destination.
In the case of a normal call, no CUG information is passed to the MSC and the call is established normally.
On authorisation failure the VLR shall reject the call providing a suitable indication to the serving MSC which is passed
to the calling party.
1.1.2 Mobile Terminated (MT) CUG call handling
The terminating network is responsible for enforcing the integrity of a CUG related call. The terminating network must
therefore ensure that the calling party attributes and the called party subscription meet CUG restrictions. The
terminating network provides the called user with an indication of an incoming CUG call.
Non-CUG related Call Barring supplementary service requirements are discharged before CUG authorisations. Call
forwarding requirements are discharged after CUG authorisations.
1.1.2.1 MT CUG handling at the GMSC
The GMSC shall pass any CUG information contained in an incoming call establishment message to the HLR in the
routing enquiry.
The GMSC shall continue the call establishment using the CUG information received from the HLR rather than that
which was initially received. Note, in rare circumstances the HLR may discard CUG parameters, see the Call
Forwarding interaction.
If a CUG call fails the GMSC shall return an indication to the originating network.
1.1.2.2 MT CUG handling functions at the HLR
Authorisation of a MT CUG call is performed at the called parties HLR. Authorisation is determined by the information
received in the call establishment signalling, the called party subscription information stored in the HLR, and the MT
CUG call authorisation function, see Functions clause.
On successful authorisation, the HLR supplies the GMSC with CUG information for the continuation of the call
establishment. On unsuccessful authorisations the HLR rejects the call supplying an indication of the reason for failure.
ETSI
3GPP TS 23.085 version 14.0.0 Release 14 8 ETSI TS 123 085 V14.0.0 (2017-04)
1.1.2.3 MT CUG handling functions at the MSC
The MSC shall pass any CUG related information received in incoming call establishment signalling to the VLR.
If the VLR returns CUG information to the serving MSC in response, the MSC shall pass the information to the called
party in the call set-up signalling.
If the CUG call is rejected by the VLR (due to the call forwarding interaction) the MSC shall return an indication to the
originating network.
1.1.2.4 MT CUG handling functions at the VLR
When the VLR receives an incoming call enquiry for a CUG subscriber, it shall attempt to provide a CUG call
indication to the called party. The indication is sent depending on the attributes of the incoming call and the called
parties subscription, as shown in table 1.1. The indication is achieved by sending the CUG Index, associated with the
Interlock Code of the invoked CUG, to the called user.
Table 1.1: CUG Index provision at terminating VLR
┌──────────┬─────────╥───────────────────────────────────────┐
│     │     ║    Called party subscription   │
│ Calling │     ╟────────────────────────────┬──────────┤
│  Party │Interlock ║    CUG subscriber    │     │
│  CUG  │ check ╟────────────┬───────────────┤ Normal │
│ Infor- │     ║  No IA  │   IA    │subscriber │
│ mation │     ╟──────┬─────┼──────┬────────┤     │
│     │     ║No ICB │ ICB │No ICB │ ICB  │     │
╞══════════╪═════════╬══════╪═════╪══════╪════════╪══════════╡
│     │ Match ║Index │ - │Index │  -  │     │
│Interlock ├─────────╫──────┴─────┼──────┴────────┤  -   │
│     │ No Match ║   -   │   -    │     │
├──────────┼─────────╫──────┬─────┼──────┬────────┼──────────┤
│Interlock │ Match ║Index │ - │Index │No Index │     │
│+ Outgoing ├─────────╫──────┴─────┼──────┴────────┤ No Index │
│ Access │ No Match ║   -   │  No Index  │     │
├──────────┼─────────╫────────────┼───────────────┼──────────┤
│ No CUG │  -  ║   -   │  No Index  │ No Index │
│  Info. │     ║      │        │     │
└──────────┴─────────╨────────────┴───────────────┴──────────┘
NOTE: "-" = Not Applicable, this check is not performed since such calls are rejected by the called parties HLR.
1.1.3 CUG subscriber roaming requirements
Normal CUG restrictions apply to CUG subscribers when roaming in CUG supporting GSM PLMNs. Extra restrictions
(specified in GSM 02.85) are applied to CUG subscribers roaming in non-CUG GSM VPLMNs to preserve the integrity
of CUG.
These restrictions are applied by the application of call barring programmes which are not under user control. Such
restrictions only apply to a subscribers ability to make outgoing calls using CUG related basic services. Extra
restrictions are
...