1、 TIA TELECOMMUNICATIONS SYSTEMS BULLETIN IP Network Reference Model (NRM) for cdma2000 Spread Spectrum Systems TSB-151 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Electronic Industries Alliance Pr
2、ovided 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 manufacturers and purchasers, facilitating
3、interchangeability and improvement of products, and assisting the purchaser 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 from manufacturing or se
4、lling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA members, whether the standard is to be used either domestically or internationally. Standards, Publications and Bulletins
5、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, Publication, or Bulletin. Further details of the d
6、evelopment process are available in the TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm Technical Bulletins are distinguished from TIA Standards or Documents, in that they contain a compilation of engineering data or information useful to the technical
7、 community, and represent approaches to good engineering practices that are suggested by the formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly represent good engineering practice, or that may be acceptable to, or have been accepted by, app
8、ropriate bodies. Parties who wish to bring other approaches to the attention of the formulating committee to be considered for inclusion in future revisions of this Bulletin are encouraged to do so. It is the intention of the formulating committee to review this document every five years, but it may
9、be revised and updated at any time as may be occasioned by changes in technology, industry practice, or government regulations, or for other appropriate reasons. (From Project No. 3-0122, formulated under the cognizance of the TIA TR-45 Committee on Mobile each character is defined as: “X” = publish
10、ed revision to which this enhancement applies. “Y” = major technical enhancement number beyond “X”. “Z” = editorial enhancement number beyond “Y”. Version Date Description Source 1.0.0 December, 2003 Initial publication “IP Network Architecture Model for cdma2000 Spread Spectrum Systems”, Revision 3
11、.0.0 (3GPP2 S.P0037-0); 3GPP2 TSG-S WG2 Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo re
12、production or networking permitted without license from IHS-,-,-TIA/TSB-151 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 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 1 1. PURPOSE AND SCOPE This document recommends the b
13、asic 3GPP2 Wireless IP Network Architecture Model. 1.1 References 3GPP 3GPP TS 23.127 - “Virtual Home Environment/Open Service Architecture (Release 5)”. 3GPP TS25.401 “UTRAN Overall Description”. 3GPP TS23.002 “Technical Specification Group Services and System Aspects, Network Architecture (Release
14、 5)”. 3GPP2 3GPP2 P.S0001-B, “Wireless IP Network Standard”, Version 1.0, October 25, 2002,. IEEE 802.11, ISO/IEC 8802-11 ANSI/IEEE Standard 802.11 First Edition 1999-00-00. “Information Technology Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks Speci
15、fic Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (Phy) Specifications”. IETF Calhoun, Perkins, Mobile IP Foreign Agent Challenge/Response Extension, RFC 3012, November 2000. Calhoun, Perkins, Mobile NAI Extension RFC 2794, March 2000. Cong, Hamnlen, Perkins, The
16、Definitions of Managed Objects for IP Mobility Support Using SMIv2, RFC 2006, October 1995. Internet Engineering Task Force, RFC 3261 SIP: Session Initiation Protocol. Montenegro, Reverse Tunneling for Mobile IP, RFC 3024, January, 2001. Perkins, IP Mobility Support for IPv4, RFC 3220, January 2002
17、Perkins, IP Encapsulation within IP, RFC 2003, October 1996. Perkins, Minimal Encapsulation within IP, RFC 2004, October 1996. Solomon, Applicability Statement for IP Mobility support, RFC 2005, October 1995. TIA/EIA-41 ANS/TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations, Decem
18、ber, 1997. TIA/EIA/IS-725, Over-The-Air Service Provisioning, June 1997. TIA/EIA/IS-737, IS-41-C Enhancements to Support Circuit Mode Services, (approved for publication). TIA/EIA-95 TIA/EIA/IS-95-A, Mobile Station Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular S
19、ystems; Telecommunications Industry Association; May 1995. TSB74, Support for 14.4 kbps Data Rates and PCS Interaction for Wideband Spread Spectrum Cellular Systems, December, 1995. TIA/EIA/IS-95-B, Mobile Station Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular Sy
20、stems; Telecommunications Industry Association; March 1999. TIA/EIA/IS-2000-1-A to 6, cdma2000 Family of Standards for Spread Spectrum Systems; Telecommunications Industry Association; March 2000. TIA/EIA-124 TIA/EIA-124-D, Wireless Radio Telecommunications Intersystem Non-Signaling Data Communicati
21、ons (DMH); Telecommunications Industry Association; January 2002. Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/TSB-151 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
22、24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 2 TIA/EIA-553 EIA/TIA/IS-553, Mobile Station - Land Station Compatibility Specification; September 1989. OTA TIA/EIA/IS-683-A, Over-The-Air Service Provisioning of Mobile Stations in Spread
23、 Spectrum Systems, February 1997. 1.2 Terminology This document uses the following “verbal forms” and “verbal form definitions”: 1. “should” and “should not” indicate items of interest that are highly desirable and particularly suitable, without identifying or excluding other items; or (in the negat
24、ive form) indicate items of interest that are not desirable, are not particularly suitable, or are not recommended but not prohibited, and 2. “may” and “may not” indicate items of interest that are optional but permissible within the limits of this recommendation. 1.3 Assumptions a. The architecture
25、 described in this document assumes the following protocols: 1. SIP (Session Initiation Protocol), 2. DIAMETER, and 3. MOBILE IP (i.e., IPv4 and/or IPv6). b. The use, support, and interoperation of IPv4 and IPv6 in the All-IP network is currently assumed in this document, but whether IPv6 should be
26、used exclusively needs to be strongly considered in ongoing work. c. There are known bearer paths not shown in Figure 2.1 (e.g., bearer paths between the Application Servers and the Border Router, the Application Servers and the Media Resource Function Processor). Some of these interfaces are shown
27、in additional diagrams in this document, but not numerically labeled, see Section 3. d. There are known signaling paths not shown in Figure 2.1 (e.g., signaling paths between two Call Session Control Functions (CSCFs), two AAA, an external SIP entity beyond the Border Router and the CSCF). Some of t
28、hese interfaces are shown in additional diagrams in this document, but not numerically labeled, see Section 3. 1.4 Architectural Principles The statements contained in this section should guide the development of the All-IP network architecture. While these statements are too general to be treated a
29、s specific requirements, they form a set of principles meant to govern the overall development of the All-IP network, they are: a. The All-IP network architecture should be independent of the underlying Layer 1 and Layer 2 protocols through the use of IP-based protocols. b. The All-IP core network s
30、hould be independent of the access network. The core network should have the ability to support multiple access network technologies (e.g., cable, radio access technologies, wireless LAN, DSL). The core network should have the ability to support access networks as they evolve and as new access techn
31、ologies are identified. This implies that network functions such as Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/TSB-151 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 2
32、3 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 3 call control and service control should be independent of access functions. How this independence is maintained for mobility management and location-based services (which may be depende
33、nt on access technology) is for further study. c. A phased migration of existing networks to the All-IP network should be possible. d. All pertinent interfaces in the All-IP network should be defined in an open manner. e. The All-IP network should promote efficient use of radio interface resources.
34、f. The All-IP network should be capable of supporting reliability levels equal to or better than those found in legacy networks. g. The All-IP network should support capabilities for rapid service creation, including service creation by the user and by third parties as well as service profile custom
35、ization by end users. h. The All-IP network should permit separate signaling and bearer paths. i. The All-IP network architecture and protocols should be scalable. j. The All-IP network architecture development process should aim to identify and reuse solutions from other initiatives within the IMT-
36、2000 family (especially 3GPP), whenever possible and reasonable. k. The All-IP network should support Quality of Service equal to or better than that found in legacy networks. l. The All-IP network architecture should be defined in terms of separate functions and clear interfaces such that it is pos
37、sible to separate bearer from signaling. m. The All-IP network should be functionally designed to allow and encourage reduced complexity and/or resource utilization. n. The All-IP network should support a range of terminal types (e.g., voice-only terminals, IP Multimedia terminals, laptop computers)
38、. Not all these terminals may be able to support end-to-end IP capabilities (e.g., 2G and 3G legacy terminals). o. The All-IP architecture should be designed in such a way that a migration from IPv4 to IPv6 is feasible and that IPv4 and IPv6 based All-IP networks may interoperate. 1.5 Legend This se
39、ction provides a definition of the different styles of lines and rectangles used in many figures within this recommendation, as: Dashed Line Signaling interface, Dashed Rectangle Collective Network Entity and Composite Network Entity, Heavy Dashed Line Radio Link (air interface), Solid Line Circuit
40、Bearer or Packet Bearer interface, and Solid Rectangle Network Entity. Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/TSB-151 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 2
41、2 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 4 1.6 Definitions This section provides definitions of some terms used within this document, as: Quality of Service (QoS) QoS refers to a set of capabilities that a network may provide
42、 to a communications session. These capabilities can be specified so that particular applications (e.g., voice, video, streaming audio) fulfill human factors or other requirements with respect to fidelity and performance. QoS in a packet network consists of at least the following components: a. Band
43、width: Data rate (e.g., 64 kbps), b. Delay: End-to-end or roundtrip latency (e.g., 300 ms), c. Jitter: Inter-packet latency variation (e.g., 10 ms), and e. Loss: Rate at which packets are dropped (e.g., 3%). Additionally, this QoS may be: a. unidirectional or bidirectional, b. guaranteed or statisti
44、cal, c. end-to-end or limited to a particular domain or domains, and e. applied to all traffic or just to a particular session or sets of sessions. Wireless Network Operator (WNO) A network operator offering wireless services using the architecture defined by 3GPP2. This architecture may also suppor
45、t other access technologies. Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA/TSB-151 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 34 35 3
46、6 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 5 1.7 Abbreviations This section provides a definition of the abbreviations used within this recommendation, as: AAA Authentication, Authorization, and Accounting MS Mobile Station API Application Programming Interface MSC Mob
47、ile Switching Center AGW Access Gateway NAI Network Access Identifier AS Application Server NML Network Management Layer BGCF Breakout Gateway Control Function OSA Open Service Access BML Business Management Layer OSA-SCS OSA - Service Capability Server BR Border Router OSF Operations Systems Functi
48、on BSC Base Station Controller OSS Operations Support System BTS Base Transceiver System OTAF Over the Air Activation Function CoA Care of Address PCF Packet Control Function CSCF Call Session Control Function P-CSCF Proxy CSCF DB Database PDE Position Determining Entity DSI Dynamic Subscriber Infor
49、mation PDSN Packet Data Service Node EIR Equipment Identity Register PDF Policy Decision Function EML Element Management Layer PSTN Public Switched Telephone Network FA Foreign Agent QoS Quality of Service HA Home Agent RAN Radio Access Network HLR Home Location Register RNC Radio Network Controller IMS IP Multimedia Subsystem SCE Service Creation Environment IP Internet Protocol SCP Service Contro
