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… 
9 Procedures for SMS  9.1 Criteria for contact with the CSE  9.2 Short message submission request procedure  9.3 Successful Short Message submission procedure  9.4 Unsuccessful Short Message submission procedure  9.5 Short message delivery request procedure  9.6 Successful Short Message delivery procedure  9.7 Unsuccessful Short Message delivery procedure  9.8 Charging Procedures 
...

 

9  Procedures for SMS  p. 43

9.1  Criteria for contact with the CSE  p. 43

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:

9.1.1  CSI criteria applicable at Short message delivery |R5|  p. 43

9.1.1.1  CSI criteria applicable at SM delivery when MT SM attempt has been received  p. 43

CSI criteria may be defined for a subscriber for the MT SM delivery.
  • Criterion on the status report;
    This criterion can indicate:
    • The VPLMN shall trigger only in the case of a status report;
    • The VPLMN shall not trigger in the case of a status report.
When this criterion is not present this criterion is regarded as satisfied.

9.2  Short message submission request procedure  p. 43

The purpose of this procedure is to detect an SMS set-up request and to allow the CSE to modify the handling of the SMS set-up request.
The SMS set-up request may be circuit switched based or packet switched based.
If (according to the CSI):
  • The subscriber is provisioned with a CAMEL based SMS originating service; and
  • The SMS set-up request occurs
Then the VPLMN shall suspend SMS processing, make contact with the CSE and await further instructions.
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 subsequent control service events for the SM submission. The CSE shall have the possibility to send the following information:
    • The subsequent service event which shall be detected and reported:
      • Successful SM submission to the SMSC
      • Unsuccessful SM submission to the SMSC;
      • The type of monitoring.
There shall be no restriction regarding the order of the above instructions. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Bar the SM submission;
  • Continue the submission;
  • Continue the SM submission with modified information. The CSE shall have the possibility to send the following information:
    • Called Party Number;
    • Calling Party Number;
    • SMSC address.
If the SM submission is barred, the served subscriber shall be informed.
Up

9.3  Successful Short Message submission procedure  p. 44

The purpose of this procedure is to detect the successful submission of a Short Message (SM) to the SMSC and to inform the CSE about it.
If the successful SM submission event occurs then the VPLMN shall suspend processing, make contact with the CSE and await further instructions or send a notification and continue.
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.
Once the CSE has concluded performing charging activities, it shall issue the following instruction:
  • Continue the processing.
Up

9.4  Unsuccessful Short Message submission procedure  p. 44

The purpose of this procedure is to detect the unsuccessful submission of a Short Message (SM) to the SMSC and to inform the CSE about it.
If the unsuccessful SM submission event occurs then the VPLMN shall suspend processing, make contact with the CSE and await further instructions or send a notification and continue.
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.
Once the CSE has concluded performing charging activities, it shall issue the following instruction:
  • Continue the processing.
Up

9.5  Short message delivery request procedure |R5|  p. 45

The purpose of this procedure is to detect a SMS set-up request and allow the CSE to modify the handling of the SMS set-up request.
The SMS set-up request may be circuit switched based or packet switched based.
If according to the CSI:
  • The subscriber is provisioned with a CAMEL based SMS terminating service, and
  • The SMS set-up request occurs
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 SM delivery. The CSE shall have the possibility to send the following information:
    • The service event which shall be detected and reported:
      • Successful SM delivery to the MS;
      • Unsuccessful SM delivery to the MS.
There shall be no restriction regarding the order of the above instructions. Once the CSE has concluded issuing the above instructions, it shall issue one and only one of the following instructions:
  • Bar the SM delivery;
  • Continue the delivery;
  • Continue the SMS delivery with modified information. The CSE shall have the possibility to send the following information:
    • Calling Party Number.
If the SM delivery is barred, the SMSC shall be informed.
Up

9.6  Successful Short Message delivery procedure |R5|  p. 45

The purpose of this procedure is to detect the successful delivery of a Short Message (SM) to the MS and to inform the CSE about it.
If the successful SM delivery event occurs then the VPLMN shall suspend processing, make contact with the CSE and await further instructions or send a notification and continue.
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.
Once the CSE has concluded performing charging activities, it shall issue the following instruction:
  • Continue the processing.
Up

9.7  Unsuccessful Short Message delivery procedure |R5|  p. 45

The purpose of this procedure is to detect the unsuccessful delivery of a Short Message (SM) to the MS and to inform the CSE about it.
If the unsuccessful SM delivery event occurs then the VPLMN shall suspend processing, make contact with the CSE and await further instructions or send a notification and continue.
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.
Once the CSE has concluded performing charging activities, it shall issue the following instruction:
  • Continue the processing.
Up

9.8  Charging Procedures |R5|  p. 46

9.8.1  Inclusion of Free Format data in CDR  p. 46

The CSE may send free format data to the VPLMN, for inclusion in a CDR.
When sending the free format data to the VPLMN, the CSE may instruct the VPLMN to
  • Overwrite the existing data in the CDR with the newly received free format data, or
  • Append the newly received free format data to the existing data in the CDR.

Up   Top   ToC