id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 245
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
181 002
|
<empty>
|
TS
|
2.2.5
|
http://www.etsi.org/deliver/etsi_ts/181000_181099/181002/02.02.05_60/ts_181002v020205p.pdf
|
The present document defines the requirements for multimedia telephony services which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities. An important aspect of the Multimedia Telephony with PSTN/ISDN Simulation service is to provide PSTN/ISDN like services. Nevertheless the requirements are independent of the media that is used during the communication. The present document covers part of the transition from PSTN/ISDN to an NGN. Interconnection between the existing networks and a TISPAN NGN is also covered. The present document only provides requirements for services using IMS. Services provided by a TISPAN NGN to support legacy terminals and interfaces (PSTN/ISDN emulation) are defined in existing PSTN/ISDN documents. Requirements for PSTN/ISDN Emulation are out of the scope of the present document and are described in other documents. New NGN services are out of the scope of the present document and are described in other documents. The applicability of PSTN/ISDN simulation services to services other than Multimedia Telephony (e.g. instant messaging) is not defined. Some PSTN/ISDN simulation services (for example communication waiting) are clearly not applicable to some real-time communication services. The requirements in the present document are described from the user point of view to assist in the transition of phone services to IP multimedia services with a similar behaviour. The requirements do not take into account capabilities of existing protocols. The evolution or modifications to these protocols are beyond the scope of the present document.
|
170 016
|
Project MESA; Technical Specification Group - System; Functional Requirements Definition
|
TS
|
3.1.1
|
http://www.etsi.org/deliver/etsi_ts/170000_170099/170016/03.01.01_60/ts_170016v030101p.pdf
|
The present document give guidelines for the functional requirements required for a MESA system that is consistent with the Service Specification Group's Statement of Requirements (TS 170 001 [1]) and the Technical Specification Groups Network Architecture (MESA 70.015 [i.1]). The present document is intended to be the input into a gap analysis of existing standards and technologies with an ultimate goal to update the existing standards and technologies to be fully compliant with the functional requirements in the present document.
|
181 005
|
<empty>
|
TS
|
3.3.1
|
http://www.etsi.org/deliver/etsi_ts/181000_181099/181005/03.03.01_60/ts_181005v030301p.pdf
|
The present document specifies network requirements in terms of service-related capabilities for TISPAN NGN. The present document places requirements for all TISPAN NGN Release 1 subsystems. The present document provides generic requirements for services and interoperability in TISPAN NGN in terms of the capabilities for a network or networks. Requirements on service-related subsystems provide sufficient detail for architecture, networking requirements and protocols to be specified. Requirements on service independent subsystems are contained within the service-related subsystem requirements. Specific service requirements may be contained in other documents, as identified in the present document, and by other documents referencing the present document. The present document does not define services, only capabilities and requirements. The present document does not place requirements on terminals or other customer-owned equipment. The present document specifies the service-related requirements that are used to determine the network architecture, requirements and control protocols for a network interface to a customer environment. NOTE: The present document uses the term "NGN" only in the context of TISPAN.
|
183 007
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/183000_183099/183007/02.00.00_60/ts_183007v020000p.pdf
|
The present document specifies the stage three (protocol description) of the Originating Identification Presentation (OIP) simulation service and the Originating Identification Restriction (OIR) simulation services.
|
170 001
|
Project MESA; Service Specification Group - Services and Applications; Statement of Requirements (SoR)
|
TS
|
3.3.1
|
http://www.etsi.org/deliver/etsi_ts/170000_170099/170001/03.03.01_60/ts_170001v030301p.pdf
|
The present document describes the basis for a functional and technical specification and standards platform that can be installed as either a private system owned by government or a governmental/commercial partnership that provides priority service to public safety agencies and possibly secondary service to other commercial clients. It is envisaged that the Project MESA specifications will define robust management and control systems to ensure secure and reliable operational capabilities for the public safety and public security users worldwide. The present document reflects the requirements of public service and public safety agencies to have priority service and system restoration, extremely reliable service, and ubiquitous coverage within a user's defined service area.
|
181 002
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services
|
TS
|
1.2.10
|
http://www.etsi.org/deliver/etsi_ts/181000_181099/181002/01.02.10_60/ts_181002v010210p.pdf
|
The present document defines the requirements for multimedia telephony services which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities. An important aspect of the Multimedia Telephony with PSTN/ISDN Simulation service is to provide PSTN/ISDN like services. Nevertheless the requirements are independent of the media that is used during the communication. The present document covers part of the transition from PSTN/ISDN to an NGN. Interconnection between the existing networks and a TISPAN NGN is also covered. The present document only provides requirements for services using IMS. Services provided by a TISPAN NGN to support legacy terminals and interfaces (PSTN/ISDN emulation) are defined in existing PSTN/ISDN documents. Requirements for PSTN/ISDN Emulation are out of the scope of the present document and are described in other documents. New NGN services are out of the scope of the present document and are described in other documents. The applicability of PSTN/ISDN simulation services to services other than Multimedia Telephony (e.g. instant messaging) is not defined. Some PSTN/ISDN simulation services (for example communication waiting) are clearly not applicable to some real-time communication services. The requirements in the present document are described from the user point of view to assist in the transition of phone services to IP multimedia services with a similar behaviour. The requirements do not take into account capabilities of existing protocols. The evolution or modifications to these protocols are beyond the scope of the present document.
|
138 521-2
|
<empty>
|
TS
|
18.7.0
|
http://www.etsi.org/deliver/etsi_ts/138500_138599/13852102/18.07.00_60/ts_13852102v180700p.pdf
|
...................................................................................................................................................... 18
|
138 521-1
|
<empty>
|
TS
|
18.6.0
|
http://www.etsi.org/deliver/etsi_ts/138500_138599/13852101/18.06.00_60/ts_13852101v180600p.pdf
|
.............................................................................................................................................. 25
|
133 120
|
Universal Mobile Telecommunications System (UMTS); 3G Security; Security Principles and Objectives (3G TS 33.120 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/133100_133199/133120/03.00.00_60/ts_133120v030000p.pdf
|
........................................................................................................................................................5
|
133 106
|
Universal Mobile Telecommunications System (UMTS); 3G Security; Lawful Interception Requirements (3G TS 33.106 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/133100_133199/133106/03.01.00_60/ts_133106v030100p.pdf
|
........................................................................................................................................................5
|
132 106-8
|
Universal Mobile Telecommunications System (UMTS); Telecommunication Management; Configuration Management; Part 8: Name convention for Managed Objects (3G TS 32.106-8 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/132100_132199/13210608/03.02.00_60/ts_13210608v030200p.pdf
|
........................................................................................................................................................6
|
132 102
|
Universal Mobile Telecommunications System (UMTS); 3G Telecom Management architecture (3G TS 32.102 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/132100_132199/132102/03.02.00_60/ts_132102v030200p.pdf
|
........................................................................................................................................................6
|
129 119
|
Universal Mobile Telecommunications System (UMTS); GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) (3G TS 29.119 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/129100_129199/129119/03.00.00_60/ts_129119v030000p.pdf
|
........................................................................................................................................................5
|
129 006
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Interworking between the Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services (3G TS 29.006 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/129000_129099/129006/03.00.00_60/ts_129006v030000p.pdf
|
........................................................................................................................................................5
|
132 111-4
|
Universal Mobile Telecommunications System (UMTS); Telecommunication Management; Fault Management; Part 4: Alarm Integration Reference Point: CMIP solution set (3G TS 32.111-4 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/132100_132199/13211104/03.02.00_60/ts_13211104v030200p.pdf
|
........................................................................................................................................................5
|
126 092
|
Universal Mobile Telecommunications System (UMTS); Mandatory Speech Codec speech processing functions AMR Speech Codec - Comfort noise aspects (3G TS 26.092 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/126000_126099/126092/03.00.01_60/ts_126092v030001p.pdf
|
........................................................................................................................................................5
|
132 106-1
|
Universal Mobile Telecommunications System (UMTS); Telecommunication Management; Configuration Management; Part 1: 3G Configuration Management: Concept and Requirements (3G TS 32.106-1 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/132100_132199/13210601/03.01.00_60/ts_13210601v030100p.pdf
|
........................................................................................................................................................6
|
124 087
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); User-to-User Signalling (UUS) Supplementary Service - Stage3 (3G TS 24.087 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124087/03.00.00_60/ts_124087v030000p.pdf
|
........................................................................................................................................................5
|
126 094
|
Universal Mobile Telecommunications System (UMTS); Mandatory Speech Codec speech processing functions AMR speech codec; Voice Activity Detector (VAD) (3G TS 26.094 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/126000_126099/126094/03.00.00_60/ts_126094v030000p.pdf
|
........................................................................................................................................................5
|
125 442
|
Universal Mobile Telecommunications System (UMTS); UTRAN Implementation Specific O&M Transport (3G TS 25.442 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/125400_125499/125442/03.01.00_60/ts_125442v030100p.pdf
|
........................................................................................................................................................5
|
126 091
|
Universal Mobile Telecommunications System (UMTS); Mandatory Speech Codec speech processing functions AMR speech codec - Error concealment of lost frames (3G TS 26.091 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/126000_126099/126091/03.01.00_60/ts_126091v030100p.pdf
|
........................................................................................................................................................5
|
129 011
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Signalling interworking for supplementary services (3G TS 29.011 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/129000_129099/129011/03.00.00_60/ts_129011v030000p.pdf
|
........................................................................................................................................................6
|
126 071
|
Universal Mobile Telecommunications System (UMTS); Mandatory Speech Codec speech processing functions - AMR Speech Codec - General Description (3G TS 26.071 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/126000_126099/126071/03.00.01_60/ts_126071v030001p.pdf
|
........................................................................................................................................................5
|
124 091
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Explicit Call Transfer (ECT) supplementary service - Stage 3 (3G TS 24.091 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124091/03.00.00_60/ts_124091v030000p.pdf
|
........................................................................................................................................................5
|
124 085
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Closed User Group (CUG) supplementary service - Stage 3 (3G TS 24.085 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124085/03.00.00_60/ts_124085v030000p.pdf
|
This Technical Specification (TS) for Mobile communications specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) 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 GSM 04.10, the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.85 is related to the community of interest supplementary services. Technical realization of supplementary services is described in technical specifications GSM 03.11 and GSM 03.8x and 03.9x-series. GSM 03.85 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 GSM 04.07 and GSM 04.08. Signalling interworking for supplementary services between GSM 09.02 and GSM 04.08 and between GSM 09.02 and GSM 04.80 is defined in GSM 09.11. The following supplementary services belong to the community of interest supplementary services and are described in this TS: - Closed User Group (CUG) 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification Supplementary Services - Stage 1". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) Supplementary Services - Stage 1". [5] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". [6] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) Supplementary Services - Stage 1". ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 6 3G TS 24.085 version 3.0.0 [7] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) Supplementary Services - Stage 1". [8] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) Supplementary Services - Stage 1". [9] GSM 02.87: "Digital cellular telecommunications system. (Phase 2+); User-to-User Signalling (UUS) Service description - Stage 1". [10] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) Supplementary Services - Stage 1". [11] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data (USSD) - Stage 1". [12] GSM 03.02: "Digital cellular telecommunications system (Phase 2+); Network architecture". [13] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [14] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [15] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [16] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [17] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 2". [18] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [19] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [20] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [21] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [25] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [26] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [27] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [28] GSM 09.11: "Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services". ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 7 3G TS 24.085 version 3.0.0 0.2 Abbreviations Abbreviations used in this TS are listed in GSM 01.04. 1 Closed User Group (CUG) 1.1 Normal operation 1.1.1 Mobile originated CUG calls 1.1.1.1 Successful operation 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. NOTE: No more than one of each parameter may be included per call attempt. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ForwardCUG-Info (CUG-Index, SuppressPrefCUG, SuppressOA)) Figure 1.1: Transfer of CUG information during CUG call set-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. MS Network FACILITY/CALL PROCEEDING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CUG-Index)) Figure 1.2: Indication of CUG invocation to the calling subscriber by the network ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 8 3G TS 24.085 version 3.0.0 1.1.1.2 Unsuccessful operation 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 GSM 03.85. Cause values are defined in GSM 04.08 and diagnostics in GSM 04.80. NOTE: Annex A specifies the mapping of cause values between MAP, ISUP and GSM 04.08 for remotely generated CUG rejections. MS Network DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ .....Cause #29 (Facility Rejected (diagnostics))..... Figure 1.3: Indication of local CUG call rejection MS Network DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Cause Information Element (Cause Value) Figure 1.4: Indication of remote CUG call rejection Table 1.1: Use of diagnostic values for local CUG call failure indications Reason for rejection See GSM 03.85 Facility Rejected #29 Diagnostic Field (Diagnostics) Outgoing calls barred within the CUG Outgoing calls barred within the CUG Inconsistent access info - No CUG Selected No CUG Selected Unknown CUG Index Unknown CUG Index Inconsistent access info - Index incompatible with requested basic service Index incompatible with requested basic service ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 9 3G TS 24.085 version 3.0.0 Table 1.2: Use of cause values for remote CUG call failure indications Reason for rejection See GSM 03.85 Cause Information Element (cause value) Called party supplementary service interaction violation Facility Rejected #29 Diagnostic = CUG call failure, unspecified Incompatible Destination (see note) Facility Rejected #29 Diagnostic = CUG call failure, unspecified Incoming calls barred within the CUG Incoming calls barred within the CUG #55 Interlock mismatch User not a member of CUG #87 Requested basic service violates CUG constraints Facility Rejected #29 NOTE: In cases of interworking failures ETSI ISUP V2 clears the call with cause value #29 "Facility Rejected", Diagnostic = "Interlock Code". This is mapped to Facility Rejected with general diagnostic value "CUG call failure, unspecified" since the interlock code has no meaning for a mobile user. 1.1.2 Mobile terminated calls 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. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CUG-Index)) Figure 1.5: Presentation of the CUG Index to a CUG subscriber during reception of a CUG call 1.2 Activation, deactivation, interrogation, registration and erasure Activation, deactivation, interrogation, registration and erasure of the supplementary service closed user group are not applicable. ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 10 3G TS 24.085 version 3.0.0 Annex A (normative): CUG rejection cause value mapping Table A.1 indicates how MAP, ISUP and GSM 04.08 cause values are mapped to enable a rejection indication to be passed from the remote rejecting node to the calling user. Table A.1: Protocol mapping for CUG call rejection cause values GSM MAP CUG reject cause value CCITT ISUP cause value GSM 04.08 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) NOTE 1: There is no specific cause value in ISUP for this rejection case. Therefore it is proposed that Cause Value #29 "Facility Rejected" is used with the diagnostic equal to the interlock of the call. This approach has been used in ISUP for interworking problems. NOTE 2: There is no specific cause value in ISUP for this rejection case. It is therefore proposed to use cause value #29 "Facility Rejected" to indicate a general supplementary service failure. ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 11 3G TS 24.085 version 3.0.0 Annex B: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.85 6.0.0 Transferred to 3GPP CN1 CN#03 24.085 3.0.0 Approved at CN#03 ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 12 ETSI ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
124 088
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Barring (CB) Supplementary Service - Stage3 (3G TS 24.088 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124088/03.00.00_60/ts_124088v030000p.pdf
|
This Technical Specification (TS) specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. Technical realization of supplementary services is described in GSM 03.11, GSM 03.8x and GSM 03.9x-series. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call restriction supplementary services and are described in this specification: - Barring of outgoing calls (clause 1): - Barring of all outgoing calls (BAOC) (Barring program 1); - Barring of outgoing international calls (BOIC) (Barring program 2); - Barring of outgoing international calls EXCEPT those directed to the home PLMN country (BOIC-exHC) (Barring program 3). - Barring of incoming calls (clause 2): - Barring of all incoming calls (BAIC) (Barring program 1); - Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) (Barring program 2). 0.1 Normative references References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [4] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 7 3G TS 24.088 version 3.0.0 [5] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [6] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [7] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [8] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". 0.2 Abbreviations Abbreviations used in this specification are listed in GSM 01.04. 0.3 Cross phase compatibility For the following supplementary services, a number of changes exist between this specification and the protocol version 1 specification: - Barring of outgoing calls; - Barring of incoming calls. The main body of this specification assumes that all network entities comply with this version of the service. In each case an additional subclauses 1.7 and 2.7 defines the additional requirements for when one or more network entities or the MS complies with the protocol version 1 specifications for the supplementary service procedures. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 8 3G TS 24.088 version 3.0.0 1 Barring of outgoing calls 1.1 Normal operation When a barring program relating to outgoing calls is active and operative for a basic service, each call set up related to that basic service and not allowed by the barring program will be refused by the network. In this case a NotifySS operation containing the SS-Status indicating that a barring program relating to outgoing calls is currently active and operative will be sent to the served mobile subscriber in a clearing message (see figure 1.1). MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE 1: The SS-Code will be the common code for outgoing barring services. NOTE 2: $(CAMEL2)$ The DISCONNECT and RELEASE messages were introduced because of CAMEL Phase 2. Figure 1.1: Notification to the served mobile subscriber that barring of outgoing calls is active When a barring program is active (operative or quiescent), the ability of the served mobile subscriber to set up emergency calls is not affected, irrespective of the basic service to which the barring program applies. When a barring program relating to outgoing calls is active (operative or quiescent), the ability of the served mobile subscriber to receive calls is not affected. 1.2 Registration If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the subscriber has to register a call barring password at provision time. Furthermore the served mobile subscriber can change the call barring password by a registration procedure at any time. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to register a new call barring password will be denied. The procedure to register a new password is specified in GSM 04.10. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 9 3G TS 24.088 version 3.0.0 1.3 Activation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is activated for a basic service if the subscriber has requested so by means of an activation procedure for that basic service. If the subscriber does not indicate a specific basic service, the activation applies to all basic services. The subscriber may use the call barring password at activation (see figure 1.2). If the activation is successful, the service will be activated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is activated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been activated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the activation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to activate the service will be denied and the served mobile subscriber receives an error indication (see figure 1.3). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code will be one of the specific outgoing barring codes. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 1.2: Activation of a barring program ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 10 3G TS 24.088 version 3.0.0 1.4 Deactivation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is deactivated for a basic service if the subscriber has requested deactivation by means of a deactivation procedure for that basic service. The subscriber may use the call barring password at deactivation (see figure 1.3). The deactivation request of a barring program may specify the basic service. If the subscriber does not indicate a specific basic service, the deactivation applies to all basic services (see figure 1.3). If the deactivation is successful, the service will be deactivated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is deactivated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been deactivated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the deactivation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to deactivate the supplementary service will be denied and the served mobile subscriber receives an error indication (see figure 1.3). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific outgoing barring codes, the common code for the outgoing barring services, or the SS-Code for all call barring services. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 1.3: Deactivation of barring of outgoing calls ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 11 3G TS 24.088 version 3.0.0 1.5 Interrogation The interrogation procedure enables the mobile subscriber to obtain information about data stored in the PLMN. After having requested this procedure the network shall return a list of all basic service groups for which the service is active (see figure 1.4). If there is no basic service group for which the service is active, an SS-Status will be returned indicating that the service is "deactivated". MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (SS-Code)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode)) or RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific outgoing barring codes. Figure 1.4: Interrogation of a barring program 1.6 Invocation and erasure Invocation and erasure are not applicable to barring programs. 1.7 Cross phase compatibility 1.7.1 Network only supports GSM Phase 1 control of SS by the subscriber In this case there is no relevant cross phase compatibility problem. 1.7.2 MS only supports protocol version 1 control of SS by the subscriber In this case there is no relevant cross phase compatibility problem. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 12 3G TS 24.088 version 3.0.0 2 Barring of incoming calls 2.1 Normal operation When a barring program relating to incoming calls is active and operative for a basic service, each incoming call set-up related to that basic service and not allowed by the barring program will be refused by the network. In this case a NotifySS operation containing the SS-Status indicating that a barring program relating to incoming calls is currently active and operative will be sent to the calling mobile subscriber in a clearing message (see figure 2.1). MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common code for incoming barring services. Figure 2.1: Notification to the calling mobile subscriber that at the called subscriber side barring is active When barring of incoming calls is active (operative or quiescent), the ability of the served mobile subscriber to originate calls is not affected. 2.2 Registration If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the subscriber has to register a call barring password at provision time. Furthermore the served mobile subscriber can change the call barring password by a registration procedure at any time. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to register a new call barring password will be denied. The procedure to register a new password is specified in GSM 04.10. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 13 3G TS 24.088 version 3.0.0 2.3 Activation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is activated for a basic service if the subscriber has requested so by means of an activation procedure for that basic service. If the subscriber does not indicate a specific basic service, the activation applies to all basic services. The subscriber may use the call barring password at activation (see figure 2.2). If the activation is successful, the service will be activated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is activated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been activated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the activation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to activate the service will be denied and the served mobile subscriber receives an error indication (see figure 2.2). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code will be one of the specific incoming barring codes. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 2.2: Activation of a barring program ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 14 3G TS 24.088 version 3.0.0 2.4 Deactivation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is deactivated for a basic service if the subscriber has requested deactivation by means of a deactivation procedure for that basic service. The subscriber may use the call barring password at deactivation (see figure 2.3). If the deactivation is successful, the service will be deactivated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is deactivated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been deactivated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the deactivation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to deactivate the supplementary service will be denied and the served mobile subscriber receives an error indication (see figure 2.3). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific incoming barring codes, the common code for the incoming barring services, or the SS-Code for all call barring services. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 2.3: Deactivation of barring of incoming calls ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 15 3G TS 24.088 version 3.0.0 2.5 Interrogation The interrogation procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return a list of all basic service groups for which the service is active (see figure 2.4). If there is no basic service group for which the service is active, an SS-Status will be returned indicating that the service is "deactivated". MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (SS-Code)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode)) or RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific incoming barring codes. Figure 2.4: Interrogation of a barring program 2.6 Invocation and erasure Invocation and erasure are not applicable to barring programs. 2.7 Cross phase compatibility 2.7.1 Network only supports GSM Phase 1 control of SS by the subscriber In this case there is no relevant cross phase compatibility problem. 2.7.2 MS only supports protocol version 1 control of SS by the subscriber The NotifySS operation containing the SS-Status indicating that a barring program relating to incoming calls is currently active and operative shall be sent to the calling subscriber only in the RELEASE COMPLETE message, if the MS only supports GSM Phase 1. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 16 3G TS 24.088 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.88 6.0.1 Transferred to 3GPP CN1 CN#03 24.088 3.0.0 Approved at CN#03 ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 17 ETSI ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
125 432
|
Universal Mobile Telecommunications System (UMTS); UTRAN lub Interface: Signalling Transport (3G TS 25.432 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/125400_125499/125432/03.01.00_60/ts_125432v030100p.pdf
|
........................................................................................................................................................5
|
124 086
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Advice of Charge (AOC) supplementary services - Stage3 (3G TS 24.086 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124086/03.00.00_60/ts_124086v030000p.pdf
|
The present document specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of charging 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 GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.24 and 02.86 are related to the charging supplementary services. Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.86 is related to the charging supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the charging supplementary services and are described in the present document: - Advice of Charge (Information) (AoCI) (clause 1); - Advice of Charge (Charging) (AoCC) (clause 2). 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)". [4] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [5] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [6] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [7] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 6 3G TS 24.086 version 3.0.0 [8] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". [9] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 1". [10] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [11] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 1". [12] GSM 03.02: "Digital cellular telecommunications system (Phase 2+); Network architecture". [13] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [14] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [15] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [16] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [17] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [18] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [19] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [20] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [21] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [25] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [26] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 7 3G TS 24.086 version 3.0.0 1 Advice of Charge (Information) (AoCI) 1.1 Normal operation with successful outcome On every successful request for an applicable telecommunications service, the served Mobile Station (MS) will be provided with charging information. The network sends the Charge Advice Information (CAI) to the MS according to GSM 02.24, GSM 02.86 and GSM 03.86. With this information the MS is able to calculate the units associated with the requested service in real time. In the case where the served mobile is to be charged for multi party calls, separate processes within the MS are used to calculate units appropriate to each call. For unit calculation, each call is treated in the same way as a normal "two-party" call. Any change in the charging rate during a call may be indicated to the MS. 1.1.1 Call re-establishment When the MS detects a radio link failure, the Chargeable Duration (CDUR) shall be suspended. If a call re-establishment procedure is attempted, the MS shall resume the CDUR when: - an MM connection has been successfully completed; and - a TCH has been successfully seized in the appropriate mode. 1.1.2 MS originated call For an MS originated call, charging information is transferred to the MS as shown in figure 1.1. The charging information is acknowledged in a FACILITY message only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86. AoCI refers to the Advice of Charge (Information) service. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> etc. CONNECT/FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCI, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 1.1: Notification to the served mobile subscriber of the charging information in case of an originated call set up 1.1.3 MS terminated call For an MS terminated call, where required, charging information is transferred to the MS as shown in figure 1.2. The charging information is acknowledged only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 8 3G TS 24.086 version 3.0.0 MS Network CONNECT ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCI, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 1.2: Notification to the served mobile subscriber of the charging information in case of a terminated call set-up 1.1.4 Change of charging information To inform the MS of a change in charging information the procedure of figure 1.3 is performed. The charging information is acknowledged only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86. MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCI, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 1.3: Notification to the served mobile subscriber of a change in the charging information 1.2 Normal operation with unsuccessful outcome No signalling is performed by the network if a MS fails to acknowledge receipt of charging Information. 1.3 Activation, deactivation and invocation Activation, deactivation and invocation of the Advice of Charge (Information) supplementary service are not applicable. 1.4 Interrogation, registration and erasure Interrogation, registration and erasure of the Advice of Charge (Information) supplementary service are not applicable. 2 Advice of Charge (Charging) (AoCC) 2.1 Normal operation with successful outcome On every successful request for an applicable telecommunications service, the served MS will be provided with charging information. The network sends the Charge Advice Information (CAI) to the MS according to GSM 02.24, GSM 02.86 and GSM 03.86. With this information the MS is able to calculate the units associated with the requested service in real time. In the case where the served mobile is to be charged for multi party calls, separate processes within the MS are used to calculate units appropriate to each call. For unit calculation, each call is treated in the same way as a normal "two-party" call. Any change in the charging rate during a call may be indicated to the MS. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 9 3G TS 24.086 version 3.0.0 2.1.1 Call re-establishment When the MS detects a radio link failure, the Chargeable Duration (CDUR) shall be suspended. If a call re-establishment procedure is attempted, the MS shall resume the CDUR when: - an MM connection has been successfully completed; and - a TCH has been successfully seized in the appropriate mode. 2.1.2 MS originated call For an MS originated call, charging information is transferred to the MS as shown in figure 2.1. The charging information is acknowledged in a FACILITY message only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. AoCC refers to the Advice of Charge (Charging) service. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> etc. CONNECT/FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 2.1: Notification to the served mobile subscriber of the charging information in case of an originated call set up 2.1.3 MS terminated call For an MS terminated call, where required, charging information is transferred to the MS as shown in figure 2.2. The charging information is acknowledged only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. MS Network CONNECT ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 2.2: Notification to the served mobile subscriber of the charging information in case of a terminated call set up 2.1.4 Change of charging information To inform the MS of a change in charging information the procedure of figure 2.3 is performed. The charging information is acknowledged only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 10 3G TS 24.086 version 3.0.0 MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 2.3: Notification to the served mobile subscriber of a change in the charging information 2.2 Normal operation with unsuccessful outcome If timer T(AoC) (see GSM 03.86) expires before the Charge Advice Information is acknowledged, the network shall release the call. The MS and network shall act in accordance with GSM 04.08 network initiated call clearing procedures (see figure 2.4). MS Network DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ ....Cause #69 (Requested facility not implemented).... Figure 2.4: Network release due to unsuccessful operation of Advice of Charge (Charging) service 2.3 Accumulated Call Meter is equal to or greater than ACMmax If the change stored in the Accumulated Call Meter (ACM) is equal to or greater than the maximum value specified by ACMmax, then the MS shall initiate call clearing giving a specific cause value for this situation as indicated in figure 2.5. MS Network DISCONNECT ------------------------------------------------------------------------------------------------------------------------> ....Cause #68 (ACM equal to or greater than ACMmax).... Figure 2.5: Mobile station releases the call due to ACM being equal to or greater than ACMmax 2.4 Activation, deactivation and invocation Activation, deactivation and invocation of the Advice of Charge (Charging) supplementary service are not applicable. 2.5 Interrogation, registration and erasure Interrogation, registration and erasure of the Advice of Charge (Charging) supplementary service are not applicable. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 11 3G TS 24.086 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.86 6.0.0 Transferred to 3GPP CN1 CN#03 24.086 3.0.0 Approved at CN#03 ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 12 ETSI ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
124 090
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Unstructured Supplementary Service Data (USSD) - Stage 3 (3G TS 24.090 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124090/03.00.00_60/ts_124090v030000p.pdf
|
........................................................................................................................................................5
|
124 083
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3 (3G TS 24.083 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124083/03.00.00_60/ts_124083v030000p.pdf
|
The present document specifies the procedures used at the radio interface (Reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call completion supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.83 is related specially to call completion supplementary services. Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.83 is related specially to call completion supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call completion supplementary services and are described in the present document: - Call waiting (CW) (clause 1); - Call hold (HOLD) (clause 2). 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [5] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [6] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [7] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 6 3G TS 24.083 version 3.0.0 [8] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) supplementary services - Stage 1". [9] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [10] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 1". [11] GSM 02.91: "Digital cellular telecommunications system (Phase 2+); ECT supplementary services operation - Stage 1". [12] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [13] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [14] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [15] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [16] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [17] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [18] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [19] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [20] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [21] GSM 03.91: "Digital cellular telecommunications system (Phase 2+); Explicit Call Transfer (ECT) supplementary service - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [25] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [26] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [27] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 7 3G TS 24.083 version 3.0.0 1 Call Waiting (CW) 1.1 Waiting call indication and confirmation When this service is activated for the controlling subscriber B and the B-subscriber has calls only in states U10 (Active) or U26 (MO Modify) as defined in GSM 04.08, the arrival of an incoming call from subscriber C shall, if no other call is waiting be signalled to the mobile station B by a normal call indication. In that case the network and the mobile station shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) allocated to the waiting call and must not be the same as the transaction identifier (A-B) for the already existing call (see figure 1.1). In the CALL CONFIRMED message sent to the network the Cause information element shall be included with cause #17 "user busy" (see figure 1.1). When the ALERTING message is received by the network the call waiting timer T2 shall be started or if call forwarding on no reply is activated for the B-subscriber the no reply condition timer T3 shall be started. If the network received a non-zero SS Screening indicator from the calling users mobile station the ALERTING/FACILITY message sent to a calling mobile user shall include the Facility information element with an invoke of the Notification operation indicating that the call is waiting (see figure 1.2). If the network did not receive a non-zero SS Screening indicator from the calling users mobile station it shall not send a notification, i.e. either the ALERTING message does not include the Notification operation or the FACILITY message is omitted. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ .....Transaction identifier(C-B)..... CALL CONFIRMED ------------------------------------------------------------------------------------------------------------------------> .....Transaction identifier(C-B)..... .....Cause #17 (user busy)..... ALERTING ------------------------------------------------------------------------------------------------------------------------> .....Transaction identifier(C-B)..... start T2/T3 NOTE: The SETUP message shall include a "Signal Information" element with value #7 (call waiting tone on). This shall be used by the MS to generate an appropriate call waiting indication. Figure 1.1: Call indication to the mobile station on arrival of an incoming call and call confirmation from the mobile station MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> CALL PROCEEDING <------------------------------------------------------------------------------------------------------------------------ ALERTING/FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CW, CallIsWaiting-Indicator)) NOTE: If possible, the ALERTING message shall be used as the carrier message for the Call Waiting notification. Otherwise the FACILITY message shall be used. Figure 1.2: Notification to a calling mobile station that the call is in the waiting state ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 8 3G TS 24.083 version 3.0.0 1.2 Normal operation with successful outcome 1.2.1 Waiting call accepted; existing call released If the mobile user B before expiry of timer T2 determines to accept the waiting call and release the existing call the mobile station shall release the existing call firstly and accept the waiting call secondly. For the release of the existing call the mobile station and the network shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (A-B) of the already existing call. The Cause information element in the first clearing message shall indicate cause #16 "normal clearing". For the acceptance of the waiting call the mobile station and the network shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) of the waiting call. When the network receives the CONNECT message the timer T2 or if applicable the timer T3 shall be stopped. 1.2.2 Waiting call accepted; existing call on hold If the mobile user B before expiry of timer T2 or if applicable timer T3 determines to accept the waiting call and put the existing call on hold the mobile station shall put the existing call on hold firstly and accept the waiting call secondly. In case there is one active call (A-B) and another call (D-B) on hold and call (C-B) waiting, and the mobile user B wants to accept the waiting call (C-B) and put the active call (A-B) on hold, the held call (D-B) has to be released first, either by user B or user D, in accordance with GSM 04.08. To put the existing call on hold the mobile station and the network shall act in accordance with clause 2. The hold function shall be initiated by the mobile station and the transaction identifier shall be the transaction identifier (A-B) of the existing call (see figure 1.3). For the acceptance of the waiting call the mobile station and the network shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) of the waiting call (see figure 1.3). When the network receives the CONNECT message the timer T2 or if applicable the timer T3 shall be stopped. MS Network HOLD ------------------------------------------------------------------------------------------------------------------------> .....Transaction identifier(A-B)..... HOLD ACKNOWLEDGE <------------------------------------------------------------------------------------------------------------------------ .....Transaction identifier(A-B)..... HOLD REJECT <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .....Transaction identifier(A-B)..... .....Cause #29 (facility rejected)..... or #50 (requested facility not subscribed) or #69 (requested facility not implemented) CONNECT ------------------------------------------------------------------------------------------------------------------------> .....Transaction identifier(C-B)..... stop T2/T3 CONNECT ACKNOWLEDGE <------------------------------------------------------------------------------------------------------------------------ .....Transaction identifier(C-B)..... Figure 1.3: Existing call on hold and acceptance of waiting call by the mobile station ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 9 3G TS 24.083 version 3.0.0 1.2.3 Existing call released by user A; waiting call accepted If user A before the expiry of timer T2 or if applicable timer T3 determines to release the existing call then the existing call shall by released by the network firstly and the waiting call may be accepted by the mobile station secondly. For the release of the existing call the network and the mobile station shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (A-B) of the existing call. For the acceptance of the waiting call the mobile station and the network shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) of the waiting call. When the network receives the CONNECT message the timer T2 or if applicable the timer T3 shall be stopped. 1.3 Normal operation with unsuccessful outcome 1.3.1 Waiting call released by subscriber B For the release of the waiting call the mobile station and the network shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) of the waiting call. * If the B subscriber indicates UDUB by the sending of the first clearing message with cause information element #17 (User Busy), and call forwarding on mobile subscriber busy is activated for the B subscriber the call shall be forwarded by the network. If call forwarding is not active the call will be cleared. * If any other causes are given in the first clearing message the call will be released. 1.3.2 Waiting call released by calling user C If the calling user C, before the expiry of timer T2 or timer T3 (if applicable), releases the waiting call then the network shall release the waiting call against the mobile station. For the release of the waiting call the network and the mobile station shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) of the waiting call. When the network initiates clearing by sending a clearing message to the mobile station the timer T2 or, if applicable, the timer T3 shall be stopped. 1.3.3 Waiting call times out If the timer T2 expires the network shall release the waiting call. The network and the mobile station shall act in accordance with GSM 04.08. The transaction identifier shall be the transaction identifier (C-B) of the waiting call. The Cause information element in the first clearing message shall indicate cause #102 "recovery on timer expiry". 1.3.4 No reply condition timer expires If call forwarding on no reply is activated for the B-subscriber and the no reply condition timer expires the waiting call shall be forwarded in accordance with GSM 04.82. The network shall clear the waiting call towards the B-subscriber as in subclause 1.3.3. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 10 3G TS 24.083 version 3.0.0 1.4 Activation Activation of the supplementary service call waiting will be performed by the subscriber. The network will send a return result indication of acceptance of the request (see figure 1.4). If the network cannot accept an activation request, an error indication is returned to the served mobile subscriber. Error values are specified in GSM 04.80 (see figure 1.4). If the mobile subscriber does not indicate a specific basic service group the activation of call waiting is valid for all applicable basic services (see figure 1.4). Normal outgoing call procedures apply when this service is activated. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CW, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (BasicServiceCode)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If the BasicServiceCode is not included the activation is valid for all applicable basic services. Figure 1.4: Activation of call waiting 1.5 Deactivation Deactivation of the supplementary service call waiting will be performed by the subscriber. The network will send a return result indication of acceptance of the request (see figure 1.5). If the network cannot accept a deactivation request, an error indication is returned to the served mobile subscriber. Error values are specified in GSM 04.80 (see figure 1.5). If the subscriber does not indicate a specific basic service group the deactivation of call waiting is valid for all applicable basic services (see figure 1.5). ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 11 3G TS 24.083 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CW, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (BasicServiceCode)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If the BasicServiceCode is not included the deactivation is valid for all applicable basic services. Figure 1.5: Deactivation of call waiting 1.6 Interrogation Status check The mobile subscriber can request the status of the supplementary service call waiting and be informed whether the service is supported in the network and if so, a list of all basic service groups to which the call waiting supplementary service is active (see figure 1.6). If a mobile subscriber interrogates the network on the status of call waiting, and the network supports call waiting but the service is not active for any basic service groups then an SS-Status parameter shall be returned indicating "deactivated" (see figure 1.6). If a mobile subscriber interrogates the network on the status of call waiting, whilst the network does not support call waiting, the network shall return an error indication (see figure 1.6). MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CW)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode(s)) or RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (SS-Status) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) Figure 1.6: Interrogation of call waiting ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 12 3G TS 24.083 version 3.0.0 1.7 Invocation Invocation of call waiting causes no signalling on the radio path. 1.8 Registration and erasure Registration and erasure of the supplementary service call waiting are not applicable. 2 Call Hold (HOLD) 2.1 Normal operation 2.1.1 Hold and retrieve functions The hold and retrieve functions are performed on the same MM-connection. The hold function is used to put an existing call which is in the active phase in the Call held auxiliary state. By default, it retains the MM-connection in use and the transaction identifier of the held call for possible subsequent call retrieval. On receipt of a HOLD message the network shall return a HOLD ACKNOWLEDGE message, provided that the requested function can be performed. The network disconnects any user information path allocated to the active call when putting that call in the Call held auxiliary state. The mobile station disconnects any user information path to the active call and retains the transaction identifier and the MM-connection when putting that call in the Call held auxiliary state. The HOLD ACKNOWLEDGE message puts the call in the Call held auxiliary state and indicates that the hold function has been performed. The HOLD REJECT message indicates that the hold request was denied and returns the call to the condition it was in prior to the hold request. The HOLD REJECT message contains the Cause information element with e.g.: - cause #29 "Facility rejected"; - cause #50 "Requested facility not subscribed"; - cause #69 "Requested facility not implemented". The retrieve function reconnects the mobile station to the requested user information path. The RETRIEVE message requests that a call be retrieved. The RETRIEVE ACKNOWLEDGE message indicates that the retrieve function has been performed. The RETRIEVE REJECT message indicates that the retrieve request was denied. The RETRIEVE REJECT message contains the Cause information element with e.g.: - cause #34 "No channel available". 2.1.2 Hold invocation The served mobile subscriber indicates to the network that communication on the interface is to be interrupted. The hold function should be invoked in association with an existing active call. The invocation of the hold function does not affect the existing GSM 04.08 call states, but does affect the auxiliary state. The request for placing a call on hold places the auxiliary state in the hold request state. The responding entity will acknowledge this request with a HOLD ACKNOWLEDGE message if this operation was successful (see figure 2.1). This will result in the auxiliary state being put in the Call held state. If the requested hold function cannot be obtained, then a HOLD REJECT message will be returned with the appropriate cause (see figure 2.1). This will result in the auxiliary state returning to the Idle state. The traffic channel is now available to originate another call or to accept a waiting call (see call waiting). If at any time a call is in the held state, either party may clear the call according to the normal release procedure. Before to originate another call the MS will request the establishment of an MM-connection first, see GSM 04.08. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 13 3G TS 24.083 version 3.0.0 MS Network HOLD ------------------------------------------------------------------------------------------------------------------------> HOLD ACKNOWLEDGE <------------------------------------------------------------------------------------------------------------------------ HOLD REJECT <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .....Cause..... Figure 2.1: Invocation of call hold If the network received a non-zero SS Screening indicator from the remote party's mobile station the network shall send a notification to the remote party indicating that the call has been placed on hold (see figure 2.2). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (HOLD, CallOnHold-Indicator)) Figure 2.2: Notification to the held mobile party that the existing call being put on hold If the served mobile subscriber clears the current call and another call is still on hold, the normal call clearing procedure is used. 2.1.3 Retrieve procedure When the mobile subscriber that invoked the call hold service indicates that the call is to be retrieved, the network shall re-establish communication and send an acknowledgement to the served mobile subscriber (see figure 2.3). If the network received a non-zero SS Screening indicator from the remote party's mobile station the network shall send a notification to the remote party indicating that the call has been retrieved (see figure 2.4). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. The retrieve function is requested by sending a RETRIEVE message. This message may be sent while the auxiliary state is in the Call held state. Upon the sending of the RETRIEVE message the auxiliary state of the initiator's terminal would be the retrieve request state. If the retrieve request is successful, the RETRIEVE ACKNOWLEDGE message will be returned. The initiator should not assume that call retrieval has occurred until it receives this message. The auxiliary state would then return to the Idle state. If the retrieve request is not successful, the RETRIEVE REJECT message will be returned with an appropriate cause. The auxiliary state machine would then remain to the Call held state. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 14 3G TS 24.083 version 3.0.0 MS Network RETRIEVE ------------------------------------------------------------------------------------------------------------------------> RETRIEVE ACKNOWLEDGE <------------------------------------------------------------------------------------------------------------------------ RETRIEVE REJECT <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .....Cause..... Figure 2.3: Notification that the held call is to be retrieved (using the transaction identifier of the held call), by the served mobile subscriber MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (HOLD, CallOnHold-Indicator)) Figure 2.4: Notification to the held mobile party that the held call has been retrieved 2.1.4 Alternate from one call to the other If the served mobile subscriber is connected to an active call and a call on hold, he can alternate from one call to the other. This results in the previously active call being held and the previously held call becoming retrieved. This is achieved by sending a HOLD message for the active call, followed by a RETRIEVE message for the held call (see figure 2.5). These requests place the auxiliary state for the held and active calls in the retrieve request and hold request states respectively. If this alternate procedure is successful the HOLD ACKNOWLEDGE message will be returned, followed by the RETRIEVE ACKNOWLEDGE message. The initiator should not assume that the held call is retrieved and the active call is held until it receives both these messages. If the alternate procedure is not successful the HOLD REJECT message will be returned followed by the RETRIEVE REJECT message. This will result in the auxiliary state for the held and active calls returning to the previous states. If the network received a non-zero SS Screening indicator from the remote party's mobile station the network shall send a notification towards the previously held party that the call has been retrieved (see figure 2.4) and towards the previously active party that the call has been on hold (see figure 2.2). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 15 3G TS 24.083 version 3.0.0 MS Network HOLD (TI A-B) ------------------------------------------------------------------------------------------------------------------------> RETRIEVE (TI A-C) ------------------------------------------------------------------------------------------------------------------------> HOLD ACKNOWLEDGE (TI A-B) <------------------------------------------------------------------------------------------------------------------------ RETRIEVE ACKNOWLEDGE (TI A-C) <------------------------------------------------------------------------------------------------------------------------ HOLD REJECT (TI A-B) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .....Cause..... RETRIEVE REJECT (TI A-C) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .....Cause..... NOTE: TI A-B indicates the transaction identifier allocated to the original active call and TI A-C indicates the transaction identifier allocated to the original held call. Figure 2.5: Alternate procedure 2.1.5 Auxiliary states for hold and retrieve It is possible to place a call on hold in the Active state. The concept of dimensioned state space is being introduced to ensure state synchronization between the mobile station and the network. This concept suggests dimensioning the call state machine into two dimensions. In other words, there would be two states associated with each call. The first would be a GSM 04.08 call state and the second would be an auxiliary state associated with hold. Suppose the dimensioned state space is represented by two co-ordinates: one is a GSM 04.08 call state co-ordinate and the other is a hold co- ordinate. If a GSM 04.08 call state transition occurs, the former co-ordinate is updated. If a call is put on hold, the hold co-ordinate is updated. When the held call is reconnected, the hold co-ordinate is again updated. There are four auxiliary states associated with the hold and retrieve functions: - Idle; - Hold request; A request has been made for the hold function. - Call held; The call is held and the user information path has been reserved. - Retrieve request; A request has been made for the retrieve function. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 16 3G TS 24.083 version 3.0.0 2.1.6 An example of dimensioned state space Suppose a call is in the Active state. The dimensioned state space would be: (Active, Idle). Now the mobile station requests the hold function. The dimensioned state space would become: (Active, Hold request). The call is then put on hold. The mobile station becomes aware of this upon receiving the HOLD ACKNOWLEDGE message from the network. The dimensioned state space would now be: (Active, Call held). Now the mobile station requests the retrieve function. The dimensioned state space would become: (Active, Retrieve request). When a call is reconnected, the dimensioned state space would be: (Active, Idle). 2.2 Activation and deactivation Activation and deactivation of the supplementary service call hold cause no signalling on the radio path. 2.3 Registration, erasure and interrogation Registration, erasure and interrogation of the supplementary service call hold are not applicable. ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 24.083 V3.0.0 (1999-05) 17 3G TS 24.083 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.83 6.0.0 Transferred to 3GPP CN1 CN#03 24.083 3.0.0 Approved at CN#03 ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) ETSI ETSI 18 ETSI ETSI TS 124 083 V3.0.0 (2000-01) (3G TS 24.083 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
126 090
|
Universal Mobile Telecommunications System (UMTS); Mandatory Speech Codec speech processing functions AMR Speech Codec - Transcoding functions (3G TS 26.090 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/126000_126099/126090/03.01.00_60/ts_126090v030100p.pdf
|
....................................................................................................................................................... 6
|
124 081
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Line identification supplementary services - Stage 3 (3G TS 24.081 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124081/03.01.00_60/ts_124081v030100p.pdf
|
........................................................................................................................................................5
|
124 012
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (3G TS 24.012 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124012/03.00.00_60/ts_124012v030000p.pdf
|
........................................................................................................................................................5
|
123 119
|
Universal Mobile Telecommunications System (UMTS); Gateway Location Register (GLR); Stage2 (3G TS 23.119 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/123100_123199/123119/03.00.00_60/ts_123119v030000p.pdf
|
........................................................................................................................................................7
|
123 108
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Mobile radio interface layer 3 specification; Core Network Protocols - Stage 2 (3G TS 23.108 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/123100_123199/123108/03.02.00_60/ts_123108v030200p.pdf
|
........................................................................................................................................................5
|
123 097
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Multiple Subscriber Profile (MSP) (Phase 1) - Stage 2 (3G TS 23.097 version 3.1.1 Release 1999)
|
TS
|
3.1.1
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123097/03.01.01_60/ts_123097v030101p.pdf
|
........................................................................................................................................................6
|
123 073
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Support of Localized Service Area (SoLSA); Stage 2 (3G TS 23.073 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123073/03.00.00_60/ts_123073v030000p.pdf
|
........................................................................................................................................................5
|
123 070
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Routeing of calls to/from Public Data Networks (PDN) (3G TS 23.070 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123070/03.00.00_60/ts_123070v030000p.pdf
|
........................................................................................................................................................5
|
124 082
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Forwarding (CF) supplementary services - Stage 3 (3G TS 24.082 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124082/03.00.00_60/ts_124082v030000p.pdf
|
This European Standard (EN) specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, interrogation and network invocation of call offering supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10, the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.82 is related specially to call offering supplementary services. Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.82 is related specially to call offering supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call offering supplementary services and are described in the present document: - Call forwarding unconditional (CFU) (clause 1); - Call forwarding on mobile subscriber busy (CFB) (clause 2); - Call forwarding on no reply (CFNRy) (clause 3); - Call forwarding on mobile subscriber not reachable (CFNRc) (clause 4). 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)". [3] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [4] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [5] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 7 3G TS 24.082 version 3.0.0 [6] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [7] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [8] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". [9] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 1". [10] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [11] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data (USSD) - Stage 1". [12] GSM 03.02: "Digital cellular telecommunications system (Phase 2+); Network architecture". [13] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [14] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [15] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [16] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [17] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [18] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [19] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [20] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [21] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [25] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification; General aspects". [26] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 8 3G TS 24.082 version 3.0.0 0.3 Cross phase compatibility For the following supplementary services, a number of changes exist between the present document and the protocol version 1 specification: - Call forwarding unconditional; - Call forwarding on mobile subscriber busy; - Call forwarding on no reply; - Call forwarding on mobile subscriber not reachable. For these supplementary services, the main body of the present document assumes that all network entities comply with this version of the service. In each case, an additional subclause (subclause x.7) defines the additional requirements for when one or more network entities or the MS complies with the protocol version 1 specifications for the supplementary service procedures. 1 Call Forwarding Unconditional (CFU) 1.1 Normal operation 1.1.1 Served mobile subscriber side When call forwarding unconditional is active, all incoming calls for the specified basic service(s) will be forwarded without being offered to the served mobile subscriber. When CFU is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that CFU is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 1.1. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFU, SS-Status)) Figure 1.1: Notification to the served mobile subscriber that call forwarding is active 1.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 1.2. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 9 3G TS 24.082 version 3.0.0 Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFU, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 1.2: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 1.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 1.3. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFU, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 1.3: Notification to the calling mobile subscriber that the call is forwarded 1.2 Registration The following information has to be registered in the network: - the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded. 1.2.1 Registration by the served mobile subscriber A CFU registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services. If the registration is successful, the CFU service will be registered and activated. The network will then send a return result indicating acceptance of the request including the ForwardedToNumber and possibly the BasicService (group) Code to which CFU is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases, the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 1.4. Note that the use of SS-Status is to provide backwards compatibility with phase 1. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 10 3G TS 24.082 version 3.0.0 If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFU registration was not successful. Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFU, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Status may not be included in all cases, see text. Figure 1.4: Registration of call forwarding unconditional When registering call forwarding, the SS-Code may indicate the code for "all forwarding SS". In this case, if the subscriber has CFU provisioned, the return result shall contain the information for CFU. If the subscriber does not have CFU provisioned, the return result shall contain the information for any conditional call forwarding services which the subscriber has provisioned. 1.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFU for a specific basic service group to another directory number, thus causing the previous registration of CFU to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 1.3.1 Erasure by the served mobile subscriber If the erasure is successful, the CFU service will be erased (and automatically deactivated). The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the BasicService (group) Code for which CFU was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 1.5. Note that the use of SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the erasure was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the network cannot accept the erasure request, the status of CFU in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFU was unsuccessful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 11 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 1.5: Erasure of call forwarding unconditional 1.4 Activation An explicit CFU activation request from a mobile user shall contain the supplementary service to be activated and possibly the basic service group the request applies to. If a basic service group is not included in the activation request the request applies to all basic services against which a CFU forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFU activation request, see figure 1.6. Error values (which are used in the two latter situations) are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code for "all forwarding SS", being handled as for registration (see subclause 1.2.1). Figure 1.6: Activation of call forwarding unconditional ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 12 3G TS 24.082 version 3.0.0 1.5 Deactivation An explicit CFU deactivation request shall contain the supplementary service to be deactivated and possibly the basic service group the request applies to. If a basic service group is not included in the deactivation request the request applies to all basic services against which CFU is activated. The user shall receive appropriate notification of acceptance or rejection of the CFU deactivation request, see figure 1.7. Error values to be used in the latter situation are specified in GSM 04.80. Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code for "all forwarding SS". Figure 1.7: Deactivation of call forwarding unconditional 1.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFU is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress, see figure 1.8. If CFU is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 13 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFU)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group. Figure 1.8: Interrogation of active call forwarding unconditional for all basic services - in response to a specific request concerning one particular basic service group, the served mobile subscriber should be informed whether or not CFU is registered, including information on whether or not it is active and operative or active and quiescent for that basic service group. If CFU is registered, the associated ForwardedToNumber shall be given, see figure 1.9. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFU is not registered for the interrogated basic service group, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 1.9: Interrogation of active call forwarding unconditional for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 14 3G TS 24.082 version 3.0.0 1.7 Cross phase compatibility 1.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFU registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFU activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 1.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFU interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFU is activated and operative. Data shall not be returned for basic service groups to which CFU is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFU registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. 2 Call Forwarding on mobile subscriber Busy (CFB) 2.1 Normal operation 2.1.1 Served mobile subscriber side When call forwarding on mobile subscriber busy is active, the following actions are taken by the network: - If the mobile is Network Determined User Busy (NDUB as defined in GSM 02.01), incoming calls for the specified basic service(s) will be forwarded without being offered to the served mobile subscriber. - If the mobile is not NDUB, the incoming call is offered (as a normal or waiting call) to the served mobile subscriber. - if the call is subsequently released by the mobile with the first clearing message containing the cause = "User Busy" before the CONNECT message is received, it will be forwarded by the network, see figure 2.0; - if any other release causes are given, the call will be released; - if one of the call control timers (T303 or T310) elapse, the call will be released. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ ....Transaction Identifier (A-B).... RELEASE COMPLETE/RELEASE/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> ....Transaction Identifier (A-B).... ....Cause # 17 (User Busy).... Figure 2.0: Call which is offered to the served mobile subscriber being released. The network will invoke call forwarding on mobile subscriber busy in this case, if CFB is active for the requested basic service ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 15 3G TS 24.082 version 3.0.0 When an incoming call is forwarded on mobile subscriber busy due to NDUB the served mobile subscriber can, as a subscription option, receive a NotifySS operation containing the SS-Notification indicating that a call has been forwarded, see figure 2.1. He will not be able to answer the incoming call. The transaction identifier employed shall correspond to any call B is having. MS Network FACILITY (TI=B-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFB, SS-Notification)) NOTE: X is any party with which B has a call. Figure 2.1: Notification to the served mobile subscriber that a call is forwarded on mobile subscriber busy When CFB is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that a conditional call forwarding supplementary service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 2.2. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common SS-Code for all conditional call forwarding services. Figure 2.2: Notification to the served mobile subscriber that a conditional call forwarding service is active 2.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 2.3. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 16 3G TS 24.082 version 3.0.0 MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFB, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 2.3: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 2.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 2.4. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFB, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 2.4: Notification to the calling mobile subscriber that the call is forwarded 2.2 Registration The following information has to be registered in the network: - the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded. 2.2.1 Registration by the served mobile subscriber A CFB registration request from a mobile user shall include the SS-Code of the forwarding service to be registered, and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services. If the registration is successful, the CFB service will be registered and activated. The network will then send a return result indicating acceptance of the request, including the ForwardedToNumber and possibly the BasicService (group) Code to which CFB is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 2.5. Note that the use of SS-Status is to provide backwards compatibility with phase 1. If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFB registration was not successful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 17 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFB, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Status may not be included in all cases, see text. Figure 2.5: Registration of call forwarding on mobile subscriber busy The SS-Code may indicate the code for "all forwarding SS", as specified in subclause 1.2.1. The SS-Code may indicate the code for "all conditional forwarding SS". In this case the return result shall contain the information for any conditional call forwarding services which the subscriber has provisioned. 2.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFB for the specific basic service to another directory number, thus causing the previous registration of CFB to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 2.3.1 Erasure by the served mobile subscriber A CFB erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services. If the erasure is successful, the CFB service will be erased (and automatically deactivated). The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the BasicService (group) Code for which CFB was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 2.6. Note that the use of SS-Status is to provide backwards compatibility with phase 1. - If the request did not include a BasicServiceCode, and the erasure was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the network cannot accept the erasure request, the status of CFB in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFB was unsuccessful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 18 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 2.6: Erasure of call forwarding on mobile subscriber busy 2.4 Activation An explicit CFB activation request shall contain the SS-Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which CFB forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFB activation request, see figure 2.7. Error values to be used in the two latter situations are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1. Figure 2.7: Activation of call forwarding on mobile subscriber busy 2.5 Deactivation An explicit CFB deactivation request shall contain the SS-Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFB is activated. The user shall receive appropriate notification of acceptance or rejection of the CFB deactivation request, see figure 2.8. Error values to be used in the latter situation are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 19 3G TS 24.082 version 3.0.0 Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the "all conditional forwarding SS" group or the "all forwarding SS" group. Figure 2.8: Deactivation of call forwarding on mobile subscriber busy 2.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFB is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress, see figure 2.9. If CFB is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 20 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFB)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group. Figure 2.9: Interrogation of active call forwarding on mobile subscriber busy for all basic services - in response to a specific request (i.e. containing one particular BasicService (group) Code, the served mobile subscriber should receive the SS-Status parameter, indicating whether or not CFB is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFB is registered, the associated ForwardedToNumber shall be given, see figure 2.10. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFB is not registered for the interrogated BasicService (group) code, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 2.10: Interrogation of active call forwarding on mobile subscriber busy for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 21 3G TS 24.082 version 3.0.0 2.7 Cross phase compatibility 2.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFB registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFB activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 2.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFB interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFB is activated and operative. Data shall not be returned for basic service groups to which CFB is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFB registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. 3 Call Forwarding on No Reply (CFNRy) 3.1 Normal operation 3.1.1 Served mobile subscriber side When call forwarding on no reply is active, all incoming calls for the specified basic service(s) that are not answered within the period defined by the no reply condition timer, will be forwarded. When an incoming call is forwarded on no reply the served mobile subscriber can, as a subscription option, receive a NotifySS operation containing the SS-Notification indicating that a call has been forwarded, see figure 3.1. MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRy, SS-Notification)) Figure 3.1: Notification to the served mobile subscriber that the call is forwarded on no reply When CFNRy is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that a conditional call forwarding supplementary service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 3.2. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common SS-Code for all conditional call forwarding services. Figure 3.2: Notification to the served mobile subscriber that a conditional call forwarding service is active ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 22 3G TS 24.082 version 3.0.0 3.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 3.3. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRy, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for "all forwarding SS" will be used. Figure 3.3: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 3.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 3.4. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRy, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for "all forwarding SS" will be used. Figure 3.4: Notification to the calling mobile subscriber that the call is forwarded ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 23 3G TS 24.082 version 3.0.0 3.2 Registration The following information has to be registered in the network: - the ForwardedToNumber, which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded; - the duration of the no reply condition timer. 3.2.1 Registration by the served mobile subscriber A CFNRy registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the applicable BasicServiceCode and NoReplyConditionTime. If the BasicServiceCode is not included, the request applies to all basic services. If the NoReplyConditionTime is not included, the previous value set by the mobile user or network operator applies. If the registration is successful, the CFNRy service will be registered and activated. The network will then send a return result indicating acceptance of the request, including the ForwardedToNumber and possibly the applicable BasicService (group) code and NoReplyConditionTime. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 3.5. Note that the use of SS-Status is to provide backwards compatibility with phase 1. If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFNRy registration was not successful. Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFNRy, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. If NoReplyConditionTime is not included the value previously registered in the network applies. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Code may also indicate the code for "all conditional forwarding SS", as specified in subclause 2.2.1, or the code for "all forwarding SS", as specified in subclause 1.2.1. The SS-Status may not be included in all cases, see text. Figure 3.5: Registration of call forwarding on no reply ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 24 3G TS 24.082 version 3.0.0 3.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFNRy for the specific basic service to another directory number, thus causing the previous registration of CFNRy to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 3.3.1 Erasure by the served mobile subscriber A CFNRy erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services. If the erasure is successful, the CFNRy service will be erased (and automatically deactivated). The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the BasicService (group) Code for which CFNRy was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 3.6. Note that the use of SS-Status is to provide backwards compatibility with phase 1. - If the request did not include a BasicServiceCode, and the erasure was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the network cannot accept the erasure request, the status of CFNRy in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFNRy was unsuccessful. Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 3.6: Erasure of call forwarding on no reply ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 25 3G TS 24.082 version 3.0.0 3.4 Activation An explicit CFNRy activation request shall contain the SS-Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which a CFNRy forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFNRy activation request, see figure 3.7. Error values (which are used in the two latter situations) are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1. Figure 3.7: Activation of call forwarding on no reply 3.5 Deactivation An explicit CFNRy deactivation request shall contain the SS-Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFNRy is activated. The user shall receive appropriate notification of acceptance or rejection of the CFNRy deactivation request, see figure 3.8. Error values to be used in the latter situation are specified in GSM 04.80. Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate "all conditional forwarding SS" group or the "all forwarding SS" group. Figure 3.8: Deactivation of call forwarding on no reply ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 26 3G TS 24.082 version 3.0.0 3.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFNRy is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress; - the duration of the no reply condition timer, see figure 3.9. If CFNRy is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRy)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, NoReplyConditionTime)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basis service group. Figure 3.9: Interrogation of active call forwarding on no reply for all basic services - in response to a specific request (i.e. containing one particular BasicService (group) code, the served mobile subscriber should receive the SS-Status parameter, indicating whether or not CFNRy is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFNRy is registered for the interrogated basic service group, the associated ForwardedToNumber and the duration of the no reply condition timer shall be given, see figure 3.10. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFNRy is not registered for the interrogated BasicService (group) code, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 27 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 3.10: Interrogation of active call forwarding on no reply for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. 3.7 Cross phase compatibility 3.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFNRy registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFNRy activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 3.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFNRy interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFNRy is activated and operative. Data shall not be returned for basic service groups to which CFNRy is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFNRy registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. 4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) 4.1 Normal operation 4.1.1 Served mobile subscriber side When call forwarding on mobile subscriber not reachable, all incoming calls for the specified basic service(s) when the mobile subscriber is not reachable, will be forwarded without being offered to the served mobile subscriber. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 28 3G TS 24.082 version 3.0.0 When CFNRc is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that a conditional call forwarding service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 4.1. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common SS-Code for all conditional call forwarding services. Figure 4.1: Notification to the served mobile subscriber that a conditional call forwarding service is active 4.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 4.2. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRc, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for call forwarding SS will be used. Figure 4.2: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 4.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 4.3. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 29 3G TS 24.082 version 3.0.0 MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRc, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 4.3: Notification to the calling mobile subscriber that the call is forwarded 4.2 Registration The following information has to be registered in the network: - the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded. 4.2.1 Registration by the served mobile subscriber A CFNRc registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services. If the registration is successful, the CFNRc will be registered and activated. The network will then send a return result indicating of acceptance of the request, including the ForwardedToNumber and possibly the applicable BasicService (group) code to which CFNRc is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 4.4. Note that the use of SS-Status is to provide backwards compatibility with phase 1. If the registration is successful, the CFNRc will be registered and activated. The network will then send a return result indicating of acceptance of the request, including the ForwardedToNumber to which CFNRc is registered. If no BasicServiceCode was included in the registration request it is not included in the return result either, see figure 4.4. If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFNRc registration was not successful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 30 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFNRc, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Code may also indicate the code for "all conditional forwarding SS", as specified in subclause 2.2.1, or the code for "all forwarding SS", as specified in subclause 1.2.1. The SS-Status may not be included in all cases, see text. Figure 4.4: Registration of call forwarding on mobile subscriber not reachable 4.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFNRc for the specific basic service to another directory number, thus causing the previous registration of CFNRc to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 4.3.1 Erasure by the served mobile subscriber A CFNRc erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services. If the erasure is successful, the CFNRc service will be erased (and automatically deactivated). The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the BasicService (group) Code for which CFNRc was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 4.5. Note that the use of SS-Status is to provide backwards compatibility with phase 1. - If the request did not include a BasicServiceCode, and the erasure was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the network cannot accept the erasure request, the status of CFNRc in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFNRc was unsuccessful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 31 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 4.5: Erasure of call forwarding on mobile subscriber not reachable 4.4 Activation An explicit CFNRc activation request shall contain the SS-Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which a CFNRc forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFNRc activation request, see figure 4.6. Error values (which are used in the two latter situations) are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1. Figure 4.6: Activation of call forwarding on mobile subscriber not reachable 4.5 Deactivation An explicit CFNRc deactivation request shall contain the SS-Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFNRc is activated. The user shall receive appropriate notification of acceptance or rejection of the CFNRc deactivation request, see figure 4.7. Error values to be used in the latter situation are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 32 3G TS 24.082 version 3.0.0 Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the "all conditional forwarding SS" group or the "all forwarding SS" group. Figure 4.7: Deactivation of call forwarding on mobile subscriber not reachable 4.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFNRc is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress, see figure 4.8. If CFNRc is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 33 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRc)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group. Figure 4.8: Interrogation of call forwarding on mobile subscriber not reachable active for all basic services - in response to a specific request (i.e. containing one particular BasicService (group) code), the served mobile subscriber should receive the SS-Status parameter, indicating whether or not CFNRc is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFNRc is registered, the associated ForwardedToNumber shall be given, see figure 4.9. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFNRc is not registered for the interrogated BasicService (group) code, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 4.9: Interrogation of active call forwarding on mobile subscriber not reachable for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 34 3G TS 24.082 version 3.0.0 4.7 Cross phase compatibility 4.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFNRc registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFNRc activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 4.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFNRc interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFNRc is activated and operative. Data shall not be returned for basic service groups to which CFNRc is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFNRc registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 35 3G TS 24.082 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.82 7.0.0 Transferred to 3GPP CN1 CN#03 24.082 3.0.0 Approved at CN#03 ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 36 ETSI ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
124 072
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Deflection (CD) Supplementary Service - Stage 3 (3G TS 24.072 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124072/03.00.00_60/ts_124072v030000p.pdf
|
........................................................................................................................................................5
|
122 094
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Follow Me Service description - Stage 1 (3G TS 22.094 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122094/03.01.00_60/ts_122094v030100p.pdf
| |
122 093
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1 (3G TS 22.093 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122093/03.00.01_60/ts_122093v030001p.pdf
|
........................................................................................................................................................5
|
123 038
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Alphabets and language-specific information (3G TS 23.038 version 3.3.0 Release 1999)
|
TS
|
3.3.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123038/03.03.00_60/ts_123038v030300p.pdf
| |
124 096
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Name Identification supplementary services - Stage 3 (3G TS 24.096 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124096/03.00.00_60/ts_124096v030000p.pdf
|
........................................................................................................................................................5
|
124 084
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Multi Party (MPTY) supplementary service - Stage 3 (3G TS 24.084 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124084/03.00.00_60/ts_124084v030000p.pdf
|
The present document specifies the procedures used at the radio interface (Reference point Um as defined in GSM 04.02) for normal operation and invocation of MultiParty supplementary services. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and the GSM 02.8x and GSM 02.9x-series. GSM 02.84 is related specially to MultiParty supplementary services. Technical realization of supplementary services is described in GSM 03.11 and the GSM 03.8x and GSM 03.9x-series. GSM 03.84 is related specially to MultiParty supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary service belongs to the MultiParty supplementary services and is described in the present document: - MultiParty service (MPTY) (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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [5] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [6] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [7] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 6 3G TS 24.084 version 3.0.0 [8] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) supplementary services - Stage 1". [9] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [10] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 1". [11] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [12] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [13] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [14] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [15] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [16] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [17] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [18] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [19] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [20] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [21] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [22] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [23] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [24] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [25] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 7 3G TS 24.084 version 3.0.0 1 MultiParty service (MPTY) 1.1 Beginning the MultiParty service The served mobile subscriber A may initiate an active MultiParty call from an active call C and a held call B. The mobile station invokes the service by sending a FACILITY message to the network containing the BuildMPTY request. This BuildMPTY request indicates to the network that the mobile subscriber wishes all his calls to be connected together in a MultiParty call. The network will normally accept the request and connect the mobile subscriber with the other existing connections (active call C and held call B). If the request is not accepted, the network will indicate the error to the served mobile (see figure 1.1). The network confirms with the same transaction identifier. Error values are specified in GSM 04.80. During the BuildMPTY operation the MS shall run a timer T(BuildMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. MS Network FACILITY (TI A-B/A-C) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = BuildMPTY) FACILITY (TI A-B/A-C) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-B/A-C) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-B/A-C) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: A-B/A-C indicates a choice. The transaction identifier (TI) used must be that of the active call or the held call. Figure 1.1: Invocation of the MultiParty call If the network received a non-zero SS Screening indicator from the remote party's mobile station the network will also send indications towards the remote parties that the MultiParty call has been invoked, and towards the previously-held party to indicate that he is now retrieved (see figures 1.2 and 1.3). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. B Network FACILITY (TI A-B) <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (HOLD, CallOnHold-indicator), Invoke = NotifySS (MPTY, MPTYindicator)) NOTE: The CallOnHold notification (CallOnHold-indicator) sent to the remote subscriber is the same as described in GSM 04.83. Figure 1.2: Notification of invocation to previously-held remote party C Network FACILITY (TI A-C) <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (MPTY, MPTYindicator)) Figure 1.3: Notification of invocation to previously-active remote party ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 8 3G TS 24.084 version 3.0.0 1.2 Managing an active MultiParty call 1.2.1 Served mobile subscriber During an active MultiParty call the served mobile subscriber can request the network to: 1.2.1.1 Put the MultiParty call on hold This is achieved by sending a FACILITY message to the network with any transaction identifier corresponding to a call within the MultiParty call. This requests the network to place the mobile subscriber's connection to the MultiParty call on hold. The network confirms with another message containing the same transaction identifier (see figure 1.4). During the HoldMPTY operation the MS shall run a timer T(HoldMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. MS Network FACILITY (TI A-X) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = HoldMPTY) FACILITY (TI A-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: X = Any remote party in MultiParty call. Figure 1.4: Served mobile subscriber places his connection to the MultiParty call on hold Indications are sent towards all remote parties in the MultiParty call by means of normal CallOnHold notifications as described in GSM 04.83. 1.2.1.2 Create a private communication with one of the remote parties To create a private communication with one of the remote parties, the served mobile will send a SplitMPTY message to the network (see figure 1.5). The network will send normal CallOnHold notifications to the remote parties on hold in the MPTY call. During the SplitMPTY operation the MS shall run a timer T(SplitMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 9 3G TS 24.084 version 3.0.0 MS Network FACILITY (TI A-X) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = SplitMPTY) FACILITY (TI A-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: X = Party with which to establish a private communication. Figure 1.5: Served mobile subscriber requests a private communication with a single remote party 1.2.1.3 Terminate the entire MultiParty call The MultiParty call is terminated by disconnecting all individual parties as described in subclause 1.2.1.4. 1.2.1.4 Explicitly disconnect a remote party Any remote party may be individually disconnected by initiation of call clearing as defined in GSM 04.08 with the same transaction identifier corresponding to that party. 1.2.2 Remote Parties During an active MultiParty call any conferee is able to: 1.2.2.1 Release from the MultiParty call In this case, the network will initiate the call clearing procedure towards the served mobile subscriber as defined in GSM 04.08 with the transaction identifier corresponding to the disconnecting party. 1.2.2.2 Place his connection to the MultiParty call on hold, and typically later retrieve it Where a held/retrieved indication is received from any remote party, the network will forward this to the served mobile subscriber (see GSM 04.83). 1.3 Managing a held MultiParty call 1.3.1 Served mobile subscriber During a held MultiParty call the served mobile subscriber can request the network to: 1.3.1.1 Retrieve the held MultiParty call To retrieve the held MultiParty call, a FACILITY message is sent to the network with a transaction identifier corresponding to any call in the MPTY. The network confirms the retrieval with another message containing the same transaction identifier (see figure 1.6). ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 10 3G TS 24.084 version 3.0.0 During the RetrieveMPTY operation the MS shall run a timer T(RetrieveMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. MS Network FACILITY (TI A-X) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RetrieveMPTY) FACILITY (TI A-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: X = Any remote party in MultiParty call. Figure 1.6: Served mobile subscriber retrieves MultiParty call Indications are sent towards all remote parties by means of normal CallOnHold (= CallRetrieved) notifications as described in GSM 04.83. 1.3.1.2 Initiate a new call This is achieved by normal call set-up procedures (GSM 04.08). 1.3.1.3 Process a call waiting request This is described in GSM 04.83. 1.3.1.4 Terminate the held MultiParty call This is achieved by the same procedure as in subclause 1.2.1.3. 1.3.1.5 Explicitly disconnect a remote party This is achieved by the same procedure as in subclause 1.2.1.4. 1.3.2 Remote parties During a held MultiParty call any remote party is able to perform the same operations as described for an active MultiParty call in subclause 1.2.2. 1.4 Managing a single call and a MultiParty call 1.4.1 Served mobile subscriber If the served mobile subscriber is connected to a MultiParty call (active or on hold) and another single call (active or on hold), he can request the network to: ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 11 3G TS 24.084 version 3.0.0 1.4.1.1 Disconnect the single call This is achieved by using the call clearing procedure as described in GSM 04.08 with the transaction identifier corresponding to the single call. 1.4.1.2 Disconnect the MPTY This is achieved by the same procedure as disconnecting a held/active MPTY without another call (see subclauses 1.2.1 and 1.3.1). 1.4.1.3 Disconnect all calls This is achieved by using the procedures in subclauses 1.4.1.1 and 1.4.1.2. 1.4.1.4 Add the single call to the MPTY The served mobile subscriber may request the connection of all his calls, held and active, into an active MultiParty call at any time by sending a FACILITY message with the transaction identifier corresponding to any remote party and containing the BuildMPTY invoke component (see subclause 1.1). This procedure will apply whether the MultiParty call is on hold or active, and whether the single call is on hold or active. If the request is successful, previously held remote parties will receive an MPTY notification and a CallRetrieved notification as shown in figure 1.2, and previously active remote parties will receive an MPTY notification as shown in figure 1.3. If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. If the request is unsuccessful e.g. because the maximum number of remote parties has already been reached, then an error is returned to the served mobile subscriber, as shown in figure 1.1. Error values are specified in GSM 04.80. 1.4.1.5 Alternate between the MPTY call and the single call This procedure follows the Alternate procedure defined in GSM 04.83 with the exception that the MPTY call is held/retrieved using HoldMPTY/RetrieveMPTY in place of HOLD/RETRIEVE as follows: Single call MPTY call (Facility) HOLD Invoke (HoldMPTY) HOLD ACKNOWLEDGE Return result HOLD REJECT Return error (error) RETRIEVE Invoke (RetrieveMPTY) RETRIEVE ACKNOWLEDGE Return result RETRIEVE REJECT Return error (error) 1.5 Adding extra remote parties Extra remote parties are added by placing the MultiParty call on hold (subclause 1.2.1.1), setting up a new connection (either a new call or a waiting call) and then sending a FACILITY message to the network requesting that the active call be joined with the MPTY, using the same signalling as for invocation (see figure 1.1). This results in an active MultiParty call. Notifications are sent as for the initial invocation (i.e. previously-held parties in MPTY receive CallRetrieved notifications and MPTY notifications; the new remote party only receives an MPTY notification) (see figures 1.2 and 1.3). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. If the request is not accepted, e.g. because the maximum number of remote parties has already been reached, then the error is indicated to the mobile station. Error values are specified in GSM 04.80. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 12 3G TS 24.084 version 3.0.0 1.6 Auxiliary states for MPTY In the call hold service (GSM 04.83), a two dimensional state space is defined, where the first dimension corresponds to the GSM 04.08 call control state and the second dimension corresponds to the call hold state (Idle, Hold Request, Call Held, Retrieve Request). For the purposes of the MPTY service, it is necessary to introduce another dimension to this state space, i.e. the MultiParty state. There are four auxiliary states associated with the MPTY service: - Idle; - MPTY request; A request has been made to add this call to the MPTY. - Call in MPTY; This call is in the MPTY. - Split request; A request has been made to remove this call from the MPTY. These Auxiliary states apply in addition to the GSM 04.08 call control states and the GSM 04.83 call hold states. Thus for example, an active call in a held MPTY has the state (Active, Call held, Call in MPTY). Not all states are allowed, for example an MPTY cannot be split while it is held, so (Active, Call held, Split request) is forbidden. 1.7 Activation, deactivation, registration, erasure and interrogation Activation, deactivation, registration, erasure and interrogation of the MultiParty service are not applicable. 1.8 Simultaneous use of MultiParty operations The operations BuildMPTY, SplitMPTY, HoldMPTY and RetrieveMPTY interact with each other, and cannot be applied simultaneously. Once the mobile station has initiated one of these operations, it shall not initiate another MultiParty operation until the first operation has been acknowledged by the network, or the MS locally determines (due to timer expiry) that the first operation has failed. The use of several MultiParty operations as different components in the same message is not allowed. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 13 3G TS 24.084 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.84 6.0.0 Transferred to 3GPP CN1 CN#03 24.084 3.0.0 Approved at CN#03 ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 14 ETSI ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
122 085
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Closed User Group (CUG) Supplementary Services - Stage 1 (3G TS 22.085 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122085/03.01.00_60/ts_122085v030100p.pdf
| |
123 066
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2 (3G TS 23.066 version 3.3.0 Release 1999)
|
TS
|
3.3.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123066/03.03.00_60/ts_123066v030300p.pdf
|
........................................................................................................................................................6
|
123 042
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Compression algorithm for text messaging services (3G TS 23.042 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123042/03.01.00_60/ts_123042v030100p.pdf
|
........................................................................................................................................................8
|
123 110
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); UMTS Access Stratum Services and Functions (3G TS 23.110 version 3.4.0 Release 1999)
|
TS
|
3.4.0
|
http://www.etsi.org/deliver/etsi_ts/123100_123199/123110/03.04.00_60/ts_123110v030400p.pdf
|
........................................................................................................................................................6
|
122 090
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Unstructured Supplementary Service Data (USSD) - Stage 1 (3G TS 22.090 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122090/03.01.00_60/ts_122090v030100p.pdf
|
........................................................................................................................................................4
|
122 087
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); User-to-User Signalling (UUS); Service description - Stage 1 (3G TS 22.087 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122087/03.01.00_60/ts_122087v030100p.pdf
|
........................................................................................................................................................6
|
123 012
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Location Management Procedures (3G TS 23.012 version 3.3.0 Release 1999)
|
TS
|
3.3.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123012/03.03.00_60/ts_123012v030300p.pdf
|
........................................................................................................................................................6
|
122 140
|
Universal Mobile Telecommunications System (UMTS); Service aspects; Stage 1 Multimedia Messaging Service (3G TS 22.140 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122100_122199/122140/03.01.00_60/ts_122140v030100p.pdf
|
........................................................................................................................................................5
|
122 084
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); MultiParty (MPTY) Supplementary Services - Stage 1 (3G TS 22.084 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122084/03.00.01_60/ts_122084v030001p.pdf
| |
123 054
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Description for the use of a Shared Inter Working Function (SIWF) in a GSM PLMN - Stage 2 (3G TS 23.054 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123054/03.00.00_60/ts_123054v030000p.pdf
|
........................................................................................................................................................6
|
122 081
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Line identification Suplementary Services; Stage 1 (3G TS 22.081 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122081/03.02.00_60/ts_122081v030200p.pdf
|
........................................................................................................................................................6
|
122 079
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Support of Optimal Routeing (SOR); Service definition - Stage 1 (3G TS 22.079 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122079/03.00.01_60/ts_122079v030001p.pdf
| |
122 072
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Deflection Service description - Stage 1 (3G TS 22.072 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122072/03.00.01_60/ts_122072v030001p.pdf
| |
123 015
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Technical realization of Operator Determined Barring (ODB) (3G TS 23.015 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/123000_123099/123015/03.01.00_60/ts_123015v030100p.pdf
| |
122 086
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Advice of Charge (AoC) Supplementary Services - Stage 1 (3G TS 22.086 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122086/03.01.00_60/ts_122086v030100p.pdf
|
........................................................................................................................................................5
|
121 111
|
<empty>
|
TS
|
18.0.0
|
http://www.etsi.org/deliver/etsi_ts/121100_121199/121111/18.00.00_60/ts_121111v180000p.pdf
|
........................................................................................................................................................ 7
|
122 057
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Mobile Station Application Execution Environment (MExE); Service description; Stage 1 (3G TS 22.057 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122057/03.00.01_60/ts_122057v030001p.pdf
| |
122 043
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Support of Localised Service Area (SoLSA); Service description; Stage 1 (3G TS 22.043 version 3.1.0 Release 1999)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122043/03.01.00_60/ts_122043v030100p.pdf
|
........................................................................................................................................................5
|
122 042
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Network Identity and Timezone (NITZ); Service description, Stage 1 (3G TS 22.042 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122042/03.00.01_60/ts_122042v030001p.pdf
|
........................................................................................................................................................5
|
122 034
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); High Speed Circuit Switched Data (HSCSD); Stage 1 (3G TS 22.034 version 3.2.1 Release 1999)
|
TS
|
3.2.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122034/03.02.01_60/ts_122034v030201p.pdf
|
........................................................................................................................................................6
|
122 024
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Description of Charge Advice Information (CAI) (3G TS 22.024 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122024/03.00.01_60/ts_122024v030001p.pdf
| |
122 001
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) (3G TS 22.001 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122001/03.02.00_60/ts_122001v030200p.pdf
|
........................................................................................................................................................6
|
119 524-2
|
Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Electronic Registered Delivery Services; Part 2: Test suites for interoperability testing of Electronic Registered Delivery Service Providers
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119500_119599/11952402/01.02.01_60/ts_11952402v010201p.pdf
|
The present document defines: 1) A test suite for supporting interoperability tests within the field of Electronic Registered Delivery Services (ERD services or ERDS hereinafter) as specified in ETSI EN 319 522 parts 1 [1], 2 [2], 3 [3], 4 [4], [5] and [6]. The test suite defines test cases for the following environments: - Environments that correspond to the basic model as defined in ETSI EN 319 522-1 [1] where sender and all the entities at receiving side are subscribed to the same ERDS. - Environments that correspond to the 4-corner model as defined in ETSI EN 319 522-1 [1] where sender is subscribed to one ERDS and the entities at receiving side are subscribed to another one, and no intermediate ERDS is required for relaying ERD messages between them. - Environments that correspond to the extended model as defined in ETSI EN 319 522-1 [1] where sender is subscribed to one ERDS and the entities at receiving side are subscribed to another one, and intermediate ERDSs are required for relaying ERD messages between them. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite.
|
122 121
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Service aspects; The Virtual Home Environment (3G TS 22.121 version 3.3.0 Release 1999)
|
TS
|
3.3.0
|
http://www.etsi.org/deliver/etsi_ts/122100_122199/122121/03.03.00_60/ts_122121v030300p.pdf
|
........................................................................................................................................................5
|
122 096
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Name identification supplementary services; Stage 1 (3G TS 22.096 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122096/03.00.01_60/ts_122096v030001p.pdf
| |
119 512
|
Electronic Signatures and Infrastructures (ESI); Protocols for trust service providers providing long-term data preservation services
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.02.01_60/ts_119512v010201p.pdf
|
Based on a scoping study and survey with respect to long-term preservation techniques for digital signatures and general data documented in ETSI SR 019 510 [i.13], the present document and its companion document ETSI TS 119 511 [i.14] have been created. ETSI TS 119 511 [i.14] specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and of general data, i.e. unsigned data or signed data, using digital signature techniques. The present document complements ETSI TS 119 511 [i.14] and specifies protocols for trust service providers providing long-term data preservation services of digital signatures and of general data (i.e. unsigned data or signed data). Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document first addresses general aspects (see clause 4) such as a system architecture for preservation, which contains a preservation interface offered by the preservation service and used by the client (see clause 4.1). The preservation service may aim at different preservation goals (see clause 4.2), may or may not provide storage functionality (see clause 4.3), and provide different profiles of preservation schemes, which may implement different preservation evidence policies (see clause 4.4). In a second step, the present document specifies methods and data objects constituting a protocol between a client and a long-term data preservation service for the issuance and maintenance of evidences (see clause 5). For each call at the preservation interface it first specifies the semantics in a generic fashion and then specifies the concrete syntax of the conveyed data elements based on XML and JSON together with its binding to SOAP [i.25] and REST respectively.
|
119 612
|
Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists
|
TS
|
2.4.1
|
http://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf
|
The present document specifies a format and mechanisms for establishing, locating, accessing and authenticating a trusted list which makes available trust service status information so that interested parties may determine the status of a listed trust service at a given time. It defines the format and semantics of a TL as well as the mechanisms for accessing TLs. It also provides guidance for locating and authenticating TLs. The present document applies to European Union Member State (EU MS) trusted lists as a means to express trust service status information with regards to their compliance with the relevant provisions laid down in Regulation (EU) No 910/2014 [i.10] and in its applicable secondary legislation. In the context of non-EU countries or international organizations, scheme operators may issue trusted lists in accordance with the present document to facilitate mutual recognition of digital signatures. In addition, the present document defines requirements for relying parties to use TLs and the status information held within them.
|
119 612
|
Electronic Signatures and Infrastructures (ESI); Trusted Lists
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119600_119699/119612/01.02.01_60/ts_119612v010201p.pdf
|
The present document specifies a format and mechanisms for establishing, locating, accessing and authenticating a trusted list which makes available trust service status information so that interested parties may determine the status of a listed trust service at a given time. It defines the format and semantics of a TL as well as the mechanisms for accessing TLs. It also provides guidance for locating and authenticating TLs. The present document applies to European Union Member State (EU MS) trusted lists as a means to express trust service status information with regards to their compliance with the relevant provisions laid down in Regulation (EU) No 910/2014 [i.10] and in its applicable secondary legislation. In the context of non-EU countries or international organizations, scheme operators may issue trusted lists in accordance with the present document to facilitate mutual recognition of digital signatures. In addition, the present document defines requirements for relying parties to use TLs and the status information held within them.
|
119 534-2
|
Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Registered Electronic Mail Services; Part 2: Test suites for interoperability testing of providers using same format and transport protocols
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119500_119599/11953402/01.02.01_60/ts_11953402v010201p.pdf
|
The present document defines: 1) A test suite for supporting interoperability tests within the field of Registered Electronic Mail (REM hereinafter) as specified in ETSI EN 319 532 parts 1 [3], 2 [4], 3 [5] and 4 [6]. The test suite defines test cases for the following environments: - Environments that correspond to the basic model as defined in ETSI EN 319 532-1 [3] where sender and all the entities at receiving side are subscribed to the same REMS. Test cases are defined for REMSs operating Store&Forward and for REMSs operating Store&Notify styles. - Environments that correspond to the 4-corner model as defined in ETSI EN 319 532-1 [3] where sender is subscribed to one REMS and the entities at receiving side are subscribed to another one, and no intermediate REMS is required for relaying REM messages between them. Test cases are defined for covering the three possible different combinations of styles, namely Store&Forward to Store&Forward, Store&Forward to Store&Notify, and Store&Notify to Store&Forward. - Environments that correspond to the extended model as defined in ETSI EN 319 532-1 [3] where sender is subscribed to one REMS and the entities at receiving side are subscribed to another one, and intermediate REMSs are required for relaying REM messages between them. Test cases are defined for covering two different combinations of styles, namely Store&Forward to Store&Forward to Store&Forward, Store&Forward to Store&Notify to Store&Forward. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite.
|
119 534-1
|
Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Registered Electronic Mail Services; Part 1: Testing conformance
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119500_119599/11953401/01.02.01_60/ts_11953401v010201p.pdf
|
The present document defines the set of checks to be performed for testing conformance in the provision of Registered Electronic Mail Services against the specific technical requirements defined in ETSI EN 319 532-3 [1] and against technical requirements for the provision of the service defined in ETSI EN 319 532-1 [2]. More specifically, the present document defines test assertions for testing conformance regarding: 1) The construction of MIME and SMIME headers (clause 5) and bodies (clause 6) in ETSI EN 319 532-3 [1]. 2) The construction of REM messages (clause 7). 3) The generation of digital signatures in REM messages and ERDS evidence (clause 8). 4) Some aspects of the Common Service Interface (clause 9). 5) The structure and contents of ERDS evidence (clause 10). 6) Relevant aspects of the provision of the service, namely: the generation of ERDS evidence following certain events, and the security measures in the relevant interfaces defined in ETSI EN 319 532-3 [1], clause 11. The present document does not define the checks to be performed for testing conformance in the provision of Registered Electronic Mail Services against technical requirements defined in none of the technical specifications on which ETSI EN 319 532-3 [1] is built.
|
119 524-1
|
Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Electronic Registered Delivery Services; Part 1: Testing conformance
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119500_119599/11952401/01.02.01_60/ts_11952401v010201p.pdf
|
The present document defines the set of checks to be performed for testing conformance in the provision of Electronic Registered Delivery Services against the specific technical requirements defined in ETSI EN 319 522-3 [3], ETSI EN 319 522-4-1 [4] and ETSI EN 319 522-4-2 [5]. More specifically, the present document defines test assertions for testing conformance regarding: 1) The structure and contents of ERDS evidence as defined in ETSI EN 319 522-3 [3] (clause 6). 2) The structure and contents of new metadata defined in ETSI EN 319 522-3 [3] (clause 7). 3) The construction of AS4 ERDS messages (clause 8). 4) The generation of digital signatures in ERDS messages and ERDS evidence (clause 9). 5) Some aspects of the Common Service Interface (clause 10). 6) Relevant aspects of the provision of the service, namely: the generation of ERDS evidence following certain events and the security measures in the relevant interfaces defined in ETSI EN 319 522-1 [1] (clause 11). The present document does not define test assertions for testing conformance in the provision of Electronic Registered Delivery Services against technical requirements defined outside of any of the parts of ETSI EN 319 522 [1] to [6], namely, requirements for: AS4 [15], Business Document Metadata Service Location Version 1.0 (BDXL) [17], Service Metadata Publishing (SMP) Version 1.0 (SMP) [18] and digital signatures that are defined in their respective specifications.
|
119 614-1
|
Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Trusted Lists; Part 1: Specifications for testing conformance of XML representation of Trusted Lists
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of Trusted Lists as specified in ETSI TS 119 612 [1]. Checks specified by the present document are exclusively constrained to elements specified by ETSI TS 119 612 [1], certain elements defined in ETSI TS 101 903 [2], and certain elements specified in XMLSig [3]. Regarding XML elements, the present document explicitly differentiates between structural requirements that are defined by the different XML Schemas where the tested elements are defined, and the rest of the requirements specified by ETSI TS 119 612 [1]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set includes tests on the correctness of the structure of all the elements specified by the XML Schemas associated with ETSI TS 119 612 [1].
|
122 083
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Waiting (CW) and Call Holding (HOLD); Supplementary Services - Stage 1 (3G TS 22.083 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122083/03.00.01_60/ts_122083v030001p.pdf
| |
119 495
|
Electronic Signatures and Trust Infrastructures (ESI); Sector Specific Requirements; Certificate Profiles and TSP Policy Requirements for Open Banking
|
TS
|
1.7.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119495/01.07.01_60/ts_119495v010701p.pdf
|
The present document: 1) Specifies requirements for qualified certificates, or other non-EU schemes which provide equivalent assurance based ETSI best practices, for electronic seals and website authentication, to be used by payment service providers in order to meet needs of Open Banking including the EU PSD2. These profiles are based on ETSI EN 319 412-1 [1], ETSI EN 319 412-3 [3], ETSI EN 319 412-4 [4], IETF RFC 3739 [7] and ETSI EN 319 412-5 [i.6] (by indirect reference). 2) Specifies additional TSP policy requirements for the management (including verification and revocation) of additional certificate attributes as required by the above profiles. These policy requirements extend the requirements in ETSI EN 319 411-2 [5]. 3) Specifies specific requirements for EU use of the qualified certificates for electronic seals and website authentication, to meet the requirements of the EU PSD2 Regulatory Technical Standards (RTS) [i.3]. Certificates for electronic seals can be used for providing evidence with legal assumption of authenticity (including identification and authentication of the source) and integrity of a transaction. Certificates for website authentication can be used for identification and authentication of the communicating parties and securing communications. Communicating parties can be payment initiation service providers, account information service providers, payment service providers issuing card-based payment instruments or account servicing payment service providers. The identifier for the Competent Authority and its country (see clause 5.2.3) can be used to identify the applicable legislation. It can be determined whether a country's' national legislation follows the EU PSD2 Directive (Directive (EU) 2015/2366 [i.2]), and hence whether the RTS [i.3] applies, using the EBA list of NCA identifiers as identified in Annex D. The requirements in clauses 5 and 6 for the certificate profile and policy are common to both EU PSD2 and non- EU Open Banking certificates. The present document identifies information for Open Banking that is provided by a regulatory authority recognized through regulations as competent for providing such information. In the case of EU PSD2 this information is provided through a national register operated by the NCA or a register operated by the European Banking Authority. In addition, the TSP may provide services to the Competent Authority to enable revocation of certificates based on information provided by competent authority. The present document places no requirements on the operation of Competent Authorities providing information for Open Banking.
|
119 471
|
Electronic Signatures and Trust Infrastructures (ESI); Policy and Security requirements for Providers of Electronic Attestation of Attributes Services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119471/01.01.01_60/ts_119471v010101p.pdf
|
The present document specifies policy and security requirements for electronic attestation of attributes trust service providers and the attestation of attributes services they provide. More specifically the present document specifies policy and security requirements on attributes issuance and validation of EAA by the trust service provider.
|
119 461
|
Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service components providing identity proofing of trust service subjects
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119461/02.01.01_60/ts_119461v020101p.pdf
|
The present document specifies policy and security requirements for trust service components providing identity proofing of trust service subjects. Such a trust service component can be provided by the Trust Service Provider (TSP) itself as an integral part of the trust service or by a specialized Identity Proofing Service Provider (IPSP) acting as a subcontractor to the TSP. The term "trust service component" is used because identity proofing is not considered as a trust service on its own but as a component of the trust service for which the identity proofing is done. The present document provides requirements for two Levels of Identity Proofing (LoIP), Baseline and Extended. These LoIPs aim to support identity proofing for ETSI trust services standards such as ETSI EN 319 411-1 [i.7], ETSI EN 319 411-2 [i.8] and ETSI EN 319 521 [i.12]. The present document also provides requirements to enhance an identity proofing from Baseline LoIP to Extended LoIP when the Baseline LoIP has been reached by use of electronic Identification means (eID) at Level of Assurance (LoA) 'substantial' according to the amended eIDAS regulation [i.25] or a similar LoA based on a comparable assurance level framework. The present document aims at supporting identity proofing in European and other regulatory frameworks. Specifically, but not exclusively, the Baseline LoIP aims to support identity proofing for qualified certificates as defined in Regulation (EU) No 910/2014 [i.1] (the original eIDAS regulation) Article 24.1, while the Extended LoIP aims to support identity proofing for qualified certificates and qualified attestations of attributes as defined in Articles 24.1, 24.1a, and 24.1b of the amended eIDAS regulation [i.25]. The present document aims to meet the requirements of the original eIDAS regulation [i.1] by the requirements in clause C.2 and the requirements of the amended eIDAS regulation [i.25] by the requirements in clause C.3. The present document is intended to be applicable for reference from an implementing act according to Article 24.1c of the amended eIDAS regulation [i.25], setting out minimum technical specifications, standards and procedures with respect to the verification of identity and attributes in accordance with Articles 24.1, 24.1a, and 24.1b of the amended eIDAS regulation [i.25]. The present document aims to meet the requirements of Article 44 of the aforementioned regulations on identity proofing for qualified electronic registered delivery services by the requirements in clause C.4. eIDAS has no specific requirements for identity proofing for other qualified trust services. The present document can be used by Conformity Assessment Bodies (CAB) as the basis for confirming that an organization is trustworthy and reliable in its identity proofing process. NOTE 1: See ETSI EN 319 403-1 [i.6] for guidance on the assessment of TSP processes and services. NOTE 2: The present document has the potential to have wider applicability than the defined scope, but any application for other purposes than trust services is out of scope.
|
119 461
|
Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service components providing identity proofing of trust service subjects
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119461/01.01.01_60/ts_119461v010101p.pdf
|
The present document specifies policy and security requirements for trust service components providing identity proofing of trust service subjects. Such a trust service component can be provided by the Trust Service Provider (TSP) itself as an integral part of the trust service or by a specialized Identity Proofing Service Provider (IPSP) acting as a subcontractor to the TSP. The term "trust service component" is used because identity proofing is not considered as a trust service on its own but as a component of the trust service for which the identity proofing is done. The present document provides requirements for two Levels of Identity Proofing (LoIP), Baseline and Extended. These LoIPs aim to support identity proofing for ETSI trust services standards such as ETSI EN 319 411-1 [i.7], ETSI EN 319 411-2 [i.8] and ETSI EN 319 521 [i.12]. The present document also provides requirements to enhance an identity proofing from Baseline LoIP to Extended LoIP when the Baseline LoIP has been reached by use of electronic Identification means (eID) at Level of Assurance (LoA) 'substantial' according to the amended eIDAS regulation [i.25] or a similar LoA based on a comparable assurance level framework. The present document aims at supporting identity proofing in European and other regulatory frameworks. Specifically, but not exclusively, the Baseline LoIP aims to support identity proofing for qualified certificates as defined in Regulation (EU) No 910/2014 [i.1] (the original eIDAS regulation) Article 24.1, while the Extended LoIP aims to support identity proofing for qualified certificates and qualified attestations of attributes as defined in Articles 24.1, 24.1a, and 24.1b of the amended eIDAS regulation [i.25]. The present document aims to meet the requirements of the original eIDAS regulation [i.1] by the requirements in clause C.2 and the requirements of the amended eIDAS regulation [i.25] by the requirements in clause C.3. The present document is intended to be applicable for reference from an implementing act according to Article 24.1c of the amended eIDAS regulation [i.25], setting out minimum technical specifications, standards and procedures with respect to the verification of identity and attributes in accordance with Articles 24.1, 24.1a, and 24.1b of the amended eIDAS regulation [i.25]. The present document aims to meet the requirements of Article 44 of the aforementioned regulations on identity proofing for qualified electronic registered delivery services by the requirements in clause C.4. eIDAS has no specific requirements for identity proofing for other qualified trust services. The present document can be used by Conformity Assessment Bodies (CAB) as the basis for confirming that an organization is trustworthy and reliable in its identity proofing process. NOTE 1: See ETSI EN 319 403-1 [i.6] for guidance on the assessment of TSP processes and services. NOTE 2: The present document has the potential to have wider applicability than the defined scope, but any application for other purposes than trust services is out of scope.
|
119 441
|
Electronic Signatures and Infrastructures (ESI); Policy requirements for TSP providing signature validation services
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119441/01.02.01_60/ts_119441v010201p.pdf
|
The present document, based on the general policy requirements specified in ETSI EN 319 401 [2], specifies policy and security requirements for signature validation services operated by a TSP. NOTE 1: Beside signature validation, other signature services, like signature creation, signature augmentation or signature preservation can also be offered by TSPs. Such services can be provided as stand-alone services or combined (e.g. augmentation can be used to support a preservation service). The present document does not provide requirements on signature services beyond validation and does not provide requirements on how to combine signature related services. NOTE 2: A distinct Technical Specification (TS) provides policy and security requirements for TSP offering signature augmentation services as a stand-alone service or in complement to one of the above-mentioned services. The present document is aimed at trust services supporting the validation of digital signatures in accordance with ETSI EN 319 102-1 [3]. It takes into account the relevant requirements for signature validation application specified in ETSI TS 119 101 [1] as they relate to TSPs. It is aimed at supporting the validation of digital signatures in European and other regulatory frameworks. NOTE 3: Specifically, but not exclusively, the present document is aimed at qualified and non-qualified trust services, supporting the validation of digital signatures in accordance with the requirements of the Regulation (EU) No 910/2014 [i.1] for validation of electronic signatures and electronic seals (both advanced and qualified). Annex B complements the requirements for signature validation service providers offering a Qualified Validation Service for qualified electronic signatures or for qualified electronic seals as specified by Regulation (EU) No 910/2014 [i.1]. NOTE 4: Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document may be used by competent bodies as the basis for confirming that an organization is trustworthy in validating digital signatures on behalf of other persons or on its own behalf. NOTE 5: See ETSI EN 319 403 [i.13] for guidance on assessment of TSP processes and services. The user's interface is outside the scope of the main TSP service. However, the present document provides in annex D recommendations for the user's interfaces (for inputting the request and to visualize the validation report). The TSP has connections with external (trust) services that can be contacted for provisioning validation information, or to relay the validation request. The present document does not put requirements on the trust service policies applied by such external services. The present document identifies specific controls needed to address specific risks associated with validation services.
|
119 432
|
Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf
|
The present document specifies protocols and interfaces applicable when the process of creating AdES digital signatures as defined by ETSI TS 119 102-1 [i.7] and/or digital signature values, as result of Data To Be Signed Representations signatures, is carried out by a distributed solution comprised of two or more systems/services/components. The present document is limited to remote server signing, i.e. the signing key is held in a remote shared service. NOTE: Remote signature creation with local signing, i.e. the signing key is held with the signer's personal device but other steps in the signature creation are carried out by means of networked services, is a possible solution but protocols for such architecture are not covered in the present document. Finally, the present document specifies two bindings, each one in a different syntax (XML and JSON), for each of the protocols mentioned above. As far as it has been possible and suitable, the protocols have re-used constructs of CSC JSON and OASIS DSS-X XML specifications. When this has not been possible the present document specifies new components semantically and also syntactically in the two formats: XML and JSON. The authorized signer's use of its key for signing requires users to provide multiple proofs of their claimed identity before being granted access to the needed set of resources. The way in which the user identity verification process is carried out by the service provider or any suggestion concerning the usage of multi-factor authentication mechanisms is out of the scope of the present document.
|
119 431-2
|
Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers; Part 2: TSP service components supporting AdES digital signature creation
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/11943102/01.02.01_60/ts_11943102v010201p.pdf
|
The present document provides policy and security requirements for Trust Service Providers (TSPs) implementing a service component supporting AdES digital signature creation. This component contains a signature creation application and is thus called Signature Creation Application Service Component (SCASC). However, it is more than just the SCA. It contains service elements around which parts of the driving application as defined in ETSI TS 119 102-1 [2] and ETSI TS 119 101 [1] can be implemented. The present document does not give restrictions on whether something is covered within a signature creation application or outside, as long as it is done by the SCASC. The present document gives no restrictions on the type of TSP implementing such a service component. The present document aims at supporting the creation of digital signatures in European and other regulatory frameworks. NOTE 1: Specifically, but not exclusively, the present document is aimed at trust services, supporting the creation of digital signatures in accordance with the requirements of the Regulation (EU) No 910/2014 [i.1] for electronic signatures and electronic seals (both advanced and qualified). Annex B contains specific requirements for SCASC in the context of Regulation (EU) No 910/2014 which aim at providing best practice requirements for the creation of advanced electronic signatures and seals based on X.509 certificates. NOTE 2: Specifically, but not exclusively, digital signatures in the present document can be used to create electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document may be used by competent bodies as the basis for confirming that an organization is trustworthy in creating AdES digital signatures. NOTE 3: See ETSI EN 319 403 [i.6] for guidance on assessment of TSP processes and services. The SCASC has connections with external (trust) services that can be contacted for example for provisioning information to be included within the signature. The present document does not put requirements on the trust service policy applied by such external services. The present document does not specify any protocol used to access the SCASC or how the SCACS can contact an SSASC or an SCDev. NOTE 4: Protocols to contact a SCASC or a SSASC are defined in ETSI TS 119 432 [i.9]. The present document identifies specific controls needed to address specific risks associated with services providing AdES signature creation.
|
119 431-1
|
Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service providers; Part 1: TSP services operating a remote QSCD / SCDev
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/11943101/01.03.01_60/ts_11943101v010301p.pdf
|
The present document specifies generally applicable policy and security requirements for Trust Service Providers (TSPs) operating a remote Signature Creation Device (SCDev). Specific requirements apply when the device is a remote QSCD as defined in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. The service consists of a server signing application and a QSCD / SCDev. The term used in the present document is Server Signing Application Service (SSAS). NOTE 1: Regulation (EU) 2024/1183 [i.11] (eIDASv2) defines the management of remote electronic signature/seal creation devices as a trust service. In addition, it introduces the qualified trust service for the management of remote qualified electronic signature/seal creation devices. The policy and security requirements are defined in terms of requirements for creation, maintenance, life-cycle management and use of signing keys used to create digital signatures. The present document is aimed to be used by independent bodies as the basis for a conformity assessment that a TSP can be trusted for operating a remote QSCD / SCDev. [i.1]. The present document supports European and other regulatory frameworks. NOTE 2: Specifically, but not exclusively, the present document is aimed at qualified and non-qualified trust service managing remote qualified and non-qualified electronic signature/seal creation devices supporting electronic signatures and electronic seals (both advanced and qualified) in accordance with the requirements of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. Annex A contains requirements specific for an SSAS in the context of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. The present document does neither specify how fulfilment of the requirements can be assessed by an independent conformity assessment body, nor requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE 3: See ETSI EN 319 403 [i.3] for guidance on assessment of a TSP's processes and services. NOTE 4: The present document references ETSI EN 319 401 [1] for general policy requirements common to all TSP services covered by ETSI standards. The present document does not specify protocols used to access the SSAS. NOTE 5: Protocols for remote digital signature creation are defined in ETSI TS 119 432 [i.4]. The present document identifies specific controls needed to address risks associated with services operating remote QSCD / SCDev.
|
124 093
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Completion of calls to Busy Subscriber (CCBS) - Stage 3 (3G TS 24.093 version 3.0.0 Release 1999)
|
TS
|
3.0.0
|
http://www.etsi.org/deliver/etsi_ts/124000_124099/124093/03.00.00_60/ts_124093v030000p.pdf
|
........................................................................................................................................................5
|
122 067
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 1 (3G TS 22.067 version 3.0.1 Release 1999)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122067/03.00.01_60/ts_122067v030001p.pdf
| |
122 066
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Support of Mobile Number Portability (MNP); Service description; Stage 1 (3G TS 22.066 version 3.2.0 Release 1999)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/122000_122099/122066/03.02.00_60/ts_122066v030200p.pdf
|
........................................................................................................................................................5
|
119 442
|
Electronic Signatures and Infrastructures (ESI); Protocol profiles for trust service providers providing AdES digital signature validation services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119400_119499/119442/01.01.01_60/ts_119442v010101p.pdf
|
The present document specifies the semantics of a protocol for requesting to a remote server (and for receiving the corresponding response) the validation of AdES digital signatures compliant with the following ETSI deliverables: ETSI EN 319 122 [2], ETSI EN 319 132 [3], ETSI EN 319 142 [4], ETSI TS 101 733 [5], ETSI TS 102 778 [9], ETSI TS 101 903 [7], ETSI TS 103 171 [8], ETSI TS 103 172 [10] and ETSI TS 103 173 [6]. The present document specifies the semantics of a second protocol for requesting the augmentation of AdES digital signatures compliant with the aforementioned ETSI deliverables. The present document also specifies the semantics of a third protocol for requesting the validation and augmentation of AdES digital signatures compliant with the aforementioned ETSI deliverables. Finally, the present document specifies two bindings, each one in a different syntax (XML and JSON), for each of the aforementioned protocols. As far as it has been possible and suitable, the protocols have re-used constructs of DSS-X core v2.0: "Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0" [1] (also identified as DSS-X core v2.0 hereinafter). The protocols define new features which are not supported by DSS-X core v2.0. NOTE 1: The protocols specified in the present document do not include components for submitting to the server ASiC containers compliant with ETSI EN 319 162-1 [i.1], ETSI EN 319 162-2 [i.2], ETSI TS 102 918 [i.3], and ETSI TS 103 174 [i.4]. They do not include either components for reporting on the validation of signatures included within an ASiC container. However, clients can always extract individual signatures and groups of signed documents from ASiC containers and prepare and submit suitable requests to the server for these individual signatures and groups of signed documents. NOTE 2: The protocols specified in the present document do not include components for submitting to the server time-stamp tokens for their verification. They do not include either components for reporting on the verification of time-stamp tokens. Protocols specified by OASIS DSS-X Technical Committees include this type of components. NOTE 3: The present document builds on a draft OASIS Committee Specification as the final OASIS specification was not available at the time of publication of the present document. The present deliverable will then be updated when the OASIS Committee Specification is formally adopted.
|
119 615
|
Electronic Signatures and Infrastructures (ESI); Trusted lists; Procedures for using and interpreting European Union Member States national trusted lists
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.02.01_60/ts_119615v010201p.pdf
|
The present document specifies procedures for using and interpreting EUMS national trusted lists when validating EU qualified trust service outputs against them (e.g. validating EU qualified certificates, EU qualified time stamps, evidences created by qualified electronic registered delivery services, EU electronic signatures or seals on EU qualified validation reports on EU qualified electronic signatures or seals).
|
119 192
|
Electronic Signatures and Infrastructures (ESI); AdES related Uniform Resource Identifier
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/119192/01.02.01_60/ts_119192v010201p.pdf
|
The present document describes the root Uniform Resource Identifier (URI) http://uri.etsi.org/ades and sub branches that allow to define URI applicable for more than one AdES signature format and/or the ASiC signature container. The present document describes how to define URIs to reference a specific version and/specific attribute/property of an AdES format. NOTE: The present document defines URIs which are not used as pointers to a specific location but are used as unique identifiers.
|
119 182-1
|
Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf
|
The present document: 1) Specifies a JSON [1] format for AdES signatures (JAdES signatures hereinafter) built on JSON Web Signatures (JWS hereinafter) as specified in IETF RFC 7515 [2]. For this, the present document: - Extends the JSON Web Signatures specified in IETF RFC 7515 [2] by defining an additional set of JSON header parameters that can be incorporated in the JOSE Header (either in its JWS Protected Header or its JWS Unprotected Header parts). Many of these new header parameters have the same semantics as the attributes/properties defined in CAdES [i.2] and XAdES [4] digital signatures. Other header parameters are defined to meet specific requirements that current JSON Web Signatures cannot meet (e.g. for explicitly referencing detached JWS Payload). These new header parameters and their corresponding types are defined in a JSON schema. - Specifies the mechanisms for incorporating the aforementioned JSON components in JSON Web Signatures [2] to build JAdES signatures, offering the same features as CAdES and XAdES in JSON syntax, and therefore fulfilling the same requirements (such as the long-term validity of digital signatures). 2) Defines four levels of JAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term. Each level requires the presence of certain JAdES header parameters, suitably profiled for reducing the optionality as much as possible. The aforementioned levels provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. EXAMPLE: An example of requirements raised in specific domains is signing HTTP messages exchanged by parties in certain environments, which require signing both the HTTP body and some specific http headers. The format specified in IETF RFC 7515 [2] does not provide any native mechanism for individually identifying a detached JWS Payload. Clause 5.2.8 of the present document defines sigD, a new JSON header parameter that allows to identify one or more detached data objects which, suitably processed and concatenated, form the detached JWS Payload. Procedures for creation, augmentation, and validation of JAdES digital signatures are out of scope. NOTE 1: ETSI EN 319 102-1 [i.3] specifies procedures for creation, augmentation and validation of other types of AdES digital signatures. The present multi-part deliverable aims at supporting electronic signatures independent of any specific regulatory framework. NOTE 2: Specifically, but not exclusively, it is the aim that JAdES digital signatures specified in the present multi-part deliverable can be used to meet the requirements of electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as defined in Regulation (EU) No 910/2014 [i.1].
|
119 172-4
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 4: Signature applicability rules (validation policy) for European qualified electronic signatures/seals using trusted lists
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917204/01.01.01_60/ts_11917204v010101p.pdf
|
The present document specifies a set of rules that aims at defining the technical requirements for determining, taking into account the EU Member States trusted lists [i.4], whether a digital signature is fit for meeting the requirements of EU qualified electronic signatures/seals in the sense of the applicable European legislation, i.e. either Directive 1999/93/EC [i.2] or Regulation (EU) No 910/2014 [i.1].
|
119 172-3
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 3: ASN.1 format for signature policies
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917203/01.01.01_60/ts_11917203v010101p.pdf
|
The present document defines an ASN.1 format of machine readable signature policies based on the building blocks that define technical constraints on digital signatures and are specified in ETSI TS 119 172-1 [i.2]. Pure signature applicability rules, directly related to procedural constraints imposed by business processes, are out of the scope of the present document which does not define ASN.1 elements for the building blocks specified in ETSI TS 119 172-1 [i.2] defining only applicability rules. For each element of the machine readable signature policy, the present document references to the semantics described in ETSI TS 119 172-2 [3] and defines the corresponding ASN.1 syntax. The present document defines elements which can be used to describe technical constraints on signature creation, signature validation, and signature augmentation. These elements are designed in a way that it is possible to generate ASN.1 documents that include components of a signature generation policy, or/and signature validation policy, and/or signature augmentation policy. An ASN.1 document conformant to the present specification, defines constraints (on generation, augmentation, validation, any combination of two of them, or the three of them) that one signature has to meet. NOTE: Complex business processes, where several digital signatures need to be managed, having to meet different set of technical constraints, will require several ASN.1 documents conformant to the present document, each one defining one of these sets of technical constraints. It is out of the scope to specify mechanisms for protecting the integrity of the machine-readable signature policy documents specified in the present document.
|
119 172-2
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 2: XML format for signature policies
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917202/01.01.01_60/ts_11917202v010101p.pdf
|
The present document defines an XML format of machine readable signature policies based on the building blocks that define technical constraints on digital signatures and are specified in ETSI TS 119 172-1 [i.2]. Pure signature applicability rules, directly related to procedural constraints imposed by business processes, are out of the scope of the present document which does not define XML elements for the building blocks specified in ETSI TS 119 172-1 [i.2] that define only applicability rules. For each element of the machine readable signature policy, the present document specifies the semantics and the how to implement it in XML syntax. The present document defines elements which can be used to describe technical constraints on signature creation, signature validation, and signature augmentation. These elements are designed in a way that it is possible to generate XML documents that include components of a signature generation policy, or/and signature validation policy, and/or signature augmentation policy. An XML document conformant to the present specification, defines constraints (on generation, augmentation, validation, any combination of two of them, or the three of them) that one signature has to meet. NOTE : Complex business processes, where several digital signatures need to be managed, having to meet different set of technical constraints, will require several XML documents conformant to the present document, each one defining one of these sets of technical constraints. It is out of the scope to specify mechanisms for protecting the integrity of the machine-readable signature policy documents specified in the present document.
|
119 172-1
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 1: Building blocks and table of contents for human readable signature policy documents
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917201/01.01.01_60/ts_11917201v010101p.pdf
|
The present document defines the building blocks of signature policy and specifies a table of contents for human readable signature policy documents.
|
119 164-5
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 5: Testing Conformance of additional ASiC containers
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916405/01.01.01_60/ts_11916405v010101p.pdf
|
The present document defines the sets of checks required for testing conformance of ASiC containers against: • ASiC containers conforming to building blocks defined in ETSI EN 319 162-1 [1] and containing extended CAdES [i.5] and extended XAdES [i.6] digital dignatures, expanding the scope of ASiC baseline containers also defined in ETSI EN 319 162-1 [1]; and • additional containers defined in ETSI EN 319 162-2 [2]. The set of checks that are common with ASiC baseline containers, are defined in ETSI TS 119 164-4 [5] and referenced when needed.
|
119 164-4
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 4: Testing Conformance of ASiC baseline containers
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916404/01.01.01_60/ts_11916404v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of ASiC containers against ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The present document does not specify checks leading to conclude whether a container is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in signatures inside the container may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a container that has been successfully tested by any tool conformant to the present document. Checks are exclusively constrained to elements specified by ASiC [1]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by ASiC [1].
|
119 511
|
Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers providing long-term preservation of digital signatures or general data using digital signature techniques
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf
|
The present document builds on the general policy requirements specified in ETSI EN 319 401 [1], specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and of general data, i.e. signed data or unsigned data, using digital signature techniques. The present document aims at supporting preservation services in different regulatory frameworks. Specifically, but not exclusively, the preservation service addressed in the present document aims at supporting qualified preservation service for qualified electronic signatures or seals as per Regulation (EU) No 910/2014 [i.2]. Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.2]. The present document addresses two main cases: 1) The preservation over long periods of time, using digital signature techniques, of the ability to validate a digital signature, of the ability to maintain its validity status and of the ability to get a proof of existence of the associated signed data as they were at the time of the submission to the preservation service even if later the signing key becomes compromised, the certificate expires, or cryptographic attacks become feasible on the signature algorithm or the hash algorithm used in the submitted signature. NOTE 1: A qualified preservation service for qualified electronic signatures or seals as per Regulation (EU) No 910/2014 [i.2] for which the status of the technical validity needs to be preserved, is covered in this case. NOTE 2: The validity status of a signature means the status of the signature that will not change over time. Such a status may be valid (TOTAL_PASSED according to ETSI EN 319 102-1 [i.6]) or invalid (TOTAL_FAILED and certain cases for INDETERMINATE according to ETSI EN 319 102-1 [i.6]). NOTE 3: "Digital signature techniques" designates techniques based on digital signatures, time-stamps or evidence records. 2) The provision of a proof of existence of digital objects, whether they are signed or not, using digital signature techniques (digital signatures, time-stamp tokens, evidence records, etc.). NOTE 4: In this case, even if the main object to be preserved is a signature, it is treated in the same way as any other file. NOTE 5: A proof of existence of digital object not using digital signature techniques is not in the scope of the present document. The present document covers different strategies for the preservation service. The applicable requirements depend on the strategy chosen by the preservation service. EXAMPLE 1: The preservation service can provide storage, no storage, or temporary storage. EXAMPLE 2: The preservation service can receive the digital signature, the signed data, the revocation information or only hash values and evidences. The present document identifies specific controls needed to address specific risks associated with preservation services. The transformation of the original data into another data object with equivalent object content and semantic to avoid the risk that the original data object/viewer system is becoming obsolete is out of the scope of the present document. ETSI ETSI TS 119 511 V1.1.1 (2019-06) 8
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.