CDMA2000 IP Network Arc

All-IP NAM Rev 3.
1
2
3
4
3GPP2 S.R0037-0 v3.0
5 Version Date: August 21, 2003
6
7
Version 3.0
8
9
10
11
12
13
14
15
16
17 IP Network Architecture Model for cdma2000
18
19
Spread Spectrum Systems
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 COPYRIGHT
50 3GPP2 and its Organizational Partners claim copyright in this document and individual
51 Organizational Partners may copyright and issue documents or standards publications in
52 individual Organizational Partner's name based on this document. Requests for reproduction
53 of this document should be directed to the 3GPP2 Secretariat at “secretariat@3gpp2.org”.
54
Requests to reproduce individual Organizational Partner's documents should be directed to
55
that Organizational Partner. See “www.3gpp2.org” for more information.
56
57
58
59
60
3GPP2 TSG-S All-IP NAM

All-IP NAM Rev 3.0
IP Network Architecture Model for cdma2000 Spread Spectrum Systems 1

2
3
4
CONTENTS 5
6
7
LIST OF FIGURES........................................................................................................................................ ii 8
9
PREFACE ...................................................................................................................................................... ii 10
11
REVISION HISTORY .................................................................................................................................. iv 12
13
1. PURPOSE AND SCOPE ..................................................................................................................1
14
1.1 References...........................................................................................................................1 15
1.2 Terminology........................................................................................................................2 16
17
1.3 Assumptions........................................................................................................................2 18
1.4 Architecture Principles........................................................................................................2 19
20
1.5 Legend ................................................................................................................................3
21
1.6 Definitions ..........................................................................................................................4 22
1.7 Abbreviations......................................................................................................................5 23
24
2. ARCHITECTURE MODELS ...........................................................................................................6 25
26
2.1 3GPP2 Wireless All-IP Network Architecture Model ........................................................6
27
2.1.1 Network Entities ...................................................................................................9
28
2.1.2 Reference Points .................................................................................................25 29
30
3. ALL-IP NAM DETAILED VIEWS ...............................................................................................32
31
3.1 Planer Views .....................................................................................................................32 32
3.1.1 Access Plane .......................................................................................................33 33
3.1.2 Network Plane ....................................................................................................34 34

35
3.1.3 Multimedia Bearer Plane ....................................................................................35
36
3.1.4 Multimedia Application Server Control Plane ...................................................36 37
3.2 Authentication and Authorization View ...........................................................................40 38

39
3.3 Mobile Station (MS) View................................................................................................42
40
3.4 Legacy MS Domain Control and Bearer View .................................................................44 41
3.5 Multimedia Domain Control and Bearer View .................................................................46 42

43
4. SERVICE CREATION AND MANAGEMENT............................................................................48 44
45
4.1 Service Creation Environment (SCE) ...............................................................................48
46
4.2 Service Management System (SMS) ................................................................................48 47
48
49
50
51
52
53
54
55
56
57
58
59
60
3GPP2 Wireless IP NAM ii Contents

All-IP NAM Rev 3.0
1
2 LIST OF FIGURES
3
4 Figure 2.1 3GPP2 Wireless All-IP Network Architecture Model........................................................8
5 Figure 3.1.1 Access Plane .....................................................................................................................33
6
Figure 3.1.2 Network Plane ..................................................................................................................34
7
8
Figure 3.1.3 Multimedia Bearer Plane ..................................................................................................35
9 Figure 3.1.4a Multimedia Application Server Control Plane .................................................................37
10 Figure 3.1.4b Multimedia SIP Services Control Plane ...........................................................................38
11 Figure 3.1.4c Multimedia Data Services Control Plane..........................................................................39
12
Figure 3.2 Authentication and Authorization View ...........................................................................41
13
14
Figure 3.3 Mobile Station (MS) View ...............................................................................................42
15 Figure 3.4 Legacy MS Domain Control and Bearer View.................................................................45
16 Figure 3.5 Multimedia Domain Control and Bearer View.................................................................47
17
Figure 4.1 Service Creation and Management ...................................................................................48
18
19
20
21
22 PREFACE
23
24 This 3GPP2 Wireless IP Network Architecture Model depicts packet mode operations
25 and gateway information.
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
iii 3GPP2 TSG-S All-IP NAM

All-IP NAM Rev 3.0
REVISION HISTORY 2
3
4
The “Revision” identifier is three characters “X.Y.Z”; each character is defined as: 5
“X” = published revision to which this enhancement applies. 6

7
“Y” = major technical enhancement number beyond “X”.
8
“Z” = editorial enhancement number beyond “Y”. 9
10
Version Date Description Source 11
1.0 October 25, 2000 Initial publication 3GPP2 All-IP AdHoc Group 12
2.0 May 14, 2002 NAM Version 2.0.0 3GPP2 TSG-S (April 17th 13
meeting) 14
3.0 August 21, 2003 NAM Revision 3.0.0 text SDO review comments 15
incorporated 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
3GPP2 TSG-S All-IP NAM iv

All-IP NAM Rev 3.0
1
2 1. PURPOSE AND SCOPE
3
4
This document recommends the basic 3GPP2 Wireless IP Network Architecture Model.
5
6
7
1.1 References
8
9 3GPP
10 • 3GPP TS 23.127 - “Virtual Home Environment/Open Service Architecture (Release 5)”.
11
• 3GPP TS25.401 – “UTRAN Overall Description”.
12
• 3GPP TS23.002 – “Technical Specification Group Services and System Aspects, Network
13
Architecture (Release 5)”.
14
15 3GPP2
16 • 3GPP2 P.S0001-B, “Wireless IP Network Standard”, Version 1.0, October 25, 2002,.
17
18 IEEE
19 • 802.11, ISO/IEC 8802-11 ANSI/IEEE Standard 802.11 First Edition 1999-00-00.
20 “Information Technology – Telecommunications and Information Exchange Between
21 Systems – Local and Metropolitan Area Networks – Specific Requirements – Part 11:
22 Wireless LAN Medium Access Control (MAC) and Physical Layer (Phy) Specifications”.
23
24
IETF
• Internet Engineering Task Force, RFC 3261 – SIP: Session Initiation Protocol.
25
26 • Perkins, IP Mobility Support for IPv4, RFC 3220, January 2002
27 • Perkins, IP Encapsulation within IP, RFC 2003, October 1996.
28 • Perkins, Minimal Encapsulation within IP, RFC 2004, October 1996.
29 • Solomon, Applicability Statement for IP Mobility support, RFC 2005, October 1995.
30 • Cong, Hamnlen, Perkins, The Definitions of Managed Objects for IP Mobility Support
31 Using SMIv2, RFC 2006, October 1995.
32
• Montenegro, Reverse Tunneling for Mobile IP, RFC 3024, January, 2001.
33
• Calhoun, Perkins, Mobile IP Foreign Agent Challenge/Response Extension, RFC xxxx,
34
December 1999.
35
• Calhoun, Perkins, Mobile NAI Extension RFC 2794, March 2000.
36
37
TIA/EIA-41
38
• ANSI/TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations,
39 December, 1997.
40
• TIA/EIA/IS-725, Over-The-Air Service Provisioning, June 1997.
41
• TIA/EIA/IS-737, IS-41-C Enhancements to Support Circuit Mode Services, (approved for
42
publication).
43
44
TIA/EIA-95
45
• TIA/EIA/IS-95-A, Mobile Station – Base Station Compatibility Standard for Dual-Mode
46
Wideband Spread Spectrum Cellular Systems; Telecommunications Industry Association;
47
May 1995.
48
• TSB74, Support for 14.4 kbps Data Rates and PCS Interaction for Wideband Spread
49
Spectrum Cellular Systems, December, 1995.
50
• TIA/EIA/IS-95-B, Mobile Station – Base Station Compatibility Standard for Dual-Mode
51
Wideband Spread Spectrum Cellular Systems; Telecommunications Industry Association;
52
March 1999.
53
• TIA/EIA/IS-2000-1-A to 6, cdma2000®1 Family of Standards for Spread Spectrum
54
Systems; Telecommunications Industry Association; March 2000.
55
56
1
57
cdma2000® is the trademark for the technical nomenclature for certain specifications
58
and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as
59
60
1 3GPP2 TSG-S All-IP NAM

All-IP NAM Rev 3.0
TIA/EIA-124 1
• TIA/EIA-124-D, Wireless Radio Telecommunications Intersystem Non-Signaling Data 2
Communications (DMH); Telecommunications Industry Association; January 2002. 3

4
TIA/EIA-553 5
• EIA/TIA/IS-553, Mobile Station - Land Station Compatibility Specification; September 6
1989. 7
8
OTA 9
• TIA/EIA/IS-683-A, Over-The-Air Service Provisioning of Mobile Stations in Spread 10

Spectrum Systems, February 1997. 11
12
13
1.2 Terminology 14
15
This document uses the following “verbal forms” and “verbal form definitions”: 16
17
1. “should” and “should not” indicate items of interest that are highly desirable and 18
particularly suitable, without identifying or excluding other items; or (in the 19
negative form) indicate items of interest that are not desirable, are not particularly 20
suitable, or are not recommended but not prohibited, and 21
2. “may” and “may not” indicate items of interest that are optional but permissible 22
within the limits of this recommendation. 23

24
25
1.3 Assumptions 26
27
a. The architecture described in this document assumes the following protocols: 28
29
1. SIP (Session Initiation Protocol),
30
2. DIAMETER, and 31
3. MOBILE IP (i.e., IPv4 and/or IPv6). 32

33
b. The use, support, and interoperation of IPv4 and IPv6 in the All-IP network is currently 34
assumed in this document, but whether IPv6 should be used exclusively needs to be 35
strongly considered in ongoing work. 36
37
c. There are known bearer paths not shown in Figure 2.1 (e.g., bearer paths between the
38
Application Servers and the Border Router, the Application Servers and the Media
39
Resource Function Processor). Some of these interfaces are shown in additional
40
diagrams in this document, but not numerically labeled, see Section 3.
41
d. There are known signaling paths not shown in Figure 2.1 (e.g., signaling paths between 42
two Call Session Control Functions (CSCFs), two AAA, an external SIP entity beyond 43
the Border Router and the CSCF). Some of these interfaces are shown in additional 44
diagrams in this document, but not numerically labeled, see Section 3. 45
46
47
1.4 Architectural Principles 48
49
The statements contained in this section should guide the development of the All-IP network 50
architecture. While these statements are too general to be treated as specific requirements, 51
they form a set of principles meant to govern the overall development of the All-IP network, 52
they are: 53
54
55
56
of the date of publication), cdma2000® is a registered trademark of the 57
Telecommunications Industry Association (TIA-USA) in the United States. 58
59
60
3GPP2 TSG-S All-IP NAM 2

All-IP NAM Rev 3.0
a. The All-IP network architecture should be independent of the underlying Layer 1 and
1
Layer 2 protocols through the use of IP-based protocols.
2
3 b. The All-IP core network should be independent of the access network. The core network
4 should have the ability to support multiple access network technologies (e.g., cable, radio
5 access technologies, wireless LAN, DSL).
6
7 The core network should have the ability to support access networks as they evolve and
8 as new access technologies are identified. This implies that network functions such as
9 call control and service control should be independent of access functions. How this
10 independence is maintained for mobility management and location-based services (which
11 may be dependent on access technology) is for further study.
12
13 c. A phased migration of existing networks to the All-IP network should be possible.
14
15
d. All pertinent interfaces in the All-IP network should be defined in an open manner.
16
e. The All-IP network should promote efficient use of radio interface resources.
17
18 f. The All-IP network should be capable of supporting reliability levels equal to or better
19 than those found in legacy networks.
20
21 g. The All-IP network should support capabilities for rapid service creation, including
22 service creation by the user and by third parties as well as service profile customization
23 by end users.
24
25
h. The All-IP network should permit separate signaling and bearer paths.
26
i. The All-IP network architecture and protocols should be scalable.
27
28 j. The All-IP network architecture development process should aim to identify and reuse
29 solutions from other initiatives within the IMT-2000 family (especially 3GPP), whenever
30 possible and reasonable.
31
32 k. The All-IP network should support Quality of Service equal to or better than that found
33 in legacy networks.
34
35 l. The All-IP network architecture should be defined in terms of separate functions and
36 clear interfaces such that it is possible to separate bearer from signaling.
37
m. The All-IP network should be functionally designed to allow and encourage reduced
38
39
complexity and/or resource utilization.
40
n. The All-IP network should support a range of terminal types (e.g., voice-only terminals,
41
IP Multimedia terminals, laptop computers). Not all these terminals may be able to
42
support end-to-end IP capabilities (e.g., 2G and 3G legacy terminals).
43
44 o. The All-IP architecture should be designed in such a way that a migration from IPv4 to
45 IPv6 is feasible and that IPv4 and IPv6 based All-IP networks may interoperate.
46
47
48 1.5 Legend
49
50 This section provides a definition of the different styles of lines and rectangles used in
51 many figures within this recommendation, as:
52
Dashed Line Signaling interface,
53
54 Dashed Rectangle Collective Network Entity and Composite Network Entity,
55 Heavy Dashed Line Radio Link (air interface),
56
57
Solid Line Circuit Bearer or Packet Bearer interface, and
58 Solid Rectangle Network Entity.
59
60

All-IP NAM Rev 3.0
1.6 Definitions 1
2
3
This section provides definitions of some terms used within this document, as: 4
5
Quality of Service (QoS) 6
7
QoS refers to a set of capabilities that a network may provide to a communications 8
session. These capabilities can be specified so that particular applications (e.g., voice, 9
video, streaming audio) fulfill human factors or other requirements with respect to 10
fidelity and performance. 11

12
QoS in a packet network consists of at least the following components: 13
a. Bandwidth: Data rate (e.g., 64 kbps), 14

15
b. Delay: End-to-end or roundtrip latency (e.g., 300 ms), 16
c. Jitter: Inter-packet latency variation (e.g., 10 ms), and 17
18
e. Loss: Rate at which packets are dropped (e.g., 3%).
19
Additionally, this QoS may be: 20

21
a. unidirectional or bidirectional, 22
b. guaranteed or statistical, 23
24
c. end-to-end or limited to a particular domain or domains, and
25
e. applied to all traffic or just to a particular session or sets of sessions. 26
27
Wireless Network Operator (WNO) 28

29
30
A network operator offering wireless services using the architecture defined by 3GPP2.
31
This architecture may also support other access technologies.
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

All-IP NAM Rev 3.0
1
1.7 Abbreviations
2
3
This section provides a definition of the abbreviations used within this recommendation, as:
4 AAA Authentication, Authorization, and MS Mobile Station
5 Accounting
6 API Application Programming MSC Mobile Switching Center
7 Interface
8 AGW Access Gateway NAI Network Access Identifier
9
AS Application Server NML Network Management Layer
10
BGCF Breakout Gateway Control OSA Open Service Access
11
Function
12
BML Business Management Layer OSA- OSA - Service Capability Server
13
SCS
14
BR Border Router OSF Operations Systems Function
15
16 BSC Base Station Controller OSS Operations Support System
17 BTS Base Transceiver System OTAF Over the Air Activation Function
18 CoA Care of Address PCF Packet Control Function
19 CSCF Call Session Control Function P-CSCF Proxy CSCF
20 DB Database PDE Position Determining Entity
21
DSI Dynamic Subscriber Information PDSN Packet Data Service Node
22
EIR Equipment Identity Register PDF Policy Decision Function
23
EML Element Management Layer PSTN Public Switched Telephone
24
Network
25
26
FA Foreign Agent QoS Quality of Service
27 HA Home Agent RAN Radio Access Network
28 HLR Home Location Register RNC Radio Network Controller
29 IMS IP Multimedia Subsystem SCE Service Creation Environment
30 IP Internet Protocol SCP Service Control Point
31 IPv4 Internet Protocol Version 4 SGW Signaling Gateway
32
IPv6 Internet Protocol Version 6 SIBB Service Independent Building
33
Block
34
I-CSCF Interrogating CSCF SIP Session Initiation Protocol
35
MAP Mobile Application Part SLA Service Level Agreement
36
37
MC Message Center SML Service Management Layer
38 ME Mobile Equipment SMS Service Management System
39 MGW Media Gateway S-CSCF Serving CSCF
40 MGCF Media Gateway Control Function TE Terminal Equipment
41 MM Mobility Manager UIM User Identity Module
42 Multimedia Domain
MMD UTRAN Universal Terrestrial Radio
43 Access Network
44 Managed-Network Entity Wireless Intelligent Network
M-NE WIN
45
MRFC Media Resource Function WLAN Wireless Local Area Network
46
Controller
47
MRFP Media Resource Function WNO Wireless Network Operator
48
Processor
49
50
51
NOTE to the Reader: The NAM (Network Architecture Model) has made the following name changes
52
after version 2.0.0: SCM (Session Control Manager) has become CSCF (Call Session Control Function),
53 NCGW (Network Capability Gateway) has become OSA-SCS (Open Service Architecture – Service
54 Capability Server), and Service Application has become Application Server. Also, the SQM (Subscription
55 Quality of Service Manager) and associated reference points 5 and 9 have been removed. The CQM
56 (Core Quality of Service Manager) has been renamed the PDF (Policy Decision Function).
57
58
59
60

All-IP NAM Rev 3.0
1
2
2. ARCHITECTURE MODELS 3
4
5
Architecture models are a graphical tool used to visualize, structure, and describe 6
certain complex subjects. A few such models are widely used in the 3GPP2 wireless 7
recommendations. 8
9
10
2.1 3GPP2 Wireless All-IP Network Architecture Model 11
12
Figure 2.1 presents the network entities and associated reference points that comprise a 13
wireless All-IP network. The network entities are represented by squares and rectangles; 14
the interfaces between network entities are reference points identified by numbers. The 15
network architecture model in this document is the compilation of several architecture 16
models currently in use in 3GPP2 wireless recommendations. 17
18
19
Note the following: 20

21
a. The network architecture model is a functional block 22

23
diagram. 24
25
b. A network entity represents a group of functions, not a 26
physical device. The physical realization is an implementation 27
issue; a manufacturer may choose any physical 28
implementation of network entities, either individually or in 29

30
combination, as long as the implementation meets the 31
functional requirements. Sometimes, for practical reasons, the 32
functional network entity is a physical device. The Mobile 33
Station (MS) is an excellent example. 34

35
c. A reference point is a conceptual point that divides two 36
groups of functions. It is not necessarily a physical interface. 37

38
A reference point only becomes a physical interface when the 39
network entities on either side of it are contained in different 40
physical devices. One or more interfaces may be defined to 41
support each reference point. 42

43
d. A reference point may or may not be standardized. This is a 44

45
subject for further study, for each particular reference point. 46
47
e. An interface is comprised of a standardized set of procedures, 48
messages, and protocols. Interface specification is beyond the 49
scope of this document. 50
51
f. A “Collective Entity” contains encompassed network entities 52
that are an instance of the collective (e.g., cdma2000 Access 53
Network). 54
55
g. A “Composite Entity” contains encompassed network entities 56

57
that are part of the composite (e.g., Mobile Station). 58
59
60

All-IP NAM Rev 3.0
1
Network OSA SIP
2
3
EIR DSI Subscription
Profile
Policy
Rules ... Application Application
4
Databases
Server Server
5
6 1 2 3 4 6 8/OSA-API 12/ISC 5/Mk
m3
7
8
OSF- Breakout
9
OSA Service
10 Network Gateway
Capability
11 Management Control
Server
12 Layer / OSS 11/Sh 10 Function
13
14 m2 m4 11/Sh 12/ISC 9/Mi 49/Mj
15
16
OSF Element Call Session Policy
17
Position
18 Management
15
AAA Control Decision
19 Layer Server 16/Cx Function 50 Function
20 17/Mg
21 18 19 20 21 22 24/Mr 28/Go
22
m1 29
23
Media Media
24 Managed Position
Resource Gateway
25
Network Determining
26 Function Control
Entity Entity
27 Controller Function
28
25/Mp 26/PSTN
29
30/Mc
30 27
31 cdma2000 Access Network Media
Access
32 Gateway Resource Media
33 BSC/RNC 31 32/Mb Function 33/Mb Gateway
BTS
34 + PCF Processor
35 35 37/Mb
36
36/Mb 38/Mb 40/Mb
37 MM
38 FA /
Attendant 41
Mobile IP 42/Mb
39
Border
40 Home
Other Access Networks 43/Mb 44/Mb Router
41
Agent
42
43
45/Mb
48 46/Mb
44
45 47/Um 39 34/Mb
46
MAP IP
47
Mobile Legacy MS Domain PSTN Network
48 TIA/EIA-41
Station 14 Support 13
49
50
51
52
53 Figure 2.1 3GPP2 Wireless All-IP Network Architecture Model
54
55
56
57
58
59
60

All-IP NAM Rev 3.0
2.1.1 Network Entities 1

2
3
Each network entity may be a physical device, it may form part of a physical device, or
4
it may be distributed over a number of physical devices.
5
6
Access Gateway (AGW) 7

8
The AGW is a network component that should support both the Multimedia and Legacy 9
MS Domains. The CDMA20002 Access Gateway (AGW) consists of the Packet Data 10
Service Node (PDSN) and other logical functions required to interface the core network 11
to the CDMA2000 Radio Access Network (RAN). 12

13
The AGW provides the Core Network (CN) with access to the resources of the Access 14
Network. The AGW presents the CN with a common interface to the specific 15
capabilities, configuration, and resources of the numerous Access Network 16
technologies. An Access Gateway performs the following functions: 17

18
IP Multimedia Domain: 19
a. supports inter-access gateway handoffs, 20

21
b. provides Foreign Agent (IPv4) and/or Attendant (IPv6) functionality, 22
c. includes the link layer peer function for link layer termination of the IP traffic 23
from and to the Mobile Station (e.g., PPP [Point-to-Point Protocol]), 24
25
e. provides the interface to access network functions (e.g., the PCF function of
26
the BSC/RNC+PCF),
27
f. transports bearer streams (containing both upper layer signaling and user 28
traffic) between the mobile station and the core network, 29
30
g. provides access to network level registration and authentication for the mobile
31
station (e.g., Mobile IP registration),
32
h. communicates with the AAA for user authentication, access authorization to 33
the core network, and accounting, 34
i. communicates with the Policy Decision Function (PDF) for management of 35
QoS resources, 36
37
j. supports link layer handoffs between homogeneous access networks supported 38
by the same AGW, 39
k. may support link layer handoffs among access networks of differing 40
technologies when the Access Networks are supported by the same access 41
gateway, 42
43
l. maps Network Access Identifiers (NAIs) into mobile station identifiers,
44
m. propagates appropriate policy decision information to the Access Network for 45
enforcement within the Access Network, 46
n. may intercept the QoS requests from the mobile station. QoS allocation 47
requests may be forwarded to the Policy Decision Function (PDF) for 48

49
authorization. If successfully authorized, the QoS allocation request may be
50
forwarded toward the request’s final destination,
51
o. may mark packets from mobile station as per QoS profile, 52
p. enforces policy decisions for authorized services, and 53

54
55
56
2
cdma2000® is a registered trademark of the Telecommunications Industry 57
Association (USA-TIA). 58
59
60

All-IP NAM Rev 3.0
q. gathers accounting information from the Access Network and forwards it to the
1
Accounting Function along with accounting information maintained by the
2
AGW.
3
4
Legacy MS Domain:
5
6 a. Supports packet data services for cdma2000 legacy mobile stations.
7
The 3GPP2 AGW is one of numerous types of access gateways (e.g., CDMA2000
8
RAN, UTRAN, 802.11, wireline, etc.).
9
10
The AGW is connected via Reference Points (see Section 2.1.2):
11
12
19. Position Server (signaling [Multimedia Domain only]),
13 21. AAA (signaling),
14
28/Go. Policy Decision Function (signaling),
15
16 31. cdma2000® Access Network (bearer streams),
17 32/Mb. Media Resource Function Processor (bearer streams),
18
19
35. cdma2000® Access Network (signaling),
20 36/Mb. Media Gateway (bearer streams [Multimedia Domain only]),
21
41. Mobile IP Home Agent (signaling),
22
23 43/Mb. Mobile IP Home Agent (bearer streams), and
24 45/Mb. Border Router (bearer streams).
25
26
27 Access Network
28
29 The Access Network is a network component that may support both the Multimedia and
30 Legacy MS Domains.
31
32
The access network may perform mobility management functions for registering,
33
authorizing, authenticating and paging IP based terminals, independent of circuit based
34
terminals. The access network may perform handoffs within an access network and
35 between access networks of the same technology and may support handoffs between
36 access networks of differing technologies.
37
38
cdma2000 Access Network:
39
40 The cdma2000 Access Network contains:
41
42 Base Transceiver System (BTS)
43
44
The BTS is an entity that provides transmission capabilities across the Um
45 reference point. The BTS consists of radio devices, antenna and equipment.
46
47 Base Station Controller (BSC)
48
49 The BSC is an entity that provides control and management for one or more
50 BTSs.
51
52 In support of the IP Multimedia Domain, the BSC/PCF interfaces to the Access
53 Gateway to support bearer streams between the terminal and the IP Multimedia
54 core network.
55
56
57 In support of the Legacy MS Domain (LMSD), the BS may initiate the QoS
58 allocation request. The QoS allocation request uses the address of the Media
59
60

All-IP NAM Rev 3.0
Gateway and QoS parameters provided by the LMSDS. Additionally, the BSC 1
exchanges messages with the BTS, other BSCs, AGW, and the LMSDS. 2
Signaling for call control, mobility management, and MS management as well 3

4
as traffic may pass transparently through the BSC.
5
6
Mobility Manager (MM) 7
The IP Multimedia Domain MM function’s responsibilities include: 8

9
a. Handling registration messages from the Mobile Station for the 10
establishment of logical bearers through the IP Multimedia Domain 11
core network, 12
b. Communicating with the AAA for access network authentication, 13
authorization of radio link access and accounting. Example of 14
accesses that MM should authenticate and/or authorize with the AAA 15
include multimedia registration, multimedia page response, inter-radio 16
access network handoff, and 17

18
c. Supporting hard handoff within and between access networks when 19
possible. 20
21
NOTE: The functionality of the MM is under study.
22
The MM has a signaling relationship with the BSC/RNC + PCF. 23
24
Packet Control Function (PCF) 25
26
The PCF function’s responsibilities include:
27
a. establish maintain and terminate layer-2 connection to the Access 28
Gateway (AGW), 29
b. interact with AGW to support dormant handoff, 30

31
c. maintain knowledge of radio resource status (e.g., active, dormant), 32
d. buffer packets arriving from the AGW, when radio resources are not 33
in place or are insufficient to support the flow from the AGW, 34
35
e. relay packets to and from the AGW,
36
f. map mobile station ID and connection reference to a unique layer-2 37
connection identifier used to communicate with the AGW, and 38
g. collect and send radio link (air interface) related accounting 39
information to the AGW. 40

41
The cdma2000 Access Network is connected via Reference Points (see Section 42
2.1.2): 43
44
2. Databases (signaling),
45
20. AAA (signaling [Multimedia Domain only]), 46
27. Media Gateway (bearer streams [Legacy MS Domain only]), 47

48
31. Access Gateway (bearer streams), 49
35. Access Gateway (signaling), 50
51
47/Um. Mobile Station (Radio Link [air interface]), and
52
48. Legacy MS Domain Support (signaling [Legacy MS Domain only]). 53
54
Other Access Network: 55
56
For example WLAN (Wireless Local Area Network). 57
58
59
60

All-IP NAM Rev 3.0
1
Authentication, Authorization and Accounting (AAA)
2
The AAA is a network component that should support both the Multimedia and Legacy
3
MS Domains.
4
5
The AAA provides IP based Authentication, Authorization, and Accounting functions.
6
The AAA maintains security associations with peer AAA entities to support intra-
7
and/or inter-administrative domain AAA functions.
8
9
10 Authentication Function
11
12 The Authentication Function of the AAA provides Authentication of terminal
13 devices and subscribers.
14
15 The Authentication Function:
16 a. verifies an entity’s identity for network access, QoS request, multimedia
17 resource request, or service request, and
18
19
b. provides authentication and/or encryption keys to establish dynamic
20
security associations between network entities.
21
22
Authorization Function
23
24
The Authorization Function of the AAA provides authorization of requests for
25
services and/or bandwidth, etc. and has access to the Policy Repository, the
26
Directory Services, Subscriber Profiles, and the Device Register.
27
28 The Authorization Function provides the authorization decision for services,
29 bandwidth, etc. The Authorization Function answers the question (yes or no)
30 whether a user or device is authorized for a particular service, and to what levels
31 that service may be used.
32
33 The service authorization request may come from the Call Session Control
34 Function once the Call Session Control Function (in the case of a multimedia
35 session) has determined the specific service to be provided.
36
37 An entity that requests authorization from the AAA entity may receive a set of
38 information that allows it to make further decisions concerning services and/or
39 bandwidth, etc.) without a new request to the AAA entity (i.e., the requesting entity
40 may be able to cache authorization information from the AAA entity). Cached
41 information may have an assigned expiration time. The AAA entity may send
42 unsolicited messages containing policy decisions to appropriate entities.
43
44
Note: The OSA Service Capability Server, in conjunction with AAA, is responsible
45
for guaranteeing proper authorization for access to all resources for all OSA
46
Application Server requests. There are still outstanding concerns related to privacy
47
applications and/or conditions that cannot be satisfied by an initial authorization
48 from AAA which are not fully known at this time and must be further investigated
49 by the applicable TSGs.
50
51
Accounting Function
52
53
The Accounting Function of the AAA gathers data concerning the services, QoS,
54
and multimedia resources requested and used by individual subscribers.
55
56
57
58
59
60

All-IP NAM Rev 3.0
The Accounting Function: 1

2
a. records session details (e.g., requesting party, requested services, actual 3
services used, date and time of requests, duration of usage, QoS used, 4
terminal used), 5
b. records mobility (e.g., administrative domain location, date and time of 6
attach, date and time of detach), 7

8
c. collects session details from various sources (e.g., CSCF, other
9
Accounting Servers), 10
d. allows session details to be retrieved for further processing, and 11
12
e. provides accounting information to downstream OAM&P functions (e.g.,
13
Billing Management).
14
15
The AAA is connected via signaling Reference Points (see Section 2.1.2): 16
4. Databases [Network Policy Rules, Subscriber Profile], 17

18
11/Sh. OSA Service Capability Server and SIP Application Server 19
[Multimedia Domain only], 20
15. Position Server, 21
22
16/Cx. Call Session Control Function [Multimedia Domain only],
23
24
Editorial Note: The impacts of 1xEVDO on RF-20 are TBD. 25
26
20. cdma2000 Access Network [Multimedia Domain only], 27
28
21. Access Gateway,
29
22. Mobile IP Home Agent, and 30
--- between Local AAA and Home AAA servers (not shown in NAM 31
Figure 2.1; see “gg” Section 3.1). 32

33
34
Application Server 35
36
The Application Servers are network components that may support both the Multimedia 37
and Legacy MS Domains. 38
39
These services may be accessed via the OSA Service Capability Server (OSA-SCS) or 40
accessed directly from the user’s mobile station via other network entities. See section 41
3.1.4 for details on Application Server usage. 42
43
The OSA Application Server (OSA-AS) is connected via signaling Reference Points 44
(see Section 2.1.2): 45
46
8/OSA-API. OSA Service Capability Server, and
47
--- between the OSA Application Server and the IP Multimedia Client 48
([Multimedia Domain only], not shown in Figure 2.1; see “ii” 49
Section 3.1.4). 50
51
The SIP Application Server (SIP AS) is connected via signaling Reference Points (see 52
Section 2.1.2): 53
54
11/Sh AAA [Multimedia Domain only], 55
12/ISC. CSCF [Multimedia Domain only], and 56
57
--- between SIP AS and IP Multimedia Client ([Multimedia Domain
58
only], not shown in Figure 2.1; see “ii” Section 3.1.4).
59
60

All-IP NAM Rev 3.0
Notes:
1
2 The distribution of an Application Server may consist of any of the
3 following combinations:
4 a. all Application Servers may be hosted in a single server, or
5
6
b. one Application Server may be hosted in a constellation of servers.
7
An Application Server refers to:
8
9
a. a "Home Application Server" (i.e., owned and executed by the
10
home service provider who may or may not be the home WNO),
11 b. a "Third Party Application Server" (i.e., owned and executed by a
12 third party, but uses the resources of the WNO network), and/or
13
c. a "Local Application Server" (i.e., owned and executed by the
14
15
visited WNO).
16
Application servers use their underlying MMD network resources through
17
the following two interfacing categories.
18
19 a. SIP Application Servers: SIP application servers providing
20 service control interact directly with the network elements such as
21 the S-CSCF, and the AAA. These servers include Multimedia
22 Domain (MMD) in-house and trusted SIP-based multimedia
23 application servers offering both service content and service
24 control.
25
b. OSA Application Servers: The OSA application servers interact
26
indirectly with the network elements via the OSA Application
27
Programming Interface (OSA API) to the OSA Service Capability
28
Server (SCS) in the OSA SCS. This category of application
29
servers provides all applications that are independent from their
30
underlying core network technology, and are delivered via the use
31
of an open standardized API. In this scheme, Network APIs open
32
up access to core network capabilities and resources towards 3rd
33
party application providers all the while ensuring network integrity.
34
35 This access to network capabilities is achieved by defining an
36 abstracted set of network functionalities in terms of a series of
37 generic Service Capability Features (SCFs), and by specifying an
38 OSA-API interface between the application server (OSA-AS) and
39 the OSA-SCS. This arrangement is to provide access to the
40 network elements in order to build applications. On the network
41 side, the OSA-SCS interfaces with its underlying network
42 protocols. In this way, applications and their service control
43 protocols become independent from the underlying network
44 technology.
45
46
47
Border Router (BR)
48
The BR is a network component that should support both the Multimedia and Legacy
49
MS Domains.
50
51 The BR connects the Core Network with peer networks (e.g., other service providers,
52 corporate networks, Internet). The BR performs IP packet routing, exterior gateway
53
routing protocols, and policing of incoming and outgoing traffic, ensuring traffic
54
complies with defined Service Level Agreements established with peer networks. The
55
BR may intercept any QoS allocation request, and issue a request to the Policy Decision
56
Function (PDF), which should verify that the requested inbound and/or outbound QoS
57
58
59
60

All-IP NAM Rev 3.0
is available. A successful response from the PDF may cause the BR to forward the 1
bandwidth allocation request to its final destination. 2

3
The BR is connected via Reference Points (see Section 2.1.2): 4
5
29. Policy Decision Function (signaling),
6
40/Mb. Media Gateway (bearer streams), 7
42/Mb. Media Resource Function Processor (bearer streams), 8

9
44/Mb. Mobile IP Home Agent (bearer streams), 10
45/Mb. Access Gateway (bearer streams), and 11
12
46/Mb. IP Network (bearer streams).
13
14
Breakout Gateway Control Function (BGCF) 15
16
The BGCF is a network component that applies only to the Multimedia Domain. 17
18
The BGCF selects the network in which PSTN breakout is to occur and, within the
19
network where the breakout is to occur, selects the MGCF.
20
The BGCF is connected via signaling Reference Points (see Section 2.1.2): 21
22
9/Mi. S-CSCF, 23
49/Mj. MGCF, and 24
25
5/Mk. BGCF.
26
27
Call Session Control Function (CSCF) 28
29
The CSCF is a network component that applies only to the Multimedia Domain. 30
31
The CSCF establishes, monitors, supports, and releases Multimedia sessions and 32
manages the user's service interactions. The CSCF is responsible for: 33
34
a. managing the allocation of required resources such as announcement 35
servers, multi-party bridges, etc., 36
b. maintaining knowledge of session states and user's service precedence, 37
38
c. querying the AAA for authentication information and user profile
39
information, and
40
d. performing session processing tasks (e.g., network selection) required for 41
session completion. 42
43
The CSCF entity in the home network is responsible for session control, as described 44
above. The P-CSCF is used to proxy requests from the mobile station to an CSCF in the 45
home network and to return responses from the home network to the mobile station. 46
47
The CSCF entity in the home network may be further divided into an Interrogating-Call
48
Session Control Function (I-CSCF) and a Serving- Call Session Control Function (S-
49
CSCF). The reason for this could be load sharing and/or hiding of the internal network
50
structure, or for allocation of an S-CSCF close to the mobile station. The I-CSCF
51
would in such a case be the entry point to the network, responsible for locating the S-
52
CSCF serving the user, while the S-CSCF is the entity actually keeping the session 53
state. 54
55
The communication between the CSCF and AAA may include the passing of addresses
56
and security tokens necessary for the CSCF to communicate with other CSCF entities.
57
Other techniques may also apply that allow an CSCF to determine the address of
58
another CSCF entity.
59
60

All-IP NAM Rev 3.0
The S-CSCF has access to Subscriber Profiles.

1
2 The CSCF uses information from various databases (e.g., subscriber profile) and
3 invocation of various services applications to determine the exact service being
4 requested.
5
6 The CSCF is connected via signaling Reference Points (see Section 2.1.2):
7
12/ISC. OSA Service Capability Server/SIP Application Server,
8
9
16/Cx. AAA [Authorization Function],
10 17/Mg. Media Gateway Control Function,
11
24/Mr. Media Resource Function Controller,
12
13 --- between P-CSCF and I-CSCF ([not shown in Figure 2.1; see
14 “dd/Mw” Section 3.1.4]),
15
--- between P-CSCF and S-CSCF ([not shown in Figure 2.1; see
16
“dd/Mw” Section 3.1.4]),
17
18
9/Mi between BGCF and S-CSCF (also see Section 3.1.4),
19 50 between P-CSCF and PDF,
20
--- between I-CSCF and S-CSCF [not shown in Figure 2.1; see “ff/Mw”
21
Section 3.1.4]), and
22
23 --- between IP Multimedia Client and P-CSCF [not shown in Figure 2.1;
24 “hh/Gm” see Section 3.1.4]).
25
26
27
Databases (DB)
28
29
The DB is a network component that may support both the Multimedia and Legacy MS
30
Domains.
31
The information in the core network DBs may include but is not limited to EIR,
32
Dynamic Subscriber Information, Network Policy Rules and Subscriber Profile data.
33
34
35 EIR (Equipment Identity Register)
36
37 The EIR is a database of equipment information, including but not limited to a
38 record of stolen equipment. The nature, purpose and utilization of the EIR
39 information is for further study.
40
41
42 Dynamic Subscriber Information
43
44 The Dynamic Subscriber Information database contains the current session
45 registration information (e.g., the serving Call Session Control Function
46 address).
47
48
49
Network Policy Rules
50
The Network Policy Rules database provides the policy rules for subscription
51
resource usage, expected QoS, valid times and routes, geographical service
52
area definitions, policy rules for the applications serving a user, etc. The
53
54
Network Policy Rules database also provides network wide policy rules
55
specified by the operator to control the network.
56
The Network Policy Rules database is a data repository referenced by the
57
Authorization Function of AAA, and the Policy Decision Function.
58
59
60

All-IP NAM Rev 3.0
Subscriber Profile 1
2
3
The Subscriber Profile database contains subscriber specific information that
4
identifies items as: authorized features, authorized services, authorized service
5
area and credit worthiness.
6
The Databases are connected via signaling Reference Points (see Section 2.1.2): 7
8
1. Position Server [Multimedia Domain only], 9
2. cdma2000 Access Network, 10
11
3. Policy Decision Function,
12
4. AAA, and 13
6. Legacy MS Domain Support [Legacy MS Domain only]. 14

15
16
IP Multimedia Client 17
18
The IP Multimedia Client is an IP application that resides in the MS and applies only to
19
the Multimedia Domain.
20
The IP Multimedia Client communicates with Application Servers, P-CSCFs, and other 21
IP Multimedia Clients. 22
23
The IP Multimedia Client is not shown in Figure 2.1, see Section 3.1.4. 24
25
The IP Multimedia Client is connected via signaling Reference Points (not shown in 26
Figure 2.1; see Section 3.1.4): 27
hh/Gm. Proxy-Call Session Control Function, and 28

29
ii. Application Servers. 30
31
IP Network 32
33
The IP network is a network component that should support both the Multimedia and 34
Legacy MS Domains. 35
36
The IP network corresponds to IP based packet data networks that provide a transport 37
mechanism between the core network and external IP networks. IP Network represents 38
packet networks connected to the core network including the public Internet, private IP 39
backbone networks and private IP networks such as a corporate Intranets. 40

41
The IP Network is connected via signaling and bearer streams Reference Points (see 42
Section 2.1.2): 43
44
46/Mb. Border Router.
45
46
Legacy MS Domain Support (LMSDS) 47
48
The LMSDS is a network component that applies only to the Legacy MS Domain. 49
50
The LMSDS contains functional network components supporting the Legacy MS 51
Domain; including: 52
Home Location Register emulation (HLRe), 53

54
Mobile Switching Center emulation (MSCe), and 55
Service Control Point emulation (SCPe). 56
57
The SCPe component of LMSDS may also support the Multimedia Domain users’ 58
access to legacy features. 59
60

All-IP NAM Rev 3.0
The LMSDS performs the call control, mobility management, and service management
1
functions to provide support for non-IP (i.e., legacy) MSs. The LMSDS is responsible
2
for the control of mobile originated and mobile terminated calls. The LMSDS
3
terminates the user-network signaling and converts it into the appropriate network-
4
network signaling. The LMSDS also controls the connections for bearer channels in a
5
Media Gateway connected to a BSC in the Access Network.
6
7 Note: The LMSDS requires an authentication function capable of supporting legacy
8
authentication methods. The placement of that authentication function is for further
9
study. An interface to the HLRe should be necessary.
10
11 Note: The LMSDS requires a VLR type function. The placement of the VLR is for
12 further study.
13
14 Note: The LMSDS requires existing functionality (e.g., OTAF, MC) to support legacy
15 capabilities. The placement of these functions is for further study. The sharing of these
16 functions between the Legacy MS and Multimedia Domains is for further study.
17
18 The Legacy MS Domain Support contains network entities:
19
20 Home Location Register emulation (HLRe)
21
22
The HLRe is a network entity that supports non-IP Terminals (legacy MSs) in
23
an IP network. The HLRe differs from an HLR in its interfaces and its
24
functionality. The HLRe has IP signaling interfaces. For legacy and dual
25
mode MSs (e.g., multimedia mode capable MSs and legacy mode capable
26
MSs), the HLRe supports roaming to legacy networks and to Legacy MS
27 Domains of IP networks.
28 The HLRe manages the subscriber profile for both voice services (e.g., Call
29 Forwarding, Three Way Calling, Message Waiting Notification and data
30 services (e.g., Priority). Subscriber profile information may be accessed from
31 the HLRe or may be downloaded to a serving system as needed.
32
33
The HLRe manages subscriber location and/or accessibility information. This
34
includes updating the dynamic subscriber information database with current
35
domain information (e.g., MSCe address) and with MS status information (e.g.,
36
SMS pending flag). The HLRe interacts with the location database to update
37 or retrieve current location information.
38
39
Mobile Switching Center emulation (MSCe)
40
41 The MSCe provides processing and control for calls and services. The MSCe
42 provides signaling capabilities comparable to those of a legacy MSC but has
43 only bearer management capabilities. The MSCe:
44
a. establishes, manages, and releases calls and connections (e.g., uses IP
45
signaling to: setup calls between MSCes, control bearer resource
46
allocation, control network resources such as tones and
47
48
announcements),
49 b. provides trigger mechanisms to access WIN and other service
50 application functionality,
51
c. modifies call and connection processing functions under the control of
52
service logic, and
53
54 d. provides interworking functions between TIA/EIA-41 and IP
55 signaling protocols.
56
57
58
59
60

All-IP NAM Rev 3.0
Service Control Point emulation (SCPe) 1

2
The SCPe commands call control functions in the processing of WIN provided 3
and custom service requests. The SCPe may interact with other functional 4
entities to access additional logic or to obtain information (service or user data) 5
required to process a call and service logic instance. The SCPe: 6

7
a. interacts with the MSCe, 8
b. contains the logic and processing capability required to handle 9
Wireless Intelligent Network (WIN) provided service attempts, 10
11
c. interacts with other SCPes and Application Servers for secured data
12
acquisition and manipulation, distributed service control and
13
unsolicited service notifications, if necessary, and
14
d. interacts with the databases for data acquisition and manipulation. 15
16
The LMSDS is connected via signaling Reference Points (see Section 2.1.2): 17
6. Databases, 18
19
13. PSTN,
20
14. MAP (TIA/EIA-41), 21
39. Media Gateway, 22

23
48. cdma2000 Access Network,
24
--- Position Server (not shown in Figure 2.1; see “jj” Section 3.4), 25
--- OSA Service Capability Server (not shown in Figure 2.1; see “kk” 26
27
Section 3.4),
28
--- Media Resource Function Processor (not shown in Figure 2.1; see 29
“xx” Section 3.4 [Legacy MS Domain only]), and 30
--- other LMSDSs (not shown in Figure 2.1; see “zz” Section 3.4 31
[Legacy MS Domain only]). 32

33
34
Managed Network Entity (M-NE) 35
36
A M-NE within the Collective Entity or any specific network entity (including 37
databases) having OS management needs, including another OS. 38
39
IP Multimedia Domain: 40
a. Supporting management capabilities as defined in S.S0028-A. 41
42
Legacy MS Domain: 43
a. Supporting management capabilities as defined in S.S0028-A. 44
45
The M-NE is connected via Reference Points (see Section 2.1.2): 46
m1. OSF-EML. 47
48
Managed Wireless Network Entity (MWNE) 49

50
51
A MWNE within the Collective Entity or any specific network entity having Operation
52
Systems (OS) wireless management needs, including another OS.
53
54
Media Gateway (MGW) 55

56
The MGW is a network component that should support both the Multimedia and Legacy 57
MS Domains. 58
59
60

All-IP NAM Rev 3.0
The MGW provides an interface between the packet environment of the Core Network
1
and the circuit switched environment of the PSTN for bearer traffic, when equipped
2
with circuit capabilities. The MGW may provide vocoding and/or transcoding
3
functions to the bearer traffic. The MGW may also provide modem functions to convert
4
digital byte streams to and from audio modem tones placed on circuits, and may provide
5
the capability to terminate PPP (Point-to-Point Protocol) connections. It also provides
6
policy enforcement relative to its activities and resources.
7
8 Since the MGW has the ability to connect to the IP-based core network environment as
9
well as the circuit-based PSTN environment, the resources provided by the MGW,
10
including transcoding resources, can be used to support bearer channels that are
11
contained entirely within the IP environment.
12
13 The MGW is connected via Reference Points (see Section 2.1.2):
14
27. BSC (bearer streams [Legacy MS Domain only]),
15
16 30/Mc. Media Gateway Control Function (signaling [Multimedia Domain
17 only]),
18
33/Mb. Media Resource Function Processor (bearer streams),
19
20
34/Mb. PSTN (bearer streams),
21 36/Mb. Access Gateway (bearer streams [Multimedia Domain only]),
22
38/Mb. Mobile IP Home Agent (bearer streams [Multimedia Domain only]),
23
24 39. Legacy MS Domain Support (signaling, [Legacy MS Domain only]),
25 40/Mb. Border Router (bearer streams), and
26
27
--- other MGWs (bearer streams, not shown in Figure 2.1; see “yy”
28
Section 3.4 [Legacy MS Domain only]).
29
30
Media Gateway Control Function (MGCF)
31
32
The MGCF is a network component that applies only to the Multimedia Domain.
33
34 The MGCF provides the ability to control a Media Gateway through standardized
35 interfaces. Such control includes allocation and deallocation of resources of the Media
36 Gateway, as well as modification of the usage of those resources.
37
38 The MGCF interfaces to the Media Gateway and to the Call Session Control Function.
39 The MGCF interface to the Call Session Control Function is for communicating session
40 control information (e.g., via a protocol like SIP). The MGCF interface to the PSTN is
41 for communicating signaling information to the PSTN (e.g., ISUP signaling). The
42 MGCF has the ability to translate between session based signaling within the All-IP
43 core network and ISUP signaling.
44
45 The MGCF is connected via signaling Reference Points (see Section 2.1.2):
46 17/Mg. Call Session Control Function,
47
48
26/PSTN. PSTN,
49 30/Mc. Media Gateway, and
50
49/Mj. Breakout Gateway Control Function.
51
52
53 Media Resource Function Controller (MRFC)
54
55 The MRFC is a network component that applies only to the Multimedia Domain.
56
57 The MRFC, in conjunction with the MRFP, provides a set of resources within the core
58 network that are useful in supporting services to subscribers. The MRFC, in
59
60

All-IP NAM Rev 3.0
conjunction with the MRFP, provides multi-way conference bridges, announcement 1
playback services, tone playback services, etc. 2

3
The MRFC controls allocation, de-allocation, and modification of the usage of 4
resources of the MRFP. 5
6
The MRFC is connected via signaling Reference Points (see Section 2.1.2): 7
24/Mr. Call Session Control Function, and 8

9
25/Mp. Media Resource Function Processor. 10
11
12
Media Resource Function Processor (MRFP) 13
14
The MRFP is a network component that may support both the Multimedia and Legacy 15
MS Domains. 16
17
The MRFP, in conjunction with the controlling entity, provides multi-way conference 18
bridges, announcement playback services, tone playback services, etc. 19
20
Bearer paths may go between the MRFP and network entities Access Gateway, Border
21
Router, Media Gateway, and Mobile IP Home Agent.
22
The MRFP is connected via Reference Points (see Section 2.1.2): 23

24
25/Mp. Media Resource Function Controller (signaling [Multimedia Domain 25
only]), 26
32/Mb. Access Gateway (bearer streams [Multimedia Domain only]), 27
28
33/Mb. Media Gateway (bearer streams),
29
37/Mb. Mobile IP Home Agent (bearer streams [Multimedia Domain only]), 30
42/Mb. Border Router (bearer streams), and 31

32
--- Legacy MS Domain Support (not shown in Figure 2.1; see “xx” 33
Section 3.4 [Legacy MS Domain only]). 34
35
Mobile IP Home Agent (HA) 36
37
The HA is a network component that should support both the Multimedia and Legacy 38
MS Domains. 39
40
The HA provides two major functions: registering the current point of attachment of the 41
user, and forwarding of IP packets to and from the current point of attachment (IPv4 42
Care of Address [CoA] and/or IPv6 Co-located CoA) of the user. The HA accepts 43
registration requests using the Mobile IP protocol and uses the information in those 44
requests to update internal information about the current point of attachment of the user, 45
i.e., the current IP address to be used to transmit and receive IP packets to and from that 46
user. The HA interacts with the AAA to process Mobile IP registration requests that 47
have been authenticated, and to return Mobile IP registration responses. The HA also 48
interacts with the Access Gateway to receive subsequent Mobile IP registration 49
requests. The HA may interact with several network entities in performing its work of 50
forwarding IP packets to the current point of attachment of the user. 51
52
53
54
55
56
57
58
59
60

All-IP NAM Rev 3.0
The HA is connected via Reference Points (see Section 2.1.2):

1
2 22. AAA (signaling),
3 37/Mb. Media Resource Function Processor (bearer streams [Multimedia
4 Domain only]),
5
6
38/Mb. Media Gateway (bearer streams [Multimedia Domain only]),
7 41. Access Gateway (signaling),
8
43/Mb. Access Gateway (bearer streams), and
9
10
44/Mb. Border Router (bearer streams).
11
12
Mobile Station (MS)
13
14
The MS is a network component that may support both the Multimedia and Legacy MS
15
Domains.
16
17 See Section 3.3 “Mobile Station View”.
18
19 The MS is connected via the Radio Link (air interface) Reference Point (see Section
20 2.1.2):
21
47/Um. Base Transceiver System.
22
23
24 Operations Systems Function (OSF)
25
26 The OSF is defined by the Telecommunications Management Network (TMN) OSF (see
27 ITU M.3100). These functions include Element Management Layer (EML), Network
28 Management Layer (NML), Service Management Layer (SML), and Business
29 Management Layer (BML) functions spanning across all operations systems functions
30 (e.g., Fault Management, Performance Management, Configuration Management,
31 Accounting Management and Security Management.
32
33
34 OSF – Element Management Layer (OSF-EML)
35
36 The OSF-EML covers Element Management Layer (EML) aspects and spanning
37 across all operations systems functions.
38
39
IP Multimedia Domain:
40 a. Supporting capabilities as defined in S.S0028-A.
41
Legacy MS Domain:
42
44
The OSF-EML is connected via Reference Points (see Section 2.1.2):
45
46
m1. M-NE,
47 m2. OSF-NML/OSS, and
48 m4. Databases.
49
50 OSF – Network Management Layer (OSF-NML/OSS)
51
52 The OSF-NML/OSS (Operations Support System) includes Network Management
53 Layer (NML), Service Management Layer (SML), and Business Management
54
Layer (BML) functions and spanning across all operations systems functions..
55
56 IP Multimedia Domain:
58
59
60

All-IP NAM Rev 3.0
Legacy MS Domain: 1
2
a. Supporting capabilities as defined in S.S0028-A.
3
The OSF-NML/OSS is connected via Reference Points (see Section 2.1.2): 4

5
m2. OSF-EML,
6
m3. OSF-NML/OSS, and 7
m4. Databases. 8
9
OSA Service Capability Server (OSA-SCS) 10
11
The OSA-SCS is a network component that may support both the Multimedia and 12
Legacy MS Domains. 13
14
The OSA-SCS provides access to network resources needed during service application 15
execution. The interface towards the Application Server uses application programming 16
interfaces such as Open Service Architecture (OSA). The interfaces towards other 17
network entities use the relevant protocols. 18
19
The OSA-SCS, in conjunction with AAA and the Position Server (for position related 20
requests), is responsible for guaranteeing proper authorization for access to resources. 21
Note: There are still outstanding concerns related to privacy applications and/or 22
conditions that cannot be satisfied by an initial authorization from AAA which are not 23
fully known at this time and must be further investigated by the applicable TSGs. 24
25
The OSA-SCS (for Legacy MS Domain Support) interfaces to Application Server and
26
Legacy MS Domain Support network entities and relays service application information
27
between these two network entities.
28
The OSA-SCS is connected via signaling Reference Points (see Section 2.1.2): 29
30
8/OSA-API. Service Application, 31
10. Position Server, 32
33
11/Sh. AAA,
34
12/ISC. Call Session Control Function [Multimedia Domain only], and 35
--- Legacy MS Domain Support [not shown in Figure 2.1; see “kk” 36
Section 3.4, Legacy MS Domain only]. 37

38
39
Policy Decision Function (PDF) 40
41
The PDF is a network component that applies only to the IP Multimedia Domain. 42
43
The PDF provides management of core network QoS resources within its own core 44
network necessary to support services to network users. It communicates with the 45
Access Gateway to provide authorization of resource allocations. The PDF makes 46
policy decisions with regard to use of core network QoS resources within its own 47
network, including consideration of Service Level Agreements (SLAs [Note, the 48
maintenance of SLAs is for further study.]). QoS policy information for network 49
resource utilization may be forwarded to and cached by the PDF. 50
51
PDF manages resources of the Border Router and Access Gateway that handle traffic 52
between low-speed networks (e.g., radio access network) and the high-speed backbone 53
core network. 54
55
Additionally, the PDF makes policy decisions based on information obtained from P-
56
CSCF.
57
58
59
60

All-IP NAM Rev 3.0
The PDF is connected via signaling Reference Points (see Section 2.1.2):
1
2 3. Database [Network Policy Rules],
3 28/Go. Access Gateway,
4
29. Border Router, and
5
6 50. P-CSCF.
7
8 Position Determining Entity (PDE)
9
10 The PDE is a network component that may support both the Multimedia and Legacy
11 MS Domains.
12
13
The PDE communicates with the Position Server to determine the precise geographic
14
position of the MS based on input data provided by the Position Server.
15 The PDE is connected via signaling Reference Point (see Section 2.1.2):
16
18. Position Server.
17
18
19
Editor’s Note: Regarding the PDE placement in the NAM issue (i.e., in the core
20
network, access gateway, or in the RAN), although it was agreed that
21
the PDE remain in the core network, the following considerations were
22 identified (see S00-20021209-119R1.):
23 - Consideration of the goal of core network independence from the radio
24 access technology and the need for the PDE to know how to obtain
25 the location of an MS that uses location technology that is dependant
26 on the RAN.
27
28
- Consideration of current location technology functionality distribution
29
in the NAM in light of possible WLAN inter-working in the future.
30
31
Position Server
32
33
The Position Server is a network component that may support both the Multimedia and
34
Legacy MS Domains.
35
36 The Position Server provides geographic position information to requesting entities.
37
38 The Access Gateway chooses a Position Server and requests registration for a particular
39 terminal. The Position Server is responsible for granting such registrations, forwarding
40 registration information to a proxy Position Server in the same network, if such a proxy
41 exists, and interfacing with the Access Gateway to obtain necessary information to
42 respond to position information requests. The Position Server selects a Position
43 Determining Equipment (PDE) based on the positioning capabilities of the MS (as
44 received from the Access Gateway). The (Proxy) Position Server interacts with the
45 AAA to authenticate and authorize position service requests. The Position Server may
46 cache the MS position.
47
48 The Position Server may simultaneously provide Proxy Position Server capabilities. In
49 that capacity, the Position Server may also interface to other Proxy Position Servers.
50
51
The Position Server is connected via signaling Reference Points (see Section 2.1.2):
52
53 1. Databases (DSI [Multimedia Domain only]),
54 10. OSA Service Capability Server [Multimedia Domain only],
55
56
15. AAA,
57 18. Position Determining Entity (PDE),
58
59
60

All-IP NAM Rev 3.0
19. Access Gateway [Multimedia Domain only], and 1

2
--- Legacy MS Domain Support (not shown in Figure 2.1; see “jj” 3
Section 3.4 [Legacy MS Domain only]). 4
5
6
Public Switched Telephone Network (PSTN) 7

8
9
The PSTN is a network component that may support both the Multimedia and Legacy
10
MS Domains (see Section 3.5 and Section 3.4, respectively).
11
The PSTN is defined in accordance with the appropriate applicable national and 12
regional standards. 13
14
The PSTN is connected via Reference Points (see Section 2.1.2): 15
13. Legacy MS Domain Support (signaling [Legacy MS Domain only]), 16

17
26/PSTN. Media Gateway Control Function (signaling [Multimedia Domain 18
only]), and 19
34/Mb. Media Gateway (bearer streams). 20

21
Signaling Gateway (SGW) 22

23
The SGW is a network component that may support both the Multimedia and Legacy 24
MS Domains. 25
26
The SGW function interconnects between the IP transport layer and the SS7 transport 27
layer for signaling. The SGW function is not shown in Figure 2.1. The SGW function 28
may reside within another entity or be a standalone entity. 29
30
31
2.1.2 Reference Points 32
33
An interface exists when two Network Entities are interconnected through exactly one 34
signaling or bearer stream Reference Point. The Reference Points and their associated 35
Network Entities are: 36
37
Reference Point 1 38
39
Reference Point 1 is the signaling interface between the Databases and the Position 40
Server [Multimedia Domain only]. 41

42
43
45
Reference Point 2 is the signaling interface between the Databases and the cdma2000 46
Access Network. 47
48
49
51
Reference Point 3 is the signaling interface between the Databases and the Policy 52
Decision Function [Multimedia Domain only]. 53
54
56
Reference Point 4 is the signaling interface between the Databases and the AAA. 57
58
59
60

All-IP NAM Rev 3.0
1
Reference Point 5/Mk
2
Reference Point 5/Mk is the signaling interface between Breakout Gateway Control
3
Functions [Multimedia Domain only].
4
5
6
7
8 Reference Point 6
9
10 Reference Point 6 is the signaling interface between the Databases and the Legacy MS
11 Domain Support [Legacy MS Domain only].
12
13
14
Reference Point 7
15
16
Reserved.
17
18
Reference Point 8/OSA-API
19
20
21 Reference Point 8/OSA-API is the signaling interface between the OSA Application
22 Server and the OSA Service Capability Server. Reference Point 8/OSA-API may
23 employ interfacing techniques that support a wide spectrum of capabilities, ranging
24 from secure (e.g., application programming interfaces such as Parlay, used for un-
25 trusted parties) to non-secure (e.g., used for trusted parties).
26
27
28
Reference Point 9/Mi
29
30
Reference Point 9/Mi is the signaling interface between the BGCF and the Serving-
31
CSCF [also see Figures 3.1.4b and 3.1.4c, Multimedia Domain only].
32
33
Reference Point 10
34
35
Reference Point 10 is the signaling interface between the Position Server and the OSA
36
Service Capability Server [Multimedia Domain only].
37
38
39 Reference Point 11/Sh
40
41 Reference Point 11/Sh is the signaling interface between the SIP Application Server and
42 the AAA and between the OSA Service Capability Server and the AAA, for user’s
43 service authentication and/or authorization, and for retrieving information from the
44 MMD database [Multimedia Domain only].
45
46
47
Reference Point 12/ISC
48
49
Reference Point 12/ISC is the signaling interface between the SIP Application Server
50 and Call Session Control Function and between the OSA Service Capability Server and
51 the Call Session Control Function for service control [Multimedia Domain only].
52
53
Reference Point 13
54
55
Reference Point 13 is the signaling interface between the Legacy MS Domain Support
56
and the PSTN [Legacy MS Domain only].
57
58
59
60

All-IP NAM Rev 3.0
2
3
Reference Point 14 is the signaling interface between the Legacy MS Domain Support
4
and the MAP (TIA/EIA-41) [Legacy MS Domain only].
5
6
8
Reference Point 15 is the signaling interface between the Position Server and AAA. 9
10
11
Reference Point 16/Cx 12
13
Reference Point 16/Cx is the signaling interface between the AAA and the Call Session 14
Control Function [Multimedia Domain only]. 15
16
Reference Point 17/Mg 17

18
19
Reference Point 17/Mg is the signaling interface between the Call Session Control
20
Function and the Media Gateway Control Function [Multimedia Domain only].
21
22
24
Reference Point 18 is the signaling interface between the Position Server and the 25
Position Determining Entity. 26

27
28
30
Reference Point 19 is the signaling interface between the Position Server and the Access 31
Gateway [Multimedia Domain only]. 32
33
34
36
Reference Point 20 is the signaling interface between the AAA and the cdma2000
37
Access Network [Multimedia Domain only].
38
39
41
Reference Point 21 is the signaling interface between the AAA and Access Gateway. 42
43
44
46
Reference Point 22 is the signaling interface between the AAA and the Mobile IP Home 47
Agent. 48
49
50
52
Reserved.
53
54
Reference Point 24/Mr 55

56
Reference Point 24/Mr is the signaling interface between the Call Session Control 57
Function and the Media Resource Function Controller [Multimedia Domain only]. 58
59
60

All-IP NAM Rev 3.0
1
Reference Point 25/Mp
2
Reference Point 25/Mp is the signaling interface between the Media Resource Function
3
Controller and the Media Resource Function Processor.
4
5
6 Reference Point 26/PSTN
7
8 Reference Point 26/PSTN is the signaling interface between the Media Gateway Control
9 Function and the PSTN [Multimedia Domain only].
10
11
12 Reference Point 27
13
14 Reference Point 27 is the bearer stream interface between the cdma2000 Access
15 Network and the Media Gateway [Legacy MS Domain only].
16
17
18
Reference Point 28/Go
19
20
Reference Point 28/Go is the signaling interface between the Policy Decision Function
21
and Access Gateway.
22
24
25 Reference Point 29 is the signaling interface between Policy Decision Function and the
26 Border Router.
27
28
29 Reference Point 30/Mc
30
31 Reference Point 30/Mc is the signaling interface between the Media Gateway Control
32 Function and the Media Gateway [Multimedia Domain only].
33
34
35
Reference Point 31
36
37
Reference Point 31 is the bearer stream interface between cdma2000 Access Network
38
and the Access Gateway.
39
40
Reference Point 32/Mb
41
42
Reference Point 32/Mb is the bearer stream interface between the Access Gateway and
43
the Media Resource Function Processor .
44
45
46 Reference Point 33/Mb
47
48 Reference Point 33/Mb is the bearer stream interface between the Media Resource
49 Function Processor and the Media Gateway.
50
51
52
53
54
Reference Point 34/Mb is the bearer stream interface between the Media Gateway and
55
the PSTN.
56
57
58
59
60

All-IP NAM Rev 3.0
2
3
Reference Point 35 is the signaling interface between the cdma2000 Access Network
4
and the Access Gateway.
5
6
Reference Point 36/Mb 7

8
Reference Point 36/Mb is the bearer stream interface between the Access Gateway and 9
the Media Gateway. 10

11
12
14
Reference Point 37/Mb is the bearer stream interface between the Media Resource 15
Function Processor and the Mobile IP Home Agent. 16
17
18
20
Reference Point 38/Mb is the bearer stream interface between the Media Gateway and
21
the Mobile IP Home Agent [Multimedia Domain only].
22
23
25
Reference Point 39 is the signaling interface between the Media Gateway and the 26
Legacy MS Domain Support [Legacy MS Domain only]. 27

28
29
31
Reference Point 40/Mb is the bearer streams interface between the Media Gateway and 32
the Border Router. 33
34
35
37
Reference Point 41 is the signaling interface between the Access Gateway and the
38
Mobile IP Home Agent. 39
40

42
Reference Point 42/Mb is the bearer streams interface between the Media Resource 43
Function Processor and the Border Router. 44

45
46
48
Reference Point 43/Mb is the bearer streams interface between the Access Gateway and 49
the Mobile IP Home Agent. 50
51
52
54
Reference Point 44/Mb is the bearer stream interface between the Mobile IP Home 55
Agent and the Border Router. 56
57
58
59
60

All-IP NAM Rev 3.0
1
2
Reference Point 45/Mb is the bearer stream interface between the Access Gateway and
3
the Border Router.
4
5
6 Reference Point 46/Mb
7
8 Reference Point 46/Mb is the bearer stream interface between the Border Router and the
9 IP Network.
10
11
12 Reference Point 47/Um
13
14 Reference Point 47/Um is the Radio Link (air interface) between the Mobile Station and
15 the cdma2000 Access Network.
16
17
18
Reference Point 48
19
20
Reference Point 48 is the signaling interface between the cdma2000 Access Network
21
and the Legacy MS Domain Support [Legacy MS Domain only].
22
23 Reference Point 49/Mj
24
25 Reference Point 49/Mj is the signaling interface between the Breakout Gateway Control
26 Function and the Media Gateway Control Function [Multimedia Domain only].
27
28
30
31 Reference Point 50 is the signaling interface between the Policy Decision Function and
32 the P-CSCF [Multimedia Domain only].
33
34 Reference Point aa
35
36 Reference Point aa is the bearer stream interface between the MS’s IP Multimedia
37 Client and the Home or Visited Network’s Peer Mobile Station [not shown in Figure 2.1
38 (see Figure 3.1.3), Multimedia Domain only].
39
40
41
Reference Point bb
42
43
Reference Point bb is the bearer stream interface between the MS’s IP Multimedia
44
Client and the Home or Visited Network’s Media Resource Function Processor [not
45
shown in Figure 2.1 (see Figure 3.1.3), Multimedia Domain only].
46
47
Reference Point cc
48
49
Reference Point cc is the bearer stream interface between the MS’s IP Multimedia
50
Client and the Home or Visited Network’s Media Gateway [not shown in Figure 2.1
51
(see Figure 3. 1.3), Multimedia Domain only].
52
53
54 Reference Point dd/Mw
55
56 Reference Point dd/Mw represents several signaling interfaces. Reference Point dd/Mw
57 exists between the Proxy-CSCF and the Serving-CSCF, and between the Visited
58
59
60

All-IP NAM Rev 3.0
Network’s Proxy-CSCF and the Home Service Network’s Interrogating-CSCF [not 1
shown in Figure 2.1 (see Figure 3.1.4b), Multimedia Domain only]. 2

3
4
Reference Point ff/Mw 5
6
Reference Point ff/Mw is the signaling interface between the Home Service Network’s 7
Interrogating-CSCF and the Home Service Network’s Serving-CSCF [not shown in 8
Figure 2.1 (see Figures 3.1.4b and 3.1.4c), Multimedia Domain only]. 9
10
11
Reference Point gg 12
13
Reference Point gg is the signaling interface between the Visited Network’s Local-AAA 14
and the Home Network’s Home-AAA [not shown in Figure 2.1 (see Figures 3.1.1 and 15
3.1.2)]. 16
17
Reference Point hh/Gm 18

19
20
Reference Point hh/Gm is the signaling interface between the MS’s IP Multimedia
21
Client and the Visited Network’s Proxy-CSCF [not shown in Figure 2.1 (see Figure
22
3.1.4b), Multimedia Domain only].
23
24
Reference Point ii 25
26
Reference Point ii is the signaling interface between the MS’s IP Multimedia Client and 27
the Home Service Network’s Application Server [not shown in Figure 2.1 (see Figure 28
3.1.4c), Multimedia Domain only]. 29

30
31
Reference Point jj 32
33
Reference Point jj is the signaling interface between the Position Server and the Legacy 34
MS Domain Support [not shown in Figure 2.1 (see Figure 3.4), Legacy MS Domain 35
only]. 36
37
38
Reference Point kk 39
40
Reference Point kk is the signaling interface between the OSA Service Capability
41
Server and the Legacy MS Domain Support [not shown in Figure 2.1 (see Figure 3.4),
42
Legacy MS Domain only]. 43
44
Reference Point m1 45
46
Reference Point m1 is the management interface between an M-NE and an OSF-EML 47
(applicable definitions provided by S.S0028-A). 48

49
50
Reference Point m2 51
52
Reference Point m2 is the management interface between an OSF-EML and an OSF- 53
NML/OSS; this reference point is equivalent to the 3GPP Itf-N interface (applicable 54
definitions provided by S.S0028-A). 55
56
57
58
59
60

All-IP NAM Rev 3.0
1
Reference Point m3
2
Reference Point m3 is the management interface between an OSF-NML/OSS and
3
another OSF-NML/OSS (applicable definitions provided by S.S0028-A).
4
5
6 Reference Point m4
7
8 Reference Point m4 is the management interface between OSF-EML / OSF-NML/OSS
9 and 3GPP2 NAM Databases, such as Network Policy Rules and Subscriber Profile
10 (applicable definitions provided by S.S0028-A).
11
12
13 Reference Point O1
14
15 Reference Point O1 is the interface between an MWNE and the OSF.
16
17
18
Reference Point O2
19
20
Reference Point O2 is the OSF to OSF interface.
21
22 Reference Point xx
23
24 Reference Point xx is the signaling interface between the Media Resource Function
25 Processor and the Legacy MS Domain Support [not shown in Figure 2.1 (see Figure
26 3.4)].
27
28
29 Reference Point yy
30
31 Reference Point yy is the bearer stream interface between two Media Gateways [not
32 shown in Figure 2.1 (see Figure 3.4)].
33
34
35
Reference Point zz
36
37
Reference Point zz is the signaling interface between two Legacy MS Domain Supports
38
[not shown in Figure 2.1 (see Figure 3.4)].
39
40
41
42
3. ALL-IP NAM DETAILED VIEWS
43
44
45
3.1 Planar Views
46
47 There are several different drivers for having a planar view of the architecture showing:
48 a. the separation of access specific functions from access independent functions,
49
b. how IP transparency is used to facilitate communication between functions in
50
the mobile station and on the network side,
51
52 c. how the concepts of different home networks in different planes apply to the
53 architecture, and
54
d. the concepts of separation between transport and signaling wherever they
55
apply.
56
57
58
59
60

All-IP NAM Rev 3.0
3.1.1 Access Plane 1

2
3
The purpose of the access plane is to hide anything access specific from the upper
4
planes (network, multimedia bearer, multimedia control). The access plane should
5
receive QoS requests through the network plane, and the access plane functions should
6
translate these requests to resource requests that are applicable to that specific access
7
technology.
8
The access plane contains functions specific to an access network such as access 9
technology specific authentication and authorization (also known as L2 functions). The 10
access plane should provide all the infrastructure needed for this task, even though some 11
of the functions may be physically implemented in the same entity as functions of the 12
other planes. 13
14
In the access plane, the concept of a “Home Access Network” is introduced. In the case
15
of cdma2000 networks, the home network is the network of the service provider
16
providing the subscription to the wireless access. The “Home Access Network” is
17
logically different from the concepts of Home Network of the Network plane and in the
18
Multimedia Control plane, even though they in many cases physically would be the 19
same network. 20
The access plane contains the following components: 21
22
a. Mobile Station (TE part, link layer, air interface signaling etc.),
23
b. RAN (BSC/RNC+PCF, BTS, MM), 24
c. Access Gateway, and 25

26
d. AAA (for L2 AAA functions).
27
28
Mobile Visited Home 29
Station Access Network Access Network 30

31
32
local gg home
gg 33
AAA AAA 34
35
36
20 37
38
39
cdma2000 Access Network 40
Access
41
Gateway
Terminal 47/ BSC/RNC 31 42
BTS
Equipment Um + PCF 43
44
35 45
MM 46
47
FA /
Attendant 48
49
Other Access Networks
50
51
52
53
Figure 3.1.1 Access Plane 54
55
56
57
58
59
60

All-IP NAM Rev 3.0
1
3.1.2 Network Plane
2
The purpose of the network plane is to provide end-to-end IP connectivity between the
3
mobile station (including devices connected to it) and other IP entities. Other IP entities
4
5
may include nodes in the multimedia control or bearer planes.
6 The network plane interacts with the access plane, which to the network plane appears
7 as a link layer, controlling it through means such as DiffServ, RSVP, and an Access
8 Gateway-Policy Decision Function interface.
9
The interaction with the multimedia bearer or control planes should be through generic
10
and transparent interfaces, so that the applications executing either on the network side
11
or on the mobile station side may request QoS resources without any direct knowledge
12
of the access currently in use.
13
14 In the network plane, the concept of “Home IP network” is introduced. This concept
15 has the same meaning as in P.S0001-B. The home IP network may be the same as the
16 wireless home (access) network. The home IP network could be an ISP network or it
17 could be a corporate network.
18
The network plane contains the following components:
19
20 a. Mobile Station (IP capabilities, MIP Client, QoS client),
21 b. Home Agent,
22
c. Policy Decision Function, and
23
24 e. AAA (for Layer-3 AAA functions).
25
26 Mobile Visited Home IP
27
28
Station Network Network
29
30 local home
31 AAA AAA
32 gg
33
34 21 23 22
35
36 Policy
37
Decision
38
Function
39
40
41
28/Go
42
43
cdma2000 Access Network
44 Access
Gateway
45
Mobile IP 31 43/Mb Mobile IP
46 47/ BTS
BSC/RNC
Client + PCF Home
47 Um
48 35 41 Agent
49
50
MM
51
FA /
52
Attendant
53 Other Access Networks
54
55
56
57 Figure 3.1.2 Network Plane
58
59
60

All-IP NAM Rev 3.0
1
2
3
3.1.3 Multimedia Bearer Plane 4

5
The purpose of the multimedia bearer plane is to transport the user data (bearers) 6
between the network entities involved in multimedia sessions or calls. This includes 7
network entities such as the mobile station, Media Gateways, Media Resource Function 8
Processors and entities on the Internet. 9

10
The multimedia bearer plane is an abstraction above the network plane. The network 11
plane provides end-to-end IP connectivity to the multimedia bearer plane, so that these 12
network entities may communicate directly. If, for example, a bearer path is to be 13
established between the mobile station and a Media Gateway, the mobile station would 14
need to: 15
a. Obtain the IP address of the Media Gateway from the multimedia control 16
plane, 17
18
b. Request the necessary QoS from the network layer, and 19
c. Start sending IP packets to the Media Gateway. 20
21
The purpose of the underlying planes is to make sure that the necessary QoS is available 22
through all parts of the network (including over the air interface) and to make sure that 23
the packets are routed correctly. 24
The multimedia bearer plane contains the following components: 25

26
a. Mobile station (Multimedia client or applications), 27
b. Media Resource Function Processor, 28
29
c. Media Gateway, and
30
d. Internet (peer entity on the Internet). 31
32
Mobile Home or Visited 33
Station Network 34
35
36
Peer 37
Mobile 38
Station 39
40
aa 41
42
IP Media 43
bb Resource
Multimedia Function
44
45
Client Processor
cc 46
47
48
49
Media 50
51
Gateway 52
53
54
Figure 3.1.3 Multimedia Bearer Plane 55

56
57
58
59
60

All-IP NAM Rev 3.0
1
3.1.4 Multimedia Application Server Control Plane
2
The multimedia application server control plane implements all the call control and
3
services or applications that makes up the multimedia services of the All-IP domain.
4
5
The multimedia application server control plane functions are access independent,
6
except in generic terms such as available QoS etc.
7 The multimedia application server control plane is an abstraction above the network
8 plane. The network plane provides end-to-end IP connectivity to the multimedia control
9 plane, so that these entities may communicate directly. Assuming the lower planes
10 ensure IP packets are routed correctly, and the necessary QoS is available, the entities of
11 the multimedia application server control plane may communicate directly with each
12 other and with entities in the multimedia bearer plane. For example a SIP Client in the
13 mobile station may communicate with SIP Servers (CSCFs) in the network, assuming
14 the SIP Client has obtained knowledge about the IP address to use.
15
16
The multimedia application server control plane contains the following components:
17 a. Mobile Station (Multimedia client and/or applications),
18
b. OSA Service Capability Server,
19
20 c. Call Session Control Function,
21 d. AAA (for application level AAA),
22
e. Application Servers, and
23
24 f. Databases.
25
26
The S-CSCF chooses a particular service control application server using user profile
27
information it has received from the AAA. No choice of protocol needs to be made to
28 access a particular service control application server since the same IP multimedia
29 service control interface is used between the S-CSCF and each of these service control
30 application servers.
31 Figure 3.1.4a shows the variety of application server configurations that may be
32 supported in the Multimedia Application Server Control Plane. These configurations
33 include:
34
35
a. application servers that reside inside or outside of the WNO network (i.e.,
36
Application Servers A to C),
37 b. application servers that access network resources (e.g., Call Session Control
38 Function, AAA, Position Server) for functionality needed during service logic
39 execution using either APIs and the OSA Service Capability Server (OSA-
40 SCS) (i.e., Type-A Application Server) or direct interfaces such as Reference
41 Point “11/Sh” (i.e., Type-B Application Server), and
42
43
c. applications that do not use network resources other than for bearer
44
management (i.e., Type-C Application Server).
45
In each of the configurations shown:
46
47 a. a bearer relationship may be established between the mobile station and the
48 application server,
49 b. application server management may be performed by the WNO, the service
50 provider, or a third party, and
51
52
c. the information provided by Reference Point 8 to a Type-A Application Server
53
and or by Reference Points 11/Sh and 12/ISC to a Type-B Application Server
54
may vary by the level-of-trust afforded by the WNO.
55
56
57
58
59
60

All-IP NAM Rev 3.0
1
OSA Application Server SIP Application Server Application Server 2
[Control and Content] [Control and Content] [Content only] 3
4
Type A Type B Type C 5

6
Service Service Service 7
Application Application Application 8

9
8/OSA-API 11/Sh 12/ISC 10

11
12
OSA Service 13
Capability Databases 14
Server 12/ISC 4 15
16
17
10 11/Sh 18
19
20
Position Call Session 21
AAA Control
Server 15 16/Cx Function
22
23
24
25
Figure 3.1.4a Multimedia Application Server Control Plane 26
27
28
29
Figure 3.1.4a illustrates the following three application server signaling configurations:
30
A: Type A Application Servers are hosted on equipment in the Wireless Network 31
Operator’s (WNO) network, in the Internet or in a private network. These 32
application servers use standard APIs (e.g., OSA API) supported by the OSA- 33
SCS. The APIs allow access to application servers during SIP sessions and 34
allow applications to access resources in the network (e.g., Position Server, 35
CSCF, AAA) as required for service logic execution. 36
37
While accessing functionality in the WNO network (e.g., AAA, CSCF, 38
Position Server), Type A Application Servers may also access private 39
databases, SIP or http servers, and other functionality on equipment provided 40
by a third party. 41
Type A Application Servers may have bearer access using the WNO intranet, 42
allowing a higher QoS than public Internet. 43

44
B: Type B Application Servers are hosted on equipment in the WNO network, in 45
the Internet or in a private network capable of communication in SIP and 46
offering both service control and content. These application servers require 47
signaling access to functionality provided in the WNO network in addition to 48
the signaling needed for bearer management. 49

50
Type B Application Servers may have bearer access using the WNO intranet, 51
allowing a higher QoS than public Internet. 52
53
C: Type C Application Servers are hosted on equipment in the Internet or in the
54
WNO network offering content applications only. These application servers
55
do not require signaling access to the WNO network other than as needed for
56
bearer management
57
58
59
60

All-IP NAM Rev 3.0
Figure 3.1.4b depicts the functional entities involved in providing service applications
1
to SIP based sessions. The applications are invoked from the Call Session Control
2
Function either directly or via the OSA Service Capability Server and may request use
3
of network resources via the OSA Service Capability Server. Figure 3.1.4b also
4
illustrates how the CSCF functionality is distributed between the visited and home
5
networks. After a SIP client in the mobile station has registered through a Proxy-CSCF
6
(P-CSCF) in the visited/home network, all further communication between the SIP
7
client and the home network passes through the P-CSCF.
8
9
10 Mobile Visited/Home Home Service
11 Station Network Network
12
13
14 SIP OSA
15 Application Application
16
17
Server Server
18
11/Sh 12/ISC 8/OSA-
19
API
20
21 OSA Service
22
Capability
23
Server
24
25
11/Sh 12/ISC
26
27
28
29
home
30 AAA
31
32
16/Cx 16/Cx
33
34
IP (Proxy) dd/Mw
35
hh/ Call Session
36 Multimedia Gm Control
37 Client Function dd/Mw
38
39
40
Breakout 9/Mi (Interrogating) (Serving)
41
Gateway Call Session ff/ Call Session
42
43 Control Control Mw Control
44 Function Function Function
45
46 17/Mj 17/Mg 24/Mr
47
48
Media Media Media
49 Gateway Gateway Resource
50 Control Control Function
51 Function Function Controller
52
53
54 Figure 3.1.4b Multimedia SIP Services Control Plane
55
56 Figure 3.1.4c depicts the functional entities involved in providing service applications to
57 data sessions. The applications are invoked from the mobile station after the application
58 server has provided the service addresses. Depending on the connectivity scenario, the
59
60

All-IP NAM Rev 3.0
application server may request use of network resources either directly or via the OSA 1
Service Capability Server. 2

3
4
Mobile Visited/Home Home Service 5
Station Network Network 6
7
8
SIP OSA 9
Application Application 10
Server Server 11
12
8/OSA- 13
API 14
15
OSA Service 16
ii ii 11/Sh 12/ISC Capability 17
Server 18
19
20
11/Sh 12/ISC
21
22
home 23
24
AAA 25
26
16/Cx 16/Cx 27
28
IP (Proxy) dd/Mw 29
Call Session
Multimedia hh/
30
Gm Control 31
Client Function dd/Mw 32
33
34
Breakout 9/Mi (Interrogating) (Serving) 35
Gateway Call Session ff/ Call Session 36

37
Control Control Mw Control
38
Function Function Function
39
40
49/Mj 17/Mg 24/Mr
41
42
Media Media Media
43
Gateway Gateway Resource 44
Control Control Function 45
Function Function Controller 46
47
48
Figure 3.1.4c Multimedia Data Services Control Plane 49
50
51
52
3.2 Authentication and Authorization View 53
54
Authentication and authorization are performed at different times and may employ
55
different network elements in order to support wireless access network IP-based and
56
circuit-based service requests, see Figure 3.2. 57
58
59
60

All-IP NAM Rev 3.0
Permission for IP-based access and services is authorized and authenticated at various
1
levels. In the IP model, user initiated MS service requests may employ additional levels
2
of authorization and authentication processes based on the service application or
3
multimedia feature being accessed. The purpose of the architecture is to allow the
4
configuration of authorization and/or authentication interaction paths (i.e., “a”, “b”, “c”
5
and “d”) necessary to support network based or independent approval authorities or a
6
combination of these processes.
7
8 Permission for existing circuit-based access and services is authorized and authenticated
9
using specific procedures for the TIA/EIA-41 wireless network. The interaction paths
10
(i.e., “e”) extend from the Mobile Station to the Legacy MS Domain Support that
11
contains several logical network entities (i.e., “HLRe”, “MSCe” and “SCPe”).
12
13 Further definitions of these authorization and authentication interaction paths are:
14
15 “a” Multimedia Layer-2 access permission is sought from the serving wireless
16 access provider and involves interaction with the subscriber's home wireless
17 access provider for final approval, this action is initiated by a MS access
18 request.
19
20
“b” Simple IP or Mobile IP Layer-3 access permission is sought from the IP
21
service provider, which may be the same provider as the wireless access
22 network or in the case of IP access to a private network, the IP Access
23 provider may be different.
24
TIA/EIA-41 packet data service Simple IP or Mobile IP access permission is
25
26
sought from the IP service provider, this action is initiated by a Legacy MS
27
Domain packet data service access request.
28
“c” multimedia services access permission is requested from the multimedia
29
service provider, access for each user is requested by the Call Session Control
30
Function.
31
32 “d” services within the multimedia domain are approved for each user by
33 Application Server via the OSA Service Capability Server. In each of these
34 cases, the necessary authentication and/or authorization approval may be
35 different for each service authority or all service levels may employ one and
36 the same AAA.
37
38 “e” Layer-2 and Layer-3 TIA/EIA-41 access permission is sought from the serving
39 Legacy MS Domain Support wireless access provider and may involve
40 interaction with the subscriber's home TIA/EIA-41 wireless access provider
41 for final approval, this action is initiated by a Legacy MS Domain access
42 request.
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

All-IP NAM Rev 3.0
1
AAA AAA AAA 2
(Home AAA 3
(Multimedia (Application
Access (IP/MIP) 4
Provider) Provider)
Provider) 5
6
7
8
OSA Service 9
Capability 10
Server 11
12
13
AAA AAA Call Session 14
Control
Application 15
(Access (Access
Layer-2) Layer-3) Function Server 16
17
18
a b c d 19
20
21
22
Access 23
cdma2000 Access Network Gateway 24
25
Mobile BTS
BSC/RNC 26
Station + PCF 27
28
29
FA /
MM Attendant
30
31
e 32
33
34
35
Legacy MS Domain Support 36
37
38
HLRe MSCe SCPe 39
40
41
42
Figure 3.2. Authentication and Authorization View 43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

All-IP NAM Rev 3.0
1
3.3 Mobile Station (MS) View
2
3
4
MS
5
6
7
8
MT0
9 ME
10
11
12
13 Sm MT1
14 TE1
15
47
16
17 (Um)
18 Rm TAm
TE2
19
20
21
22
23 Rm MT2
TE2
24
25
26
27
U
28 i
29
30 U
r UIM
31
32
33
34 Figure 3.3 Mobile Station (MS) View
35
36
The Mobile Station Plane contains the following entities and reference points:
37
38
Mobile Equipment (ME)
39
40
The ME is the MS without a UIM. The ME is only capable of accessing the network per
41
locally defined service configuration (e.g., emergency services, service center, etc).
42
43
44 Mobile Station (MS)
45
46 The MS is a wireless terminal used by subscribers to access the Legacy MS Domain or
47 the IP Multimedia Domain services over a radio interface. MSs include portable units
48 (e.g., hand-held units), units installed in vehicles, and somewhat paradoxically, fixed
49 location MSs. The MS is the interface equipment used to terminate the radio path at the
50 subscriber. A MS is a ME with a programmed UIM.
51
52
53 Mobile Terminal 0 (MT0)
54
55 A self-contained data capable ME termination that does not support an external
56 interface.
57
58
59
60

All-IP NAM Rev 3.0
Mobile Terminal 1 (MT1) 1

2
3
A ME termination that provides an ISDN user-network interface.
4
5
Mobile Terminal 2 (MT2) 6

7
A ME termination that provides a non-ISDN user-network interface (e.g., ITU-T 8
[CCITT] V series, ITU-T [CCITT] X series). 9

10
11
Terminal Adapter m (TAm) 12
13
An entity that converts signaling and user data between a non-ISDN and an ISDN 14
interface. 15
16
Terminal Equipment 1 (TE1) 17

18
19
A data terminal that provides an ISDN user-network interface.
20
21
Terminal Equipment 2 (TE2) 22

23
A data terminal that provides a non-ISDN user-network interface (e.g., ITU-T [CCITT] 24
V series, ITU-T [CCITT] X series). 25

26
27
User Identity Module (UIM) 28
29
The UIM contains subscription information such as the NAM and may contain 30
subscription feature information. The UIM can be integrated into any mobile equipment 31
or it may be removable. 32
33
34
Reference Point Rm 35
36
Reference Point Rm is the interface between TE2 and the TAm and the interface 37
between TE2 and the MT2. 38
39
40
Reference Point Sm 41
42
Reference Point Sm is the interface between the TE1 and a MT1. 43
44
45
Reference Point Ui 46
47
Reference Point Ui is the interface between the integrated UIM and a ME. 48
49
50
Reference Point Um 51
52
Reference Point Um is the interface between the BS and the MS, which corresponds to 53
the air interface. 54
55
56
Reference Point Ur 57
58
Reference Point Ur is the interface between the Removable-UIM and a ME. 59
60

All-IP NAM Rev 3.0
1
3.4 Legacy MS Domain Control and Bearer View
2
The Legacy MS Domain provides support for existing MSs (e.g., analog, IS-95-A, IS-
3
95-B, cdma2000) in an IP core network environment. This domain supports the
4
5
features and capabilities provided in a legacy network in a manner transparent to the
6
user. New features and capabilities supported by the IP core network may be made
7
available to subscribers where they are supported by the MS capabilities.
8
The Media Gateway provides conversion between IP bearers and circuit bearers (e.g.,
9
ISDN, Feature Group D, CAMA).
10
11 Figure 3.4 provides a detailed view of the Legacy MS Domain. It includes an
12 expansion of the Legacy MS Domain Support entity shown in Figure 2.1 as well as
13 other IP network elements required to support legacy MSs (NOTE: except those not
14 shown such as OTAF, MC, etc.).
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

All-IP NAM Rev 3.0
Network OSA 2
EIR DSI Subscription Policy

... Application 3
Profile Rules 4
Server 5
Databases
6
m3 2 1 6 4 8/OSA-API 7
8
9
OSF-
OSA Service 10
Network
Capability 11
Management 12
Server
Layer / OSS 13
14
m2 m4 kk 15
16
17
OSF Element
Position AAA
18
Management 19
Server 15
Layer 20
21
18 jj 21 22 22
m1 23
24
Managed Position 25
Network Determining 26
Entity Entity 27
28
29
30
31
cdma2000 Access Network 27 Media
Access yy 32
Gateway Resource Media 33

BSC/RNC 31 Function 33/Mb Gateway 34
BTS 32/Mb
+ PCF Processor 35
35 xx 37/Mb
36
36/Mb 40/Mb 37
38
FA / 42/Mb 39
41 Mobile IP
Attendant Border 40
Home 41
Other Access Networks
43/Mb 44/Mb Router
Agent 42
43
45/Mb
48 46/Mb 44
45
47/Um 39 34/Mb
46
Legacy MS Domain Support
47
Mobile MAP HLRe MSCe SCPe IP 48
TIA/EIA-41 14 13 PSTN Network 49

Station 50
zz 51
52
53
Figure 3.4 Legacy MS Domain Control and Bearer View 54

55
56
57
58
59
60

All-IP NAM Rev 3.0
1
2
Within Figure 3.4 there are several items of interest, as:
3
4 a. the bearer path from the BSC to the MGW is used to support voice and circuit
5 data services,
6 b. the bearer path for packet data from the BSC to the Access Gateway continues
7 through the Border Router to the IP Network,
8
9
c. the LMSDS has signaling relationships with the cdma2000 Access Network,
10
MGW, and MRFP. The LMSDS also has a signaling relationship with
11
TIA/EIA-41 networks that allows interworking between the LMSD and other
12
TIA/EIA-41 based systems. The relationship with the MGW allows control of
13 the bearer paths to and from the PSTN,
14 d. services supported on the SCP make use of information stored in the Databases
15 component of the core network, including subscriber information, and may
16 interact with service applications, and
17
18
e. the HLRe uses information that may be stored commonly in the Databases.
19
This may allow the Databases to service both the Legacy MS Domain and the
20
IP Multimedia Domain.
21
22 3.5 Multimedia Domain Control and Bearer View
23
24
The Multimedia Domain provides support for SIP capable mobile stations in an IP core
25
network environment. This domain supports new multimedia features and capabilities
26
and also supports the features and capabilities provided in a legacy network in a manner
27
transparent to the user.
28
The Multimedia Domain supports multimedia sessions to and from SIP-capable mobile
29
stations.
30
31 The Multimedia Domain supports interconnectivity with the PSTN for circuit switched
32 sessions to and from SIP-capable mobile stations.
33 Figure 3.5 provides a detailed view of the Multimedia Domain.
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

All-IP NAM Rev 3.0
Network OSA SIP 2

3
EIR DSI Subscription
Profile
Policy
Rules ... Application Application 4
Databases
Server Server 5
6
m3 1 2 3 4 8/OSA-API 12/ISC 5/Mk 7

8
9
OSF- Breakout
Network OSA Service 10
Gateway
Management Capability 11
Control 12
Layer / OSS Server
11/Sh 10 Function 13
14
m2 m4 11/Sh 12/ISC 9/Mi 49/Mj 15
16
17
OSF Element Call Session Policy
Position 18
Management
15
AAA Control Decision 19
Layer Server 16/Cx Function 50 Function 20
17/Mg 21
18 19 20 21 22 24/Mr 28/Go 22
m1 29 23
24
Media Media
Managed Position 25
Resource Gateway
Network Determining 26
Function Control
Entity Entity 27
Controller Function 28
29
25/Mp 26/PSTN
30
30/Mc 31
cdma2000 Access Network Media
Access 32
Gateway Resource Media 33

BSC/RNC 31 32/Mb Function 33/Mb Gateway 34
BTS
+ PCF Processor 35
35 37/Mb
36
36/Mb 38/Mb 40/Mb 37

MM 38
FA / 39
Attendant 41
Mobile IP 42/Mb
Border 40
Home 41
Other Access Networks 43/Mb 44/Mb Router
Agent 42
43
45/Mb 44
46/Mb
45
47/Um 34/Mb 46
47
IP
Mobile PSTN Network
48
49
Station 50
51
52
53
Figure 3.5 Multimedia Domain Control and Bearer View 54
55
56
57
58
59
60

All-IP NAM Rev 3.0
1 4. SERVICE CREATION AND MANAGEMENT

2
3
4
5 4.1 Service Creation Environment (SCE)
6
7 The SCE is a non-real time development environment for creating service applications.
8 Service providers and third party application developers may use different versions
9 (e.g., flavors) of the SCE. The technology used to create applications may be a function
10 of technological choices (e.g., SIBBs), or vendor preferences. Its implementation
11 should, ideally be protocol independent, but could as well be technology specific (e.g.,
12 SIP). The SCE could allow for version and configuration management control of
13 existing and being developed services.
14
15 The SCE is connected via signaling Reference Point (see Figure 4.1):
16
A Service Management System.
17
18
19
Service
20
Creation
21
22
Environment
23
24
25
26 A
27
28
29
30
Network B Service
31 Subscrption Policy Management
32
EIR DSI
Profile Rules ...
System
33 Databases
34
35
36 C D E
37
38
39
40
Home Local Third Party
41 Application Application Application
42 Server Server Server
43
44
45
Figure 4.1 Service Creation and Management
46
47
48
4.2 Service Management System (SMS)
49
50
The Service Management System (SMS) provides overall service management
51
functionality for the network. Service providers and third party application developers
52
may use different versions (e.g., flavors) of the SMS. The SMS interacts with the SCE
53
and other entities to perform service provisioning, monitoring, testing, deployment, and
54
subscriber data management functions.
55
56
57
58
59
60

All-IP NAM Rev 3.0
The Service Management System is connected via signaling Reference Points (see 1
Figure 4.1): 2
3
A. Service Creation Environment, 4
B. Databases, 5
6
C. Home Service Applications,
7
D. Local Service Applications, and 8
E. Third Party Service Applications. 9

10
Note that a particular SCE and SMS pair may have access only to those databases and 11
application servers operated and authorized by a service provider. For example, an SCE 12
and SMS pair owned by service provider A may have access to databases and 13
application servers also owned by provider A, but may not have access to databases 14
owned by service provider B. The specification of Reference Points A, B, C, D and E is 15
beyond the scope of this document. 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

CDMA2000 IP Network Arc

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CDMA2000 IP Network Arc

Uploaded by

Copyright:

Available Formats

All-IP NAM Rev 3.

3GPP2 TSG-S All-IP NAM

IP Network Architecture Model for cdma2000 Spread Spectrum Systems 1

3.1.1 Access Plane .......................................................................................................33 33

3.1.2 Network Plane ....................................................................................................34 34

3.2 Authentication and Authorization View ...........................................................................40 38

3.5 Multimedia Domain Control and Bearer View .................................................................46 42

3GPP2 Wireless IP NAM ii Contents

iii 3GPP2 TSG-S All-IP NAM

“X” = published revision to which this enhancement applies. 6

3GPP2 TSG-S All-IP NAM iv

1 3GPP2 TSG-S All-IP NAM

• TIA/EIA-124-D, Wireless Radio Telecommunications Intersystem Non-Signaling Data 2

Communications (DMH); Telecommunications Industry Association; January 2002. 3

• EIA/TIA/IS-553, Mobile Station - Land Station Compatibility Specification; September 6

• TIA/EIA/IS-683-A, Over-The-Air Service Provisioning of Mobile Stations in Spread 10

within the limits of this recommendation. 23

3. MOBILE IP (i.e., IPv4 and/or IPv6). 32

3GPP2 TSG-S All-IP NAM 2

3 3GPP2 TSG-S All-IP NAM

fidelity and performance. 11

a. Bandwidth: Data rate (e.g., 64 kbps), 14

Additionally, this QoS may be: 20

Wireless Network Operator (WNO) 28

3GPP2 TSG-S All-IP NAM 4

5 3GPP2 TSG-S All-IP NAM

Note the following: 20

a. The network architecture model is a functional block 22

implementation of network entities, either individually or in 29

Station (MS) is an excellent example. 34

c. A reference point is a conceptual point that divides two 36

groups of functions. It is not necessarily a physical interface. 37

physical devices. One or more interfaces may be defined to 41

support each reference point. 42

d. A reference point may or may not be standardized. This is a 44

that are an instance of the collective (e.g., cdma2000 Access 53

g. A “Composite Entity” contains encompassed network entities 56

3GPP2 TSG-S All-IP NAM 6

7 3GPP2 TSG-S All-IP NAM

2.1.1 Network Entities 1

Access Gateway (AGW) 7

to the CDMA2000 Radio Access Network (RAN). 12

capabilities, configuration, and resources of the numerous Access Network 16

technologies. An Access Gateway performs the following functions: 17

a. supports inter-access gateway handoffs, 20

i. communicates with the Policy Decision Function (PDF) for management of 35

requests may be forwarded to the Policy Decision Function (PDF) for 48

p. enforces policy decisions for authorized services, and 53

3GPP2 TSG-S All-IP NAM 8

9 3GPP2 TSG-S All-IP NAM

Signaling for call control, mobility management, and MS management as well 3

The IP Multimedia Domain MM function’s responsibilities include: 8

b. Communicating with the AAA for access network authentication, 13

authorization of radio link access and accounting. Example of 14

accesses that MM should authenticate and/or authorize with the AAA 15

include multimedia registration, multimedia page response, inter-radio 16

access network handoff, and 17

b. interact with AGW to support dormant handoff, 30

g. collect and send radio link (air interface) related accounting 39

information to the AGW. 40

27. Media Gateway (bearer streams [Legacy MS Domain only]), 47

3GPP2 TSG-S All-IP NAM 10

11 3GPP2 TSG-S All-IP NAM

The Accounting Function: 1