Content for TS 23.204 Word version: 19.0.0

0… 5… 6… 6.3a 6.4… 6.5… 6.6… 6.8 6.9 6.10… 6.12… 6.15 6.16 6.17… A B… B.2…

3.1 Definitions 3.2 Abbreviations 4a.1 General 4a.2 Transport-level interworking 4a.3 Service-level interworking 4a.4 SMS without MSISDN 4a.5 SMS without MSISDN interworking with Non-supporting MSISDN-less SMS UE
...

0 Introduction p. 5

The Short Message Service (SMS) has have enjoyed great success in cellular networks. At the same time, specifications have been and are being developed for extending 3GPP services to non-cellular IP Connectivity Access Networks (IP-CANs). In this same spirit, this specification describes the capabilities needed to support SMS for generic IP-CANs.

SMS over generic IP access can be used to support applications and services that use SMS when a generic IP access is used.

1 Scope p. 6

The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228). These include (but are not limited) to:

Enhancements to the HSS;
Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
Authentication of service usage and registration;
Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
Mechanisms to handle MT-SMS without MSISDN to IMS UE, and SMS between IMS UEs that support MSISDN-less SMS operation.

The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.

The document also specifies the capabilities and enhancements needed to support service level interworking for the Short Message service, as defined in the TS 23.040 and in this specification and the OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. The features supported from the CPM specification are the exchange of short or large immediate messages in pager mode, as well as session-based messaging.

The service requirements are described in TS 22.340.

2 References p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".

[3] Void.

[4] Void.

[5] Void.

[6]

TS 29.002: "Mobile Application Part (MAP) specification".

[7] Void.

[8] Void.

[9]

TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[10] Void.

[11] Void.

[12]

OMA-TS-SIMPLE_IM-V1_0: "Instant Messaging using SIMPLE", http://www.openmobilealliance.org/.

[13]

RFC 5438: "Instant Message Disposition Notification", February, 2009.

[14]

TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".

[15]

OMA-RD-CPM-V1_0: "CPM Requirements", http://www.openmobilealliance.org/.

[16]

OMA-AD-CPM-V1_0: "CPM Architecture", http://www.openmobilealliance.org/.

[17]

OMA-TS-CPM_Conv_Fnct-V1_0: "CPM Conversation Functions", http://www.openmobilealliance.org/.

[18]

TS 22.340: "IP Multimedia System (IMS) messaging; Stage 1".

[19]

RFC 4975: "The Message Session Relay Protocol (MSRP)", September 2007.

[20]

TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".

[21]

TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".

[22]

TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".

[23]

TS 23.501: "System Architecture for the 5G System; Stage 2".

[24]

TS 23.502: "Procedures for the 5G System; Stage 2".

[25]

TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".

3 Definitions and abbreviations p. 7

3.1 Definitions p. 7

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following definitions apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905:

Converged IP Messaging:

as defined in OMA-RD-CPM-V1_0 [15]. Converged IP Messaging supports one-to-one, one-to-many personal communications, and also communication with Applications.

CPM Message:

as defined in OMA-RD-CPM-V1_0 [15]: Information that is sent to one or more recipients. A CPM Message can contain several discrete Media (e.g. text, images, audio-clips, video-clips).

CPM AS:

An application server supporting the functionality of a CPM Participating Function and/or a CPM Controlling Function as defined in OMA-RD-CPM-V1_0 [15].

IM origination:

origination of an Instant Message by an IMS UE.

IM termination:

termination of an Instant Message by an IMS UE.

IMS core:

refers to the core session control elements of the IM CN Subsystem, i.e. the CSCFs, and the IBCF.

Instant Message:

an Instant Message as defined in the OMA-TS-SIMPLE_IM-V1_0 [12] and TS 24.247. The term Instant Message is also used to designate a CPM Message.

Interworking Selection Function:

as defined in OMA-AD-CPM-V1_0 [16]. The Interworking Selection Function selects an Interworking Function that should perform the actual interworking between CPM and SMS.

MSISDN-less SMS operation:

operation to support SMS communication without the need of MSISDN in the UE's IMS subscription profile.

MSISDN-less Correlation ID:

information element which consists of Receiver Identity (i.e. SIP-URI of B party), Sender Identity (i.e. SIP-URI of A party), and HLR Identity (i.e., HLR that serves the B party).

Non-supporting MSISDN-less SMS UE:

a UE which does not support MSISDN-less SMS operation as defined in this specification.

SIMPLE IM service:

the Instant Messaging Service as defined in the OMA-TS-SIMPLE_IM-V1_0 [12].

SM origination:

origination of a Short Message (including SMS over IP) by an SMS capable UE, as defined in TS 23.040 and this specification.

SM termination:

termination of a Short Message (including SMS over IP) by an SMS capable UE, as defined in TS 23.040 and this specification.

SMS:

the Short Message Service as defined in the TS 23.040.

SMSF:

the SMS Function as defined in TS 23.501.

SMSIP MESSAGE:

an immediate message as defined in TS 23.228, which encapsulates a SM in its text body.

SMSIP UE:

a UE which supports SMSIP MESSAGE.

3.2 Abbreviations |R8| p. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply:

CPM

Converged IP Messaging

Instant Message

IMDN

Instant Message Disposition Notification

IP-SM-GW

IP-Short-Message-Gateway

ISF

Interworking Selection Function

Short Message

4 Void

4a Architecture Requirements p. 8

4a.1 General |R8| p. 8

The SMS-IP architecture supports the following:

Notification shall be sent to the HSS that a previously unreachable UE is now reachable.
Functionality is required to be able to select the domain for message delivery between IMS and CS/PS, and to have the message delivered to the selected domain.
Functionality is required to determine whether to transform the message format or not, and to perform the transformation of the message format when determined.
The interworking function shall generate the appropriate charging-related information and provide the appropriate online charging mechanism (if it is applied for the Short Message Service and/or SIMPLE IM services and/or CPM based services) for the interworking services.

4a.2 Transport-level interworking |R8| p. 9

For transport-level interworking , the architecture allows for the following:

A registration and de-registration mechanism shall be supported where UEs are required to explicitly indicate their ability to send and receive encapsulated Short Messages.
It shall provide for the transport of Short Message Service TP layer PDUs (TS 23.040) and associated RP layer information.

4a.3 Service-level interworking |R8| p. 9

For service-level interworking, the architecture allows for the following:

The service-level interworking is a value added service which requires service subscription. In addition, it shall also take the operator's policy, if available, into account, e.g. checking on the barring setting of the subscriber to determine whether to provide this interworking or not, so the service authorisation shall be supported before the interworking is executed.
The service-level interworking applies as a fallback only if the users cannot communicate with each other using their chosen messaging service according to the user preference and operator policy. The location of the interworking service can be in the originating network and in the terminating network.
The service-level interworking shall support interworking between OMA SIMPLE IM service as defined in OMA-TS-SIMPLE_IM-V1_0 [12] and Short Message Service, as defined in the TS 23.040 and in the current specification.
The service-level interworking shall support interworking between OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17] and Short Message Service, as defined in the TS 23.040 and in the current specification.
The service-level interworking shall take the capability of the terminating UE into account when possible.
The service level interworking shall be transparent to the end user.
The service-level interworking shall minimize the impact on the IMS architecture.
The service-level interworking shall not impact existing functionality of the Short Message Service as described in TS 23.040 or of the SIMPLE IM service enabler as described in OMA-TS-SIMPLE_IM-V1_0 [12] or of the CPM service enabler as described in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. Existing security mechanisms for the SIMPLE IM service, the Converged IP Messaging service and the Short Message Service shall be reused.
The interworking function shall be aware if the message should be interworked or not, e.g. specific types of Short Messages such as an over the air configuration message, shall not be interworked at service-level, but shall be instead transported as a Short Message via IMS, CS or PS.
If an SMS user requests an SMS status report that the message was delivered to the recipient, then an SMS status report shall be generated when the message is delivered using Instant Message.
If an IMS user requests a notification that the message was delivered to the recipient and the Instant Message is interworked to Short Message on the originating side, an SMS status report shall be interworked to a delivery notification when the message is delivered.
The interworking functionality shall be executed in the following cases:
- Originating network:
  - The sender is an IM user or a CPM user who has subscribed to the interworking function and the recipient is not routable in IMS;
  - The operator policy on the originating side has been set to send the Instant Messages via Short Message Service.
- Terminating network:
  - The user preferences and/or the operator policy of the recipient have been set to receive the incoming Instant Messages via Short Message Service;
  - The received message is a Short Message and the recipient is an IM user or a CPM user and has subscribed to the interworking service.

4a.4 SMS without MSISDN |R11| p. 10

For SMS without MSISDN interworking, the architecture allows for the following in addition to clause 4a.2:

It shall provide for the transport of Mobile Terminating Short Message Service to UE without the need of MSISDN in the UE's IMS subscription profile.
It shall provide for the transport of Mobile Originating Short Message Service from IMS UE that supports MSISDN-less SMS operation to other IMS UE.

4a.5 SMS without MSISDN interworking with Non-supporting MSISDN-less SMS UE |R12| p. 10

This version of the specification does not require the support of SMS communication between IMS UE that supports MSISDN-less SMS operation as defined in this specification and non-supporting MSISDN-less SMS UE.