hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.1.3 Connection release | ..................................................................................................................................... 26 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2 Network initiated SS Management | .................................................................................................................. 27 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2.1 Connection establishment phase | ................................................................................................................ 27 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2.2 Connection established | ............................................................................................................................... 27 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2.3 Connection release | ..................................................................................................................................... 27 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2.4 ForwardCheckSSIndication | ....................................................................................................................... 28 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2.5 CCBS Recall | .............................................................................................................................................. 28 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.2.6 CCBS Monitoring | ...................................................................................................................................... 29 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents | .................................... 29 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.3.1 Operation codes | .......................................................................................................................................... 29 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.3.2 Error codes | ................................................................................................................................................. 29 |
32dca953c19f1349b85cfc45d684f611 | 129 011 | 6.3.3 Parameter tags and parameter values | ......................................................................................................... 30 Annex A: Change history......................................................................................................................31 History..............................................................................................................................................................32 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 5 3G TS 29.011 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS provides a detailed specification for interworking between the A-interface protocol and the Mobile Application Part (MAP) for handling of 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; (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 6 3G TS 29.011 version 3.0.0 1 Scope The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces. The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification. Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification. Clause 2 describes general procedures for interworking between the A- and D- physical interfaces. Clause 3 describes the general procedures for the SS version negotiation. Clause 4 describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces. Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity. Clause 6 describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see GSM 09.02) and the SS handling functions of the network entities (see GSM 04.10 and GSM 04.80). Reference is made to the following Technical Specifications: - GSM 02.04 and GSM 02.8x and GSM 02.9x-series, for definition of supplementary services; - GSM 03.11, GSM 03.8x and GSM 03.9x-series, for technical realisation of supplementary services; - GSM 04.10, GSM 04.80, GSM 04.8x and GSM 04.9x-series, for radio path signalling procedures for supplementary services; - GSM 09.02 (MAP). (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 7 3G TS 29.011 version 3.0.0 1.1 Normative references The following documents contain provisions which, through reference in this text, constitute provisions of the present document. β’ References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. β’ For a specific reference, subsequent revisions do not apply. β’ For a non-specific reference, the latest version applies. β’ A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [5] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 1". [6] GSM 02.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber - Stage 1". [7] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [8] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [9] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber - Stage 2". [10] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [11] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification General aspects". [12] GSM 04.72: "Digital cellular telecommunications system (Phase 2+); Call Deflection supplementary service - Stage 3". [13] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". [14] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". [15] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". [16] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". [17] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 3". (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 8 3G TS 29.011 version 3.0.0 [18] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". [19] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". [20] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". [21] GSM 04.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 3". [22] GSM 04.91: "Digital cellular telecommunications system (Phase 2+); Explicit Call Transfer (ECT) supplementary services - Stage 3". [23] GSM 04.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber - Stage 3". [24] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [25] GSM 09.10: "Digital cellular telecommunications system (Phase 2+); Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". 1.2 Definitions and abbreviations Abbreviations used in this specification are listed in GSM 01.04. 2 Introduction This clause describes general procedure at the MSC/VLR for SS interworking between the A- and D-interfaces. 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface Upon receipt of supplementary service signalling on the A-interface, the MSC/VLR shall: - perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); - if necessary request access to the HLR over the D-interface using the procedures defined in this specification and MAP, GSM 09.02; - use the version indicator received from the MS to set up the right AC context name towards the HLR (see clause 3). The version indicator is described in GSM 04.10 and GSM 04.80. AC names are defined in GSM 09.02; - perform mapping between layer 3 messages on the radio path and TC transaction sublayer messages as required (see clause 3). (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 9 3G TS 29.011 version 3.0.0 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface Upon receipt of supplementary service signalling on the D-interface, the MSC/VLR shall: - perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); - handle any information elements according to the screening indicator procedure as described in GSM 04.10; - perform mapping between TC transaction sublayer messages and layer 3 messages on the radio path as required (see clause 3). 3 SS version negotiation This clause describes the general procedures for the call related and call independent supplementary services version negotiation. 3.1 Call related supplementary services interworking No interworking identified. 3.2 Call independent supplementary services interworking On receipt of the REGISTER message from the MS, the MSC/VLR will include the appropriate AC name in the dialogue control portion of the BEGIN message based on the following rules: - if no version indicator is present, no AC name is included in the BEGIN message towards the HLR (no AC name indicates "version1"); - if the version indicator is less or equal to the highest AC name the MSC/VLR and HLR both support, the "dialogue" will be handled according to the AC name corresponding to the version indicator and to the SS operation received; - if the version indicator is greater than the highest commonly supported AC name within the network (MSC/VLR, HLR), the "dialogue" will be handled according to this highest AC name if the request from the MS can also be fulfilled with this version of the "dialogue". The selection of the highest commonly supported AC name by the network is described in GSM 09.02. It should be noted that unknown parameters of the extension field within the Facility Information Element shall be forwarded to a phase 2 HLR according to the Extensibility rules as defined in GSM 09.02. They may be discarded when sent to a phase 1 HLR. According to this version of the standards, the highest AC name is "version3". The description method employed in the clauses 4 to 6 is tabled showing the mapping of parameter values. The exact values of the parameters and parameter tags can be found in the referenced specifications. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 10 3G TS 29.011 version 3.0.0 4 Mapping between TC transaction sublayer messages and layer 3 radio path messages This clause describes the mapping of TC transaction sublayer messages to layer 3 radio path messages over the external interfaces. The precise coding of these messages is given in other technical specifications. 4.1 D-interface to A-interface mapping Table 4.1 shows the mapping of TC transaction sublayer messages to layer 3 messages on the radio path. Table 4.1: Mapping of TC transaction sublayer messages to layer 3 radio path messages TC transaction sublayer message Layer 3 radio path message BEGIN REGISTER (note 1) CONTINUE (note 2) FACILITY/REGISTER (note 3) END (note 2) RELEASE COMPLETE/REGISTER (note 3) ABORT (note 2) RELEASE COMPLETE NOTE 1: AC name is not mapped to a version indicator. NOTE 2: The user information field if present is discarded. NOTE 3: A CONTINUE or END is mapped to REGISTER if a new transaction has to be established. 4.2 A-interface to D-interface mapping Table 4.2 shows the mapping of layer 3 radio path messages to TC transaction sublayer messages. Table 4.2: Mapping of layer 3 radio path messages to TC transaction sublayer messages Layer 3 radio path message TC transaction sublayer message REGISTER BEGIN (note) FACILITY CONTINUE RELEASE COMPLETE END NOTE: The right AC name shall be included, see clause 3. 4.3 Procedures The mapping from TC Transaction Sublayer messages to Layer 3 radio path messages must include a replacement of the tag and length of the Component Portion in the Transaction Sublayer message with the Information element identifier and length of the Facility Information Element for the Layer 3 message. Similarly for the reverse mapping. However, if a version indicator is received an AC name will be provided in the BEGIN message, see clause 3. All transaction sublayer messages, except the ABORT message, will normally contain one or more components. If components are included, the conversion algorithm described below applies. If a message does not contain a component, then the corresponding message is also sent without a component: messages shall not be withheld by the interworking function. For call independent SS operations each message shall only contain a single component. If a message contains more than one component then a RELEASE COMPLETE message with the cause "Facility rejected" (see GSM 04.08) and without any component shall be sent on the radio path (see GSM 04.10). TC Transaction sublayer messages can also contain a dialogue portion. If a user-information is received within this dialogue portion, it will not be conveyed in a Layer 3 radio path message. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 11 3G TS 29.011 version 3.0.0 If an ABORT message is received in TC, a RELEASE COMPLETE message is to be sent on the radio path. The RELEASE COMPLETE message shall not contain any component. If a cause is to be provided to the MS, one of the cause codes of GSM 04.08 shall be used. If an ABORT message with a dialogue portion indicating "version fallback" (e.g. the cause "AC-not-supported") is received in TC then, if the MSC does not re-attempt the "dialogue" (e.g. by using a different AC name), it shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see GSM 04.08) and without any component. If an END message with a dialogue portion indicating "dialogue refused" is received in TC then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see GSM 04.08) and without any component. If a layer 3 radio path message or a component in the layer 3 radio path message is rejected by the MSC, the MSC shall: - return a RELEASE COMPLETE message to the MS. If the reject condition is not associated with a component, one of the cause codes of GSM 04.08 shall be inserted, as described below. If it is a component (except a REJECT component), a REJECT component with the appropriate problem code shall be inserted in the RELEASE COMPLETE message, as described below. If the reject condition concerns a REJECT component the RELEASE COMPLETE message may be empty; - terminate the transaction with the VLR by use of an ABORT message. If a dialogue cannot be established with the HLR because no common AC name is available then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected". 5 Call related supplementary services management 5.1 SS management in connection establishment phase When a CM connection is being set up between an MS and an MSC, setting up of a connection between the MSC and the VLR to request access proceeds as for normal call set-up (see GSM 09.02). Moreover, the MSC will also assess the capabilities of the MS according to the screening indicator (see GSM 04.10 and GSM 04.80). As the call set-up proceeds, the following supplementary services may apply: 5.1.1 Line Identification services These supplementary services (described in GSM 04.81) require interworking in the MSC between both GSM 04.08, MAP (GSM 09.02) and the fixed network protocol, see also GSM 09.10. 5.1.1.1 Calling Line Identification Presentation (CLIP) The signalling at invocation of the CLIP supplementary service is shown in figure 5.1. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G 6(783 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.1: Signalling for CLIP supplementary service When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the CLIP service is provided (and CLIR is not indicated in the incoming call set-up message from the PSTN), then the number of the calling subscriber (if received in the incoming call set-up) shall be mapped onto the Calling Party BCD number parameter in the SETUP message sent to the mobile. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.81. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 12 3G TS 29.011 version 3.0.0 5.1.1.2 Calling Line Identification Restriction (CLIR) The signalling at invocation of the CLIR supplementary service is shown in figure 5.2. MS MSC VLR HFI HFI HFI G G G G G G G G 6(783 G G6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783G G G GFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G G G G G Figure 5.2: Signalling for CLIR supplementary service When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the CLIR service is provided and if the CLIR service shall be invoked (according to the presentation mode and possible subscriber request), then this information is indicated in the initial address message sent using the fixed network protocol (if possible). If this parameter indicates that the CLIR service is not provided and the calling subscriber has attempted to invoke CLIR, then the call set-up shall be rejected as defined in GSM 04.81. 5.1.1.3 Connected Line Identification Presentation (COLP) The signalling at invocation of the COLP supplementary service is shown in figure 5.3. MS MSC VLR HFI HFI HFI G G G G G G G G 6(783 G G6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783G G G GFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G &211(&7 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFG G G G G G G G G G Figure 5.3: Signalling for COLP supplementary service When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the COLP service is provided, then if the connected line identity is made available by the terminating network (i.e. no interworking or presentation restrictions apply) then the connected number is passed to the calling mobile subscriber in the ConnectedNumber parameter in the CONNECT message. 5.1.1.4 Connected Line Identification Restriction (COLR) The signalling at invocation of the COLR supplementary service is shown in figure 5.4. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G 6(783 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.4: Signalling for COLR supplementary service When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the COLR service is provided, then this information is sent to the originating network using the fixed network protocol (if possible). (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 13 3G TS 29.011 version 3.0.0 5.1.2 Call Forwarding services 5.1.2.1 Notification to served mobile subscriber As described in GSM 02.82, when a subscriber has any (set of) Call Forwarding service(s) active, a notification of this fact is sent to the MS at mobile originated call set-up from the served mobile subscriber. The signalling for this notification is shown in figure 5.5. MS MSC VLR HFI HFI HFI G G 6(783 G G G G G GFFFFFFFFFF!G G6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G $/(57,1* G G G G G G &211(&7 G G &203/(7( &$// G G G G )$&,/,7< G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that a call forwarding service is active, then any of the ALERTING, CONNECT or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.82. 5.1.3 Call Waiting service (CW) 5.1.3.1 Offering a waiting call The signalling for this situation is shown in figure 5.6. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 352&(66 &: G G G G 6(783 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.6: Signalling for setting up a waiting call A waiting call is offered to a busy MS using a normal SETUP message including a "Signal" information element with value #7 (call waiting tone on), as described in GSM 04.83. This is the required MSC behaviour if it has received a MAP_PROCESS_CALL_WAITING service primitive as a response to a MAP_SEND_INFO_FOR_INCOMING_CALL service primitive on the B-interface. Exact values of the parameter and parameter tag are indicated in GSM 04.08. 5.1.3.2 Notification of waiting call to calling subscriber The signalling for this notification is shown in figure 5.7. MS MSC HFI HFI G G G G G G $/(57,1* G G G G FFFFFFFFFFFFFFFFFFFG G G G G G Figure 5.7: Signalling for notification of waiting call to calling subscriber (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 14 3G TS 29.011 version 3.0.0 If there are no network interworking limitations between the originating and destination MSCs, then the calling MS receives notification of his waiting call as follows: A Facility Information element in the ALERTING message includes a NotifySS operation with the following parameters: - SS-Code parameter indicates "callWaiting"; - CallIsWaitingIndicator parameter indicates "callIsWaiting". Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.83. 5.1.4 Closed User Group service (CUG) 5.1.4.1 Explicit invocation of a CUG call The signalling for this situation is shown in figure 5.8. MS MSC VLR HFI HFI HFI G G G G G G G G 6(783 G G6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783G G G GFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 5.8: Signalling at explicit invocation of a CUG call When a subscriber to the CUG supplementary service sets up a call, an explicit invocation involves transport of a ForwardCUG-Info operation in a Facility information element in the SETUP message. Parameter mapping between the air-interface SETUP message and the B-interface MAP_SEND_INFO_FOR_OUTGOING_CALL service primitive shall take place in the MSC. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. The parameter tags and values are mapped as follows: Table 5.1: Mapping of parameter names and values for explicit invocation of a CUG call GSM 04.80 parameter name GSM 09.02 parameter name cug-Index cug-Index suppressPrefCUG suppressPrefCUG suppressOA suppressOutgoingAccess 5.1.4.2 Notification of CUG invocation to served MS The signalling for this situation is shown in figure 5.9. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G&$// 352&((',1*G G &203/(7( &$// G G G G )$&,/,7< G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.9: Signalling flow for notification of CUG invocation to served MS The network may indicate to the MS that a CUG has been invoked for the outgoing call by sending a NotifySS operation in the Facility information element in the FACILITY or CALL PROCEEDING message towards MSa. The parameter to be included in this operation (cug-Index) is obtained from the MAP_COMPLETE_CALL service primitive. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.4.3 Notification of rejection of CUG invocation to served MS The signalling for this situation is shown in figure 5.10. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 15 3G TS 29.011 version 3.0.0 MS MSC VLR HFI HFI HFI G G 6(783 G G 6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783 G G G GFFFFFFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783 (5525G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G ',6&211(&7 G G G G G G 5(/($6( G G G G G G5(/($6( &203/(7(G G G G G G FFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS When an attempted CUG call is rejected for CUG related reasons, mapping of parameter values take places in order to inform the MSa of the failure in the DISCONNECT, RELEASE or RELEASE COMPLETE message. If the call is rejected by the serving VLR, a mapping of errors received on the B-interface (as response to MAP_SEND_INFO_FOR_OUTGOING_CALL) to diagnostics (in the diagnostics field of the Facility Rejected cause value) must be performed. The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in GSM 09.02, GSM 04.08, and GSM 04.80 respectively): Table 5.2: Mapping of GSM 09.02 error causes to diagnostics at notification of rejection of CUG invocation to served MS GSM 09.02 error cause Facility rejected #29 diagnostic field outgoingCallsBarredWithinCUG Outgoing calls barred within the CUG noCUG-Selected No CUG selected unknownCUG-Index Unknown CUG index indexIncompatibleWith RequestedBasicService Index incompatible with requested basic service If there are no network interworking restrictions (i.e. originating MSC = gateway MSC = terminating MSC), interworking between MAP and the air-interface takes place also for rejection of CUG calls by terminating end. The signalling for this situation is shown in figure 5.11. MSa MSC HLR HFI HFI HFI G G G G G G G G G G 6(1'B5287,1*B,1)2 G G G G G G6(1'B5287,1*B,1)2B606G G G G G G IRU 06E G G G G G GFFFFFFFFFFFFFFFFFFFF!G G G G ',6&211(&7 G G G G G G 5(/($6( G G G G G G5(/($6( &203/(7(G G 6(1'B5287,1*B,1)2 G G G G FFFFFFFFFFFFFFFG G FFFFFFFFFFFFFFFFFFFFG G G G G G G G Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in GSM 09.02, GSM 04.08, and GSM 04.80 respectively): Table 5.3: Mapping of GSM 09.02 error causes to cause values at notification of rejection by terminating end GSM 09.02 error cause Cause information element (cause value) calledPartySSInteractionViolation Facility Rejected #29, Diagnostic = CUG call failure, unspecified incomingCallsBarredWithinCUG Incoming calls barred within the CUG #55 subscriberNotMemberOfCUG User not a member of CUG #87 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 16 3G TS 29.011 version 3.0.0 requestedBasicServiceViolatesCUG-Constraints Facility Rejected #29 5.1.4.4 Notification of CUG invocation to terminating MS The signalling for this situation is shown in figure 5.12. MS MSC VLR HFI HFI HFI G G G G G G G G G G 6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// 352&(66 &$// :$,7,1* G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 6(783 G G G G G G FFFFFFG G G G G G G G G G Figure 5.12: Signalling flow for notification of CUG invocation to terminating end When a CUG call arrives at the terminating end, the CUG index associated with the invoked CUG may be passed to the mobile station. The cug-Index parameter is obtained from the fixed network connection establishment request message, or if no fixed network protocol is involved (i.e. originating = terminating MSC), it is obtained from the MAP_COMPLETE_CALL or MAP_PROCESS_CALL_WAITING service primitive. Its value is mapped onto the cug- Index parameter in the NotifySS operation in the Facility Information element of the SETUP message on the air- interface. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.5 Advice of Charge services 5.1.5.1 Notification of Charging information to served MS, mobile originated call The signalling for this situation is shown in figure 5.13. MSa MSC VLR HFI HFI HFI G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFG G G G &211(&7 G G G G G G )$&,/,7< G G G G G G FFFFFFFFFG G G G G G G G G G Figure 5.13: Signalling flow for notification of Mobile originated Charging Information to served MS The network may indicate charging information to the MS at mobile originated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice Of Charge Information in the MAP_COMPLETE_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of either the CONNECT or the FACILITY message. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.5.2 Notification of Charging information to served MS, mobile terminated call The signalling for this situation is shown in figure 5.14. MSb MSC VLR HFI HFI HFI G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFG G G G )$&,/,7< G G G G G G FFFFFFFFFG G G G G G G G G G Figure 5.14: Signalling flow for notification of Mobile terminated Charging Information to served MS (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 17 3G TS 29.011 version 3.0.0 The network may indicate charging information to the MS at mobile terminated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice of Charge Information in the SS-Data parameter included in the MAP_COMPLETE_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.6 Call Barring services These supplementary services (described in GSM 04.88) require the following interworking in the MSC: 5.1.6.1 Barring of outgoing calls The signalling for this situation is shown in figure 5.15. MS MSC VLR HFI HFI HFI G G G G 6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783 G G G G G G 6(1' ,1)250$7,21 )25 02%,/( 25,*,1$7(' 606 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 6(1' ,1)250$7,21 )25 287*2,1* &$// 6(783 (5525G G G G G G6(1' ,1)250$7,21 )25 02%,/( 25,*,1$7(' 606 (5525G G G G 5(/($6( G G (5525 G G G G &203/(7( G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFG G G G G G G G G G Figure 5.15: Signalling flow for barring of an outgoing call If the error code "CallBarred" is received as a response to the MAP_SEND_INFO_FOR_OUTGOING_CALL or MAP_SEND_INFO_FOR_MO_SMS service primitives on the B-interface, then a RELEASE COMPLETE message with a NotifySS operation shall be sent to the originating MS, as described in GSM 04.88. The mapping of GSM 09.02 callBarringCause to GSM 04.08 cause values is shown in table 5.4. Exact values of the parameter and parameter tags are indicated in GSM 04.80, GSM 04.88 and GSM 04.08. Table 5.4: Mapping of GSM 09.02 callBarringCause to GSM 04.08 cause values at barring of outgoing call GSM 09.02 callBarringCause GSM 04.08 Cause value barringServiceActive #31: Normal Unspecified operatorBarring #8: Operator Determined Barring (None) #21: Call Rejected 5.1.6.2 Barring of incoming calls The signalling for this situation is shown in figure 5.16. MSa GMSC HLRb HFI HFI HFI G G G G 6(1'B5287,1*B,1)2 G G G G G G6(1'B5287,1*B,1)2B606G G G G G G IRU 06E G G G G G GFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G ',6&211(&7 G G 6(1'B5287,1*B,1)2 G G G G 5(/($6( G G (5525 G G G G 5(/($6( &203/(7( G G FFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.16: Signalling flow for barring of an incoming call (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 18 3G TS 29.011 version 3.0.0 If the error code "CallBarred" is received as a response to the MAP_SEND_ROUTING_INFO or MAP_SEND_ROUTING_INFO_FOR_SM service primitives on the D-interface, then if no network interworking limitations apply, a NotifySS operation shall be sent to the originating MS in the first clearing message, as described in GSM 04.88. The mapping of GSM 09.02 error causes to GSM 04.08 cause values is shown in table 5.5. Exact values of the parameter and parameter tags are indicated in GSM 04.80, GSM 04.88 and GSM 04.08. Table 5.5: Mapping of GSM 09.02 error causes to cause values at barring of incoming call GSM 09.02 error cause Cause value barringServiceActive #21: Call Rejected operatorBarring #21: Call Rejected (None) #21: Call Rejected 5.1.7 CCBS call outcome For the purpose of monitoring the destination B (the target of a CCBS request activated by subscriber A), the HLR on the B-side needs to know the outcome of a CCBS call. A CCBS call is a call being set-up after acceptation of a recall (indication to subscriber A that B is idle). Thus, in case of a CCBS call, on receipt of call related messages from the MS, the MSC shall send (via the VLR) the MAP_STATUS_REPORT to the HLR. MS MSC VLR HLR HFI HFI HFI HFI G G 6(783 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G G G &211(&7 G G G G G G G G $/(57,1* G G G G G G G G ',6&211(&7 G G G G G G G G 5(/($6( G G G G G G G G 5(/($6( G G G G G G G G &203/(7( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G&&%6 &$// '(/,9(5<G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G 67$786B5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G Figure 5.16a: Signalling for CCBS call outcome The CONNECT or ALERTING messages imply that the call establishment has been successful. Then the value of the Outcome information element in the MAP_STATUS_REPORT is set to success. The DISCONNECT and RELEASE are, in this case, error messages and can contain different causes (e.g. Call Rejected or User Busy). The MSC translates the message and/or the cause received into the proper value for the Outcome information element (Failure or Busy). Exact coding and values of the messages and parameter tags can be found in GSM 04.08 and GSM 09.02. 5.2 SS Management in stable connection state When a stable CM connection is set up between a mobile station and the network, the following supplementary services may apply: 5.2.1 Call Forwarding services 5.2.1.1 Notification of invocation of CFB to served mobile subscriber As described in GSM 02.82, when the Call Forwarding on MS Busy service is invoked by the network, a notification of this fact may be sent to the MS. The signalling for the situation when the user is NDUB is shown in figure 5.17. Note that if the subscriber is not NDUB, this notification does not apply. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 19 3G TS 29.011 version 3.0.0 MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 1'8% G G G G HVWDEOLVKHG G G G G G G G G G G )$&,/,7< G G G G G G FFFFFFFFFFG G G G G G G G G G Figure 5.17: Signalling for notification of invocation of CFB supplementary service The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that CFB is active, then the FACILITY message may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.82. 5.2.2 Call Hold service (HOLD) As described in GSM 04.83, an MS can at any time during the active phase of a call signal invocation of the Call Hold supplementary service towards the network. This is done by use of the HOLD message (defined in GSM 04.80). When the MSC receives such a message, it requests access to the VLR and sends the MAP_INVOKE_SS service primitive to the VLR (as described in GSM 09.02). The interworking function triggers this behaviour by sending an internal MAP_INVOKE_SS signal to the MAP Service User of the MSC, indicating the following parameter values: - SS-Code = Call Hold; - BS-Code = Basic service of the on-going call. The signalling for this situation is shown in figure 5.18. Exact values of the parameter and parameter tags are indicated in GSM 04.80, GSM 04.83 and GSM 09.02. MS MSC VLR HFI HFI HFI G G G G G G G G +2/' G G ,192.(66 G G G GFFFFFFFFFF!G GFFFFFFFFFFFFF!G G G G G G G G G G G G ,192.(66 $&. G G G G +2/' $&. G G FFFFFFFFFFFFFG G G G +2/' 5(- G G G G G G FFFFFFFFFFG G G G G G G G G G Figure 5.18: Signalling flow at invocation of Call Hold supplementary service If the A_INVOKE_SS signal from the MAP Service User in the MSC is empty, the HOLD ACKNOWLEDGE message is returned to the MS. If it refers to an error, the mapping of error causes takes place according to table 5.6. Exact values of the parameter tags are indicated in GSM 04.80 and GSM 09.02. Table 5.6: Mapping of GSM 09.02 operation errors to GSM 04.80 HOLD REJECT causes GSM 09.02 operation error GSM 04.80 HOLD REJECT cause SystemFailure #63: Service/Option not available DataMissing #100: Invalid Information Element contents UnexpectedDataValue #100: Invalid Info. element contents CallBarred #29: Facility Rejected IllegalSS-Operation #50: Requested Facility not subscribed SS-ErrorStatus #50: Requested facility not subscribed SS-NotAvailable #69: Requested facility not implemented Note that Call Retrieval requires no communication on the B-interface, and thus no interworking requirements have been identified. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 20 3G TS 29.011 version 3.0.0 5.2.3 Multi Party service (MPTY) As described in GSM 04.84, an MS can at any time during the active phase of a call signal invocation of the Multi Party supplementary service towards the network. This is done by including a BuildMPTY operation (defined in GSM 04.80) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP_INVOKE_SS service primitive to the VLR (as described in GSM 09.02). The interworking function triggers this behaviour by sending an internal MAP_INVOKE_SS signal to the MAP Service User of the MSC, indicating the following parameter values: - SS-Code = MPTY; - BS-Code = Basic Service Code of the on-going calls. Note that the MSC does not allow the MPTY to be invoked if the two calls are not telephony calls. The signalling for this situation is shown in figure 5.19. MS MSC VLR HFI HFI HFI G G G G G G G G EXLOG037< G G ,192.(66 G G G GFFFFFFFFFF!G GFFFFFFFFFFFFF!G G G G G G G G G G G G ,192.(66 $&. G G G G EXLOG037< G G FFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.19: Signalling flow at invocation of Multi Party supplementary service If the A_INVOKE_SS signal from the MAP Service User in the MSC is empty, the BuildMPTY return result is returned to the MS in a FACILITY message. If it refers to an error, the mapping of errors takes place according to table 5.7. Table 5.7: Mapping of GSM 09.02 operation errors to GSM 04.80 BuildMPTY errors GSM 09.02 operation error GSM 04.80 BuildMPTY error SystemFailure SystemFailure DataMissing SystemFailure UnexpectedDataValue SystemFailure CallBarred IllegalSS-Operation IllegalSS-Operation IllegalSS-Operation SS-ErrorStatus SS-ErrorStatus SS-NotAvailable SS-NotAvailable Note that Holding, Retrieving and Splitting a multi party requires no communication on the B-interface, and thus no interworking requirements have been identified. 5.2.4 Advice of Charge services Notification of Charging information to served MS during the call The network may indicate revised charging parameters (as required according to GSM 02.24, GSM 02.86, GSM 03.86 and GSM 04.86) to the MS during a call. The parameters are forwarded to MSa using the ForwardChargeAdvice operation in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 21 3G TS 29.011 version 3.0.0 5.2.5 Explicit Call Transfer service (ECT) As described in GSM 04.91, an MS can at any time during the active phase of a call signal invocation of the Explicit Call Transfer supplementary service towards the network. This is done by including a ExplicitCT operation (defined in GSM 04.80) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP_INVOKE_SS service primitive to the VLR (as described in GSM 09.02). The interworking function triggers this behaviour by sending an internal MAP_INVOKE_SS signal to the MAP Service User of the MSC, indicating the following parameter values: - SS-Code = ect; - BS-Code = Basic Service Code of the on-going calls. Note that the MSC does not allow the ECT to be invoked if the two calls are not telephony calls. The signalling for this situation is shown in the following figure 5.21. MS MSC VLR HFI HFI HFI G G G G G G G G H[SOLFLW&7G G ,192.(66 G G G GFFFFFFFFFF!G GFFFFFFFFFFFFF!G G G G G G G G G G G G ,192.(66 $&. G G G G H[SOLFLW&7G G FFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service If the A_INVOKE_SS signal from the MAP Service User in the MSC is empty, the ExplicitCT return result is returned to the MS in a DISCONNECT/RELEASE/RELEASE COMPLETE message. If it refers to an error, the mapping of errors takes place according to table 5.8. Table 5.7: Mapping of GSM 09.02 operation errors to GSM 04.80 ExplicitCT errors GSM 09.02 operation error GSM 04.80 ExplicitCT error SystemFailure SystemFailure DataMissing SystemFailure UnexpectedDataValue SystemFailure CallBarred CallBarred IllegalSS-Operation IllegalSS-Operation SS-ErrorStatus SS-ErrorStatus SS-NotAvailable SS-NotAvailable 5.3 SS Management in disconnecting phase When a CM connection is being released, the following supplementary services may apply: (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 22 3G TS 29.011 version 3.0.0 5.3.1 Call Forwarding services Notification of invocation of CFNRy to served mobile subscriber As described in GSM 02.82, when the Call Forwarding on No Reply service is invoked by the network, a notification of this fact may be sent to the MS as the call attempt is disconnected. The signalling for this situation is shown in figure 5.20. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 6(783 G G G G G G FFFFFFFFFFFFFFFG G G G G G G G G G G G 15&7 G G G G 7LPHRXW G G G G G G G G G G )$&,/,7< G G G G G G ',6&211(&7 G G G G G G 5(/($6( G G G G G G5(/($6( &203/(7(G G G G G G FFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.20: Signalling for notification of invocation of CFNRy supplementary service The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that CFNRy is active, then if required, either one of the DISCONNECT, RELEASE, RELEASE COMPLETE or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.82. 5.3.2 CCBS Request Activation As described in GSM 02.93, when subscriber A encounters a busy destination B, subscriber A can request the CCBS supplementary service (i.e. activate a CCBS request against destination B). The signalling for this situation is shown in figure 5.21. MS MSC VLR HLR HFI HFI HFI HFI G G ',6&211(&7 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G G G 5(/($6( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G &&%6 5(48(67 G G G G G G G GFFFFFFFFFFFFFFFFF!G G 5(*,67(5B&& (175<G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G G G G G 5(*,67(5B&& G G G G G G G G (175<B$&. G G G G G G G G 5(*,67(5B&& G G G G G G G G (175<B(5525 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G&&%6 5(48(67 (5525G G G G G G G G &&%6 5(48(67 $&. G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G 5(/($6( &203/(7( G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G Figure 5.21: Signalling for CCBS Request Activation (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 23 3G TS 29.011 version 3.0.0 The MS request the activation of CCBS in a Facility information element of a RELEASE message in response to a DISCONNECT message containing the diagnostic CCBS is possible and the Allowed Actions information element set to Recall is possible. Then, the MSC transmits the request in an Invoke component together with the call information towards the VLR in a CCBS_REQUEST message on the B-interface. The VLR forwards it in a MAP_REGISTER_CC_ENTRY on the D-interface. The outcome of the activation is sent back by the HLR in a MAP_REGISTER_CC_ENTRY_ACK or a MAP_REGISTER_CC_ENTRY_ERROR message. This outcome is subsequently mapped and inserted in the Facility information element of the RELEASE COMPLETE message from the MSC to the MS. Exact values of the parameters and parameter tags are indicated in GSM 04.08, GSM 04.80, GSM 04.93 and GSM 09.02. 5.3.3 Call Deflection service 5.3.3.1 Call Deflection Operation Request As described in GSM 04.72, a MS may signal invocation of the Call Deflection supplementary service for a mobile terminated call at any time after call confirmation until the call is accepted. The signalling for this situation is shown in figure 5.22. MS MSC VLR HFI HFI HFI G G G G G G G G ',6&211(&7 G G &203/(7( &$// (5525 352&(66 &$// :$,7,1* (5525 G G G GFFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G G G Figure 5.22: Signalling of a Call Deflection Request The MS requests Invocation of Call Deflection by including a CallDeflection operation (defined in GSM 04.80) in a DISCONNECT message. The parameters of the CallDeflection operation of the DISCONNECT message shall be transferred by the MSC to the VLR with the B-interface COMPLETE_CALL_ERROR or PROCESS_CALL_WAITING_ERROR message. 5.3.3.2 Call Deflection Operation Response Optimal Routeing of late call forwarding is not invoked The signalling for this situation is shown in figure 5.23. MS MSC VLR HFI HFI HFI G G G G G G G G G G &203/(7( &$// (5525 352&(66 &$// :$,7,1* (5525 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783 $&. G G G G G G 6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783 (5525 G G G G 5(/($6( G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFG G G G G G G G G G Figure 5.23: Mapping of Call Deflection Response without SOR The MSC shall send a CallDeflection return result to the MS if the SEND_INFO_FOR_INCOMING_CALL_ACK message is received from the VLR and the invocation of Optimal Routeing is not requested. The MSC shall send a CallDeflection return error to the MS if a SEND_INFORMATION_FOR_INCOMING_CALL_SETUP ERROR message is received from the VLR. The MSC shall obtain the value of the CallDeflection error from the error received in the SEND_INFORMATION_FOR_INCOMING_CALL_SETUP ERROR message. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 24 3G TS 29.011 version 3.0.0 Optimal Routeing of late call forwarding is invoked: The signalling for this situation is shown in figure 5.24. MS MSC VLR GMSC HFI HFI HFI HFI G G G G 6(1' ,1)250$7,21 G G G G G G G G )25 ,1&20,1* &$//G G G G G G G G 6(783 $&. G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G 5(680( &$// +$1'/,1* G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 5(680( &$// +$1'/,1* $&. G G G G G G 5(680( &$// +$1'/,1* (5525 G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 5(/($6( G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.24: Mapping of Call Deflection Response in case of SOR If for a Call Deflection Request Optimal Routeing of late call forwarding is invoked the MSC shall send a CallDeflection return result to the MS if the MAP_RESUME_CALL_HANDLING_ACK is received from the GMSC. If a MAP_RESUME_CALL_HANDLING_ERROR message with error "ForwardingFailed" is received from the GMSC the MSC shall send a CallDeflection return error "ForwardingFailed" to the MS. Reception of other errors than "ForwardingFailed" in the MAP_RESUME_CALL_HANDLING_ERROR message shall lead to local processing in the MSC. Exact values of the parameters and parameter tags are indicated in GSM 04.80 and GSM 09.02. 6 Call independent supplementary services management 6.1 MS initiated SS Management 6.1.1 Connection establishment phase Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. When a request to open such a connection arrives at the MSC, the MSC will request access permission from the VLR, as described in GSM 09.02. It will also assess the capabilities of the MS according to the screening indicator, as described in GSM 04.10 and GSM 04.80. The signalling for this situation is shown in figure 6.1. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G &0 VHUYLFH UHTXHVW G G G G G G &0 VHUYLFH W\SH G G G G G G 66 $FWLYDWLRQ G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFF!G G $B&0B6(59B5(4 G G G G G G &0 VHUYLFH W\SH G G G G G G 66 $FWLYDWLRQ G G G G G GFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.1: Signalling flow for SS connection establishment (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 25 3G TS 29.011 version 3.0.0 6.1.2 Connection established At this stage of the connection, the version negotiation mechanism will be invoked as described in clause 3. The abstract definition of the protocol used for call independent SS operations is imported directly from GSM 09.02 into GSM 04.80. The signalling for invocation of a supplementary service operation is shown in figure 6.2, while figure 6.3 shows the signalling for returning the result of the supplementary service operation. Tables 6.1 and 6.2 show the mapping of GSM 04.80 operation codes to MAP service primitives, and vice versa respectively. The detailed mapping of the contents of the facility information elements to the service primitives triggering the MAP user are described in subclause 6.3. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G 5(*,67(5)$&,/,7< G G G G G G 66 23(5$7,21 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFF!G G66B6(59,&( 35,0,7,9( 5(4G G G G G GFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.2: Signalling flow for SS operation invocation (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 26 3G TS 29.011 version 3.0.0 Choice of service primitive on the basis of received facility information element is as follows: Table 6.1: Mapping of GSM 04.80 operations to GSM 09.02 service primitives Facility information element operation Service primitive for MAP Service user RegisterSS A_REGISTER_SS EraseSS A_ERASE_SS ActivateSS A_ACTIVATE_SS DeactivateSS A_DEACTIVATE_SS InterrogateSS A_INTERROGATE_SS RegisterPassword A_REGISTER_PASSWORD ProcessUnstructuredSS-Request A_PROCESS_UNSTRUCTURED_SS_REQUEST EraseCC-Entry A_ERASE_CC_ENTRY MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G 5(*,67(5)$&,/,7< G G66B6(59,&( 35,0,7,9( &1)G G G G 66 23(5$7,21 G G FFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 6.3: Signalling flow for SS operation return result Choice of facility information element on the basis of received service primitive is as follows: Table 6.2: Mapping of GSM 09.02 service primitives to GSM 04.80 operations Service primitive for MAP Service user Facility information element operation A_REGISTER_SS RegisterSS A_ERASE_SS EraseSS A_ACTIVATE_SS ActivateSS A_DEACTIVATE_SS DeactivateSS A_INTERROGATE_SS InterrogateSS A_REGISTER_PASSWORD RegisterPassword A_PROCESS_UNSTRUCTURED_SS_REQUEST ProcessUnstructuredSS-Request A_UNSTRUCTURED_SS_REQUEST UnstructuredSS-Request A_UNSTRUCTURED_SS_NOTIFY ProcessUnstructuredSS-Notify A_GET_PASSWORD GetPassword A_REGISTER_CC_ENTRY AccessRegisterCCEntry A_ERASE_CC_ENTRY EraseCCEntry 6.1.3 Connection release A supplementary service control connection is usually released by the network. The signalling for this situation is shown in figure 6.4. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G G G $B&0B5(/B&203 G G G G 5(/($6( &203/(7( G G FFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 6.4: Signalling flow for SS connection release by the network (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 27 3G TS 29.011 version 3.0.0 However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G 5(/($6( &203/(7( G G G G G GFFFFFFFFFFFFFFFFFFF!G G $B&0B6(59B5(/ G G G G G GFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.5: Signalling flow for SS connection release by the MS 6.2 Network initiated SS Management 6.2.1 Connection establishment phase Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. The MSC may need to open a connection towards the MS (as described in GSM 04.08) to send the Network initiated SS operation to the MS. Detailed mapping rules are described in subclause 6.3. 6.2.2 Connection established The abstract definition of the protocol used for call independent SS operations is imported directly from GSM 09.02 into GSM 04.80. The signalling for invocation of a Network initiated SS operation is shown in figure 6.6, while figure 6.7 shows the signalling for returning the result of supplementary service operation. Choice of facility information element on the basis of received service primitive is described in table 6.2. MS MSC MAP User in MSC HFI HFI HFI G G G G66B6(59,&( 35,0$7,9( 5(4G G G G G G FFFFFFFFFFFFFFFFFFFFFFFG G G G 5(*,67(5)$&,/,7< G G G G G G 66 23(5$7,21 G G G G G G FFFFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 6.6: Signalling flow for Network Initiated SS operation invocation Choice of service primitive on the basis of received facility information element is described in table 6.2. MS MSC MAP User in MSC HFI HFI HFI G G )$&,/,7< G G G G G G 66 23(5$7,21 G G G G G GFFFFFFFFFFFFFFFFFFF!G G G G G G G G66B6(59,&( 35,0$7,9( &1)G G G G G GFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.7: Signalling flow for Network Initiated SS operation return result 6.2.3 Connection release A Network initiated SS connection is usually released by the network. The signalling for this situation is shown in figure 6.4. However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 28 3G TS 29.011 version 3.0.0 6.2.4 ForwardCheckSSIndication When a mobile station first makes contact with the network after there has been a HLR restart, an indication may be sent by the HLR to the MS to inform of possible unintended consequences with respect to supplementary services. This indication is a separate service in the MAP (MAP_FORWARD_CHECK_SS_INDICATION service), and the abstract definition of its operation (ForwardCheckSSIndication) is imported into the GSM 04.80 protocol. Upon receipt of ForwardCheckSSIndication from the VLR, the MSC shall create a new call independent SS transaction and then send ForwardCheckSSIndication (see GSM 04.10). The MSC is only required to deliver ForwardCheckSSIndication if there is an active RR connection to the MS. The network shall not page the MS in order to deliver ForwardCheckSSIndication. MS MSC VLR HLR HFI HFI HFI HFI G G G G G G)RUZDUG&KHFN66,QGG G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G)RUZDUG&KHFN66,QGG G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G)RUZDUG&KHFN66,QGG G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G Figure 6.8: ForwardCheckSSIndication 6.2.5 CCBS Recall As described in GSM 02.93, when destination B, target of a CCBS request activated by subscriber A, becomes idle, the network shall automatically recall subscriber A. When subscriber A accepts the recall, the network will automatically generate a CCBS call to destination B. The signalling for this situation is shown in figure 6.9. MS MSC VLR HLR HFI HFI HFI HFI G G G G G G 5(027(B86(5 )5(( G G G G G G G G FFFFFFFFFFFFFFFFFFFG G G G G G &&%6 58) G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G&0 6(59,&( 352037 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G G G 3URFHGXUH GHILQHGG G G G G G G G LQ *60 G G G G G G G G G G G G G G G G G G G G G G G G 6(783 G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G &&%6 58) $&. G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G5(027(B86(5 )5((B$&.G G G G G G G GFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G Figure 6.9: Signalling for CCBS Recall The indication of destination B idle is sent in the MAP_REMOTE_USER_FREE service primitive. It is transmitted on the D-interface and relayed on the B-interface. Then, the recall procedure starts with the establishment of a CC connection initiated by the network with the CM SERVICE PROMPT message. The following exchange of message concerns only the A-interface and is not described here since it is already done in GSM 04.93. The acceptation of the recall by the user is implicit in the SETUP message sent by the MS to the MSC. This message contains the call information previously sent to the MS and the indication that the call in its establishment phase is a CCBS call. The MSC informs the HLR of this acceptation by sending a MAP_REMOTE_USER_FREE_ACK message on the B-interface and further on the D-interface. In case an error occurs (e.g. MS not reachable or Incompatible terminal), at any time of the recall procedure (i.e. just after the error has been received), the MSC shall send the MAP_REMOTE_USER_FREE_ERROR with the appropriate value for the Error information element. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 29 3G TS 29.011 version 3.0.0 Exact values of the parameters and parameter tags are indicated in GSM 04.08, GSM 04.93 and GSM 09.02. 6.2.6 CCBS Monitoring The monitoring process is initiated by the network. It is started on the B-side as soon as subscriber B becomes a target of a CCBS request. It is started on the A-side when subscriber A is found to be busy or suspends a request while being offered a recall. Since the status of a subscriber is linked to its activity, a message sent by the MS to the MSC may lead to the transmission of a message containing the new status on the D-interface (i.e. the MAP_STATUS_REPORT service primitive). This message contains a Status information element which can take the value Idle, Not_Reachable or Not Idle. Several situations might occur, they are described in the figure 6.10. MS MSC VLR HLR HFI HFI HFI HFI G G G G G G G G a. G G&0 6(59,&( 5(48(67G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G 06 $&7,9,7< G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G b. G G ,06, '(7$&+ G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G '(7$&+ ,06, G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G c. G G 5(/($6( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G &$// (1' G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G d. G G 6(783 G G G GFFFFFFFFFFFFFFFFF!G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G 127 ,'/( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G Figure 6.10: Signalling for CCBS Monitoring For all these situations (from a to d), the transmission of the MAP_STATUS_REPORT service primitive depends on the possible change of status of the MS. The detailed behaviour of this procedure is described in GSM 03.93. Exact coding and values of the messages are indicated in GSM 04.08 and GSM 09.02. 6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents 6.3.1 Operation codes The same operation codes are used for equivalent operations in GSM 04.80 and GSM 09.02 for call independent supplementary service management. 6.3.2 Error codes For call independent supplementary service management, the same error codes are used for equivalent error types in GSM 04.80 and GSM 09.02. The RETURN ERROR components are also constructed in the same way on both sides of the interface. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 30 3G TS 29.011 version 3.0.0 The same parameter tags and parameter values are used for equivalent parameters in GSM 04.80 and GSM 09.02. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 31 3G TS 29.011 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 09.11 7.0.0 Transferred to 3GPP CN1 CN#03 29.011 3.0.0 Approved at CN#03 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 32 ETSI ETSI TS 129 011 V3.0.0 (2000-01) (3G TS 29.011 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 0.1 References | .......................................................................................................................................................... 5 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 0.2 Abbreviations | ..................................................................................................................................................... 6 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1 MultiParty service (MPTY) | .....................................................................................................................7 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.1 Beginning the MultiParty service | ...................................................................................................................... 7 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2 Managing an active MultiParty call | ................................................................................................................... 8 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.1 Served mobile subscriber | ............................................................................................................................. 8 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.1.1 Put the MultiParty call on hold | ............................................................................................................... 8 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.1.2 Create a private communication with one of the remote parties | ............................................................. 8 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.1.3 Terminate the entire MultiParty call | ....................................................................................................... 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.1.4 Explicitly disconnect a remote party | ...................................................................................................... 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.2 Remote Parties | ............................................................................................................................................. 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.2.1 Release from the MultiParty call | ............................................................................................................ 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.2.2.2 Place his connection to the MultiParty call on hold, and typically later retrieve it | ................................. 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3 Managing a held MultiParty call | ........................................................................................................................ 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.1 Served mobile subscriber | ............................................................................................................................. 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.1.1 Retrieve the held MultiParty call | ............................................................................................................ 9 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.1.2 Initiate a new call | .................................................................................................................................. 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.1.3 Process a call waiting request | ............................................................................................................... 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.1.4 Terminate the held MultiParty call | ....................................................................................................... 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.1.5 Explicitly disconnect a remote party | .................................................................................................... 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.3.2 Remote parties | ............................................................................................................................................ 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4 Managing a single call and a MultiParty call | ................................................................................................... 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4.1 Served mobile subscriber | ........................................................................................................................... 10 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4.1.1 Disconnect the single call | ..................................................................................................................... 11 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4.1.2 Disconnect the MPTY | .......................................................................................................................... 11 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4.1.3 Disconnect all calls | ............................................................................................................................... 11 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4.1.4 Add the single call to the MPTY | .......................................................................................................... 11 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.4.1.5 Alternate between the MPTY call and the single call | ........................................................................... 11 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.5 Adding extra remote parties | ............................................................................................................................. 11 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.6 Auxiliary states for MPTY | .............................................................................................................................. 12 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.7 Activation, deactivation, registration, erasure and interrogation | ..................................................................... 12 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 1.8 Simultaneous use of MultiParty operations | ..................................................................................................... 12 Annex A: Change history......................................................................................................................13 History..............................................................................................................................................................14 ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 4 3G TS 24.084 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS specifies the procedures used at the radio interface for normal operation and invocation of MultiParty 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; ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 5 3G TS 24.084 version 3.0.0 |
2db8737326eb47c66bc9dbdbc50e66e0 | 124 084 | 0 Scope | The present document specifies the procedures used at the radio interface (Reference point Um as defined in GSM 04.02) for normal operation and invocation of MultiParty supplementary services. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and the GSM 02.8x and GSM 02.9x-series. GSM 02.84 is related specially to MultiParty supplementary services. Technical realization of supplementary services is described in GSM 03.11 and the GSM 03.8x and GSM 03.9x-series. GSM 03.84 is related specially to MultiParty supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary service belongs to the MultiParty supplementary services and is described in the present document: - MultiParty service (MPTY) (clause 1). 0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. β’ References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. β’ For a specific reference, subsequent revisions do not apply. β’ For a non-specific reference, the latest version applies. β’ A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [5] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [6] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [7] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 6 3G TS 24.084 version 3.0.0 [8] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) supplementary services - Stage 1". [9] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [10] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 1". [11] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [12] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [13] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [14] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [15] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [16] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [17] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [18] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [19] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [20] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [21] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [22] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [23] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [24] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [25] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 7 3G TS 24.084 version 3.0.0 1 MultiParty service (MPTY) 1.1 Beginning the MultiParty service The served mobile subscriber A may initiate an active MultiParty call from an active call C and a held call B. The mobile station invokes the service by sending a FACILITY message to the network containing the BuildMPTY request. This BuildMPTY request indicates to the network that the mobile subscriber wishes all his calls to be connected together in a MultiParty call. The network will normally accept the request and connect the mobile subscriber with the other existing connections (active call C and held call B). If the request is not accepted, the network will indicate the error to the served mobile (see figure 1.1). The network confirms with the same transaction identifier. Error values are specified in GSM 04.80. During the BuildMPTY operation the MS shall run a timer T(BuildMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. MS Network FACILITY (TI A-B/A-C) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = BuildMPTY) FACILITY (TI A-B/A-C) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-B/A-C) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-B/A-C) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: A-B/A-C indicates a choice. The transaction identifier (TI) used must be that of the active call or the held call. Figure 1.1: Invocation of the MultiParty call If the network received a non-zero SS Screening indicator from the remote party's mobile station the network will also send indications towards the remote parties that the MultiParty call has been invoked, and towards the previously-held party to indicate that he is now retrieved (see figures 1.2 and 1.3). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. B Network FACILITY (TI A-B) <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (HOLD, CallOnHold-indicator), Invoke = NotifySS (MPTY, MPTYindicator)) NOTE: The CallOnHold notification (CallOnHold-indicator) sent to the remote subscriber is the same as described in GSM 04.83. Figure 1.2: Notification of invocation to previously-held remote party C Network FACILITY (TI A-C) <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (MPTY, MPTYindicator)) Figure 1.3: Notification of invocation to previously-active remote party ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 8 3G TS 24.084 version 3.0.0 1.2 Managing an active MultiParty call 1.2.1 Served mobile subscriber During an active MultiParty call the served mobile subscriber can request the network to: 1.2.1.1 Put the MultiParty call on hold This is achieved by sending a FACILITY message to the network with any transaction identifier corresponding to a call within the MultiParty call. This requests the network to place the mobile subscriber's connection to the MultiParty call on hold. The network confirms with another message containing the same transaction identifier (see figure 1.4). During the HoldMPTY operation the MS shall run a timer T(HoldMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. MS Network FACILITY (TI A-X) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = HoldMPTY) FACILITY (TI A-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: X = Any remote party in MultiParty call. Figure 1.4: Served mobile subscriber places his connection to the MultiParty call on hold Indications are sent towards all remote parties in the MultiParty call by means of normal CallOnHold notifications as described in GSM 04.83. 1.2.1.2 Create a private communication with one of the remote parties To create a private communication with one of the remote parties, the served mobile will send a SplitMPTY message to the network (see figure 1.5). The network will send normal CallOnHold notifications to the remote parties on hold in the MPTY call. During the SplitMPTY operation the MS shall run a timer T(SplitMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 9 3G TS 24.084 version 3.0.0 MS Network FACILITY (TI A-X) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = SplitMPTY) FACILITY (TI A-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: X = Party with which to establish a private communication. Figure 1.5: Served mobile subscriber requests a private communication with a single remote party 1.2.1.3 Terminate the entire MultiParty call The MultiParty call is terminated by disconnecting all individual parties as described in subclause 1.2.1.4. 1.2.1.4 Explicitly disconnect a remote party Any remote party may be individually disconnected by initiation of call clearing as defined in GSM 04.08 with the same transaction identifier corresponding to that party. 1.2.2 Remote Parties During an active MultiParty call any conferee is able to: 1.2.2.1 Release from the MultiParty call In this case, the network will initiate the call clearing procedure towards the served mobile subscriber as defined in GSM 04.08 with the transaction identifier corresponding to the disconnecting party. 1.2.2.2 Place his connection to the MultiParty call on hold, and typically later retrieve it Where a held/retrieved indication is received from any remote party, the network will forward this to the served mobile subscriber (see GSM 04.83). 1.3 Managing a held MultiParty call 1.3.1 Served mobile subscriber During a held MultiParty call the served mobile subscriber can request the network to: 1.3.1.1 Retrieve the held MultiParty call To retrieve the held MultiParty call, a FACILITY message is sent to the network with a transaction identifier corresponding to any call in the MPTY. The network confirms the retrieval with another message containing the same transaction identifier (see figure 1.6). ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 10 3G TS 24.084 version 3.0.0 During the RetrieveMPTY operation the MS shall run a timer T(RetrieveMPTY). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re-attempt the operation or inform the user of the failure. MS Network FACILITY (TI A-X) ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RetrieveMPTY) FACILITY (TI A-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) FACILITY/DISCONNECT/RELEASE/RELEASE COMPLETE (TI A-X) <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: X = Any remote party in MultiParty call. Figure 1.6: Served mobile subscriber retrieves MultiParty call Indications are sent towards all remote parties by means of normal CallOnHold (= CallRetrieved) notifications as described in GSM 04.83. 1.3.1.2 Initiate a new call This is achieved by normal call set-up procedures (GSM 04.08). 1.3.1.3 Process a call waiting request This is described in GSM 04.83. 1.3.1.4 Terminate the held MultiParty call This is achieved by the same procedure as in subclause 1.2.1.3. 1.3.1.5 Explicitly disconnect a remote party This is achieved by the same procedure as in subclause 1.2.1.4. 1.3.2 Remote parties During a held MultiParty call any remote party is able to perform the same operations as described for an active MultiParty call in subclause 1.2.2. 1.4 Managing a single call and a MultiParty call 1.4.1 Served mobile subscriber If the served mobile subscriber is connected to a MultiParty call (active or on hold) and another single call (active or on hold), he can request the network to: ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 11 3G TS 24.084 version 3.0.0 1.4.1.1 Disconnect the single call This is achieved by using the call clearing procedure as described in GSM 04.08 with the transaction identifier corresponding to the single call. 1.4.1.2 Disconnect the MPTY This is achieved by the same procedure as disconnecting a held/active MPTY without another call (see subclauses 1.2.1 and 1.3.1). 1.4.1.3 Disconnect all calls This is achieved by using the procedures in subclauses 1.4.1.1 and 1.4.1.2. 1.4.1.4 Add the single call to the MPTY The served mobile subscriber may request the connection of all his calls, held and active, into an active MultiParty call at any time by sending a FACILITY message with the transaction identifier corresponding to any remote party and containing the BuildMPTY invoke component (see subclause 1.1). This procedure will apply whether the MultiParty call is on hold or active, and whether the single call is on hold or active. If the request is successful, previously held remote parties will receive an MPTY notification and a CallRetrieved notification as shown in figure 1.2, and previously active remote parties will receive an MPTY notification as shown in figure 1.3. If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. If the request is unsuccessful e.g. because the maximum number of remote parties has already been reached, then an error is returned to the served mobile subscriber, as shown in figure 1.1. Error values are specified in GSM 04.80. 1.4.1.5 Alternate between the MPTY call and the single call This procedure follows the Alternate procedure defined in GSM 04.83 with the exception that the MPTY call is held/retrieved using HoldMPTY/RetrieveMPTY in place of HOLD/RETRIEVE as follows: Single call MPTY call (Facility) HOLD Invoke (HoldMPTY) HOLD ACKNOWLEDGE Return result HOLD REJECT Return error (error) RETRIEVE Invoke (RetrieveMPTY) RETRIEVE ACKNOWLEDGE Return result RETRIEVE REJECT Return error (error) 1.5 Adding extra remote parties Extra remote parties are added by placing the MultiParty call on hold (subclause 1.2.1.1), setting up a new connection (either a new call or a waiting call) and then sending a FACILITY message to the network requesting that the active call be joined with the MPTY, using the same signalling as for invocation (see figure 1.1). This results in an active MultiParty call. Notifications are sent as for the initial invocation (i.e. previously-held parties in MPTY receive CallRetrieved notifications and MPTY notifications; the new remote party only receives an MPTY notification) (see figures 1.2 and 1.3). If the network did not receive a non-zero SS Screening indicator from the remote party's mobile station it shall not send a notification. If the request is not accepted, e.g. because the maximum number of remote parties has already been reached, then the error is indicated to the mobile station. Error values are specified in GSM 04.80. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 12 3G TS 24.084 version 3.0.0 1.6 Auxiliary states for MPTY In the call hold service (GSM 04.83), a two dimensional state space is defined, where the first dimension corresponds to the GSM 04.08 call control state and the second dimension corresponds to the call hold state (Idle, Hold Request, Call Held, Retrieve Request). For the purposes of the MPTY service, it is necessary to introduce another dimension to this state space, i.e. the MultiParty state. There are four auxiliary states associated with the MPTY service: - Idle; - MPTY request; A request has been made to add this call to the MPTY. - Call in MPTY; This call is in the MPTY. - Split request; A request has been made to remove this call from the MPTY. These Auxiliary states apply in addition to the GSM 04.08 call control states and the GSM 04.83 call hold states. Thus for example, an active call in a held MPTY has the state (Active, Call held, Call in MPTY). Not all states are allowed, for example an MPTY cannot be split while it is held, so (Active, Call held, Split request) is forbidden. 1.7 Activation, deactivation, registration, erasure and interrogation Activation, deactivation, registration, erasure and interrogation of the MultiParty service are not applicable. 1.8 Simultaneous use of MultiParty operations The operations BuildMPTY, SplitMPTY, HoldMPTY and RetrieveMPTY interact with each other, and cannot be applied simultaneously. Once the mobile station has initiated one of these operations, it shall not initiate another MultiParty operation until the first operation has been acknowledged by the network, or the MS locally determines (due to timer expiry) that the first operation has failed. The use of several MultiParty operations as different components in the same message is not allowed. ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.084 V3.0.0 (1999-05) 13 3G TS 24.084 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.84 6.0.0 Transferred to 3GPP CN1 CN#03 24.084 3.0.0 Approved at CN#03 ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) ETSI 14 ETSI ETSI TS 124 084 V3.0.0 (2000-01) (3G TS 24.084 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 1 Scope | ........................................................................................................................................................5 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 2 Normative references | ...............................................................................................................................5 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 3 Definitions, symbols and abbreviations | ...................................................................................................6 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 3.1 Definitions | ......................................................................................................................................................... 6 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 3.2 Symbols | ............................................................................................................................................................. 6 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 3.3 Abbreviations | ..................................................................................................................................................... 6 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 4 General | .....................................................................................................................................................7 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 5 Functions on the transmit (TX) side | ........................................................................................................7 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 5.1 LSF evaluation | ................................................................................................................................................... 8 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 5.2 Frame energy calculation | ................................................................................................................................... 8 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 5.3 Modification of the speech encoding algorithm during SID frame generation | .................................................. 9 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 5.4 SID-frame encoding | ........................................................................................................................................... 9 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 6 Functions on the receive (RX) side | ..........................................................................................................9 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 6.1 Averaging and decoding of the LP and energy parameters | ............................................................................... 9 6. 2 Comfort noise generation and updating........................................................................................................... 10 |
9cfb9318b04cdace4e6b2fc06f7cf91e | 126 092 | 7 Computational details and bit allocation | ................................................................................................11 Annex A: Change history......................................................................................................................12 History..............................................................................................................................................................13 (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 4 3G TS 26.092 version 3.0.1 Foreword This Technical Specification has been produced by the 3GPP. The present document defines the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in the narrowband telephony speech service employing the Adaptive Multi-Rate (AMR) speech coder 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; (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 5 3G TS 26.092 version 3.0.1 1 Scope This document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation for the AMR speech codec during Source Controlled Rate (SCR) operation. The requirements described in this document are mandatory for implementation in all UEs capable of supporting the AMR speech codec. The receiver requirements are mandatory for implementation in all networks capable of supporting the AMR speech codec, the transmitter requirements only for those where downlink SCR will be used. In case of discrepancy between the requirements described in this document and the fixed point computational description of these requirements contained in [1], the description in [1] will prevail. 2 Normative references This document incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this document only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. [1] 3G TS 26.073 : "AMR Speech Codec; ANSI-C code". [2] 3G TS 26.090 : "AMR Speech Codec; Transcoding functions". [3] 3G TS 26.091 : "AMR Speech Codec; Error concealment of lost frames ". [4] 3G TS 26.093 : "AMR Speech Codec; Source Controlled Rate operation ". [5] 3G TS 26.101 : "AMR Speech Codec; Frame Structure". (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 6 3G TS 26.092 version 3.0.1 3 Definitions, symbols and abbreviations 3.1 Definitions For the purpose of this document, the following definitions apply. Frame: Time interval of 20 ms corresponding to the time segmentation of the adaptive multi-rate speech transcoder, also used as a short term for traffic frame. SID frames: Special Comfort Noise frames. It may convey information on the acoustic background noise or inform the decoder that it should start generating background noise. Speech frame: Traffic frame that cannot be classified as a SID frame. VAD flag: Voice Activity Detection flag. TX_TYPE: one of SPEECH, SID_FIRST, SID_UPD, NO_DATA (defined in [4]). RX_TYPE: Classification of the received traffic frame (defined in [4]). Other definitions of terms used in this document can be found in [2] and [4]. The overall operation of SCR is described in [4]. 3.2 Symbols For the purpose of this document , the following symbols apply. Boldface symbols are used for vector variables. [ ] f T f f f = 1 2 10 ... Unquantized LSF vector [ ] ... f T f f f = 1 2 10 Quantized LSF vector f ( ) m Unquantized LSF vector of frame m f ( ) m Quantized LSF vector of frame m f mean Averaged LSF parameter vector enlog Logarithmic frame energy enmean log Averaged logarithmic frame energy f ref Reference vector for LSF quantization e Computed LSF parameter prediction residual e Quantized LSF parameter prediction residual x n n a b ( ) =β ( ) ( ) ( ) ( ) = + + + + β + x a x a x b x b 1 1 3.3 Abbreviations For the purpose of this document , the following abbreviations apply. (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 7 3G TS 26.092 version 3.0.1 AMR Adaptive Multi-Rate SCR Source Controlled Rate operation ( aka source discontinuous transmission ) UE User Equipment SID SIlence Descriptor LP Linear Prediction LSP Line Spectral Pair LSF Line Spectral Frequency RX Receive TX Transmit VAD Voice Activity Detector 4 General A basic problem when using SCR is that the background acoustic noise, which is transmitted together with the speech, would disappear when the transmission is cut, resulting in discontinuities of the background noise. Since the SCR switching can take place rapidly, it has been found that this effect can be very annoying for the listener - especially in a car environment with high background noise levels. In bad cases, the speech may be hardly intelligible. This document specifies the way to overcome this problem by generating on the receive (RX) side synthetic noise similar to the transmit (TX) side background noise. The comfort noise parameters are estimated on the TX side and transmitted to the RX side at a regular rate when speech is not present. This allows the comfort noise to adapt to the changes of the noise on the TX side. 5 Functions on the transmit (TX) side The comfort noise evaluation algorithm uses the following parameters of the AMR speech encoder, defined in [2]: - the unquantized Linear Prediction (LP) parameters, using the Line Spectral Pair (LSP) representation, where the unquantized Line Spectral Frequency (LSF) vector is given by [ ] f T f f f = 1 2 10 ... ; - the unquantized LSF vector for the 12.2 kbit/s mode is given by the second set of LSF parameters in the frame. The algorithm computes the following parameters to assist in comfort noise generation: - the averaged LSF parameter vector f mean (average of the LSF parameters of the eight most recent frames); - the averaged logarithmic frame energy enmean log (average of the logarithmic energy of the eight most recent frames). These parameters give information on the level (enmean log ) and the spectrum ( f mean ) of the background noise. The evaluated comfort noise parameters ( f mean andenmean log ) are encoded into a special frame, called a Silence Descriptor (SID) frame for transmission to the RX side. A hangover logic is used to enhance the quality of the silence descriptor frames. A hangover of seven frames is added to the VAD flag so that the coder waits with the switch from active to inactive mode for a period of seven frames, during that time the decoder can compute a silence descriptor frame from the quantized LSFs and the logarithmic frame energy of the decoded speech signal. Therefore, no comfort noise description is transmitted in the first SID frame after active speech. If the background noise contains transients which will cause the coder to switch to active mode and then back to inactive mode in a very short timeperiod, no hangover is used. Instead the previously used comfort noise frames are used for comfort noise generation. (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 8 3G TS 26.092 version 3.0.1 The first SID frame also serves to initiate the comfort noise generation on the receive side, as a first SID frame is always sent at the end of a speech burst, i.e., before the transmission is terminated. The scheduling of SID or speech frames on the network path is described in [4]. 5.1 LSF evaluation The comfort noise parameters to be encoded into a SID frame are calculated over N = 8 consecutive frames marked with VAD=0, as follows: The averaged LSF parameter vector ( ) f mean i of the frame i shall be computed according to the equation: ( ) f f mean n i i n = β =β 1 8 0 7 ( ) (1) where ( ) f i n β is the (unquantized) LSF parameter vector of the current frame i ( n = 0) and past frames (n = 1 7 , , ). The averaged LSF parameter vector ( ) f mean i of the frame i is encoded using the same encoding tables that are also used by the 7.4 kbit/s mode for the encoding of the non-averaged LSF parameter vectors in ordinary speech encoding mode, but the quantization algorithm is modified in order to support the quantization of comfort noise. The LSF parameter prediction residual to be quantized for frame i is obtained according to the following equation: ( ) ( ) e f f i i mean ref = β (2) where f ref is a reference vector picked from a codebook. The vector f ref used in eq (2) is encoded for each SID frame. A lookup table containing 8 vectors typical for background noise are searched. The vector which yields the lowest prediction residual energy is selected. After the above step the LSF parameter encoding procedure is performed. The 3-bit index for the reference vector and the 26 bits for LSF parameter are transmitted in the SID frame (see bit allocation in table 1). 5.2 Frame energy calculation The frame energy is computed for each frame marked with VAD=0 according to the equation : ( ) ( ) en i N s n n N log log =  ο£ο£¬ ο£Ά ο£Έο£· = β β 1 2 1 2 2 0 1 (3) where ( ) s n is the HP-filtered input speech signal of the current frame i. The averaged logarithmic energy is computed by: ( ) en i en i n mean n log log( ) = β =β 1 8 0 7 . (4) The averaged logarithmic energy is quantized means of a 6 bit algorithmic quantizer. The 6 bits for the energy index are transmitted in the SID frame (see bit allocation in table 1). (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 9 3G TS 26.092 version 3.0.1 5.3 Modification of the speech encoding algorithm during SID frame generation When the TX_TYPE is not equal to SPEECH the speech encoding algorithm is modified in the following way: - The non-averaged LP parameters which are used to derive the filter coefficients of the filters ( ) H z and ( ) W z of the speech encoder are not quantized; - The open loop pitch lag search is performed, but the closed loop pitch lag search is inactivated. The adaptive codebook gain and memory is set to zero. - No fixed codebook search is made. - The memory of weighting filter ( ) W z is set to zero, i.e., the memory of ( ) W z is not updated. - The ordinary LP parameter quantization algorithm is inactive. The averaged LSF parameter vector f mean is calculated each time a new SID frame is to be sent to the AN. This parameter vector is encoded into the SID frame as defined in subclause 5.1. - The ordinary gain quantization algorithm is inactive. - The predictor memories of the ordinary LP parameter quantization and fixed codebook gain quantization algorithms are initialized when TX_TYPE is not SPEECH, so that the quantizers start from known initial states when the speech activity begins again. 5.4 SID-frame encoding The encoding of the comfort noise bits in a SID frame is described in [5] where the indication of the first SID frame is also described. The bit allocation and sequence of the bits from comfort noise encoding is shown in Table 1. 6 Functions on the receive (RX) side The situations in which comfort noise shall be generated on the receive side are defined in [4]. In general, the comfort noise generation is started or updated whenever a valid SID frame is received. 6.1 Averaging and decoding of the LP and energy parameters When speech frames are received by the decoder the LP and the energy parameters of the last seven speech frames shall be kept in memory. The decoder counts the number of frames elapsed since the last SID frame was updated and passed to the RSS by the encoder. Based on this count, the decoder determines whether or not there is a hangover period at the end of the speech burst (defined in[4] ). The interpolation factor is also adapted to the SID update rate. As soon as a SID frame is received comfort noise is generated at the decoder end. The first SID frame parameters are not received but computed from the parameters stored during the hangover period. If no hangover period is detected, the parameters from the previous SID update are used. The averaging procedure for obtaining the comfort noise parameters for the first SID frame is as follows: - when a speech frame is received, the LSF vector is decoded and stored in memory, moreover the logarithmic frame energy of the decoded signal is also stored in memory. - the averaged values of the quantized LSF vectors and the averaged logarithmic frame energy of the decoded frames are computed and used for comfort noise generation. The averaged value of the LSF vector for the first SID frame is given by: (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 10 3G TS 26.092 version 3.0.1 ( ) ( ) β = β = 7 0 Λ 8 1 Λ n mean n i i f f (5) where ( ) f i n β , n > 0 is the quantized LSF vector of one of the frames of the hangover period and where ( ) 0 Λ β i f = ( ) 1 Λ β i f . The averaged logarithmic frame energy for the first SID frame is given by: ( ) ( ) β = β = 7 0 log log Λ 8 1 Λ n mean n i n e i n e (6) where ( ) log en i n β , n > 0 is the logaritmic vector of one of the frames of the hangover period computed for the decoded frames and where ( ) 0 Λ log β i n e = ( ) 1 Λ log β i n e . For ordinary SID frames, the LSF vector and logarithmic frame energy are computed by table lookup. The energy is also adjusted according to the signalled speech modes capabilities, as to provide high quality transitions from Comfort Noise to Speech. The LSF vector is given by the sum of the decoded reference vector and the decoded LSF prediction residual. During comfort noise generation the spectrum and energy of the comfort noise is determined by interpolation between old and new SID frames. In order to achieve a comfort noise that is less static in appearance the LSF vector is slightly perturbed for each frame by adding a small component based on parameters variations computed in the hangover period. The computation of the perturbation is made by computing the mean LSF vector from the matrix f , this mean vector is then subtracted from each of the elements of f forming a new matrix f . For every frame a mean removed LSF vector is randomly choosen from f and added to the interpolated LSF vector. 6. 2 Comfort noise generation and updating The comfort noise generation procedure uses the adaptive multi-rate speech decoder algorithm defined in [2]. When comfort noise is to be generated, the various encoded parameters are set as follows: In each subframe, the pulse positions and signs of the fixed codebook excitation are locally generated using uniformly distributed pseudo random numbers. The excitation pulses take values of +1 and -1 when comfort noise is generated. The fixed codebook comfort noise excitation generation algorithm works as follows: for (i = 0; i < 40; i++) code[i] = 0; for (i = 0; i < 10; i++) { j = random(4); idx = j * 10 + i; if (random(2) == 1) code[idx] = 1; else code[idx] = -1; } where: code[0..39] fixed codebook excitation buffer; random(4) generates a random integer value, uniformly distributed between 0 and 3; (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 11 3G TS 26.092 version 3.0.1 random(2) generates a random integer value, uniformly distributed between 0 and 1. The fixed codebook gain is computed from the logarithmic frame energy parameter by converting it to the linear domain and normalizing with the gain of LP synthesis filter. The adaptive codebook gain values in each subframe are set to 0, also the memory of the adaptive codebook is set to zero. The pitch delay values in each subframe are set to 40. The LP filter parameters used are those received in the SID frame. The predictor memories of the ordinary LP parameter and fixed codebook gain quantization algorithms are initialized when RX_TYPE is not SPEECH , so that the quantizers start from given initial states when the speech activity begins again. With these parameters, the speech decoder now performs the standard operations described in [2] and synthesizes comfort noise. Updating of the comfort noise parameters (energy and LP filter parameters) occurs each time a valid SID frame is received, as described in [4]. When updating the comfort noise, the parameters above should be interpolated over the SID update period to obtain smooth transitions. A bit exact computational description of comfort noise encoding and generation in form of an ANSI-C source code is found in [1]. The detailed bit allocation and the sequence of bits in the comfort noise encoding is shown in Table 1. Table 1: Source encoder output parameters in order of occurrence and bit allocation for comfort noise encoding. Bits (MSB-LSB) Description s1 β s3 index of reference vector s4 - s11 index of 1st LSF subvector s12 β s20 index of 2nd LSF subvector s21 β s29 index of 3rd LSF subvector s30 β s35 index of logarithmic frame energy (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 3GPP 3G TS 26.092 V3.0.1 (1999-08) 12 3G TS 26.092 version 3.0.1 Annex A: Change history Document history V. 0.1.0 March 1999 First Draft based on GSM 06.92 2.0.0 V. 0.2.1 April 1999 Presented in S4#4 V. 1.0.0 April 22, 1999 Editorial updates V. 2.0.0 June 21, 1999 Presented at S#4 Plenary for approval V. 3.0.0 June 22, 1999 Approved at S#4 Plenary V. 3.0.1 August 22, 1999 Reformatted in 3GPP style (3G TS 26.092 version 3.0.1 Release 1999) ETSI TS 126 092 V3.0.1 (2000-01) ETSI 13 ETSI ETSI TS 126 092 V3.0.1 (2000-01) (3G TS 26.092 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication |
b738be600defdc5decba60fb085dc736 | 126 091 | 1 Scope | ........................................................................................................................................................5 |
b738be600defdc5decba60fb085dc736 | 126 091 | 2 Normative references | ...............................................................................................................................5 |
b738be600defdc5decba60fb085dc736 | 126 091 | 3 Definitions and abbreviations | ..................................................................................................................5 |
b738be600defdc5decba60fb085dc736 | 126 091 | 3.1 Definitions | ......................................................................................................................................................... 5 |
b738be600defdc5decba60fb085dc736 | 126 091 | 3.2 Abbreviations | ..................................................................................................................................................... 6 |
b738be600defdc5decba60fb085dc736 | 126 091 | 4 General | .....................................................................................................................................................6 |
b738be600defdc5decba60fb085dc736 | 126 091 | 5 Requirements | ...........................................................................................................................................6 |
b738be600defdc5decba60fb085dc736 | 126 091 | 5.1 Error detection | ................................................................................................................................................... 6 |
b738be600defdc5decba60fb085dc736 | 126 091 | 5.2 Lost speech frames | ............................................................................................................................................. 6 |
b738be600defdc5decba60fb085dc736 | 126 091 | 5.3 First lost SID frame | ............................................................................................................................................ 7 |
b738be600defdc5decba60fb085dc736 | 126 091 | 5.4 Subsequent lost SID frames | ............................................................................................................................... 7 6 Example ECU/BFH Solution 1................................................................................................................7 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.1 State Machine | .................................................................................................................................................... 7 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.2 Assumed Active Speech Frame Error Concealment Unit Actions | ..................................................................... 8 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.2.1 BFI = 0, prevBFI = 0, State = 0 | .................................................................................................................... 8 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.2.2 BFI = 0, prevBFI = 1, State = 0 or 5 | ............................................................................................................ 8 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.2.3 BFI = 1, prevBFI = 0 or 1, State = 1...6 | ....................................................................................................... 9 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.2.3.1 LTP-lag update | ....................................................................................................................................... 9 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.2.3.2 Innovation sequence | ............................................................................................................................. 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.3 Assumed Non-Active Speech Signal Error Concealment Unit Actions | .......................................................... 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.3.1 General | ....................................................................................................................................................... 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.3.2 Detectors | .................................................................................................................................................... 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.3.2.1 Background detector | ............................................................................................................................. 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.3.2.2 Voicing detector | ................................................................................................................................... 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.3.3 Background ECU Actions | .......................................................................................................................... 10 |
b738be600defdc5decba60fb085dc736 | 126 091 | 6.4 Substitution and muting of lost SID frames | ..................................................................................................... 10 7 Example ECU/BFH Solution 2..............................................................................................................11 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.1 State Machine | .................................................................................................................................................. 11 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.2 Substitution and muting of lost speech frames | ................................................................................................ 11 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.2.1 BFI = 0, prevBFI = 0, State = 0 | .................................................................................................................. 11 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.2.2 BFI = 0, prevBFI = 1, State = 0 or 5 | .......................................................................................................... 11 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.2.3 BFI = 1, prevBFI = 0 or 1, State = 1...6 | ..................................................................................................... 12 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.2.3.1 LTP-lag update | ..................................................................................................................................... 12 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.2.4 Innovation sequence | ................................................................................................................................... 12 |
b738be600defdc5decba60fb085dc736 | 126 091 | 7.3 Substitution and muting of lost SID frames | ..................................................................................................... 12 Annex A: Change history......................................................................................................................13 History..............................................................................................................................................................14 (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 4 3G TS 26.091 version 3.1.0 Foreword This Technical Specification has been produced by the 3GPP. The present document defines an error concealment procedure, also termed frame substitution and muting procedure, of the narrowband telephony speech service employing the Adaptive Multi-Rate (AMR) speech coder 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; (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 5 3G TS 26.091 version 3.1.0 1 Scope This specification defines an error concealment procedure, also termed frame substitution and muting procedure, which shall be used by the AMR speech codec receiving end when one or more lost speech or lost Silence Descriptor (SID) frames are received. The requirements of this document are mandatory for implementation in all networks and User Equipment (UE)s capable of supporting the AMR speech codec. It is not mandatory to follow the bit exact implementation outlined in this document and the corresponding C source code. 2 Normative references This document incorporates, by dated and undated reference, provisions from other publications. These normative references are cited in the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this document only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. [1] 3G TS 26.102 "AMR Speech Codec; Interface to RAN". [2] 3G TS 26.090 "AMR Speech Codec; Transcoding functions". [3] 3G TS 26.093 "AMR Speech Codec; Source Controlled Rate operation". [4] 3G TS 26.101 "AMR Speech Codec; Frame structure". 3 Definitions and abbreviations 3.1 Definitions For the purposes of this document, the following definition applies: N-point median operation: Consists of sorting the N elements belonging to the set for which the median operation is to be performed in an ascending order according to their values, and selecting the (int (N/2) + 1) -th largest value of the sorted set as the median value. Further definitions of terms used in this document can be found in the references. (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 6 3G TS 26.091 version 3.1.0 3.2 Abbreviations For the purposes of this document, the following abbreviations apply: AN Access Network BFI Bad Frame Indication from AN BSI_netw Bad Sub-block Indication obtained from AN interface CRC checks prevBFI Bad Frame Indication of previous frame PDFI Potentially Degraded Frame Indication RX Receive SCR Source Controlled Rate (operation) SID Silence Descriptor frame (Background descriptor) CRC Cyclic Redundancy Check ECU Error Concealment Unit BFH Bad Frame Handling medianN N-point median operation 4 General The purpose of the error concealment procedure is to conceal the effect of lost AMR speech frames. The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user and to avoid generating possible annoying sounds as a result from the error concealment procedure. The network shall indicate lost speech or lost SID frames by setting the RX_TYPE values [3] to SPEECH_BAD or SID_BAD. If these flags are set, the speech decoder shall perform parameter substitution to conceal errors. The network should also indicate potentially degraded frames using the flag RX_TYPE value SPEECH_PROBABLY_DEGRADED. This flag may be derived from channel quality indicators. It may be used by the speech decoder selectively depending on the estimated signal type. The example solutions provided in paragraphs 6 and 7 apply only to bad frame handling on a complete speech frame basis. Sub-frame based error concealment may be derived using similar methods. 5 Requirements 5.1 Error detection If the most sensitive bits of the AMR speech data (class A in [4]) are received in error, the network shall indicate RX_TYPE = SPEECH_BAD in which case the BFI flag is set. If a SID frame is received in error, the network shall indicate RX_TYPE = SID_BAD in which case the BFI flag is also set. The RX_TYPE = SPEECH_PROBABLY_DEGRADED flag should be set appropriately using quality information from the channel decoder, in which case the PDFI flas is set. 5.2 Lost speech frames Normal decoding of lost speech frames would result in very unpleasant noise effects. In order to improve the subjective quality, lost speech frames shall be substituted with either a repetition or an extrapolation of the previous good speech frame(s). This substitution is done so that it gradually will decrease the output level, resulting in silence at the output. Subclauses 6, and 7 provide example solutions. (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 7 3G TS 26.091 version 3.1.0 5.3 First lost SID frame A lost SID frame shall be substituted by using the SID information from earlier received valid SID frames and the procedure for valid SID frames be applied as described in [3]. 5.4 Subsequent lost SID frames For many subsequent lost SID frames, a muting technique shall be applied to the comfort noise that will gradually decrease the output level. For subsequent lost SID frames, the muting of the output shall be maintained. Subclauses 6 and 7 provide example solutions. 6 Example ECU/BFH Solution 1 The C code of the following example is embedded in the bit exact software of the codec. In the code the ECU is designed to allow subframe-by-subframe synthesis, thereby reducing the speech synthesis delay to a minimum. 6.1 State Machine This example solution for substitution and muting is based on a state machine with seven states (Figure 1). The system starts in state 0. Each time a bad frame is detected, the state counter is incremented by one and is saturated when it reaches 6. Each time a good speech frame is detected, the state counter is reset to zero, except when we are in state 6, where we set the state counter to 5. The state indicates the quality of the channel: the larger the value of the state counter, the worse the channel quality is. The control flow of the state machine can be described by the following C code (BFI = bad frame indicator, State = state variable): if(BFI != 0 ) State = State + 1; else if(State == 6) State = 5; else State = 0; if(State > 6 ) State = 6; In addition to this state machine, the Bad Frame Flag from the previous frame is checked (prevBFI). The processing depends on the value of the State-variable. In states 0 and 5, the processing depends also on the two flags BFI and prevBFI. (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 8 3G TS 26.091 version 3.1.0 The procedure can be described as follows: STATE = 0 BFI = 0 PrevBFI = 0 or 1 STATE = 1 BFI = 1 PrevBFI = 0 STATE = 2 BFI = 1 PrevBFI = 1 STATE = 3 BFI = 1 PrevBFI = 1 STATE = 5 BFI = 0 or 1 PrevBFI = 1 STATE = 6 BFI = 1 PrevBFI = 0 or 1 Good frame (BFI=0) Bad frame (BFI=1) STATE = 4 BFI = 1 PrevBFI = 1 Figure 1: State machine for controlling the bad frame substitution 6.2 Assumed Active Speech Frame Error Concealment Unit Actions 6.2.1 BFI = 0, prevBFI = 0, State = 0 No error is detected in the received or in the previous received speech frame. The received speech parameters are used in the normal way in the speech synthesis. The current frame of speech parameters is saved. 6.2.2 BFI = 0, prevBFI = 1, State = 0 or 5 No error is detected in the received speech frame, but the previous received speech frame was bad. The LTP gain and fixed codebook gain are limited below the values used for the last received good (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 9 3G TS 26.091 version 3.1.0 subframe: ( ) ( ) ( ) g g g g g g g p p p p p p p = β€ β β > β ο£± ο£² ο£³ , , 1 1 1 (1) where g p = current decoded LTP gain, ( ) g p β1 = LTP gain used for the last good subframe (BFI = 0), and ( ) ( ) ( ) g g g g g g g c c c c c c c = β€ β β > β ο£± ο£² ο£³ , , 1 1 1 (2) where gc = current decoded fixed codebook gain and ( ) gc β1 = fixed codebook gain used for the last good subframe (BFI = 0). The rest of the received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved. 6.2.3 BFI = 1, prevBFI = 0 or 1, State = 1...6 An error is detected in the received speech frame and the substitution and muting procedure is started. The LTP gain and fixed codebook gain are replaced by attenuated values from the previous subframes: g P state g g median g g P state median g g g median g g p p p p p p p p p p = β β β€ β β β β β > β β ο£±   ( ) ( ), ( ) ( ( ),..., ( )) ( ) ( ( ),..., ( )), ( ) ( ( ),..., ( )) 1 1 5 1 5 5 1 5 1 5 1 5 (3) where g p = current decoded LTP gain, g g n p p ( ),..., ( ) β β 1 = LTP gains used for the last n subframes, median5() = 5-point median operation, P(state) = attenuation factor (P(1) = 0.98, P(2) = 0.98, P(3) = 0.8, P(4) = 0.3, P(5) = 0.2, P(6) = 0.2), state = state number, and g C state g g median g g C state median g g g median g g c c c c c c c c c c = β β β€ β β β β β > β β ο£±   ( ) ( ), ( ) ( ( ),..., ( )) ( ) ( ( ),..., ( )), ( ) ( ( ),..., ( )) 1 1 5 1 5 5 1 5 1 5 1 5 (4) where gc = current decoded fixed codebook gain, g g n c c ( ),..., ( ) β β 1 = fixed codebook gains used for the last n subframes, median5() = 5-point median operation, C(state) = attenuation factor (C(1) = 0.98, C(2) = 0.98, C(3) = 0.98, C(4) = 0.98, C(5) = 0.98, C(6) = 0.7), and state = state number. The higher the state value is, the more the gains are attenuated. Also the memory of the predictive fixed codebook gain is updated by using the average value of the past four values in the memory: ( ) ( ) ener ener i i 0 1 4 1 4 = β =β (5) The past LSFs are shifted towards their mean: ( ) ( ) ( ) ( ) lsf q i lsf q i past lsf q i mean lsf i i _ _ _ _ ( ) _ , ... 1 2 1 0 9 = = + β = Ξ± Ξ± (6) where Ξ± = 0.95, lsf_q1 and lsf_q2 are two sets of LSF-vectors for current frame, past_lsf_q is lsf_q2 from the previous frame, and mean_lsf is the average LSF-vector. Note that two sets of LSFs are available only in the 12.2 mode. 6.2.3.1 LTP-lag update The LTP-lag values are replaced by the past value from the 4th subframe of the previous frame (12.2 mode) or slightly modified values based on the last correctly received value (all other modes). (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 10 3G TS 26.091 version 3.1.0 6.2.3.2 Innovation sequence The received fixed codebook innovation pulses from the erroneous frame are used in the state in which they were received when corrupted data are received . In the case when no data were received random fixed codebook indicies should be employed. 6.3 Assumed Non-Active Speech Signal Error Concealment Unit Actions 6.3.1 General The Non-Active Speech ECU is used to reduce the negative impact of amplitude variations and tonal artifacts when using the conventional Active Speech ECU in non-voiced signals such as background noise and unvoiced speech. The background ECU actions are only used for the lower rate Speech Coding modes. The Non-Active Speech ECU actions are done as postprocessing actions of the Active Speech ECU, actions thus ensuring that the Active Speech ECU states are continuously updated. This will guarantee instant and seamless switching to the Active Speech ECU. The detectors and state updates have to be running continuously for all speech coding modes to avoid switching problems. Only the differences to the Active Speech ECU are stated below. 6.3.2 Detectors 6.3.2.1 Background detector An energy level and energy change detector is used to monitor the signal. If the signal is considered to contain background noise and only shows minor energy level changes, a flag is set. The resulting indicator is the inBackgroundNoise flag which indicates the signal state of the previous frame. 6.3.2.2 Voicing detector The received LTP gain is monitored and used to prevent the use of the background ECU actions in possibly voiced segments. A median filtered LTP gain value with a varying filter memory length is thresholded to provide the correct voicing decision. Additionally, a counter voicedHangover is used to monitor the time since a frame was presumedly voiced. 6.3.3 Background ECU Actions The BFI, and DFI indications are used together with the flag inBackgroundNoise and the counter voicedHangover to adjust the LTP part and the innovation part of the excitation. The actions are only taken if the previous frame has been classified as background noise and sufficient time has passed since the last voiced frame was detected. The background ECU actions are: energy control of the excitation signal, relaxed LTP lag control, stronger limitation of the LTP gain, adjusted adaptation of the Gain-Contour-Smoothing algorithm and modified adaptation of the Anti- Sparseness Procedure. 6.4 Substitution and muting of lost SID frames In the speech decoder a single frame classified as SID_BAD shall be substituted by the last valid SID frame information and the procedure for valid SID frames be applied. If the time between SID information updates (updates are specified by SID_UPDATE arrivals and ocassionally by SID_FIRST arrivals see 06.92) is greater than one second this shall lead to attenuation. (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 11 3G TS 26.091 version 3.1.0 7 Example ECU/BFH Solution 2 This is an alternative example solution which is a simplified version of Example ECU/BFH Solution 1. 7.1 State Machine This example solution for substitution and muting is based on a state machine with seven states (Figure 1, same state machine as in Example 1). The system starts in state 0. Each time a bad frame is detected, the state counter is incremented by one and is saturated when it reaches 6. Each time a good speech frame is detected, the state counter is reset to zero, except when we are in state 6, where we set the state counter to 5. The state indicates the quality of the channel: the larger the state counter, the worse the channel quality is. The control flow of the state machine can be described by the following C code (BFI = bad frame indicator, State = state variable): if(BFI != 0 ) State = State + 1; else if(State == 6) State = 5; else State = 0; if(State > 6 ) State = 6; In addition to this state machine, the Bad Frame Flag from the previous frame is checked (prevBFI). The processing depends on the value of the State-variable. In states 0 and 5, the processing depends also on the two flags BFI and prevBFI. 7.2 Substitution and muting of lost speech frames 7.2.1 BFI = 0, prevBFI = 0, State = 0 No error is detected in the received or in the previous received speech frame. The received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved. 7.2.2 BFI = 0, prevBFI = 1, State = 0 or 5 No error is detected in the received speech frame but the previous received speech frame was bad. The LTP gain and fixed codebook gain are limited below the values used for the last received good subframe: ( ) ( ) ( ) g g g g g g g p p p p p p p = β€ β β > β ο£± ο£² ο£³ , , 1 1 1 (7) where g p = current decoded LTP gain, ( ) g p β1 = LTP gain used for the last good subframe (BFI = 0), and ( ) ( ) ( ) g g g g g g g c c c c c c c = β€ β β > β ο£± ο£² ο£³ , , 1 1 1 (8) where gc = current decoded fixed codebook-gain and ( ) gc β1 = fixed codebook gain used for the last good subframe (BFI = 0). The rest of the received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved. (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 12 3G TS 26.091 version 3.1.0 7.2.3 BFI = 1, prevBFI = 0 or 1, State = 1...6 An error is detected in the received speech frame and the substitution and muting procedure is started. The LTP gain and fixed codebook gain are replaced by attenuated values from the previous subframes: g P state g g median g g P state median g g g median g g p p p p p p p p p p = β β β€ β β β β β > β β ο£±   ( ) ( ), ( ) ( ( ),..., ( )) ( ) ( ( ),..., ( )), ( ) ( ( ),..., ( )) 1 1 5 1 5 5 1 5 1 5 1 5 (9) where g p = current decoded LTP gain, g g n p p ( ),..., ( ) β β 1 = LTP gains used for the last n subframes, median5() = 5-point median operation, P(state) = attenuation factor (P(1) = 0.98, P(2) = 0.98, P(3) = 0.8, P(4) = 0.3, P(5) = 0.2, P(6) = 0.2), state = state number, and g C state g g median g g C state median g g g median g g c c c c c c c c c c = β β β€ β β β β β > β β ο£±   ( ) ( ), ( ) ( ( ),..., ( )) ( ) ( ( ),..., ( )), ( ) ( ( ),..., ( )) 1 1 5 1 5 5 1 5 1 5 1 5 (10) where gc = current decoded fixed codebook gain, g g n c c ( ),..., ( ) β β 1 = fixed codebook gains used for the last n subframes, median5() = 5-point median operation, C(state) = attenuation factor (C(1) = 0.98, C(2) = 0.98, C(3) = 0.98, C(4) = 0.98, C(5) = 0.98, C(6) = 0.7), and state = state number. The higher the state value is, the more the gains are attenuated. Also the memory of the predictive fixed codebook gain is updated by using the average value of the past four values in the memory: ( ) ( ) ener ener i i 0 1 4 1 4 = β =β (11) The past LSFs are used by shifting their values towards their mean: ( ) ( ) ( ) ( ) lsf q i lsf q i past lsf q i mean lsf i i _ _ _ _ ( ) _ , ... 1 2 1 0 9 = = + β = Ξ± Ξ± (12) where Ξ± = 0.95, lsf_q1 and lsf_q2 are two sets of LSF-vectors for current frame, past_lsf_q is lsf_q2 from the previous frame, and mean_lsf is the average LSF-vector. Note that two sets of LSFs are available only in the 12.2 mode. 7.2.3.1 LTP-lag update The LTP-lag values are replaced by the past value from the 4th subframe of the previous frame (12.2 mode) or slightly modified values based on the last correctly received value (all other modes). 7.2.4 Innovation sequence The received fixed codebook innovation pulses from the erroneous frame are used in the state in which they were received when corrupted data are received. In the case when no data were received random fixed codebook indicies should be employed. In the speech decoder a single frame classified as SID_BAD shall be substituted by the last valid SID frame information and the procedure for valid SID frames be applied. If the time between SID information updates (updates are specified by SID_UPDATE arrivals and occasionally by SID_FIRST arrivals) is greater than one second this shall lead to attenuation. (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 3GPP 3G TS 26.091 V3.1.0 (1999-12) 13 3G TS 26.091 version 3.1.0 Annex A: Change history Tdoc SPEC CR RE VER SUBJECT CAT NEW SP-99570 26.091 A001 3.0.1 Use of random excitation when RX_NODATA and not in DTX F 3.1.0 (3G TS 26.091 version 3.1.0 Release 1999) ETSI TS 126 091 V3.1.0 (2000-01) ETSI 14 ETSI ETSI TS 126 091 V3.1.0 (2000-01) (3G TS 26.091 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 1 Scope | ....................................................................................................................................................... 6 |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 2 Normative references | ............................................................................................................................... 6 |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 3 Definitions, symbols and abbreviations | ................................................................................................... 7 |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 3.1 Definitions | ..........................................................................................................................................................7 |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 3.2 Symbols | ..............................................................................................................................................................8 |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 3.3 Abbreviations | ...................................................................................................................................................14 |
027a41cea2de098957b2616ae8f22de5 | 126 090 | 4 Outline description | ................................................................................................................................ 14 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.