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

Top   Top   Up   Prev   Next
1…   4…   5…   5.4…   6…   6.3   6.4…   7…   7.3   7.4…   7.5a…   8…   8.2.4a…   8.3…   8.4…   B…   B.2…   B.2.2…   B.2.3a…   B.2.3a.4…   B.2.4…   B.3…   C…   C.8… 
C SMS in MME  C.1 General  C.2 Architecture  C.3 Reference Points  C.4 Network Entities  C.5 Roaming considerations  C.6 Unsuccessful Mobile-Terminated SMS Transfer  C.7 Information storage 

 

C (Normative)  SMS in MME |R11|  p. 93

C.1  General  p. 93

SMS in MME is an architecture option primarily intended for networks that do not deploy GERAN or UTRAN. SMS in MME delivers SMS services over EPS NAS signalling for UE's requiring SMS services. SMS in MME architecture option enables support of SMS in the EPS via E-UTRAN without requiring deployment of 3GPP MSCs.
For SMS in MME the SMS service control is performed by the MME. The MME receives SMS subscriber data and the MME verifies whether the subscriber is permitted to obtain SMS services.
The SMS subscriber data received and used by the MME may be PS subscriber data (the MME directly obtains from HSS) or CS subscriber data (the MME obtains via an interworking function as described in clause C.5).
MPS priority treatment of SMS via MME for a UE with an MPS subscription is supported as described TS 23.401.
Up

C.2  Architecture  p. 93

As outlined in the architecture Figure below SMS in MME requires support of SMS functionality in the MME and the MME also needs to receive SMS subscription information from the HSS. The SMS subscription information may be received through the S6a interface.
Copy of original 3GPP image for 3GPP TS 23.272, Fig. C.2-1: SMS in MME Architecture
Figure C.2-1: SMS in MME Architecture
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.272, Fig. C.2-2: SMS in MME architecture using IWF
Figure C.2-2: SMS in MME architecture using IWF
(⇒ copy of original 3GPP image)
Up
There is no impact on the UE and E-UTRAN. The SMS entities (including SMS router, etc.) functionality to support SMS in MME is the same as defined for reference point 2 and 3 in TS 23.040 except the SGd and S6c interfaces use Diameter protocols as specified in TS 29.338. The interaction between SMS in MME and SMS over IP is described in TS 23.204.
Up

C.3  Reference Points  p. 94

C.3.1  General  p. 94

The following reference points specifically enable support of SMS in MME.

C.3.2  S6a  p. 94

In order to support "SMS in MME" the S6a shall allow the MME to request SMS subscription information and to register as a serving node for SMS. If the HSS supports this and has SMS subscription information available, it sends SMS subscription data to the MME. The SMS subscription data include for example the barring status of MO-SMS and MT-SMS and the MSISDN. If the HSS determines that the MME shall be deregistered for SMS, it shall indicate to the MME that it is not registered for SMS.
Up

C.3.3  S6c  p. 94

In order to support "SMS in MME" the Diameter based S6c shall allow the SMS central functions to request routing information from the HSS.

C.3.4  SGd  p. 95

In order to support "SMS in MME" the Diameter based SGd shall provide the Short Message Relay Layer (SM-RL) between MME serving the UE and SMS central functions.

C.4  Network Entities  p. 95

C.4.1  General  p. 95

The following network entities specifically enable support of SMS in MME

C.4.2  MME  p. 95

The MME needs to support the following features:
  • UE-MME NAS procedures for SMS over SGs.
  • S6a functionality as described in clause C.3.2.
  • SMS procedures between UE and MME including support for the Short Message Control (SMC) and Short Message Relay (SM-RL) functions defined in TS 24.011.
  • Reporting UE's availability for receiving MT SMS to the HSS.
  • SMS functions including charging and Lawful Interception (LI).
  • Support combined EPS/IMSI procedures for "SMS-only" and in these:
    • provide a non-broadcasted LAI (not associated with any VLR); and
    • if needed provide a reserved TMSI that cannot cause any ambiguities with other TMSIs (e.g. when the UE changes to an area where it needs to derive SMS services from a GERAN/UTRAN MSC); and
    • indicate in the Attach/TAU Accept message that the IMSI attach is for "SMS-only"; and
    • notify the HSS it is capable of SMS transfer without the need of establishing an SGs association with an MSC; and
    • obtain SMS-related subscription information.
  • Support the registration procedures for SMS in MME described in clause C.8.
  • Support for Service Gap Control for MO SMS as specified in clause 4.3.17.9 of TS 23.401.
  • Support MPS priority treatment (e.g. determining the DRMP value in the messages related to SMS delivery, Paging Priority setting when paging is triggered for UE in CM-IDLE mode) for SMS delivery based on MPS for Messaging indication in HSS data.
Up

C.4.3  HSS  p. 95

When an MME registers via the S6a including a registration for SMS Request, the HSS registers the MME as an MSC for MT SMS (i.e. in response to Send Routing Information (SRI) for SM the MME identity is passed back to the SMS-GMSC/SMS router) when the HSS supports and decides to use SMS in MME. This registration as an MSC for MT SMS causes the HSS to cancel any old registered MSC. See clause C.8 for the detailed registration procedures. If the HSS receives a SRI for other CS Services than SMS it shall treat the UE as if it was detached from the CS domain. If the UE subsequently registers with an MSC for CS services, the HSS needs to replace the MME with the new MSC as the destination for SMS (but this is not a reason to cancel the MMEs registration for EPS Services).
An HSS allows an operator to configure a subscription, which is limited to only PS domain services and to SMS service via the CS and the PS domain. This limitation is indicated in the PS subscription data as "PS and SMS only".
When an HSS supports "SMS in MME", i.e. provides all HSS functionality described for "SMS in MME", and the operator configured the HSS to apply that functionality, the HSS indicates "SMS in MME Support" in the data provided to an MME.
If the HSS determines that an MME shall be deregistered for SMS (e.g. because of a removal of SMS subscription, CS location update, etc), the HSS shall indicate to the MME that it is not registered for SMS.
The HSS data, as in clause C.7.1, may include the MPS for Messaging indication parameter if the parameter is provisioned by an AS (as specified in TS 23.682) or by an operator. The HSS provides the parameter to the MME and to the SMS-GMSC/SMS router/IP-SM-GW when the HSS responds to an SMS routing information request.
Up

C.5  Roaming considerations  p. 96

The SMS in MME architecture is an optional architecture enhancement for operators that wish to avoid to the use of MSC and SGs and do not provide Fallback to 3GPP CS services over GERAN or UTRAN.
To support inbound roamers from networks that do not support the provision of SMS subscription information over S6a there are different options to provide interworking, e.g.:
  • SMS over SGs.
  • Use of an interworking function to convert between the S6a with SMS subscription data and S6a without SMS subscription data and D for SMS subscription. When the MME sends Ready for SM message to HSS for UE reachability notification, the interworking function also needs to convert the Ready for SM message transferred via the S6a interface to Ready for SM message transferred via the D interface.
Operators that do not deploy the SMS in MME architecture option are not required to support the S6a enhancements in the HSS or the MME.
Up

C.6  Unsuccessful Mobile-Terminated SMS Transfer  p. 96

The MME or the HSS may not be able to deliver the SM to the UE. This can for example happen when the UE is not attached to EPS, when the UE's SMS memory capacity is exceeded, or when the Mobile-terminated SMS is barred.
When the MME cannot deliver the SM to the UE, the MME shall return a failure report to the SMS GMSC/SMS router. The SMS-GMSC/SMS router/HSS procedures for handling the failure report are specified in TS 23.040. Additionally, if the SM failed due to the UE not being reachable, the MME shall set the Mobile-Not-Reachable-Flag-in-MME-for-SMS (MNRF-MME) indication in the MME.
If the UE is using extended idle mode DRX with a DRX cycle value or if the UE is in PSM (as defined in TS 23.682) that can cause mobile terminating SMS retransmissions, the MME may return a failure report to the SMS GMSC/SMS router while still paging the UE. The MME shall set the Mobile-Not-Reachable-Flag-in-MME-for-SMS (MNRF-MME) indication in the MME.
If the UE subsequently becomes reachable and MNRF-MME indication is set, the MME shall send a Ready for SM (IMSI, UE-Present) message to the HSS and the MME shall clear the corresponding MNRF-MME indication for that UE.
If the UE subsequently notifies the MME that SMS memory is available, the MME shall send a Ready for SM (IMSI, UE-Memory-Available) message to the HSS.
Reception of a Ready for SM message or an Update Location Request message by the HSS when MNRF is set, shall trigger the SMS alert procedure as defined in TS 23.040.
Up

C.7  Information storage  p. 97

C.7.1  HSS  p. 97

The following table specifies the HSS data defined per UE to support SMS in MME.
Field Description
SMS Subscription ParametersSMS subscription parameters, e.g. SMS teleservice, SMS barring list.
Network Access Mode (NAM)Indicates whether the subscription includes subscriber data allowing for accessing PS and or CS domain. (Note 2)
PS and SMS onlyIndicates a subscription which is limited to PS domain services and to SMS service via the CS and the PS domain. (Note 2)
MME Registered for SMSIndicates that MME has been registered for SMS in the HSS
MPS for MessagingIndicates whether the user has MPS for Messaging set (enabled)/cleared (disabled) as described in clause C.1. This MPS for Messaging indication parameter is valid only when the MPS-EPS-Priority bit is set.
When the HSS functionality for "SMS in the MME" is enabled, the HSS will include an "SMS in MME" feature indication along with the UE subscription information to the MME.
Up

C.7.2  MME  p. 97

The following table specifies the MME data defined per UE to support SMS in MME.
Field Description
SMS Subscription DataSMS subscription parameters, e.g. SMS teleservice, SMS barring list.
MME Registered for SMSIndicates that MME has been registered for SMS in the HSS
MNRF-MMEIndicates whether activity from the UE shall be reported to the HSS.
Network Access Mode (NAM)Indicates whether the subscription includes subscriber data allowing for access to PS and or CS domain. (Note 1)
PS and SMS onlyIndicates a subscription which is limited to PS domain services and to SMS service via the CS and the PS domain. (Note 1)
SMS in MME SupportCapability of the HSS to support the SMS in MME feature
MPS for MessagingIndicates whether the user has MPS for Messaging set (enabled)/cleared (disabled) as described in clause C.1. This MPS for Messaging indication parameter is valid only when the MPS-EPS-Priority bit is set.
Up

Up   Top   ToC