Network Initiated Data Session (NIDS)

Transcription

1 GPP S.R000-0 Version.0 Version Date: 0 June 00 0 Network Initiated Data Session (NIDS) 0 Stage Requirements COPYRIGHT NOTICE GPP and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner s name based on this document. Requests for reproduction of this document should be directed to the GPP Secretariat at secretariat@gpp.org. Requests to reproduce individual Organizational Partner s documents should be directed to that Organizational Partner. See for more information. 00 GPP

2 S.R000-0 v.0 EDITOR John Kay, Motorola REVISION HISTORY REVISION HISTORY Rev..0 Initial Publication 0 June GPP Page ii

3 S.R000-0 v.0 0 Table of Contents Network Initiated Data Session (NIDS)... i INTRODUCTION AND SCOPE... REFERENCES... DEFINITIONS AND ABBREVIATIONS.... Definitions.... Abbreviations... GENERAL FEATURE DESCRIPTION... DETAILED FUNCTIONALITY REQUIREMENTS.... General Requirements.... Mobile Station Addressing.... Routing and Session Establishment.... Subscription and User Profile.... Roaming.... Security... HIGH LEVEL SYSTEM DESIGN GPP Page iii

4 S.R000-0 v.0 List of Tables GPP Page iv

5 S.R000-0 v GPP Page v

6 S.R000-0 v.0 List of Figures GPP Page vi

7 S.R000-0 v INTRODUCTION AND SCOPE This document defines the requirements for providing the Network Initiated Data Session (NIDS) capability. Wireless data applications today assume initial action by the mobile station to establish a data session with the network, and therefore make the mobile station reachable for the network to forward IP packets. An alternative to this is to have the mobile station automatically establish a data session upon application of power, and maintain the session until power is turned off. This is commonly referred to as Always ON capability. There is a third possible approach, which may be applicable for devices, but which occasionally need to establish packet data communication sessions at times determined by the core network. There may be an array of such applications, including notification, certain location-based applications, maintenance actions such as PRL download, etc. The scope of these requirements apply to the case when a Packet Data capable mobile station is currently in packet data disconnected condition and a Correspondent Node wishes to establish a data session with the mobile station (i.e. push data to the mobile station). This capability may be used in conjunction with other services such as Immediate Messaging, Multi-Media Messaging, or any service that requires the pushing of data to the Mobile Station. The term Packet Data Disconnected Condition means that network resources are not yet assigned to allow IP packets to be sent to the MS. REFERENCES The applicable document references include: [] GPP X.S00, Wireless IP Network Standard DEFINITIONS AND ABBREVIATIONS. Definitions Packet data session See reference [] Push Correspondent Node Mobile Station Packet Data Disconnected Condition The act of sending unsolicited data to a mobile station at the initiative of a Correspondent Node In the context of this document, the CN is the iniator of IP packets being pushed to the MS. In the context of this document, the MS is the receiver of the IP packets being pushed by the CN The condition of packet data connection in which network resources are not yet assigned which would allow IP packets to be sent to the

8 S.R000-0 v.0 MS Wireless IP Network See reference []. Abbreviations BS FA HA HLR MS MSC NIDS PCF PDSN PPP VLR Base Station Foreign Agent Home Agent Home Location Register Mobile Station Mobile Switching Center Network Initiated Data Session Packet Control Function Packet Data Serving Node Point to Point Protocol Visited Location Register 0 0 GENERAL FEATURE DESCRIPTION In order for the network to push data to a mobile without NIDS capability, the network must currently maintain a dormant data session for a given mobile station when there is no data activity. This requires the maintenance of resources, including some of the following:. Memory Space: Maintaining a dormant session in PCF for the MS. This requires memory space in the PCF.. Signaling Traffic: For example, periodically renewing the R-P tunnel between the PCF and PDSN periodically adds unneeded signaling.. PDSN Resources: Maintaining the PPP state in the PDSN.. Air Interface Resources: These resources are usually associated with packet data mobility. For example the mobile must leave dormancy to notify the base station its location each time it moves into a new Packet Zone. If this results in an inter PDSN handoff, a new PPP and Mobile IP registration will be necessary. This requires the use of Traffic Channel resources.. IP Address Space: Maintaining an IP address for the mobile. If IPv is used, there is a practical limit of available addresses. The goal of the Network Initiated Data Session feature is to extend network capability to deliver IP packets to a mobile station for which some of the resources have been reclaimed, i.e., to optimize network resources. Without NIDS, in order to reach the mobile, there must be packet data connection between the network and the mobile, be it by means of Always ON, or by means of mobile initiated connectivity. NIDS would be most beneficial for mobiles that spend most of their time in the packet data dormant state. Probably the most critical amongst them is the air interface resource.

9 S.R000-0 v.0 In principle, the NIDS service presented in this document may be built upon a Wireless IP Network reference model as defined in reference []. To describe the requirements for the NIDS service, the reference model is simplified as shown in the following figure: MSC SS Network HLR Access Provider Network Home Access Provider network A RADIUS IP Network RADIUS Home IP network RADIUS Broker network P i Mobile Station RN R-P interface A0, A PDSN/FA CN Private network HA Home IP network, Private network, Home Access Provider network 0 Figure : Simplified Wireless IP Network Reference Model The NIDS service assumes that the Correspondent Node is capable of addressing and sending IP packets to an MS with an assigned IP address. DETAILED FUNCTIONALITY REQUIREMENTS A reference diagram for NIDS is shown in Figure.

10 IBM IBM d i g i t a l S.R000-0 v.0 HLR MSC Correspondent Node AAA TIA/EIA/IS- Network Home RAN PDSN IP Network Mobile Station MSC/VLR Visited RAN PDSN Home Agent Foreign Agent Figure : Network Reference Diagram 0 0. General Requirements NIDS-0. The Network Initiated Data Session capability shall be efficient in the use of network and Mobile Station resources. It shall be possible to reclaim some of the resources associated with a packet data session. NIDS-0. The Network Initiated Data Session capability shall be transparent to the originating Correspondent Node. NIDS-0. The Network Initiated Data Session capability shall be transparent to existing data services (Immediate Messaging, MMS, Presence, etc.) NIDS-0. The NIDS service shall support Simple IP and Mobile IP. NIDS-0. The network shall be able to initiate a data session with an MS that is registered with the packet data network.. Mobile Station Addressing NIDS-0. The Mobile Station shall have performed an air interface registration and be assigned an IP address in order to be able to receive NIDS data using either a static or dynamic IP address. NIDS-0. The Mobile Station that has performed an air interface registration with the network shall be reachable when in Packet Data Disconnected Condition (e.g. no PPP session exists).. Routing and Session Establishment NIDS-0. When the Wireless IP Network receives an IP packet from a Correspondent Node addressing an MS for which some of the resources have been reclaimed (e.g. R-P connection) it shall be possible for the Wireless IP network to re-establish the resources and deliver the packet to the MS. NIDS-0. The network shall provide information to allow a Mobile Station to filter the data being downloaded and accept or deny the NIDS data.

11 S.R000-0 v Subscription and User Profile NIDS-0. The network shall maintain in the Mobile Station User Profile the MS s subscription status for Network Initiated Data capability. NIDS-. The network may maintain the activation status of the NIDS service in the subscriber s Mobile Station User Profile.. Roaming NIDS-. The NIDS capability shall support subscriber roaming.. Security NIDS-. The Network Initiated Data Session capability shall use existing security mechanisms.. User Interaction, Activation and Deactivation. NIDS-. The MS User shall have the capability to reject a NIDS request received from the network. NIDS-. The subscription administrator shall have the capability to deactivate the NIDS service for a subscriber. NIDS-. The subscription administrator shall have the capability to activate the NIDS service for a subscriber. HIGH LEVEL SYSTEM DESIGN For future study.