hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7 Description of CAMEL BCSMs | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.1 General Handling | The BCSM is used to describe the actions in an MSC/GMSC during originating, forwarded or terminating calls. The BCSM identifies the points in basic call processing when Operator Specific Service (OSS) logic instances (accessed through the gsmSCF) are permitted to interact with basic call control capabilities. Figure 2 ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2 Originating Basic Call State Model (O-BCSM) | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2.1 Description of O-BCSM | The O-BCSM is used to describe the actions in an MSC during originating (MSC) or forwarded (MSC or GMSC) calls. When encountering a DP the O-BCSM processing is suspended at the DP and the MSC/GMSC indicates this to the gsmSSF which determines what action, if any, shall be taken in case the DP is armed. ETSI TS 101 441 ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2.1.1 Description of the call model (PICs) | This subclause describes the call model for originating and forwarded calls. For each PIC a description can be found of the entry events, functions and exit events. ETSI TS 101 441 V6.2.0 (1998-11) 21 GSM 03.78 version 6.2.0 Release 1997 It should be noted that although the names used for PICs match those used in ITU-T... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2.1.1.1 O_Null & Authorise_Origination_Attempt_Collect_Info | Entry events: - Disconnection and clearing of a previous call (DP9 - O_Disconnect) or default handling of exceptions by gsmSSF/(G)MSC completed. - Abandon event is reported from Analyse, Routing and Alerting PIC. - Exception event is reported. Functions: - Interface is idled. - Originating call: SETUP message containin... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2.1.1.2 Analyse, Routing & Alerting | Entry events: - Originating CSI is analysed. (DP2 - Collected Info). - Busy event, Route Select Failure event, Not Reachable event or No Answer event is reported from Analyse Routing and Alerting PIC. - Disconnect event is reported from O_Active PIC. Functions: - Information being analysed and/or translated according t... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2.1.1.3 O_Active | Entry events: - Indication from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP7 - O_Answer) Functions: - Connection established between originating party and terminating party. Call supervision is provided. - Call release is awaited. Exit events: - A disconnection indicat... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.2.1.1.4 O_Exception | Entry events: - An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for a PIC can not be met. Functions: - Default handling of the exception condition is being provided. This includes general actions ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3 Terminating Basic Call State Model (T-BCSM) | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3.1 Description of T-BCSM | The T-BCSM is used to describe the actions in a GMSC during terminating calls. When encountering a DP the T-BCSM processing is suspended at the DP and the GMSC indicates this to the gsmSSF which determines what action, if any, shall be taken in case the DP is armed. ETSI TS 101 441 V6.2.0 (1998-11) 23 GSM 03.78 version... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3.1.1 Description of the call model (PICs) | This subclause describes the call model for terminating calls in the GMSC. For each PIC a description can be found of the entry events, functions, information available and exit events. ETSI TS 101 441 V6.2.0 (1998-11) 24 GSM 03.78 version 6.2.0 Release 1997 It should be noted that although the names used for PICs matc... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3.1.1.1 T_Null | Entry events: - Disconnection and clearing of a previous call (DP 17) or default handling of exceptions by gsmSSF/GMSC completed. - Abandon event is reported from Terminating Call Handling PIC ; - Exception event is reported. Functions: - Interface is idled. - ISUP_IAM is received, the appropriate information is analys... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3.1.1.2 Terminating Call Handling | Entry events: - Response is received from HLR and terminating CSI (if available) is analysed. (DP 12 Terminating_Attempt_Authorised), - Busy event, Not Reachable event or No Answer event is reported from Terminating Call Handling PIC, - Disconnect event is reported from T_Active PIC. - The terminating party is not reac... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3.1.1.3 T_Active | Entry events: - Indication that the call is accepted and answered by the terminating party. (DP15 - T_Answer) Functions: - Connection established between originating party and terminating party. Call supervision is being provided. - Call release is awaited. Exit events: - A disconnection indication is received from the... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.3.1.1.4 T_Exception | Entry events: - An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for PIC cannot be met. Functions: - Default handling of the exception condition is being provided. This includes general actions nec... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.4 BCSM Modelling of Call Scenarios | This subclause describes how the BCSMs defined above are used to model GSM call scenarios. For each scenario the used and unused BCSMs involved in the call are shown. In some cases these models may have an allocation to physical nodes different from that shown. However, the physical separation of the logic functions sh... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.4.1 Mobile Originated Call | The O-BCSM for the call from A to B (labelled "O(A-B)") is invoked if the A-party has an active O-CSI. A control relationship with gsmSCF (1) will be created. MSC gsmSSF/CCF T(A-B) B-Party A-Party O(A-B) gsmSCF (1) CAMEL relationship Figure 5: BCSM Scenario for Mobile Originated Call |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.4.2 Mobile Terminated Call | The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. A control relationship with gsmSCF (1) will be created. GMSC gsmSSF/CCF T(A-B) B-Party A-Party O(A-B) gsmSCF (1) CAMEL relationship MSC gsmSSF/CCF Figure 6: BCSM Scenario for Mobile Terminated Calls |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.4.3 Call Forwarding at the GMSC | The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. A control relationship with gsmSCF (1) will be created. ETSI TS 101 441 V6.2.0 (1998-11) 27 GSM 03.78 version 6.2.0 Release 1997 A new call leg to a "C" party is created if: - a GSM call forwarding supplementary servi... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 7.4.4 Call Forwarding at the MSC | The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. A control relationship with gsmSCF (1) will be created. Following processing at the GMSC the call will be extended to the MSC serving the B-party. This MSC may be physically integrated with the GMSC, but it is shown a... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8 Procedures for CAMEL | The SDLs in this specification illustrate how CAMEL modifies the normal call handling. They do not attempt to show all the details of call handling in nodes that support CAMEL. Relevant parts of GSM 03.18 [3] apply in addition to these SDLs. For example, some inputs leading to unsuccessful call attempts are not shown o... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.1 Overall SDL architecture | The following diagram shows the overall architecture for the SDL diagrams. ETSI TS 101 441 V6.2.0 (1998-11) 29 GSM 03.78 version 6.2.0 Release 1997 A interface ISUP interface Internal interface Internal interface CAP interface gsmSRF CAP relay interface OCH_MSC gsmSSF Mobile Station Destination exchange gsmSCF Figure 9... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2 Handling of mobile originated calls | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.1 Handling of mobile originated calls in the originating MSC | The functional behaviour of the originating VMSC is specified in GSM 03.18 [3]. The procedures specific to CAMEL are specified in this subclause : - Procedure CAMEL_OCH_MSC_INIT, - Procedure CAMEL_OCH_MSC_ANSWER, - Procedure CAMEL_OCH_MSC1, - Procedure CAMEL_OCH_MSC2, - Procedure CAMEL_OCH_MSC_DISC1, - Procedure CAMEL_... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.1.1 Actions of the MSC on receipt of Int_Error | The MSC checks the default Call Handling parameter in O-CSI. If the default call handling is release call, a Release_Transaction is sent to the MS and an Abort to the VLR. The MSC then releases all call resources and the process CAMEL_OCH_MSC returns to idle. If the default call handling is continue call, the MSC conti... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.1.2 Actions of the MSC on receipt of Int_Continue | The MSC continues processing without any modification of call parameters. It sends Send_Info_For_Ougoing_Call_2 to the VLR and waits in state Wait_For_MO_Call_Result_2. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.1.3 Actions of the MSC on receipt of Int_Connect | The MSC continues processing with modified call parameters. The MSC shall transparently modify the call parameters with the received information. The MSC then sends a PROGRESS message to the MS. Call parameters which are not included in the Int_Connect message are unchanged. Signalling limitations or regulatory require... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.1.4 Actions of the MSC on receipt of Int_Release_Call | A Release_Transaction is sent to the MS, an abort to the VLR and a Release is sent to the destination exchange. The release cause received in the Int_Release_Call is used. The MSC then releases all call resources and the process CAMEL_OCH_MSC returns to idle. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.1.5 Action of the MSC in procedure CAMEL_OCH_ETC | In procedure CAMEL_OCH_ETC (sheet 2) the MSC will remain in the Wait_For_Assisting_Answer state until it receives an ISUP Answer Message (ANM) or timeout occurs. This is to ensure that a call record is always generated for every successful establishment of a temporary connection to a gsmSRF, especially in the case wher... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.2.2 Handling of mobile originating calls in the originating VLR | The functional behaviour of the originating VLR is specified in GSM 03.18 [3]. The procedure specific to CAMEL are specified in this subclause : - Procedure CAMEL_OCH_VLR - Process CAMEL_Reconnected_Call_VLR ETSI TS 101 441 V6.2.0 (1998-11) 57 GSM 03.78 version 6.2.0 Release 1997 Procedure in the VLR to handle an outgo... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3 Retrieval of routeing information | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.1 Retrieval of routeing information in the GMSC | The functional behaviour of the GMSC is specified in GSM 03.18 [3]. The procedures specific to CAMEL are specified in this subclause : - Procedure CAMEL_Set_ORA_Parameters ETSI TS 101 441 V6.2.0 (1998-11) 59 GSM 03.78 version 6.2.0 Release 1997 - Procedure CAMEL_MT_GMSC_INIT - Procedure CAMEL_MT_GMSC_ANSWER - Procedure... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.1.1 Action of the GMSC on receipt of Int_Release_Call | An ISUP_Release is sent to the originating exchange and resources are released. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.1.2 Action of the GMSC on receipt of Int_Error | The GMSC checks in T-CSI the default Call Handling parameter. If the default call handling is release call, an ISUP_Release is sent to the originating exchange. The MSC then releases all call resources and the procedure CAMEL_MT_GMSC_INIT returns result=fail. If the default call handling is continue call, the MSC conti... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.1.3 Action of the GMSC on receipt of Int_Continue | If a FTN has been stored the information received from HLR is used to overwrite corresponding call parameters. Note that the MSISDN is replaced by the FTN as the Called party number. The redirection counter is incremented. If no FTN has been stored, a Send Routeing Info message including a T-CSI suppression parameter i... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.1.4 Action of the GMSC on receipt of Int_Connect | If the Destination Number received from the gsmSCF (via the gsmSSF) is the same as the ISUP Called party number, i.e. the MSISDN, the following parameters, if received, are used to overwrite the corresponding ISUP parameters (for mapping see GSM 09.78 [5]): Calling Partys Category and Generic Number. If received, the A... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.1.9 Action of the GMSC in procedure CAMEL_MT_ETC | In procedure CAMEL_MT_ETC (sheet 2) the GMSC will remain in the Wait_For_Assiting_Answer state until it receives an ISUP Answer Message (ANM) or timeout occurs. This is to ensure that a call record is always generated for every successful establishment of a temporary connection to a gsmSRF, especially in the case where... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.2 Retrieval of routeing information in the HLR | The functional behaviour of the HLR is specified in GSM 03.18 [3]. The procedures specific to CAMEL are specified in this subclause : - CAMEL_HLR_INIT, - CAMEL_CSI_Check_HLR, - CAMEL_O_CSI_CHECK_HLR, - CAMEL_T_CSI_CHECK_HLR, The procedure Provide_Subscriber_Info_HLR is specified in subclause 0. ETSI TS 101 441 V6.2.0 (... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.3.3 Handling of provide roaming number request in the VLR | The functional behaviour of the VLR is specified in GSM 03.18 [3]. The procedure specific to CAMEL is specified in this subclause : - CAMEL_SET_SOA. ETSI TS 101 441 V6.2.0 (1998-11) 92 GSM 03.78 version 6.2.0 Release 1997 Pr oc edure in the VLR to s et the s uppression of an nounc ement indic ator as required for this ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.4 Handling of mobile terminating calls | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.4.1 Handling of mobile terminating calls in the terminating VMSC | The functional behaviour of the terminating VMSC is specified in GSM 03.18 [3]. The only behaviour specific to CAMEL is: ETSI TS 101 441 V6.2.0 (1998-11) 93 GSM 03.78 version 6.2.0 Release 1997 - the inclusion of the O-CSI parameter in the Perform Call Forwarding message sent to the process MT_CF_MSC if it was received... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.4.2 Handling of mobile terminating calls in the VLR | The functional behaviour of the terminating VLR is specified in GSM 03.18 [3]. The only behaviour specific to CAMEL is: - the inclusion of the O-CSI parameter in the Send Info For Incoming Call ack if the call is to be forwarded and O- CSI is included in the subscriber data for that subscriber in the VLR; - the inclusi... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.5 Handling of forwarded calls | The handling of forwarded calls in the GMSC or the terminating VMSC is specified in GSM 03.18 [3]. The procedures specific to CAMEL are specified in this subclause. - Procedure CAMEL_CF_MSC_INIT, - Procedure CAMEL_CF_MSC_ANSWER - Procedure CAMEL_CF_ETC, - Procedure CAMEL_CF_CTR. A mobile terminated call can be forwarde... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.5.1 Procedure CAMEL_CF_MSC_INIT : handling of Int_Connect | The received parameters are used to overwrite the corresponding ISUP parameters (for mapping see GSM 09.78 [5]. Call parameters which are not included in the Int_Connect message are unchanged. An a network operator option, loop prevention mechanisms may cause the redirection information to be ignored or modified (e.g.,... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.5.2 Action of the GMSC in procedure CAMEL_CF_ETC | In procedure CAMEL_CF_ETC (sheet 2) the GMSC or terminating VMSC will remain in the Wait_For_Assiting_Answer state until it receives an ISUP Answer Message (ANM) or timeout occurs. This is to ensure that a call record is always generated for every successful establishment of a temporary connection to a gsmSRF, especial... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.6 Handling of mobile calls in the gsmSSF | Handling of mobile calls in the gsmSSF may involve the following process and procedures : - gsmSSF, - Check_Criteria. - Handle_AC, - Handle_ACR, - Handle_CIR, - Handle_SCI. The detailed error handling for the process gsmSSF and the associated procedures is specified in GSM 09.78 ([5]). |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.6.1 Information flow for call duration control | The following diagram shows the handling of the different timers that are used in the process gsmSSF and in the procedures Handle_AC, Handle_ACR, Handle_CIR. Timers Tssf, Tcp, Tsw, Tw and DELTA are defined in the process gsmSSF. AC(Tcp1) ANSWER ACR AC(Tcp2) RELEASE ACR RRBCSM CONNECT SET UP ALERT ANSWER AC(Tcp3) RELEAS... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.6.2 Behaviour of the gsmSSF in the process gsmSSF | The following paragraphs give details on the behaviour of the gsmSSF in the procedure gsmSSF. 8.6.2.1 Actions of the gsmSSF on receipt of CAP_Request_Report_BCSM_Event (at the state Waiting_For_Instructions) The gsmSSF arms the requested EDP, if the arming rules are fulfilled and returns to state Waiting_For_Instructio... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.6.3 Procedure Handle_SCI | 1) Precondition: before an answer event is detected and no Tsw running: if 1 set of e-parameters received --> send to the MSC if 2 sets e-parameters received --> error if 1 set of e-parameters and Tariff Switch received --> error if 2 sets of e-parameters and Tariff Switch received --> send 1st/start Tsw/store 2nd 2) P... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.7 Assisting case | Assisting case involves the following processes : - CAMEL_Assisting_MSC, - Assisting_gsmSSF. The detailed error handling for these 2 processes is specified in GSM 09.78 ([5]). ETSI TS 101 441 V6.2.0 (1998-11) 133 GSM 03.78 version 6.2.0 Release 1997 Process in the MSC to handle an assist request Process CAMEL_Assisting... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8 Procedure CAMEL_Provide_Subscriber_Info | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.1 MS reachable | A Provide_Subscriber_Info Request is sent to VLR and the HLR waits in state Wait_For_Information. If the VLR returns a Provide_Subscriber_Info ack, the HLR uses the returned information to set the Subscriber Info to be returned to the gsmSCF. As a network option, the HLR may use the returned Cell Id or Location Area to... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.2 MS not reachable | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.2.1 Location Information requested | If VLR number is available in the HLR, then the Location Information is set to this parameter only. If location information is not available in the HLR, no location information is set. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.2.2 Subscriber State requested | The Subscriber State is set to "Network determined not reachable". |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.3 Actions at state Wait_For_Information | The following actions are possible in state Wait_For_Information depending on the result of the Provide_Subscriber_Info Request sent to VLR. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.3.1 Provide_Subscriber_Info ack | The Location Information or/and the Subscriber State are set to the received information. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.8.3.2 Provide_Subscriber_Info Negative Response | If location information was requested the VLR number is provided as location information. If the subscriber state was requested the subscriber state is set to “not provided from VLR”. ETSI TS 101 441 V6.2.0 (1998-11) 143 GSM 03.78 version 6.2.0 Release 1997 P r oc e d u re in t he H L R f o r R e tri e va l o f L o ca ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.9 Any Time Interrogation | Handling of Any Time Interrogation involves the following process : - CAMEL_ATI_HLR. If an OSS needs the Subscriber State and/or the Location Information, the gsmSCF initiates a transaction to the HLR by sending a Any_Time_Interrogation Request. Support for this procedure is a network operator option. ETSI TS 101 441 V... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.10 Handling of USSD to/from gsmSCF | The functional model of USSD in an HLR that supports CAMEL is shown in figure 52. The phase 2 USSD handler is defined in GSM 03.90 ([8)]. Phase 1 USSD messages may be relayed from the HLR to the gsmSCF. CAMEL introduces a "CAMEL USSD application" which is invoked by the USSD handler. The CAMEL USSD application behaviou... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.10.1 MS Initiated USSD | For the behaviour of the USSD handler in HLR when receiving a MS initiated USSD see GSM 03.90. When the USSD handler has determined that the service code present in the received USSD does not indicate that an USSD application in the HLR shall be invoked it shall route the USSD to the USSD application specific for CAMEL... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.10.2 gsmSCF Initiated USSD | The HLR may at any time receive a USSD operation from the gsmSCF. If the subscriber can be contacted, the HLR shall set up a transaction to the VLR and forward the operation unchanged. Any further information exchange between the gsmSCF and MSC shall be transparent to the VLR and the HLR. When one transaction is releas... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.10.3 Content of the USSD General CAMEL Service Information (UG-CSI) | The service information specified in this subclause is for information only. This subclause defines the contents of the USSD General CAMEL Service Information (UG-CSI). The allocation of the UG-CSI is independent from a particular subscriber. The UG-CSI consists of a list of pairs of the following two parameters. ETSI ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.10.3.1 Service Code | Service code for a specific application in a gsmSCF which interacts with the user by USSD. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.10.3.2 gsmSCF address | Address to be used to access the gsmSCF for a particular a particular service code. The address shall be an E.164 number to be used for routeing. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.11 Handling of Supplementary Service Invocation Notification | At the invocation of any of the services ECT, CD and MPTY the MSC/VLR checks whether the criteria for sending a notification is fulfilled, i.e. whether the subscriber is provisioned with the SS-CSI and the particular invoked supplementary service is marked in the SS-CSI. If this is the case a notification is sent to th... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.13 Processing of Non-Call Related Events | CAMEL does not modify any of the standardized procedures for non-call related events including: - call independent supplementary service procedures; - transfer of SMS messages; - mobility management procedures. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 8.14 Cross phase compatibility | To avoid a case by case fallback between the gsmSSF and the gsmSCF, the gsmSSF shall use the CAP phase corresponding to the CAMEL phase negotiated on the HLR-VLR interface when it opens a dialogue with the gsmSCF. The HLR-VLR negotiation of CAMEL phase is per subscriber. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9 Description of information flows | This clause contains the detailed description of the information flows used by CAMEL. Each Information Element, IE is marked as Mandatory, Conditional, Optional or Not applicable for each different traffic case, Mobile Originating call (MO), Mobile Forwarded call (MF) and Mobile Terminating call (MT). This categorisati... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1 gsmSSF to gsmSCF information flows | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.1 Activity Test ack | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.1.1 Description | This IF is the response to the Activity Test. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.1.2 Information Elements | This IF contains no information elements. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.2 Apply Charging Report | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.2.1 Description | This IF is used by the gsmSSF to report to the gsmSCF the information requested in the Apply Charging IF. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.2.2 Information Elements | Information element name MO MF MT Description Call Result M M M This IE contains the charging information to be provided by the gsmSSF. M Mandatory (The IE shall always be sent) Call Result contains the following information: Information element name MO MF MT Description Time Duration Charging Result M M M This IE is a... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.3 Call Information Report | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.3.1 Description | This IF is used to send specific call information for a single call to the gsmSCF as requested from the gsmSCF in a previous Call Information Request. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.3.2 Information Elements | Information element name MO MF MT Description Requested Information List M M M This IE specifies a list of Requested information Values which are requested. Leg ID M M M This IE indicates the party in the call for which information shall be collected. When absent, it indicates the ‘outgoing’ leg created with Connect or... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.4 Event Report BCSM | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.4.1 Description | This IF is used to notify the gsmSCF of a call-related event (i.e., BCSM events as answer and disconnect) previously requested by the gsmSCF in a Request Report BCSM Event IF. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.4.2 Information Elements | The following information elements are required: Information element name MO MF MT Description Event type BCSM M M M This IE specifies the type of event that is reported. Event Specific Information BCSM C C C This IE indicates the call related information specific to the event. Leg ID M M M This IE indicates the party ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.5 Initial DP | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.5.1 Description | This IF is generated by the gsmSSF when a trigger is detected at a DP in the BCSM, to request instructions from the gsmSCF. ETSI TS 101 441 V6.2.0 (1998-11) 150 GSM 03.78 version 6.2.0 Release 1997 |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.1.5.2 Information Elements | The following information elements are required: Information element name MO MF MT Description Additional Calling Party Number - C C The calling party number provided by the access signalling system of the calling user. Bearer Capability M C C This IE indicates the type of the bearer capability connection to the user. ... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2 gsmSCF to gsmSSF information flows | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.1 Activity Test | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.1.1 Description | This IF is used to check for the continued existence of a relationship between the gsmSCF and gsmSSF. If the relationship is still in existence, then the gsmSSF will respond. If no reply is received, then the gsmSCF will assume that the gsmSSF has failed in some way and will take the appropriate action. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.1.2 Information Elements | This IF contains no information elements. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.2 Apply Charging | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.2.1 Description | This IF is used for interacting from the gsmSCF with the gsmSSF charging mechanisms to control the call duration. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.2.2 Information Elements | Information element name MO MF MT Description ACh Billing Charging Characteristics M M M This IE specifies the charging related information to be provided by the gsmSSF and the conditions on which this information has to be provided back to the gsmSCF. Send Calculation To SCP Indication M M M This IE indicates that App... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.3 Call Information Request | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.3.1 Description | This IF is used to request the gsmSSF to record specific information about a single call and report it to the gsmSCF (with a CallInformationReport) |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.3.2 Information Elements | Information element name MO MF MT Description Requested Information Type List M M M This IE specifies a list of specific items of information which are requested. Leg ID M M M This IE indicates the party in the call for which information shall be collected. When absent, it indicates the ‘outgoing’ leg created with Conn... |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.4 Cancel | |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.4.1 Description | This IF is used by the gsmSCF to request the gsmSSF to cancel all EDP and report. |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.4.2 Information Elements | The following information elements are used: Information element name MO MF MT Description all request MO MO MO This IE indicates that all active requests for EventReportBCSM, ApplyCharging and CallInformationReport shall be cancelled. M Mandatory (The IE shall always be sent) |
dbc272db428ef1fb005c9df8379962ae | 101 441 | 9.2.5 Connect |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.