Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 22.078  Word version:  18.0.1

Top   Top   Up   Prev   Next
0…   4…   5…   6…   7…   9…   10…   12…   16…   19…   24…   B… 
5 Procedures for Mobile Originated Calls and Forwarded Calls  5.1 Initial service events  5.2 Criteria for contact with the CSE  5.3 Call set-up request procedure  5.4 Calling party abandon  5.5 Unsuccessful call establishment  5.6 Called party connection procedure  5.7 Mid call procedure  5.8 Call disconnection procedure  5.9 CSE initiated call release procedure  5.11 Called party alert reporting procedure  5.12 Change of position procedure  5.13 Change of basic service 
...

 

5  Procedures for Mobile Originated Calls and Forwarded Calls  p. 17

5.1  Initial service events  p. 17

It shall be possible to specify which of the following initial service events shall initiate contact with the CSE:
  • Collection of dialled digits;
  • Analysis of dialled digits;
  • Detection of unsuccessful call establishment.
    Unsuccessful call establishment may be caused by:
    • Route select failure.
The definition of which of the above initial service events shall initiate contact with the CSE is part of the subscriber's CAMEL subscription information. Analysis of dialled digits can open a new dialogue regardless of whether a relationship exists. Upon detection of unsuccessful call establishment no new relationship is opened if there is already a dialogue open due to the same CSI.
Up

5.2  Criteria for contact with the CSE  p. 17

It shall be possible for the HPLMN to specify criteria which must be satisfied before the CSE is contacted.
The following criteria may be defined:

5.2.1  CSI criteria applicable at call setup  p. 17

5.2.1.1  CSI criteria applicable at call setup when dialled digits have been collected  p. 17

CSI criteria may be defined for a subscriber for the case where collection of dialled digits has been performed.
  • Criteria on the dialled number; these consist of:
    • The contents of the dialled number (a list of up to 10 dialled number strings may be defined in the criteria. Each dialled number string may be of any type of number (TON) format supported by the access protocol).
    • The length of the dialled number (a list of up to three lengths may be defined.).
  • The criteria on the dialled number may be collectively defined to be either "enabling" triggering criteria or "inhibiting" triggering criteria (see below). The HPLMN may also choose not to define any criteria on the dialled number.
  • A criterion on the basic service: this consists of a list of up to 5 basic service codes for individual basic services or basic service groups. The HPLMN may also choose not to define any criterion on the basic service.
  • A criterion on the type of call: this consists of defining whether the call must be a forwarded call.
    A call is treated as forwarded in this respect when either a forwarding supplementary service applies or when the call is forwarded as a result of a terminating CAMEL based service. The HPLMN may also choose not to define any criterion on the type of call.
If the criteria on the dialled number are "enabling" then the dialled number criteria are satisfied if:
  • The dialled number matches a dialled number string defined in the criteria; or
  • The length of the dialled number matches a dialled number length defined in the criteria.
If the criteria on the dialled number are "inhibiting" then the dialled number criteria are satisfied if:
  • The dialled number does not match any of the dialled number strings defined in the criteria; and
  • The length of the dialled number is not the same as any dialled number length defined in the criteria.
In these tests the dialled number matches one of the dialled number strings if:
  • The two numbers are of the same Type Of Number (TON); and
  • The dialled number is at least as long as the dialled number string in the criteria; and
  • All the digits in the dialled number string in the criteria match the leading digits of the dialled number.
If no criterion on the dialled number is specified then the dialled number criteria are satisfied.
The criterion on the basic service is satisfied if the basic service used for the call corresponds to any basic service code or basic service group defined in the criterion or if no basic service criterion is specified.
The criterion on the type of call is satisfied if the type of the call is the same as the type defined in the criterion or if no call type criterion is specified.
The criteria on the call setup event procedure are satisfied if:
  • The criteria on the dialled number are satisfied; and
  • The criterion on the basic service is satisfied; and
  • The criterion on the type of call is satisfied.
Up

5.2.1.2  CSI criterion applicable at call setup for subscribed dialled services  p. 18

A CSI criterion on the contents of the called number shall be defined for subscribed dialled services. A list of up to 10 called number strings may be defined in the criterion. Each entry in the called number list has associated with it a CSE identity and a service key which defines the service to be triggered if the criterion is satisfied.
If any other CAMEL dialogue has changed the called number, then the modified called number shall be used for the conditional triggering check.
The called number criterion is satisfied if the called number matches a called number string defined in the criterion.
In this test the called number matches one of the called number strings if:
  • The two numbers are of the same Type Of Number (TON); and
  • The called number is at least as long as the called number string in the criteria; and
  • All the digits in the called number string in the criteria match the leading digits of the called number.
Up

5.2.1.3  CSI criterion applicable on detection of unsuccessful call establishment  p. 18

A criterion on the release cause may be defined. This consists of a list of up to 5 cause values. The criterion on the release cause is satisfied if the received call release cause corresponds to any cause value defined in the list or if no criterion is defined.

5.3  Call set-up request procedure  p. 19

5.3.1  Procedure when dialled digits have been collected  p. 19

The purpose of this procedure is to detect a call set-up request at the point where digits have been collected but not analysed, and to allow the CSE to modify the handling of the call set-up request.
If (according to the CSI):
  • The subscriber is provisioned with a CAMEL based originating service; and
  • The call set-up request occurs; and
  • The criteria are satisfied.
Then the VPLMN/IPLMN shall suspend call processing, make contact with the CSE and await further instructions. When the VPLMN/IPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN/IPLMN to act as described below.
  • Perform charging activities;
  • Activate subsequent control service events for the call. The CSE shall have the possibility to send the following information:
    • The subsequent service event which shall be detected and reported:
      • Called party alert;
      • Called party connection;
      • Call disconnection;
      • Calling party abandon;
      • Unsuccessful call establishment. In the case of no answer the CSE may provide a no answer timer;
      • Mid call event (DTMF). The CSE shall specify the digit string(s) for which the instruction is valid.. The arming and detection of the mid call event shall be limited to the VPLMN;
      • Change of Position. The CSE may specify notification criteria. The arming and detection of the Change of Position event shall be limited to the VPLMN;
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported (calling or called party);
    • The type of monitoring (control or notification).
  • Order in-band user interaction;
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Bar the call (i.e. release the call prior to connection);
  • Continue the call processing;
  • Continue the call processing with modified information;
  • Continue the handling of the calling party without routeing the call to the destination.
Up

5.3.2  Procedure for subscribed dialled services  p. 20

The purpose of this procedure is to detect a call set-up request at the point where the called party number has been compared with the dialled services information, and allow the CSE to modify the handling of the call set-up request. Triggering of this procedure shall happen immediately after the procedure when dialled digits have been collected.

5.3.2.1  Initiation of contact with the CSE  p. 20

If (according to the CSI):
  • The subscriber is provisioned with a CAMEL based originating service; and
  • The call set-up request occurs; and
  • The criteria are satisfied.
Then the VPLMN/IPLMN shall suspend call processing, make contact with the CSE and await further instructions.
Contact with the CSE shall (if necessary) be made in this manner before network dialled services are invoked.

5.3.2.2  Further processing of the call  p. 20

If a relationship exists with a CSE, then when the VPLMN/IPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN/IPLMN to act as described below:
  • Perform charging activities The CSE is only allowed to send e-values (refer to sect. 15.1, 'CSE controlled e-values') and include free format data in Call Data Records (refer to sect. 15.2, 'Inclusion in charging records of information received from the CSE');
  • Order in-band user interaction. (Interaction between the service triggered from previous triggering may be needed to avoid duplicated guidance etc.).
Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Release the call;
  • Continue the call processing;
  • Continue the call processing with modified information;
If no relationship exists with a CSE for the call, then when the VPLMN/IPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN/IPLMN to act as described below:
  • Perform charging activities;
  • Activate subsequent control service events for the call. The CSE shall have the possibility to send the following information:
    • The subsequent service event which shall be detected and reported:
      • Called party alert;
      • Called party connection;
      • Call disconnection;
      • Calling party abandon;
      • Unsuccessful call establishment. In the case of no answer the CSE may provide a no answer timer;
      • Mid call event (DTMF). The CSE shall specify the digit string(s) for which the instruction is valid. The arming and detection of the mid call event shall be limited to the VPLMN;
      • Change of Position. The CSE may specify notification criteria. The arming and detection of the Change of Position event shall be limited to the VPLMN;
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported (calling or called party);
    • The type of monitoring (control or notification).
  • Order in-band user interaction.
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Allow the call processing to continue unchanged;
  • Allow the call processing with modified information;
  • Continue the handling of the calling party without routeing the call to the destination;
  • Release the call.
Due to interworking problems, the service operator shall ensure that sending of e-values and call period control is not used by the other services in the same call of the served subscriber with Enhanced CSE capability for Dialled Services.
Up

5.4  Calling party abandon  p. 21

The purpose of this procedure is to manage an outgoing call set-up at the time it is terminated by the calling party before the call is established.
If the CSE has activated this subsequent service event for this call in notify mode and the calling party abandon event occurs the VPLMN/IPLMN shall:
  • Notify the CSE and continue.
The following information shall be provided to the CSE:
  • Event met;
  • Type of monitoring;
The CSE shall send the following instruction:
  • Continue the call processing.
If the CSE has activated this subsequent service event for this call in request mode and the calling party abandon event occurs the VPLMN/IPLMN shall suspend call processing, make contact with the CSE and await further instructions.
When the VPLMN/IPLMN has made contact with the CSE in request mode, the CSE shall be able to instruct the VPLMN to act as described below.
  • Perform charging activities.
There shall be no restriction regarding the number of times the above instruction can be repeated. Once the CSE has concluded issuing the above instruction, it shall issue the following instruction:
  • Continue the call processing.
Up

5.5  Unsuccessful call establishment  p. 21

The purpose of this procedure is to manage an outgoing call set-up at the time when the call establishment is unsuccessful.
If no control relationship for the given call exists and
  • The unsuccessful call establishment procedure is defined as an initial service event (according to the CSI); and
  • The call attempt is unsuccessful; and
  • The triggering criteria are satisfied.
Then the VPLMN/IPLMN shall suspend call processing, make contact with the CSE and await further instructions.
If a relationship for the given call already exists and the CSE has activated this subsequent service event for this call and the unsuccessful call establishment event occurs the VPLMN/IPLMN shall:
  • Suspend call processing, notify the CSE and await further instructions, or
  • Notify the CSE and continue call processing.
In both cases above the following information shall be provided to the CSE:
  • Event met;
  • Type of monitoring;
  • Cause for unsuccessful call establishment:
    • Not reachable;
    • Busy;
    • No answer;
    • Route select failure.
If the unsuccessful call procedure is armed as an initial service event, a new relationship is opened only if triggering criteria are fulfilled and no relationship already exists for the same CSI.
When the VPLMN/IPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN/IPLMN to act as described below:
  • Perform charging activities;
  • Activate subsequent control service events for the call. The CSE shall have the possibility to send the following information:
    • The subsequent service event which shall be detected and reported:
      • Called party alert;
      • Called party connection;
      • Call disconnection;
      • Calling party abandon;
      • Unsuccessful call establishment. In the case of no answer the CSE may provide a no answer timer;
      • Mid call event (DTMF). The CSE shall specify the digit string(s) for which the instruction is valid. The arming and detection of the mid call event shall be limited to the VPLMN;
      • Change of Position. The CSE may specify notification criteria. The arming and detection of the Change of Position event shall be limited to the VPLMN;
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported (calling or called party);
    • The type of monitoring (control or notification).
  • Order in-band user interaction;
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Release the call;
  • Continue the call processing;
  • Continue the call processing with modified information.
Up

5.6  Called party connection procedure  p. 23

The purpose of this procedure is to manage an outgoing call set-up at the time when the called party answers and the call is successfully established.
If the CSE has activated this subsequent service event for this call and the called party connection event occurs the VPLMN/IPLMN shall:
  • Suspend call processing, notify the CSE and await further instructions, or
  • Notify the CSE and continue call processing.
The following information shall be provided to the CSE:
  • Event met;
  • The party in the call for which the event is reported (only called party applicable);
  • The charge indicator which will be used in the Call Data Record if available;
  • Type of monitoring.
When the VPLMN/IPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN/IPLMN to act as described below.
  • Perform charging activities;
  • Activate subsequent control service events for the call. The CSE shall have the possibility to send the following information:
    • The subsequent service event which shall be detected and reported:
      • Call disconnection;
      • Mid call event (DTMF). The CSE shall specify the digit string(s) for which the instruction is valid. The arming and detection of the mid call event shall be limited to the VPLMN;
      • Change of Position. The CSE may specify notification criteria. The arming and detection of the Change of Position event shall be limited to the VPLMN;
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported (calling or called party);
    • The type of monitoring (control or notification).
    • Order in-band user interaction.
    There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
    • Release the call;
    • Continue the call processing.
Up

5.7  Mid call procedure |R4|  p. 24

When the CSE instructs the VPLMN to arm the mid-call event it shall specify a criterion against which digits entered by the originating subscriber using the DTMF procedure shall be matched. It shall be possible for the CSE to instruct the VPLMN to re-arm the mid-call event when it is encountered.
In the following, each digit shall be taken from the ordered set (0 9, *, #).
The criterion consists of a list defining:
  • The minimum number of digits to be collected, and
  • The maximum number of digits to be collected, and
  • The maximum delay between successive digits, and optionally
  • The digit(s) used to indicate the start of the input, and optionally
  • The digit(s) used to indicate the end of the input, and optionally
  • The digit(s) used to indicate that the input shall be cancelled.
The minimum and maximum number of digits to be collected includes the digit(s) used to indicate the start and end of the input.
A digit string has been cancelled if:
  • The CSE has specified digit(s) used to indicate that the input shall be cancelled, and
  • The specified digit(s) has/have been received from the user.
If the CSE has specified digit(s) used to indicate the start of the input, then the input has started if:
  • The specified digit(s) has/have been received from the user, and
  • The digit string has not been cancelled.
If the CSE has not specified digit(s) used to indicate the start of the input, then the input has started if:
  • At least one digit has been received from the user, and
  • The digit string has not been cancelled.
If the CSE has specified digit(s) used to indicate the end of the input, then the input has ended if:
  • The specified digit(s) has/have been received from the user, or
  • The maximum number of digits has been received, or
  • The maximum delay between successive digits has been exceeded.
If the CSE has not specified digit(s) used to indicate the end of the input, then the input has ended if:
  • The maximum number of digits has been received, or
  • The maximum delay between successive digits has been exceeded.
A digit string satisfies the criterion for the Mid call detection point if:
  • The input has started, and
  • The digit string contains at least the minimum number of digits, and
  • The input has ended.
Triggering of the mid-call event shall occur immediately after the criterion has been satisfied. Once the triggering occurs the VPLMN shall disarm the mid-call event.
Digits collected from the subscriber shall be relayed as DTMF towards the destination subscriber independent of any CAMEL processing.
If the CSE has activated this service event for the served subscriber and a mid-call event (as determined by the criterion for the mid-call procedure being satisfied) occurs the VPLMN shall:
  • Suspend call processing, notify the CSE and await further instructions, or
  • Notify the CSE and continue call processing.
The following information shall be provided to the CSE:
  • Event met;
  • Type of monitoring;
  • Event specific data:
    • Received DTMF digits.
When the VPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN to act as described below:
  • Perform charging activities;
  • Activate other control service events for the call. The CSE shall have the possibility to send the following information:
    • The service event which shall be detected and reported:
      • Call disconnection;
      • Mid call event (DTMF). The CSE shall specify the digit string(s) for which the instruction is valid.
      • Change of Position. The CSE may specify notification criteria.
    • The party in the call for which the event shall be detected and reported (calling or a called party);
    • The type of monitoring (control or notification).
  • Order in-band user interaction.
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Release the call;
  • Continue the call processing;
  • Continue the call processing with modified information.
Up

5.8  Call disconnection procedure  p. 25

The purpose of this procedure is to manage the actions on disconnection of an established call. This procedure is applicable to any party in the call.
If the CSE has activated this subsequent service event for this call and the call disconnection event occurs the VPLMN/IPLMN shall:
  • Suspend call processing, notify the CSE and await further instructions, or
  • Notify the CSE and continue call processing.
The following information shall be provided to the CSE:
  • Event met;
  • The party in the call for which the event is reported;
  • Type of monitoring;
  • Disconnection reason.
When the VPLMN/IPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN/IPLMN to act as described below:
  • Perform charging activities
  • Activate subsequent control service events for the call. The CSE shall have the possibility to send the following information:
    • The subsequent service event which shall be detected and reported:
      • Called party alert;
      • Called party connection;
      • Call disconnection;
      • Calling party abandon;
      • Unsuccessful call establishment. In the case of no answer the CSE may provide a no answer timer;
      • Mid call event (DTMF). The CSE shall specify the digit string(s) for which the instruction is valid. The arming and detection of the mid call event shall be limited to the VPLMN;
      • Change of Position. The CSE may specify notification criteria. The arming and detection of the Change of Position event shall be limited to the VPLMN;
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported (calling or called party);
    • The type of monitoring (control or notification).
  • Order in-band user interaction;
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Continue the call processing, i.e. release the call;
  • Continue the call processing with modified information.
Up

5.9  CSE initiated call release procedure  p. 26

Following the CAMEL processing of the Call set-up request procedure it shall be possible for the CSE to initiate a call release at any moment of the call.
To use this procedure:
  • The originating VPLMN shall have reported an initial service event to the CSE and be waiting for instructions from the CSE, or
  • The CSE shall be waiting for the report of any subsequent service event (with "Type of monitoring" set to control).

5.10  Void

5.11  Called party alert reporting procedure |R5|  p. 27

The purpose of this procedure is to manage an outgoing call set-up at the time when the called party is alerted.
If the CSE has activated this service event for this call and the called party alert event occurs the IPLMN/VPLMN shall:
  • Suspend call processing, notify the CSE and await further instructions, or
  • Notify the CSE and continue call processing.
The following information shall be provided to the CSE:
  • Event met;
  • The party in the call for which the event is reported (only called party applicable);
  • Type of monitoring.
When the IPLMN/VPLMN has made contact with the CSE, the CSE shall be able to instruct the IPLMN/VPLMN to act as described below:
  • Perform charging activities;
  • Activate subsequent control service events for the call. The CSE shall have the possibility to send the following information:
    • The service event which shall be detected and reported:
      • Calling party abandon;
      • Unsuccessful call establishment. In the case of no answer the CSE may provide a no answer timer;
      • Call disconnection;
      • Mid call event (DTMF); The CSE shall specify the digit string(s) for which the instruction is valid. The arming and detection of the mid call event shall be limited to the VPLMN;
      • Change of Position. The CSE may specify notification criteria. The arming and detection of the Change of Position event shall be limited to the VPLMN;
      • Called party connection
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported;
    • The type of monitoring (control or notification).
  • Order in-band user interaction with the calling party.
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated. Once the CSE has concluded issuing the above instructions, it shall issue the following instruction:
  • Continue the call processing.
Up

5.12  Change of position procedure |R5|  p. 27

When the CSE instructs the VPLMN to arm the change of position event it may specify a list of up to 10 criteria against which the change of position shall be matched. The VPLMN shall report the event when the subscriber's location information changes and one of the criteria is met.
Each element of the list of criteria contains either:
  • the identifier of a location which the subscriber enters or leaves. It is specified as one of the following:
  • cell global id;
  • location area id;
  • service area id;
or one of the following types of handover:
  • "inter-system handover";
  • "inter-PLMN handover";
  • "inter-MSC handover".
If more than one criterion is met, then only one change of position event shall be reported to the CSE.
If this list of criteria is not included in the instruction, the criteria upon any change of position shall be regarded as fulfilled.
It shall be possible for the CSE to instruct the VPLMN to re-arm the change of position event when it is encountered.
If the CSE has activated this service event for the served subscriber and a change of position event occurs (as determined by the criteria for the change of position procedure being satisfied) the VPLMN shall:
  • Notify the CSE and continue call processing.
The following information shall be provided to the CSE:
  • Event met;
  • Type of monitoring;
  • Event specific data;
  • Location information;
  • Charge result if charging supervision is provided.
When the VPLMN has made contact with the CSE, the CSE shall be able to instruct the VPLMN to act as described below:
  • Perform charging activities;
  • Activate other control service events for the call. The CSE shall have the possibility to send the following information:
    • The service event which shall be detected and reported:
      • Change of position. The CSE may specify notification criteria.
  • The party in the call for which the event shall be detected and reported;
  • The type of monitoring (notification);
  • Order in-band user interaction.
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated.
Up

5.13  Change of basic service |R6|  p. 28

When the CSE has instructed the IPLMN/VPLMN to arm the change of basic service event, the IPLMN/VPLMN shall report the event when the basic service changes. It shall be possible for the CSE to instruct the IPLMN/VPLMN to re-arm the change of basic service event when it is encountered. The CSE may arm this event in the various phases of the call (as specified in this specification)- however the IPLMN/VPLMN reports the basic service changes in the active phase of the call only.
If the CSE has activated this service event for the served subscriber and a change of basic service event occurs the IPLMN/VPLMN shall:
  • Notify the CSE and continue call processing.
The following information shall be provided to the CSE:
  • Event met;
  • Type of monitoring;
  • Event specific data;
  • Basic service:
  • Charge result if charging supervision is provided:
When the IPLMN/VPLMN has made contact with the CSE, the CSE shall be able to instruct the IPLMN/VPLMN to act as described below:
  • Perform charging activities;
  • Activate other control service events for the call. The CSE shall have the possibility to send the following information:
    • The service event which shall be detected and reported:
      • Change of basic service.
    • The party in the call for which the event shall be detected and reported;
    • The type of monitoring (notification).
There shall be no restriction regarding the order of the above instructions or the number of times each of the above instructions can be repeated.
Up

Up   Top   ToC