TIA EIA IS-658-1-1999 Data Services Interworking Function Interface for Wideband Spread Spectrum Systems (Addendum 1 to TIA EIA IS-658).pdf

《TIA EIA IS-658-1-1999 Data Services Interworking Function Interface for Wideband Spread Spectrum Systems (Addendum 1 to TIA EIA IS-658).pdf》由会员分享，可在线阅读，更多相关《TIA EIA IS-658-1-1999 Data Services Interworking Function Interface for Wideband Spread Spectrum Systems (Addendum 1 to TIA EIA IS-658).pdf（4页珍藏版）》请在麦多课文档分享上搜索。

1、TIA/EIA INTERIM STANDARD Data Services Interworking Function Interface for Wideband Spread Spectrum Systems Addendum 1 TIA/EIA/IS-658=1 APRIL 1999 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Electronic Industrias Alliance NOTICE TiA/EiA Enginering Standards and Publications are designed to serve the pub

2、lic interest through eliminating misunderstandings between manufhcturers and purchasers, facilitating interchangeability and improvement of products, and assisting &e purchaser in selecting and obtaining with minimum delay the proper product for his particular need. J35stence of such Standards and P

3、ublications shali not in any respect preclude any member or nonmember of TIA/EIA from manufacftinng or selling products not conforming to such Standards and hblications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TiAEIA members, whethe

4、r the standard is to be used either domestically or internationally. Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Iostitute (ANSI) patent policy. By such action, TLAfELA does not assume any liabiiity to any patent owner, nor does it assume any

5、obligation whatever to parties adopting the Standard or Publication. “WEIA Interim Standards contain information deemed to be of technical value to the industry, and *e published at the request of the originating Committee without riecessanl * y following the rigorous public review and resolution of

6、 comments which is a procedural part of the development of a -IA Standard. TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decGion made on whether to proceed to develop a TIA/EIA Standard on this subject. TUVEIA Interim Standards must be cancelled b

7、y the Committee and removed from the TLA/ELA Standards Catalog before the end of their third year of existence. Publication of tfiis TIA/EIA Interim Standard for trist use and comment has been approved by the Telecommunications Industry Associition. Distribution of this TLA/EIA Interim Standard for

8、comment shaii not continue beyond 36 months from the date of publication. It is expected that foliowing this 36 month period, this TIA/EIA Interim Standard, revised as necessary, WU be submtted to the American National Siandards Institute for approval as an American National Standard. Suggestions fo

9、r revision should be directed to: Standards & Technology Department, Telecommunications Industry Association, 2500 Wilson Boulevard, Arlington, VA 22201. (From Project No. 4374, formulated under the cognizance of the TIA TR45.5 Subcommittee on Spread Spectrum Digital Techwlogy.) Published by TELECOM

10、MUNICATIONS INDUSTRY ASSOCIATION 1999 Standards & Technology Department 2500 Wilson Boulevard Arlington, VA 22201 PRICE: Please refer to current Catalog of EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854- 7179)

11、 International (303-397-7956) Ail rights reserved Printed in U.S.A. 4 STD-EIA TIA/IS-b$B-L-ENGL 1999 = 3234600 Ob37409 T38 I TIA/EIA/IS-658- 1 i 1 INTRODUCTION 2 3 4 5 6 section following figure 4.2.9-3. 7 This addendum is being published for the purpose of extending the ability to perform interface

12、 status exchange at times other than call setup. It is intended that section 4.2.6 in this addendum replace section 4.2.6 in TIA/EIA/IS-658. Also, in section 4.2.9 in this addendum, a new reason code, 0x02, is added to the values The remainder of TIA/EIA/IS-658 is unchanged. 8 2 NORMATIVECHANGES 9 4

13、.2.6 Optional Interface Status Exchange 10 11 12 Either the BS/MSC or the IWF may initiate an exchange of interface status information during FR SVC establishment (see 4.2.1 or 4.2.3) or at any other time. This involves an exchange of one or more INTERFACE-STATUS segments. 13 During FR SVC establish

14、ment, if the receiving entity responds to a SETUP message with a 14 message including the user-user information element with one or more 15 INTERFACE-STATUS segments, these segments shall refer to the same interfaces as the 16 INTERFACE-STATUS segments in the SETUP message, and they shall be in the

15、same 17 order as the INTERFACE-STATUS segments in the SETUP message. I8 19 20 21 22 23 24 25 26 27 28 Either the BS/MSC or IWF may initiate an exchange of interface status information at any time other than FR SVC establishment by sending a SETUP message in accordance with T1.617. The SETUP message

16、shall include a REASON segment with the REASON-CODE field set to 0x02 and one or more INTERFACE-STATUS segments. The receiving entity should respond to the SETUP message with a RELEASE COMPLETE message that includes a REASON segment with REASON-CODE field set to Ox02 and includes one or more INTEFSA

17、CE-STATUS segments. These INTERFACE-STATUS segments shall refer to the same interfaces as the INTERFACE-STATUS segments in the SETUP message, and they shall be in the same order as the INTERFACE-STATUS segments in the SETUP message. The Call Reference information element in the SETUP and RELEASE COM

18、PLETE messages shall be sent with a global call reference value. 29 This standard does not address the use of the information contained in the 30 INTERFACE-STATUS segments by either the BS/MSC or the IWF. 31 4.2.7 Initialization 32 . 33 4.2.8 Optional Packet Data Service Mobility Function 34 1 TIA/E

19、IA/IS-658- 1 I 4.2.9 Use of the User-User Information Element Octet 2 2 3 VERSION = Ox01 Octet 1 1 SEGMENT-TYPE = REASON (0x03) I 4 5 6 7 8 9 10 11 12 Figure 4.2.9-3. REASON Segment Format REASON-CODE has value: 0 0 Ox00 to request/inform-of active Link Layer connection closure, Ox0 1 to request deactivation of active Link Layer connection, or 0x02 to request/respond-to exchange of interface status information. All other values are reserved. 2