hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.13 Advice of charge services
|
................................................................................................................................ 16
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.14 Barring of All Outgoing Calls (BAOC)
|
........................................................................................................... 16
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.15 Barring of Outgoing International Calls (BOIC)
|
............................................................................................. 16 7.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC- exHC)............................................................................................................................................................... 16
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.17 Barring of All Incoming Calls (BAIC)
|
............................................................................................................ 16
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)
|
............................. 16
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.19 Explicit call transfer
|
......................................................................................................................................... 17
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.20 Completion of calls to busy subscriber
|
............................................................................................................ 17
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.21 Customised Applications for Mobile network Enhanced Logic (CAMEL)
|
..................................................... 17
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
7.22 Support of Private Numbering Plan (SPNP)
|
.................................................................................................... 17 ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 4 3G TS 22.093 version 3.0.1
|
e36388c5c871ca9e9c179d4fdecef43c
|
122 093
|
8 Mobility aspects
|
.....................................................................................................................................17 Annex A (informative): Cross Phase compatibility ....................................................................................18 A.1 Activation of a CCBS request................................................................................................................18 A.2 CCBS Recall..........................................................................................................................................18 A.3 Interrogation ..........................................................................................................................................18 A.4 Deactivation...........................................................................................................................................18 Annex B (normative): Roaming to non-supporting networks ...................................................................19 B.1 Roaming into networks or registering in network entities not supporting CCBS..................................19 B.1.1 Subscriber A may register in a non-supporting network or network entity ..................................................... 19 B.1.2 Destination B may register in a non-supporting network entity ...................................................................... 19 Annex C (informative): Change history.......................................................................................................21 History..............................................................................................................................................................22 ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 5 3G TS 22.093 version 3.0.1 Foreword This Technical Specification has been produced by the 3GPP. This TS specifies the stage 1 description of Completion of Calls to Busy Subscriber (CCBS) from the subscriber's and user's points of view; in particular: - the procedures for normal operation with successful outcome; - the action to be taken in exceptional circumstances; - the interaction with other 3GPP supplementary services. within the 3GPP system. 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; 1 Scope The present document specifies the stage 1 description of Completion of Calls to Busy Subscriber (CCBS) from the subscriber's and user's points of view; in particular: - the procedures for normal operation with successful outcome; - the action to be taken in exceptional circumstances; - the interaction with other supplementary services; The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications. The charging principles applied to CCBS are outside of the scope of this specifcation. Any interactions with other networks not dealt with in the present document are outside the scope of the present document. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 6 3G TS 22.093 version 3.0.1 2 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 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". [4] TS 29.002: "Mobile Application Part (MAP) specification". [5] TS 22.085: "Closed User Group (CUG) Supplementary Services - Stage 1". [6] TR 21.905: "Vocabulary for 3GPP Specifications". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: CCBS supplementary service: is a service which enables a calling subscriber A, encountering a NDUB destination B, to have the call completed when the busy destination B becomes idle, without having to make a new call attempt. CCBS busy on the A side: is caused by the following condition: - while the CCBS recall timer T4 or the CCBS notification timer T10 is running or until the CCBS call is completed or the CCBS call fails. CCBS busy on the B side: is caused by the following conditions: - while the idle guard timer (T8) is running; - while there is CCBS recall pending (i.e. while the CCBS recall timer T9 is running). Subscriber A and Destination B is indicated as idle if there are no active calls, no calls on hold and no call waiting for the subscribers. Subscriber A and Destination B is indicated as not reachable if one of the conditions defined in TS 29.002 [4] apply (e.g. IMSI detach, no paging response, no location information in HLR). CCBS recall: an indication informing subscriber A that destination B is idle. CCBS call: a call set-up from subscriber A to destination B resulting from subscriber A's acceptance of a CCBS recall. CCBS request: A request by subscriber A against an NDUB destination B requesting that subscriber A be automatically informed when destination B becomes idle. The CCBS request shall be held in a CCBS queue pending the correct conditions for the CCBS request to be completed. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 7 3G TS 22.093 version 3.0.1 Destination B: the entity addressed in the original call set up. Subscriber A: the subscriber that originated the call, activated a CCBS request and is uniquely identifiable for CCBS recall. Suspended CCBS request: a CCBS request which cannot be served even if destination B is idle, because subscriber A is CCBS busy, not reachable or is not idle and ignores the CCBS recall. Resumed CCBS request: a CCBS request which was suspended before and has become not suspended as a result of subscriber A becoming idle, not CCBS busy or reachable again. Automatic deactivation: an action by the network resulting in removal of all reference to a CCBS request without informing the subscriber. Automatic deactivation is performed after a successful CCBS procedure or for exceptional situations. Timers at the originating side (A): CCBS retention timer (T1): this timer specifies the amount of time that the network retains the call information when the call encounters busy. The value shall be greater than 15 seconds. The upper limit of the CCBS retention timer is a network option. CCBS service duration timer (T3): the maximum time the CCBS request will be active within the network. The value of this period is a network option, in the range of 15 to 45 minutes. CCBS recall timer (T4): the maximum time the network will wait for a subscriber A response to a CCBS recall when subscriber A is idle. The value of this timer is a network option and shall be in the range 20 to 30 seconds. CCBS notification timer (T10): the maximum time the network will wait for a subscriber A response to a CCBS recall when subscriber A is not idle and not CCBS busy. The value of the timer is a network option and shall be in the range 20 to 30 seconds. CCBS resume timer (T11): the timer started as soon as a suspended CCBS request is resumed, making sure only one CCBS request is becoming resumed at a time. Duration of the timer shall allow a CCBS recall resulting from the destination side CCBS queue being processed. The value of the timer is a network option and shall be in the range 20 to 25 seconds. Timers at the terminating side (B): CCBS service duration timer (T7): is the timer which specifies the maximum length of time the CCBS request will be held within the network. The value of this period is a network option shall be greater than 45 minutes. Destination B idle guard timer (T8): the time the network will wait after destination B has become idle before initiating a "CCBS recall" to subscriber A. The value of this timer is a network option and shall be in the range 0 to 15 seconds. NOTE 1: This timer enables destination B to initiate a call before any notification is given to subscriber A that destination B has become idle and prevents destination B to receive incoming calls. CCBS recall B timer (T9): is the timer, which supervises the CCBS recall establishment on the B-side. The value is a network option and shall be shall be in the range of 40 to 55 seconds. NOTE 2: This timer prevents destination B from receiving other incoming calls than from subscriber A. NOTE 3: The timer values may vary from one PLMN to another and thus give the subscriber a slightly different perception of the service as she roams between PLMN’s. 3.2 Abbreviations For the purposes of the present document the following abbreviations apply: CCBS Completion of Calls to Busy Subscriber NDUB Network Determined User Busy Additional abbreviations may be found in GSM 01.04 [1] and TR 21.905 [6]. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 8 3G TS 22.093 version 3.0.1 4 Description When subscriber A encounters a Network Determined User Busy (NDUB) destination B, subscriber A can request the CCBS supplementary service (i.e. activate a CCBS Request against destination B). The network will then monitor the wanted destination B for becoming idle. When the wanted destination B becomes idle, then the network will wait a short time in order to allow destination B to make an outgoing call. If destination B does not make any outgoing call within this time, then the network shall automatically recall subscriber A. When subscriber A accepts the CCBS recall, within a defined time, then the network will automatically generate a CCBS call to destination B. CCBS has to be supported by the originating, as well as by the terminating network. 4.1 Applicability to telecommunications services The applicability of the CCBS supplementary service is defined in TS 22.004 [2]. 5 Normal procedures with successful outcome 5.1 Provision 5.1.1 Subscriber A The CCBS supplementary service shall be provided to subscriber A after prior arrangement with the service provider. This supplementary service is provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BSs. 5.1.2 Subscriber B Subscriber B is the user of destination B and is not provided with the CCBS supplementary service. However, if provided by the network operator/service provider as an option, subscriber B may elect not to be a target of CCBS requests. In this case, the size of her destination B CCBS queue shall be reduced to zero length by the service provider. Only the service provider may subsequently change the destination B CCBS queue length on demand of subscriber B. 5.2 Withdrawal The CCBS supplementary service shall be withdrawn at the customer's request or for administrative reasons. At the same time, all outstanding CCBS requests shall be automatically deactivated. 5.3 Registration Not applicable. 5.4 Erasure Not applicable. 5.5 Activation The CCBS service shall be activated as a result of provisioning. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 9 3G TS 22.093 version 3.0.1 A CCBS request shall be activated by the mobile subscriber on a per-call basis by a control procedure as described in TS 22.030 [3]. When subscriber A encounters a NDUB destination B, the network shall retain the call information for a period defined by the CCBS retention timer (T1), and inform subscriber A that CCBS is possible when the following set of conditions apply: - subscriber A has the CCBS supplementary service provisioned; - the call failure reason is either "user busy or "no circuit/channel available"; - CCBS is available (as determined by network B as described below). During this time subscriber A can activate the CCBS request. CCBS is available at network B, when the following set of conditions apply: - network B supports the CCBS supplementary service; - destination B is found to be NDUB; and - the maximum length of destination B's CCBS queue is greater than zero. If the network accepts the activation of a CCBS request the network shall register the call information in the original call request, and subscriber A shall be informed that the activation was successful. When the activation of a CCBS request is accepted the CCBS service duration timers (T3 and T7) are started. The network shall monitor destination B for destination B becoming idle. Subscriber A can have a limited number of CCBS requests outstanding. This limit is a network option (with a maximum value of 5). The CCBS requests can be to different destination Bs, or can be to the same destination B with different basic service requirements. Destination B can have a limited number of incoming CCBS requests outstanding. This limit is a network option (with a maximum value of 5). The requests can be from different subscriber As, or can be from the same subscriber A with different basic service requirements. Having activated a CCBS, subscriber A can originate calls and receive calls as normal. 5.6 Deactivation The CCBS supplementary service shall be deactivated as a result of withdrawal. A previous CCBS request activation shall be deactivated by the mobile subscriber by a control procedure as described in TS 22.030 [3]or shall be automatically deactivated after a successful CCBS procedure or for exceptional situations as described in subclause 6.4. Deactivation of a CCBS request shall result in all reference to this CCBS request (entries in A and B queue and timers) being removed from the network. Subscriber A can send the following deactivation request: a) deactivate all outstanding CCBS requests; b) deactivate one specific CCBS request. Subscriber A shall be informed that the deactivation is successful. 5.7 Invocation and operation The CCBS supplementary service shall be automatically invoked by the network after destination B has become idle. When destination B is or becomes idle or reachable and there are non-suspended CCBS requests in destination B's CCBS queue, then the network shall start the destination B idle guard timer (T8). ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 10 3G TS 22.093 version 3.0.1 When the destination B idle guard timer (T8) expires and destination B is still idle, the first non-suspended CCBS request shall be processed, provided that an entry in the destination B's CCBS queue is not currently being processed. Entries shall not be processed in parallel. This means that the CCBS recall procedure shall be started towards subscriber A, informing subscriber A that destination B is now idle and the CCBS recall B timer (T9) shall be started. If subscriber A is idle or not CCBS busy, subscriber A shall be recalled with an indication that it is a CCBS recall and with an indication of which CCBS request it applies to, and the CCBS recall timer (T4) shall be started. Optionally, the ME may use a specific alert (e.g. a tone, different from the one used for normal MT call) for the indication of a CCBS recall. If subscriber A accepts the recall before the CCBS recall timer (T4) expires, then the network shall initiate the CCBS call to destination B using the call information of the original call set-up (retained in the network). When the network receives an indication that the destination B is being informed of the CCBS call, the corresponding CCBS request shall be considered as completed. Whilst the destination B idle guard timer (T8) is running, and also whilst awaiting the CCBS call to destination B (whilst CCBS recall B timer (T9) is running), a new incoming call shall not be offered to destination B. For such incoming calls, the called user shall be considered as being NDUB and the calling user shall be informed as for basic call procedures. The CCBS requests in the destination B CCBS queue shall be processed in the order they are received, although the actual mechanism for processing the CCBS queue is outside the scope of the present document. During the processing of the destination B CCBS queue, CCBS requests which are currently suspended shall be ignored and the next entry in the CCBS queue shall be processed. If, for any reason, no CCBS call results from the processing of a CCBS request, then provided destination B is still idle, the next CCBS request in the destination B CCBS queue shall be selected for processing. This procedure shall be repeated until the processing of the destination B CCBS queue is complete. If all of the destination B CCBS queue has been processed and no CCBS call results, then processing is complete. 5.8 Interrogation Subscriber A can request the list of the CCBS requests by a control procedure as described in TS 22.030 [3].. In response to the request subscriber A shall be given a list of the addresses and basic services against which CCBS requests are outstanding. 6 Exceptional procedures or unsuccessful outcome 6.1 Registration Not applicable. 6.2 Erasure Not applicable. 6.3 Activation If the Mobile Station (MS) does not receive information from the network that CCBS is possible, the activation of a CCBS request shall be rejected. If the network cannot accept subscriber A's request to activate a CCBS request, the network shall inform subscriber A and give the appropriate reason. If the request to activate a CCBS request can not be accepted due to special situation regarding CCBS the following indications shall be given to subscriber A: ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 11 3G TS 22.093 version 3.0.1 a) short term denial: The network temporarily cannot accept subscriber A's request to activate a CCBS request. A later attempt to activate a CCBS request for the same destination B may succeed. - The maximum number of CCBS requests permitted against destination B has been reached; - Subscriber A tried to activate a CCBS request against destination B after the CCBS retention timer T1 has expired; - Subscriber A has reached the maximum number of CCBS requests permitted; - if there is an interaction with a supplementary service which temporarily prevents the activation of a CCBS request; b) long term denial: The network cannot accept subscriber A's request to activate a CCBS request and a later attempt to activate a CCBS request against the same destination B will also be rejected. - A CCBS request is not allowed against destination B i.e. because the destination B CCBS queue is set to zero; If subscriber A does not wait for the CCBS recall to a particular destination B, but makes another call to that (busy) destination B and activates another CCBS request then, the following procedures can apply: - if the two calls are identical, the original CCBS request shall be automatically deactivated and the current CCBS request shall be accepted. The current CCBS request shall be treated as new CCBS request (see subclause 5.5); NOTE: There will be no restriction how often subscriber A is allowed to activate identical requests like this. If destination B's CCBS queue is limited to a size of one, i.e. only one CCBS request is allowed to be planted against destination B, then if subscriber A re-activates CCBS request before T3 expires then no other subscriber can activate CCBS against destination B. - if the two calls are not identical, then the network shall treat this as a new CCBS request. (see subclause 5.5). In order to decide that the two calls are identical, the originating network shall only compare the basic call information, i.e. the basic service requirements, and called subscriber identity. The originating network shall check for identical CCBS requests. 6.4 Deactivation If there are no CCBS requests outstanding which meet the criteria specified in the deactivation request, the network shall inform subscriber A. 6.5 Invocation and operation If, as a result of processing the entries in the queue, all entries become either suspended or automatically deactivated, no further processing shall take place. If, while destination B is idle, a previously suspended entry is resumed, or a new entry is added to the queue, the network shall process that entry. If destination B becomes idle , the network shall process that entry. If, while destination B is still idle and no other CCBS call is awaited (CCBS Recall B timer (T9) is not running), a previously suspended entry is resumed or a new entry is added to the destination B CCBS queue, the network shall process that entry as described in subclause 5.7. 6.5.1 Exceptional situation at destination B's side: a) Destination B makes an outgoing call during the idle guard timer is running. If destination B makes an outgoing call while the destination B idle guard timer (T8) is running, then invocation of CCBS shall be deferred until destination B becomes idle again. b) destination B is NDUB upon arrival of the CCBS call. If destination B is is NDUB upon arrival of the CCBS call, then two network options exist: ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 12 3G TS 22.093 version 3.0.1 - the corresponding CCBS request shall be automatically deactivated. If subscriber A activates a CCBS request again, this activation shall be considered as a new CCBS request; or - the original CCBS request shall retain its position in the CCBS queue, and the CCBS service duration timers (T3 and T7) shall not be restarted. If subscriber A attempts to activate a CCBS request again, this shall be treated as an identical request (see subclause 6.3). NOTE: The option to retain the information of the original CCBS request can only be invoked if both the originating and the destination network support this option. It is the responsibility of networks supporting the option to retain the original CCBS request to provide interworking with those networks that do not. c) destination B is not reachable. The network may determine that destination B is not reachable: - when the network monitors destination B for destination B becoming idle; - while running the destination B idle guard timer (T8). In each of the above cases, the CCBS request shall remain in the CCBS queue until. When destination B becomes reachable, the network shall process any CCBS requests in the CCBS queue (see subclause 5.7). If subscriber A accepts the CCBS recall and destination B is not reachable, then the corresponding CCBS request shall be automatically deactivated. d) destination B rejects the CCBS call with UDUB. If destination B rejects the CCBS call using UDUB, the CCBS request shall be automatically deactivated. The network shall not offer subscriber A the opportunity to activate a CCBS request for this call again. e) supplementary service interaction on destination B's side: If a supplementary service is active and operative on destination B side which prohibits the invocation of the CCBS supplementary service (for details see also Clause 7), then the processing of the B CCBS queue shall be stopped. The outstanding CCBS requests shall remain in destination B CCBS request CCBS queue. If the supplementary service interaction ends the outstanding CCBS requests shall be processed (see subclause 5.7). f) CCBS request becomes suspended while awaiting the CCBS call: If a CCBS request becomes suspended while being processed, the network shall stop the CCBS recall timer (T9) and process the next non-suspended CCBS request. g) CCBS service duration timer (T7) expires: If the CCBS service duration timer (T7) expires and the subscriber A has not been informed that destination B is idle for that CCBS request, i.e. the CCBS recall timer (T9) is not running, then the network shall automatically deactivate the CCBS request. If the CCBS service duration timer (T7) expires after the subscriber A has been informed that destination B is idle for that CCBS request, i.e. the CCBS recall B timer (T9) is running, then the CCBS request shall not be automatically deactivated until the processing of the CCBS request is completed. h) CCBS recall B timer (T9) expires: If the CCBS recall B timer (T9) expires then the network shall automatically deactivate the CCBS request. 6.5.2 Exceptional situation at subscriber A's side: a) non-acceptance or rejection of CCBS recall when subscriber A is found to be idle. If subscriber A rejects the CCBS recall or the CCBS recall timer (T4) expires, then the CCBS request shall be automatically deactivated. If subscriber A tries to suspend the CCBS recall then the CCBS request shall be automatically deactivated. b) subscriber A is found to be not idle. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 13 3G TS 22.093 version 3.0.1 When the destination B's idle guard timer (T8) expires and subscriber A is found to be not idle, the network shall notify subscriber A and start the CCBS notification timer (T10). While the CCBS notification timer (T10) is running, subscriber A may: - Accept the CCBS recall: The subscriber A has to free up the required resources to set-up the CCBS call, e.g. by releasing the existing calls or put the existing call on hold. The CCBS recall shall then be handled in the same way as when subscriber A is idle (subclause 5.7). - Reject the CCBS notification. The network shall automatically deactivate the CCBS request. - Ignore the CCBS notification. When the CCBS notification timer (T10) expires, the network shall suspend the CCBS request if T3 is still running. If T10 expires while T3 has already expired, then the CCBS request shall be automatically deactivated. - Suspend the CCBS request . The request may later be resumed according to subclause 6.5.2.e. c) subscriber A is found to be CCBS busy. If subscriber A is CCBS busy when destination B's idle guard timer (T8) expires, the network shall suspend the CCBS request without notifying subscriber A. d) Subscriber A is not reachable. If it is identified that subscriber A is not reachable when the destination B idle guard timer expires, then the CCBS request shall be suspended until subscriber A becomes reachable again. e) If subscriber A becomes idle after being not idle or CCBS busy, or subscriber A becomes reachable again and there are one or more suspended CCBS requests in subscriber A's CCBS queue, this queue shall be processed in the following way: The first suspended CCBS request shall be resumed. The CCBS resume timer (T11) is started, provided that subscriber A’s CCBS queue holds more than one CCBS request; - If no CCBS recall results from the resume procedure before the CCBS resume timer (T11) expires, processing of subscriber A's CCBS queue shall be continued as described above until no more suspended CCBS requests are left in that queue; - If a CCBS recall results from the resume procedure, the CCBS resume timer (T11) is stopped, and the CCBS recall is treated in the normal way as described in subclause 5.7. f) CCBS service duration timer (T3) expires: - If the CCBS service duration timer (T3) expires and the subscriber A has not been informed that destination B is idle for that CCBS request, i.e. the CCBS recall timer (T4) or the CCBS notification timer (T10) are not running then the network shall automatically deactivate the CCBS request. - If the CCBS service duration timer (T3) expires and the subscriber A has been informed that destination B is idle, i.e. the CCBS recall timer (T4) or the CCBS notification timer (T10) are running, then the CCBS request shall not be automatically deactivated until the processing of the CCBS request is completed. g) CCBS recall timer (T4) expires: If the CCBS recall timer (T4) expires then the network shall automatically deactivate the CCBS request. 6.5.3 Exceptional situations in the network If the CCBS call fails for any other reason than described in subclauses 6.5.1 and 6.5.2, then subscriber A shall be informed as for the basic call procedures, and the CCBS request shall be automatically deactivated. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 14 3G TS 22.093 version 3.0.1 7 Interaction with other supplementary services 7.1 Calling line identification presentation No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. 7.2 Calling line identification restriction CLIR information from the original call, stored in the network, shall also be automatically included in the CCBS call. 7.3 Connected line identification presentation No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. 7.4 Connected line identification restriction No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. 7.5 Call Forwarding Unconditional (CFU) CCBS recalls shall never be forwarded. If subscriber A places a call to destination B and the call is forwarded to user C by the CFU supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication. If destination B activates the CFU supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network’s queue processing until the CFU supplementary service becomes deactive or quiescent or until the CCBS duration timers (T3 or T7) expire. If destination B activates the CFU supplementary service for the relevant Basic Service Group between the expiry of the destination B idle guard timer and the arrival of the CCBS call, the CCBS call shall be forwarded as a normal call. If the destination network B receives a CCBS request from the originating A network while the CFU supplementary is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial. 7.6 Call Forwarding on mobile subscriber Busy (CFB) CCBS recalls shall never be forwarded. If subscriber A places a call to destination B and the call is forwarded to user C by the CFB supplementary service and user C is busy, then any subsequent attempt to activate a CCBS request by subscriber A against destination B will be accepted. If destination B activates the CFB supplementary service after subscriber A has activated a CCBS request, then the processing of destination B's CCBS queue shall be continued. If destination B which has activated the CFB supplementary service is busy upon arrival of a CCBS call two network provider options exist with regard to the treatment of that CCBS call, i.e.: - the CCBS call shall be treated according to the exceptional procedures (destination B again busy); or - the CCBS call shall be forwarded as a normal call. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 15 3G TS 22.093 version 3.0.1 7.7 Call Forwarding on No Reply (CFNRy) CCBS recalls shall never be forwarded. If subscriber A places a call to destination B and the call is forwarded to user C by the CFNRy supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication. If destination B activates the CFNRy supplementary service after subscriber A has activated a CCBS request, then the processing of destination B's CCBS queue shall be continued. If destination B activates the call forwarding no reply supplementary service after subscriber A has activated a CCBS requestagainst destination B, then the CCBS call shall be given to destination B at the user's original location. After the no reply timer has expired at destination B the CCBS call shall be forwarded as a normal call. 7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) CCBS recalls shall never be forwarded. If subscriber A places a call to destination B and the call is forwarded to user C by the CFNRc supplementary service and user C is busy, then subscriber A shall not receive any CCBS possible indication. If destination B activates the CFNRc supplementary service after subscriber A has activated a CCBS request, then the processing of destination B's queue shall be continued. If destination B activates the CFNRc supplementary service after subscriber A has activated a CCBS request against destination B and destination B is not reachable upon the arrival of CCBS call then the CCBS call shall be forwarded as a normal call. 7.9 Call waiting If subscriber A has subscribed to the CCBS supplementary service and places a normal call to a destination B that has subscribed to the call waiting supplementary service, and the call waiting indication is given to destination B (i.e. the call is waiting), a subsequent CCBS request activation by subscriber A shall not be allowed. If the call waiting indication cannot be given at the destination B, subscriber A will receive busy indication and can activate a CCBS request against destination B. CCBS requests in the destination B CCBS queue shall only be processed if destination B is idle. A CCBS call shall be treated as a normal call with respect to call waiting, at subscriber B. 7.10 Call hold No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. 7.11 Multiparty services No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. 7.12 Closed user group Closed user group information from the original call, stored in the network, shall also be automatically included in the CCBS call. If subscriber A or destination B roam to a network not supporting CUG the call restriction procedures as described in TS 22.085 [4] shall apply after a CCBS request has been activated. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 16 3G TS 22.093 version 3.0.1 7.13 Advice of charge services No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. If subscriber A has subscribed to Advice of Charge Charging (AoCC) and if ACMmax is reached, or exceeded, and subscriber A is awaiting a CCBS recall notification, then the ME shall be informed of the CCBS recall. Subscriber A shall not be informed of the CCBS recall. The ME shall reject the CCBS recall which shall stop T4 or T10 and the corresponding CCBS request shall be deactivated. Any outstanding CCBS request shall remain in subscriber A's CCBS queue until the CCBS service duration timer (T3 or T7) expires. 7.14 Barring of All Outgoing Calls (BAOC) If the BAOC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred and the CCBS Request shall be automatically deactivated. 7.15 Barring of Outgoing International Calls (BOIC) If the BOIC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred if it is an international call and the CCBS Request shall be automatically deactivated. 7.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC) If the BOIC-exHC supplementary service becomes active and operative for subscriber A after subscriber A has activated a CCBS request, and subscriber A accepts the CCBS Recall, the CCBS call will be barred if it is an international call except to the HPLMN country and the CCBS Request shall be automatically deactivated. 7.17 Barring of All Incoming Calls (BAIC) If destination B activates the BAIC supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network’s queue processing until the BAIC supplementary service becomes deactive or until the CCBS duration timers (T3 or T7) expire. If the BAIC supplementary service is active and operative for the relevant Basic Service Group when the HPLMN B receives an interrogation to route the CCBS call, then the specific CCBS request relating to that CCBS call shall be automatically deactivated. If the destination network B receives a CCBS request from the originating A network while the BAIC supplementary service is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial. 7.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam) If destination B activates the BIC-Roam supplementary service after subscriber A has activated a CCBS request, then all the CCBS requests related to the relevant Basic Service Group shall be excluded from the destination B network’s queue processing until the BAIC supplementary service becomes deactive or quiescent or until the CCBS duration timers (T3 or T7) expire. If the BIC-Roam supplementary service becomes active and operative for the relevant Basic Service Group when the HPLMN B receives an interrogation to route the CCBS call, then the specific CCBS request relating to that CCBS call shall be automatically deactivated. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 17 3G TS 22.093 version 3.0.1 If the destination network B receives a CCBS request from the originating A network while the BIC-Roam supplementary service is active and operative for the relevant Basic Service Group, then the CCBS request shall be rejected with an indication of short term denial. 7.19 Explicit call transfer No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. 7.20 Completion of calls to busy subscriber No impact. A subscriber can be both a "subscriber A" and a "destination B" simultaneously, i.e. the same subscriber can be both the originator and the target of one or more CCBS requests. If the subscriber receives a CCBS call while that subscriber is being alerted or is awaiting completion of the CCBS call for which the subscribers is the originator, then the received CCBS call shall be treated as if the subscriber was busy again. 7.21 Customised Applications for Mobile network Enhanced Logic (CAMEL) The CCBS call shall be treated as normal originating call for the purpose of CAMEL based originating services. If a mobile originating CAMEL based service determines for a CCBS call different called party address than for the initial call, the CCBS call shall be released by the network and the corresponding CCBS request shall be automatically deactivated. There will be no interaction in case of the called party address is not changed by any CAMEL based terminating service. In case of a terminating CAMEL based service changing the called party address, then a CCBS request activation shall not be allowed. At Interrogation the network shall return the same B subscriber address as subscriber A has entered at the time of CCBS request activation. If the CSE (CAMEL Service Environment) requests a call set-up to an alternative destination after the original call set- up to destination B has encountered a busy condition and this call meets a busy destination, then any subsequent attempt to activate a CCBS request by subscriber A against destination B (the original called party) will be accepted. If the CSE (CAMEL Service Environment) requests a call set-up to an alternative destination after the original call set- up has failed for other reasons than the busy condition of destination B or was disconnected and this call meets a busy destination, then subscriber A shall not receive any CCBS possible indication.. 7.22 Support of Private Numbering Plan (SPNP) A CCBS call shall always be directed to the party originally addressed, regardless of any changes in the B party number after activation of a CCBS request. At Interrogation, the network shall return the same B subscriber address as subscriber A has entered at the time of the original call. The processing of CCBS requests shall not be affected by the mobility of subscriber A or destination B if either or both of the subscribers is a mobile subscriber. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 18 3G TS 22.093 version 3.0.1 Annex A (informative): Cross Phase compatibility Users of existing MSs (Phase 2 and possibly Phase 1) are not prevented from using the CCBS supplementary service. Existing Phase 1/Phase 2 functional signalling mechanisms and USSD shall be used to offer the service to these MSs. Networks wishing to offer this service to existing MSs are therefore required to support both functional (Phase 1/Phase 2) and stimulus signalling (USSD). A.1 Activation of a CCBS request Activation of CCBS requests by existing MSs shall be performed using USSD. The standardised MMI is defined in TS22.030 [3]. The network shall interpret the USSD string as an activation of a CCBS request. Consequently, networks which do not support USSD will not be able to offer the service to existing MSs which do not support USSD will not be able to activate a CCBS request. A.2 CCBS Recall A CCBS Recall to an existing MS shall be handled as a normal mobile terminated call using Phase 1/Phase 2 functional signalling. A.3 Interrogation Existing MSs shall use USSD to interrogate the service. The MMI is defined in TS 22.030[3]. A.4 Deactivation Existing MSs shall use USSD to deactivate the service. The MMI is defined in TS22.030 [3]. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 19 3G TS 22.093 version 3.0.1 Annex B (normative): Roaming to non-supporting networks B.1 Roaming into networks or registering in network entities not supporting CCBS This clause looks at the times when either parties involved in CCBS may roam from a supporting network entity into a non-supporting network or network entity. Consider the times when neither Subscriber A or Destination B can register in another location area. Subscriber A cannot register in another location area: a) Having received a CCBS Possible indication and while the network is awaiting the initial CCBS Request; b) Having received a CCBS Recall and while the network is awaiting acceptance of the CCBS Recall; c) During the duration of the CCBS Call. Destination B cannot register in another location area: a) During the duration of the CCBS Call; B.1.1 Subscriber A may register in a non-supporting network or network entity Whilst waiting for the CCBS Recall from Destination B If Subscriber A registers in a non-supporting entity whilst waiting for the CCBS Recall from destination B. The network shall be aware that the CCBS supplementary service is not supported and shall suspend the CCBS Request. The CCBS Request shall remain suspended until either Subscriber A registers in a supporting entity or until the service duration timer T3 expires. B.1.2 Destination B may register in a non-supporting network entity a) If destination B becomes idle after "CCBS Possible" has been sent and before a "CCBS Request" is received. If destination B is idle and has registered in a non-supporting entity when the CCBS Request arrives then the CCBS Request shall be accepted, but the handling of the destination B CCBS queue shall be frozen until the destination B registers in a supporting entity or until a service duration timer expires. b) While T8 is running. If destination B registers in a non-supporting network entity during T8, then the processing of the destination B CCBS queue shall be stopped until either destination B registers in a supporting network entity or the service duration time expires. c) After T8 expires. If Destination B registers in a non-supporting entity after having sent the CCBS Recall, then error handling will ensure that the entity informs the network that it doesn't support CCBS. However, the CCBS Call shall be allowed to continue. When the non-supporting entity receives the CCBS Call, it will not be able to inform the network that the CCBS has been completed. The only safeguard is that T9 in the network will expire, which will result in automatic deactivation of the CCBS Request from the queue. d) When a CCBS Request is suspended and before it is resumed. If destination B has registered in a non-supporting entity when the CCBS Resume arrives, then the CCBS Resume shall be treated as a CCBS Request and shall be accepted, but the handling of the destination B CCBS queue shall be frozen until destination B registers in a supporting entity or until a service duration timer expires. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 20 3G TS 22.093 version 3.0.1 ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.093 V3.0.1 (1999-10) 21 3G TS 22.093 version 3.0.1 Annex C (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.93 7.0.0 Transferred to 3GPP SA1 SA#04 22.093 3.0.0 SA#05 22.093 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) ETSI 22 ETSI ETSI TS 122.093 V3.0.1 (2000-01) (3G TS 22.093 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
1 Scope
|
........................................................................................................................................................4
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
2 References
|
................................................................................................................................................4
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
3 Abbreviations
|
...........................................................................................................................................5
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
4 Description
|
...............................................................................................................................................5 5 Unstructured SS data operations – MMI mode........................................................................................5
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.1 Mobile initiated unstructured SS data operations
|
.................................................................................................... 5
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.1.1 Initiating action at the Mobile Station (MS)
|
...................................................................................................... 5
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.1.2 Action at the network
|
......................................................................................................................................... 5
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.1.3 Mobile initiated USSD cross phase compatibility
|
............................................................................................. 6
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.1.4 Allocation of service codes (to be noted by network operators)
|
........................................................................ 6
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.2 Network initiated unstructured SS data operation
|
................................................................................................... 6
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.2.1 Initiating actions in the network
|
........................................................................................................................ 6
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.2.2 Actions at the MS
|
.............................................................................................................................................. 7
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
5.3 Network aspects of unstructured SS data operation
|
................................................................................................ 7 6 Unstructured SS data operations – application mode ..............................................................................7
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.1 General
|
.................................................................................................................................................................... 7
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.2 Mobile initiated transfer
|
.......................................................................................................................................... 7
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.2.1 Initiating action at the mobile station
|
................................................................................................................. 7
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.2.2 Action in the network
|
........................................................................................................................................ 7
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.3 Network initiated transfer
|
........................................................................................................................................ 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.3.1 Initiating action in the network
|
.......................................................................................................................... 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.3.2 Action at the mobile station
|
............................................................................................................................... 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.4 External addressing
|
................................................................................................................................................. 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.5 Charging aspects
|
...................................................................................................................................................... 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.6 Compatibility aspects
|
.............................................................................................................................................. 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.6.1 Mobile initiated transfer
|
..................................................................................................................................... 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.6.2 Network initiated transfer
|
.................................................................................................................................. 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.7 Interaction with other services
|
................................................................................................................................. 8
|
76a764a7077571c15dd73994579dbe64
|
122 090
|
6.8 Security
|
.................................................................................................................................................................... 8 Annex A (informative): Change history.................................................................................................9 History..............................................................................................................................................................10 ETSI ETSI TS 122 090 V3.1.0 (2000-03) 4 3G TS 22.090 version 3.1.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. 1 Scope The present document defines the stage 1 description of Unstructured Supplementary Service Data (USSD) for use in one or a number of Public Land Mobile Networks (PLMNs). 2 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. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: "General on supplementary services". [3] TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". [4] TS 23.038: "Alphabets and language-specific information". [5] TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding". [6] TS 21.905: "Vocabulary for 3GPP Specifications". ETSI ETSI TS 122 090 V3.1.0 (2000-03) 5 3G TS 22.090 version 3.1.0 Release 1999 3 Abbreviations For the purposes of the present document, the abbreviations listed in GSM 01.04 [1] and TS 21.905 [6] apply. 4 Description There are two modes of USSD: MMI-mode and application mode. MMI-mode USSD is for the transparent transport of MMI strings entered by the user to the network and for the transparent transport of text strings from the network that are displayed by the mobile for user information. Application mode USSD is for the transparent transport of data between the network and the mobile station. Application mode USSD is intended to be used by applications in the network and their peer applications in the MS. The communication over the radio interface takes place on the signalling channels using short dialogues with peak data throughput rate capabilities of up to approximately 600 bits/s outside of a call and 1 000 bits/s during a call. 5 Unstructured SS data operations – MMI mode 5.1 Mobile initiated unstructured SS data operations 5.1.1 Initiating action at the Mobile Station (MS) If the user enters an MMI string that, according to TS 22.030 [3], should be treated as USSD, the MS shall send this string to the network using the appropriate operation from TS 24.080 [5]. The mobile initiated operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the user. The MS may initiate an USSD Operation either during a call or out of call. 5.1.2 Action at the network A network supporting USSD shall examine the alphabet indicator. If the serving network does not recognize the alphabet indicated in the mobile initiated USSD operation, it shall send the operation to the HLR. On recognition of the alphabet, the network shall examine the contents of the string, and take appropriate action, according to the following rules, depending of the format of the message. Case a) 1, 2 or 3 digits from the set (*, #) followed by 1X(Y), where X=any number 0-4, Y=any number 0-9, then, optionally "* followed by any number of any characters", and concluding with # SEND: This case is reserved for HPLMN use. When a serving network receives such a message from a visiting subscriber, it shall pass the USSD message directly to the HPLMN. If it receives it from a home subscriber, it is up to the network to decide whether to treat it locally or to pass it to the HLR. Case b) 1, 2 or 3 digits from the set (*, #) followed by 1X(Y), where X=any number 5-9, Y=any number 0-9, then, optionally "* followed by any number of any characters", and concluding with # SEND: This case is reserved for VPLMN use. It is up to the VPLMN to decide how to treat it. Case c) 7(Y) SEND, where Y=any number 0-9: This case is reserved for HPLMN use. When a serving network receives such a message from a visiting subscriber, it shall pass the USSD message directly to the HPLMN. If it receives it from a home subscriber, it is up to the network to decide whether to treat it locally or to pass it to the HLR. ETSI ETSI TS 122 090 V3.1.0 (2000-03) 6 3G TS 22.090 version 3.1.0 Release 1999 Case d) All other formats: The visited network examines the message. If it is able, it acts upon it. Failing that, it passes the message to the HLR. If the HLR does not support the alphabet indicated, it shall inform the MS. The network shall terminate the mobile initiated operation by responding to the request from the mobile with either an error signal, or a text string indicating the outcome of the operation. The response string uses the characters available in the selected alphabet as defined in TS 23.038 [4]. If no indication to the user is required, the response string may be empty. The response to the mobile initiated USSD operation shall contain alphabet and language indicators. The selection of values for these indicators is a matter for the network operator. 5.1.3 Mobile initiated USSD cross phase compatibility In situations of incompatibility the mobile initiated USSD operation will be rejected by a non-supporting network and the attempt will fail. In this situation, if it is possible to encode the content of the USSD message in the IA5 alphabet, the MS shall attempt the operation again using the IA5 format without the alphabet and language indicators. This procedure is not applicable if an operation failure is due to alphabet support problems, services not supported or network failure problems. 5.1.4 Allocation of service codes (to be noted by network operators) Service codes for use in control of Supplementary Services are standardized by international agreement, so must not be used by PLMNs unless authorized, except for those codes allocated for PLMN use. If the message is of the format: 1, 2 or 3 digits from the set (*, #), followed by NN(N), where N=0-9, optionally followed by "* and any number of any characters", and terminating in # SEND: then NN(N) is known as the service code. Only codes specified in TS 22.030 [3] and those defined in cases a) and b) above may be used. All other values are reserved. Similarly, if the message is of the format: X(Y) SEND, where X=0-6 or 8-9 and Y=0-9: the codes X(Y) are standardized. Only codes specified in TS 22.030 [3] subclause 4.5.5 may be used. All other values are reserved. 5.2 Network initiated unstructured SS data operation 5.2.1 Initiating actions in the network At any stage while the MS is registered with a network, the network may send an unstructured string to the MS. This string contains operator determined information that is relevant to the user. If the network is unable to successfully reach the MS, then an error shall be returned to the node that originated the operation. The network initiated USSD operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the network operator. ETSI ETSI TS 122 090 V3.1.0 (2000-03) 7 3G TS 22.090 version 3.1.0 Release 1999 5.2.2 Actions at the MS If the MS is unable to process the network initiated unstructured SS data operation (e.g. the feature is not supported or the user is engaged in another MMI activity) then an error indication shall be returned to the node that originated the operation. If the alphabet indicated by the network is not supported by the MS, the MS shall inform the network. The network may explicitly indicate to the MS that a response from the user is required. In this case, the next string entered by the user shall be used as the response (and is not interpreted according to normal MMI procedures stated in TS 22.030 [3]). An MMI command shall be provided to allow the user to terminate the dialogue with a null response. The response string uses the characters available in the selected alphabet as defined in TS 23.038 [4]. The response is sent to the node that originated the operation. If the network does not indicate that a response is required, then the normal MMI procedures on the MS continue to apply. The MS shall include alphabet and language indicators in the response to the network (if any). 5.3 Network aspects of unstructured SS data operation Applications that use Unstructured SS Data Operations may be located in either the HPLMN or a roamed to VPLMN. Network applications using Unstructured SS Data Operations may: - use several Unstructured SS Data Operations (possibly a mixture of mobile initiated and network initiated) in combination as part of a dialogue with the user. Linkage between separate operations as part of a dialogue is only implemented locally in the network application and does not lead to any special mode of operation in the MS. The network initiated request for a response from the user and the corresponding response is a single operation; - act on calls in progress, or place new calls, as part of the service the application provides. Release of the connection used for an unstructured dialogue is normally the responsibility of the network and may be carried out at the request of the application using the Unstructured SS Data Operations. The user may also initiate connection release through an MMI procedure. 6 Unstructured SS data operations – application mode 6.1 General USSD supports communication between an application (handler) in the MS and a corresponding application (handler) in the network by enabling transparent transfer of binary data between the network and the MS. The applications may use USSD either during a call or out of call. Application-level addressing is out of scope of the present document. 6.2 Mobile initiated transfer 6.2.1 Initiating action at the mobile station If the MS wishes to send data to the network, it can do so using USSD. It shall be possible for the MS to send data to nodes in the VPLMN and in the HPLMN, i.e. MSC, VLR, HLR, MExE servers, CSEs and proxy servers. 6.2.2 Action in the network The serving network shall pass the received message to its destination node. If the VPLMN cannot route the message to the destination it shall forward the message to the HPLMN. ETSI ETSI TS 122 090 V3.1.0 (2000-03) 8 3G TS 22.090 version 3.1.0 Release 1999 6.3 Network initiated transfer 6.3.1 Initiating action in the network If a node in the network wishes to send data to an MS, it can do so using USSD. If the network is unable successfully to reach the MS, then an error shall be returned to the node that originated the operation. 6.3.2 Action at the mobile station The MS shall pass the message to the ME, to the SIM/USIM or to the TE as indicated in the message. 6.4 External addressing The USSD dialogue exists inside thePLMN. However, it shall be possible to transport the address of an external node in the USSD message. The address format must be standardised and support at least E.164- and IP-addresses. When addressing of an MS from an external node the address shall be an MSISDN number. The return address shall be present and in the same format the MS uses to address an external node. This mechanism for communication between thePLMN and the external node is out of scope of the present document. 6.5 Charging aspects It shall be possible to charge for the use of application mode USSD based on e.g. the destination node. Charging for the use of an application is out of scope of the present document. 6.6 Compatibility aspects 6.6.1 Mobile initiated transfer If the network does not support application mode USSD, the mobile initiated operation will be rejected and the attempt will fail. The MS shall not attempt automatic fall back to phase 1 USSD or to MMI mode USSD in case of incompatibility. Application-level recovery is outside the scope of the present document. If the network is unable to identify the destination node, it shall forward the message to the HLR. 6.6.2 Network initiated transfer If the MS is unable to process the network initiated USSD operation, then an error indication shall be returned to the node that originated the operation. 6.7 Interaction with other services The user or the network operator shall be able to prevent the use of application mode USSD during calls. The use of USSD in parallel with a circuit switched call may have a negative impact on the quality of the speech or data transmission. Application-level security is out of scope of the present document. ETSI ETSI TS 122 090 V3.1.0 (2000-03) 9 3G TS 22.090 version 3.1.0 Release 1999 Annex A (informative): Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New Jun 1999 02.90 Transferred to 3GPP SA1 8.0.0 SA#04 22.090 3.0.0 SP-05 SP-99479 S1-99636 22.090 001 R99 D Editorial changes for alignment for 3GPP 3.0.0 3.0.1 SP-07 SP-000063 S1-000048 22.090 002 R99 C UCS2 character set for MMI mode 3.0.1 3.1.0 ETSI ETSI TS 122 090 V3.1.0 (2000-03) 10 3G TS 22.090 version 3.1.0 Release 1999 History Document history V3.0.0 July 1999 Transferred to TSG SA at ETSI SMG#29. Under TSG TSG SA Change Control V3.0.1 October 1999 Inclusion of CR at SA#05 V3.1.0 March 2000 Implemented CRs approved at SA #07 11 ETSI ETSI TS 122 090 V3.1.0 (2000-03) 3G TS 22.090 version 3.1.0 Release 1999 History Document history V3.1.0 March 2000 Publication
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
1 Scope
|
........................................................................................................................................................6
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
2 References
|
................................................................................................................................................6
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
3 Definitions and Abbreviations
|
.................................................................................................................6
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
4 Description
|
...............................................................................................................................................7
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
4.1 Description
|
......................................................................................................................................................... 7
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
4.2 Applicability to telecommunication services
|
..................................................................................................... 7
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5 Normal procedures with successful outcome
|
...........................................................................................7
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.1 Provision
|
............................................................................................................................................................ 7
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.2 Withdrawal
|
........................................................................................................................................................ 7
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.3 Registration and Erasure
|
.................................................................................................................................... 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.4 Activation and Deactivation
|
.............................................................................................................................. 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.5 Invocation
|
.......................................................................................................................................................... 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.6 Interrogation
|
...................................................................................................................................................... 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7 Handling of UUS services
|
................................................................................................................................. 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.1 Activation
|
..................................................................................................................................................... 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.1.1 Service 1
|
................................................................................................................................................. 8
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.1.2 Service 2
|
................................................................................................................................................. 9
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.1.3 Service 3
|
................................................................................................................................................. 9 5.7.1.4 "UUS required" request.......................................................................................................................... 9
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.2 Invocation and operation
|
................................................................................................................................... 9
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.2.1 Service 1
|
............................................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.2.2 Service 2
|
............................................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.2.3 Service 3
|
............................................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
5.7.2.4 Charging requirements
|
......................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
6 Exceptional procedures or unsuccessful outcome
|
.................................................................................10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
6.1 Provision and Withdrawal
|
............................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
6.2 Registration and Erasure
|
.................................................................................................................................. 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
6.3 Handling of UUS services
|
............................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
6.3.1 Activation
|
................................................................................................................................................... 10
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
6.3.2 Invocation
|
........................................................................................................................................................ 11
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7 Interactions with other supplementary services
|
.....................................................................................11
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.1 Call forwarding unconditional
|
......................................................................................................................... 11
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.2 Call forwarding on mobile subscriber busy
|
..................................................................................................... 11
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.3 Call forwarding on no reply
|
............................................................................................................................. 11
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.4 Call forwarding on mobile subscriber not reachable
|
....................................................................................... 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.5 Call waiting
|
...................................................................................................................................................... 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.6 Call hold
|
.......................................................................................................................................................... 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.7 Completion of calls to busy subscribers
|
.......................................................................................................... 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.8 Explicit call transfer
|
......................................................................................................................................... 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.9 Multi party service
|
........................................................................................................................................... 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.10 Advice of charge
|
.............................................................................................................................................. 12
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.11 Barring of outgoing calls
|
................................................................................................................................. 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.12 Barring of outgoing international calls
|
............................................................................................................ 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.13 Barring of outgoing international calls except those directed to the home PLMN country
|
............................. 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.14 Barring of incoming calls
|
................................................................................................................................ 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.15 Barring of incoming calls when roaming outside the home PLMN country
|
................................................... 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
7.16 Call Deflection
|
................................................................................................................................................. 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
8 Interactions with other network features
|
................................................................................................13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
8.1 Support of Optimal Routeing
|
........................................................................................................................... 13 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 4 3G TS 22.087 version 3.1.0
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
8.2 Multicall
|
........................................................................................................................................................... 13
|
3e132ee54cef081bf4705ff3e4691de3
|
122 087
|
9 Interworking considerations
|
..................................................................................................................13 Annex A (informative): Deviations of the 3GPP UUS supplementary service from the ISDN service.............................................................................................................15 Annex B: Change history ..............................................................................................................................16 History..............................................................................................................................................................17 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 5 3G TS 22.087 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.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 6 3G TS 22.087 version 3.1.0 1 Scope The User-to-User Signalling (UUS) supplementary service allows a mobile subscriber to send/receive a limited amount of information to/from another PLMN or ISDN subscriber over the signalling channel in association with a call to the other subscriber. 2 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. [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: General on supplementary services. [3] TS 22.030: Man-Machine Interface (MMI) of the Mobile Station (MS). [4] TS 21.905: "Vocabulary for 3GPP Specifications". [5] TS 22.135: "Multicall stage 1". 3 Definitions and Abbreviations 3.1 Definitions For the purposes of this TS, the following definitions apply: User-to-User Information (UUI): The information transferred by using the UUS supplementary service. UUS service: The UUS services (Service 1, 2 and 3) are components of the UUS supplementary service. If the UUS supplementary service is provided to a subscriber, she can handle the UUS services independently within a call. Served subscriber: The subscriber who has a provision of the UUS supplementary service and who activates the UUS supplementary service. For service 1 and 2 the served subscriber is always the calling subscriber, for service 3 either the calling or the called subscriber can be the served subscriber. Remote party: For service 1 and 2 the remote party is the called party of a call to which the UUS supplementary service is activated by the served subscriber. For service 3 the remote party can be either the called or the calling party of an established call to whom the use of the UUS supplementary service is requested by the served subscriber. 3.2 Abbreviations For the purposes of this TS the following abbreviations apply. UUS User-to-User Signalling UUI User-to-User Information Further GSM related abbreviations are listed in GSM 01.04 [1] and TS 21.905 [4]. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 7 3G TS 22.087 version 3.1.0 4 Description 4.1 Description The UUS supplementary service allows the served subscriber to send/receive a limited amount of subscriber generated information to/from another user in association with a call to the user. This information shall be passed transparently (i.e. without modification of contents) through the network. Normally, the network shall not interpret or act upon this information. The served subscriber can send and receive UUI in different phases of the call depending on the service(s) to which the subscriber subscribes. These services are: Service 1: UUI can be sent and received during the origination and termination of a call, with UUI embedded within call control messages. The service 1 can be activated implicit by inserting UUI when set-up a call or explicit with an appropriate procedure. Service 2: UUI can be sent and received after the served subscriber has received an indication that the remote party is being informed of the call and prior to the establishment of the connection. UUI sent by the served subscriber prior to receiving the acceptance of the call by the remote party, may as a network option be delivered to the remote party after the call has been established. The service 2 shall be activated explicitly. Service 3: User-to-user-information can be sent and received only while the connection is established. The service 3 shall be activated explicitly. Service 1, service 2 and service 3 shall allow the transmission of UUI with the maximum length of 128 octets per message. 4.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004 [2]. 5 Normal procedures with successful outcome 5.1 Provision The UUS supplementary service shall be provided to the served subscriber after pre-arrangement with the service provider. The remote party needs no subscription of the UUS supplementary service. NOTE: The remote party is able to send UUI without provision of the UUS supplementary service when the service is activated against her by the served subscriber. As a service provider option, one or any combination of the following shall be provided: - service 1 (implicitly requested andexplicitly requested); - service 2; - service 3. 5.2 Withdrawal The UUS supplementary service and several UUS services shall be withdrawn by the service provider upon the subscriber's request or for service providers reasons. The supplementary service UUS shall be withdrawn if all UUS services provided to the served subscriber are withdrawn. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 8 3G TS 22.087 version 3.1.0 5.3 Registration and Erasure not applicable. 5.4 Activation and Deactivation The UUS supplementary service shall be activated by the service provider as a result of provision and deactivated as a result of withdrawal. 5.5 Invocation The UUS supplementary service is invoked if at least one UUS service is activated by the served subscriber. 5.6 Interrogation not applicable. 5.7 Handling of UUS services 5.7.1 Activation UUS service is activated when: - activation is implicitly requested (for service 1); or - activation is explicitly requested (for service 1, service 2 and service 3) and is accepted by the remote party. Depending on the served subscriber subscription to the UUS supplementary service and the provision of the UUS services by the service provider, service 1 implicit, service 1 explicit, service 2 and service 3 can be activated individually or in combination. Service 1 implicit and service 1 explicit cannot be simultaneously active. Once an UUS service is activated the network shall accept UUI from either subscriber in the call, according to the service that has been activated. The network shall confirm the explicit activation of a UUS service (service 1, 2 and 3) to the served subscriber. This confirmation shall be preceded by an end-to-end check by the network for service availability. The network shall interrogate the remote party and check for the availability of the UUS service on the remote party's side. The mobile station shall confirm the requested services if it is able to handle the UUS service. The remote party shall not have the possibility to confirm or reject the request for the UUS service on a per call basis. No response from the remote party shall be taken by the network as a rejection of the request for the UUS service. NOTE: Nevertheless the remote party may restrict the use of a UUS service by pre-programming of the mobile station to reject incoming UUS activation requests. The network shall explicitly indicate to the calling mobile subscriber whether or not the requested service has been successfully activated. 5.7.1.1 Service 1 UUS service 1 shall be activated by the calling mobile subscriber when originating a call if UUI transfer is desired in either direction. Service 1 is automatically deactivated when the call is terminated. Service 1 can be activated by means of an implicit activation request or an explicit activation request. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 9 3G TS 22.087 version 3.1.0 Implicit activation: Service 1 is implicitly activated when UUI is included when originating a call. When service 1 is implicitly activated, service 1 is active for the call, i.e. the remote party is not required to send a response to the implicit activation request. However, the remote party can include UUI in the call response. Explicit activation: The UUS service 1 shall be activated explicitly by using of the procedure defined in TS 22.030 [3]. The served mobile subscriber shall be given an explicit response (acceptance or rejection) to an explicit activation request. An explicit activation request can include UUI. When service 1 is explicitly requested, the remote party can include UUI when accepting the activation request for the UUS supplementary service. 5.7.1.2 Service 2 The UUS service 2 shall be activated by using of the procedure defined in TS 22.030 [3]. Service 2 shall be activated by the served subscriber when originating a call, if UUI transfer is desired in either direction. Service 2 shall be explicitly requested. The served mobile subscriber shall be given an explicit response (acceptance or rejection) to an explicit activation request. Service 2 is automatically deactivated when the called subscriber is no longer being informed of the call, i.e. if the call is established or released. 5.7.1.3 Service 3 The served subscriber can explicit request the activation of service 3 when a call is originated or after the connection has been established by using the procedure defined in TS 22.030 [3]. The request for the UUS service 3 shall be accepted from the remote party in order to activate the UUS supplementary service. The served user shall be given an explicit response (acceptance or rejection) to the explicit activation request. Service 3 is automatically deactivated when the call is no longer established. 5.7.1.4 "UUS required" request When a call is originated, the calling subscriber can specify whether the requested UUS service(s) is (are) required for the call, i.e. if the call should be completed or not if UUI cannot be passed. If the "UUI-required" indication is given by the subscriber, the call shall not be completed if UUI cannot be passed to the called subscriber. If the "UUI-not- required" indication is given by the subscriber, the call will be completed even if UUI cannot be passed. If service 1 is implicitly requested or if service 3 is requested during the call, it cannot be requested as "UUI-required". 5.7.2 Invocation and operation If activated by the served subscriber a UUS service shall be invoked when UUI is sent by either subscriber to the network. When a subscriber sends UUI the network shall not confirm its delivery to the subscriber. For service 2 and 3, when sending a UUI message, the subscriber can indicate that the subscriber will send further UUI associated with this UUI message. This indication shall be given to the receiving subscriber. When sending a UUI message, the subscriber may indicate the use of particular user protocol associated with the UUI message. This indication shall be given to the receiving subscriber. The identification of, and the use of, user protocols is outside of this standard. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 10 3G TS 22.087 version 3.1.0 5.7.2.1 Service 1 A PLMN subscriber can transfer UUI when originating a call. When service 1 has been activated, either subscriber can include UUI when accepting, rejecting, or terminating a call. NOTE: It is possible for a calling subscriber to invoke the UUS service 1 with a call set-up and terminate the call before the connection is established. 5.7.2.2 Service 2 Any time between activation of service 2 and connection is established, either subscriber can transfer up to 2 UUI messages in each direction to the other subscriber involved in the call. 5.7.2.3 Service 3 After service 3 has been activated, either subscriber can transfer UUI to the other subscriber on the call after the connection has been established. NOTE: The amount of UUI messages that can be transferred with service 3 shall be defined. 5.7.2.4 Charging requirements The served subscriber shall be charged according to the number of UUI messages transferred in either direction. When charging for UUI the destination (e.g. international calls, diverted calls) of the related call shall not be considered. It shall be possible to charge for the invocation of the UUS supplementary service even if there are no other call charges. 6 Exceptional procedures or unsuccessful outcome 6.1 Provision and Withdrawal No exceptional procedures. 6.2 Registration and Erasure not applicable. 6.3 Handling of UUS services 6.3.1 Activation If the network cannot accept an implicit request for the activation of UUS service 1, no notification shall be given to the subscriber. In all other cases, if the network cannot accept a request for the activation of a UUS service, the network shall reject the activation. In addition, the network shall indicate which of service 1, service 2 and/or service 3 have been rejected. For the rejection of the activation request the following reasons may be possible: - service not subscribed to; - necessary signalling connectivity does not exist between sending and receiving subscribers; - conflicting situation with other supplementary service (e.g. CUG, incoming call barring); - service is already active; 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 11 3G TS 22.087 version 3.1.0 - network congestion. 6.3.2 Invocation The subscriber may not be able to interpret incoming UUI. In such situations, the user can discard this information without disrupting normal call handling. No specific signalling is provided by the network to accommodate this situation. Under circumstances of network congestion or failure, the network may discard services 2 and 3 UUI. 7 Interactions with other supplementary services 7.1 Call forwarding unconditional No impact NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.2 Call forwarding on mobile subscriber busy If call forwarding on mobile subscriber busy is invoked as a result of a network determined user busy condition (NDUB) of the called subscriber, any UUI and UUS request accompanies the call set-up request shall be forwarded with the call If call forwarding on mobile subscriber busy is invoked as a result of an user determined user busy condition (UDUB) the following cases shall be distinguished: - If the UDUB condition is met before alerting any UUI and UUS request accompanies the call set-up request shall be forwarded with the call. - If the UDUB condition is met after alerting the interactions as defined for call forwarding on no reply shall apply. UUI included in a UDUB request by the forwarding subscriber shall be ignored by the network. NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.3 Call forwarding on no reply Service 1: If UUS service 1 is implicitly requested to the forwarding subscriber the UUI shall be transferred to the forwarded-to party after the invocation of CFNRy. If UUS service 1 is explicitly requested with the option "UUS required“ to a called subscriber who has CFNRy active and operative and the no-reply condition timer expires, the call shall be released. If UUS service 1 is explicitly requested with the option "UUS not required“ to a called subscriber who has CFNRy active and operative, CFNRy shall be invoked. If the called subscriber has confirmed the UUS service 1 request prior to the invocation of CFNRy, the UUI and the UUS request shall be transferred to the forwarded-to party. Otherwise the UUI and the UUS request shall not be forwarded with the call. Service 2: If UUS service 2 is requested with the option "UUS not required“ to a called subscriber who has CFNRy active and operative, CFNRy shall be invoked but no UUS activation request will be given to the forwarded-to subscriber. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 12 3G TS 22.087 version 3.1.0 If UUS service 2 is requested with the option "UUS required“ to a called subscriber who has CFNRy active and operative, CFNRy shall not be invoked. Service 3: Any activation request for UUS service 3 that accompanies the call set-up request shall be forwarded with the call. NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.4 Call forwarding on mobile subscriber not reachable No impact NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.5 Call waiting UUI for the operation of UUS service 1 included in the call request shall be delivered with the call waiting indication to the called subscriber. There are no interactions with service 2 and service 3. 7.6 Call hold A subscriber who has invoked the Call Hold supplementary service may send or receive UUI to/from both the active and the held party. If the served subscriber has an active and a held call the mobile station shall indicate which party has sent a received UUI message. 7.7 Completion of calls to busy subscribers Requests for the activation of a UUS service contained in the original call request shall be stored with the request for the invocation of the CCBS supplementary service. The network shall also store any UUI containing in the original call request and use this stored UUI in the CCBS call. 7.8 Explicit call transfer When calls are transferred as a result of invocation of the explicit call transfer supplementary service, UUS services activated on either of the calls prior to the invocation of the explicit call transfer supplementary service shall be automatically deactivated by the network. No specific notification shall be sent to the involved subscribers when the UUS services are no longer activated. The subscribers involved in the transferred call may request the activation of service 3 again, if required. 7.9 Multi party service During a MPTY the MPTY-Manager can send and receive UUI to/from each remote party separately. The mobile station of the multi party manager shall indicate from which remote party a received UUI message was sent. UUI shall not be transferred between remote parties. 7.10 Advice of charge No impact. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 13 3G TS 22.087 version 3.1.0 NOTE: The Advice of Charge services may not provide any information concerning charges for the use of the UUS supplementary service. 7.11 Barring of outgoing calls no impact 7.12 Barring of outgoing international calls no impact 7.13 Barring of outgoing international calls except those directed to the home PLMN country no impact 7.14 Barring of incoming calls no impact. 7.15 Barring of incoming calls when roaming outside the home PLMN country no impact. 7.16 Call Deflection If Call Deflection is invoked before alerting the same interactions as for Call forwarding on mobile subscriber busy shall apply. If Call Deflection is invoked after alerting the same interactions as for Call forwarding on no reply shall apply. 8 Interactions with other network features 8.1 Support of Optimal Routeing The invocation of Optimal Routeing in case of late call forwarding shall have no impact on the interactions of UUS with the call forwarding supplementary services as defined in section 7. 8.2 Multicall See TS 22.135 [5]. The UUS supplementary service can be delivered only when both subscribers' networks provide a means of conveying the UUI. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 14 3G TS 22.087 version 3.1.0 Some networks may support the transmission of UUI with a maximum length of only 32 octets per message for service 1. In the interworking case only the first 32 octets of UUI with more than 32 octets per message shall be transferred. No notification about the limitation of the UUI shall be given to any subscriber. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 15 3G TS 22.087 version 3.1.0 Annex A (informative): Deviations of the 3GPP UUS supplementary service from the ISDN service The ISDN service UUS allows as a network option the transfer of UUI with a maximum length of 32 octets for service 1. This option shall not be supported in PLMNs. However there is the possibility that networks using the phase 1 or phase 2 standard can support the UUS service 1 implicitly requested with 32 octets. These networks shall apply the rules defined in the section 8, Interworking considerations. In the 3GPP specification some charging requirement are defined. These requirements shall allow network operators to charge their subscribers for the use of and to prevent misuse of the UUS supplementary service. Because of the different handling of busy states in ISDN the interactions with call forwarding on mobile subscriber busy are different. The network option to allow forwarding of UUS requests and UUI only if the forwarding subscriber has the subscription of the relevant UUS service is not supported. The general principle of CCBS to retain all information of the original call set-up and reusing this information for the CCBS call shall also be valid for the UUS supplementary service. Therefore the UUI contained in the original call set- up shall be stored in network and reused in the CCBS call. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 16 3G TS 22.087 version 3.1.0 Annex B: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.87 7.1.0 Transferred to 3GPP SA1 SA#04 22.087 3.0.0 SA#05 22.087 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. SA#05 22.087 3.0.1 002 R99 3.1.0 Multicall (This CR was wrongly marked as 22.086 and should be to 22.087) 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 17 3G TS 22.087 version 3.1.0 History Document history V3.0.0 July 1999 Transferred to TSG SA at ETSI SMG#29. Under TSG TSG SA Change Control. V3.0.1 October 1999 Inclusion of CR at SA#05 V3.1.0 December 1999 Inclusion of a subsequent CR from SA#05 3G TS 22.087 version 3.1.0 Release 1999 18 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 3G TS 22.087 version 3.1.0 Release 1999 History Document history V3.1.0 March 2000 Publication
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
1 Scope
|
........................................................................................................................................................5
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
2 References
|
................................................................................................................................................5
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
2.1 Normative references
|
......................................................................................................................................... 5
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
2.2 Informative references
|
....................................................................................................................................... 6
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4 Main concepts
|
..........................................................................................................................................7
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.1 Localised Service Area definition
|
...................................................................................................................... 7
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.2 Subscriber information for Localised Service Area
|
........................................................................................... 7
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.3 Localised Service Area support in idle mode
|
.................................................................................................... 7
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.