TIA EIA-732-501-2001 Cellular Digital Packet Data (CDPD) System Specification Mobile Network Location Protocol《蜂窝数字分组数据(CDPD)系统规范 移动网位置协议》.pdf

《TIA EIA-732-501-2001 Cellular Digital Packet Data (CDPD) System Specification Mobile Network Location Protocol《蜂窝数字分组数据(CDPD)系统规范 移动网位置协议》.pdf》由会员分享，可在线阅读，更多相关《TIA EIA-732-501-2001 Cellular Digital Packet Data (CDPD) System Specification Mobile Network Location Protocol《蜂窝数字分组数据(CDPD)系统规范 移动网位置协议》.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、ANSI/TIA/EIA-732-501-2001 Approved: June 7, 2001 TIA/EIA STANDARD Cellular Digital Packet Data (CDPD) System Specification Mobile Network Location Protocol TIA/EIA-732-501 OJpgrade of TIAIEIAIIS-732-501) JULY 2001 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Tlie Telecoininiiiiicatioiis Industry Associat

2、ion represents tlie communications sector of NOTICE TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandmgs between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purch

3、aser 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, n

4、or 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 Standards

5、Institute (ANSI) patent policy. By such actio% TMIA 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 applicable r

6、egulatory 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-501-UG, formulated under the cognizance of the TIA TR-45.6

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

8、UBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) All rights reserved Printed in U.S.A. TINEIA-732-501 Contents fi 1 Introduction . .501-1 9 1 (3 11 2 Overview of the Protocol .501-1 . : 2.2 Network Service Access Points .501-3 Security an

9、d Encryption . .501-5 1 -7 3 Protocol Functions . .501-5 3.1.1 Holding Timer .501-5 .? .1 3.1.2 MD-IS Cache Timer .501-5 3.2.2 Registration Directory .501-6 2.1 Underlying Service Assumed by the Protocol .501-2 I J 2.3 Network Layer Protocol Identification .501-4 . 1.3 .1 ,. IL? I (5 2.4 _il z. 1 1

10、Y 3.1 Parameters I * . ., LL 3.2 Forwarding Information Base . .501-6 3.2.1 Location Directory . .501-6 .,C t: .* 3.2.3 Home Domain Directory .501-6 MD-IS Information Directory .501-7 MD-IS Information Cache . .501-8 3.3.1 Key Management .501-9 3.3.3 Decryption .501-11 L. 1: /: 3.2.4 3.2.5 .? 7 Li 7

11、2 z. . ., ._ .a 3.3 Security . :t: 3.3.2 Encryption .501-10 . - 3.4 Location Update Function . .501-12 3.4.1 MNLP PDU Reception Function . .501-12 Record Location Function .501-16 .$ 3.4.5 Flush Registration Information Function . .501-19 3.5 Forward NPDU Function . .501-21 .?$ 3.5.1 Redirection Fun

12、ction .501-21 , 2.2. 33 .?il .a .u x .* ., ; , 3.4.2 MNLP PDU Transmission Function . .501-13 Report Location Function .501-14 .,I. 3.4.3 3.4.4 3 40 ,.$il 3.4.6 Flush Location Information Function .501-20 .+ ,. 3.4.7 Query Location Function . .501-21 ., $ 3 /i 4 .1 4.1 PDUStructure . 4.1.1 PDUType 4

13、.1.2 4.1.3 OptionsArea .501-28 4.2 PDUDefinitions Addressing Parameters Area . .501-26 4.2.1 Redirect Request (RDR) . .501-29 4.2.2 Redirect Confirm (RDC) . .501-33 4.2.3 Redirect Flush (RDF) . .501-36 501 -i TINEIA-732-501 4.2.4 4.2.5 4.2.6 Redirect Expiry (RDE) . .501-37 Redirect Query (RDQ) . .50

14、1-39 Encapsulated Security Payload (ESP) .501-40 501-i TINEIA-732-501 PART 501 Mobile Network Location Protocol Foreword This foreword is not part of the Standard This Standard has been produced by the TR-45.6 Subcommittee of the TIAIEIAPTR-45 Committee. This document contains significant portions o

15、f 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 used to provide these service

16、s consists of radio channels typically used for Advanced Mobile Phone System (AMPS) cellular service. Document Structure This Standard is published as a series of Parts. Each Part contains information pertaining to one aspect of the system. The functional structure of the Cellular Digital Packet Dat

17、a System Specification is as follows: o Introduction and Overview 501-iii TINEIA-732-501 Mobile Network Location Protocol This document provides an overview of the CDPD Network and serves as a guide to the remainder of the system specification for specific detailed information. In this Part, design

18、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 interfaces, major network elements and network services. A listing of key identifiers in CDPD is then followed by a comprehensive g

19、lossary 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. Part 300 to Part 799-Protocols and Interfaces These Parts form the heart of the CDPD System Specification. They define the commun

20、ications architecture of CDPD, including communications layer entities, services, protocol stacks, the three key interfaces, Radio Resource Control, Mobility Management, Accounting Management, Support Services and Network Management. Part 800 to Part 899-Supplementary Protocol Information These Part

21、s contain further specification of the primary CDPD protocols. State transition matrices are used to define protocol state machines, and Protocol Implementation Conformance Statements (PICS) are provided for implementors. Part 900 to Part 999-Protocol Test Specifications Following an overview of pro

22、tocol 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 799. Part 1000 to Part 1999-Guidelines for Service Providers These Parts describe guidelines for CDPD Service Providers. 501-i

23、v Introduction TIAEIA-732-501 PART 501 Mobile Network Location Protocol 1 Introduction 2 This Part of the CDPD System Specification defies a protocol for the exchange of forwarding and routing information between home and serving Mobile Data Intermediate Systems (MD-ISS), and between home MD-ISS, fo

24、r the support of Network Layer mobility. This connectionless protocol operates over Connectionless Network Protocol (CLNP) ISO-84731, and optionally operates over Internet Protocol (IP) RFC791. MNLP is designed to operate in conjunction with the Mobile Network Registration Protocol (MNRP), described

25、 in Part 507, and Radio Resource Management Protocol, described in Part 405, for providing Mobility Management services in the CDPD Network. This protocol provides for the exchange of location and redirection information between MD-ISS, as well as the forwarding and routing of messages to visiting M

26、-ESs. Overview of the Protocol This protocol provides the following services: a. b. c. Notification to MD-ISS of the current location (routing area subdomain) of Network Entity Identifiers (NEIs) associated with an M-ES Conveyance of data origin authentication information about M-ESs and their NEIs

27、Confirmation by a home MD-IS to a serving MD-IS of the willingness and ability to provide network forwarding services on behalf of an M-ES at its current location 501-1 TIA/EIA-732-501 Mobile Network Location Protocol d. Forwarding of NPDUs addressed to an M-ES from the home MD-IS to the current ser

28、ving MD-IS. These services are provided at the home MD-IS by the Mobile Home Function (MHF), and at the serving MD-IS by the Mobile Serving Function (MSF). The MHF consists of two services: a. The Location Directory maintains an information base of the current forwarding address for each M-ES in its

29、 home area (ie., the address of the Readdress Server). The Location Directory is kept current through the procedures defined in this Part. The Redirection Server performs the forwarding of NPDUs for M-ESs. The Redirection Server queries the Location Directory for the current forwarding address of th

30、e M-ES. Redirection consists of intercepting NPDUs addressed to M-ESs, encapsulating them, and forwarding them to the Readdress Server in the current serving area. b. The MSF consists of two services: The Registration Directory maintains an information base of the NSAP addresses of M-ESs currently r

31、egistered within its serving area. The Registration Directory is kept current through the procedures defiied in this Part and in Part 507. The Readdress Server decapsulates forwarded NPDUs for M-ESs in its area and relays them to their destinations. The communication between MD-ISS can be secure for

32、 IP only. The following apply to IP supported MD-ISS: Each MD-IS can decrypt a message from a remote MD-IS or security gateway with whom it is communicating, if secure communication is chosen. Every MD-IS shall have access to an MD-IS Information Directory which is a “trusted“ directory providing ad

33、dressing and security information pertaining to an MD-IS. 2.1 Underlying Service Assumed by the Protocol The Mobile Network Location Protocol assumes unreliable delivery of data for inter MD-IS communication. When the underlying network service selected is the Connectionless Mode Network Service, th

34、e required primitives are defiied in Table 501-1. When the underlying network service selected is User Datagram Protocol/Internet Protocol (UDP/IP), the required primitives for Location Update of the M-ES NEIs are defiied in Table 50 1-2. When the underlying network service selected is IP, the requi

35、red primitives for Forwarding of encapsulated NPDUs from the home MD-IS to the serving MD-IS are defiied in Table 501-3. Encapsulated IP NPDUs shall be sent using protocol type 4 (IP in IP). Encapsulated CLNP NPDUs shall be sent using protocol type 80 (CLNP in IP). 501-2 Overview of the Protocol TIA

36、EIA-732-501 Primitive N-UNITDATA. request, indication TABLE 501-1 Parameters NS-Destination-Address NS-SourceAddress NS-Quality-of-Service NS-UserData Primitive N-UNITDATA. request, indication TABLE 501-2 Parameters Destination-Address SourceAddress Protocol-Type UserData TABLE 501-3 2.2 Network Ser

37、vice Primitives in UDP/IP Mode Communication for Location Update I I I Primitive N-UNITDATA. request, indication Parameters Destination-Address SourceAddress Destination -Port UserData Network Service Primitives in UDP/IP Mode Communication for NPDU Forwarding The network service primitives describe

38、 an abstract service interface that exists between the protocol machine and the underlying Connectionless Mode Network Service. The protocol providing the underlying network service is CLNP ISO-84731. Network Service Access Points MNLP allows either CLNP or UDP/IP modes for inter MD-IS communication

39、s. Every MD-IS shall be uniquely identified by a 32- bit MD-IS Identifier. The most significant 16 bit shall be the Service Provider Identifier. The least significant 16 bits shall be assigned by the service provider to uniquely identiSl each MD-IS within the service providers network. For CLNP mode

40、 communications, distinct Network Service Access Points (NSAPs) are used to convey the services performed by this protocol. Two NSAPs are used at each MD-IS: Location Update Service NSAP 501-3 TIA/EIA-732-501 Mobile Network Location Protocol SPI 2.3 Network Layer Protocol Location information update

41、s are transferred between MD-IS peer entities using the NSAP assigned to the Location Update function. NPDUs ultimately destined for M-ESs are forwarded between MD-IS peer entities using the NSAP assigned to the Forward NPDU function. Forwarding Service NSAP TIA/EIA-732 defines the NSAP-Selector val

42、ues assigned to these NSAPs. For UDP/IP mode communications: Location Update Service Port Forwarding Service Protocol Types The transport UDP port UDP-PORT-MNLP shall be used for Location Update. IP protocol type 4 (IP in IP) shall be used for Encapsulated IP forwarding. IP protocol type 80 (CLNP in

43、 IP) shall be used for Encapsulated CLNP forwarding. Network Layer Protocol Identification The CDPD Network is a multi-protocol connectionless network. A single method of forwarding NPDUs to their intended destination requires that different Network Layer protocols be identifiable. When using CLNP a

44、s the transport, MNLP follows the principles of ISO-TR-95771, Protocol Identification in the Network Layer. As defiied by ISO-TR-95771, the first octet of a network service data unit is used as the Subsequent Protocol Identifier (SPI). The Forward NPDU function uses the same technique for encapsulat

45、ing NPDUs for forwarding. Assigned values of current interest to CDPD for NPDU encapsulation and forwarding are shown in Table 50 1-4. TABLE 501-4 I I ox81 I CLNPISO-8473 I I oxcc I IPRFC-7911 When using IP as the transport, the IP protocol type shall be used for network layer protocol Identificatio

46、n. There shall be no SPI in the encapsulated NPDU in this mode of transport. 1. UDP-PORT-MNLP shall be procured from InterNIC. 501-4 Protocol Functions TIAEIA-732-501 2.4 - Security and Encryption Encapsulating Security Protocol (ESP) RFC1827 may be used to provide security between MD-ISS operating

47、in the IP option mode. ESP may be supported either directly in the MD-IS or in a security gateway on behalf of an MD-IS. An example of a security gateway is a router that provides security services for a local MD-IS. Security information for ESP such as encryption algorithm and keys are stored in Se

48、curity Associations (SA) RFC1825. The keys stored in Security Associations may be manually provisioned or may be generated as described in Section 3.3. Only (IP based) MNLP control messages are encrypted; user data associated with the Forward NPDU function is not encrypted. 3 Protocol Functions This

49、 section describes the functions performed as part of this protocol. The functions described are mandatory in all implementations. These functions consist of: Location Update function Forward NPDU function. 3.1 Parameters 3.1.1 3.1.2 Holding Timer The Holding Timer applies to Location Directory information. The value of the Holding Timer is set by the home MD-IS, and indicates how long location information is retained by the Location Directory. Old location information is discarded after the Holding Timer expires to ensure correct operation of the protoco