Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 23.875
Support of Push service

3GPP‑Page   ToC  
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

Here   Top

1  ScopeWord‑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  ReferencesWord‑p. 7

3  Definitions, symbols and abbreviationsWord‑p. 8

3.1  DefinitionsWord‑p. 8

3.2  SymbolsWord‑p. 9

3.3  AbbreviationsWord‑p. 9

4  IntroductionWord‑p. 9

5  RequirementsWord‑p. 9

6  General DescriptionWord‑p. 10

7  Architecture for GPRSWord‑p. 18

7.1  IntroductionWord‑p. 18

7.2  Network requested PDP Context activation with User-IDWord‑p. 18

7.3  PDP context activation triggered by DNS queryWord‑p. 30

7.4  SMS Push ServiceWord‑p. 38

7.5  Push solution with dynamic address using always on and SMSWord‑p. 42

7.6  SIP based Push ServiceWord‑p. 49

7.7  Push Proxy Based Architecture Using HTTP as Delivery ProtocolWord‑p. 54

7.7.1  ArchitectureWord‑p. 54

7.7.2  Push ProxyWord‑p. 55

7.7.3  AddressingWord‑p. 56

7.7.4  Push Delivery MechanismWord‑p. 56

7.7.5  UE Capability ProfileWord‑p. 57

7.7.6  Roaming ConsiderationsWord‑p. 57

7.7.7  Delivery ReliabilityWord‑p. 57

7.7.8  Protocol ArchitectureWord‑p. 58

7.7.9  Security ConsiderationsWord‑p. 58

8  Conclusion and RecommendationsWord‑p. 58

A  Comparison of the Push Techniques comparisonWord‑p. 60

B  A study on how NRCA and "always on" fulfil PUSH service requirementsWord‑p. 61

B.1  IntroductionWord‑p. 61

B.2  Description of the procedures:Word‑p. 61

B.2.1  NRCAWord‑p. 61

B.2.2  Always onWord‑p. 62

B.3  Scalability, or supporting burst of push messages during busy hour.Word‑p. 63

B.3.1  NRCAWord‑p. 63

B.3.2  Always-onWord‑p. 63

B.3.3  ConclusionWord‑p. 63

B.4  DelaysWord‑p. 63

B.4.1  Always-on:Word‑p. 63

B.4.2  NRCA:Word‑p. 64

B.4.3  ConclusionWord‑p. 64

B.5  network resources are used as efficiently as possible;Word‑p. 64

B.5.1  Always-on:Word‑p. 64

B.5.2  NRCA:Word‑p. 64

B.5.3  ConclusionWord‑p. 65

B.6  Minimum investmentWord‑p. 65

B.6.1  Always-on:Word‑p. 65

B.6.2  NRCA:Word‑p. 65

B.6.3  ConclusionWord‑p. 65

B.7  Minimum operating costWord‑p. 66

B.7.1  Always-on:Word‑p. 66

B.7.2  NRCA:Word‑p. 66

B.7.3  ConclusionWord‑p. 66

B.8  interoperability and Service availability when roamingWord‑p. 66

B.8.1  Always-on:Word‑p. 66

B.8.2  NRCA:Word‑p. 66

B.8.3  ConclusionWord‑p. 66

B.9  ChargingWord‑p. 67

B.10  Type of IP addresses usedWord‑p. 67

B.11  FINAL ConclusionWord‑p. 68

C  Comparison of NRCA and SMS as a push solutionWord‑p. 68

C.1  IntroductionWord‑p. 68

C.2  MM signalling requiredWord‑p. 68

C.3  Signalling during push deliveryWord‑p. 68

C.4  ConclusionWord‑p. 70

$  Change historyWord‑p. 70


Up   Top