Content for TR 29.817 Word version: 12.1.0
2 References
3 Definitions and abbreviations
4 Study area
5 The Rx interface
6 Architecture of the 3rd party web service based on Rx
7 Rx protocols for 3rd party web application developers
8 Charging
9 Security
10 Roaming and routing
11 Conclusion and recommendation
A Example - XML schema (example 1)
B Consideration on charging extension
C The procedures of protocol converter by using two TCP connections
$ Change History
2 References p. 7
3 Definitions and abbreviations p. 8
3.1 Definitions p. 8
3.2 Abbreviations p. 8
4 Study area p. 8
4.1 Architecture and deployment p. 8
4.2 Functions p. 9
4.3 Protocols and languages p. 9
4.4 Charging p. 10
4.5 Roaming and routing p. 10
4.6 Security p. 10
4.7 New consideration for XML based Rx interface p. 10
5 The Rx interface p. 10
6 Architecture of the 3rd party web service based on Rx p. 11
6.1 General p. 11
6.2 Protocol converter p. 11
6.2.1 Architecture description p. 11
6.2.2 Procedures of protocol converter p. 13
6.2.2.1 AF Session Establishment p. 13
6.2.2.2 AF Session Modification initiated by AF p. 13
6.2.2.3 Gate Related Procedures p. 14
6.2.2.4 AF Session Termination p. 14
6.2.2.5 Subscription to Notification of Signalling Path Status p. 14
6.2.2.6 Notification of traffic plane events p. 15
6.2.3 Roaming and routing of protocol converter p. 16
6.2.3.1 PC located in the PLMN but outside of the PCRF realm p. 16
6.2.3.1.1 General p. 16
6.2.3.1.2 Routing between the AF and Protocol converter p. 16
6.2.3.1.3 Routing between the Protocol converter and PCRF p. 16
6.2.3.2 PC located in the PCRF realm p. 17
6.2.4 Study on location of XML-DIAMETER Protocol Converter p. 17
6.3 PCRF web server p. 20
6.3.1 Procedures of PCRF web server p. 20
6.3.1.1 AF Session Establishment p. 20
6.3.1.2 AF Session Modification p. 21
6.3.1.3 AF Session Termination p. 21
6.3.1.4 Gate Related Procedures p. 22
6.3.1.5 Subscription to notification of traffic plane events p. 22
6.3.1.6 Notification of traffic plane events p. 22
6.3.2 PCRF addressing p. 23
6.3.2.1 Non-roaming cases p. 23
6.3.2.1.1 Solution1: DRA-like entity interacting with DRA to get the PCRF address based on Diameter protocol p. 23
6.3.2.1.2 Solution 2: DRA-like entity interacting with DRA to get the PCRF address based on XML based protocol p. 25
6.3.2.1.3 Solution 3: DRA-like entity supporting DRA functionalities p. 26
6.3.2.2 Roaming cases p. 26
6.3.2.2.1 Solution1b: DRA-like entity interacting with DRA to get the PCRF address based on diameter protocol p. 27
6.3.2.2.2 Solution2b: DRA-like interacting with DRA to get the PCRF address based on XML based protocol p. 27
6.3.2.2.3 Solution3b: DRA-like entity supporting DRA functionalities p. 28
6.3.2.3 Evaluation p. 28
6.3.2.4 Conclusion p. 29
6.4 Evaluation p. 29
7 Rx protocols for 3rd party web application developers p. 29
7.1 Transport solutions for Rx messages p. 29
7.1.1 Transport protocols p. 29
7.1.1.1 RESTful HTTP p. 29
7.1.1.2 SOAP p. 30
7.1.2 HTTP and bidirectional communication p. 31
7.2 Application level protocols and data structures p. 31
7.3 Session management p. 33
7.3.1 General p. 33
7.3.2 HTTP streaming p. 33
7.3.3 HTTP long polling p. 34
7.3.4 Two TCP connections p. 35
7.3.5 Evaluation p. 35
7.3.6 Conclusion p. 35
7.4 Void
7.5 Evaluation p. 36
8 Charging p. 36
9 Security p. 37
10 Roaming and routing p. 37
11 Conclusion and recommendation p. 37
11.1 Impacts on the PCC architecture p. 37
11.2 Transport protocols and languages p. 38
11.3 Impacts on existing 3GPP specifications p. 38
11.4 Recommendation for an XML based access of AF to the PCRF p. 38
A Example - XML schema (example 1) p. 39
A.1 Example - XML schema (example 1) p. 39
A.1.1 Analysis of Diameter Data Types and XML Schema Data Types p. 39
A.1.2 "AVP Parameters" group p. 41
A.1.3 XML schema for Diameter AAR applying "AVP Parameters" group p. 42
A.1.3.1 Diameter Header p. 43
A.1.3.2 AVP Parameter Group p. 43
A.1.3.3 Session ID AVP p. 43
A.1.3.4 Auth-Application ID AVP p. 44
A.1.3.5 Origin Host AVP p. 44
A.1.3.6 Origin Realm AVP p. 44
A.1.3.7 Destination Realm AVP p. 44
A.1.3.8 Destination Host AVP p. 45
A.1.3.9 IP Domain ID AVP p. 45
A.1.3.10 AFAppIdentifier AVP p. 45
A.1.3.11 Media Component Description AVP p. 45
A.1.3.12 Service Info Status AVP p. 48
A.1.3.13 AF Charging Identifier AVP p. 48
A.1.3.14 SIP Forking Indication AVP p. 48
A.1.3.15 Specific Action AVP p. 48
A.1.3.16 Subscription ID AVP p. 49
A.1.3.17 Supported Features AVP p. 49
A.1.3.18 Reservation Priority AVP p. 50
A.1.3.19 Framed IP address AVP p. 51
A.1.3.20 Framed Ipv6 prefix AVP p. 51
A.1.3.21 Service URN AVP p. 51
A.1.3.22 Sponsored Connectivity Data AVP p. 51
A.1.3.23 MPS Identifier AVP p. 55
A.1.3.24 Rx-Request-Type AVP p. 55
A.1.3.25 Required- Access- Info AVP p. 56
A.1.3.26 Origin State ID AVP p. 56
A.1.3.27 Proxy Info AVP p. 56
A.1.3.28 Route Record AVP p. 57
B Consideration on charging extension p. 58
C The procedures of protocol converter by using two TCP connections p. 59
C.1 General p. 59
C.2 AF Session Establishment p. 59
C.3 AF Session Modification initiated by AF p. 59
C.4 AF Session Termination initiated by the AF p. 60
C.5 Notification of traffic plane events p. 60
C.6 AF Session Termination initiated by the PCRF p. 61
$ Change History p. 62
