ANSI TIA EIA-732-620-2001 Cellular Digital Packet Data (CDPD) System Specification Message Handling Service.pdf

1、 TIA/EIA STANDARD Cellular Digital Packet Data (CDPD) System Specification Message Handling Service TIA/EIA-732-620 (Upgrade of TIA/EIA/IS-732-620) JULY 2001 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of ANSI/TIA/EIA-732-6

2、20-2001 Approved: June 8, 2001 TIA/EIA-732-620 NOTICE TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the pu

3、rchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications

4、, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA/EIA members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by TIA/EIA in accordance with the American National Standar

5、ds Institute (ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all appli

6、cable 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 limitations before its use. (From Standards Proposal No. 4033-620-UG, formulated under the cognizance of the TIA

7、TR-45.6 Subcommittee on Adjunct Data Packet Wireless Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2001 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 PRICE: Please refer to current Catalog of EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEE

8、RING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) All rights reserved Printed in U.S.A. PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the TIA and may not be reproduced without permission. Organizations may obtain perm

9、ission to reproduce a limited number of copies through entering into a license agreement. For information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 620iTIA/EIA-732-620123456789101112131

10、415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Contents1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620-12 Message Handling System (MHS). . . . . . . . . . . . . . . . . . . . . . . . . .

11、. . . . 620-23 MHS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620-44 Conformance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620-54.1 Use of Directory by UA and MTA . . . . . . . . . . . . . . . . . . . . . .

12、. . . . . . . . . . . . . . . . . . . . . . .620-54.2 Security Class Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .620-65 CDPD Use of IPM and External Body Parts . . . . . . . . . . . . . . . . . . . . 620-65.1 MHS Interpersonal Messagin

13、g Service (IPMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .620-85.2 Externally Defined Body Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .620-95.3 Extended Body Part Object Identifiers . . . . . . . . . . . . . . . . . .

14、. . . . . . . . . . . . . . . . . . . . . .620-106 Message Transfer System Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620-11TIA/EIA-732-620620ii123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960620iii12345678910111213

15、1415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960TIA/EIA-732-620PART 620 Message Handling ServiceForewordThis foreword is not part of the StandardThis Standard has been produced by the TR-45.6 Subcommittee of the TIA/EIA/TR-45 Committee.This document cont

16、ains significant portions of material originally submitted by the Cellular Digital Packet Data Forum Inc.This document set constitutes the Cellular Digital Packet Data (CDPD) System Specification. CDPD is a technology intended to provide packet data networking services to mobile hosts. The media use

17、d to provide these services consists of radio channels typically used for Advanced Mobile Phone System (AMPS) cellular service.Document StructureThis Standard is published as a series of Parts. Each Part contains information pertaining to one aspect of the system.The functional structure of the Cell

18、ular Digital Packet Data System Specification is as follows:a71 Introduction and OverviewTIA/EIA-732-620 Message Handling Service620iv123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960This document provides an overview of the CDPD Network

19、and serves as a guide to the remainder of the system specification for specific detailed information.In this Part, design objectives are described and are followed by the design concepts used to realize the stated objectives. The resultant network is then described in terms of its external interface

20、s, major network elements and network services. A listing of key identifiers in CDPD is then followed by a comprehensive glossary of CDPD terms and a reference list of non-CDPD documents.This Part contains the detailed listing of all Parts of the Cellular Digital Packet Data Specifications.a71 Part

21、300 to Part 799Protocols and InterfacesThese Parts form the heart of the CDPD System Specification. They define the communications architecture of CDPD, including communications layer entities, services, protocol stacks, the three key interfaces, Radio Resource Control, Mobility Management, Accounti

22、ng Management, Support Services and Network Management.a71 Part 800 to Part 899Supplementary Protocol InformationThese Parts contain further specification of the primary CDPD protocols. State transition matrices are used to define protocol state machines, and Protocol Implementation Conformance Stat

23、ements (PICS) are provided for implementors.a71 Part 900 to Part 999Protocol Test SpecificationsFollowing an overview of protocol testing, these Parts contain Abstract Test Suites (ATSs) and Protocol Implementation eXtra Information for Test (PIXIT) for the protocols specified in Part 300 to Part 79

24、9.a71 Part 1000 to Part 1999Guidelines for Service ProvidersThese Parts describe guidelines for CDPD Service Providers.6201123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Introduction TIA/EIA-732-620PART 620 Message Handling Service1 Int

25、roductionThis Part is directed towards Cellular Digital Packet Data (CDPD) Service Providers intending to build or purchase equipment for use in the CDPD internal network. This Part does not directly affect CDPD subscribers or Mobile End System (M-ES) manufacturers.CDPD Message Handling Services pro

26、vide a generic message store and forward service that is utilized by other CDPD Network Support Services (Part 630) and some CDPD Network Application Services. The Message Handling Service is based on standards published in 1988: ISO-10021-1-7 and CCITT-X.400.The CCITT-X.400 Message Handling System

27、(MHS) recommendations provide message exchange by means of a Message Transfer System (MTS) consisting of a series of Message Transfer Agents (MTAs) that are responsible for relaying a message from an originators User Agent (UA) to a recipients UA. This specification is aligned with the 1993 issue of

28、 the Industry/Government Open System Specification (IGOSS) IGOSS-1.This Part specifies the MHS requirements in support of CDPD Network Support Services and CDPD Network Application Services. Individual service provider networks may wish to utilize X.400 as a foundation to offer additional services.

29、Additional MHS requirements (if any) needed to support such additional services are outside the scope of this specification.TIA/EIA-732-620 Message Handling Service62021234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859602 Message Handling Sy

30、stem (MHS)The CCITT-X.400 MHS Functional Model is shown in Figure 620-1 and is composed of Users, User Agents, Message Transfer System, Message Transfer Agents, Access Unit, Physical Delivery Access Unit and Message Store.Users A user is a person or a computer process. Users are either direct users

31、(i.e., engage in message handling by direct use of MHS) or are indirect users (i.e., engage in message handling through another communication system e.g., a physical delivery system that is linked to MHS). A user is referred to as either an originator (when sending a message) or a recipient (when re

32、ceiving a message). Message handling elements of service define the set of message types and the capabilities that enable an originator to transfer messages of those types to one or more recipients.FIGURE 620-1 MHS Functional ModelMTA MSUAAUPDAUPhysical Delivery ServicesOther Telematic ServicesMTAMT

33、AMTAUAUAMTSMHSUserUserUserUserUser6203Message Handling System (MHS) TIA/EIA-732-620123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960User Agent (UA)A UA is an application process that interacts with the MTS or a Message Store (MS) to submi

34、t messages on behalf of a single user.Each message is uniquely and unambiguously identified. To facilitate meaningful communication, a UA can specify the encoded information types that can be contained in messages which are delivered to it. The content type and original encoded information type(s) o

35、f a message and an indication of any conversions that have been performed, and the resulting encoded information type(s) are supplied with each delivered message. In addition, the submission time and delivery time are supplied with each message.Message Transfer System (MTS)The MTS delivers the messa

36、ges submitted to it to one or more recipient UAs, Access Units (AUs) or MSs, and can return notifications to the originator. The X.400 basic message transfer service is defined in Section 19.2 of CCITT-X.400. It enables a UA to submit and to have messages delivered to it. If a message cannot be deli

37、vered, the originating UA is so informed through a non-delivery notification. Functions performed solely by the UA and not standardized as part of the message handling elements of service are called local functions. A UA can accept delivery of messages directly from the MTS or it can use the capabil

38、ities of an MS to receive delivered messages for subsequent retrieval by the UA. The MTS comprises a number of MTAs.Message Transfer Agents (MTA) Operating together, in a store and forward manner, the MTAs transfer messages and deliver them to the intended recipients.Access Unit (AU)Access by indire

39、ct users of MHS is accomplished by AUs.Physical Delivery Access Units (PDAU)Physical delivery to indirect users of MHS is accomplished by PDAUs.TIA/EIA-732-620 Message Handling Service6204123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960M

40、essage Store (MS)The message store acts as an intermediary between the UA and MTA. Its primary purpose is to store and permit retrieval of delivered messages. The MS also allows for submission from the UA and alerting to the UA.Not all of these components are required in a configuration of a message

41、 handling system. The CDPD MHS Functional Model in particular incorporates a subset of these components (Figure 620-2). CDPD MHS includes the MTS and UAs. The CDPD MHS functional model does not include AUs and other Telematic Services, PDAUs and Physical Delivery Services and MS. 3 MHS Configuration

42、sAs specified by IGOSS-1, several physical configurations of message handling systems are possible. The CDPD physical configurations are indicated in Table 620-1.FIGURE 620-2 Message Transfer System Refined ModelMTS-UserMessage Transfer System (MTS)OriginatorMessageReportdeliverySubmission(or non-de

43、livery)MTS-UserMTS-UserIntendedrecipientsMessage-delivery(non-deliveryof message)MTAMTAMTAMTAMessageTransferReport Transfer6205Conformance Requirements TIA/EIA-732-620123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960a71 R is the recommend

44、ed configurationa71 O is Optional and may replace the recommended configuration if it is consistent with the way a service provider is constructing its MD-ISs and Message Transfer Serversa71 I selects an Interpersonal Messaging (IPM) User Agent. Accounting information, location information and other

45、 information conformant with the CDPD usage of message handling services shall be captured as an instance of an Externally Defined Body Part Type and delivered within the framework of IPM services.a71 S selects a UA that is secure. Secure UAs are optional.ADMD gateways within an MTA are not required

46、 for conformance to CDPD specifications, but individual Service Provider Networks may wish to add this requirement to their specific procurements.4 Conformance RequirementsConformance requirements for the CDPD Message Handling System track the recommendations from Stable Implementation Agreements fo

47、r Open Systems Interconnection Protocols: Output from the September 1992 Open Systems Environment Implementors Workshop OIW-1.The OIW-1 recognizes that the 1988 MHS standards cover a wide range of functional areas, not all of which would be relevant to every implementation. Part 8, Table 30 in OIW-1

48、 lists the functional groups and the conformance requirements for different configurations. The CDPD conformance requirements are specified in Table 620-2.4.1 Use of Directory by UA and MTAAccess to the Directory services by the UA or MTA is not required but may be requested by specific Service Prov

49、ider Network procurement authorities.TABLE 620-1 CDPD MHS Physical ConfigurationsConfigurations (As per IGOSS-1)RequirementIGOSS-1 MHS 1988 MTA RIGOSS-1 MHS 1988 Remote UA(IS)-P3 OIGOSS-1 MHS 1988 MTA-UA(IS) RTIA/EIA-732-620 Message Handling Service62061234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859604.2 Security Class ConformanceSecure communications between UAs is optional. When security is required for UA-to-UA communication, Class S0a that implements all security outside of the MTA is s