1、TIA STANDARD Short Messaging Services (Supercedes TIA-637-B) AUGUST 2004 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Tdecornmunications Industry Association represents lhe cornmunicalions seclor of Elsctronir Industries Alliar-ce TIA Engineering Standards and Publications are designed to serve the p
2、ublic interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Public
3、ations shall not in any respect preclude any member or non-member of TIA fi-om manufacturing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use by non- TIA members, either domestically or internationally. TIA DOCUMENTS
4、TIA Documents contain information deemed to be of technical value to the industry, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of a American National St
5、andard (ANS). Further details of the development process are available in the TIA Engineering Manual, located at htrp :imv.tiaonhe, sfbzistandagdsis/en manaall. ci311 TIA Documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on whether to reaffirm, revise,
6、 withdraw, or proceed to develop an American National Standard on this subject. Suggestions for revision should be directed to: Standards anrUaI.c-frn. TIA?s function is to administer the process, but not the content, of document preparation in accordance with the Manual and, when appropriate, the p
7、olicies and procedures of the American National Standards Institute (?ANSI?). TIA does not evaluate, test, verify or investigate the information, accuracy, soundness, or credibility of the contents of the Document. In publishing the Document, TIA disclaims any undertaking to perform any duty owed to
8、 or for anyone. If the Document is identified or marked as a project number (PN) document, or as a standards proposal (SP) document, persons or parties reading or in any way interested in the Document are cautioned that: (a) the Document is a proposal; (b) there is no assurance that the Document wil
9、l be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (?I
10、PR?), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIA?s attention, a statement from the holder thereof is requested,
11、all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties
12、involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. TIA does not
13、 enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION
14、, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR INFRINGEMENT OF ANY THIRD PARTY?S INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENT?S CO
15、MPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON- TIA S
16、HALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION,
17、OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS W
18、OULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA- 63 7 - C PREFACE These technical requirements form a standard for a Short Message Service (SMS), providing delivery of text and numeric information for paging, messaging, and voice mail notification. This standard includes Service Option 6
19、and Service Option 14 (as defined in 15), which support delivery of short messages on Traffic Channels. Service Option 6 and Service Option 14 conform to the general requirements for service options specified in lo. A mobile station can obtain Short Message Service operating in either the analog or
20、the spread spectrum (CDMA) mode when it conforms to this standard. This standard does not address the quality or reliability of Short Message Service, nor does it cover equipment performance or measurement procedures. SECTION SUMMARY Introduction. This section defines the terms, references, protocol
21、s and network reference model used in this document. SMS Relay Layer. This section defines the requirements for the lower layer of the SMS bearer service protocols. The SMS Relay Layer provides the interface between the Transport Layer and the Link Layer used for message transmission. SMS Transport
22、Layer. This section defines the requirements for the upper layer of the SMS bearer service protocols. The SMS Transport Layer manages the end- to-end delivery of messages. SMS Teleservice Layer. This section defines the requirements for the SMS Teleservice Layer, which provides application-level dat
23、a formats and procedures. i TIA- 63 7 - C NOTES 1. The following verbal forms are used: “Shall” and “shall not” identify requirements to be followed strictly to conform to the standard and from which no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is r
24、ecommended as particularly suitable, without mentioning or excluding others; that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. “May” and “need not” indicate a course o
25、f action permissible within the limits of the standard. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical, or causal. Footnotes appear at various points in this specification to elaborate and to further clarify items discussed in the body of the spe
26、cification. Unless indicated otherwise, this document presents numbers in decimal form. Binary numbers are distinguished in the text by the use of single quotation marks. In some tables, binary values may appear without single quotation marks if table notation clearly specifies that values are binar
27、y. The character k is used to represent a bit of unspecified value. For example xxxO0010 represents any however, these requirements also apply to a Um Interface Link Layer that is compliant with 22 (where appropriate). On the N Interface, the SMS Relay Layer supports the SMS Transport Layer by provi
28、ding the interface to the network protocols needed to carry SMS data between the message center and base stations. For the general N Interface, the SMS Relay Layer requirements in this standard are limited to the requirements for the Relay Layer interface to the Transport Layer. Specific requirement
29、s are given for operation with an N Interface that is part of a network compliant with 8. 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 2.2 Overview 2.2.1 Model of Operation 2.2.1.1 Um Interface In this standard, the Um reference point is the CDMA wireless syste
30、m as described in lo. The dual-mode CDMA wireless system provides analog and digital mobile telephone service using the wireless mobile telephone frequency bands. Requirements for SMS message delivery in the analog mode are found in lo. The CDMA system provides the functions necessary for a mobile s
31、tation to acquire CDMA system timing and the overhead information needed for access to system functions. A CDMA mobile station that is fully initialized and is capable of providing access to system functions can operate in any of the following three states that are defined in lo: 0 Mobile Station Id
32、le State 0 System Access State 0 The SMS Relay Layer can deliver messages to mobile stations in any of these states. The Relay Layer is also capable of using call control signaling to direct mobile stations to change states as necessary in order to deliver SMS messages. Mobile Station Control on the
33、 Traffik Channel State 2- 1 TIA- 63 7 - C 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 2.2.1.2 N (Intersystem) Interface In this standard, the N reference point is assumed to be an intersystem network link with connectivity to the message center. Intersystem links can use a variety of public and
34、private protocols, one example of which is defined in 8. SMS protocols and message formats on intersystem links may differ from those used on the CDMA air interface. The N Interface Relay Layer is responsible for formatting and parsing SMS messages as necessary when transmitting and receiving messag
35、es on the intersystem links. 2.2.2 Relay Layer Functions The Relay Layer performs the following functions: Accepting Transport Layer messages and delivering them to the next indicated relay point or end point. Providing error indications to the Transport Layer when messages cannot be delivered to th
36、e next relay point or end point. Receiving messages and forwarding them to the Transport Layer. Interfacing to and controlling the Link Layer used for message relay. Formatting messages according to the SMS standards and related message standards, as required by the Link Layer or peer SMS layers. 2-
37、2 TIA- 63 7 - C 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 2.2.3 Service Description 2.2.3.1 Service Primitives Service primitives represent a logical exchange of information between layers. The types of primitives used in the Relay Layer are shown in Figure 2.2.3.1-1. t Transport Layer Confirm I nd
38、cat io n I Relay Layer Figure 2.2.3.1-1. Primitive Types The Request primitive type is used by the Transport Layer to request a service from the Relay Layer. The Confirm primitive type is used by the Relay Layer to report a consequence of the Request primitive type. The Indication primitive type is
39、used by the Relay Layer to provide information to the Transport Layer. The Response primitive type is used by the Transport Layer to request a service from the Relay Layer as a consequence of the Indication primitive type. The following tables contain some examples of the primitive definitions. The
40、conventions used for service interface primitives are shown in Table 2.2.3.1-1. 2-3 TIA- 63 7 - C Primitive Type Request 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Source Destination Purpose Service user Service provider Request a service, resource, etc. Table 2.2.3.1-1. Um Interface Primitive Types
41、Confin Indication Service provider Service user Response to a Request primitive Service provider Service user Indicates that data or an event for the service user has occurred Response Service user Service provider Acknowledgment of an Indication Note that every Request primitive has a corresponding
42、 Confin primitive, and every Indication primitive has a corresponding Response primitive. The invocation of service primitives is noted as follows: RX.Primitive_Type(parameters) where RX, Primitive-Type and parameters are defined in Table 2.2.3.1-2. Rx Primitive-Type Parameters An abbreviation for t
43、he service provider entity (e.g., RL-BCDATA for Relay Layer Broadcast Data). The specific Primitive Type as defined in Table 2.2.3.1-1 (e.g., Request) An (optional) list of parameters for the primitive (e.g., Address) For example, a request to transfer broadcast SMS messages between the Transport La
44、yer and the Relay Layer uses the RL-BCDATA primitive. The Relay Layer passes the Transport Layer Message text, and the destination broadcast address parameters as follows: RGBCDATA.Request(Transport Layer Message, Broadcast Address) Primitives and parameters for the Um Interface Relay Layer are summ
45、arized in Table 2.2.3.1.1-1. 2-4 TIA- 63 7 - C RL-D ATA RL-BCDATA RL-ERROR RL-CONTROL I 2.2.3.1.1 Um Interface Primitives 2 3 Interface. Table 2.2.3.1.1-1 summarizes the primitives supported by the Relay Layer for the Um 4 5 Table 2.2.3.1.1-1. Relay Layer Service Primitives, Um Interface Request Con
46、firm Indication Response X X X X X X X X 6 SMS Entity 7 8 9 10 11 12 13 Primitive Is.pe Address 14 Mobile 15 Request Originating mobile station identifier Indication None 16 Base Name I Is.pe Request Destination mobile station identifier Indication Originating mobile station identifier Parameters Tr
47、ansport Layer Message, Address, Authentication, Confirm Request Transport Layer Message, Broadcast Address Error Type The RL-DATA primitive is used to transfer point-to-point SMS messages and SMS acknowledgments between the Transport Layer and the Relay Layer. The parameters of the RL-DATA primitive
48、 are the Transport Layer message text, authentication data, confirmation request and the mobile station identifier, which may be a source or destination address, according to the direction of transmission. For the mobile station and base station Um Interface Relay Layer, the parameters of the RL-DAT
49、A primitive are summarized in Table 2.2.3.1.1-2. Table 2.2.3.1.1-2. RL-DATA Primitive Parameters, Um Interface I Response I Originating mobile station identifier Auth I Req Xtx 17 18 In the mobile station, the Authentication parameter of the RL-DATA.Request primitive contains the authentication digits used in forming the AUTHR field that is sent in all Datu 2-5 TIA- 63 7 - C 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Burst Messages carrying SMS messages, as required in 3.3.3 and in 9. In the base station, the Authentication parameter of
