Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 24.085
Closed User Group (CUG)
Supplementary Service

3GPP‑Page   ETSI‑search   CONTENT↓
V18.0.0 (PDF)  2024/03  … p.
V17.0.0  2022/03  12 p.
V16.0.0  2020/06  12 p.
V15.0.0  2018/06  12 p.
V14.0.0  2017/03  12 p.
V13.0.0  2015/12  12 p.
V12.0.0  2014/09  12 p.
V11.0.0  2012/09  12 p.
V10.0.0  2011/04  12 p.
V9.0.0  2009/12  12 p.
V8.0.0  2008/12  12 p.
V7.0.0  2007/07  12 p.
V6.0.0  2005/01  12 p.
V5.0.0  2002/06  12 p.
V4.0.1  2002/06  12 p.
V3.0.0  1999/04  13 p.
GSM Rel-98 v7.0.0  1999/06  12 p.
GSM Rel-97 v6.0.0  1998/10  12 p.
GSM Rel-96 v5.0.0  1996/10  13 p.
GSM Phase-2 v4.1.1  1996/05  14 p.
Rapporteur:
Mr. Wiehe, Ulrich
Nokia Solutions & Networks (S)

Content for  TS 24.085  Word version:  17.0.0

Here   Top

0  Scope  p. 5

This Technical Specification (TS) for Mobile communications specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of community of interest supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats coding for the supplementary services.
Definitions and descriptions of supplementary services are given in TS 22.004 and 3GP TSP 22.08x and 3GPP TS 22.09x-series. TS 22.085 is related to the community of interest supplementary services.
Technical realization of supplementary services is described in technical specifications TS 23.011 and 3GPP TS 23.08x and 3GPP TS 23.09x-series. TS 23.085 is related to the community of interest supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
Signalling interworking for supplementary services between TS 29.002 and TS 24.008 and between TS 29.002 and TS 24.080 is defined in TS 29.011.
The following supplementary services belong to the community of interest supplementary services and are described in this TS:
Up

0.1  References  p. 5

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.004: "General on supplementary services".
[3]
TS 22.081: "Line identification Supplementary Services - Stage 1".
[4]
TS 22.082: "Call Forwarding (CF) Supplementary Services - Stage 1".
[5]
TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1".
[6]
TS 22.084: "Multi Party (MPTY) Supplementary Services - Stage 1".
[7]
TS 22.085: "Closed User Group (CUG) Supplementary Services - Stage 1".
[8]
TS 22.086: "Advice of Charge (AoC) Supplementary Services - Stage 1".
[9]
TS 22.087: "User-to-User Signalling (UUS) Service description - Stage 1".
[10]
TS 22.088: "Call Barring (CB) Supplementary Services - Stage 1".
[11]
TS 22.090: "Unstructured Supplementary Service Data (USSD) - Stage 1".
[12]
TS 23.002: "Network architecture".
[13]
TS 23.011: "Technical realization of supplementary services".
[14]
TS 23.081: "Line identification supplementary services - Stage 2".
[15]
TS 23.082: "Call Forwarding (CF) supplementary services - Stage 2".
[16]
TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2".
[17]
TS 23.084: "Multi Party (MPTY) supplementary services - Stage 2".
[18]
TS 23.085: "Closed User Group (CUG) supplementary services - Stage 2".
[19]
TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2".
[20]
TS 23.088: "Call Barring (CB) supplementary services - Stage 2".
[21]
TS 23.090: "Unstructured supplementary services operation - Stage 2".
[22]
TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) Access Reference Configuration".
[23]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[24]
TS 24.008: "Mobile radio interface layer 3 specification".
[25]
TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General aspects".
[26]
TS 24.080: "Mobile radio interface layer 3 supplementary services specification; Formats and coding".
[27]
TS 29.002: "Mobile Application Part (MAP) specification".
[28]
TS 29.011: "Signalling interworking for supplementary services".
Up

0.2  Abbreviations  p. 6

Abbreviations used in this TS are listed in TR 21.905.

1  Closed User Group (CUG)  p. 6

1.1  Normal operation  p. 6

1.1.1  Mobile originated CUG calls  p. 6

1.1.1.1  Successful operation  p. 6

CUG calls may be invoked Implicitly or Explicitly by the calling user.
In the case of Implicit invocation, no CUG information is provided by the user in the call set-up request and a default attribute of CUG is invoked. Normal call establishment procedures are followed over the radio interface and no CUG signalling is required.
In the case of Explicit CUG invocation, CUG information is provided by the user and is included in the SETUP message using the ForwardCUG-Info operation (see Figure 1.1). User provided CUG information may consist of any combination of the following parameters:
  • CUG Index;
  • Suppress Preferential CUG indicator;
  • Suppress OA indicator.
Copy of original 3GPP image for 3GPP TS 24.085, Fig. 1.1: Transfer of CUG information during CUG call set-up
Figure 1.1: Transfer of CUG information during CUG call set-up
(⇒ copy of original 3GPP image)
Up
If the network received a non-zero SS Screening indicator from the calling user's mobile station, the network may optionally indicate to the MS that a CUG has been invoked for a call (see Figure 1.2). When a CUG Index is received from the VLR the MSC shall send it immediately to the MS in a FACILITY or CALL PROCEEDING message. If the network did not receive a non-zero SS Screening indicator from the calling user's mobile station, it shall not send this notification.
Copy of original 3GPP image for 3GPP TS 24.085, Fig. 1.2: Indication of CUG invocation to the calling subscriber by the network
Figure 1.2: Indication of CUG invocation to the calling subscriber by the network
(⇒ copy of original 3GPP image)
Up

1.1.1.2  Unsuccessful operation  p. 7

When an attempted CUG call is rejected for CUG related reasons, the mobile station is provided with an indication of the reason for failure.
The indication is passed to the calling MS in the first clearing message. The indication may be given in one of two ways:
  • Diagnostics information in cause value #29 "Facility Rejected";
  • A standard call control cause value.
Diagnostics are used when the rejection is generated locally (the serving VLR has rejected the call), or if they are provided in a cause value from a remote network node (see Figure 1.3). Table 1.1 gives the diagnostics information for each potential local rejection case.
A CUG rejection from a remote network node is generally indicated using a standard (CUG related) call control cause value contained in an ISUP clearing message. These cause values are passed to the mobile station in the appropriate radio interface clearing message (see Figure 1.4). Table 1.2 gives the cause values in each potential remote rejection case.
All CUG related call rejection cases are defined in TS 23.085. Cause values are defined in TS 24.008 and diagnostics in TS 24.080.
Copy of original 3GPP image for 3GPP TS 24.085, Fig. 1.3: Indication of local CUG call rejection
Figure 1.3: Indication of local CUG call rejection
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 24.085, Fig. 1.4: Indication of remote CUG call rejection
Figure 1.4: Indication of remote CUG call rejection
(⇒ copy of original 3GPP image)
Up
Reason for rejection
See TS 23.085 		Facility Rejected #29
Diagnostic Field
(Diagnostics)
Outgoing calls barred within the CUGOutgoing calls barred within the CUG
Inconsistent access info - No CUG SelectedNo CUG Selected
Unknown CUG IndexUnknown CUG Index
Inconsistent access info -
Index incompatible with requested basic service		Index incompatible with requested basic service
Reason for rejection
See TS 23.085 		Cause Information Element
(cause value)
Called party supplementary service interaction violationFacility Rejected #29
Diagnostic = CUG call failure,
unspecified
Incompatible Destination
(see note)		Facility Rejected #29
Diagnostic = CUG call failure,
unspecified
Incoming calls barred within the CUGIncoming calls barred within the CUG #55
Interlock mismatchUser not a member of CUG #87
Requested basic service violates CUG constraintsFacility Rejected #29
Up

1.1.2  Mobile terminated calls  p. 8

If the network received a non-zero SS Screening indicator from the called user's mobile station, when a CUG call is terminated by a CUG subscriber the Index associated with the invoked CUG may be passed to the mobile station (see Figure 1.5). If the network did not receive a non-zero SS Screening indicator from the called user's mobile station, it shall not send this notification.
Copy of original 3GPP image for 3GPP TS 24.085, Fig. 1.5: Presentation of the CUG Index to a CUG subscriber during reception of a CUG call
Figure 1.5: Presentation of the CUG Index to a CUG subscriber during reception of a CUG call
(⇒ copy of original 3GPP image)
Up

1.2  Activation, deactivation, interrogation, registration and erasure  p. 8

Activation, deactivation, interrogation, registration and erasure of the supplementary service closed user group are not applicable.

A (Normative)  CUG rejection cause value mapping  p. 9

Table A.1 indicates how MAP, ISUP and TS 24.008 cause values are mapped to enable a rejection indication to be passed from the remote rejecting node to the calling user.
GSM MAP CUG reject cause value CCITT ISUP cause value TS 24.008 cause value
calledPartySupplementary-ServiceInteractionViolation#29 Facility Rejected
Diagnostic = IC
(see note 1)		#29 Facility Rejected
Diagnostic = CUG call failure,
unspecified
incomingCallsBarredWithinCUG#55 I/C calls barred
within CUG		#55 I/C calls barred
within CUG
subscriberNotMemberOfCUG#87 User not member
of CUG		#87 User not member
of CUG
requestedBasicService-ViolatesCUGConstraints#29 Facility Rejected
(see note 2)		#29Facility Rejected
(no diagnostic)
Up

$  Change history  p. 10

Up   Top