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 23.078  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4.2…   4.3…   4.4…   4.5…   4.5.2…   4.5.3…   4.5.4…   4.5.5…   4.5.6…   4.5.7…   4.5.8…   4.6…   4.6.2…   4.6.3…   4.6.7…   4.6.13…   5…   6…   6.5…   6.6…   7…   7.5…   8…   9…   10…   11…   12…   A… 
7 Short Message Services  7.1 Architecture  7.2 Detection Points (DPs)  7.3 Description of CAMEL Subscriber Data  7.4 Description of SMS State Models 
...

 

7  Short Message Services  p. 618

7.1  Architecture  p. 618

7.1.1  Functional Entities used for CAMEL  p. 618

This subclause describes the functional architecture needed to support Mobile Originating Short Message Service (MO SMS) and Mobile Terminating Short Message Service (MT SMS) interworking for CAMEL. Figure 7.1-1 and Figure 7.1-2 show the functional entities involved in MO SMS or MT SMS requiring CAMEL support. Further details of the architecture needed to support Mobile Originating Short Message Service (MO SMS) and Mobile Terminating Short Message Service (MT SMS) are given in TS 23.040.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 7.1-1: Functional architecture for support of CAMEL control of MSC switched MO and MT SMS
Figure 7.1-1: Functional architecture for support of CAMEL control of MSC switched MO and MT SMS
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 7.1-2: Functional architecture for support of CAMEL control of SGSN switched MO and MT SMS
Figure 7.1-2: Functional architecture for support of CAMEL control of SGSN switched MO and MT SMS
(⇒ copy of original 3GPP image)
Up
HLR:
The HLR stores MO-SMS-CSI and/or MT-SMS-CSI. MO-SMS-CSI contains subscription information for subscribers that require CAMEL support of MO SMS. MT-SMS-CSI contains subscription information for subscribers that require CAMEL support of MT SMS. One or both of MO-SMS-CSI and MT-SMS-CSI are transferred to the VLR or to the SGSN on Location Update and Restore Data or when MO-SMS-CSI or MT-SMS-CSI has changed.
VLR:
The VLR receives the MO-SMS-CSI and MT-SMS-CSI for the subscriber from the HLR. MO-SMS-CSI and MT-SMS-CSI are used by the MSC to determine whether a Service Logic shall be invoked for an MO SMS submission or MT SMS delivery.
MSC:
The MSC receives MO-SMS-CSI and MT-SMS-CSI from the VLR and uses this to determine whether a Service Logic shall be invoked for an MO SMS submission or MT SMS delivery.
SGSN:
The SGSN receives the MO-SMS-CSI and MT-SMS-CSI for the subscriber from the HLR. The SGSN uses the MO-SMS-CSI and MT-SMS-CSI to determine whether a Service Logic shall be invoked for an MO SMS submission or MT SMS delivery.
gprsSSF:
see subclause 3.1.
gsmSSF:
see subclause 3.1.
gsmSCF:
see subclause 3.1.
SMSC:
The Short Message Service Centre accepts messages submitted by an MS or other MO short message entity, stores them and delivers them to the destination MS or other MT short message entity.
SMS-GMSC:
The Short Message Service Gateway MSC receives short messages from the SMSC, interrogates the HLR for routeing information to deliver each short message and forwards each short message to the serving node (MSC or SGSN) for delivery to the destination MS. The SMS-GMSC may be physically integrated with the SMSC or with the MSC for the destination subscriber.
SMS-IWMSC:
The Short Message Service InterWorking MSC terminates the MAP signalling from the MSC or the SGSN for MO short message submission, and transfers the short message to the SMSC, The SMS-IWMSC may be physically integrated with the SMSC or with the MSC for the originating subscriber.
Up

7.1.2  Interfaces defined for CAMEL  p. 620

7.1.2.1  HLR - VLR interface  p. 620

This interface is used to send CAMEL related subscriber data (MO-SMS-CSI and MT-SMS-CSI) to a visited MSC/VLR or to remove CAMEL related subscriber data from a visited MSC/VLR.

7.1.2.2  HLR - SGSN interface  p. 620

This interface is used to send CAMEL related subscriber data (MO-SMS-CSI and MT-SMS-CSI) to a visited SGSN or to remove CAMEL related subscriber data from a visited SGSN.

7.1.2.3  gsmSSF - gsmSCF interface  p. 620

This interface is used by the gsmSCF to control the handling of MO SMS and MT SMS in the MSC. A relationship on this interface is opened as a result of the gsmSSF sending a request for instructions to the gsmSCF.

7.1.2.4  gprsSSF - gsmSCF interface  p. 620

This interface is used by the gsmSCF to control the handling of MO SMS and MT SMS in the SGSN. A relationship on this interface is opened as a result of the gprsSSF sending a request for instructions to the gsmSCF.

7.1.2.5  MSC - gsmSSF interface  p. 620

This is an internal interface. The interface is described in the present document to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

7.1.2.6  SGSN - gprsSSF interface  p. 621

This is an internal interface. The interface is described in the present document to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

7.1.2.7  MSC - VLR interface  p. 621

This is an internal interface. The interface is described in the present document to make it easier to understand the internal information flow within the MSC/VLR.

7.1.2.8  MSC - SMSC interface  p. 621

This interface is used by the MSC to submit a SM to the SMSC and to deliver a SM to the MSC.

7.1.2.9  SGSN - SMSC interface  p. 621

This interface is used by the SGSN to submit a SM to the SMSC and to deliver a SM to the SGSN.

7.2  Detection Points (DPs)  p. 621

For the general handling of the DPs, see subclause 4.2.

7.2.1  Criteria at DP SMS Delivery Request |R5|  p. 621

The HLR may store a criterion that indicates when triggering shall take place. The criterion for DP SMS_Delivery_Request consists of a list of TPDU types. Refer to TS 23.040 for the available TPDU types. When the TPDU type of the Short Message is present in the list of TPDU types, then triggering shall take place. Otherwise, triggering shall not take place.
If no criterion is defined for a subscriber, then triggering shall take place regardless of the TPDU type of the Short Message.
Up

7.3  Description of CAMEL Subscriber Data  p. 621

7.3.1  Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI)  p. 621

This subclause defines the contents of the Short Message Service CAMEL Subscription Information.

7.3.1.1  gsmSCF address  p. 621

Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routeing.

7.3.1.2  Service Key  p. 621

The Service Key identifies to the gsmSCF the service logic.

7.3.1.3  Default SMS Handling  p. 621

The Default SMS Handling indicates whether the Short Message submission shall be released or continued as requested in the case of error in the dialogue between gsmSCF and gsmSSF or gprsSSF.

7.3.1.4  TDP List  p. 622

The TDP List indicates on which detection point triggering shall take place. For MO-SMS-CSI only DP SMS_Collected_Info is used.

7.3.1.5  CAMEL Capability Handling  p. 622

CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. This parameter shall be set to CAMEL Phase 3

7.3.1.6  CSI state  p. 622

The CSI state indicates whether the MO-SMS-CSI is active or not.

7.3.1.7  Notification flag  p. 622

The notification flag indicates whether the change of the MO-SMS-CSI shall trigger Notification on Change of Subscriber Data or not.

7.3.2  Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) |R5|  p. 622

This subclause defines the contents of the Mobile Terminating Short Message Service CAMEL Subscription Information.

7.3.2.1  gsmSCF address  p. 622

Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routeing.

7.3.2.2  Service Key  p. 622

The Service Key identifies to the gsmSCF the service logic.

7.3.2.3  Default SMS Handling  p. 622

The Default SMS Handling indicates whether the Short Message delivery shall be released or continued as requested in the case of error in the dialogue between gsmSCF and gsmSSF or gprsSSF.

7.3.2.4  TDP List  p. 622

The TDP List indicates on which detection point triggering shall take place. For MT-SMS-CSI only DP SMS_Delivery_Request is used.

7.3.2.5  DP criteria  p. 622

The DP criteria indicate whether the SMS_SSF shall request the gsmSCF for instructions.

7.3.2.6  CAMEL Capability Handling  p. 622

CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. This parameter shall be set to CAMEL Phase 4.

7.3.2.7  CSI state  p. 622

The CSI state indicates whether the MT-SMS-CSI is active or not.

7.3.2.8  Notification flag  p. 623

The notification flag indicates whether the change of the MT-SMS-CSI shall trigger Notification on Change of Subscriber Data or not.

7.3.3  gsmSCF address list for CSI |R5|  p. 623

The gsmSCF address list indicates a list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. This list is common to all CSI's.

7.4  Description of SMS State Models  p. 623

7.4.1  General Handling  p. 623

See subclause 4.4.1.
The State Model for MO SMS handling contains Points in Association (PIA's) instead of Points in Call (PIC's).

7.4.2  Mobile Originating SMS State Models  p. 623

7.4.2.1  Description of MO SMS state model  p. 623

The MO SMS state model is used to describe the actions in an MSC and in a SGSN during Mobile Originating SMS.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 7.2: MO SMS State Model
Figure 7.2: MO SMS State Model
(⇒ copy of original 3GPP image)
Up
CAMEL Detection Point DP Type Description
DP SMS_Collected_InfoTDP-RIndication that the MO-SMS-CSI is analysed and a mobile originated short message is received.
DP O_SMS_FailureEDP-N, EDP-RIndication that the SM submission to the Short Message Service Centre failed
DP O_SMS_SubmittedEDP-N, EDP-RIndication that the SM has been successfully submitted to the Short Message Service Centre.
Up
7.4.2.1.1  Description of the MO SMS state model (PIAs)  p. 624
This subclause describes the state model for originating SMS transfer. For each PIA a description can be found of the entry events, actions and exit events.
7.4.2.1.1.1  SMS Null & Start & Authorize  p. 624
Entry events:
  • Previous MO SMS transfer to the SMSC completed (DP O_SMS_Submitted).
  • Exception event is reported.
Actions:
  • Interface is idled.
  • Authentication.
  • Ciphering.
  • MO SMS subscription check.
  • RP-MO-DATA message containing the User Data and the SMSC address is received from MS.
  • The supplementary service "barring of all outgoing calls" is checked and invoked if necessary.
  • The ODB category "barring of all outgoing calls" is checked and ODB is invoked if necessary.
Exit events:
  • MO-SMS-CSI is analysed.
  • An exception condition is encountered.
Up
7.4.2.1.1.2  SMS Analyse & Routing  p. 624
Entry events:
  • MO-SMS-CSI is analysed (DP SMS_Collected_Info).
Actions:
  • Information being analysed and/or translated to determine routeing address of the SMSC.
  • Outgoing barring services and ODB categories not already applied are checked and invoked if necessary. If any of the barring services or ODB categories prevents the submission of the MO-SMS, then the MSC or SGSN shall generate the "O_SMS_Failure" event. The cause code to be used in that case shall be "sM-DeliveryFailure".
  • The short message is sent to the SMSC.
Exit events:
  • Acknowledge from the SMSC is received. (DP O_SMS_submitted).
    A positive acknowledgement is sent to the MS.
  • An exception condition is encountered - this leads to the SMS_Exception PIA.
    A negative acknowledgement is sent to the MS.
  • Attempt to select the route for the SMS fails (DP O_SMS_Failure).
    A negative acknowledgement is sent to the MS.
  • Negative acknowledgement from the SMSC is received (DP O_SMS_Failure).
    A negative acknowledgement is sent to the MS.
Up
7.4.2.1.1.3  SMS_Exception  p. 625
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 PIA cannot be met.
Actions:
  • Default handling of the exception condition is applied. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as:
  • If a relationship exists between the gsmSCF and gsmSSF or gprsSSF send an error information flow closing the relationship and indicating that any outstanding Short Message handling instructions will not run to completion.
  • The MSC/gsmSSF or SGSN/gprsSSF shall make use of vendor-specific procedures to ensure release of internal resources.
Exit events:
  • Default handling of the exception condition by MSC/gsmSSF or SGSN/gprsSSF completed.
Up

7.4.3  Mobile Terminating SMS State Model |R5|  p. 625

7.4.3.1  Description of MT SMS state model  p. 625

The MT SMS state model is used to describe the actions in an MSC and in a SGSN during Mobile Terminating SMS.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 7.3: MT SMS State Model
Figure 7.3: MT SMS State Model
(⇒ copy of original 3GPP image)
Up
CAMEL Detection Point DP Type Description
DP SMS_Delivery_RequestTDP-RIndication that the MT-SMS-CSI is analysed and a mobile terminating short message or status report is received.
DP T_SMS_FailureEDP-N, EDP-RIndication that the SM delivery to the Mobile Station has failed
DP T_SMS_DeliveredEDP-N, EDP-RIndication that the SM has been successfully delivered to the Mobile Station.
Up
7.4.3.1.1  Description of the MT SMS state model (PIAs)  p. 626
This subclause describes the state model for terminating SMS transfer. For each PIA a description can be found of the entry events, actions and exit events.
7.4.3.1.1.1  SMS Null & Start & Authorize  p. 626
Entry events:
  • MAP-MT-FORWARD-SHORT-MESSAGE message is received from SMS-GMSC.
  • Previous MT SMS transfer to the MS completed (DP T_SMS_Delivered).
  • Exception event is reported.
Actions:
  • Interface is idled.
  • MT SMS subscription check.
  • MT-SMS-CSI is received from the VLR (in the MSC only).
Exit events:
  • MT-SMS-CSI is analysed.
  • An exception condition is encountered.
7.4.3.1.1.2  SMS Delivery  p. 626
Entry events:
  • MT-SMS-CSI is analysed. (DP SMS_Delivery_Request).
Actions:
  • Subscriber paging is performed, if required.
  • The short message is delivered to the MS.
Exit events:
  • Acknowledge from the MS is received. (DP T_SMS_Delivered).
    A positive acknowledgement is sent to the SMSC.
  • An exception condition is encountered - this leads to the SMS_Exception PIA.
    A negative acknowledgement is sent to the SMSC.
  • Negative acknowledgement from the MS is received (DP T_SMS_Failure).
    A negative acknowledgement is sent to the SMSC.
Up
7.4.3.1.1.3  SMS_Exception  p. 627
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 PIA cannot be met.
Actions:
  • Default handling of the exception condition is applied. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as:
  • If a relationship exists between the gsmSCF and gsmSSF or gprsSSF send an error information flow closing the relationship and indicating that any outstanding Short Message handling instructions will not run to completion.
  • The MSC/gsmSSF or SGSN/gprsSSF shall make use of vendor-specific procedures to ensure release of internal resources.
Exit events:
  • Default handling of the exception condition by MSC/gsmSSF or SGSN/gprsSSF completed.
Up

Up   Top   ToC