TIA-918.pdf

8/14/2019 TIA-918.pdf

1/76

TIA

DOCUMENT

Signaling Conformance Standard for

cdma2000

Wireless IP Networks

TIA-918

MAY 2002

TELECOMMUNICATIONS INDUSTRY ASSOCIATION

The Telecommunications Industry Association

represents the communications sector of

8/14/2019 TIA-918.pdf

2/76

NOTICE

TIA Engineering Standards and Publications are designed to serve the public interest through eliminating

misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of

products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for

their particular need. The existence of such Publications shall not in any respect preclude any member or

non-member of TIA from manufacturing or selling products not conforming to such Publications. Neither

shall the existence of such Documents preclude their voluntary use by non-TIA members, either domesticallyor internationally.

TIA DOCUMENTS

TIA Documents contain information deemed to be of technical value to the industry, and are published at the

request of the originating Committee without necessarily following the rigorous public review and resolution

of comments which is a procedural part of the development of a American National Standard (ANS). Further

details of the development process are available in the TIA Engineering Manual, located at

http://www.tiaonline.org/standards/sfg/engineering_manual.cfm

TIA Documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on

whether to reaffirm, revise, withdraw, or proceed to develop an American National Standard on this subject.Suggestions for revision should be directed to: Standards & Technology Department, Telecommunications

Industry Association, 2500 Wilson Boulevard, Arlington, VA 22201 U.S.A.

(From Project No. 3-0056, formulated under the cognizance of the TIA TR-45.5 Subcommittee on Spread

Spectrum Digital Technology.)

Published by

TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2003

Standards & Technology Department

2500 Wilson Boulevard

Arlington, VA 22201 U.S.A.

PRICE: Please refer to current Catalog of

TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS

AND ENGINEERING PUBLICATIONS

or call Global Engineering Documents, USA and Canada

(1-800-854-7179) International (303-397-7956)

or search online at http://www.tiaonline.org/standards/search_n_order.cfm

All rights reserved

Printed in U.S.A.

8/14/2019 TIA-918.pdf

3/76

NOTICE OF DISCLAIMER AND LIMITATION OF LIABILITY

The document to which this Notice is affixed (the Document) has been prepared by one or more

Engineering Committees or Formulating Groups of the Telecommunications Industry Association (TIA). TIA

is not the author of the Document contents, but publishes and claims copyright to the Document pursuant to

licenses and permission granted by the authors of the contents.

TIA Engineering Committees and Formulating Groups are expected to conduct their affairs inaccordance with the TIA Engineering Manual (Manual), the current and predecessor versions of which are

available at http://www.tiaonline.org/standards/sfg/engineering_manual.cfm. TIAs function is to administer

the process, but not the content, of document preparation in accordance with the Manual and, when appropriate,

the policies and procedures of the American National Standards Institute (ANSI). TIA does not evaluate, test,

verify or investigate the information, accuracy, soundness, or credibility of the contents of the Document. In

publishing the Document, TIA disclaims any undertaking to perform any duty owed to or for anyone.

The use or practice of contents of this Document may involve the use of intellectual property rights

(IPR), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no

search or investigation for IPR. When IPR consisting of patents and published pending patent applications are

claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with

the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into,the scope or validity of any claims of IPR.

TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify,

inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents

of the Document.

ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT

LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS,

ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS

MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL

PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE

ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIESREGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR

REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR

SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH

THE CONTENTS.

TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING

FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING

WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL

DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR

THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT

(INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS AFUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS

WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS.

8/14/2019 TIA-918.pdf

4/76

PLEASE!

DON'T VIOLATE

THE

LAW!

This document is copyrighted by the TIA and may not be reproduced without prior

permission of the Telecommunications Industry Association. For information

consult our website at http://www.tiaonline.org/about/faqDetail.cfm?id=18

Organizations may obtain permission to reproduce a limited number of copies

through entering into a license agreement. For information, contact:

Global Engineering Documents

15 Inverness Way East

Englewood, CO 80112-5704 U.S.A. or call

U.S.A. and Canada 1-800-854-7179, International (303) 397-7956

8/14/2019 TIA-918.pdf

5/76

TIA-918

CONTENTS

FOREWORD................................................................................................................... iv

NORMATIVE REFERENCES............................................................................................ vi

1 Introduction ..............................................................................................................1-1

1.1 Purpose ...............................................................................................................1-1

1.2 Scope ..................................................................................................................1-1

1.3 Network Architecture ...........................................................................................1-1

1.4 Requirements Language.......................................................................................1-2

1.5 Document Organization .......................................................................................1-2

2 Glossary and Definitions............................................................................................2-1

2.1 Acronyms ............................................................................................................2-1

2.2 Terms and Definitions..........................................................................................2-3

3 Simple IP Tests..........................................................................................................3-1

3.1 Simple IP Establishment without Authentication of the Mobile Station..................3-1

3.2 Simple IP Establishment with CHAP.....................................................................3-2

3.3 Simple IP Establishment with PAP........................................................................3-3

4 Agent Discovery and Registration...............................................................................4-1

4.1 Successful PPP Negotiation and Termination ........................................................4-1

4.2 Agent Discovery and Registration using Dynamic Home Address Assignment,

Successful Scenario .............................................................................................4-3

4.3 Agent Discovery and Registration using Static Home Address Assignment,

Successful Scenario .............................................................................................4-5

4.4 Router Advertisement Lifetime Expires .................................................................4-6

4.5 Mobile Station Registration Request Failed, HA has Insufficient Resources............4-7

4.6 Mobile Station Registration Request Retry ............................................................4-8

4.7 Registration Lifetime Processing...........................................................................4-9

4.8 Timestamp Error ...............................................................................................4-10

4.9 Mobile Station De-Registers ...............................................................................4-11

4.10 Simultaneous Simple IP and Mobile IP .............................................................4-11

5 Handoffs ...................................................................................................................5-1

5.1 Inter-PDSN Handoff, Mobile Station in Active State...............................................5-1

5.2 Inter-PDSN handoff, Mobile Station in Dormant State...........................................5-2

5.3 Intra-PDSN Handoff, Mobile Station in Active State ..............................................5-3

8/14/2019 TIA-918.pdf

6/76

TIA-918

ii

5.4 Intra-PDSN Handoff, Mobile Station in Dormant State ..........................................5-4

5.5 Simple IP Inter-PDSN Idle Handoff .......................................................................5-5

5.6 Simple IP Intra-PDSN Handoff, Mobile Station in Dormant State...........................5-6

6 Authentication and IPsec Security Association Support ..............................................6-1

6.1 RADIUS Support, Successful Scenario .................................................................6-1

6.2 RADIUS Support, Unsuccessful Scenario .............................................................6-2

6.3 IPSec Security Support, Preserving of Existing Security Association......................6-4

6.4 Authentication Failure, MN-HA Authenticator is Invalid........................................6-4

6.5 Foreign Agent Reverse Tunnel Registration Behavior.............................................6-5

6.6 Private Network Support, Successful Scenario......................................................6-7

6.7 Private Network Support, Unsuccessful Scenario..................................................6-8

6.8 Successful Authentication using the MN-AAA Extension.......................................6-87 Network Specific Tests ...............................................................................................7-1

7.1 Mobile IP Registration Request with Invalid Extensions.........................................7-1

7.2 Foreign Agent Busy..............................................................................................7-1

7.3 Mobile IP Registration Request Rejected, Invalid Home Address ............................7-2

7.4 Registration Rejected by FA, Poorly Formed Request.............................................7-2

7.5 Registration Rejected by Home Agent, Administratively Prohibited ........................7-3

7.6 Agent Advertisements not sent to Mobile Station using Simple IP..........................7-4

7.7 Mobile IP Registration Expires..............................................................................7-4

7.8 Mobile IP Registration Request Lifetime Exceeds Agent Advertisement Lifetime......7-5

7.9 Multiple Home Addresses.....................................................................................7-6

7.10 Mobile Station Assigned Same Home Address By Two Home Agents ....................7-7

7.11 Ingress Address Filtering....................................................................................7-8

7.12 IPsec Security Support, Statically Configured IKE Pre-Shared Secret...................7-9

7.13 IP Security Support, Dynamically Configured IKE Pre-Shared Secret.................7-10

7.14 Security Association using Public X.509 Certificates.........................................7-11

7.15 Security Association using the Root X.509 Certificates......................................7-12

7.16 Unsuccessful IPsec Security Association Establishment....................................7-13

7.17 PDSN Clears PPP State, R-P Session Closed......................................................7-14

7.18 PDSN Terminates Simple IP Session Due to PDSN PPP Inactivity Timer

Expiration..........................................................................................................7-14

7.19 PDSN Terminates a Simple IP Session when the R-P Session is Closed..............7-15

8/14/2019 TIA-918.pdf

7/76

TIA-918

iii

8 Accounting ................................................................................................................8-1

8.1 Accounting Scenario without Containers and No Change in Multiplex Options,

User Zone, or QoS................................................................................................8-1

8.2 Accounting Scenario with Containers and a Change in Multiplex Options, User

Zone, or QoS ........................................................................................................8-28.3 Accounting Scenario without Containers and a Change in Multiplex Options,

User Zone, or QoS................................................................................................8-2

8.4 Multiple Home Agent Test with Accounting...........................................................8-3

8.5 Single Home Agent and Simple IP Test with Accounting ........................................8-4

8.6 HDLC Byte Accounting Test with Simple IP ..........................................................8-5

8.7 Simple IP Test with Accounting and CHAP............................................................8-6

8.8 Simple IP Test with Accounting and PAP ..............................................................8-7

8/14/2019 TIA-918.pdf

8/76

TIA-918

iv

FOREWORD

(This foreword is not part of this Standard)

This standard was prepared by Technical Specification Group C of the Third Generation

Partnership Project 2 (3GPP2). This standard is a companion to the cdma2000 Wireless IP

Network standard. This specification provides a set of procedures that the mobile station

and network elements can use to conduct the signaling conformance tests in a laboratory

environment.

8/14/2019 TIA-918.pdf

9/76

TIA-918

v

No text.

8/14/2019 TIA-918.pdf

10/76

TIA-918

vi

NORMATIVE REFERENCES

The following standards and documents contain provisions, which, through reference in

this text, constitute provisions of this specification. At the time of publication, the editions

indicated were valid. All standards are subject to revision, and parties to agreements based

on this standard are encouraged to investigate the possibility of applying the most recenteditions of the standards indicated below.

[1] RFC2002, IPv4 Mobility, May 1995.

[2] TIA/EIA/IS-835-A, cdma2000 Wireless IP Network Standard, May 2001.

[3] RFC2344, Reverse Tunneling for Mobile IP, May 1998.

[4] TIA/EIA/IS-707-A, Data Service Options for Wideband Spread Spectrum Systems.

[5] TIA/EIA/IS-2000.5-A-2, Upper Layer (Layer 3) Signaling for cdma2000 SpreadSpectrum Systems.

[6] RFC 1661, The Point to Point Protocol (PPP),July 1994.

[7] RFC 3012, Mobile IPv4 Challenge/Response Extensions, Nov 2000.

[8] TIA/EIA/TSB100, Network Reference Model.

[9] TSB115, Wireless IP Architecture Based on IETF Protocols, August 2000.

[10] TIA/EIA/IS-2001-A, Access Network Interfaces Interoperability Specification, June

2001.

8/14/2019 TIA-918.pdf

11/76

TIA-918

1-1

1 INTRODUCTION1

1.1 Purpose2

This document is designed to facilitate the interoperability testing between mobile stations3

and infrastructure supporting [2], as well as provide network specific test cases.4

Definitions, recommended methods of measurement, and minimum standards are5

provided.6

1.2 Scope7

These technical requirements form a standard for signaling conformance in cdma20008

wireless packet data systems. These requirements ensure that a compliant mobile station9

and compliant network elements (PDSN, HA and RADIUS Server) can interoperate to10

execute tests in meeting the objectives stated in 1.1. Furthermore, network specific test11

requirements ensure compliant network elements for various error cases.12

1.3 Network Architecture13

Figure 1.3-1 shows the general network architecture for Simple IP:14

Home IP

Network

RADIUS

Mobile Station

Visited Access

Provider Network

VLR HLR

RADIUS

SS7

Network

IP

Network

PDSNRN

R-P

Interface

Home Access

Provider Network

RADIUS

Broker

Network

15

Figure 1.3-1 Simple IP Network Architecture16

17

8/14/2019 TIA-918.pdf

12/76

TIA-918

1-2

Figure 1.3-2 shows the general network architecture for Mobile IP:1

Home IP

Network

RADIUS

Mobile Station

HAVisited Access

Provider Network

VLR HLR

RADIUS

SS7

Network

IP

Network

PDSNRN

Home IP Network,

Private Network,

Home Access Provider

Network

R-P

Interface

Home Access

Provider Network

RADIUS

Broker

Network

2

Figure 1.3-2 Mobile IP Network Architecture3

1.4 Requirements Language4

Shall and shall not identify requirements to be followed strictly to conform to the5

standard and from which no deviation is permitted. Should and should not indicate that6

one of several possibilities is recommended as particularly suitable, without mentioning or7

excluding others, that a certain course of action is preferred but not necessarily required,8

or that (in the negative form) a certain possibility or course of action is discouraged but not9

prohibited. May and need not indicate a course of action permissible within the limits of10

the standard. Can and cannot are used for statements of possibility and capability,11

whether material, physical, or causal.12

1.5 Document Organization13

This document is organized into the following sections:14

Section 1 Introduction: This section describes the document purpose and scope as15

well as document organization.16

8/14/2019 TIA-918.pdf

13/76

TIA-918

1-3

Section 2 Glossary and Definitions: This section includes the list of acronyms and1

definitions used throughout the document.2

Section 3: This section describes the test setups, procedures, and minimum3

requirements for interoperability testing between the mobile station and PDSN4

supporting Simple IP service.5


requirements for interoperability testing between the mobile station and PDSN7

supporting Mobile IP service.8


requirements for interoperability testing of Simple IP and Mobile IP handoffs.10

Section 6: This section describes the test setups procedures, and minimum11

requirements for testing RADIUS support, authentication, and reverse tunneling12

behavior.13


requirements for network specific testing of Simple IP and Mobile IP infrastructure15

elements associated with registration, addressing, security association and agent16

advertisement.17


requirements for network specific testing of Mobile IP infrastructure elements19

associated with accounting for Simple IP and Mobile IP.20

21

8/14/2019 TIA-918.pdf

14/76

8/14/2019 TIA-918.pdf

15/76

TIA-918

2-1

2 GLOSSARY AND DEFINITIONS1

2.1 Acronyms2

Table 2.1 List of Abbreviations3

Acronym Expansion

AAA Authentication, Authorization,and Accounting

ACCM Asynchronous Control CharacterMap

AH Authentication Header

CA Certificate Authority

CANID Current Access NetworkIDentifiers

CCP Compression Control Protocol

CHAP Challenge HandshakeAuthentication Protocol

COA Care-of-Address

CRL Certificate Revocation List

DSA Digital Signature Algorithm

DOI Domain of Interpretation

ESP Encapsulating Security Payload

FA Foreign Agent

FAC Foreign Agent Challenge

HA Home Agent

HLR Home Location Register

IANA Internet Assigned NumberingAuthority

IETF Internet Engineering Task Force

IKE Internet Key Exchange

IMSI International Mobile StationIdentity

IMT-2000 International MobileTelecommunications - 2000

IP Internet Protocol

IPCP IP Control Protocol

IPsec IP Security

IRM International roaming MIN

8/14/2019 TIA-918.pdf

16/76

TIA-918

2-2

Acronym Expansion

ISAKMP Internet Security Association andKey Management Protocol

ISP Internet Service Provider

LAC Link Access ControlLCP Link Control Protocol

MAC Medium Access Control

MIN Mobile Identification Number

MIP Mobile IP

MS Mobile Station

MN Mobile Node

MSID Mobile Station ID

NAI Network Access Identifier

PAP Password AuthenticationProtocol

PANID Previous Access NetworkIDentifiers

PCF Packet Control Function

PDSN Packet Data Serving Node

PL Physical Layer

PPP Point-to-Point Protocol

PSI PCF Session ID

PZID Packet Zone ID

QoS Quality of Service

RADIUS Remote Authentication Dial InUser Service

RN Radio Network

RRP Mobile IP Registration Reply

RRQ Mobile IP Registration Request

RSA Rivest-Shamir-Adleman publickey algorithm

SA Security Association

SHA Secure Hash Algorithm

SPI Security Parameter Index

SS7 Signaling System 7

TCP Transmission Control Protocol

UDR Usage Data Record

8/14/2019 TIA-918.pdf

17/76

TIA-918

2-3

Acronym Expansion

UDP User Datagram Protocol

VLR Visitor Location Register

1

2.2 Terms and Definitions2

Access Provider Network: An IMT-2000 wireless network providing access to the mobile3

user.4

Broker RADIUS: An intermediate RADIUS server that has security relationships with the

Visited RADIUS and the Home RADIUS and is used to securely transfer RADIUS messages

between the Visited Access Provider Network and the Home IP Network. In some situations,

there may be more than one broker RADIUS in the path between visited RADIUS and home

RADIUS.

Broker RADIUS Network: A network with an administrative domain that contains the5

Broker RADIUS.6

Home RADIUS:The RADIUS server that resides in the Home IP Network.7

Home Access Provider Network:The IMT-2000 wireless network that is the home for the8

mobile subscriber unit. The user may have a different home network for data services.9

Home IP Network: The home network that provides IP based data services to the user.10

This network is where the user's NAI is homed. This network may be a private corporate11

network, publicly accessible ISP network, or an IMT-2000 network.12

IMT-2000 network: An IMT-2000 home/visited network is characterized by its ability to13

provide IMT-2000 capabilities to its users as identified in the IMT-2000 capability sets (ITU-14

Q.1701).15

Packet control function: See Radio Network.16

Packet data service: A general term describing a packet switched data service offered by17

an IMT-2000 network to a mobile subscriber (user).18

Packet data service option: A service option provides a means between MS and RN to19

establish and maintain cdma2000 Traffic Channels for packet data service.20

Packet data session: Describes an instance of continuous use of packet data service by21

the user. A packet data session begins when the user invokes packet data service. A packet22

data session ends when the user or the network terminates packet data service. During a23

particular packet data session, the user may change locations but the same IP address is24

maintained. For Simple IP service, moving from the coverage area of one PDSN to another25

PDSN constitutes a change in packet data session because a new IP address is assigned by26

the new PDSN. For Simple IP service, a packet data session and a PPP session are27

concurrent. For Mobile IP service, a packet data session can span several PDSNs as long as28

the user continuously maintains mobility bindings at the Home Agent and there is no lapse29

8/14/2019 TIA-918.pdf

18/76

TIA-918

2-4

in Mobile IP registrations/re-registrations (i.e., the IP address is persistent). For Mobile IP1

service, the Packet Data session can exist through several changes of the PPP session.2

PPP Session: A PPP session describes the time during which a particular PPP connection3

instance is maintained in the open state in both the mobile station and PDSN. The PPP4

session is maintained during periods when the mobile station is dormant. If a user hands5

off from one RN to another RN but is still connected to the same PDSN, the PPP session6

remains. If a user changes PDSN, a new PPP session is created at the new PDSN.7

Private Network: A Home IP Network that resides behind a firewall and that may use8

private IP addresses.9

Radio Network: The RN is equivalent to the BS as defined in [9], and corresponds to the10

collection of radio access equipment that includes the functional entities Radio Resource11

Control (RRC) and Packet Control Function (PCF) as described in [10]. At times the terms12

PCF and RN are used interchangeably in this document when describing handoffs across13

the R-P interface.14

R-P Interface: The interface between the Radio Network (specifically the PCF) and the15

PDSN. This interface is also referred to as the Aquater interface and the A10/A11 interface in16

[11].17

R-P session:The R-P session is a logical connection established over the R-P interface for a18

particular PPP session. If a user changes RNs during packet data service, the R-P session19

between the previous RN and PDSN is released and a new R-P session is established20

between the new RN and the same (or new) PDSN.21

Service Provider Network: An IMT-2000 network operated by either the home service22

provider or the visited service provider. The home service provider maintains the customer23

business relationship with the user. The visited service provider provides IMT-2000 access24

services through the establishment of a service agreement with a home service provider.25

Visited Access Provider Network:The IMT-2000 cellular network providing service to the26

user when he is roaming outside his home access provider network.27

Visited RADIUS:The RADIUS server that resides in the Visited Access Provider Network.28

8/14/2019 TIA-918.pdf

19/76

TIA-918

3-1

3 SIMPLE IP TESTS1

3.1 Simple IP Establishment without Authentication of the Mobile Station2

3.1.1 Definition3

If the mobile station can be configured to not use CHAP or PAP authentication, this test4

verifies that the mobile station and PDSN can successfully negotiate a PPP session during a5

Simple IP session. This test verifies the mobile station can successfully terminate the PPP6

session.7

3.1.2 Traceability8

5.1.1 PPP Session [2]9

5.2.1.3 Authentication [2]10

5.2.1.4 Addressing with IPCP [2]11


5.2.1.2 Termination [2]13

3.1.3 Method of Measurement14

a. Configure mobile station to initiate Simple IP service.15

b. Configure the PDSN to not require authentication of the mobile station.16

c. Set up a mobile station originated Service Option 33 call.17

d. Verify the PDSN proposes CHAP in the LCP Configure-Request.18

e. Verify the mobile station sends an LCP Configure-Reject rejecting the19

authentication option.20

f. Verify the PDSN sends a new LCP Configure-Request without the authentication21

option.22

g. Verify the mobile station sends an LCP Configure-Ack to the PDSN.23

h. Verify the mobile station sends an IPCP Configure-Request to the PDSN that24

includes the IP-Address Configuration Option with an IP address of 0.0.0.0.25

i. Verify the PDSN assigns an IP address to the mobile station.26

j. Once the PPP session has been established and the mobile station is on the27

traffic channel, instruct the mobile station to terminate the PPP session.28

k. Verify the mobile station sends an LCP-terminate request to the PDSN or29

signaling messages with Service Inactive indicator before terminating the packet30

data session with the RN.31

l. Verify the PDSN and mobile station are in the Null State.32

8/14/2019 TIA-918.pdf

20/76

TIA-918

3-2

3.1.4 Minimum Standard1

The mobile station shall establish a PPP session. The PDSN shall assign an IP address to2

the mobile station. The mobile station may send an LCP-terminate request to terminate the3

PPP session.4

3.2 Simple IP Establishment with CHAP5

3.2.1 Definition6

This test verifies the proper operation of Simple IP with CHAP authentication. This test7

verifies the mobile station can terminate the PPP session.8

3.2.2 Traceability9




a. Set up a mobile station originated Service Option 33 call.13

b. Verify the PDSN proposes CHAP in the LCP Configure-Request.14

c. Verify the mobile station sends an LCP Configure-Ack to the PDSN.15

d. Verify the PDSN sends a CHAP Challenge to the mobile station.16

e. Verify the mobile station sends a CHAP Response to the PDSN.17

f. Verify the PDSN sends a CHAP Success to the mobile station18

g. Verify the mobile station sends an IPCP Configure-Request to the PDSN that19

includes the IP-Address Configuration Option with address 0.0.0.0.20

h. Verify the PDSN assigns an IP address to the mobile station.21

i. Instruct the mobile to terminate PPP.22

j. Verify the mobile station sends an LCP-terminate request to the PDSN or23



k. Verify the PDSN and mobile station are in the Null State.26


The mobile station shall support CHAP authentication for Simple IP. The PDSN shall28authenticate the mobile station using CHAP. The mobile station may send an LCP-29

terminate request to terminate the PPP session.30

8/14/2019 TIA-918.pdf

21/76

TIA-918

3-3

3.3 Simple IP Establishment with PAP1

3.3.1 Definition2

If the mobile station supports using PAP and can be configured to prefer PAP instead of3

CHAP, this test verifies the proper operation of Simple IP with PAP authentication.4

3.3.2 Traceability5





b. Verify the PDSN proposes CHAP in the LCP Configure-Request.10

c. Verify the mobile station sends an LCP Configure-Nack to the PDSN proposing11

PAP.12

d. Verify the PDSN sends an LCP Configure-Request with PAP.13

e. Verify the mobile station sends a PAP Auth-Response to the PDSN.14

f. Verify the PDSN sends a PAP Auth-Ack to the mobile station.15

g. Verify the mobile station sends an IPCP Configure-Request to the PDSN that16

includes the IP-Address Configuration Option with address 0.0.0.0.17

h. Verify the PDSN assigns an IP address to the mobile station.18

i. Instruct the mobile station to terminate PPP.19

j. Verify the mobile station sends an LCP-terminate request to the PDSN or20



k. Verify the PDSN and mobile station are in the Null State.23


The mobile station may support PAP authentication for Simple IP. The PDSN shall25

authenticate the mobile station using PAP. The mobile station may send an LCP-terminate26

request to terminate the PPP session.27

8/14/2019 TIA-918.pdf

22/76

8/14/2019 TIA-918.pdf

23/76

TIA-918

4-1

4 AGENT DISCOVERY AND REGISTRATION1

4.1 Successful PPP Negotiation and Termination2

4.1.1 Definition3

This test verifies that the mobile station and PDSN/FA can successfully negotiate a PPP4

session when initiating a Mobile IP call. This test verifies the mobile station will not include5

an IP-Address Configuration Option in the IPCP Configure-Request and the PDSN shall not6

assign an IP address to the mobile station in IPCP. This test also verifies the mobile station7

can successfully terminate the PPP session.8

4.1.2 Traceability9



6.2.1.4 Addressing with IPCP [2]12

6.2.2.2 Addressing and Mobile IP [2]13


8/14/2019 TIA-918.pdf

24/76

TIA-918

4-2

4.1.3 Call Flow Example1

Service Option 33 Call

MS PDSN/FA

LCP Configure-Request Proposing CHAP

LCP Configure-Reject

LCP Configure-Request without CHAP

LCP Configuration Ack

IPCP Configure-Request without IP-AddressConfiguration Option

IPCP Configuration Ack

LCP Terminate-Request

Successful

Mobile IP

Registration

MS wishes to

terminate

PPP session

2


a. Configure mobile station and Home Agent (HA) to use static or dynamic home4

address assignment.5

b. Set up a mobile station originated Service Option 33 call.6

c. Verify the PDSN/FA proposes CHAP in the LCP Configure-Request.7

d. Verify the mobile station sends an LCP Configure-Reject rejecting the8


e. Verify the PDSN/FA sends a new LCP Configure-Request without the10


f. Verify the mobile station sends an LCP Configure-Ack to the PDSN/FA.12

g. Verify the mobile station sends an IPCP Configure-Request to the PDSN/FA that13

does not include the IP-Address Configuration Option.14

h. Verify the PDSN/FA sends an IPCP Configure-Reject to the mobile station if the15

Mobile IPv4 Configuration Option is included in the IPCP Configure-Request.16

8/14/2019 TIA-918.pdf

25/76

TIA-918

4-3

i. Verify the PDSN/FA CONF_ACKs the mobile request without assigning an IP1

address to the mobile station.2

j. Once the PPP session has been established, verify a successful Mobile IP3

registration occurs following an Agent Advertisement from the PDSN/FA.4

k. Ensure the mobile station is in the active state.5

l. Instruct the mobile station to terminate the PPP session.6

m. Verify the mobile station sends an LCP-terminate request to the PDSN/FA or7



n. Verify the PDSN/FA and mobile station are in the Null State.10


The PPP session shall be established. The mobile station shall not include the IP-Address12

Configuration Option in the IPCP Configure Request. The PDSN/FA shall not assign an IP13

address to the mobile station. The mobile station may send an LCP-terminate request to14

terminate the PPP session.15

4.2 Agent Discovery and Registration using Dynamic Home Address Assignment,16

Successful Scenario17

4.2.1 Definition18

This test verifies that the PDSN/FA sends Agent Advertisements upon the establishment of19

a PPP Session and the mobile station processes the Agent Advertisement correctly. The20

Mobile IP Registration Request (RRQ) and Mobile IP Registration Reply (RRP) process is21

verified.22

4.2.2 Traceability23

6.2.2.1 Agent Advertisements [2]24

6.5.2.1 Agent Discovery [2]25

6.5.2.2 Registration Messages [2]26

8/14/2019 TIA-918.pdf

26/76

TIA-918

4-4


MS PDSN

Local

RADIUS HAHome

RADIUSPPP

Agent Advertisement

MIP RRQ

Access-Request

Access-Accept

MIP RRQ

MIP RRP


a. Configure mobile station and HA to use dynamic home address assignment.3


c. Verify the PDSN/FA begins sending the configured number of Agent5

Advertisements to mobile station after the PPP session is established.6

d. Verify the Agent Advertisement contains the MN-FA Challenge Extension.7

e. Verify the mobile station responds to the Agent Advertisement and sends a valid8

Mobile IP RRQ.9

f. Verify the home address in the Mobile IP RRQ is 0.0.0.0.10

g. Verify the mobile station includes MN-FA Challenge Extension, MN-AAA11

Extension, MN-NAI Extension, and the MN-HA extension in the Mobile IP RRQ.12

h. Verify the PDSN/FA stops sending Agent Advertisements to the mobile station13

after receiving the Mobile IP RRQ or after the configured number of Agent14

Advertisements has been sent.15

i. Verify the PDSN/FA requests authentication of the MN-AAA from the RADIUS16

sever infrastructure.17

j. Verify the home RADIUS server verifies the MN-AAA extension and responds to18

the PDSN/FA via the local RADIUS server.19

k. Verify the PDSN/FA sends the Mobile IP RRQ to the HA when the successful20

authentication is received from the home RADIUS server via the local RADIUS21

server.22

l. Verify the PDSN/FA correctly acquires the mobile station home address received23

in the Mobile IP RRP from the HA.24

8/14/2019 TIA-918.pdf

27/76

8/14/2019 TIA-918.pdf

28/76

TIA-918

4-6

h. Verify the PDSN/FA stops sending Agent Advertisements to the mobile station1

after receiving the Mobile IP RRQ or after the configured number of Agent2

Advertisements has been sent.3

i. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.4

j. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the5

mobile station with the Code field set to 0 (Registration Accepted).6

k. Verify Mobile IP RRP from the PDSN/FA includes the next challenge the mobile7

station should use in its next re-registration.8

l. Verify the mobile station can send and receive IP datagrams using the mobile9

stations w.x.y.z home address.10


The mobile station shall respond to the Agent Advertisement from the PDSN/FA with a12

Mobile IP RRQ with the correct extensions. The mobile station shall set the home address to13

w.x.y.z. The PDSN/FA shall forward the Mobile IP RRP to the mobile station indicating the14registration was accepted.15

4.4 Router Advertisement Lifetime Expires16

4.4.1 Definition17

Perform this test only if the mobile station supports sending an Agent Solicitation after the18

FA Router Advertisement Lifetime expires. If sent, the FA shall respond with Agent19

Advertisements including a new FA challenge value.20





8/14/2019 TIA-918.pdf

29/76

TIA-918

4-7


MSPDSN/

FA

RouterAdvertisement

Lifetime Expires

Agent

Solicitation

Agent

Advertisement


a. Configure the Router Advertisement Lifetime to be less than the Registration3

Lifetime.4

b. Establish a Mobile IP call.5

c. Verify the PDSN/FA does not send Agent Advertisements to refresh the6

Advertisement Lifetime.7

d. Allow the Router Advertisement Lifetime to expire.8

e. Verify the mobile station sends an Agent Solicitation to the PDSN/FA.9

f. Verify the PDSN/FA sends an Agent Advertisement in response to the Agent10

Solicitation.11

g. Verify the Agent Advertisement contains an unused challenge value.12


After the expiration of the Router Advertisement Lifetime, the mobile station may send14

Agent Solicitations to the PDSN/FA. The PDSN shall not send unsolicited Agent15

Advertisements to refresh the Router Advertisement Lifetime. The Agent Advertisement16

extension sent in response to the Agent Solicitation shall contain an unused challenge17

value.18

4.5 Mobile Station Registration Request Failed, HA has Insufficient Resources19

4.5.1 Definition20

This test verifies that when the mobile station initiates a dynamic Mobile IP call, the Mobile21

IP RRQ is denied due to insufficient HA resources. The HA will not have resources either22

because the HA address pool is not configured or all IP addresses in the address pool have23

been exhausted.24

8/14/2019 TIA-918.pdf

30/76

TIA-918

4-8

4.5.2 Traceability1

3.4 Registration Reply [1]2

3.6.2 Receiving Registration Replies [1]3

3.8.2.3 Denying Invalid Requests [1]4


a. Configure the HA with insufficient resources to ensure the mobile station will6

not receive an IP address from the HA.7


c. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after9

the PPP session is established.10

d. Verify the mobile station sends a valid Mobile IP RRQ.11

e. Verify the HA sends a Mobile IP RRP to the mobile station with the code field set12

to 130, "Insufficient Resources".13

f. Verify the PDSN/FA sends the Mobile IP RRP with the code field set to 130 to the14

mobile station. If the PDSN/FA does not close the PPP session, the mobile15

station may re-send a Mobile IP RRQ to the PDSN/FA.16


The HA shall send a Mobile IP RRP to the mobile station with the code field set to 13018

indicating the HA does not have resources.19

4.6 Mobile Station Registration Request Retry20

4.6.1 Definition21

This test verifies the mobile station re-sends a Mobile IP Registration Request if the22

Registration Reply is not received. This test also verifies the mobile station uses a different23

ID in the new Registration Request. This test also verifies the mobile station and the HA24

support the mandatory replay protection using timestamps.25


3.6.3 Registration Retransmission [1]27


a. Configure the mobile station with a HA IP address.29

b. Verify the mobile station and HA are configured to use replay protection using30

timestamps as part of their security association.31


d. Instruct the mobile station to send a Mobile IP RRQ with the HA IP address set33

to the HA address.34

8/14/2019 TIA-918.pdf

31/76

TIA-918

4-9

e. Instruct the HA not to respond to the Mobile IP RRQ.1

f. Verify the mobile station re-sends the same Mobile IP RRQ with a new2

registration Identification.3


The mobile station shall use a different registration identification field in the subsequent5

Mobile IP RRQ.6

4.7 Registration Lifetime Processing7

4.7.1 Definition8

This test verifies the mobile station accepts a Mobile IP Registration Reply with the9

registration lifetime less than the requested lifetime.10


3.6 Mobile Node Considerations [1]12

6.2.2 Mobile IP Registration [2]13





3.2 Foreign Agent Processing for Agent Advertisement Requests [8]18


a. Configure the HA Registration lifetime timer to be less than the Registration20lifetime timer in the Agent Advertisement from the PDSN/FA.21




d. Verify the mobile station sends a valid Mobile IP RRQ with the Lifetime less than25

or equal to the value in the Agent Advertisement.26

e. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.27

f. Verify the HA sends a Mobile IP RRP to the PDSN/FA with the Registration28

Lifetime less than the requested value.29

g. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the30

mobile station with the Code field set to 0 (Registration Accepted). The PDSN/FA31

also shall update the binding information for the MS.32

h. Verify the mobile station attempts to re-register before the Registration Lifetime,33

decreased by the RRP lifetime difference, value received in the Mobile IP RRP34

expires.35

8/14/2019 TIA-918.pdf

32/76

TIA-918

4-10

i. Verify the mobile station Mobile IP RRQ uses a valid and unused challenge1

value.2


The mobile station shall attempt to re-register before the Registration Lifetime in the Mobile4

IP RRP expires.5

4.8 Timestamp Error6

4.8.1 Definition7

This test verifies the HA will reject the Mobile IP RRQ if the timestamp in the Mobile IP RRQ8

is incorrect when the mobile station initiates a dynamic or static Mobile IP call.9


5.6.1 Replay Protection using Timestamps [1]11


a. Configure the mobile station and HA so that the time bases are not13

synchronized.14

b. Configure the mobile station to initiate a dynamic or static Mobile IP call.15


d. Verify the PDSN/FA sends an Agent Advertisement after the PPP session is17

established.18

e. Verify the mobile station sends a Mobile IP RRQ to the PDSN/FA.19

f. Verify the HA rejects the Mobile IP RRQ with a Mobile IP RRP to the mobile20

station via the PDSN/FA with:21

Code of 133, "Registration Identification Mismatch", and22

ID with the new timestamp in the upper 32 bits and the lower 32 bits copied23

from the Mobile IP RRQ24

g. Verify the PDSN/FA does not close the PPP session.25

h. Verify the mobile station sends a valid Mobile IP RRQ with the correct ID.26

i. Verify the new Mobile IP RRQ is accepted.27


The HA shall reject the Mobile IP RRQ when the mobile station timestamp is incorrect. The29

PDSN/FA shall not close the PPP session. The mobile station shall use the new time stamp30

received in the Mobile IP RRP.31

8/14/2019 TIA-918.pdf

33/76

TIA-918

4-11

4.9 Mobile Station De-Registers1

4.9.1 Definition2

If the mobile stations supports de-registration, perform this test to verify the mobile station3

is able to de-register by setting the registration lifetime to 0 in the Mobile IP RRQ.4

4.9.2 Traceability5


3.7 Foreign Agent Considerations [1]7

3.8 Home Agent Considerations [1]8


a. Set up a mobile station originated Service Option 33 call and wait for a10

successful Mobile IP registration.11

b. Instruct the mobile station to send a valid Mobile IP RRQ with the care-of12

address for the PDSN/FA and a registration lifetime set to 0.13

c. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.14

d. Verify the HA sends a Mobile IP RRP to the PDSN/FA with the Code field set to 015

accepting the de-registration.16

e. Verify the PDSN/FA closes the PPP session.17

f. Verify the PDSN/FA clears all mobility bindings for the mobile station with the18

HA.19

g. Verify a correspondent node cannot send packets to the mobile station.20


The mobile station shall set the registration lifetime to 0 in the Mobile IP RRQ in order to22

de-register from an a specific care-of address. The PDSN/FA shall clear all mobility23

bindings to the HA.24

4.10 Simultaneous Simple IP and Mobile IP25

4.10.1 Definition26

If the mobile station supports simultaneous Simple IP and Mobile IP sessions perform this27

test to verify the PDSN/FA is capable of supporting a mobile station requesting28

simultaneous Simple IP and one or more Mobile IP sessions over a single PPP session.29




8/14/2019 TIA-918.pdf

34/76

TIA-918

4-12


a. Configure the mobile station to support multiple addresses over a single PPP2

session.3

b. Configure the mobile station with two NAIs (NAI 1 for Simple IP and NAI 2 for4

Mobile IP).5

c. Set up a mobile station originated Service Option 33 call using NAI 1.6

d. Verify the PDSN/FA proposes CHAP in the LCP Configure-Request.7

e. Verify the mobile station sends an LCP Configure-Ack.8

f. Instruct the mobile station to authenticate with the PDSN/FA using NAI 1.9

g. Verify the HA clears the mobility binding for the mobile station.10

h. Verify the PDSN/FA closes the PPP session and clears the mobility binding for11

the mobile station.12

i. Verify the mobile station can send and receive IP datagrams using the address13assigned by the PDSN (a.b.c.d).14

j. Instruct the mobile station to send an Agent Solicitation.15

k. Verify the PDSN/FA begins sending the configured number of Agent16

Advertisements to the mobile station.17

l. Verify the mobile station responds to the Agent Advertisement and sends a valid18

Mobile IP RRQ using NAI 2.19

m. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.20

n. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the21

mobile station with an assigned home address of w.x.y.z and the Code field set22

to 0 (Registration Accepted).23

o. Verify the mobile station is able to send and receive IP datagrams using the24

Simple IP session and the Mobile IP session simultaneously.25


The PDSN/FA shall support simultaneous Simple IP and Mobile IP over a single PPP27

session. The mobile station may support simultaneous Simple IP and Mobile IP over a28

single PPP session.29

8/14/2019 TIA-918.pdf

35/76

TIA-918

5-1

5 HANDOFFS1

5.1 Inter-PDSN Handoff, Mobile Station in Active State2

5.1.1 Definition3

This test verifies the successful handoff between PDSNs. The Inter-PDSN handoff will result4

in the establishment of a new PPP session, detection of the new FA and registration with5

the HA. PDSN 1 is associated with PCF 1 and PDSN 2 is associated with PCF 2.6

5.1.2 Traceability7

7.3 PDSN to PDSN Handoff [2]8

7.2 PCF to PCF handoff [2]9

2.6.6 Handoff Procedures [5]10


3.7.3.3.2.31 General Handoff Direction Message [5]12

3.7.3.3.2.36 Universal Handoff Direction Message [5]13


MS PCF 1 PDSN 1 PDSN 2

Correspondent

Node

New R-P Session

IP Traffic

R-P Session

PPP re-negotiation + Agent Advertisement

MIP RRQ

MIP RRP

MIP RRQ

GHDM/UHDM

R-P Session Expires

PCF 2 HA

Handoff Completion Message

IP Traffic

15


a. Set up a mobile station originated Service Option 33 call and wait for successful17

Mobile IP Registration on PCF 1, PDSN 1.18

b. Ensure the mobile station is in the active state.19

8/14/2019 TIA-918.pdf

36/76

TIA-918

5-2

c. Perform a CDMA handoff between PCF 1 and PCF 2. This may be accomplished1

by sending any supported CDMA handoff direction messageto the mobile2

station.3

d. Verify PCF 2 selects PDSN 2.4

e. Verify PCF 2 triggers a new R-P session setup.5

f. Verify PDSN 2 re-negotiates the PPP session.6

g. Verify PDSN 2 sends Agent Advertisements upon establishment of the PPP7

session.8

h. Verify the mobile station sends a Mobile IP RRQ to the PDSN 2.9

i. Verify authentication is successful with the RADIUS infrastructure.10

j. Verify PDSN 2 forwards the Mobile IP RRP received from the HA to the mobile11

station with the Code field set to 0 (Registration Accepted).12

k. Verify the mobile station IP address remains the same.13

l. Verify the HA correctly forwards incoming traffic to the mobile station.14

m. Verify PDSN 1 clears the PPP resources after the first R-P session expires.15


The Inter-PDSN handoff shall complete successfully. The new PPP session shall be17

established with the target PDSN. The mobile station shall re-register with the HA after the18

new PPP session is established.19

5.2 Inter-PDSN handoff, Mobile Station in Dormant State20

5.2.1 Definition21

This test verifies the mobile station can be successfully transitioned from the dormant state22

to the active state in order for an Inter-PDSN handoff to occur.23





a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs.28

b. Set up a mobile station originated Service Option 33 call and wait for successful29

MIP Registration.30

c. Allow the mobile station to go dormant.31

d. Perform an idle handoff to PCF 2.32

e. Verify the mobile station originates a Service Option 33 call on PCF 2.33

8/14/2019 TIA-918.pdf

37/76

TIA-918

5-3

f. Verify PCF 2 selects the PDSN 2.1

g. Verify PCF 2 triggers a new R-P session setup.2

h. Verify the mobile station transitions to the active state.3

i. Verify the PDSN 2 re-negotiates the PPP session.4

j. Verify the PDSN 2 sends Agent Advertisements upon establishment of the PPP5

session.6

k. Verify the mobile station sends a Mobile IP RRQ to PDSN 2.7

l. Verify authentication is successful with the RADIUS infrastructure.8

m. Verify PDSN 2 forwards the Mobile IP RRP received from the HA to the mobile9

station with the Code field set to 0 (Registration Accepted).10

n. Verify the mobile station IP address remains the same.11

o. Allow the mobile station to return to the dormant state.12


The mobile station shall transition to the active state. The Inter-PDSN handoff shall14

complete successfully. The new PPP session shall be established with the target PDSN. The15

mobile station shall re-register with the HA after the new PPP session is established.16

5.3 Intra-PDSN Handoff, Mobile Station in Active State17

5.3.1 Definition18

This test verifies the successful handoff between PCFs on the same PDSN/FA. The Intra-19

PDSN handoff will result in a continuation of the same PPP session and no Mobile IP20

registration with the HA.21


7.2 PCF to PCF Handoff [2]23





a. Set up a mobile station originated Service Option 33 call and wait for a28

successful Mobile IP registration.29

b. Ensure the mobile station is in the active state.30

c. Perform a CDMA handoff between PCF 1 and PCF 2. This may be accomplished31

by sending any supported CDMA handoff direction message to the mobile32

station.33

d. Verify PCF 2 selects the same PDSN.34

8/14/2019 TIA-918.pdf

38/76

TIA-918

5-4

e. Verify PCF 2 triggers a new R-P session.1

f. Verify the PDSN does not re-negotiate the PPP session.2

g. Verify the PDSN does not send Agent Advertisements.3

h. Verify the mobile station does not send a Mobile IP RRQ to the PDSN.4

i. Verify the mobile station is able to send and receive IP datagrams.5


The Intra-PDSN handoff shall complete successfully. No new PPP session shall be7

established. The mobile station shall not re-register with the HA. The mobile stations IP8

address shall remain the same.9

5.4 Intra-PDSN Handoff, Mobile Station in Dormant State10

5.4.1 Definition11

This test verifies the successful handoff between PCFs on the same PDSN/FA while the12

mobile station is in the dormant state. The Intra-PDSN handoff will result in a continuation13

of the same PPP session and no mobile IP registration with the HA.14





a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs.19


MIP Registration.21



e. Verify PCF 2 selects the same PDSN.24

f. Verify PCF 2 triggers a new R-P session.25

g. Verify the PDSN does not re-negotiate the PPP session.26

h. Verify the PDSN does not send Agent Advertisements upon establishment of the27

PPP session.28

i. Verify the mobile station does not send a Mobile IP RRQ to the PDSN.29

j. Verify the mobile station is able to send and receive IP datagrams.30

8/14/2019 TIA-918.pdf

39/76

TIA-918

5-5


The Intra-PDSN handoff shall complete successfully. No new PPP session shall be2

established. The mobile station shall not re-register with the HA. The mobile stations IP3

address shall remain the same.4

5.5 Simple IP Inter-PDSN Idle Handoff5

5.5.1 Definition6

This test verifies the mobile station can be successfully transitioned from the dormant state7

to the active state in order for an Inter-PDSN idle handoff to occur. The result of the8

handoff to a new PDSN is a complete restart of PPP. PDSN 1 is associated with PCF 1 and9

PDSN 2 is associated with PCF 2.10





a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs (i.e. PZID1 and15

PZID2, respectively).16


Simple IP establishment to complete.18

c. Instruct the mobile station to transition to the dormant state.19


e. Verify the mobile station transitions to the active state by originating a Service21

Option 33 call.22

f. Verify PCF 2 selects PDSN 2.23

g. Verify PCF 2 triggers a new R-P session setup.24

h. Verify PDSN 2 re-negotiates the PPP session.25

i. Verify PDSN 2 assigns a new address to the mobile station.26

j. Allow the mobile station to return to the dormant state.27

k. Perform an idle handoff back to PCF 1.28

l. Verify the mobile station originates a Service Option 33 call.29

m. Verify PDSN 1 forces a re-negotiation of the PPP session.30

n. Verify PDSN 1 assigns a topologically correct IP address to the mobile station.31

8/14/2019 TIA-918.pdf

40/76

TIA-918

5-6


The mobile station shall transition to the active state from the dormant state when a new2

R-P session is set up. The Inter-PDSN handoff shall result in a new PPP session on PDSN 2.3

A dormant handoff return to PDSN 1 also results in a restart of PPP.4

5.6 Simple IP Intra-PDSN Handoff, Mobile Station in Dormant State5

5.6.1 Definition6

This test verifies the successful Simple IP handoff between PCFs on the same PDSN while7

the mobile station is in the dormant state. The Intra-PDSN handoff will result in a8

continuation of the same PPP session and no mobile IP registration with the HA.9





a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs (i.e. PZID1 and14

PZID2, respectively).15


SIP Registration. Verify the PDSN receives the CANID information from PCF 1.17



e. Verify the mobile station originates a Service Option 33 call and includes the20

PZID value equal to PZID1.21

f. Verify PCF 2 selects the same PDSN.22

g. Verify PCF 2 triggers a new R-P session and forwards the CANID with PZID23

equal to PZID2 and the PANID with PZID equal to PZID1.24

h. Verify the PDSN does not re-negotiate the PPP session.25

i. Verify the mobile station is able to send and receive IP datagrams.26


The Simple IP Intra-PDSN handoff shall complete successfully. No new PPP session shall be28

established. The mobile station IP address shall remain the same.29

30

8/14/2019 TIA-918.pdf

41/76

TIA-918

6-1

6 AUTHENTICATION AND IPSEC SECURITY ASSOCIATION SUPPORT1

6.1 RADIUS Support, Successful Scenario2

6.1.1 Definition3

This test verifies that the PDSN acts as a RADIUS client to the Local RADIUS server. The4

PDSN shall send an Access-Request to the Local RADIUS Server. Upon successful5

authentication, the local RADIUS Server will send an Access-Accept to the PDSN via the6

local RADIUS server.7

6.1.2 Traceability8

6.2.3 RADIUS Support [2]9


3.7.2 Receiving Registration Requests [1]11

Annex C RADIUS Attributes [2]12


MS PDSN

Local

RADIUS HAHome

RADIUSPPP

Agent Advertisement

MIP RRQ Access-Request

Access-Accept

MIP RRQ

MIP RRP

Accounting-StartMIP RRP



b. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after16


c. Verify the mobile station sends a valid Mobile IP RRQ to the PDSN/FA.18

d. Verify the PDSN/FA creates an Access-Request with at least the parameters19

shown in the following table:20

8/14/2019 TIA-918.pdf

42/76

TIA-918

6-2

Parameter

User-Name

CHAP-Password

CHAP-Challenge

NAS-IP-Address

Home Agent Address

Correlation ID

1

e. Verify the Access-Request is sent to the Local RADIUS.2

f. Verify the Local RADIUS forwards the Access-Request to the Home RADIUS.3

g. Verify authentication at the Home RADIUS is successful.4

h. Verify the Home RADIUS sends an Access-Accept to the PDSN/FA via the local5

RADIUS.6

i. Verify upon receipt of the Access-Accept, the PDSN/FA sends the Mobile IP RRQ7

to the HA.8

j. Verify the HA sends a Mobile IP RRP to the PDSN/FA.9

k. Verify the PDSN/FA sends an Accounting-Start to the local RADIUS and sends10

the Mobile IP RRP to the mobile station.11

l. Transfer data to and from the mobile station and verify the data path.12

m. Verify the HA correctly forwards incoming traffic to the mobile station.13

n. End the call from the mobile station.14

o. Verify the PDSN/FA sends an Accounting-Stop to the local RADIUS.15


The PDSN/FA shall create an Access-Request upon receipt of a Mobile IP Registration17

Request. The Home RADIUS shall create an Access-Accept upon successful authentication.18

After the Access-Accept is received, the PDSN/FA shall forward the Mobile IP RRQ to the19

HA. The HA shall send a Mobile IP RRP to the mobile station.20

6.2 RADIUS Support, Unsuccessful Scenario21

6.2.1 Definition22

This test verifies the Home RADIUS will fail authentication and send an Access-Reject to23

the local RADIUS if the NAI or AAA secret key is invalid. The PDSN/FA will send a Mobile IP24

RRP with an error code of 67 indicating that the Mobile IP RRQ was rejected.25

8/14/2019 TIA-918.pdf

43/76

TIA-918

6-3

6.2.2 Traceability1

6.2.3 RADIUS Support [2]2


3.7.2 Receiving Registration Requests [1]4


a. Configure the mobile station with an invalid NAI value.6


c. Verify the mobile station sends a Registration Request to the PDSN/FA.8

d. Verify the PDSN/FA creates an Access-Request with at least the parameters9

shown in the following table:10

Parameter

User-Name

CHAP-Password

CHAP-Challenge

NAS-IP-Address

Home Agent Address

Correlation ID

e. Verify the Access-Request is sent to the Local RADIUS.11

f. Verify the Local RADIUS forwards the Access-Request to the Home RADIUS.12

g. Verify authentication at the Home RADIUS fails.13

h. Verify the Home RADIUS sends an Access-Reject to the PDSN/FA via the local14

RADIUS.15

i. Verify the PDSN/FA sends a Mobile IP RRP with the code field set to 6716

indicating the Mobile IP RRQ was rejected because the mobile station failed17

authentication.18

j. Verify the PDSN/FA does not send an Accounting-Start to the local RADIUS.19

k. Configure the mobile station with a valid NAI value and an incorrect secret key20

for the MN-AAA authentication.21

l. Repeat steps b through j.22


The Home RADIUS shall fail authentication and send an Access-Reject to the PDSN/FA.24

The PDSN/FA shall send a Mobile IP RRP with the code field set to 67 to the mobile station25

8/14/2019 TIA-918.pdf

44/76

TIA-918

6-4

indicating the registration was denied because authentication failed. The PDSN/FA shall1

not delete the security association with the HA because the mobile station is denied access.2

6.3 IPSec Security Support, Preserving of Existing Security Association3

6.3.1 Definition4

This test verifies that an existing IPSec security association between the PDSN/FA and HA5

is not compromised by the mobile station-authorized level of security.6

6.3.2 Traceability7

6.2.4 IP Security Support [2]8

6.2.2.5 Reverse Tunneling [2]9

6.3.2 IP Security Support [2]10


a. Configure the PDSN/FA and HA to have an existing IPSec security association.12


c. Verify the PDSN/FA sends an Access-Request.14

d. Verify the home RADIUS server does not authorize security for the mobile15

station.16

e. Verify the home RADIUS server sends an Access-Accept and the Security Level17

set to the value 4 (i.e. No IPSec).18

f. Verify the PDSN/FA does not delete the security association with the HA as a19

result of the home RADIUS server not authorizing security for the mobile20

station.21


The PDSN/FA and the HA shall not invalidate a pre-existing security association.23

6.4 Authentication Failure, MN-HA Authenticator is Invalid24

6.4.1 Definition25

This test verifies that the mobile station will fail authentication if the authenticator in the26

MN-HA Extension is invalid. The HA shall set the Code field in the Mobile IP RRP to 131.27


3.8.2.1 Validity Checks [1]29


a. Configure the mobile station with an invalid MN-HA shared secret.31


8/14/2019 TIA-918.pdf

45/76

TIA-918

6-5

c. Upon establishment of the PPP session, verify the PDSN/FA sends Agent1

Advertisements to the mobile station.2

d. Verify the mobile station sends a Mobile IP RRQ with the invalid authenticator in3

the MN-HA Extension.4

e. Verify the Home Agent rejects the registration in the Mobile IP RRP with the code5

field set to 131.6

f. Verify the PDSN/FA sends the Mobile IP RRP to the mobile station.7


The HA shall reject the Mobile IP RRQ when the authenticator in the MN-HA Extension is9

incorrect.10

6.5 Foreign Agent Reverse Tunnel Registration Behavior11

6.5.1 Definition12

This test verifies successful and unsuccessful enabling of the reverse tunnel based on the13

PDSN/FA and mobile station interaction.14


6.2.2.5 Reverse Tunnel [2]16


4.2 Foreign Agent Considerations [3]18



a. Configure mobile station, PDSN/FA and HA as shown below:21

Mobile RequestsReverse Tunnel

FA Allows ReverseTunnel

Reverse Tunnelingto HA required asindicated by home

RADIUS

Yes (T-Bit = 1) Yes Yes


c. Verify the PDSN/FA sends Agent Advertisements to mobile station after the PPP23

session is established.24

d. Verify the mobile station sends a Mobile IP RRQ to the PDSN/FA.25

e. Verify the PDSN/FA forwards the Mobile IP RRQ to the HA.26

f. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the27


8/14/2019 TIA-918.pdf

46/76

TIA-918

6-6

g. Transfer data to/from the mobile station and verify the data path.1

h. Verify the HA correctly de-capsulates and forwards traffic from the mobile2

station using the reverse tunnel.3

i. End the call from the mobile station.4

j. Repeat steps b through d making the following configuration changes:5




RADIUS

No (T-Bit = 0) Yes No

6

k. Verify the PDSN/FA forwards the Mobile IP RRQ to the HA.7

l. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the8


m. End the call from the mobile station.10

n. Repeat steps a through d making the following configuration changes:11




RADIUS

No (T-Bit = 0) Yes Yes

o. Verify the FA rejects the RRQ with code 75 "Reverse Tunnel Mandatory, T-Bit12

Not Set."13

p. If the PPP session is still up, verify the mobile station re-sends a Mobile IP RRQ14

to the PDSN/FA.15

q. Repeat steps a through d making the following configuration changes:16




RADIUS

Yes (T-Bit = 1) No No

r. Verify the FA rejects the RRQ with code 74, "Requested Tunnel Unavailable".17

s. If the PPP session is still up, verify the mobile station re-sends a Mobile IP RRQ18

to the PDSN/FA.19

8/14/2019 TIA-918.pdf

47/76

TIA-918

6-7

t. Repeat steps a through d making the following configuration changes:1




RADIUS

Yes (T-Bit = 1) Yes No

u. Verify the FA rejects the RRQ with code 74, "Requested Reverse Tunnel2

Unavailable."3

v. If the PPP session is still up, verify the mobile station re-sends a Mobile IP RRQ4

to the PDSN/FA.5


The PDSN/FA shall reject the Mobile IP Registration Request when the tunnel is7

unavailable or if the mobile station does not enable the T-Bit when required. Otherwise the8

Mobile IP RRQ shall be accepted.9

6.6 Private Network Support, Successful Scenario10

6.6.1 Definition11

This test verifies mobile station and PDSN/FA support private home addresses.12


6.2.2.4 Private Network Access [2]14

6.5.2.4 Private Network Support [2]15


a. Configure the mobile station, PDSN/FA, and HA to support reverse tunneling.17

b. Configure the mobile station with a private home address.18

c. Set up a mobile station initiated Service Option 33 call.19

d. Verify the PDSN/FA sends an Agent Advertisement after the PPP session has20

been established.21

e. Verify the mobile station sends a valid Mobile IP RRQ with T-Bit set to 1 and the22Home Address set to w.x.y.z.23

f. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the24


g. Transfer data to/from the mobile station and verify the data path.26

h. Verify the HA correctly de-capsulates reverse tunneled traffic from the mobile27

station.28

8/14/2019 TIA-918.pdf

48/76

TIA-918

6-8


The PDSN/FA shall support private home address. The mobile station shall enable the T-bit2

when requesting private network support.3

6.7 Private Network Support, Unsuccessful Scenario4

6.7.1 Definition5

This test verifies if the mobile station requests a private home address but does not set the6

T-Bit to 1 in the Mobile IP RRQ, the registration is rejected.7

6.7.2 Traceability8

6.2.2.4 Private Network Access [2]9

6.5.2.3 Private Network Support [2]10


a. Configure the PDSN/FA, and HA to support reverse tunneling.12

b. Configure the mobile station to not support reverse tunneling.13

c. Configure the mobile station with a private home address.14

d. Set up a mobile station initiated Service Option 33 call.15

e. Verify the PDSN/FA sends an Agent Advertisement after the PPP session has16

been established.17

f. Verify the mobile station sends a valid Mobile IP RRQ with T-Bit set to 0 and the18

Home Address set to w.x.y.z.19

g. Verify the PDSN/FA sends a Mobile IP RRP with the code field set to 75, "Reverse20Tunnel is Mandatory and T bit is not set."21


The PDSN/FA shall reject the Mobile IP RRQ when the mobile station requests a private23

home address but does not set the T bit to 1.24

6.8 Successful Authentication using the MN-AAA Extension25

6.8.1 Definition26

If the HA supports processing the MN-AAA extension this test verifies the HA can process27

the MN-AAA Authentication Extension of the Mobile IP RRQ. The HA will authenticate the28

registration by sending a RADIUS Access-Request to the Home RADIUS Server. This test29

case does not replace the fact that the PDSN/FA will be the first to perform MN-AAA30

validation with the home RADIUS server.31


6.3.4 Authentication [2]33

8/14/2019 TIA-918.pdf

49/76

TIA-918

6-9


a. Configure the HA to require processing of the MN-AAA Authentication2

Extension.3


c. Verify the PDSN/FA sends Agent Advertisements to mobile station after the PPP5

session is established.6

d. Verify the mobile station sends a valid Mobile IP RRQ to the PDSN/FA.7

e. Verify the PDSN/FA forwards the Mobile IP RRQ to the HA.8

f. Verify the HA creates a RADIUS Access-Request to the Home RADIUS server9

with the following:10

User-Name

CHAP-Password

CHAP-Challenge

g. Verify the Home RADIUS server sends a RADIUS Access-Accept to the HA.11

h. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the12



The HA shall send a RADIUS Access-Request to the Home RADIUS server when the HA is15

configured to process the MN-AAA authentication extension. The Home RADIUS server16

shall send a RADIUS Access-Accept upon successful authentication. The HA shall send a17

Mobile IP RRP to the mobile station indicating the registration is successful.18

19

8/14/2019 TIA-918.pdf

50/76

TIA-918

6-10

No text.1

8/14/2019 TIA-918.pdf

51/76

TIA-918

7-1

7 NETWORK SPECIFIC TESTS1

These network specific tests verify the elements of a Mobile IP infrastructure are compliant2

with [2]. The term mobile station used in this section refers to a mobile station or mobile3

station simulator that is capable of performing non-standard or optional behavior in order4

to test PDSN/FA and HA functionality.5

7.1 Mobile IP Registration Request with Invalid Extensions6

7.1.1 Definition7

This test verifies that if the Mobile IP RRQ contains unrecognized and unsupported8

extensions between 128 and 255, the invalid extensions are discarded, but the rest of the9

Mobile IP RRQ is processed.10


1.9 Message Format and Protocol Extensibility [1]12



b. Instruct the mobile station to send a Mobile IP RRQ with a valid, unrecognized15

extension between 128 and 255.16

c. Verify the PDSN/FA discards the extension between 128 and 255 but processes17

the rest of the message and the Mobile IP RRQ is accepted.18


The PDSN/FA shall process the Mobile IP RRQ with a valid extension but discard an20

unrecognized extension between 128 and 255.21

7.2 Foreign Agent Busy22

7.2.1 Definition23

This test verifies the PDSN/FA will send an Agent Advertisement with the B bit set to 1 to24

indicate that it is not accepting registrations from additional mobile stations.25


2.1.1 Mobility Agent Advertisement Extension [1]27



a. Configure the PDSN/FA to not accept any additional registrations.30


8/14/2019 TIA-918.pdf

52/76

TIA-918

7-2

c. Verify the PDSN/FA sends an Agent Advertisement with the B bit set to 1 in the1

Mobility Agent Advertisement Extension.2


The PDSN/FA shall send an Agent Advertisement to the mobile station with the B bit set to4

1 when it is not accepting additional resources.5

7.3 Mobile IP Registration Request Rejected, Invalid Home Address6

7.3.1 Definition7

This test verifies the HA rejects a Mobile IP RRQ from a mobile station using static home8

address assignment with an invalid home address. The HA IP address is provisioned9

correctly.10




a. Configure the mobile station to use an invalid home address (i.e. home IP14

address should be a.b.c.d but is provisioned as w.x.y.z.).15




d. Verify the mobile station sends a Mobile IP RRQ with the invalid home address.19

e. Verify the HA rejects the Mobile IP RRQ and sends Code 129.20


The HA shall reject the Mobile IP RRQ with Code 129 when the home address in the Mobile22

IP RRQ is invalid.23

7.4 Registration Rejected by FA, Poorly Formed Request24

7.4.1 Definition25

This test verifies the PDSN/FA will reject a Mobile IP RRQ that does not contain the MN-HA26

Authentication Extension. The PDSN/FA shall send a Mobile IP RRP to the mobile station27

with an error code of 70 to indicate the Mobile IP RRQ was poorly formed.28


3.3 Registration Request [1]30


6.2.2.3 Mobile IP Registration [2]32


8/14/2019 TIA-918.pdf

53/76

TIA-918

7-3


a. Configure the mobile station to not include the MN-HA Authentication Extension2

in the Mobile IP RRQ.3




d. Verify the mobile station sends a Mobile IP RRQ to the PDSN/FA without the7

MN-HA Authentication Extension.8

e. Verify the PDSN/FA sends a Mobile IP RRP to the mobile station with an error9

code of 70 to indicate the RRQ was poorly formed.10


The PDSN/FA shall reject a Mobile IP RRQ that does not include the MN-HA Extension with12

an error code of 70.13

7.5 Registration Rejected by Home Agent, Administratively Prohibited14

7.5.1 Definition15

This test verifies the HA can reject the Mobile IP RRQ for administrative reasons.16



3.6.2 Receiving Registration Replies [1]19

3.7.2.3 Denying Invalid Requests [1]20


a. Configure the HA to prohibit registrations from the mobile station.22




d. Verify the mobile station sends a valid Mobile IP RRQ to the PDSN/FA.26

e. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.27

f. Verify the HA rejects the registration.28

g. Verify the PDSN/FA sends the Mobile IP RRP with the Code field set to 129,29

"Administratively Prohibited" and the Registration Lifetime set to 0.30

h. Verify the PDSN/FA sends the Mobile IP RRP to the mobile station with the code31

field set to 129. If the PDSN/FA does not close the PPP session, the mobile32

station may re-send a Mobile IP RRQ to the PDSN/FA.33

8/14/2019 TIA-918.pdf

54/76

TIA-918

7-4


The HA shall reject the Mobile IP RRQ for administrative reasons when necessary. The2

PDSN/FA shall send the mobile station a Mobile IP RRP with the Code field set to 129.3

7.6 Agent Advertisements not sent to Mobile Station using Simple IP4

7.6.1 Definition5

This test verifies the PDSN/FA will not send Agent Advertisements to a mobile station6

configured to use Simple IP.7

7.6.2 Traceability8



a. Configure the mobile station to use Simple IP.11


c. Verify the mobile station sends an IPCP Configuration with the IP-Address set to13

0.0.0.0.14

d. Verify the PDSN assigns an IP address to the mobile station.15

e. Verify the mobile station accepts the IP address assigned by the PDSN.16

f. Verify the PPP session is established.17

g. Verify the PDSN does not send an Agent Advertisement to the mobile station.18


The PDSN/FA shall not send an Agent Advertisement to the mobile station using Simple IP20

after the PPP session is established.21

7.7 Mobile IP Registration Expires22

7.7.1 Definition23

This test verifies the PDSN/FA closes the PPP session if there is no successful re-24

registration before the registration lifetime expires.25


4.2.3 Home Agent Considerations [1]27





8/14/2019 TIA-918.pdf

55/76

TIA-918

7-5


a. Configure the mobile station to not re-register

Date post:	04-Jun-2018
Category:	Documents
Upload:	pzernik
View:	214 times
Download:	0 times