hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.3.8.2 Mobile terminating calls | ......................................................................................................................... 9 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.3.8.2.1 CUG call with no OA indication | ....................................................................................................... 9 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.3.8.2.2 CUG call with OA indication | ............................................................................................................ 9 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.3.8.2.3 Normal call | ....................................................................................................................................... 9 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.4 Exceptional procedures or unsuccessful outcome | .............................................................................................. 9 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.4.1 Exceptional operation or unsuccessful outcome | .......................................................................................... 9 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.4.10 Roaming into networks not supporting CUG | ............................................................................................. 10 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.5 Alternate procedures | ........................................................................................................................................ 10 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6 Interactions with other Supplementary Services | .............................................................................................. 10 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.82.1 Call forwarding unconditional | .............................................................................................................. 10 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.82.2 Call forwarding on mobile subscriber busy | .......................................................................................... 11 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.82.3 Call forwarding on no reply | .................................................................................................................. 11 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.82.4 Call forwarding on mobile subscriber not reachable | ............................................................................ 11 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.83.1 Call waiting | .......................................................................................................................................... 11 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.84.1 Multi-party service | ............................................................................................................................... 11 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.6.88 Call restriction Supplementary Services | .................................................................................................... 11 |
dec4c8c5cf1e3925fd0827d92a8d928b | 122 085 | 1.7 Interworking considerations | ............................................................................................................................. 11 Annex 1 (normative): General subscription options (Per Subscriber)......................................................13 Annex 2 (normative): Originating PLMN actions on call requests on the calling user's side.................14 Annex 3 (normative): Terminating PLMN actions.....................................................................................15 Annex 4 (normative): CUG interaction with the call forwarding Supplementary Services ...................16 Annex 5 (informative): Change history........................................................................................................17 History..............................................................................................................................................................18 (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 4 3G TS 22.085 version 3.1.0 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 5 3G TS 22.085 version 3.1.0 0 Scope The present document describes the Supplementary Services belonging to the group Community Of Interest Supplementary Services. The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004. The group of Community Of Interest Supplementary Services includes one Supplementary Service: - Closed user group (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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: General on Supplementary Services". [3] TS 23.003: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [4] ITU-T Recommendation X.121: "International numbering plan for public data networks". [5] ITU-T Recommendation X.180: "Administrative arrangements for closed user groups (CUGs)". [6] TS 21.905: "Vocabulary for 3GPP Specifications". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TS 21.905. 1 Closed User Group (CUG) 1.1 Definition The Closed User Group (CUG) Supplementary Service enables subscribers, connected to a PLMN and possibly also other networks, to form closed user groups (CUGs) to and from which access is restricted. A specific user may be a member of one or more CUGs. Members of a specific CUG can communicate among each other but not, in general, with users outside the group. The ability to set up emergency calls remains unaffected. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 6 3G TS 22.085 version 3.1.0 1.2 Description 1.2.1 Service description An ISDN/MSISDN number shall identify each member of a CUG. A CUG shall be defined for one or more basic service groups. CUG members can have additional capabilities that allow them to originate calls outside the group, and/or to receive calls from outside the group. CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG, or from receiving calls from other members of the CUG. CUG shall remain unaffected when members roam to PLMNs supporting CUG. Roaming subscribers must have the same CUG facilities on the roamed-to PLMN as on the Home PLMN. When roaming to networks not supporting CUG, the CUG restrictions must be enforced. (However, where possible, the CUG facilities should be supported, see subclause 1.4.10.) Each individual subscriber may be a member of a maximum of 10 CUGs. 1.2.2 Applicability to telecommunication services The applicability of this Supplementary Service is defined in GSM 22.004 [2]. 1.2.3 Definitions MSISDN: A number conforming to the numbering plan and structure specified in TS 23.003. CUG member: A user who has subscribed to the CUG Supplementary Service and is one of the users in the group formed by a particular CUG. CUG index: A value assigned by the network to identify a CUG. CUG Interlock Code (IC): Is used by the network (not by the MS) to identify CUG membership. preferential CUG: A preferential CUG, which can be specified for each basic service group, is the nominated default CUG to be used when no explicit CUG index is received by the network. suppress preferential CUG: A user action to prohibit the use of the preferential CUG, on a per call basis. Incoming Access (IA): An arrangement which allows a member of a CUG to receive calls from outside the CUG. Outgoing Access (OA): An arrangement which allows a member of a CUG to place calls outside the CUG. suppress OA: A user action to prohibit the use of the OA subscription option, on a per call basis. Incoming Calls Barred Within A CUG (ICB): An access restriction that prevents a CUG member from receiving calls from other members of that group. Outgoing Calls Barred Within A CUG (OCB): An access restriction that prevents a CUG member from placing calls to other members of that group. CUG calls: A CUG call is a call which is restricted to a pre-defined group of users. 1.3 Normal procedures with successful outcome 1.3.1 Provision The CUG Supplementary Service shall be provided after prior arrangement with the service provider. At provision subscription options should be selected by the served mobile subscriber. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 7 3G TS 22.085 version 3.1.0 A user may be a member of several CUGs. The service provider defines the number of CUGs, up to the maximum stated in subclause 1.2.1, which can be allocated to an individual subscriber. The user shall choose one of the following subscription options for each basic service group applied to the CUG Supplementary Service. This subscription option may be provisioned on a per basic service group basis or for all basic services: - CUG calls only; - CUG with incoming access, i.e. can also receive calls, which are not subject to CUG restrictions; - CUG with outgoing access, i.e. can also make calls, which are not subject to CUG restrictions; - CUG with incoming and outgoing access, i.e. can also make and receive calls, which are not subject to CUG restrictions. A user may subscribe to one of two additional restrictions applying for each particular CUG: - incoming calls barred within a CUG; - outgoing calls barred within a CUG. The network shall provide a subscription option in order to enable the user to specify a preferential CUG, for each basic service group included in at least one of the CUG(s). The user can request that no preferential CUG exists, or that a particular one of her CUGs (or the only one if a single CUG applies) is used as a preferential CUG for the particular basic service group. If a user has the subscription option outgoing calls barred within a CUG, it is not allowed to specify that particular CUG as a preferential CUG. The subscription options are shown in Annex 1. The CUG indices shall be allocated by prior arrangement with the service provider. The choice of preferential CUG(s) shall be alterable only by service provider action upon request by the served user. 1.3.2 Withdrawal Withdrawal of the CUG Supplementary Service, membership of one or more CUGs, will be by the action of the service provider, at the request of the subscriber or CUG management, or for administrative reasons. 1.3.5 Activation The CUG Supplementary Service will be activated by the service provider as a result of provision. 1.3.6 Deactivation The CUG Supplementary Service will be deactivated by the service provider as a result of withdrawal. 1.3.7 Invocation Normal call setup procedures shall apply to calls with the CUG Supplementary Service. 1.3.8 Normal operation with successful outcome A user having neither the restriction of incoming calls barred within a CUG, nor the restriction of outgoing calls barred within a CUG can make calls to, and receive calls from, members of those CUGs of which the user is a member. Upon receipt of a call setup attempt to or from a CUG subscriber the network shall check its validity in conjunction with the access capabilities subscribed to. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 8 3G TS 22.085 version 3.1.0 On successful validation of a CUG call setup attempt the network shall attempt to establish the call to the required destination. 1.3.8.1 Mobile originating calls When originating a call, the calling user may specify a CUG index to indicate that service to a particular CUG is required. If no CUG index is given then the preferential CUG (if specified) is used by the network. The Outgoing Access (OA) capability allows CUG subscribers to make outgoing calls, which are not subject to CUG restrictions. If a user, subscribing to the CUG Supplementary Service, originates a call and enters a request for suppression of both a preferential CUG and of the OA capability but does not enter a CUG index, the call shall be rejected. If a user, subscribing to the CUG Supplementary Service and having the OA capability, originates a call and enters a CUG index (without suppressing the OA capability), while having the restriction of outgoing calls barred within that CUG, the call shall be established without any CUG information i.e. as a normal call. The originating PLMN actions are illustrated in annex 2. As a network option, the network may signal towards the calling user the CUG index in use for the current call, if this can be determined by the network. 1.3.8.1.1 A user with no preferential CUG and no OA capability If a user, subscribing to the CUG Supplementary Service, who has no preferential CUG and no OA capability, originates a call and enters a CUG index (and possibly requests suppression of a preferential CUG and/or the OA capability) the call shall be established using the CUG index provided. If no CUG index is entered the call shall be rejected. 1.3.8.1.2 A user with a preferential CUG but no OA capability If a user, subscribing to the CUG Supplementary Service, who has a preferential CUG but no OA capability, originates a call and enters no CUG information (or if she only requests suppression of the OA capability),the call shall be established using the preferential CUG. If she enters a CUG index (and possibly a request for suppression of the preferential CUG and/or the OA capability), the call shall be established using the CUG index provided. If she enters only a request for suppression of the preferential CUG, i.e. no CUG index, the call shall be rejected. 1.3.8.1.3 A user with the OA capability but no preferential CUG If a user, subscribing to the CUG Supplementary Service, who has the OA capability but no preferential CUG, originates a call and enters no CUG information (or if she only requests suppression of a preferential CUG), the call shall be established without any CUG information being sent, i.e. this is set up as a normal call. If she enters a CUG index (and possibly a request for suppression of a preferential CUG), the call shall be established using the CUG index provided and with an indication of OA allowed. If she enters both a CUG index and a request for suppression of the OA capability (and possibly a request for suppression of a preferential CUG), the call shall be established using the CUG index provided. If she enters only a request for suppression of the OA capability, i.e. no CUG index, the call shall be rejected. 1.3.8.1.4 A user with a preferential CUG and the OA capability If a user, subscribing to the CUG Supplementary Service, who has a preferential CUG and the OA capability, originates a call without any CUG information, the call shall be established using the preferential CUG and with an indication of OA allowed. If she enters a CUG index (and possibly a request for suppression of the preferential CUG), the call shall be established using the CUG index provided and with an indication of OA allowed. If she enters only a request for suppression of the OA capability, the call shall be established using the preferential CUG. If she enters only a request for suppression of the preferential CUG, i.e. no CUG index, the call shall be established without any CUG information i.e. this is set up as a normal call. If she enters both a CUG index and a request for suppression of the OA capability (and possibly a request for suppression of the preferential CUG), the call shall be established using the CUG index provided. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 9 3G TS 22.085 version 3.1.0 1.3.8.1.5 A user not subscribing to the CUG Supplementary Service If a user, not subscribing to the CUG Supplementary Service, originates a call and enters CUG information the call shall be set up as a normal call. 1.3.8.2 Mobile terminating calls If a user, with or without the IA capability, receives a CUG call and the calling user is a member of the same CUG, the incoming CUG call shall be indicated as such, towards the called Mobile Station, with the appropriate CUG index. If a user with the IA capability receives a call from a user who has not subscribed to the CUG Supplementary service, or from a user who is a member from another CUG and who is using the OA capability, the call is offered to the user as a normal incoming call. The terminating PLMN actions are illustrated in annex 3. 1.3.8.2.1 CUG call with no OA indication For a call where an interlock code is received, but not an indication of OA allowed, the following applies: If there is a match with any of the called user's CUGs, and if she does not have incoming calls barred within this CUG, the call shall be offered as a CUG call. In all other cases the call shall be rejected. 1.3.8.2.2 CUG call with OA indication For a call where both an interlock code and an indication of OA allowed is received, the following applies: If there is a match with any of the called user's CUGs, and if she does not have incoming calls barred within this CUG, the call shall be offered as a CUG call. If the above condition does not apply, and if she has incoming access allowed, the call shall be offered as a normal call. If the called subscriber does not subscribe to the CUG Supplementary Service, the call shall be offered as a normal call. In all other cases, the call shall be rejected. 1.3.8.2.3 Normal call When a normal call is received, i.e. a call without any CUG information, the following shall apply: If the called subscriber subscribes to the CUG Supplementary Service and has incoming access allowed, or if she is a normal non-CUG subscriber, the call shall be offered as a normal call. In all other cases, the call shall be rejected. 1.4 Exceptional procedures or unsuccessful outcome 1.4.1 Exceptional operation or unsuccessful outcome Upon receipt of a call setup attempt to or from a CUG subscriber, the network shall check its validity in conjunction with the access capabilities subscribed to. If an invalid request is received or the checks cannot be performed, then the network shall reject the call and return an appropriate indication to the calling user. The network shall prohibit a user with incoming calls barred within a CUG from receiving CUG calls from members of the same CUG. The network shall prohibit a user with outgoing calls barred within a CUG from making CUG calls within that CUG. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 10 3G TS 22.085 version 3.1.0 1.4.10 Roaming into networks not supporting CUG The HPLMN shall control handling of roaming, when a CUG subscriber is roaming into a network not supporting CUG, without relying on extra functionality in network entities not supporting CUG. For subscribers roaming in a PLMN not supporting CUG the following apply: 1) In the case of basic service groups not subject to CUG restrictions, incoming and outgoing calls shall be allowed as normal. 2) In the case of basic service groups subject to CUG restrictions and without incoming access, incoming calls shall not be allowed. 3) In the case of basic service groups subject to CUG restrictions and without outgoing access, outgoing calls shall not be allowed. 4) Normal incoming calls are allowed for basic service groups subject to CUG restrictions and for which the called user has incoming access allowed. 5) Outgoing calls are allowed for basic service groups subject to CUG restrictions and for which the user has outgoing access allowed. 1.5 Alternate procedures None identified 1.6 Interactions with other Supplementary Services 1.6.82.1 Call forwarding unconditional CUG restrictions shall be met between the calling user and the forwarding user. In addition, the call must not be forwarded if the CUG restrictions of the forwarding mobile subscriber forbid her to make a call attempt of the same type to the forwarded-to user. The parameters of the CUG requested by the calling user shall be used for the forwarding call, and by this means CUG restrictions shall be met between the calling user and the forwarded-to user, except for the cases stated in section b) below. Annex 4 shows under what circumstances a call shall be allowed to be forwarded. a) CUG call with no OA indication. For calls received with an IC, but no indication of OA allowed, the following is valid: If the forwarding subscriber subscribes to the CUG Supplementary Service, and if she does not have outgoing calls barred within the CUG, the call shall be forwarded with the same IC as received from the A-party. In all other cases, the call shall be rejected. b) CUG call with an indication of OA allowed. For calls received with an IC and an indication of OA allowed, the following is valid: If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is a match with any of her CUGs, and if she does not have OA allowed, and if she does not have outgoing calls barred within the CUG, then the call shall be forwarded with the same IC as received from the A-party (the indication of OA allowed shall in this case NOT be forwarded). If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is a match with any of her CUGs, and if she does have OA allowed, and if she does not have outgoing calls barred within the CUG, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed. If this forwarding subscriber has outgoing calls barred within the CUG, then the call shall be forwarded as a normal call (the CUG information shall in this case NOT be forwarded). (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 11 3G TS 22.085 version 3.1.0 If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is no match with any of her CUGs, but if she has IA allowed and OA allowed, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed (in this case the subscription option "Intra-CUG restrictions" is not relevant). If the forwarding subscriber does not subscribe to the CUG Supplementary Service, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed. In all other cases, the call shall be rejected. c) Normal call. For normal calls received the following is valid: If the forwarding subscriber subscribes to the CUG Supplementary Service, and if she does have OA allowed, then the call shall be forwarded without any CUG data. (In this case the subscription option "Intra-CUG restrictions" is not relevant.) If the forwarding subscriber does not subscribe to the CUG Supplementary Service, then the call shall be forwarded (without any CUG data). In all other cases, the call shall be rejected. 1.6.82.2 Call forwarding on mobile subscriber busy Same as the interaction with call forwarding unconditional. 1.6.82.3 Call forwarding on no reply Same as the interaction with call forwarding unconditional. 1.6.82.4 Call forwarding on mobile subscriber not reachable Same as the interaction with call forwarding unconditional. 1.6.83.1 Call waiting No interaction. If the incoming (waiting) call is a CUG call it shall be indicated as such. 1.6.84.1 Multi-party service No interaction. Multi-party calls shall be set up taking into account the CUG relationships between the controlling party and each of the remote parties. The CUG restrictions need not to be checked between remote parties. 1.6.88 Call restriction Supplementary Services The call restriction Supplementary Services, when active and operative, takes precedence over the CUG restrictions. The activation of a call restriction Supplementary Service does not affect any current CUG call. If, due to an interworking situation, signalling in the network is not able to carry the information required to provide the service, the network shall terminate the attempt and return an appropriate indication to the calling user. However, a CUG call with an OA indication shall in this case continue to be established as a normal call. The rejection of CUG calls cannot be technically guarantied in all network interconnection cases, and can only be ensured by inter-connect agreement. Management of CUG spanning over multiple networks: (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 12 3G TS 22.085 version 3.1.0 A CUG may span over several networks. In this case the responsibility for the management of this CUG is in one of these networks. NOTE: One mechanism exists for CUGs spanning over data networks only, having X.121 as the numbering plan (see ITU-T Recommendation X.180 (1988)), "Administrative arrangements for international closed user groups". (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 13 3G TS 22.085 version 3.1.0 Annex 1 (normative): General subscription options (Per Subscriber) Subscription Option Values Available Subscription to CUGs List of one or more CUG indices to the maximum stated in subclause 1.2.1. Intra CUG restrictions (for each CUG) - None designated - Incoming calls barred within a CUG - Outgoing calls barred within a CUG Applicability to Basic Services (for each CUG) - List of one or more Basic Service groups - All Basic Services Per basic service group subscription options Subscription Option Values Available Preferential CUG - None designated (NOTE) - CUG index Type of inter CUG accessibility - None designated - Outgoing access - Incoming access - Outgoing and Incoming access (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 14 3G TS 22.085 version 3.1.0 Annex 2 (normative): Originating PLMN actions on call requests on the calling user's side Information from the calling user Calling user's subscription - - - No CUG info CUG index or CUG index and suppress pref. CUG Suppress OA Suppress pref. CUG CUG index and suppress OA or CUG index and suppress OA and suppress pref CUG User without preferential CUG and without OA Reject call Establish call using CUG index provided Reject call Reject call Establish call using CUG index provided User with preferential CUG but without OA Establish call using pref CUG Establish call using CUG index provided Establish call using pref CUG Reject call Establish call using CUG index provided User without preferential CUG but with OA Establish call without any CUG info i.e. a normal call Establish call using CUG index provided and OA indicator Reject call Establish call without any CUG info i.e. a normal call Establish call using CUG index provided User with preferential CUG and with OA Establish call using pref CUG and OA indicator Establish call using CUG index provided and OA indicator Establish call using pref CUG Establish call without any CUG info i.e. a normal call Establish call using CUG index provided User without the CUG SS Normal call Normal call Normal call Normal call Normal call NOTE 1: If a CUG user enters a non-allocated CUG index the call shall be rejected. NOTE 2: If a user, subscribing to the CUG Supplementary Service and having the OA capability, originates a call and enters a CUG index (without suppressing the OA capability), while having the restriction of outgoing calls barred within that CUG, the call shall be established without any CUG information i.e. as a normal call. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 15 3G TS 22.085 version 3.1.0 Annex 3 (normative): Terminating PLMN actions This table shows the type of call request sent to the destination user or that a rejection indication is returned to the calling user, as a result of the CUG checks on the destination network side. Network actions on call requests on the called user's side Type of CUG indication M or CUG attributes of the forwarding user for requested basic service group forwarding user is a non from the NM IA not allowed IA allowed CUG user network not icb icb not icb icb CUG call with no OA M CUG call rejected CUG call rejected rejected indication NM rejected rejected CUG call with OA indication M CUG call rejected CUG call normal call normal call NM rejected normal call Normal call -- rejected normal call normal call M: match with any of the called subscriber's CUGs for the requested basic service group. NM: no match with any of the called subscriber's CUGs for the requested basic service group. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 16 3G TS 22.085 version 3.1.0 Annex 4 (normative): CUG interaction with the call forwarding Supplementary Services This table shows under what circumstances a call shall be allowed to be forwarded. Type of CUG indication M or CUG attributes of the forwarding user for requested basic service group forwarding user is a non from the NM OA not allowed OA allowed CUG user network 1) not ocb ocb not ocb ocb CUG call with no OA M CF rejected CF rejected rejected indication NM rejected rejected CUG call with OA indication M CFm 2) rejected CF CFn CF NM rejected CF 3) Normal call -- rejected CF 3) CF Abbreviations: CF: Forward call using the calling subscriber's parameters CFm: Forward call using modified calling subscriber's parameters CFn: The call is forwarded as a normal call. NOTE 1: M: match with any of the called subscriber's CUGs for the requested basic service group. NM: no match with any of the called subscriber's CUGs for the requested basic service group. NOTE 2: Only the interlock code is sent from the forwarding subscriber towards the forwarded to subscriber. NOTE 3: The subscription option outgoing calls barred within a CUG (ocb), is not relevant in this case. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 17 3G TS 22.085 version 3.1.0 Annex 5 (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.85 7.0.0 Transferred to 3GPP SA1 SA#04 22.085 3.0.0 SA#05 22.085 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. SA#06 22.085 3.0.1 001 R99 3.1.0 Editorial update for GSM/3GPP use. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 18 ETSI ETSI TS 122 085 V3.1.0 (2000-01) (3G TS 22.085 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 0.1 References | .......................................................................................................................................................... 5 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 0.2 Abbreviations | ..................................................................................................................................................... 5 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1 MultiParty Service (MPTY) | ....................................................................................................................5 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.1 Definition | ........................................................................................................................................................... 5 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.2 Description | ......................................................................................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.2.1 Description | ................................................................................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.2.1.1 Indication about multiParty status | .......................................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.2.2 Applicability to telecommunication services | ............................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.2.3 Terminology | ................................................................................................................................................. 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3 Normal procedures with successful outcome | ..................................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.1 Provision | ...................................................................................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.2 Withdrawal | ................................................................................................................................................... 6 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.5 Activation | ..................................................................................................................................................... 7 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.6 Deactivation | ................................................................................................................................................. 7 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.7 Invocation | ..................................................................................................................................................... 7 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8 Normal operation with successful outcome | ................................................................................................. 7 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.1 Beginning the multiParty call | ................................................................................................................. 7 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.2 Managing an active multiParty call | ........................................................................................................ 7 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.3 Managing a held multiParty call | ............................................................................................................. 8 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.4 Managing a single call and a MPTY | ...................................................................................................... 8 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.4.1 Single active call | ............................................................................................................................... 8 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.4.2 Active MPTY and held call | .............................................................................................................. 8 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.3.8.5 Remote parties in a Multi-Party Call | ...................................................................................................... 9 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.4 Exceptional procedures or unsuccessful outcome | .............................................................................................. 9 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.5 Alternate procedures | .......................................................................................................................................... 9 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6 Interactions with other Supplementary Services | ................................................................................................ 9 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.81.3 Connected line identification presentation | ............................................................................................. 9 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.82.1 Call forwarding unconditional | .............................................................................................................. 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.82.2 Call forwarding on mobile subscriber Busy | ......................................................................................... 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.82.3 Call forwarding on no reply | .................................................................................................................. 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.82.4 Call Forwarding on mobile subscriber not reachable | ........................................................................... 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.83.1 Call waiting | .......................................................................................................................................... 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.83.2 Call hold | ............................................................................................................................................... 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.84.1 Multi-party service | ............................................................................................................................... 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.85.1 Closed user group | ................................................................................................................................. 10 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.88.1 Barring of all outgoing calls | ................................................................................................................. 11 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.88.2 Barring of outgoing international calls | ................................................................................................. 11 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country | .................. 11 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.88.6 Barring of incoming calls | ..................................................................................................................... 11 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country | ........................................ 11 |
64af3f064009d4e29f736a341058c0d4 | 122 084 | 1.7 Interworking considerations | ............................................................................................................................. 11 Annex A (informative): Change history.......................................................................................................12 History..............................................................................................................................................................13 (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 4 3G TS 22.084 version 3.0.1 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 5 3G TS 22.084 version 3.0.1 0 Scope The present document describes the Supplementary Services belonging to the group MultiParty Supplementary Services. The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004. The group of Supplementary Services MultiParty Supplementary Services consists of one Supplementary Service: - MultiParty service (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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004General on Supplementary Services". [3] TS 22.030: Man-Machine Interface (MMI) of the Mobile Station (MS)". [4] TS 22.083: Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". [5] TS 22.085 Closed User Group (CUG) Supplementary Services - Stage 1".. [6] TS 21.905: "Vocabulary for 3GPP Specifications" 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TS 21.905. 1 MultiParty Service (MPTY) 1.1 Definition This Supplementary Service provides a mobile subscriber with the ability to have a multi-connection call, i.e. a simultaneous communication with more than one party. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 6 3G TS 22.084 version 3.0.1 1.2 Description 1.2.1 Description A precondition for the multi-party service is that the served mobile subscriber is in control of one active call and one call on hold, both calls having been answered. In this situation the served mobile subscriber can request the network to begin the multiParty service. Once a multiParty call is active, remote parties may be added, disconnected or separated (i.e. removed from the multiParty call but remain connected to the served mobile subscriber). The maximum number of remote parties is 5. 1.2.1.1 Indication about multiParty status Notification shall be sent towards the served mobile subscriber and all the remote parties in a multiParty call at the invocation of this Supplementary Service. In addition, a notification shall always be sent towards all remote parties (i.e. not towards the served mobile subscriber) every time a new party is added to the multiParty call. Notifications shall also be sent to remote parties when they are put on hold and when they are retrieved in accordance with normal Call Hold procedures. In the case where a previously private communication is added again to the multiParty call, a notification shall be sent towards all remote parties. NOTE: During an interim period of time, some networks might not support the sending of the notifications to the remote parties. 1.2.2 Applicability to telecommunication services The applicability of this Supplementary Service is defined in TS 22.004. 1.2.3 Terminology Served Mobile Subscriber During the invocation and active phase, the service is under the control of the served mobile subscriber, i.e. the one who has subscribed to the service. Remote Party Any participant in the multiParty call who is not the served mobile subscriber. 1.3 Normal procedures with successful outcome 1.3.1 Provision This Supplementary Service is provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not to any subset of these BS. The provision of the Call Hold Supplementary Service is also required. 1.3.2 Withdrawal Withdrawal of the service is made by the service provider upon request by the subscriber or for service provider reasons. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 7 3G TS 22.084 version 3.0.1 1.3.5 Activation The Supplementary Service shall be activated by the service provider as a result of provision. 1.3.6 Deactivation The Supplementary Service shall be deactivated by the service provider as a result of withdrawal. 1.3.7 Invocation Multi-Party service will be invoked by the served mobile subscriber by use of a control procedure, as defined in TS 22.030. 1.3.8 Normal operation with successful outcome Only the served mobile subscriber shall be able to add remote parties to the multiParty call. 1.3.8.1 Beginning the multiParty call When the served mobile subscriber invokes multiParty service from the precondition defined in Section 1.2.1, the network joins the active call and the call on hold together into a multiParty call in which the served mobile subscriber and the remote parties can all communicate with one another. 1.3.8.2 Managing an active multiParty call During an active multiParty call, the served mobile subscriber shall be able to: (i) Add another remote party, to which a private communication has been established using the same procedures as in Section 1.3.8.1, if the number of remote parties does not then exceed the maximum number allowed, which results in an active multiParty call. A "MPTY invoke" notification shall be sent towards all remote parties. A Retrieve notification (according to TS 22.083) shall be sent towards all previously held remote parties. (ii) Put the connection to multiParty call on hold, i.e. place her connection to the multiParty call on hold (and typically later retrieve it). The served mobile subscriber may make an enquiry call (e.g. to a potential new remote party) or process a Call Waiting request from this state. While the multiParty call is on hold the remaining remote parties in the multiParty call can have communication with each other. As a result of this scenario, the enquiry call or the accepted waiting call can be added to the multiParty call or released. If the call is released by the served mobile subscriber or by the remote party, the served mobile subscriber is in control of a held multiParty call. A Hold notification (according to TS 22.083) shall be sent towards all remote parties. (iii) Separate a remote party: Explicitly choose one remote party to have a private communication with. This results in that remote party being removed from the multiParty call which is placed on hold, and the conversation between the served mobile subscriber and the designated remote party being a normal active call (see NOTE 1). The remaining remote parties may have communication with each other in this state. As a result of this scenario the private communication can be added again to the multiParty call or released. If the private call is released by the served mobile subscriber or by the remote party, the served mobile subscriber is in control of a held multiParty call. A Hold notification (according to TS 22.083) shall be sent towards all remote parties, except the designated remote party to which a private communication was established. (iv) Terminate the entire multiParty call. When the served mobile subscriber releases, this is interpreted as a request for termination of the entire multiParty call even if there are calls on hold. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 8 3G TS 22.084 version 3.0.1 No further notification shall be sent. (v) Disconnect a remote party: Explicitly release the remote parties on a one at a time basis (see NOTE 1). In the case when no remote parties remain, the multiParty call is terminated. NOTE 1: If the served mobile subscriber has a private communication with one of the remote parties and this remote party disconnects or is disconnected a notification is sent towards the served mobile subscriber that she has a multiParty call on hold. The notification about the held multiparty call towards the served mobile subscriber is given by the MS, not by the network. 1.3.8.3 Managing a held multiParty call During a held multiParty call the served mobile subscriber shall be able to: 1) Retrieve the held multiParty call, which results in an active multiParty call. 2) Initiate a new call. 3) Process a Call Waiting request. 4) Disconnect the held multiParty call. All calls belonging to the multiParty call shall be released. 5) Disconnect a single remote party. During a held multiParty call the served mobile subscriber shall NOT be able to: Retrieve a single remote party. 1.3.8.4 Managing a single call and a MPTY 1.3.8.4.1 Single active call If the served mobile subscriber is connected to a single active call (regardless whether it is a private communication or a new initiated call) and has a MPTY on hold, she is able to: 1) Disconnect the single active call. 2) Disconnect the held MPTY. 3) Disconnect both. All calls, even if they are on hold, shall be released. 4) Join the single active call and the held MPTY together. This would result in an active MPTY, except if the number of remote parties exceeds the number allowed. A "MPTY invoke" notification shall be sent towards all remote parties. A Retrieve notification (according to GSM 02.83) shall be sent towards the previously held remote party. 5) Alternate between both calls. 1.3.8.4.2 Active MPTY and held call If the served mobile subscriber is connected to a active MPTY and has a single call on hold, she is able to: 1) Disconnect the active MPTY. 2) Disconnect the single held call. 3) Disconnect both. All calls, even if they are on hold, shall be released. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 9 3G TS 22.084 version 3.0.1 4) Join the single held call and the active MPTY together. This would result in an active MPTY, except if the number of remote parties exceeds the number allowed. A "MPTY invoke" notification shall be sent towards all remote parties. A Retrieve notification (according to TS 22.083) shall be sent towards all previously held remote parties. 5) Alternate between both calls. If the served mobile subscriber is connected to a active Multi Party call and has a single call on hold, a request for establishing a private communication will be rejected by the network. (Because this would lead to an active call and two calls on hold, which is not supported according to the Call Hold Supplementary Service). An indication will be given to the served mobile subscriber with the reason for failure. 1.3.8.5 Remote parties in a Multi-Party Call Any of the remote parties shall be able to: a) Put her connection to the multiParty call on hold (and typically later retrieve it). The requirements of the Call Hold service then apply; b) Release from the multiParty call. If a remote party releases and no remote party then remains, the requirements of the normal call release procedures then apply. 1.4 Exceptional procedures or unsuccessful outcome If a served mobile subscriber attempts to invoke multiParty service and the network cannot accept that request, the request will be rejected and an indication will be given to the served mobile subscriber with a reason for denial. Some possible reasons for rejection are: - service not subscribed; - resources cannot be allocated; - conflicting situation with other Supplementary Services; - calls are not in appropriate state (e.g. one or more calls are not answered or are in the process of being cleared); - service not supported by the LPLMN. If the service provider cannot satisfy the request to add a further remote party (e.g. if the multiParty call has been cleared or if the maximum number of remote parties allowed has already been reached) the served mobile subscriber shall receive an indication that the request is denied, with the reason for failure. If the radio path of the served mobile subscriber is lost permanently for any reason, the multiParty call shall be released. 1.5 Alternate procedures None identified. 1.6 Interactions with other Supplementary Services 1.6.81.3 Connected line identification presentation Remote parties in an existing multiParty call who have subscribed to connected line number identification presentation will not receive a new remote party's number whenever a served mobile subscriber adds a new remote party to the multiParty call. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 10 3G TS 22.084 version 3.0.1 1.6.82.1 Call forwarding unconditional No interaction, the following text shall give a clarification. Calling subscriber: If a calling subscriber attempts to establish a multiParty call to a subscriber with call forwarding unconditional active and operative, the forwarded-to subscriber will be alerted and can be added to the conference. Forwarded-to subscriber: A forwarded-to subscriber can establish a multiParty call using an existing forwarded call as one of the multiParty connections. 1.6.82.2 Call forwarding on mobile subscriber Busy No interaction, the following text shall give a clarification. Calling subscriber: If a calling subscriber attempts to establish a multiParty call to a subscriber with call forwarding on mobile subscriber busy active and operative, and the forwarding condition is met, the forwarded-to subscriber will be alerted and can be added to the conference. Forwarded-to subscriber: A forwarded-to subscriber can establish a multiParty call using an existing forwarded call as one of the multiParty connections. 1.6.82.3 Call forwarding on no reply Same as the interaction between call forwarding on mobile subscriber busy and multiParty call. 1.6.82.4 Call Forwarding on mobile subscriber not reachable Same as the interaction between call forwarding on mobile subscriber busy and multiParty call. 1.6.83.1 Call waiting No interaction. The following text is included for clarification: A user who is active on a multiParty call, either as the served mobile subscriber or as remote party, may receive an indication of a waiting call, provided that the maximum number of calls at the mobile equipment will not be exceeded. After the multiParty call has been put on hold by this user, the waiting call may be accepted by the user. 1.6.83.2 Call hold Any party involved in an active multiParty call (i.e. the served mobile subscriber or a remote party) may place the connection to the multiParty call on hold and later retrieve it. 1.6.84.1 Multi-party service It shall be possible for any remote party in a multiParty call to alternate between two different multiParty calls. Served Mobile Subscriber: The served mobile subscriber cannot control more than one multiParty call at a time. It shall not be possible to invoke multiParty service if either or both of the initial calls are active parts of one or two other multiParty calls. Multi-Party Call controlled by one of the remote parties: The network will not be required to prevent that a leg to one of the other remote parties can be part of another multiParty call controlled by that remote party. 1.6.85.1 Closed user group See TS 22.085. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 11 3G TS 22.084 version 3.0.1 1.6.88.1 Barring of all outgoing calls If barring of all outgoing calls is activated after a multiParty call is invoked, any outgoing calls in progress within that multiParty call will not be barred. Any new outgoing call is barred. 1.6.88.2 Barring of outgoing international calls Same as interworking between barring of all outgoing calls and multiParty service. 1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country Same as interaction between barring of all outgoing calls and multiParty service. 1.6.88.6 Barring of incoming calls If barring of incoming calls is activated after a multiParty call is invoked, any incoming calls in progress within that multiParty call will not be barred. Any new incoming call is barred. 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country If barring of incoming calls when roaming outside the home PLMN country is made active and operative after a multiParty call is invoked, any incoming calls in progress within that multiParty call will not be barred. Any new incoming call is barred. Interworking with non-PLMN/ISDN: If a remote party is neither a PLMN nor an ISDN subscriber, it is possible that she is not notified. Mapping of notifications: Direction ISDN to PLMN: 3PTY and CONF shall be mapped onto MPTY. Direction PLMN to ISDN: MPTY shall be mapped onto CONF. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 12 3G TS 22.084 version 3.0.1 Annex A (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.84 7.0.0 Transferred to 3GPP SA1 SA#04 22.084 3.0.0 SA#05 22.084 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 13 ETSI ETSI TS 122 084 V3.0.1 (2000-01) (3G TS 22.084 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 0.1 References | .......................................................................................................................................................... 6 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 0.2 Abbreviations | ..................................................................................................................................................... 6 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1 Call Waiting (CW) | ...................................................................................................................................6 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.1 Definition | ........................................................................................................................................................... 6 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.2 Description | ......................................................................................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.2.1 Description | ................................................................................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.2.2 Applicability to telecommunication services | ............................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.2.3 Terminology | ................................................................................................................................................. 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3 Normal procedures with successful outcome | ..................................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.1 Provision | ...................................................................................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.2 Withdrawal | ................................................................................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.5 Activation | ..................................................................................................................................................... 7 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.6 Deactivation | ................................................................................................................................................. 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.7 Invocation | ..................................................................................................................................................... 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.8 Normal operation with successful outcome | ................................................................................................. 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.8.1 Incoming call from C | .............................................................................................................................. 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.8.2 Terminating call by A or B | ..................................................................................................................... 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.3.11 Interrogation | ................................................................................................................................................. 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.4 Exceptional procedures or unsuccessful outcome | .............................................................................................. 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.4.1 Incoming call from subscriber C ignored by subscriber B | ........................................................................... 8 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.4.2 Incoming call from subscriber C is indicated as UDUB by subscriber B (or terminal B) | ............................ 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.4.3 Release by subscriber C within the specified period | .................................................................................... 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.4.4 Incoming call from subscriber C is rejected by subscriber B | ....................................................................... 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.5 Alternate procedures | .......................................................................................................................................... 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6 Interactions with other Supplementary Services | ................................................................................................ 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.82.1 Call forwarding unconditional | ................................................................................................................ 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.82.2 Call forwarding on mobile subscriber busy | ............................................................................................ 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.82.3 Call forwarding on no reply | .................................................................................................................... 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.83.2 Call hold | 1.6.83. |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 2 Call hold | ................................................................................................................................................. 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.81.1 Calling line identification presentation | ................................................................................................... 9 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.84.2 MultiParty | ............................................................................................................................................. 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.88.6 Barring of all incoming calls | ................................................................................................................ 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country | ........................................ 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.7 Interactions with other services | ....................................................................................................................... 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.7.1 Multicall | ..................................................................................................................................................... 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 1.8 Interworking considerations | ............................................................................................................................. 10 2 Call hold.................................................................................................................................................10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 2.1 Definition | ......................................................................................................................................................... 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 2.2 Description | ....................................................................................................................................................... 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 2.2.1 Description | ................................................................................................................................................. 10 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 2.2.2 Applicability to telecommunication services | ............................................................................................. 11 |
b2671064415bba1dc2cbd2c8f0018626 | 122 083 | 2.3 Normal procedures with successful outcome | ................................................................................................... 11 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.