Tia 918 PDF

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
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 domestically or 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.
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 in accordance 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 WARRANTIES REGARDING 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 A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS.
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
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
TIA-918 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-8 7 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 ii
TIA-918 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-2 8.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
iii
TIA-918
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.
iv
TIA-918
No text.
TIA-918
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 recent editions of the standards indicated below. [1] [2] [3] [4] [5] [6] [7] [8] [9] RFC2002, IPv4 Mobility, May 1995. TIA/EIA/IS-835-A, cdma2000 Wireless IP Network Standard, May 2001. RFC2344, Reverse Tunneling for Mobile IP, May 1998. TIA/EIA/IS-707-A, Data Service Options for Wideband Spread Spectrum Systems. TIA/EIA/IS-2000.5-A-2, Upper Layer (Layer 3) Signaling for cdma2000 Spread Spectrum Systems. RFC 1661, The Point to Point Protocol (PPP), July 1994. RFC 3012, Mobile IPv4 Challenge/Response Extensions, Nov 2000. TIA/EIA/TSB100, Network Reference Model. TSB115, Wireless IP Architecture Based on IETF Protocols, August 2000.
[10] TIA/EIA/IS-2001-A, Access Network Interfaces Interoperability Specification, June 2001.
vi
TIA-918
1 INTRODUCTION 1.1 Purpose This document is designed to facilitate the interoperability testing between mobile stations and infrastructure supporting [2], as well as provide network specific test cases. Definitions, recommended methods of measurement, and minimum standards are provided. 1.2 Scope These technical requirements form a standard for signaling conformance in cdma2000 wireless packet data systems. These requirements ensure that a compliant mobile station and compliant network elements (PDSN, HA and RADIUS Server) can interoperate to execute tests in meeting the objectives stated in 1.1. Furthermore, network specific test requirements ensure compliant network elements for various error cases. 1.3 Network Architecture Figure 1.3-1 shows the general network architecture for Simple IP:
2 3 4 5 6
7 8 9 10 11 12
13 14
VLR
SS7 Network
HLR Home Access Provider Network
RADIUS
RADIUS Home IP Network
R-P Interface Mobile Station PDSN
IP Network
RADIUS Broker Network
RN
Visited Access Provider Network
15
16
Figure 1.3-1 Simple IP Network Architecture
17
1-1
TIA-918 Figure 1.3-2 shows the general network architecture for Mobile IP:
VLR
SS7 Network
HLR Home Access Provider Network
RADIUS
RADIUS Home IP Network
R-P Interface Mobile Station PDSN
IP Network
RADIUS Broker Network
RN
Visited Access Provider Network
HA Home IP Network, Private Network, Home Access Provider Network
2 3
Figure 1.3-2 Mobile IP Network Architecture 1.4 Requirements Language Shall and shall not identify requirements to be followed strictly to conform to the standard and from which no deviation is permitted. Should and should not indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. May and need not indicate a course of action permissible within the limits of the standard. Can and cannot are used for statements of possibility and capability, whether material, physical, or causal. 1.5 Document Organization This document is organized into the following sections: Section 1 Introduction: This section describes the document purpose and scope as well as document organization.
4 5 6 7 8 9 10 11 12
13 14 15 16
1-2
TIA-918 Section 2 Glossary and Definitions: This section includes the list of acronyms and definitions used throughout the document. Section 3: This section describes the test setups, procedures, and minimum requirements for interoperability testing between the mobile station and PDSN supporting Simple IP service. Section 4: This section describes the test setups, procedures, and minimum requirements for interoperability testing between the mobile station and PDSN supporting Mobile IP service. Section 5: This section describes the test setups, procedures, and minimum requirements for interoperability testing of Simple IP and Mobile IP handoffs. Section 6: This section describes the test setups procedures, and minimum requirements for testing RADIUS support, authentication, and reverse tunneling behavior. Section 7: This section describes the test setups, procedures, and minimum requirements for network specific testing of Simple IP and Mobile IP infrastructure elements associated with registration, addressing, security association and agent advertisement. Section 8: This section describes the test setups, procedures, and minimum requirements for network specific testing of Mobile IP infrastructure elements associated with accounting for Simple IP and Mobile IP.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
1-3
TIA-918
2 GLOSSARY AND DEFINITIONS 2.1 Acronyms Table 2.1 List of Abbreviations Acronym AAA ACCM AH CA CANID CCP CHAP COA CRL DSA DOI ESP FA FAC HA HLR IANA IETF IKE IMSI IMT-2000 IP IPCP IPsec IRM Expansion Authentication, Authorization, and Accounting Asynchronous Control Character Map Authentication Header Certificate Authority Current Access Network IDentifiers Compression Control Protocol Challenge Handshake Authentication Protocol Care-of-Address Certificate Revocation List Digital Signature Algorithm Domain of Interpretation Encapsulating Security Payload Foreign Agent Foreign Agent Challenge Home Agent Home Location Register Internet Assigned Numbering Authority Internet Engineering Task Force Internet Key Exchange International Mobile Station Identity International Mobile Telecommunications - 2000 Internet Protocol IP Control Protocol IP Security International roaming MIN
2-1
TIA-918
Acronym ISAKMP ISP LAC LCP MAC MIN MIP MS MN MSID NAI PAP PANID PCF PDSN PL PPP PSI PZID QoS RADIUS RN RRP RRQ RSA SA SHA SPI SS7 TCP UDR
Expansion Internet Security Association and Key Management Protocol Internet Service Provider Link Access Control Link Control Protocol Medium Access Control Mobile Identification Number Mobile IP Mobile Station Mobile Node Mobile Station ID Network Access Identifier Password Authentication Protocol Previous Access Network IDentifiers Packet Control Function Packet Data Serving Node Physical Layer Point-to-Point Protocol PCF Session ID Packet Zone ID Quality of Service Remote Authentication Dial In User Service Radio Network Mobile IP Registration Reply Mobile IP Registration Request Rivest-Shamir-Adleman public key algorithm Security Association Secure Hash Algorithm Security Parameter Index Signaling System 7 Transmission Control Protocol Usage Data Record
2-2
TIA-918
Acronym UDP VLR

1
Expansion User Datagram Protocol Visitor Location Register
2 3 4
2.2 Terms and Definitions Access Provider Network: An IMT-2000 wireless network providing access to the mobile user. 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.
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
Broker RADIUS Network: A network with an administrative domain that contains the Broker RADIUS. Home RADIUS: The RADIUS server that resides in the Home IP Network. Home Access Provider Network: The IMT-2000 wireless network that is the home for the mobile subscriber unit. The user may have a different home network for data services. Home IP Network: The home network that provides IP based data services to the user. This network is where the user's NAI is homed. This network may be a private corporate network, publicly accessible ISP network, or an IMT-2000 network. IMT-2000 network: An IMT-2000 home/visited network is characterized by its ability to provide IMT-2000 capabilities to its users as identified in the IMT-2000 capability sets (ITUQ.1701). Packet control function: See Radio Network. Packet data service: A general term describing a packet switched data service offered by an IMT-2000 network to a mobile subscriber (user). Packet data service option: A service option provides a means between MS and RN to establish and maintain cdma2000 Traffic Channels for packet data service. Packet data session: Describes an instance of continuous use of packet data service by the user. A packet data session begins when the user invokes packet data service. A packet data session ends when the user or the network terminates packet data service. During a particular packet data session, the user may change locations but the same IP address is maintained. For Simple IP service, moving from the coverage area of one PDSN to another PDSN constitutes a change in packet data session because a new IP address is assigned by the new PDSN. For Simple IP service, a packet data session and a PPP session are concurrent. For Mobile IP service, a packet data session can span several PDSNs as long as the user continuously maintains mobility bindings at the Home Agent and there is no lapse
2-3
TIA-918 in Mobile IP registrations/re-registrations (i.e., the IP address is persistent). For Mobile IP service, the Packet Data session can exist through several changes of the PPP session. PPP Session: A PPP session describes the time during which a particular PPP connection instance is maintained in the open state in both the mobile station and PDSN. The PPP session is maintained during periods when the mobile station is dormant. If a user hands off from one RN to another RN but is still connected to the same PDSN, the PPP session remains. If a user changes PDSN, a new PPP session is created at the new PDSN. Private Network: A Home IP Network that resides behind a firewall and that may use private IP addresses. Radio Network: The RN is equivalent to the BS as defined in [9], and corresponds to the collection of radio access equipment that includes the functional entities Radio Resource Control (RRC) and Packet Control Function (PCF) as described in [10]. At times the terms PCF and RN are used interchangeably in this document when describing handoffs across the R-P interface. R-P Interface: The interface between the Radio Network (specifically the PCF) and the PDSN. This interface is also referred to as the Aquater interface and the A10/A11 interface in [11]. R-P session: The R-P session is a logical connection established over the R-P interface for a particular PPP session. If a user changes RNs during packet data service, the R-P session between the previous RN and PDSN is released and a new R-P session is established between the new RN and the same (or new) PDSN. Service Provider Network: An IMT-2000 network operated by either the home service provider or the visited service provider. The home service provider maintains the customer business relationship with the user. The visited service provider provides IMT-2000 access services through the establishment of a service agreement with a home service provider. Visited Access Provider Network: The IMT-2000 cellular network providing service to the user when he is roaming outside his home access provider network. Visited RADIUS: The RADIUS server that resides in the Visited Access Provider Network.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
2-4
TIA-918
3 SIMPLE IP TESTS 3.1 Simple IP Establishment without Authentication of the Mobile Station 3.1.1 Definition If the mobile station can be configured to not use CHAP or PAP authentication, this test verifies that the mobile station and PDSN can successfully negotiate a PPP session during a Simple IP session. This test verifies the mobile station can successfully terminate the PPP session. 3.1.2 Traceability 5.1.1 5.2.1.3 5.2.1.4 5.4.1 5.2.1.2 PPP Session [2] Authentication [2] Addressing with IPCP [2] PPP Session [2] Termination [2]
3 4 5 6 7
8 9 10 11 12 13
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
3.1.3 Method of Measurement a. Configure mobile station to initiate Simple IP service. b. Configure the PDSN to not require authentication of the mobile station. c. Set up a mobile station originated Service Option 33 call. d. Verify the PDSN proposes CHAP in the LCP Configure-Request. e. Verify the mobile station sends an LCP Configure-Reject rejecting the authentication option. f. Verify the PDSN sends a new LCP Configure-Request without the authentication option.
g. Verify the mobile station sends an LCP Configure-Ack to the PDSN. h. Verify the mobile station sends an IPCP Configure-Request to the PDSN that includes the IP-Address Configuration Option with an IP address of 0.0.0.0. i. j. Verify the PDSN assigns an IP address to the mobile station. Once the PPP session has been established and the mobile station is on the traffic channel, instruct the mobile station to terminate the PPP session.
k. Verify the mobile station sends an LCP-terminate request to the PDSN or signaling messages with Service Inactive indicator before terminating the packet data session with the RN. l. Verify the PDSN and mobile station are in the Null State.
3-1
TIA-918 3.1.4 Minimum Standard The mobile station shall establish a PPP session. The PDSN shall assign an IP address to the mobile station. The mobile station may send an LCP-terminate request to terminate the PPP session. 3.2 Simple IP Establishment with CHAP 3.2.1 Definition This test verifies the proper operation of Simple IP with CHAP authentication. This test verifies the mobile station can terminate the PPP session. 3.2.2 Traceability 5.2.1.3 5.4.1.3 Authentication [2] Authentication [2]
1 2 3 4
6 7 8
9 10 11
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
3.2.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Verify the PDSN proposes CHAP in the LCP Configure-Request. c. Verify the mobile station sends an LCP Configure-Ack to the PDSN. d. Verify the PDSN sends a CHAP Challenge to the mobile station. e. Verify the mobile station sends a CHAP Response to the PDSN. f. Verify the PDSN sends a CHAP Success to the mobile station
g. Verify the mobile station sends an IPCP Configure-Request to the PDSN that includes the IP-Address Configuration Option with address 0.0.0.0. h. Verify the PDSN assigns an IP address to the mobile station. i. j. Instruct the mobile to terminate PPP. Verify the mobile station sends an LCP-terminate request to the PDSN or signaling messages with Service Inactive indicator before terminating the packet data session with the RN.
k. Verify the PDSN and mobile station are in the Null State. 3.2.4 Minimum Standard The mobile station shall support CHAP authentication for Simple IP. The PDSN shall authenticate the mobile station using CHAP. The mobile station may send an LCPterminate request to terminate the PPP session.
27 28 29 30
3-2
TIA-918 3.3 Simple IP Establishment with PAP 3.3.1 Definition If the mobile station supports using PAP and can be configured to prefer PAP instead of CHAP, this test verifies the proper operation of Simple IP with PAP authentication. 3.3.2 Traceability 5.2.1.3 5.4.1.3 Authentication [2] Authentication [2]
2 3 4
5 6 7
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
3.3.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Verify the PDSN proposes CHAP in the LCP Configure-Request. c. Verify the mobile station sends an LCP Configure-Nack to the PDSN proposing PAP. d. Verify the PDSN sends an LCP Configure-Request with PAP. e. Verify the mobile station sends a PAP Auth-Response to the PDSN. f. Verify the PDSN sends a PAP Auth-Ack to the mobile station.
g. Verify the mobile station sends an IPCP Configure-Request to the PDSN that includes the IP-Address Configuration Option with address 0.0.0.0. h. Verify the PDSN assigns an IP address to the mobile station. i. j. Instruct the mobile station to terminate PPP. Verify the mobile station sends an LCP-terminate request to the PDSN or signaling messages with Service Inactive indicator before terminating the packet data session with the RN.
k. Verify the PDSN and mobile station are in the Null State. 3.3.4 Minimum Standard The mobile station may support PAP authentication for Simple IP. The PDSN shall authenticate the mobile station using PAP. The mobile station may send an LCP-terminate request to terminate the PPP session.
24 25 26 27
3-3
TIA-918
4 AGENT DISCOVERY AND REGISTRATION 4.1 Successful PPP Negotiation and Termination 4.1.1 Definition This test verifies that the mobile station and PDSN/FA can successfully negotiate a PPP session when initiating a Mobile IP call. This test verifies the mobile station will not include an IP-Address Configuration Option in the IPCP Configure-Request and the PDSN shall not assign an IP address to the mobile station in IPCP. This test also verifies the mobile station can successfully terminate the PPP session. 4.1.2 Traceability 6.1.1 6.2.1.3 6.2.1.4 6.2.2.2 6.5.1.2 PPP Session [2] Authentication [2] Addressing with IPCP [2] Addressing and Mobile IP [2] Termination [2]
3 4 5 6 7 8
9 10 11 12 13 14
4-1
TIA-918 4.1.3 Call Flow Example
MS Service Option 33 Call
PDSN/FA
LCP Configure-Request Proposing CHAP LCP Configure-Reject LCP Configure-Request without CHAP LCP Configuration Ack IPCP Configure-Request without IP-Address Configuration Option
Successful Mobile IP Registration MS wishes to terminate PPP session
IPCP Configuration Ack
LCP Terminate-Request
3 4 5 6 7 8 9 10 11 12 13 14 15 16
4.1.4 Method of Measurement a. Configure mobile station and Home Agent (HA) to use static or dynamic home address assignment. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA proposes CHAP in the LCP Configure-Request. d. Verify the mobile station sends an LCP Configure-Reject rejecting the authentication option. e. Verify the PDSN/FA sends a new LCP Configure-Request without the authentication option. f. Verify the mobile station sends an LCP Configure-Ack to the PDSN/FA.
g. Verify the mobile station sends an IPCP Configure-Request to the PDSN/FA that does not include the IP-Address Configuration Option. h. Verify the PDSN/FA sends an IPCP Configure-Reject to the mobile station if the Mobile IPv4 Configuration Option is included in the IPCP Configure-Request.
4-2
TIA-918 i. j. Verify the PDSN/FA CONF_ACKs the mobile request without assigning an IP address to the mobile station. Once the PPP session has been established, verify a successful Mobile IP registration occurs following an Agent Advertisement from the PDSN/FA.
1 2 3 4 5 6 7 8 9 10
k. Ensure the mobile station is in the active state. l. Instruct the mobile station to terminate the PPP session.
m. Verify the mobile station sends an LCP-terminate request to the PDSN/FA or signaling messages with Service Inactive indicator before terminating the packet data session with the RN. n. Verify the PDSN/FA and mobile station are in the Null State. 4.1.5 Minimum Standard The PPP session shall be established. The mobile station shall not include the IP-Address Configuration Option in the IPCP Configure Request. The PDSN/FA shall not assign an IP address to the mobile station. The mobile station may send an LCP-terminate request to terminate the PPP session. 4.2 Agent Discovery and Registration using Dynamic Home Address Assignment, Successful Scenario 4.2.1 Definition This test verifies that the PDSN/FA sends Agent Advertisements upon the establishment of a PPP Session and the mobile station processes the Agent Advertisement correctly. The Mobile IP Registration Request (RRQ) and Mobile IP Registration Reply (RRP) process is verified. 4.2.2 Traceability 6.2.2.1 6.5.2.1 6.5.2.2 Agent Advertisements [2] Agent Discovery [2] Registration Messages [2]
11 12 13 14 15
16 17
18 19 20 21 22
23 24 25 26
4-3
MS
PPP
PDSN
Local RADIUS
HA
Home RADIUS
Agent Advertisement MIP RRQ Access-Request Access-Accept MIP RRQ MIP RRP
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
4.2.4 Method of Measurement a. Configure mobile station and HA to use dynamic home address assignment. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to mobile station after the PPP session is established. d. Verify the Agent Advertisement contains the MN-FA Challenge Extension. e. Verify the mobile station responds to the Agent Advertisement and sends a valid Mobile IP RRQ. f. Verify the home address in the Mobile IP RRQ is 0.0.0.0.
g. Verify the mobile station includes MN-FA Challenge Extension, MN-AAA Extension, MN-NAI Extension, and the MN-HA extension in the Mobile IP RRQ. h. Verify the PDSN/FA stops sending Agent Advertisements to the mobile station after receiving the Mobile IP RRQ or after the configured number of Agent Advertisements has been sent. i. j. Verify the PDSN/FA requests authentication of the MN-AAA from the RADIUS sever infrastructure. Verify the home RADIUS server verifies the MN-AAA extension and responds to the PDSN/FA via the local RADIUS server.
k. Verify the PDSN/FA sends the Mobile IP RRQ to the HA when the successful authentication is received from the home RADIUS server via the local RADIUS server. l. Verify the PDSN/FA correctly acquires the mobile station home address received in the Mobile IP RRP from the HA.
4-4
TIA-918 m. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). n. Verify Mobile IP RRP from the PDSN/FA includes the next challenge the mobile station should use in its next re-registration. o. Verify the mobile station can send and receive IP datagrams using the mobile stations assigned home address. 4.2.5 Minimum Standard The mobile station shall respond to the Agent Advertisement from the PDSN/FA with a Mobile IP RRQ with the correct extensions. The mobile station shall set the Home Address to 0.0.0.0. The PDSN/FA shall forward the Mobile IP RRP to the mobile station indicating the registration was accepted. 4.3 Agent Discovery and Registration using Static Home Address Assignment, Successful Scenario 4.3.1 Definition This test verifies that the PDSN/FA sends Agent Advertisements upon the establishment of a PPP Session and the mobile station processes the Agent Advertisement correctly. This test also verifies the Mobile IP Registration Request (RRQ) and Mobile IP Registration Reply (RRP) are processed correctly. 4.3.2 Traceability 6.2.2.1 6.5.2.1 6.5.2.2 Agent Advertisements [2] Agent Discovery [2] Registration Messages [2]
1 2 3 4 5 6
7 8 9 10 11
12 13
14 15 16 17 18
19 20 21 22
23 24 25 26 27 28 29 30 31 32 33 34
4.3.3 Method of Measurement a. Configure mobile station and HA to use static home address assignment. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to mobile station after the PPP session. d. Verify the Agent Advertisement contains the MN-FA Challenge Extension. e. Verify the mobile station responds to the Agent Advertisement and sends a Mobile IP RRQ. f. Verify the Mobile IP RRQ contains the home address w.x.y.z as configured in the mobile station.
g. Verify the mobile station includes MN-FA Challenge Extension, MN-AAA Extension, MN-NAI Extension, and the MN-HA extension in the Mobile IP RRQ.
4-5
TIA-918 h. Verify the PDSN/FA stops sending Agent Advertisements to the mobile station after receiving the Mobile IP RRQ or after the configured number of Agent Advertisements has been sent. i. j. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted).
1 2 3 4 5 6 7 8 9 10
k. Verify Mobile IP RRP from the PDSN/FA includes the next challenge the mobile station should use in its next re-registration. l. Verify the mobile station can send and receive IP datagrams using the mobile stations w.x.y.z home address.
11 12 13 14 15
4.3.4 Minimum Standard The mobile station shall respond to the Agent Advertisement from the PDSN/FA with a Mobile IP RRQ with the correct extensions. The mobile station shall set the home address to w.x.y.z. The PDSN/FA shall forward the Mobile IP RRP to the mobile station indicating the registration was accepted. 4.4 Router Advertisement Lifetime Expires 4.4.1 Definition Perform this test only if the mobile station supports sending an Agent Solicitation after the FA Router Advertisement Lifetime expires. If sent, the FA shall respond with Agent Advertisements including a new FA challenge value. 4.4.2 Traceability 6.2.2.1 6.5.2.1 6.5.2.2 Agent Advertisements [2] Agent Discovery [2] Registration Messages [2]
16
17 18 19 20
21 22 23 24
4-6
MS
Router Advertisement Lifetime Expires
PDSN/ FA
Agent Solicitation Agent Advertisement
2 3 4 5 6 7 8 9 10 11 12
4.4.4 Method of Measurement a. Configure the Router Advertisement Lifetime to be less than the Registration Lifetime. b. Establish a Mobile IP call. c. Verify the PDSN/FA does not send Agent Advertisements to refresh the Advertisement Lifetime. d. Allow the Router Advertisement Lifetime to expire. e. Verify the mobile station sends an Agent Solicitation to the PDSN/FA. f. Verify the PDSN/FA sends an Agent Advertisement in response to the Agent Solicitation.
g. Verify the Agent Advertisement contains an unused challenge value. 4.4.5 Minimum Standard After the expiration of the Router Advertisement Lifetime, the mobile station may send Agent Solicitations to the PDSN/FA. The PDSN shall not send unsolicited Agent Advertisements to refresh the Router Advertisement Lifetime. The Agent Advertisement extension sent in response to the Agent Solicitation shall contain an unused challenge value. 4.5 Mobile Station Registration Request Failed, HA has Insufficient Resources 4.5.1 Definition This test verifies that when the mobile station initiates a dynamic Mobile IP call, the Mobile IP RRQ is denied due to insufficient HA resources. The HA will not have resources either because the HA address pool is not configured or all IP addresses in the address pool have been exhausted.
13 14 15 16 17 18
19
20 21 22 23 24
4-7
TIA-918 4.5.2 Traceability 3.4 3.6.2 3.8.2.3 Registration Reply [1] Receiving Registration Replies [1] Denying Invalid Requests [1]
1 2 3 4
5 6 7 8 9 10 11 12 13 14 15 16
4.5.3 Method of Measurement a. Configure the HA with insufficient resources to ensure the mobile station will not receive an IP address from the HA. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after the PPP session is established. d. Verify the mobile station sends a valid Mobile IP RRQ. e. Verify the HA sends a Mobile IP RRP to the mobile station with the code field set to 130, "Insufficient Resources". f. Verify the PDSN/FA sends the Mobile IP RRP with the code field set to 130 to the mobile station. If the PDSN/FA does not close the PPP session, the mobile station may re-send a Mobile IP RRQ to the PDSN/FA.
17 18 19
4.5.4 Minimum Standard The HA shall send a Mobile IP RRP to the mobile station with the code field set to 130 indicating the HA does not have resources. 4.6 Mobile Station Registration Request Retry 4.6.1 Definition This test verifies the mobile station re-sends a Mobile IP Registration Request if the Registration Reply is not received. This test also verifies the mobile station uses a different ID in the new Registration Request. This test also verifies the mobile station and the HA support the mandatory replay protection using timestamps. 4.6.2 Traceability 3.6.3 Registration Retransmission [1]
20
21 22 23 24 25
26 27
28 29 30 31 32 33 34
4.6.3 Method of Measurement a. Configure the mobile station with a HA IP address. b. Verify the mobile station and HA are configured to use replay protection using timestamps as part of their security association. c. Set up a mobile station originated Service Option 33 call. d. Instruct the mobile station to send a Mobile IP RRQ with the HA IP address set to the HA address.
4-8
TIA-918 e. Instruct the HA not to respond to the Mobile IP RRQ. f. Verify the mobile station re-sends the same Mobile IP RRQ with a new registration Identification.
1 2 3
4 5 6
4.6.4 Minimum Standard The mobile station shall use a different registration identification field in the subsequent Mobile IP RRQ. 4.7 Registration Lifetime Processing 4.7.1 Definition This test verifies the mobile station accepts a Mobile IP Registration Reply with the registration lifetime less than the requested lifetime. 4.7.2 Traceability 3.6 6.2.2 6.2.2.1 6.5.2 6.5.2.1 6.5.2.2 3.2 Mobile Node Considerations [1] Mobile IP Registration [2] Agent Advertisements [2] Mobile IP Registration [2] Agent Discovery [2] Registration Messages [2] Foreign Agent Processing for Agent Advertisement Requests [8]
8 9 10
11 12 13 14 15 16 17 18
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
4.7.3 Method of Measurement a. Configure the HA Registration lifetime timer to be less than the Registration lifetime timer in the Agent Advertisement from the PDSN/FA. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after the PPP session is established. d. Verify the mobile station sends a valid Mobile IP RRQ with the Lifetime less than or equal to the value in the Agent Advertisement. e. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. f. Verify the HA sends a Mobile IP RRP to the PDSN/FA with the Registration Lifetime less than the requested value.
g. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). The PDSN/FA also shall update the binding information for the MS. h. Verify the mobile station attempts to re-register before the Registration Lifetime, decreased by the RRP lifetime difference, value received in the Mobile IP RRP expires.
4-9
TIA-918 i. Verify the mobile station Mobile IP RRQ uses a valid and unused challenge value.
1 2
3 4 5
4.7.4 Minimum Standard The mobile station shall attempt to re-register before the Registration Lifetime in the Mobile IP RRP expires. 4.8 Timestamp Error 4.8.1 Definition This test verifies the HA will reject the Mobile IP RRQ if the timestamp in the Mobile IP RRQ is incorrect when the mobile station initiates a dynamic or static Mobile IP call. 4.8.2 Traceability 5.6.1 Replay Protection using Timestamps [1]
7 8 9
10 11
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
4.8.3 Method of Measurement a. Configure the mobile station and HA so that the time bases are not synchronized. b. Configure the mobile station to initiate a dynamic or static Mobile IP call. c. Set up a mobile station originated Service Option 33 call. d. Verify the PDSN/FA sends an Agent Advertisement after the PPP session is established. e. Verify the mobile station sends a Mobile IP RRQ to the PDSN/FA. f. Verify the HA rejects the Mobile IP RRQ with a Mobile IP RRP to the mobile station via the PDSN/FA with: Code of 133, "Registration Identification Mismatch", and ID with the new timestamp in the upper 32 bits and the lower 32 bits copied from the Mobile IP RRQ
g. Verify the PDSN/FA does not close the PPP session. h. Verify the mobile station sends a valid Mobile IP RRQ with the correct ID. i. Verify the new Mobile IP RRQ is accepted.
28 29 30 31
4.8.4 Minimum Standard The HA shall reject the Mobile IP RRQ when the mobile station timestamp is incorrect. The PDSN/FA shall not close the PPP session. The mobile station shall use the new time stamp received in the Mobile IP RRP.
4-10
TIA-918 4.9 Mobile Station De-Registers 4.9.1 Definition If the mobile stations supports de-registration, perform this test to verify the mobile station is able to de-register by setting the registration lifetime to 0 in the Mobile IP RRQ. 4.9.2 Traceability 3.6 3.7 3.8 Mobile Node Considerations [1] Foreign Agent Considerations [1] Home Agent Considerations [1]
2 3 4
5 6 7 8
9 10 11 12 13 14 15 16 17 18 19 20
4.9.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call and wait for a successful Mobile IP registration. b. Instruct the mobile station to send a valid Mobile IP RRQ with the care-of address for the PDSN/FA and a registration lifetime set to 0. c. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. d. Verify the HA sends a Mobile IP RRP to the PDSN/FA with the Code field set to 0 accepting the de-registration. e. Verify the PDSN/FA closes the PPP session. f. Verify the PDSN/FA clears all mobility bindings for the mobile station with the HA.
g. Verify a correspondent node cannot send packets to the mobile station. 4.9.4 Minimum Standard The mobile station shall set the registration lifetime to 0 in the Mobile IP RRQ in order to de-register from an a specific care-of address. The PDSN/FA shall clear all mobility bindings to the HA. 4.10 Simultaneous Simple IP and Mobile IP 4.10.1 Definition If the mobile station supports simultaneous Simple IP and Mobile IP sessions perform this test to verify the PDSN/FA is capable of supporting a mobile station requesting simultaneous Simple IP and one or more Mobile IP sessions over a single PPP session. 4.10.2 Traceability 6.2.1 6.5.1 PPP Session [2] PPP Session [2]
21 22 23 24
25
26 27 28 29
30 31 32
4-11
TIA-918 4.10.3 Method of Measurement a. Configure the mobile station to support multiple addresses over a single PPP session. b. Configure the mobile station with two NAIs (NAI 1 for Simple IP and NAI 2 for Mobile IP). c. Set up a mobile station originated Service Option 33 call using NAI 1. d. Verify the PDSN/FA proposes CHAP in the LCP Configure-Request. e. Verify the mobile station sends an LCP Configure-Ack. f. Instruct the mobile station to authenticate with the PDSN/FA using NAI 1.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
g. Verify the HA clears the mobility binding for the mobile station. h. Verify the PDSN/FA closes the PPP session and clears the mobility binding for the mobile station. i. j. Verify the mobile station can send and receive IP datagrams using the address assigned by the PDSN (a.b.c.d). Instruct the mobile station to send an Agent Solicitation.
k. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to the mobile station. l. Verify the mobile station responds to the Agent Advertisement and sends a valid Mobile IP RRQ using NAI 2.
m. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. n. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with an assigned home address of w.x.y.z and the Code field set to 0 (Registration Accepted). o. Verify the mobile station is able to send and receive IP datagrams using the Simple IP session and the Mobile IP session simultaneously. 4.10.4 Minimum Standard The PDSN/FA shall support simultaneous Simple IP and Mobile IP over a single PPP session. The mobile station may support simultaneous Simple IP and Mobile IP over a single PPP session.
26 27 28 29
4-12
TIA-918
5 HANDOFFS 5.1 Inter-PDSN Handoff, Mobile Station in Active State 5.1.1 Definition This test verifies the successful handoff between PDSNs. The Inter-PDSN handoff will result in the establishment of a new PPP session, detection of the new FA and registration with the HA. PDSN 1 is associated with PCF 1 and PDSN 2 is associated with PCF 2. 5.1.2 Traceability 7.3 7.2 2.6.6 3.6.6 PDSN to PDSN Handoff [2] PCF to PCF handoff [2] Handoff Procedures [5] Handoff Procedures [5] General Handoff Direction Message [5] Universal Handoff Direction Message [5]
3 4 5 6
7 8 9 10 11 12 13
3.7.3.3.2.31 3.7.3.3.2.36
14
5.1.3 Call Flow Example

Correspondent Node
MS
PCF 1
PCF 2 R-P Session
PDSN 1 IP Traffic
PDSN 2
HA
GHDM/UHDM
New R-P Session
PPP re-negotiation + Agent Advertisement MIP RRQ MIP RRQ MIP RRP R-P Session Expires
Handoff Completion Message
IP Traffic
15
16 17 18 19
5.1.4 Method of Measurement a. Set up a mobile station originated Service Option 33 call and wait for successful Mobile IP Registration on PCF 1, PDSN 1. b. Ensure the mobile station is in the active state.
5-1
TIA-918 c. Perform a CDMA handoff between PCF 1 and PCF 2. This may be accomplished by sending any supported CDMA handoff direction message to the mobile station. d. Verify PCF 2 selects PDSN 2. e. Verify PCF 2 triggers a new R-P session setup. f. Verify PDSN 2 re-negotiates the PPP session.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
g. Verify PDSN 2 sends Agent Advertisements upon establishment of the PPP session. h. Verify the mobile station sends a Mobile IP RRQ to the PDSN 2. i. j. Verify authentication is successful with the RADIUS infrastructure. Verify PDSN 2 forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted).
k. Verify the mobile station IP address remains the same. l. Verify the HA correctly forwards incoming traffic to the mobile station.
m. Verify PDSN 1 clears the PPP resources after the first R-P session expires. 5.1.5 Minimum Standard The Inter-PDSN handoff shall complete successfully. The new PPP session shall be established with the target PDSN. The mobile station shall re-register with the HA after the new PPP session is established. 5.2 Inter-PDSN handoff, Mobile Station in Dormant State 5.2.1 Definition This test verifies the mobile station can be successfully transitioned from the dormant state to the active state in order for an Inter-PDSN handoff to occur. 5.2.2 Traceability 7.3 7.2 PDSN to PDSN Handoff [2] PCF to PCF handoff [2]
16 17 18 19
20
21 22 23
24 25 26
27 28 29 30 31 32 33
5.2.3 Method of Measurement a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs. b. Set up a mobile station originated Service Option 33 call and wait for successful MIP Registration. c. Allow the mobile station to go dormant. d. Perform an idle handoff to PCF 2. e. Verify the mobile station originates a Service Option 33 call on PCF 2.
5-2
TIA-918 f. Verify PCF 2 selects the PDSN 2.
1 2 3 4 5 6 7 8 9 10 11 12
g. Verify PCF 2 triggers a new R-P session setup. h. Verify the mobile station transitions to the active state. i. j. Verify the PDSN 2 re-negotiates the PPP session. Verify the PDSN 2 sends Agent Advertisements upon establishment of the PPP session.
k. Verify the mobile station sends a Mobile IP RRQ to PDSN 2. l. Verify authentication is successful with the RADIUS infrastructure.
m. Verify PDSN 2 forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). n. Verify the mobile station IP address remains the same. o. Allow the mobile station to return to the dormant state. 5.2.4 Minimum Standard The mobile station shall transition to the active state. The Inter-PDSN handoff shall complete successfully. The new PPP session shall be established with the target PDSN. The mobile station shall re-register with the HA after the new PPP session is established. 5.3 Intra-PDSN Handoff, Mobile Station in Active State 5.3.1 Definition This test verifies the successful handoff between PCFs on the same PDSN/FA. The IntraPDSN handoff will result in a continuation of the same PPP session and no Mobile IP registration with the HA. 5.3.2 Traceability 7.2 7.3 2.6.6 3.6.6 PCF to PCF Handoff [2] PDSN to PDSN Handoff [2] Handoff Procedures [5] Handoff Procedures [5]
13 14 15 16
17
18 19 20 21
22 23 24 25 26
27 28 29 30 31 32 33 34
5.3.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call and wait for a successful Mobile IP registration. b. Ensure the mobile station is in the active state. c. Perform a CDMA handoff between PCF 1 and PCF 2. This may be accomplished by sending any supported CDMA handoff direction message to the mobile station. d. Verify PCF 2 selects the same PDSN.
5-3
TIA-918 e. Verify PCF 2 triggers a new R-P session. f. Verify the PDSN does not re-negotiate the PPP session.
1 2 3 4 5
g. Verify the PDSN does not send Agent Advertisements. h. Verify the mobile station does not send a Mobile IP RRQ to the PDSN. i. Verify the mobile station is able to send and receive IP datagrams.
6 7 8 9
5.3.4 Minimum Standard The Intra-PDSN handoff shall complete successfully. No new PPP session shall be established. The mobile station shall not re-register with the HA. The mobile stations IP address shall remain the same. 5.4 Intra-PDSN Handoff, Mobile Station in Dormant State 5.4.1 Definition This test verifies the successful handoff between PCFs on the same PDSN/FA while the mobile station is in the dormant state. The Intra-PDSN handoff will result in a continuation of the same PPP session and no mobile IP registration with the HA. 5.4.2 Traceability 7.3 7.2 PDSN to PDSN Handoff [2] PCF to PCF handoff [2]
10
11 12 13 14
15 16 17
18 19 20 21 22 23 24 25 26 27 28 29 30
5.4.3 Method of Measurement a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs. b. Set up a mobile station originated Service Option 33 call and wait for successful MIP Registration. c. Allow the mobile station to go dormant. d. Perform an idle handoff to PCF 2. e. Verify PCF 2 selects the same PDSN. f. Verify PCF 2 triggers a new R-P session.
g. Verify the PDSN does not re-negotiate the PPP session. h. Verify the PDSN does not send Agent Advertisements upon establishment of the PPP session. i. j. Verify the mobile station does not send a Mobile IP RRQ to the PDSN. Verify the mobile station is able to send and receive IP datagrams.
5-4
TIA-918 5.4.4 Minimum Standard The Intra-PDSN handoff shall complete successfully. No new PPP session shall be established. The mobile station shall not re-register with the HA. The mobile stations IP address shall remain the same. 5.5 Simple IP Inter-PDSN Idle Handoff 5.5.1 Definition This test verifies the mobile station can be successfully transitioned from the dormant state to the active state in order for an Inter-PDSN idle handoff to occur. The result of the handoff to a new PDSN is a complete restart of PPP. PDSN 1 is associated with PCF 1 and PDSN 2 is associated with PCF 2. 5.5.2 Traceability 7.3 7.2 PDSN to PDSN Handoff [2] PCF to PCF handoff [2]
1 2 3 4
6 7 8 9 10
11 12 13
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
5.5.3 Method of Measurement a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs (i.e. PZID1 and PZID2, respectively). b. Set up a mobile station originated Service Option 33 call and wait for successful Simple IP establishment to complete. c. Instruct the mobile station to transition to the dormant state. d. Perform an idle handoff to PCF 2. e. Verify the mobile station transitions to the active state by originating a Service Option 33 call. f. Verify PCF 2 selects PDSN 2.
g. Verify PCF 2 triggers a new R-P session setup. h. Verify PDSN 2 re-negotiates the PPP session. i. j. Verify PDSN 2 assigns a new address to the mobile station. Allow the mobile station to return to the dormant state.
k. Perform an idle handoff back to PCF 1. l. Verify the mobile station originates a Service Option 33 call.
m. Verify PDSN 1 forces a re-negotiation of the PPP session. n. Verify PDSN 1 assigns a topologically correct IP address to the mobile station.
5-5
TIA-918 5.5.4 Minimum Standard The mobile station shall transition to the active state from the dormant state when a new R-P session is set up. The Inter-PDSN handoff shall result in a new PPP session on PDSN 2. A dormant handoff return to PDSN 1 also results in a restart of PPP. 5.6 Simple IP Intra-PDSN Handoff, Mobile Station in Dormant State 5.6.1 Definition This test verifies the successful Simple IP handoff between PCFs on the same PDSN while the mobile station is in the dormant state. The Intra-PDSN handoff will result in a continuation of the same PPP session and no mobile IP registration with the HA. 5.6.2 Traceability 7.3 7.2 PDSN to PDSN Handoff [2] PCF to PCF handoff [2]
1 2 3 4
6 7 8 9
10 11 12
13 14 15 16 17 18 19 20 21 22 23 24 25 26
5.6.3 Method of Measurement a. Verify that PCF 1 and PCF 2 have different, non-zero PZIDs (i.e. PZID1 and PZID2, respectively). b. Set up a mobile station originated Service Option 33 call and wait for successful SIP Registration. Verify the PDSN receives the CANID information from PCF 1. c. Allow the mobile station to go dormant. d. Perform an idle handoff to PCF 2. e. Verify the mobile station originates a Service Option 33 call and includes the PZID value equal to PZID1. f. Verify PCF 2 selects the same PDSN.
g. Verify PCF 2 triggers a new R-P session and forwards the CANID with PZID equal to PZID2 and the PANID with PZID equal to PZID1. h. Verify the PDSN does not re-negotiate the PPP session. i. Verify the mobile station is able to send and receive IP datagrams.
27 28 29
5.6.4 Minimum Standard The Simple IP Intra-PDSN handoff shall complete successfully. No new PPP session shall be established. The mobile station IP address shall remain the same.
30
5-6
TIA-918
6 AUTHENTICATION AND IPSEC SECURITY ASSOCIATION SUPPORT 6.1 RADIUS Support, Successful Scenario 6.1.1 Definition This test verifies that the PDSN acts as a RADIUS client to the Local RADIUS server. The PDSN shall send an Access-Request to the Local RADIUS Server. Upon successful authentication, the local RADIUS Server will send an Access-Accept to the PDSN via the local RADIUS server. 6.1.2 Traceability 6.2.3 3.4 3.7.2 Annex C RADIUS Support [2] Registration Reply [1] Receiving Registration Requests [1] RADIUS Attributes [2]
3 4 5 6 7
8 9 10 11 12
13
MS
PPP
PDSN
Local RADIUS
HA
Home RADIUS
Agent Advertisement MIP RRQ Access-Request Access-Accept MIP RRQ MIP RRP MIP RRP Accounting-Start
14 15 16 17 18 19 20
6.1.4 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after the PPP session is established. c. Verify the mobile station sends a valid Mobile IP RRQ to the PDSN/FA. d. Verify the PDSN/FA creates an Access-Request with at least the parameters shown in the following table:
6-1
TIA-918
Parameter
User-Name CHAP-Password CHAP-Challenge NAS-IP-Address Home Agent Address Correlation ID

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
e. Verify the Access-Request is sent to the Local RADIUS. f. Verify the Local RADIUS forwards the Access-Request to the Home RADIUS.
g. Verify authentication at the Home RADIUS is successful. h. Verify the Home RADIUS sends an Access-Accept to the PDSN/FA via the local RADIUS. i. j. Verify upon receipt of the Access-Accept, the PDSN/FA sends the Mobile IP RRQ to the HA. Verify the HA sends a Mobile IP RRP to the PDSN/FA.
k. Verify the PDSN/FA sends an Accounting-Start to the local RADIUS and sends the Mobile IP RRP to the mobile station. l. Transfer data to and from the mobile station and verify the data path.
m. Verify the HA correctly forwards incoming traffic to the mobile station. n. End the call from the mobile station. o. Verify the PDSN/FA sends an Accounting-Stop to the local RADIUS. 6.1.5 Minimum Standard The PDSN/FA shall create an Access-Request upon receipt of a Mobile IP Registration Request. The Home RADIUS shall create an Access-Accept upon successful authentication. After the Access-Accept is received, the PDSN/FA shall forward the Mobile IP RRQ to the HA. The HA shall send a Mobile IP RRP to the mobile station.
6.2 RADIUS Support, Unsuccessful Scenario
16 17 18 19 20
21
22 23 24 25
6.2.1 Definition This test verifies the Home RADIUS will fail authentication and send an Access-Reject to the local RADIUS if the NAI or AAA secret key is invalid. The PDSN/FA will send a Mobile IP RRP with an error code of 67 indicating that the Mobile IP RRQ was rejected.
6-2
TIA-918 6.2.2 Traceability 6.2.3 3.4 3.7.2 RADIUS Support [2] Registration Reply [1] Receiving Registration Requests [1]
1 2 3 4
5 6 7 8 9 10
6.2.3 Method of Measurement a. Configure the mobile station with an invalid NAI value. b. Set up a mobile station originated Service Option 33 call. c. Verify the mobile station sends a Registration Request to the PDSN/FA. d. Verify the PDSN/FA creates an Access-Request with at least the parameters shown in the following table:
Parameter
User-Name CHAP-Password CHAP-Challenge NAS-IP-Address Home Agent Address Correlation ID
11 12 13 14 15 16 17 18 19 20 21 22
e. Verify the Access-Request is sent to the Local RADIUS. f. Verify the Local RADIUS forwards the Access-Request to the Home RADIUS.
g. Verify authentication at the Home RADIUS fails. h. Verify the Home RADIUS sends an Access-Reject to the PDSN/FA via the local RADIUS. i. Verify the PDSN/FA sends a Mobile IP RRP with the code field set to 67 indicating the Mobile IP RRQ was rejected because the mobile station failed authentication. Verify the PDSN/FA does not send an Accounting-Start to the local RADIUS.
j.
k. Configure the mobile station with a valid NAI value and an incorrect secret key for the MN-AAA authentication. l. Repeat steps b through j.
23 24 25
6.2.4 Minimum Standard The Home RADIUS shall fail authentication and send an Access-Reject to the PDSN/FA. The PDSN/FA shall send a Mobile IP RRP with the code field set to 67 to the mobile station
6-3
TIA-918 indicating the registration was denied because authentication failed. The PDSN/FA shall not delete the security association with the HA because the mobile station is denied access.
6.3 IPSec Security Support, Preserving of Existing Security Association
1 2
4 5 6
6.3.1 Definition This test verifies that an existing IPSec security association between the PDSN/FA and HA is not compromised by the mobile station-authorized level of security. 6.3.2 Traceability 6.2.4 6.2.2.5 6.3.2 IP Security Support [2] Reverse Tunneling [2] IP Security Support [2]
7 8 9 10
11 12 13 14 15 16 17 18 19 20 21
6.3.3 Method of Measurement a. Configure the PDSN/FA and HA to have an existing IPSec security association. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends an Access-Request. d. Verify the home RADIUS server does not authorize security for the mobile station. e. Verify the home RADIUS server sends an Access-Accept and the Security Level set to the value 4 (i.e. No IPSec). f. Verify the PDSN/FA does not delete the security association with the HA as a result of the home RADIUS server not authorizing security for the mobile station.
22 23
6.3.4 Minimum Standard The PDSN/FA and the HA shall not invalidate a pre-existing security association.
6.4 Authentication Failure, MN-HA Authenticator is Invalid
24
25 26 27
6.4.1 Definition This test verifies that the mobile station will fail authentication if the authenticator in the MN-HA Extension is invalid. The HA shall set the Code field in the Mobile IP RRP to 131. 6.4.2 Traceability 3.8.2.1 Validity Checks [1]
28 29
30 31 32
6.4.3 Method of Measurement a. Configure the mobile station with an invalid MN-HA shared secret. b. Set up a mobile station originated Service Option 33 call.
6-4
TIA-918 c. Upon establishment of the PPP session, verify the PDSN/FA sends Agent Advertisements to the mobile station. d. Verify the mobile station sends a Mobile IP RRQ with the invalid authenticator in the MN-HA Extension. e. Verify the Home Agent rejects the registration in the Mobile IP RRP with the code field set to 131. f. Verify the PDSN/FA sends the Mobile IP RRP to the mobile station.
1 2 3 4 5 6 7
8 9 10
6.4.4 Minimum Standard The HA shall reject the Mobile IP RRQ when the authenticator in the MN-HA Extension is incorrect.
6.5 Foreign Agent Reverse Tunnel Registration Behavior
11
12 13 14
6.5.1 Definition This test verifies successful and unsuccessful enabling of the reverse tunnel based on the PDSN/FA and mobile station interaction. 6.5.2 Traceability 6.2.2.5 4.1 4.2 4.3 Reverse Tunnel [2] Mobile Node Considerations [3] Foreign Agent Considerations [3] Home Agent Considerations [3]
15 16 17 18 19
20 21
6.5.3 Method of Measurement a. Configure mobile station, PDSN/FA and HA as shown below:
Mobile Requests Reverse Tunnel FA Allows Reverse Tunnel Reverse Tunneling to HA required as indicated by home RADIUS
Yes (T-Bit = 1)
Yes
Yes
22 23 24 25 26 27 28
b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends Agent Advertisements to mobile station after the PPP session is established. d. Verify the mobile station sends a Mobile IP RRQ to the PDSN/FA. e. Verify the PDSN/FA forwards the Mobile IP RRQ to the HA. f. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted).
6-5
TIA-918 g. Transfer data to/from the mobile station and verify the data path. h. Verify the HA correctly de-capsulates and forwards traffic from the mobile station using the reverse tunnel. i. j. End the call from the mobile station. Repeat steps b through d making the following configuration changes:
1 2 3 4 5
No (T-Bit = 0)
6 7 8 9 10 11
Yes
No
k. Verify the PDSN/FA forwards the Mobile IP RRQ to the HA. l. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted).
m. End the call from the mobile station. n. Repeat steps a through d making the following configuration changes:
No (T-Bit = 0)
12 13 14 15 16
Yes
Yes
o. Verify the FA rejects the RRQ with code 75 "Reverse Tunnel Mandatory, T-Bit Not Set." p. If the PPP session is still up, verify the mobile station re-sends a Mobile IP RRQ to the PDSN/FA. q. Repeat steps a through d making the following configuration changes:
Yes (T-Bit = 1)
No
No
17 18 19
r.
Verify the FA rejects the RRQ with code 74, "Requested Tunnel Unavailable".
s. If the PPP session is still up, verify the mobile station re-sends a Mobile IP RRQ to the PDSN/FA.
6-6
TIA-918 t. Repeat steps a through d making the following configuration changes:

Yes (T-Bit = 1)
Yes
No
2 3 4 5
u. Verify the FA rejects the RRQ with code 74, "Requested Reverse Tunnel Unavailable." v. If the PPP session is still up, verify the mobile station re-sends a Mobile IP RRQ to the PDSN/FA. 6.5.4 Minimum Standard The PDSN/FA shall reject the Mobile IP Registration Request when the tunnel is unavailable or if the mobile station does not enable the T-Bit when required. Otherwise the Mobile IP RRQ shall be accepted.
6.6 Private Network Support, Successful Scenario
6 7 8 9
10
11 12
6.6.1 Definition This test verifies mobile station and PDSN/FA support private home addresses. 6.6.2 Traceability 6.2.2.4 6.5.2.4 Private Network Access [2] Private Network Support [2]
13 14 15
16 17 18 19 20 21 22 23 24 25 26 27 28
6.6.3 Method of Measurement a. Configure the mobile station, PDSN/FA, and HA to support reverse tunneling. b. Configure the mobile station with a private home address. c. Set up a mobile station initiated Service Option 33 call. d. Verify the PDSN/FA sends an Agent Advertisement after the PPP session has been established. e. Verify the mobile station sends a valid Mobile IP RRQ with T-Bit set to 1 and the Home Address set to w.x.y.z. f. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted).
g. Transfer data to/from the mobile station and verify the data path. h. Verify the HA correctly de-capsulates reverse tunneled traffic from the mobile station.
6-7
TIA-918 6.6.4 Minimum Standard The PDSN/FA shall support private home address. The mobile station shall enable the T-bit when requesting private network support.
6.7 Private Network Support, Unsuccessful Scenario
1 2 3
5 6 7
6.7.1 Definition This test verifies if the mobile station requests a private home address but does not set the T-Bit to 1 in the Mobile IP RRQ, the registration is rejected. 6.7.2 Traceability 6.2.2.4 6.5.2.3 Private Network Access [2] Private Network Support [2]
8 9 10
11 12 13 14 15 16 17 18 19 20 21
6.7.3 Method of Measurement a. Configure the PDSN/FA, and HA to support reverse tunneling. b. Configure the mobile station to not support reverse tunneling. c. Configure the mobile station with a private home address. d. Set up a mobile station initiated Service Option 33 call. e. Verify the PDSN/FA sends an Agent Advertisement after the PPP session has been established. f. Verify the mobile station sends a valid Mobile IP RRQ with T-Bit set to 0 and the Home Address set to w.x.y.z.
g. Verify the PDSN/FA sends a Mobile IP RRP with the code field set to 75, "Reverse Tunnel is Mandatory and T bit is not set." 6.7.4 Minimum Standard The PDSN/FA shall reject the Mobile IP RRQ when the mobile station requests a private home address but does not set the T bit to 1.
6.8 Successful Authentication using the MN-AAA Extension
22 23 24
25
26 27 28 29 30 31
6.8.1 Definition If the HA supports processing the MN-AAA extension this test verifies the HA can process the MN-AAA Authentication Extension of the Mobile IP RRQ. The HA will authenticate the registration by sending a RADIUS Access-Request to the Home RADIUS Server. This test case does not replace the fact that the PDSN/FA will be the first to perform MN-AAA validation with the home RADIUS server. 6.8.2 Traceability 6.3.4 Authentication [2]
32 33
6-8
TIA-918 6.8.3 Method of Measurement a. Configure the HA to require processing of the MN-AAA Authentication Extension. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends Agent Advertisements to mobile station after the PPP session is established. d. Verify the mobile station sends a valid Mobile IP RRQ to the PDSN/FA. e. Verify the PDSN/FA forwards the Mobile IP RRQ to the HA. f. Verify the HA creates a RADIUS Access-Request to the Home RADIUS server with the following: User-Name CHAP-Password CHAP-Challenge
1 2 3 4 5 6 7 8 9 10
11 12 13
g. Verify the Home RADIUS server sends a RADIUS Access-Accept to the HA. h. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). 6.8.4 Minimum Standard The HA shall send a RADIUS Access-Request to the Home RADIUS server when the HA is configured to process the MN-AAA authentication extension. The Home RADIUS server shall send a RADIUS Access-Accept upon successful authentication. The HA shall send a Mobile IP RRP to the mobile station indicating the registration is successful.
14 15 16 17 18 19
6-9
TIA-918
No text.
6-10
TIA-918
1 2 3 4 5
7 NETWORK SPECIFIC TESTS
These network specific tests verify the elements of a Mobile IP infrastructure are compliant with [2]. The term mobile station used in this section refers to a mobile station or mobile station simulator that is capable of performing non-standard or optional behavior in order to test PDSN/FA and HA functionality.
7.1 Mobile IP Registration Request with Invalid Extensions
7 8 9 10
7.1.1 Definition This test verifies that if the Mobile IP RRQ contains unrecognized and unsupported extensions between 128 and 255, the invalid extensions are discarded, but the rest of the Mobile IP RRQ is processed. 7.1.2 Traceability 1.9 Message Format and Protocol Extensibility [1]
11 12
13 14 15 16 17 18
7.1.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Instruct the mobile station to send a Mobile IP RRQ with a valid, unrecognized extension between 128 and 255. c. Verify the PDSN/FA discards the extension between 128 and 255 but processes the rest of the message and the Mobile IP RRQ is accepted. 7.1.4 Minimum Standard The PDSN/FA shall process the Mobile IP RRQ with a valid extension but discard an unrecognized extension between 128 and 255.
7.2 Foreign Agent Busy
19 20 21
22
23 24 25
7.2.1 Definition This test verifies the PDSN/FA will send an Agent Advertisement with the B bit set to 1 to indicate that it is not accepting registrations from additional mobile stations. 7.2.2 Traceability 2.1.1 6.2.2.1 Mobility Agent Advertisement Extension [1] Agent Advertisements [2]
26 27 28
29 30 31
7.2.3 Method of Measurement a. Configure the PDSN/FA to not accept any additional registrations. b. Set up a mobile station originated Service Option 33 call.
7-1
TIA-918 c. Verify the PDSN/FA sends an Agent Advertisement with the B bit set to 1 in the Mobility Agent Advertisement Extension. 7.2.4 Minimum Standard The PDSN/FA shall send an Agent Advertisement to the mobile station with the B bit set to 1 when it is not accepting additional resources.
7.3 Mobile IP Registration Request Rejected, Invalid Home Address
1 2
3 4 5
7 8 9 10
7.3.1 Definition This test verifies the HA rejects a Mobile IP RRQ from a mobile station using static home address assignment with an invalid home address. The HA IP address is provisioned correctly. 7.3.2 Traceability 3.8 Home Agent Considerations [1]
11 12
13 14 15 16 17 18 19 20
7.3.3 Method of Measurement a. Configure the mobile station to use an invalid home address (i.e. home IP address should be a.b.c.d but is provisioned as w.x.y.z.). b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after the PPP session is established. d. Verify the mobile station sends a Mobile IP RRQ with the invalid home address. e. Verify the HA rejects the Mobile IP RRQ and sends Code 129. 7.3.4 Minimum Standard The HA shall reject the Mobile IP RRQ with Code 129 when the home address in the Mobile IP RRQ is invalid.
7.4 Registration Rejected by FA, Poorly Formed Request
21 22 23
24
25 26 27 28
7.4.1 Definition This test verifies the PDSN/FA will reject a Mobile IP RRQ that does not contain the MN-HA Authentication Extension. The PDSN/FA shall send a Mobile IP RRP to the mobile station with an error code of 70 to indicate the Mobile IP RRQ was poorly formed. 7.4.2 Traceability 3.3 3.4 6.5.2 Registration Request [1] Registration Reply [1] Mobile IP Registration [2] Mobile IP Registration [2]
29 30 31 32 33
6.2.2.3
7-2
TIA-918 7.4.3 Method of Measurement a. Configure the mobile station to not include the MN-HA Authentication Extension in the Mobile IP RRQ. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after the PPP session is established. d. Verify the mobile station sends a Mobile IP RRQ to the PDSN/FA without the MN-HA Authentication Extension. e. Verify the PDSN/FA sends a Mobile IP RRP to the mobile station with an error code of 70 to indicate the RRQ was poorly formed. 7.4.4 Minimum Standard The PDSN/FA shall reject a Mobile IP RRQ that does not include the MN-HA Extension with an error code of 70.
7.5 Registration Rejected by Home Agent, Administratively Prohibited
1 2 3 4 5 6 7 8 9 10
11 12 13
14
15 16
7.5.1 Definition This test verifies the HA can reject the Mobile IP RRQ for administrative reasons. 7.5.2 Traceability 3.4 3.6.2 3.7.2.3 Registration Reply [1] Receiving Registration Replies [1] Denying Invalid Requests [1]
17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33
7.5.3 Method of Measurement a. Configure the HA to prohibit registrations from the mobile station. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA sends an Agent Advertisement to the mobile station after the PPP session is established. d. Verify the mobile station sends a valid Mobile IP RRQ to the PDSN/FA. e. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. f. Verify the HA rejects the registration.
g. Verify the PDSN/FA sends the Mobile IP RRP with the Code field set to 129, "Administratively Prohibited" and the Registration Lifetime set to 0. h. Verify the PDSN/FA sends the Mobile IP RRP to the mobile station with the code field set to 129. If the PDSN/FA does not close the PPP session, the mobile station may re-send a Mobile IP RRQ to the PDSN/FA.
7-3
TIA-918 7.5.4 Minimum Standard The HA shall reject the Mobile IP RRQ for administrative reasons when necessary. The PDSN/FA shall send the mobile station a Mobile IP RRP with the Code field set to 129.
7.6 Agent Advertisements not sent to Mobile Station using Simple IP
1 2 3
5 6 7
7.6.1 Definition This test verifies the PDSN/FA will not send Agent Advertisements to a mobile station configured to use Simple IP. 7.6.2 Traceability 6.2.2.1 Agent Advertisements [2]
8 9
10 11 12 13 14 15 16 17 18
7.6.3 Method of Measurement a. Configure the mobile station to use Simple IP. b. Set up a mobile station originated Service Option 33 call. c. Verify the mobile station sends an IPCP Configuration with the IP-Address set to 0.0.0.0. d. Verify the PDSN assigns an IP address to the mobile station. e. Verify the mobile station accepts the IP address assigned by the PDSN. f. Verify the PPP session is established.
g. Verify the PDSN does not send an Agent Advertisement to the mobile station. 7.6.4 Minimum Standard The PDSN/FA shall not send an Agent Advertisement to the mobile station using Simple IP after the PPP session is established.
7.7 Mobile IP Registration Expires
19 20 21
22
23 24 25
7.7.1 Definition This test verifies the PDSN/FA closes the PPP session if there is no successful reregistration before the registration lifetime expires. 7.7.2 Traceability 4.2.3 6.1.2 6.5.1.2 6.2.2 6.5.2 Home Agent Considerations [1] PPP Session [2] Termination [2] Mobile IP Registration [2] Mobile IP Registration [2]
26 27 28 29 30 31
7-4
TIA-918 7.7.3 Method of Measurement a. Configure the mobile station to not re-register before the registration lifetime expires. b. Verify the PPP inactivity timer is greater than the maximum allowable value for the Mobile IP registration lifetime. c. Set up a mobile station originated Service Option 33 call. d. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to mobile station after the PPP session is established. e. Verify the mobile station responds to the Agent Advertisement and sends a valid Mobile IP RRQ. f. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
g. Verify the PDSN/FA correctly acquires the mobile station home address received in the Mobile IP RRP from the HA. h. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). i. j. Allow the registration lifetime timer to expire in the PDSN/FA and HA. Verify the PDSN/FA closes the PPP session if no other IP bindings exist for the mobile station.
k. Verify the HA releases all resources associated with the mobile station. 7.7.4 Minimum Standard The PDSN/FA shall close the PPP session when no successful re-registration occurs before the registration lifetime expires. The HA shall release all resources associated with the mobile station.
7.8 Mobile IP Registration Request Lifetime Exceeds Agent Advertisement Lifetime
20 21 22 23
24
25 26 27
7.8.1 Definition This test verifies that if the Mobile IP RRQ lifetime exceeds the lifetime in the Agent Advertisement, the RRQ is denied and the Code field is set to 69. 7.8.2 Traceability 3.4 3.6.2 3.7.2.3 Registration Reply [1] Receiving Registration Replies [1] Denying Invalid Requests [1]
28 29 30 31
32 33
7.8.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call.
7-5
TIA-918 b. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to mobile station after the PPP session is established. c. Instruct the mobile station to send a Mobile IP RRQ with a requested lifetime greater than that received in the Agent Advertisement message. d. Verify the PDSN/FA sends a Mobile IP RRP indicating that the RRQ was denied with the code field set to 69, Requested Lifetime Too Long. e. Verify the PDSN/FA does not clear the PPP session. f. The mobile station should attempt to register with this same agent using a Lifetime in the Mobile IP RRQ that is less than or equal to the value in the Mobile IP RRP.
1 2 3 4 5 6 7 8 9 10
11 12 13
7.8.4 Minimum Standard The PDSN/FA shall reject a Mobile IP RRQ with a lifetime that exceeds the allowed value of the PDSN/FA. The PDNS/FA shall not clear the PPP session.
7.9 Multiple Home Addresses
14
15 16 17 18 19 20 21
7.9.1 Definition If the mobile station supports multiple home addresses over a single PPP session, this test verifies the PDSN/FA and mobile station are capable of supporting multiple home addresses using a single PPP session. This test also verifies the HA is capable of supporting multiple registrations with the same NAI using different static addresses. The PDSN/FA shall support multiple home addresses and the mobile station may support multiple home addresses over a single PPP session. 7.9.2 Traceability 6.2.1 PPP session [2] 6.5.1 PPP session [2] 7.9.3 Method of Measurement a. Configure the mobile station to support multiple addresses over a single PPP session. b. Configure the mobile station with two home addresses (a.b.c.d and w.x.y.z) and a single NAI. c. Set up a mobile station originated Service Option 33 call. d. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to mobile station after the PPP session is established. e. Verify the mobile station responds to the Agent Advertisement and sends a valid Mobile IP RRQ with the home address set to a.b.c.d. f. Verify the PDSN/FA sends the Mobile IP RRQ to the HA.
22 23 24
25 26 27 28 29 30 31 32 33 34 35
7-6
TIA-918 g. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). h. Instruct the mobile station to send another Mobile IP RRQ with the home address set to w.x.y.z. i. j. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted).
1 2 3 4 5 6 7 8 9 10 11
k. Verify the mobile station is registered with two home addresses using the same NAI over a single PPP session. l. Verify the mobile station can send and receive IP datagrams using either the a.b.c.d or w.x.y.z address.
12 13 14 15
7.9.4 Minimum Standard The PDSN/FA shall support multiple home addresses. The HA shall support multiple registrations for the same NAI using different static addresses. The mobile station may support multiple home addresses over a single PPP session.
7.10 Mobile Station Assigned Same Home Address By Two Home Agents
16
17 18 19 20
7.10.1 Definition This test verifies that while the mobile station is using private network access for multiple sessions, two HAs on separate private networks cannot assign the same address to the mobile station. 7.10.2 Traceability 6.2.2.4 6.5.2.4 Private Network Support [2] Private Network Support [2]
21 22 23
24 25 26 27 28 29 30 31 32 33 34 35
7.10.3 Method of Measurement a. Configure the mobile station, PDSN/FA, HA1 and HA2 to support reverse tunneling. b. Configure the mobile station with two HA IP addresses. c. Configure the mobile station to request dynamic home address assignment. d. Set up a mobile station initiated Service Option 33 call. e. Verify the PDSN/FA sends an Agent Advertisement after the PPP session has been established. f. Verify the mobile station sends a valid Mobile IP RRQ to HA1 with T-Bit set to 1 and the Home Address set to 0.0.0.0.
g. Verify HA1 sends a successful Mobile IP RRP assigning the mobile station an IP address via the PDSN/FA.
7-7
TIA-918 h. Transfer data to/from the mobile station and verify the data path. i. j. Verify the HA correctly de-capsulates and forwards traffic from the mobile station using the reverse tunnel. Instruct the mobile station to send a valid Mobile IP RRQ to HA2 with T-Bit set to 1 and the Home Address set to 0.0.0.0.
1 2 3 4 5 6 7 8 9
k. Instruct HA2 to use the same IP address HA1 assigned to the mobile station. l. Verify the PDSN/FA sends a Mobile IP RRP to the mobile station with an error code of 65.
m. Verify the first assigned address is not affected. 7.10.4 Minimum Standard The PDSN/FA shall send an error code of 65 if two home agents attempt to assign a mobile station the same IP address.
7.11 Ingress Address Filtering
10 11 12
13
14 15 16 17
7.11.1 Definition This test verifies the PDSN/FA will filter on the source address for packets originating from the mobile station to ensure the mobile station is using address(es) assigned by the HA and for which the registration has not expired. 7.11.2 Traceability 6.2.5 Ingress Address Filtering [2] 7.11.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Verify the PDSN/FA begins sending the configured number of Agent Advertisements to mobile station after the PPP session is established. c. Verify the mobile station responds to the Agent Advertisement and sends a valid Mobile IP RRQ. d. Verify the PDSN/FA sends the Mobile IP RRQ to the HA. e. Verify the PDSN/FA forwards the Mobile IP RRP received from the HA to the mobile station with the Code field set to 0 (Registration Accepted). f. Instruct the mobile station to send data (not a MIP RRQ or Agent Solicitation) using a source address not assigned by the HA.
18 19
20 21 22 23 24 25 26 27 28 29 30 31 32
g. Verify the PDSN/FA discards the packet. h. Verify the PDSN/FA sends an LCP Configure-Request to restart the PPP session.
7-8
TIA-918 7.11.4 Minimum Standard The PDSN/FA shall perform filtering on the source address for packets originating from the mobile station. The PDSN/FA shall restart the PPP session if the mobile station uses an address not assigned by the HA.
7.12 IPsec Security Support, Statically Configured IKE Pre-Shared Secret
1 2 3 4
6 7 8
7.12.1 Definition This test verifies that the PDSN/FA and HA negotiate IKE using a statically configured IKE pre-shared secret. 7.12.2 Traceability 6.2.3 6.2.2.5 6.3.2 IP Security Support [2] Reverse Tunneling [2] IP Security Support [2]
9 10 11 12
13

MS PDSN Local RADIUS HA Home RADIUS
PPP
Agent Advertisement MIP RRQ Access-Request Access-Accept IKE Negotiation Access-Request Access-Accept MIP RRP
MIP RRQ Accounting-Start
MIP RRQ
14 15 16 17 18 19 20 21 22 23
7.12.4 Method of Measurement a. Configure the PDSN/FA and HA to support IPsec and IKE using a statically configured secret key. b. Configure the HA with no previously assigned 'S' key. c. Set up a mobile station originated Service Option 33 call. d. After the mobile station receives an Agent Advertisement Message, instruct the mobile station to send a Mobile IP RRQ. e. Verify the PDSN/FA sends an Access-Request with the IKE Pre-Shared Secret Request set to 2 (PDSN/FA does not require a Pre-Shared Secret from the Home RADIUS).
7-9
TIA-918 f. Verify the home RADIUS server sends an Access-Accept.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
g. Verify the PDSN/FA and HA begin to negotiate IKE. h. Verify the HA sends an Access-Request to the Home RADIUS server requesting a new 'S' key. i. j. Verify the Home RADIUS server sends an 'S' key and associated lifetime to the HA. Verify the IKE negotiation is successful.
k. Verify the Mobile IP RRQ is accepted by the HA. l. Transfer data to/from the mobile station and verify the data is being transferred through the tunnel.
m. Verify the HA and PDSN/FA enforce the security policy as indicated in the 3GPP2 Security Level Attribute between the HA and PDSN/FA. n. Verify the PDSN/FA applies the required level of security to the reverse tunnel as indicated in the 3GPP2 Security Level Attribute. o. Verify the HA applies the required level of security to the forward tunnel as indicated in the 3GPP2 Security Level Attribute. 7.12.5 Minimum Standard The PDSN/FA and HA shall use IPsec when supported and authorized by the home RADIUS server. The HA shall request an 'S' key when an 'S' key has not been previously assigned. The PDSN/FA and HA shall enforce the level of security as specified by the Home RADIUS server.
7.13 IP Security Support, Dynamically Configured IKE Pre-Shared Secret
17 18 19 20 21
22
23 24 25
7.13.1 Definition This test verifies that the PDSN/FA and FA negotiate IKE using a dynamically configured IKE pre-shared secret. 7.13.2 Traceability 6.2.3 6.2.2.5 6.3.2 IP Security Support [2] Reverse Tunneling [2] IP Security Support [2]
26 27 28 29
30 31 32 33 34
7.13.3 Method of Measurement a. Configure the PDSN/FA and HA to support IPsec and IKE using a dynamically configured secret key. b. Verify the HA has a previously assigned 'S' key that has expired. c. Set up a mobile station originated Service Option 33 call.
7-10
TIA-918 d. After the mobile station receives an Agent Advertisement Message, instruct the mobile station to send a Mobile IP RRQ. e. Verify the PDSN/FA sends an Access-Request with the IKE Pre-Shared Secret Request set to 1 (Pre-shared secret is requested from the Home RADIUS.). f. Verify the home RADIUS server sends an Access-Accept with the reverse tunnel enabled and includes the pre-shared IKE secret and key identifier.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
g. Verify the HA maintains the expired 'S' for the configured amount of time. h. Verify the PDSN/FA and HA begin to negotiate IKE. i. j. Verify the HA sends an Access-Request to the Home RADIUS server requesting a new 'S' key. Verify the Home RADIUS server sends an 'S' key and associated lifetime to the HA.
k. Verify the IKE negotiation is successful. The security association attribute shall specify transport mode per [2]. l. Verify the Mobile IP RRQ is accepted by the HA.
m. Transfer data to/from the mobile station and verify the data is being transferred through the tunnel. n. Verify the HA and PDSN/FA enforce the security policy as indicated in the 3GPP2 Security Level Attribute between the HA and PDSN/FA. o. Verify the HA applies the required level of security to the forward tunnel as indicated in the 3GPP2 Security Level Attribute. p. Verify the PDSN/FA applies the required level of security to the reverse tunnel as indicated in the 3GPP2 Security Level Attribute. 7.13.4 Minimum Standard The PDSN/FA and HA shall use IPsec when supported and the Home RADIUS authorizes IPSec. The PDSN/FA shall request a dynamically configured pre-shared IKE secret when a static pre-shared IKE secret does not exist. The HA shall request an 'S' key after the current 'S' key expires. The PDSN/FA and HA shall enforce the level of security as specified by the Home RADIUS server.
7.14 Security Association using Public X.509 Certificates
24 25 26 27 28 29
30
31 32 33
7.14.1 Definition This test verifies the PDSN/FA and HA can establish a security association using HA X.509 certificates. 7.14.2 Traceability 6.2.3 6.2.2.5 IP Security Support [2] Reverse Tunneling [2]
34 35 36
7-11
TIA-918 6.3.2 IP Security Support [2]
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
7.14.3 Method of Measurement a. Configure the PDSN/FA and HA to support IPsec and IKE using the HA X.509 certificates. The certificates shall conform to Annex B of [2]. b. Set up a mobile station originated Service Option 33 call. c. After the mobile station receives an Agent Advertisement Message, instruct the mobile station to send a Mobile IP RRQ with the T-bit enabled. d. Verify the PDSN/FA and HA begin to negotiate IKE using the HA X.509 certificates. e. Verify the IKE negotiation is successful. f. Verify the Mobile IP RRQ is accepted by the HA.
g. Transfer data to/from the mobile station and verify the data is being transferred through the tunnel. h. Verify the HA and PDSN/FA enforce the security policy as indicated in the 3GPP2 Security Level Attribute between the HA and PDSN/FA. i. j. Verify the HA applies the required level of security to the forward tunnel as indicated in the 3GPP2 Security Level Attribute. Verify the PDSN/FA applies the required level of security to the reverse tunnel as indicated in the 3GPP2 Security Level Attribute.
20
7.14.4 Minimum Standard The PDSN/FA and HA shall use HA X.509 certificates to establish a security association when no previous security association exists.
21
7.15 Security Association using the Root X.509 Certificates
22 23 24
7.15.1 Definition This test verifies the PDSN/FA and HA can establish a security association using the root X.509 certificate when the HA X.509 certificates do not exist. 7.15.2 Traceability 6.2.3 6.2.2.5 6.3.2 IP Security Support [2] Reverse Tunneling [2] IP Security Support [2]
25 26 27 28
29 30 31 32
7.15.3 Method of Measurement a. Configure the PDSN/FA and HA to support IPsec and IKE using the root X.509 certificates. The certificates shall conform to Annex B of [2]. b. Set up a mobile station originated Service Option 33 call.
7-12
TIA-918 c. After the mobile station receives an Agent Advertisement Message, instruct the mobile station to send a Mobile IP RRQ with the T-bit enabled. d. Verify the PDSN/FA and HA begin to negotiate IKE using the root X.509 certificates received in Phase 1 IKE. e. Verify the IKE negotiation is successful. f. Verify the Mobile IP RRQ is accepted by the HA.
1 2 3 4 5 6 7 8 9 10 11 12
g. Transfer data to/from the mobile station and verify the data is being transferred through the tunnel. h. Verify the HA and PDSN/FA enforce the security policy as indicated in the 3GPP2 Security Level Attribute between the HA and PDSN/FA. i. Verify the PDSN/FA applies the required level of security to the reverse tunnel as indicated in the 3GPP2 Security Level Attribute.
13
7.15.4 Minimum Standard The PDSN/FA and HA shall use the root X.509 certificates to establish a security association when no previous security association exists and no HA X.509 certificates exist.
14
7.16 Unsuccessful IPsec Security Association Establishment
15 16 17 18
7.16.1 Definition This test verifies the PDSN/FA does not send the Mobile IP RRQ to the HA if the security association cannot be established with the HA. The PDSN/FA shall send a Mobile IP RRP to the mobile station indicating the registration failed. 7.16.2 Traceability 6.2.3 6.2.2.5 6.3.2 IP Security Support [2] Reverse Tunneling [2] IP Security Support [2]
19 20 21 22
23 24 25 26 27 28 29 30 31 32 33
7.16.3 Method of Measurement a. Configure the PDSN/FA and HA to support IPsec and IKE using a dynamically configured secret key. b. Configure the Home RADIUS server to not return a pre-shared IKE secret key. c. Set up a mobile station originated Service Option 33 call. d. After the mobile station receives an Agent Advertisement Message, instruct the mobile station to send a Mobile IP RRQ with the T-bit enabled. e. Verify the PDSN/FA sends an Access-Request with the IKE Pre-Shared Secret Request set to 1 (Pre-shared secret is requested from the Home RADIUS.). f. Verify the home RADIUS server sends an Access-Accept with the reverse tunnel enabled and does not include the pre-shared IKE secret and key identifier.
7-13
TIA-918 g. Verify the PDSN/FA does not forward the Mobile IP RRQ to the HA. h. Verify the PDSN/FA rejects the registration attempt with an error code of 65,administratively prohibited, in the Mobile IP RRP. 7.16.4 Minimum Standard The PDSN/FA shall reject the Mobile IP RRQ with an error code of 65 if the Home RADIUS server does not return a pre-shared key and the PDSN is mandated to use IPsec. The PDSN/FA shall not forward the Mobile IP RRQ to the HA if the security association is not established.
5
1 2 3
7.17 PDSN Clears PPP State, R-P Session Closed
6 7 8
7.17.1 Definition This test verifies that the PDSN/FA clears the PPP state for the mobile station if the R-P session is closed. 7.17.2 Traceability 6.1.2 6.5.1.2 6.2.1.3 6.2.1.4 6.2.2.2 PPP Session [2] Termination [2] Authentication [2] Addressing with IPCP [2] Addressing and Mobile IP [2]
9 10 11 12 13 14
15 16 17 18 19 20
7.17.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Once the PPP session has been established and a successful Mobile IP Registration occurs, close the R-P Session. c. Verify the PDSN/FA clears the PPP state once the R-P session for the mobile station is closed. 7.17.4 Minimum Standard The PDSN/FA shall clear the PPP state when there is no underlying R-P session for the mobile station.
21
22 23
7.18 PDSN Terminates Simple IP Session Due to PDSN PPP Inactivity Timer Expiration
24 25 26
7.18.1 Definition This test verifies the PDSN can successfully terminate the PPP session when its PPP inactivity timer expires.
7-14
TIA-918 7.18.2 Traceability 5.1.1 PPP Session [2]
1 2
3 4 5 6 7 8 9
7.18.3 Method of Measurement a. Set up a mobile station originated Service Option 33 call. b. Once the PPP session has been established, allow the mobile station to go dormant. c. Allow the PDSN PPP inactivity timer to expire. d. Verify the PPP session is closed at the PDSN. e. Verify the PDSN releases the R-P session to the RN. 7.18.4 Minimum Standard The PDSN shall terminate the PPP session when the PDSN PPP inactivity timer expires. The PDSN shall release the R-P session to the RN.
7.19 PDSN Terminates a Simple IP Session when the R-P Session is Closed
10 11 12
13
14 15 16
7.19.1 Definition This test verifies that the PDSN clears the PPP state with the mobile station if the R-P session is closed. 7.19.2 Traceability 5.1.2 5.2.1.2 PPP Session [2] Termination [2]
17 18 19
20 21 22 23 24 25 26 27
7.19.3 Method of Measurement a. Configure mobile station to use Simple IP service. b. Set up a mobile station originated Service Option 33 call. c. Once the PPP session has been established and a successful the Simple IP session has been established, close the R-P session. d. Verify the PDSN clears the PPP state once the R-P session for the mobile station is closed.
28
7.19.4 Minimum Standard The PDSN shall close the PPP session when there is no underlying R-P session for the mobile station.
7-15
TIA-918
1 2 3
8 ACCOUNTING
These accounting specific tests verify the elements of a Simple IP and Mobile IP infrastructure are compliant with [2].
8.1 Accounting Scenario without Containers and No Change in Multiplex Options, User Zone, or QoS
4 5
6 7 8
8.1.1 Definition This test verifies the accounting when containers are not used and no multiplex options, user zone or quality of service change during the entire data session. 8.1.2 Traceability 9.2 9.5 Airlink Records [2] PDSN Procedures [2]
9 10 11
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
8.1.3 Method of Measurement a. b. c. d. e. f. g. Configure the PDSN to not use containers and to send an interim record interval after one minute. Set up a mobile station originated Service Option 33 call and wait for successful MIP Registration. Verify the PDSN sends an Accounting Request Start to the AAA server. Configure the mobile station to both send and receive a known amount of data for 30 seconds. Instruct the mobile station to go into the dormant state for one minute. Verify the PDSN sends an Interim record to the local AAA. Verify there is no container in the record and that the record is correct. Configure the mobile station to go active and both send and receive a known amount of data for 30 seconds using the same multiplex options, same user zone, and same quality of service (priority). Instruct the mobile station to send an RRQ with a zero lifetime and terminate PPP. Verify the PDSN sends an Accounting Request Stop to the local AAA. Verify the RADIUS STOP record is correct.
h. i.
30
8.1.4 Minimum Standard The PDSN shall generate proper RADIUS records, including an Interim Record.
8-1
TIA-918
8.2 Accounting Scenario with Containers and a Change in Multiplex Options, User Zone, or QoS
1 2
3 4 5
8.2.1 Definition This test verifies the accounting when containers are used and when multiplex options, user zone, or quality of service change during the packet data session. 8.2.2 Traceability 9.2 9.5 Airlink Records [2] PDSN Procedures [2]
6 7 8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
8.2.3 Method of Measurement a. b. c. d. e. f. g. Configure the PDSN to use containers and to send an interim record interval after one minute. Set up a mobile station originated Service Option 33 call and wait for successful MIP Registration. Verify the PDSN sends an Accounting Request Start to the AAA server. Configure the mobile station to both send and receive a known amount of data for 30 seconds. Instruct the mobile station to go into the dormant state for one minute. Verify the PDSN sends an Interim record to the local AAA. Verify container is correct in RADIUS record. Configure the mobile station to go active and both send and receive a known amount of data for 30 seconds using different multiplex options or different user zone or different quality of service (priority). Instruct the mobile station to send and RRQ with a zero lifetime and terminate PPP. Verify the PDSN sends an Accounting Request Stop to the local AAA. Verify there are two containers in RADIUS STOP record and both are correct.
h. i.
27 28 29
8.2.4 Minimum Standard The PDSN shall generate proper RADIUS records with two containers. The PDSN shall generate an Interim Record.
8.3 Accounting Scenario without Containers and a Change in Multiplex Options, User Zone, or QoS
30 31
32 33
8.3.1 Definition This test verifies the accounting when containers are not used.
8-2
TIA-918 8.3.2 Traceability 9.2 9.5 Airlink Records [2] PDSN Procedures [2]
1 2 3
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
8.3.3 Method of Measurement a. b. c. d. e. f. g. Configure the PDSN to not use containers and to send an interim record interval after one minute. Set up a mobile station originated Service Option 33 call and wait for successful MIP Registration. Verify the PDSN sends an Accounting Request Start to the AAA server Configure the mobile station to both send and receive a known amount of data for 30 seconds. Instruct the mobile station to go into the dormant state for one minute. Verify the PDSN sends an Interim record to the local AAA. Verify the start record is correct in RADIUS record. Configure the mobile station to go active and both send and receive a known amount of data for 30 seconds using different multiplex options or different user zone or different quality of service (priority). Verify the PDSN sends a RADIUS Accounting Request Stop with the Session Continue attribute set to true. Verify the Stop does not contain a container. Verify the PDSN sends a RADIUS Accounting Request Start. Instruct the mobile to send and RRQ with zero lifetime and terminate PPP. Verify the PDSN sends an Accounting Request Stop to the local AAA. Verify the Stop record is correct and that it does not contain a container.
h. i. j. k.
24 25 26
8.3.4 Minimum Standard The PDSN shall generate proper RADIUS records with no containers, as outlined above. The PDSN shall generate an Interim Record.
8.4 Multiple Home Agent Test with Accounting
27
28 29 30
8.4.1 Definition This test verifies the proper operation of Mobile IP including accounting when there is more than one Home Agent. 8.4.2 Traceability 9.2 9.5 Airlink Records [2] PDSN Procedures [2]
31 32 33
8-3
TIA-918 8.4.3 Method of Measurement a. b. c. d. e. f. Configure the PDSN to not use containers and to send an interim record after one minute. Configure the mobile station and two Home Agents with static home addresses such that the home addresses are not identical. Set up a mobile station originated Service Option 33 call and wait for successful MIP Registration on Home Agent 1. Establish a MIP registration on Home Agent 2 with the second home address. Verify the PDSN sends two Accounting Request Starts to the AAA server, one for each home address. Configure the mobile station to both send and receive a known amount of data for 30 seconds for each home address to one or more correspondent nodes. Allow the mobile station to go into the dormant state. Verify the PDSN sends two Interim record to the local AAA. Verify the interim records correct. Instruct the mobile to go active and send and receive data using both of its home addresses for 30 seconds. Instruct the mobile to send and RRQ with zero lifetime for each home address, and then to terminate PPP. Verify the PDSN sends two Accounting Request Stop to the local AAA, one for each home address. Verify Stop are correct in RADIUS record.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
g. h. i. j. k.
24 25 26
8.4.4 Minimum Standard The PDSN shall generate proper RADIUS records with containers. The PDSN shall generate two Interim Records.
8.5 Single Home Agent and Simple IP Test with Accounting
27
28 29 30
8.5.1 Definition This test verifies the proper operation of Mobile IP including accounting when there is one Home Agent and the mobile uses Simple IP as well. 8.5.2 Traceability 9.2 9.5 Airlink Records [2] PDSN Procedures [2]
31 32 33
8-4
TIA-918 8.5.3 Method of Measurement a. b. c. d. e. f. g. h. i. Configure the PDSN to use containers and to send an interim record after one minute. Configure the mobile station and Home Agent with a static home address. Set up a mobile station originated Service Option 33 call and have the mobile establish Simple IP. Verify the PDSN sends an Accounting Request Start. Instruct the mobile station to send an Agent Solicitation. Verify the PDSN sends an Agent Advertisement. Configure the mobile station to establish a Mobile IP session upon receipt of the Advertisement; wait for successful MIP Registration on Home Agent. Verify the PDSN sends an Accounting Request Start to the AAA server for the home address. Configure the mobile station to both send and receive a known amount of data for 30 seconds with home address and the Simple IP address with other nodes. Instruct the mobile station to go into the dormant state for a minute. Verify the PDSN sends two Interim records to the local AAA. Verify the Records are correct. Instruct the mobile station to send an RRQ with zero lifetime, and then to terminate PPP. Verify the PDSN sends two Accounting Request Stop to the local AAA. Verify the records are correct.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
j. k. l. m.
24 25 26
8.5.4 Minimum Standard The PDSN shall generate proper RADIUS records. The PDSN shall generate an Interim Records.
8.6 HDLC Byte Accounting Test with Simple IP
27
28 29 30
8.6.1 Definition This test verifies the PDSN/FA counts all HDLC bytes received including excessive numbers of inter-frame fill flags. 8.6.2 Traceability 9.2 9.5 Airlink Records [2] PDSN Procedures [2]
31 32 33
8-5
TIA-918 8.6.3 Method of Measurement a. b. c. d. e. f. g. h. Set up a mobile station originated Service Option 33 Simple IP call. Verify the PPP session is established successfully between the mobile station and the PDSN. Verify the mobile station sends an IPCP Configure-Request to the PDSN/FA that includes an IP-Address Configuration Option with address of 0.0.0.0. Verify the PDSN/FA assigns an IP address to the mobile station. Verify the PDSN sends an Account-Request Start. Once the PPP session has been established, instruct the mobile to send inter-frame fill flags for one minute. Instruct the mobile station to send an LCP-terminate. Verify the PDSN/FA sends an Accounting Request-Stop and that the G14 attribute reflects a minutes worth of flags plus other data.
1 2 3 4 5 6 7 8 9 10 11 12 13
14 15 16
8.6.4 Minimum Standard The PDSN/FA shall terminate the PPP session when the inactivity timer expires. The PDSN/FA shall release the R-P session to the RN.
8.7 Simple IP Test with Accounting and CHAP
17
18 19 20
8.7.1 Definition This test verifies the proper operation of Simple IP with CHAP authentication and accounting. 8.7.2 Traceability 5.2.1.3 5.4.1.3 9.2 9.5 Authentication [2] Authentication [2] Airlink Records [2] PDSN Procedures [2]
21 22 23 24 25
26 27 28 29 30 31 32 33
8.7.3 Method of Measurement a. Configure the PDSN to not use containers. Configure the mobile station to use CHAP and configure the RADIUS server and mobile station with a shared secret. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA proposes CHAP in the LCP Configure-Request. d. Verify the mobile station sends an LCP Configure-Ack to the PDSN/FA. e. Verify the PDSN sends a CHAP Challenge to the mobile station. f. Verify the mobile station sends a CHAP Response to the PDSN.
8-6
TIA-918 g. Verify the PDSN sends an Access-Request to the RADIUS server. h. Verify the RADIUS server sends an Access-Accept to the PDSN. i. j. Verify the PDSN sends a CHAP Success to the mobile station. Verify the mobile station sends an IPCP Configure-Request to the PDSN/FA that includes the IP-Address Configuration Option with address 0.0.0.0.
1 2 3 4 5 6 7 8 9 10 11 12
k. Verify the PDSN/FA assigns an IP address to the mobile station. l. Verify the PDSN sends an Accounting Request Start.
m. Configure the mobile station to both send and receive a known amount of data for 30 seconds Simple IP address. n. Instruct the mobile station to terminate PPP. o. Verify the PDSN sends an Accounting Request Stop to the local AAA. Verify the record is correct. 8.7.4 Minimum Standard The PDSN shall authenticate the mobile station and generate proper RADIUS Start and Stop records.
8.8 Simple IP Test with Accounting and PAP
13 14 15
16
17 18 19
8.8.1 Definition If the mobile station supports using PAP perform this test. This test verifies the proper operation of Simple IP with PAP authentication and accounting. 8.8.2 Traceability 5.2.1.3 5.4.1.3 9.2 9.5 Authentication [2] Authentication [2] Airlink Records [2] PDSN Procedures [2]
20 21 22 23 24
25 26 27 28 29 30 31 32 33
8.8.3 Method of Measurement a. Configure the PDSN to not use containers. Configure the mobile station to use PAP and configure the RADIUS server and the mobile station with the same password. b. Set up a mobile station originated Service Option 33 call. c. Verify the PDSN/FA proposes CHAP in the LCP Configure-Request. d. Verify the mobile station sends an LCP Configure-Nack to the PDSN/FA proposing PAP. e. Verify the PDSN sends an LCP Configure-Request with PAP.
8-7
TIA-918 f. Verify the mobile station sends a PAP Auth-Response to the PDSN.
1 2 3 4 5 6 7 8 9 10
g. Verify the PDSN sends an Access-Request to the RADIUS server. h. Verify the RADIUS server sends an Access-Accept to the PDSN. i. j. Verify the PDSN sends a PAP Auth-Ack to the mobile station. Verify the mobile station sends an IPCP Configure-Request to the PDSN/FA that includes the IP-Address Configuration Option with address 0.0.0.0.
k. Verify the PDSN/FA assigns an IP address to the mobile station. l. Verify the PDSN sends an Accounting Request Start.
m. Instruct the mobile station to terminate PPP. n. Verify the PDSN sends an Accounting Request Stop. 8.8.4 Minimum Standard The PDSN shall authenticate the mobile station using PAP and generates proper RADIUS Start and Stop records.
11 12 13
8-8

Tia 918 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Tia 918 PDF

Загружено:

Авторское право:

Доступные форматы

TIA DOCUMENT

Signaling Conformance Standard for cdma2000 Wireless IP Networks

TELECOMMUNICATIONS INDUSTRY ASSOCIATION

The Telecommunications Industry Association represents the communications sector of

PLEASE! DON'T VIOLATE THE LAW!

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

HLR Home Access Provider Network

RADIUS Home IP Network

R-P Interface Mobile Station PDSN

RADIUS Broker Network

Visited Access Provider Network

Figure 1.3-1 Simple IP Network Architecture

HLR Home Access Provider Network

RADIUS Home IP Network

R-P Interface Mobile Station PDSN

RADIUS Broker Network

Visited Access Provider Network

HA Home IP Network, Private Network, Home Access Provider Network

Acronym UDP VLR

Expansion User Datagram Protocol Visitor Location Register

TIA-918 4.1.3 Call Flow Example

MS Service Option 33 Call

IPCP Configuration Ack

TIA-918 4.2.3 Call Flow Example

TIA-918 4.4.3 Call Flow Example

Agent Solicitation Agent Advertisement

5.1.3 Call Flow Example

PCF 2 R-P Session

New R-P Session

TIA-918 f. Verify PCF 2 selects the PDSN 2.

6.1.3 Call Flow Example

User-Name CHAP-Password CHAP-Challenge NAS-IP-Address Home Agent Address Correlation ID

User-Name CHAP-Password CHAP-Challenge NAS-IP-Address Home Agent Address Correlation ID

TIA-918 t. Repeat steps a through d making the following configuration changes:

7 NETWORK SPECIFIC TESTS

7.12.3 Call Flow Example

MIP RRQ Accounting-Start

TIA-918 f. Verify the home RADIUS server sends an Access-Accept.

TIA-918 6.3.2 IP Security Support [2]

7.15 Security Association using the Root X.509 Certificates

7.16 Unsuccessful IPsec Security Association Establishment

7.17 PDSN Clears PPP State, R-P Session Closed

TIA-918 7.18.2 Traceability 5.1.1 PPP Session [2]

Вам также может понравиться