1、 ANSI/TIA-136-750-1999 APPROVED: NOVEMBER 29, 1999 REAFFIRMED: JUNE 19, 2003 REAFFIRMED: MAY 28, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-750 November 1999TDMA Cellular/ PCS General UDP Transport Service (GUTS) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest
2、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 Publica
3、tions 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 or int
4、ernationally. 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 Publica
5、tion. 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 limitatio
6、ns before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. 3-4027.750-RF2-WD, formulated under the cognizance of the TIA TR-45 Mobile (b) there is n
7、o 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, 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
8、 intellectual property rights (“IPR”), 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 TIAs attention, a statement from t
9、he 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 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
10、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 not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Docume
11、nt or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such
12、 reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Refer
13、ence; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO s
14、hall 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 does not certify, inspect, test or otherwise investigate products, designs or services or any claims
15、 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 FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEM
16、ENT 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 CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF
17、 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 OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL
18、 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 (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SU
19、CH 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. TINEIA-1 36-750 Contents 1 . 2 . 3 . 4 . 5 . Purpose and Scope . 1 Procedures 4 Message Set 7 3.1 GUTS Data 8 Informati
20、on Element Description 9 4.1 Message Type 9 4.2 Protocol Discriminator . 9 4.3 UDP Header . 9 4.4 User Data . 10 Change History for TIA/EIA.136.750 . 11 I TINEIA-1 36-750 List of Figures Figure 1 Figure 2 Figure 3 Figure 4 HDML/WAP Browser 2 GUTS Example Protocol Stack . 3 Mapping of a mobile-termin
21、ated GUTS Data Message from R-DATA and SMDPP 5 Mapping of a mobile-originated GUTS Data Message into R-DATA and SMDPP 6 II TINEIA-1 36-750 1 1. Purpose and Scope 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 The General UDP Transport Service,
22、GUTS, is a general-purpose application data delivery service. The General UDP Transport Service increases flexibility of adding new value-added features, and creates an open platform for the creation of both consumer and corporate information services via wireless Internet and intranet access. GUTS
23、utilizes the Internet Standard User Datagram Protocol (UDP) to specify the intended application, or port. The General UDP Transport Service provides a new teleservice specially designed to require minimum protocol overhead allowing more room for the data payload (i.e., GUTS is not based on the Short
24、 Messaging Service). The General UDP Transport Service supports both mobile-terminated (point-to-point and broadcast), as well as mobile-originated services. The General UDP Transport Service assumes no specific encoding of the application datagrams, and transparently passes the data to the applicat
25、ion specified by the destination port. GUTS may also be used to integrate many current TIAEIA-136 features into the common user interface of a browser. For example, GUTS may be used to support one-way and mobile-originated “Cellular Messaging Teleservice (CMT)“-like messaging and other services asso
26、ciated with the traditional CMT service (e.g., bulk messaging), or “broadcast“ services. In effect, GUTS combined with a browser application can provide a common and consistent user interface for both enhanced and existing TIAEIA-136 services. The General UDP Transport Service can carry essentially
27、any higher layer application protocol. For mobile-terminated services, the messages defined in the General UDP Transport Service carry UDP datagrams from an application in the network (in this architecture, the Application Server or Gateway), to the appropriate application in the mobile station (for
28、 example, an HDML Browser). Similarly, for mobile-originated services, the messages defined in the General UDP Transport Service carry UDP datagrams from an application in the mobile station (for example, the HDML Browser), to an application in the network (the Application Server or Gateway). These
29、applications are defined by appropriate UDP ports. Port assignments are necessary for the UDP portion of the protocol. These port assignments may be outside of the UDP Well-Known port assignments, as it can be envisioned that existing applications defined in the Well-Known port assignments may be us
30、ed in the General UDP Transport Service. The port assignments inform the receiving end of the UDP datagram which application the data should be delivered to. On a mobile-terminated GUTS Data message, the mobile station delivers the datagram to the GUTS application. The Destination Port specifies the
31、 particular application within GUTS for which the UDP Data should be delivered. For example, if the Destination Port specifies the port for the HDML/WAP Browser, then the GUTS shall deliver the data to the HDML/WAP Browser, as shown below: 1 TINEIA-1 36-750 2 3 Figure 1 HDMLNVAP Browser HDMLNVAP Bro
32、wser Destination Pori Source Pori for for Datagram Datagram Deliver Submit Layer 3 (R-DATA) Layers 1 & 2 Mobile Station The following services require port assignments for Service: the General UDP Transport HDML/HDTP or WAP protocol Text Other port assignments shall be made as additional application
33、s are defined. 2 TINEIA-1 36-750 Application1 UI GUTS TSAR R-DATA Layers i &2 The following shows an example of the protocol stack throughout the network: Figure 2 GUTS Example Protocol Stack Application SMDPP SMDPP TINEIA-41 TINEIA-41 R-DATA S Internet (Application) Note: TSAR is the Telesewice Seg
34、mentation and Reassembly (see TIAEIA-136-620). It provides segmentation and re-assembly services, and is optional for GUTS. 3 TINEIA-1 36-750 1 2. 10 11 Procedu res General UDP Transport Service messages are sent over the TIAEIA-41 network in the SMSBearer Data portion of an SMS-DeliveryPoint-to-Poi
35、nt (SMDPP). The Teleservice Server encapsulates the incoming application data from an Application Server into the General UDP Transport Service message format, and packages it into an TIAEIA-41 SMDPP. The Teleservice Server routes the SMDPP to the serving MSC using standard TIAEIA- 41 SMS delivery p
36、rocedures. The MSC shall perform the interworking from the TIAEIA-41 SMDPP to the layer 3 message R-DATA message. The following show the mapping of mobile-terminated and mobile-originated General UDP Transport Service messages into R-Data and TIAEIA-41 SMDPP: 4 TINEIA-1 36-750 Protocol Discriminator
37、 Message Type UDP Header UDP Data 1 2 i 1 M I M I I I Figure 3 Mapping of a mobile-terminated GUTS Data Messagefrom R-DATA and SMDPP GUTS Data R-DATA Protocol (2 bits) Message Type R-Transaction (8 bits) (16 - * bits) R-DATA Unit /I (20 - * bits) Address (20 - * bits) HLPI (8 bits) User Destination
38、Su baddress (20 - 180 bits) Higher Layer PDU (8 * (N-1) bits User Originating User Originating Su baddress (20 - 180 bits) User Originating (8 bits) I API I O SMDPP 5 TINEIA-1 36-750 SMS-Notification Indicator 1 2 o Figure 4 Mapping of a mobile-originated GUTS Data Message into R-DATA and SMDPP SMS-
39、Orig Origination Address GUTS Data O R-DATA Unit I SMS-Orig Originating Subaddress Length (8 bits) O (8 bits) HLPI I Higher Layer P D U (8 * (N-1) bits . In the above mapping of R-DATA to SMDPP, the Teleservice Server Address is a required information element in the R-DATA. The mobile station shall
40、use the stored Teleservice Server Address for the GUTS HLPI (for example, see TIAEIA-136-720). Note: R = Required information in an optional field. TINEIA-41 SMDPP I SMS-Bearer Data I SMSTID M ST: 1: SMS-Destination Io SMS-Message I Destination Address Destination Subaddress I SMS-Originating Addres
41、s I o 6 TINEIA-1 36-750 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 3. Message Set This section describes the General UDP Transport Service messages. These messages are transported on the air interface via the layer 3 R-DATA message, more specifically wi
42、thin the R-DATA Unit Information Element. In all messages below, the information element at the top of the tables shall be regarded as the first when delivered into layer 3. In the information elements the most significant bit (the leftmost bit in the tables) is the first bit when delivered to layer
43、 3 when sending a message. The information element descriptions are found in Section 4 in alphabetical order. The following coding rules apply to this section: A General UDP Transport Service message shall be padded with trailing O (zeros) as necessary to the nearest octet boundary. In the interest
44、of backward compatibility, a received General UDP Transport Service message shall still be accepted by GUTS if the message length exceeds the maximum length the receiving end is capable of processing. General UDP Transport Service information elements defined in later revisions of the standard may b
45、e discarded by earlier revision mobiles. On a DCCH, if the maximum length of a padded mobile-originated General UDP Transport Service message together with the layer 3 overhead (see TIAEIA- 136-123) exceeds the R-DATA Message Length in TIAEIA-136-123 (see TIAEIA-136-910 for further information on mo
46、bile-originated and mobile-terminated message length limitation), then Segmentation and Reassembly shall be applied to the GUTS message (see TIAEIA-136-620). Unless otherwise specified, a particular information element is present only once in a given message. Whether an information element is mandat
47、ory or optional in a message is identified by an “M“ or “O“ respectively in the column “Type“ of the table describing a message. All the mandatory information elements within a message shall be delivered to layer 3 in the order that they appear in the table provided for each message. All specified l
48、engths are in bits unless otherwise noted. A “*“ symbol in the length column of a message means that the maximum length of the associated information element is only limited by the maximum message length. 7 TINEIA-1 36-750 Information Element Protocol Discriminator i 3.1 PV Type Length (Bits) PV 1 T
49、IA/EIA-136-A, M 2 GUTS Data The GUTS Data message is both a mobile-terminated and mobile-originated message used for delivery of a datagram to/from a mobile station. The user data in the datagram is binary data, which may have specific application encoding (i.e., HDMWHDTP, WAP protocol, or text) that is transparent to the teleservice. 6 The format of the GUTS Data message is as follows: Message Type I TIA/EIA-136-A, I 6 PV 1 UDP Header I TIA/EIA-136-A, I 64 PV 1 User Data I TIA/EIA-136-A, I O-* PV 1 8 TINEIA-1 36-750 Value O0 O000 3 Function GUTS Data 4. Informati
