TIA-878-1-2003 Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access Network Interfaces Addendum 1 Addendum No 1 to TIA-878《高速分组数据(HRPD)接入网络接口互用性规范(IOS)》.pdf

《TIA-878-1-2003 Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access Network Interfaces Addendum 1 Addendum No 1 to TIA-878《高速分组数据(HRPD)接入网络接口互用性规范(IOS)》.pdf》由会员分享，可在线阅读，更多相关《TIA-878-1-2003 Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access Network Interfaces Addendum 1 Addendum No 1 to TIA-878《高速分组数据(HRPD)接入网络接口互用性规范(IOS)》.pdf（130页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA DOCUMENT Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access Network Interfaces Addendum 1 TIA-878-1 (Addendum No. 1 to TIA-878) MAY 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyrigh

2、t Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between

3、 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 Publications shall not in any respect preclude any member or non-m

4、ember of TIA from manufacturing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use by non-TIA members, either domestically or internationally. TIA DOCUMENTS TIA Documents contain information deemed to be of technical va

5、lue to the industry, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of a American National Standard (ANS). Further details of the development process are a

6、vailable in the TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm TIA Documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on whether to reaffirm, revise, withdraw, or proceed to develop an American National S

7、tandard on this subject. Suggestions for revision should be directed to: Standards that a certain course of 23 action is preferred but not necessarily required; or (in the negative form) that a certain possibility or 24 course of action is discouraged but not prohibited. “May” and “need not” indicat

8、e a course of action 25 permissible within the limits of the standard. “Can” and “cannot” are used for statements of possibility 26 and capability, whether material, physical, or causal. 27 28 1.3 References 29 1.3.1 TIA / EIA 30 For ease of cross referencing, the Telecommunications Industry Associa

9、tion (TIA) / Electronics Industry 31 Association (EIA) references provided in this section are aligned with the 3GPP2 references, provided in 32 section 1.3.2. For consistency between RAN specifications, the most commonly referenced documents 33 117 are maintained or left as “Reserved” if not used i

10、n this specification. 34 1 TIA/EIA/IS-2000-A-2, cdma2000 Standards for Spread Spectrum Systems Release A, March 35 2000. 36 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-8

11、78-1 IOS HRPD May 2003 1-2 02-06 Reserved. 1 7 TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Wideband Spread 2 Spectrum Cellular Systems, March 1999. 3 8 IS-707-A-2, Data Service Options for Spread Spectrum Systems, March 2001. 4 9 TIA/EIA/IS-835-A, cdma2000 Wireless IP Networ

12、k Standard, May 2001. 5 10 TIA/EIA/IS-856-2, cdma2000 High Rate Packet Data Air Interface Specification, October 6 2002. 7 11 TIA/EIA/IS-2001-A, Inter-Operability Specification (IOS) for CDMA 2000 Access Network 8 Interfaces, May 2001. 9 12-17 Reserved. 10 1.3.2 3GPP2 11 The 3GPP2 references are ali

13、gned with the TIA/EIA references of Section 1.3.1 and are provided here for 12 information and cross reference purposes. 13 1 cdma2000 Standards for Spread Spectrum Systems Release A: 14 3GPP2 C.S0001-A, Introduction to cdma2000 Standards for Spread Spectrum Systems, June 15 2000. 16 3GPP2 C.S0002-A

14、-1, Physical Layer Standard for cdma2000 Spread Spectrum Systems, 17 October 2000. 18 3GPP2 C.S0003-A-1, Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum 19 Systems, October 2000. 20 3GPP2 C.S0004-A-1, Signaling Link Access Control (LAC) Standard for cdma2000 Spread 21 Spectrum Syst

15、ems, October 2000. 22 3GPP2 C.S0005-A-1, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread 23 Spectrum Systems, October 2000. 24 3GPP2 C.S0006-A-1, Analog Signaling Standard for cdma2000 Spread Spectrum Systems, 25 October 2000. 26 2-6 Reserved. 27 7 Reserved. Note: there is no 3GPP2 equi

16、valent for TIA/EIA-95-B. 28 8 3GPP2 C.S0017-0-2 v2.0, Data Service Options for Spread Spectrum Systems, August 2000. 29 9 3GPP2 P.S0001-A, Wireless IP Network Standard, July 2000. 30 10 3GPP2 C.S0024 v4.0, cdma2000 High Rate Packet Data Air Interface Specification, October 31 2002. 32 11 3GPP2 A.S00

17、01-A v2.0, 3GPP2 Access Network Interfaces Interoperability Specification, June 33 2001. 34 12 A.R0011, A Report on Issues Identified with IOS v4.1, August 2002. 35 13-17 Reserved. 36 1.3.3 Other 37 18 RFC 1321, MD5 Message-Digest Algorithm, April 1992. 38 19 RFC 1661, Point-to-Point Protocol, July

18、1994. 39 20 RFC 1662, PPP in HDLC-Like Framing, July 1994. 40 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-878-1 May 2003 IOS HRPD 1-3 21 RFC 1750, Randomness Recommendat

19、ions for Security, December 1994. 1 22 RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP), August 1996. 2 23 RFC 2002, IP Mobility Support, October 1996. 3 24 RFC 2486, The Network Access Identifier, January 1999. 4 25 RFC 2865, Remote Authentication Dial In User Service (RADIUS), June

20、 2000. 5 6 1.4 Terminology 7 8 1.4.1 Acronyms 9 AAA Authentication, Authorization and Accounting ACCM Async-Control-Character-Map AN Access Network ANID Access Network Identifiers AT Access Terminal BS Base Station BSC Base Station Controller CANID Current Access Network Identifiers CHAP Challenge H

21、andshake Authentication Protocol CVSE Critical Vendor/Organization Specific Extension HRPD High Rate Packet Data IMSI International Mobile Subscriber Identity IOS Inter-Operability Specification LCP Link Control Protocol MAC Medium Access Control MEI Mobility Event Indicator MN ID Mobile Node Identi

22、fication MS Mobile Station MSC Mobile Switching Center NAI Network Access Identifier NID Network Identification PANID Previous Access Network Identifiers PCF Packet Control Function PDSN Packet Data Serving Node PPP Point-to-Point Protocol PZID Packet Zone Identification RADIUS Remote Authentication

23、 Dial-In User Service SID System Identification SKey Session Key UATI Unicast Access Terminal Identifier Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-878-1 IOS HRPD May 2

24、003 1-4 1.4.2 Definitions 1 Access Authentication A procedure in which the Access Terminal (AT) is authenticated by the AN-2 AAA (Access Network Authentication, Authorization and Accounting entity). 3 Access Stream The HRPD stream whose end-points are the access terminal and the access net-4 work (r

25、adio network). This stream is used for access authentication. 5 Access Network The network equipment providing data connectivity between a packet switched 6 data network (typically the Internet) and the access terminals. An access network 7 is equivalent to a base station in cdma2000 systems. 8 Acce

26、ss Terminal A device providing data connectivity to a user. An access terminal may be 9 connected to a computing device such as a laptop personal computer or it may be 10 a self-contained data device such as a personal digital assistant. An access 11 terminal is equivalent to a mobile station in cdm

27、a2000 systems. 12 AN-AAA An entity that performs access authentication and authorization functions for the 13 Access Network. 14 Connection A connection is a particular state of the air-link in which the access terminal is 15 assigned a Forward Traffic Channel, a Reverse Traffic Channel and associat

28、ed 16 Medium Access Control (MAC) Channels. During a single HRPD session the 17 access terminal and the access network can open and can close a connection 18 multiple times. 19 Hybrid MS/AT A device capable of operating on both cdma2000 and HRPD access networks. 20 Service Stream The HRPD stream use

29、d when exchanging data between the access terminal and 21 the PDSN. 22 HRPD session An HRPD session refers to a shared state between the access terminal and the 23 access network. This shared state stores the protocols and protocol configurations 24 that were negotiated and are used for communicatio

30、ns between the access 25 terminal and the access network. Other than to open a session, an access terminal 26 cannot communicate with an access network without having an open session. 27 Note that it is possible that the A10/A11 connection is not established even 28 though the HRPD session is establ

31、ished. Refer to 10, Section 1.9. 29 Packet Data Session An instance of use of packet data service by a mobile user. A packet data session 30 begins when the user invokes packet data service. A packet data session ends 31 when the user or the network terminates packet data service. During a particula

32、r 32 packet data session, the user may change locations but the same IP address is 33 maintained. Refer to 11, Section 1.6.2. 34 35 36 37 38 39 40 41 42 43 44 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted

33、 without license from IHS-,-,-TIA-878-1 May 2003 IOS HRPD 1-5 1.5 HRPD IOS Architecture Reference Model 1 The HRPD IOS messaging and call flows are based on the Architecture Reference Model shown in Figure 2 1.5-1, HRPD IOS. 3 Source AccessNetwork (AN)Target AccessNetwork (AN)PCFA8PDSNA9A10A11AN AAA

34、A13AccessTerminal (AT)A12Air Interface4 Figure 1.5-1 HRPD IOS Architecture Reference Model 5 1.6 HRPD Micro-Mobility and Macro-Mobility Concepts 6 The figure below provides a conceptual view of levels of HRPD packet data mobility. 7 Home AgentPDSN PDSNPCFPCF PCFANAN ANANMobility betweenPDSNs (Mobile

35、 IP)Mobility betweenPCFs (A10/A11Interfaces)Mobility between ANs(A8/A9 Interfaces)8 Figure 1.6-1 Packet Data Mobility Architecture for HRPD 9 The A8/A9 interfaces support mobility between ANs under the same PCF. 10 The A10/A11 interfaces support mobility between PCFs under the same PDSN. 11 Mobile I

36、P supports mobility between PDSNs under the same Home Agent. 12 1.7 Compatibility with IS-2001 Standards 13 The HRPD IOS interface, as defined in this specification, is compatible with a TIA/EIA/IS-2001 or high-14 er release, with the provision that the HRPD capabilities are the same as those suppor

37、ted by the inter-15 operability specification, for the access network(s) in use. For example, when inter-operating with a 16 TIA/EIA/IS-2001 system, the portions of this specification related to concurrent services and support for 17 Previous/Current Access Network Identifiers (PANID/CANID) are not

38、applicable. 18 Note: When the procedures between TIA/EIA/IS-95-B or cdma2000 and HRPD systems differ, the 19 HRPD procedures are identified separately within this specification. When the TIA/EIA/IS-2001 text is 20 Copyright Telecommunications Industry Association Provided by IHS under license with E

39、IANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-878-1 IOS HRPD May 2003 1-6 applied to the HRPD RAN specification, the procedures related to the MSC shall be ignored. Hard Hand-1 off procedures, as defined in 11, are not applicable to HRPD. 2 3 1.8 HRPD IOS A

40、ssumptions 4 The following assumptions are made regarding AN/AT behavior: 5 1. A packet data session may transition from a serving cdma2000 system to a serving HRPD system and 6 from a serving HRPD system to a serving cdma2000 system. 7 2. A unique value, 59 (3BH), is used in the Service Option fiel

41、ds in accounting records transported on 8 the A9 and A11 interfaces to identify accounting records associated with HRPD packet data service. 9 3. For the case of dormant inter-AN inter-PCF handoff, the target PCF may use the PDSN address 10 received from the source AN to send the A11-Registration Re

42、quest message. Otherwise, the target 11 PCF shall use the PDSN selection algorithm (if supported and if the IMSI is available) or internal 12 algorithms to select a PDSN. 13 4. Following a dormant handoff, the target AN sends the SID, NID, PZID triplet (ANID), if received 14 from the AT, to the targ

43、et PCF. If the AT does not send the ANID, or the AN chooses not to request 15 this information from the AT, then the target AN may send the ANID received in the A13-Session 16 Information Response message from the source AN. If the target PCF supports ANIDs, then it sets 17 the PANID to the ANID rec

44、eived from the AN, and the CANID to its own ANID in the A11 18 messages. 19 5. For the instance of Packet Application terminated in the AN, the AT shall support Challenge 20 Handshake Authentication Protocol (CHAP) access authentication. In this case, the AT shall send a 21 Network Access Identifier

45、 (NAI) of the form specified in 24. 22 6. For the instance of Packet Application terminated in the AN (i.e., AN access authentication), the gen-23 eration of the NAI and password are the responsibility of the service provider. The NAI and password 24 should be chosen and managed using procedures tha

46、t minimize the likelihood of compromise. 25 7. If the access authentication feature is used, the AN shall always propose CHAP as a PPP option in an 26 initial Link Control Protocol (LCP) Configure-Request during the PPP establishment. 27 8. The Mobile Node Identification (MN ID) that is used by the

47、AN and the PCF on A8/A9 and A10/A11 28 messages is unique within the operators network, and is determined as follows: 29 - If the HRPD AN uses the access authentication feature, the MN ID field shall be set to the MN ID 30 value returned by the AN-AAA (e.g., IMSI) following successful access authent

48、ication. 31 - Otherwise, the AN/PCF shall set the MN ID field to a value that conforms to a valid MN ID 32 format (i.e., IMSI format). In this case, the MN ID is determined by other means. 33 9. After the AT indicates it is ready to exchange data on the access stream, the AT and the AN initiate 34 P

49、PP procedures according to 19. 35 10. The AT may support packet data service as specified in 9. 36 37 38 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-878-1 May 2003 IOS HRPD 2-1 2 HRPD IOS Interfaces 1 This section describes the Radio Access Network interfaces associ