1、 ETSI TS 123 142 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Value-added Services for SMS (VAS4SMS); Interface and signalling flow (3GPP TS 23.142 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI T
2、S 123 142 V14.0.0 (2017-04)13GPP TS 23.142 version 14.0.0 Release 14Reference RTS/TSGC-0423142ve00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucrat
3、if enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the pre
4、sent document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network d
5、rive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in
6、the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as
7、authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM
8、, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Ass
9、ociation. ETSI ETSI TS 123 142 V14.0.0 (2017-04)23GPP TS 23.142 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for
10、ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:
11、/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essenti
12、al to the present document. Foreword This Technical Specification (TS) has been produced by the ETSI 3rdGeneration Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpr
13、eted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“
14、, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 123 142 V14.0.0 (2017-04)
15、33GPP TS 23.142 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions 6g33.1 Definitions 6g34 VAS-SMS service requirements 7g34.1 General description of VAS-SMS service requirements 7g34.2 Ope
16、rational requirements . 8g34.2.1 VAS-SMS Provision/withdrawal 8g34.2.1.1 General 8g34.2.1.2 Requirements on the originating network side 8g34.2.1.3 Requirements on the terminating network side . 8g35 Architecture and Interface 8g35.1 Architectural requirements . 8g35.2 Reference model . 8g35.2.1 Log
17、ical network architecture 8g35.2.2 Functional entities . 9g35.2.2.1 VAS AS (VAS SMS Application Server) . 9g35.2.2.2 SMS node 9g35.2.2.3 Service Portal Function (SPF) . 9g35.2.2.4 Billing and Charging Function (BCF) . 9g35.2.3 Interfaces. 9g36 VAS-SMS service provisioning, activation 2 presented to
18、TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the docu
19、ment. ETSI ETSI TS 123 142 V14.0.0 (2017-04)63GPP TS 23.142 version 14.0.0 Release 141 Scope The present document describes the stage 2 of the VAS4SMS (Value Added Service for SMS). It includes: - The logic architecture; - The logic elements functionality; - The signaling flows; - The interaction wi
20、th other features. The service requirements of VAS4SMS are specified in 3GPP TS 22.142 2. The functionality and mechanism of SMS Service is defined in 3GPP TS 23.040 4. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present
21、 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 docum
22、ent (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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.142: “Value Added Services (VAS) for Short Message Service (SMS) require
23、ments “. 3 3GPP TS 22.041: “Operator Determined Barring (ODB)“. 4 3GPP TS 23.040: “Technical realization of the Short Message Service (SMS)“. 5 3GPP TS 23.204: “Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access“. 3 Definitions 3.1 Definitions For the purposes of
24、the present document, the terms and definitions given in TR 21.905 x and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 x. Loop prevention indication: a indication set by VAS AS which indicates that a VAS servic
25、e has been applied to generate this new message, e.g. message receipt, auto reply or message forwarding service. This indication is used by recipients VAS AS to check before also generating a new message to prevent loops. Message transfer: this term is used for SM transfer between MS and SMS Node. D
26、elivery report: this term is used to deliver the status report of original SM between MS and SMS Node VAS check: this term is used for the SMS Node to inquire the VAS AS if the VAS of user has activated. VAS check response: this term is used for the VAS AS to reply the result of VAS check. ETSI ETSI
27、 TS 123 142 V14.0.0 (2017-04)73GPP TS 23.142 version 14.0.0 Release 14Submit short message: this term is used for the VAS AS to submit a new message to the SMS Node. Submit short message sesponse: this term is used for the SMS Node to acknowledge the submit short message from the VAS AS. VAS deliver
28、y report: this term is used for the SMS Node to deliver status report of the short message from the VAS AS. VAS submittal report: this term is used for the VAS AS to submit a general status report of the short message which generated by the VAS AS based on VAS delivery report. Relay short message: t
29、his term is used to transfer the short message between SMS Nodes. Delivery status notification: this term is used to deliver VAS submittal report between SMS Nodes. NOTE: Relay short message and Delivery status notification are functionally equivalent to Message transfer and Delivery report respecti
30、vely. Different naming is used to allow different mapping in stage 3 protocols 4 VAS-SMS service requirements 4.1 General description of VAS-SMS service requirements As defined in 3GPP TS 22.1422, the VAS4SMS is an operator specific service by which an operator enables the subscriber to experience s
31、ome value-added service features for SMS. VAS4SMS features that were defined in stage 1 include: 1) Short Message Forwarding 2) Short Message Forwarding Multiple Subscriptions 3) Short Message Filtering 4) Short Message Receipt 5) Short Message Network Storage 6) Short Message to Multiple Destinatio
32、ns 7) Short Message Virtual Private Network (VPN) 8) Short Message Auto Reply 9) Short Message Personal Signature 10) Short Message Deferred Delivery VAS4SMS should not negatively affect the normal SMS communication between calling and called parties. The service subscriber is able to subscribe to t
33、he VAS4SMS service, activate (or de-activate) the service, and update the settings, e.g., to change by configure the personalized service related information. The personalized service information can consist of message signature, the forwarding destination address and message contents for auto reply
34、, etc. The VAS4SMS subscriber is able to refine the VAS4SMS behaviour with configured rules, e.g. time, the identity of the calling party, the SMS forwarding service is able to act according to the rules. VAS4SMS is either a terminating network or originating network service. That is, VAS4SMS can be
35、 used by the calling and called subscribers. In general, services offered by the senders VAS4SMS occur prior to the SMS delivering to the recipients operation. ETSI ETSI TS 123 142 V14.0.0 (2017-04)83GPP TS 23.142 version 14.0.0 Release 144.2 Operational requirements 4.2.1 VAS-SMS Provision/withdraw
36、al 4.2.1.1 General The VAS4SMS may be provided after prior arrangement with the service provider. The VAS4SMS may be provided/withdrawn upon the subscribers request or for administrative reasons. 4.2.1.2 Requirements on the originating network side A VAS4SMS application server in the originating net
37、work is required to be under the control of the SMS-SC that is serving a calling subscriber who has activated VAS4SMS. 4.2.1.3 Requirements on the terminating network side A VAS4SMS application server in the terminating network is required to be under the control of the SMS-Route that is serving a c
38、alled subscriber who has activated VAS4SMS. 5 Architecture and Interface 5.1 Architectural requirements The network architecture defined for VAS SMS should have less impact on pre-Rel 8 realization of short message service. The VAS SMS solution shall be able to be deployed independently of the pre-R
39、el 8 services. VAS SMS shall not break pre-Rel 8 services. 5.2 Reference model 5.2.1 Logical network architecture Figure 5.2.1.1 Logical network architecture for VAS4SMS NOTE: Other SMS related elements (MSC/SGSN etc.) behavior is according to 3GPP TS 23.0404. ETSI ETSI TS 123 142 V14.0.0 (2017-04)9
40、3GPP TS 23.142 version 14.0.0 Release 14Editors Notes: the name of the reference point shall be allocated by SA2. 5.2.2 Functional entities The main functional entities involved in the VAS SMS services provisioning depicted in figure 5.2.1.1 are described as follows. 5.2.2.1 VAS AS (VAS SMS Applicat
41、ion Server) The VAS AS is an entity in users HPLMN of which the main requirement with respect to handling of the VAS4SMS messages is the necessary service logic handling. The VAS AS informs the SMS Node whether or not it takes over the handling of a short message. The VAS AS will use a SMS Node for
42、delivery of new or modified messages. The VAS AS informs the SMS Node about the outcome of its short message handling. VAS AS may receive the delivery report of the VAS4SMS messages generated by it from SMS Node If the delivery of SMS is failed, VAS AS may re-send/resubmit the VAS4SMS messages for s
43、everal times, subject to operators configuration 5.2.2.2 SMS node SMS Node may be the integration of standard SMS Functional elements defined in 3GPP TS 23.0404 depending on HPLMN (MO or MT): SMS-IWMSC, SMS-GMSC, SMS-SC or SMS Router. Besides standard SMS functionalities described in TS 23.040 4 the
44、 SMS Node may support: - storage of the user subscription indication for the VAS4SMS - triggering a short message to VAS AS, if a user has VAS4SMS subscription - receiving a short message from VAS AS which is generated based on a previously triggered short message - submitting a short message which
45、comes from VAS AS to the PLMN - receiving a report from PLMN and forwarding it to VAS AS - receiving a report from VAS AS In case the communication between the SMS Node and VAS AS fails, the SMS Node proceeds as if the user hasnt subscribed the VAS4SMS. 5.2.2.3 Service Portal Function (SPF) The SPF
46、provides the means to VAS SMS subscription, activation refers to 3GPP TS 23.204 5. NOTE: Application of VAS services is triggered from either an SMS-SC or an SMS Router. As a consequence, for interworking in the originating side, both originating and terminating VAS services can be applied. For inte
47、rworking in the terminating side the terminating VAS services can be applied subject to an SMS Node being involved in the message flow. ETSI ETSI TS 123 142 V14.0.0 (2017-04)283GPP TS 23.142 version 14.0.0 Release 14Annex A: Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Ol
48、d New 2009-12 CT#46 CP-090824 3GPP TS Presented for approval in CT#46 2.0.0 9.0.0 2009-12 Editorial tidy-up 9.0.0 9.0.1 2011-03 - - - - Update to Rel-10 version (MCC) 9.0.1 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2015-12 Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 CT#75 - - - Update to Rel-14 version (MCC) 13.0.0 14.0.0 ETSI ETSI TS 123 142 V14.0.0 (2017-04)293GPP TS 23.142 version 14.0.0 Release 14History Document history V14.0.0 April 2017 Publication
