ANSI TIA-664.601-B-2007 Wireless Features Description Short Message Delivery-Point-Point Bearer Service.pdf

1、 TIA-664.601-B (Revision of TIA-664.601-A) October 2007Wireless Features Description: Short Message Delivery-Point-Point Bearer Service ANSI/TIA-664.601-B-2007 APPROVED: OCTOBER 8, 2007 REAFFIRMED: JANUARY 31, 2013 NOTICE TIA Engineering Standards and Publications are designed to serve the public in

2、terest 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 Standards and

3、Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically

4、 or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or

5、Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory li

6、mitations before its use. (From Project No. SP-3-4652.601-RV2-RF1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modifie

7、d 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 (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for I

8、PR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire

9、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 involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does

10、 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. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulat

11、ion, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligati

12、on to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall a

13、pply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA doe

14、s 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, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FIT

15、NESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTEN

16、TS COMPLIANCE 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. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM

17、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, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT

18、 (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 WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-664.601-B 1 2 3 4

19、5 6 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 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 601-i Contents Wireless Features Description: Short Message DeliveryPoint-to-Point Bearer Service Contents Revision Historyii 1 Short Mes

20、sage DeliveryPoint-to-Point Bearer Service (SMDPP) 1 1.1 Normal Procedures with Successful Outcome3 1.2 Exception Procedures or Unsuccessful Outcome .4 1.3 Alternative Procedures .5 1.4 Interactions with Other Wireless Services5 TIA-664.601-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

21、23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Revision History 601-ii Revision History Revision Date Remarks IS-53, Revision 0 August 1991 Initial publication IS-53, Revision A May 1995 Updated publication ANSI/TIA/EIA-664, Revision

22、 0 June 1996 Initial ANSI publication ANSI/TIA/EIA/664-601-A July 2000 Updated ANSI publication TIA-664.601-B September 2007 Updated publication TIA-664.601-B 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 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

23、51 52 53 54 55 56 57 58 59 60 601-1 Short Message DeliveryPoint-to-Point (SMD-PP) 1 Short Message DeliveryPoint-to-Point Bearer Service (SMDPP) Short Message DeliveryPoint-to-Point (SMDPP) provides bearer service mechanisms for delivering a short message as a packet of data between two service users

24、, known as Short Message Entities (SMEs). SMEs are SMS endpoints capable of composing or disposing of a short message. One or both of the service users may be a mobile station. The data packets are transferred transparently between two service users. The network or destination application generates

25、negative acknowledgments when it is unable to deliver the message as desired. The destination application may respond with an automatic acknowledgment and may include application generated or user provided information. The length of the Bearer Data may be up to 200 octets. Implementations and servic

26、e providers may further restrict this length. SMD does not provide packet fragmentation or reassembly services by the network. (Teleservices may support fragmentation and reassembly using messages sent independently on the network.) Message integrity should be maintained over all interfaces includin

27、g the Base Station to Mobile Station radio link (air or Uminterface). The SMDPP service attempts to deliver a message to an MS based SME whenever the MS is registered even when the MS is engaged in a voice or data call. Each SME has a network address. A SME may have multiple network addresses. MS ba

28、sed SMEs may roam throughout the network. Messages to an MS based SME are usually addressed to his or her Message Center (MC). This address is translated into a routing address for the purposes of message delivery. The SMDPP message consists of a packet with the following attributes: Bearer Data The

29、 Bearer Data attribute is of variable length up to 200 octets in length. Implementations and service providers may further restrict this length. The Bearer Data attribute is conveyed transparently by the intervening network. This attribute includes a length indication. The Bearer Data is encoded and

30、 interpreted by the teleservice. Message Type The Message Type attribute indicates the type of the message, and may be specified as: a. Request (an SMS message). b. Acknowledgment (a message sent to report errors or confirm delivery in response to an SMS message). Charge Indicator optional Message m

31、ay indicate charging options for usage metering separation. Cause Code The Cause Code is used in acknowledgments to convey the reason for not being able to complete a particular message delivery. (See MAP for the code values.) TIA-664.601-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

32、 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Short Message DeliveryPoint-to-Point (SMD-PP) 601-2 Originating Address The Originating Address is the network address identifying the node sending the SMD message. It is used to deliver a

33、 return acknowledgment message. This may not be the original message sender, when store and forward services are provided. This attribute may be physically absent, if it can be derived from other attributes. The Originating Address allows E.164, X.121, internet IP, or MDN address formats. MSs are us

34、ually addressed by their E.164 Mobile Directory Number, although mapping services may allow addresses on interconnected networks. Destination Address The Destination Address is the network address used for delivery of the message. This attribute may be physically absent, if it can be derived from ot

35、her attributes. Mobile subscribers may be assigned a temporary routing address to allow delivery of messages while roaming anywhere in the network. This address is not generally known, accessible, or available. The Destination Address allows E.164, X.121, internet IP, or MDN address formats. MSs are

36、 normally addressed by their E.164 Mobile Directory Number, although mapping services may allow aliased addresses on interconnected networks. Teleservice Identifier The Teleservice Identifier selects the application and teleservice that is to use the Bearer Data. Teleservice Identifiers should be st

37、andardized (or reserved by the standard). Carrier specific applications may be assigned a range of the identifiers. A Teleservice Identifier should be reserved for the general bearer service maintenance. This Teleservice Identifier may be used when reporting message routing problems. The Teleservice

38、 Identifier should be 16 bits. Original Originating Address The Original Originating Address is the network address initiating the message. This attribute need only be present if the Originating Address is different than the Original Originating Address. This attribute may be physically absent, if i

39、t can be derived from other attributes. The Original Originating Address is in any allowable Originating Address format. Original Destination Address The Original Destination Address is the destination network address in the original message. This attribute may be physically absent, if it can be der

40、ived from other attributes. The Original Destination Address is in any allowable Destination Address format. TIA-664.601-B 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 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 601-3

41、Short Message DeliveryPoint-to-Point (SMD-PP) Original Originating Subaddress Optional The Original Originating Subaddress is an address within an addressable message origination node to identify a particular SME. Original Destination Subaddress Optional The Original Destination Subaddress is an add

42、ress within an addressable message destination node to identify a particular SME. Mobile Identification Number Optional The Mobile Identification Number is primarily used to address messages to MS-based SMEs. Electronic Serial Number Optional The Electronic Serial Number is primarily used to address

43、 messages to MS-based SMEs. Applicability to Telecommunications Services This bearer service may be used by all Short Message Service teleservices. 1.1 Normal Procedures with Successful Outcome Authorization SMD-PP may be provided after prearrangement with the service provider. Authorization has the

44、 following options: a. Accept non-chargeable network originated terminating messages only. b. Accept all terminating messages. c. Accept all terminating and originating messages. Additionally the maximum acceptable Bearer Data size may be specified as any value up to 200 octets. The service provider

45、 may offer SMDPP in conjunction with voice and data services, or may offer SMDPP as a stand-alone service. Deauthorization SMDPP may be withdrawn at the subscribers request or for administrative reasons. Registration SMDPP has no registration. TIA-664.601-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

46、18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Short Message DeliveryPoint-to-Point (SMD-PP) 601-4 Deregistration SMDPP has no deregistration. Activation SMDPP shall be activated upon authorization. Deactivation SMDPP

47、shall be deactivated upon deauthorization. Invocation SMDPP is invoked with an SMDPP packet issued by a Short Message Entity (SME). The SME may be based in a mobile station, in any other network element, or outside of the wireless network. Normal Operation with Successful Outcome If the SMDPP messag

48、e is accepted, the SMDPP message is routed toward the indicated destination. There may be intermediate processing nodes, routers, bridges, or gateways to change address formats and network carriage or to provide additional services, such as store and forward. If the SMDPP message is delivered to its

49、 destination, it is the responsibility of the destination application or teleservice to send an acknowledgment message toward the message originator. This acknowledgment message may include application specific information. Call Detail Record The system should record the following information: a. Forward (network toward destination MS) chargeable data packet usage. b. Forward chargeable acknowledgment packet usage. c. Forward non-chargeable data packet usage. d. Reverse (originating MS toward network) data packet usage. e. Reverse acknowledgment packet u