TR 23.875
Support of Push service
V5.1.0 (Wzip)
2002/04 70 p.
- Rapporteur:
- Mr. Uda, Nobuyuki
NTT COMWARE Corporation
full Table of Contents for TR 23.875 Word version: 5.1.0
1 Scope p. 7
The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope.
2 References p. 7
3 Definitions, symbols and abbreviations p. 8
4 Introduction p. 9
5 Requirements p. 9
6 General Description p. 10
6.1 Service Environment and Scenario p. 10
6.2 Addressing p. 12
6.3 Dedicated Connection Establishment p. 13
6.4 Push Content Delivery p. 13
6.4.1 Reliable Delivery p. 13
6.4.1.1 Store and Forward p. 14
6.4.1.2 Presence Service p. 14
6.5 Multiple Services p. 16
6.6 Security and Charging p. 17
6.7 User Terminal p. 17
6.8 Roaming Support p. 17
7 Architecture for GPRS p. 18
7.1 Introduction p. 18
7.2 Network requested PDP Context activation with User-ID p. 18
7.2.1 Functional Architecture for Push Services p. 18
7.2.1.1 Application Server (AS) p. 19
7.2.1.2 Address Resolver (AR) p. 19
7.2.1.3 Proxy AS (Proxy Application Server) p. 19
7.2.1.4 Notification Agent (NA) p. 20
7.2.1.5 User Equipments (UE) p. 20
7.2.1.6 GPRS network p. 20
7.2.2 PDP Context Activation with User-ID p. 20
7.2.2.1 Information Flow Example 1 : Dedicated Connection Approach p. 20
7.2.2.2 Information Flow Example 2: Connectionless Approach p. 22
7.2.2.3 Selection of GGSNs in network requested PDP context activation process p. 22
7.2.2.4 Roaming Support p. 23
7.2.2.5 How to protect HLR from signalling overload p. 23
7.2.3 PDP Context Deactivation requested by the UE p. 23
7.2.4 PDP Context Deactivation requested by GPRS network p. 23
7.2.5 Sharing User activated PDP context with Push Services p. 25
7.2.6 Presence Service p. 25
7.2.7 Proposed Protocol Architecture p. 27
7.2.7.1 Notification Protocol p. 27
7.2.7.2 Update Protocol p. 29
7.2.8 Impact to 3G specification p. 29
7.3 PDP context activation triggered by DNS query p. 30
7.3.1 Definitions p. 30
7.3.2 Assumptions p. 30
7.3.3 Requirements p. 30
7.3.4 General Description p. 31
7.3.5 Proposed behaviours for DNS queries p. 31
7.3.6 Proposed behaviours for IP data delivery p. 33
7.3.7 Example Scenario p. 33
7.3.8 Alternative PDNS Implementation p. 34
7.3.9 Alternative GGSN Implementation p. 34
7.3.10 GGSN with embedded PDNS p. 36
7.3.11 Avoiding an Application Server Timeout p. 36
7.3.12 Protocol Architecture p. 37
7.3.13 Security p. 37
7.3.14 Roaming Support p. 37
7.3.15 Error Responses p. 37
7.3.16 Impact to 3G specification p. 37
7.4 SMS Push Service p. 38
7.4.1 Assumptions p. 38
7.4.2 Basic Service Scenarios p. 38
7.4.2.1 Short Message Push p. 38
7.4.2.2 Push Notification with User Connect Scenario p. 39
7.4.2.3 Push Broadcast Scenario p. 39
7.4.3 Addressing p. 40
7.4.4 Subscription, Security, and Charging p. 40
7.4.5 Roaming p. 40
7.4.6 Delivery Reliability p. 40
7.4.7 Protocol Architecture p. 41
7.5 Push solution with dynamic address using always on and SMS p. 42
7.5.1 Architecture p. 42
7.5.2 Push proxy p. 43
7.5.3 PUSH initiator p. 43
7.5.4 Push services subscription p. 43
7.5.5 Addressing: Push service using dynamic address p. 44
7.5.6 Presence description p. 44
7.5.7 Delivery of the push message p. 45
7.5.8 Reliability of the delivery of the push message p. 46
7.5.9 Store and forward function: p. 47
7.5.10 Multiple services p. 47
7.5.11 Security p. 47
7.5.11a Charging p. 48
7.5.12 User terminal p. 48
7.5.13 Roaming Support p. 48
7.5.14 IP address management p. 49
7.6 SIP based Push Service p. 49
7.6.1 IM Subsystem Scenario p. 50
7.6.2 No IM Subsystem Scenario p. 50
7.6.3 Roaming p. 51
7.6.4 Protocol Architecture p. 52
7.6.5 Addressing p. 53
7.6.5.1 SIP Identity p. 53
7.6.5.2 IP Address p. 53
7.6.6 Subscription, Security, and Charging p. 54
7.6.7 Delivery Reliability p. 54
7.6.8 Connectionless Push p. 54
7.6.9 Quality of Service p. 54
7.7 Push Proxy Based Architecture Using HTTP as Delivery Protocol p. 54
7.7.1 Architecture p. 54
7.7.2 Push Proxy p. 55
7.7.3 Addressing p. 56
7.7.4 Push Delivery Mechanism p. 56
7.7.5 UE Capability Profile p. 57
7.7.6 Roaming Considerations p. 57
7.7.7 Delivery Reliability p. 57
7.7.8 Protocol Architecture p. 58
7.7.9 Security Considerations p. 58
8 Conclusion and Recommendations p. 58
A Comparison of the Push Techniques comparison p. 60
B A study on how NRCA and "always on" fulfil PUSH service requirements p. 61
B.1 Introduction p. 61
B.2 Description of the procedures: p. 61
B.2.1 NRCA p. 61
B.2.2 Always on p. 62
B.3 Scalability, or supporting burst of push messages during busy hour. p. 63
B.4 Delays p. 63
B.5 network resources are used as efficiently as possible; p. 64
B.6 Minimum investment p. 65
B.7 Minimum operating cost p. 66
B.8 interoperability and Service availability when roaming p. 66
B.9 Charging p. 67
B.10 Type of IP addresses used p. 67
B.10.1 NRCA with static addresses p. 67
B.10.2 NRCA with dynamic address and MSISDN addressing p. 67
B.10.3 Always-on: p. 67
B.10.4 Conclusion p. 67
B.11 FINAL Conclusion p. 68
C Comparison of NRCA and SMS as a push solution p. 68
C.1 Introduction p. 68
C.2 MM signalling required p. 68
C.3 Signalling during push delivery p. 68
C.4 Conclusion p. 70
$ Change history p. 70
