ECMA324-2001 Private Intergrated Services Network (PISN) - Specification Functional Model and Information Flows - Short Message Service.pdf

《ECMA324-2001 Private Intergrated Services Network (PISN) - Specification Functional Model and Information Flows - Short Message Service.pdf》由会员分享，可在线阅读，更多相关《ECMA324-2001 Private Intergrated Services Network (PISN) - Specification Functional Model and Information Flows - Short Message Service.pdf（56页珍藏版）》请在麦多课文档分享上搜索。

1、 Standard ECMA-324 June 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) Specification, Functional Model and Information Flows Short Message Service Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.ch

2、 . Standard ECMA-324 June 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) Specification, Functional Model and Information Flows Short Message Service (SMSSD) Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpd

3、eskecma.ch IW ECMA-324.DOC 04-09-02 09,41 . Brief History This Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Private Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to the framework of Int

4、ernational Standards for Open Systems Interconnection as defined by ISO/IEC. It has been produced under ETSI work item DTS/ECMA-00227. This particular Standard specifies the Short Message Service. This Standard is based upon the practical experience of ECMA member companies and the results of their

5、active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardization bodies. It represents a pragmatic and widely based consensus. This ECMA Standard is contributed to ISO/IEC JTC1 under terms of the fast-track procedure, for adoption as a

6、n ISO/IEC International Standard. This ECMA Standard has been adopted by the General Assembly of June 2001. . List of corrected errata for ECMA-324 10 July 2002 Summary Following is a summary of errors detected and corrected in Standard ECMA-324, Private Integrated Services Network (PISN) Specificat

7、ion, Functional Model and Information Flows Short Message Service. Clause 1 To clarify the scope of this Standard, a paragraph is being added in clause 1 and the note is being modified. Original NOTE 1 This service is based on GSM 03.40. The Service Centre functionality described in this Standard is

8、 equal to the functionality of a Service Centre in GSM 03.40. Thus it is only necessary to implement a QSIG interface and some interworking in the Service Centre in order to use it in the herein described network. Corrected This service is based on GSM 03.40. The Service Centre functionality describ

9、ed in this Standard is equal to the functionality of a Service Centre in GSM 03.40. Thus, for interoperability with a GSM network, it is only necessary to implement a QSIG interface. NOTE 1 The interworking with other air interfaces is not precluded, but is outside the scope of this Standard. - i -

10、Table of contents 1 Scope 1 2 Conformance 1 3 References (normative) 1 4 Definitions 2 4.1 External definitions 2 4.2 Other definitions 2 4.2.1 Command 2 4.2.2 Message Centre 2 4.2.3 Message Centre Case 2 4.2.4 ScAlert 2 4.2.5 Service Centre (SC) 3 4.2.6 Short Message (SM) 3 4.2.7 Short Message Wait

11、ing Data 3 4.2.8 Status Report 3 4.2.9 Terminal Case 3 5 Acronyms 3 6 SS-Short Message Service stage 1 specification 4 6.1 Description 4 6.1.1 General description 4 6.1.2 Qualifications on applicability to telecommunications services 4 6.2 Procedures 4 6.2.1 Provision/withdrawal 4 6.2.2 Normal proce

12、dures 4 6.2.3 Exceptional procedures 5 6.3 Interactions with other Supplementary Services/ Additional Network Features 5 6.3.1 Calling Line Identification Presentation (SS-CLIP) 5 6.3.2 Connected Line Identification Presentation (SS-COLP) 5 6.3.3 Calling/Connected Line Identification Restriction (SS

13、-CLIR) 5 6.3.4 Calling Name Identification Presentation (SS-CNIP) 5 6.3.5 Calling/Connected Name Identification Restriction (SS-CNIR) 5 6.3.6 Connected Name Identification Presentation (SS-CONP) 6 6.3.7 Completion of Calls to Busy Subscriber (SS-CCBS) 6 6.3.8 Completion of Calls on No Reply (SS-CCNR

14、) 6 6.3.9 Call Transfer (SS-CT) 6 6.3.10 Call Forwarding Unconditional (SS-CFU) 6 6.3.11 Call Forwarding Busy (SS-CFB) 6 6.3.12 Call Forwarding No Reply (SS-CFNR) 6 6.3.13 Call Deflection (SS-CD) 6 6.3.14 Path Replacement (ANF-PR) 6 - ii - 6.3.15 Call Offer (SS-CO) 6 6.3.16 Call Intrusion (SS-CI) 6

15、6.3.17 Do Not Disturb (SS-DND) 6 6.3.18 Do Not Disturb Override (SS-DNDO) 6 6.3.19 Advice of Charge (SS-AOC) 6 6.3.20 Recall (SS-RE) 6 6.3.21 Call Interception (ANF-CINT) 6 6.3.22 Transit Counter (ANF-TC) 6 6.3.23 Route Restriction Class (ANF-RRC) 6 6.3.24 Message Waiting Indication (SS-MWI) 6 6.3.2

16、5 Wireless Terminal Location Registration (SS-WTLR) 6 6.3.26 Wireless Terminal Mobility Incoming Call (ANF-WTMI) 7 6.3.27 Wireless Terminal Mobility Outgoing Call (ANF-WTMO) 7 6.3.28 Authentication of a WTM user (SS-WTAT) 7 6.3.29 Authentication of the PISN (SS-WTAN) 7 6.3.30 Private User Mobility I

17、ncoming Call (ANF-PUMI) 7 6.3.31 Private User Mobility Outgoing Call (ANF-PUMO) 7 6.3.32 Private User Mobility Registration (SS-PUMR) 7 6.3.33 Common Information (ANF-CMN) 7 6.3.34 Call Priority Interruption (Protection) (SS-CPI(P) 7 6.3.35 Single Step Call Transfer (SS-SSCT) 7 6.3.36 Simple Dialog

18、(SS-SD) 7 6.3.37 Call Identification and Call Linkage (ANF-CIDL) 7 6.4 Interworking considerations 7 6.5 Overall SDL 8 7 Short Message Service stage 2 description 11 7.1 Functional model 11 7.1.1 Functional model description 11 7.1.2 Description of Functional Entities 11 7.1.3 Relationship of functi

19、onal model to Basic Call functional model 13 7.2 Information flows 13 7.2.1 Definition of information flows 13 7.2.2 Information flow sequences 21 7.3 Functional Entity actions 26 7.3.1 Functional Entity actions of FE1 26 7.3.2 Functional Entity actions of FE2 26 7.3.3 Functional Entity actions of F

20、E3 27 7.3.4 Functional Entity actions of FE4 27 7.3.5 Functional Entity actions of FE5 28 7.3.6 Functional Entity actions of FE6 28 7.3.7 Functional Entity actions of FE7 28 7.4 Functional Entity behaviour 28 7.4.1 Behaviour of FE1 29 7.4.2 Behaviour of FE2 30 7.4.3 Behaviour of FE3 30 7.4.4 Behavio

21、ur of FE4 32 - iii - 7.4.5 Behaviour of FE5 35 7.4.6 Behaviour of FE6 35 7.4.7 Behaviour of FE7 36 7.5 Allocation of Functional Entities to physical equipment 38 7.6 Interworking considerations 38 Annex A - Description of PDU elements 39 1 Scope This Standard specifies the Short Message Service (SMS

22、). SMS enables a user to send and receive Short Messages (SMs) to and from another user. This service is based on GSM 03.40. The Service Centre functionality described in this Standard is equal to the functionality of a Service Centre in GSM 03.40. Thus, for interoperability with a GSM network, it i

23、s only necessary to implement a QSIG interface. NOTE 1 The interworking with other air interfaces is not precluded, but is outside the scope of this Standard. NOTE 2 The Short Message Service is a special kind of basic service but is described in this document in the style of a supplementary service

24、. Supplementary service specifications are produced in three stages, according to the method described in ETS 300 387. This Standard contains the stage 1 and stage 2 specifications of SMS. The stage 1 specification (clause 6) specifies the service as seen by users of PISNs. The stage 2 specification

25、 (clause 7) identifies the functional entities involved in the service and the information flows between them. 2 Conformance In order to confirm to this Standard, a stage 3 standard shall specify signalling protocols and equipment behaviour that are capable of being used in a PISN which supports the

26、 service specified in this Standard. This means that, to claim conformance, a stage 3 standard is required to be adequate for the support of those aspects of clause 6 (stage 1) and clause 7 (stage 2) which are relevant to the interface or equipment to which the stage 3 standard applies. 3 References

27、 (normative) The following standards contain provisions which, through references in this text, constitute provisions of this Standard. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent ed

28、itions of the standards indicated below. In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the appropriate ISO/IEC International Standard is given in brackets after the ECMA reference. ECMA-133 Private Integrated Services Network (PISN)

29、- Reference Configuration for PISN Exchanges (PINX) (International Standard ISO/IEC 11579-1) ECMA-142 Private Integrated Services Network (PISN) - Circuit Mode 64kbit/s Bearer Services - Service Description, Functional Capabilities and Information Flows (International Standard ISO/IEC 11574) ECMA-15

30、5 Private Integrated Services Networks - Addressing (International Standard ISO/IEC 11571) ECMA-163 Private Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Name Identification Supplementary Services (International Standard ISO/IEC 13864) ECMA-241 Private

31、Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Message Waiting Indication Supplementary Service (International Standard ISO/IEC 15505) GSM 03.38 Digital cellular telecommunications systems (Phase 2+); Alphabets and language-specific information ETSI TS 1

32、00 901 Digital cellular telecommunications systems (Phase 2+); Technical realization of the Short Message Service (SMS) (GSM 03.40) GSM 03.42 Digital cellular telecommunications systems (Phase 2+); Compression algorithm for text messaging services - 2 - GSM 04.11 Digital cellular telecommunications

33、systems (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface GSM 09.02 Digital cellular telecommunications systems (Phase 2+); Mobile Application Part (MAP) specification ETS 300 387 Private Telecommunication Network (PTN); Method for the specification of bas

34、ic and supplementary services (1994) ITU-T Rec. I.112 Vocabulary of terms for ISDNs (1993) ITU-T Rec. I.210 Principles of telecommunication services supported by an ISDN and the means to describe them (1993) ITU-T Rec. Z.100 Specification and description language (1999) 4 Definitions For the purpose

35、 of this Standard, the following definitions apply. 4.1 External definitions This Standard uses the following terms defined in other documents: - Basic Service (ITU-T Rec. I.210) - Private Integrated services Network eXchange (PINX) (ECMA-133) - Private Integrated Services Network (PISN) (ECMA-133)

36、- Service (ITU-T Rec. I.112)- Signalling (ITU-T Rec. I.112)- Supplementary Service (ITU-T Rec. I.210) - User (ECMA-142)4.2 Other definitions NOTE 3 Further PDU elements are described in annex A. 4.2.1 Command A Short Message data unit which enables the Sending User to request the Service Centre to p

37、erform a certain action, which might be related to a previously sent Short Message from the same Sending User. As far as acknowledging and delivery is concerned, Commands are treated like Short Messages. In the case of certain Commands a Status Report may be sent in response from the SC which contai

38、ns the outcome of the action. 4.2.2 Message Centre The entity that activates or deactivates the Message Waiting Indication against the Receiving User as a result of the storage or retrieval of Short Messages. The Message Centre can serve as a sending, storing and receiving entity for Short Messages

39、on behalf of the Sending and/ or the Receiving User. 4.2.3 Message Centre Case This describes that either the Sending Users terminal or the Receiving Users terminal or both are not able to handle the procedures that are required by the SMS. In this case a Message Centre can act on behalf of these te

40、rminals. The procedures how a user can compose and retrieve SMS related information via a Message Centre are out of the scope of this Standard. 4.2.4 ScAlert Information provided to an SC that has previously initiated unsuccessful Short Message delivery attempt(s) to a specific Receiving User, that

41、the Receiving User is now recognised to have recovered operation or to have memory available again. - 3 - 4.2.5 Service Centre (SC) A function within the network that receives Short Messages from Sending Users. The SC is responsible for the relaying and store-and-forwarding of these Short Messages t

42、o the Receiving Users. If a Receiving User is not able to receive a Short Message, the Service Centre has to store the Short Message and attempt to deliver the Short Message again at a later time. The Service Centre is responsible for a Short Message until it is successfully delivered to the Receivi

43、ng User or the Validity Period expires. Depending on the implementation of Short Message Waiting Data the SC either repeats the delivery attempt automatically in certain intervals or attempts to deliver the Short Message upon reception of a ScAlert information. An SC may receive Commands from the Se

44、nding User and perform the requested actions. Additionally, the Service Centre may provide Status Reports to a Sending User. 4.2.6 Short Message (SM) Data unit containing the Short-Message-Text and additional data necessary for the transmission of the Short-Message-Text from the Sending to the Recei

45、ving User. 4.2.7 Short Message Waiting Data SMS user specific information containing address information of one or more SCs, which unsuccessfully attempted to deliver a Short Message to a Receiving User while the user was not able to receive the Short Message (e.g. did not have memory available or w

46、as not reachable). The Short Message Waiting Data is used to alert the SC when the Receiving User has memory available or is reachable again. 4.2.8 Status Report Information optionally sent from the SC to the Sending User containing the status of a Short Message submitted to a Receiving User or the

47、outcome of a Command submitted to an SC. A Status Report for a Command or a Short Message is sent from the SC to the Sending User if it has been requested in the Short Message or Command. 4.2.9 Terminal Case This describes that either the Sending Users terminal or the Receiving Users terminal or bot

48、h are able to handle the procedures that are required by the SMS. 5 Acronyms ANF Additional Network Feature FE Functional Entity PINX Private Integrated services Network eXchange PISN Private Integrated Services Network PNP Private Numbering Plan SC Service Centre SCTS Service-Centre-Time-Stamp SDL

49、Specification and Description Language SM Short Message SMS Short Message Service SMSC Short Message Service Centre SMWD Short Message Waiting Data VP Validity Period - 4 - 6 SS-Short Message Service stage 1 specification 6.1 Description 6.1.1 General description The Short Message Service provides a means of sending messages of limited size point-to-point between network users. The provision of SMS makes use of a Service Centre which acts as a store-and-forward centre for Short Messages, i.e. all Short Messages are sent using a Service Centre which receives Short Messages fr