Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.813
Word version: 11.0.0
1…
4…
4
Key issues
$
Change history
4
Key issues
4.1
Key Issue 1: Policy enhancement for sponsored data connectivity
4.1.1
Introduction
4.1.2
Alternative solutions
Word‑p. 8
4.1.2.1
Alternative 1
4.1.2.1.1
Reference points enhancements
Word‑p. 9
4.1.2.1.2
Call flows
Word‑p. 10
4.2
Key issue 2: Coherent access to Policy related databases
Word‑p. 12
4.2.1
Description
4.2.2
Alternative solutions
4.2.2.1
SPR as an Application Front-End of the UDC Architecture
4.2.2.2
PCRF as an Application Front-End of the UDC Architecture
Word‑p. 13
4.2.3
Comparison of alternatives
Word‑p. 14
4.2.4
Conclusion
4.3
Key issue 3: QoS and gating control based on spending limits
Word‑p. 15
4.3.1
Description
4.3.1.1
Common Principles
4.3.2
Alternative solutions
4.3.2.1
Alternative solution 1 - configuration based solution
4.3.2.2
New reference point (Sy) between PCRF and OCS
Word‑p. 17
4.3.2.2.1
General
4.3.2.2.2
PCRF contacting the OCS (PCRF-Centric approach)
Word‑p. 18
4.3.2.2.2.5
Signalling flows
Word‑p. 19
4.3.2.2.3
OCS contacting the PCRF (OCS-Centric approach)
Word‑p. 23
4.3.2.3
Alternative solution 3 - enhancing Gy and Gx
4.3.3
Conclusion
4.4
Key issue 4: Service Awareness and Privacy Policies
Word‑p. 24
4.4.1
Description
4.4.2
Actions resulting from service detection
4.4.3
Alternative solutions
4.4.3.1
Alternative 1
4.4.3.1.1
Reference Points
Word‑p. 25
4.4.3.1.2
Functional entities
4.4.3.2
Solicited service detection reporting
Word‑p. 26
4.4.3.2.1
Specific functions description
1.4.3.2.2
Signalling Flows
Word‑p. 27
4.4.3.3
Unsolicited service detection reporting
Word‑p. 33
4.4.3.3.1
Signalling Flows
4.4.3.4
Service Detection and Policy rules definition and structure
Word‑p. 34
4.4.3.4.1
General
Word‑p. 35
4.4.3.4.2
Service Detection and Policy rule relevant operations
Word‑p. 36
4.4.3.4.3
PCC rules modifications
4.4.4
Conclusion
4.5
Key issue 5: Service Based Traffic Steering
4.5.1
Description
4.5.2
Conclusion
Word‑p. 37
4.6
Key issue 6: Extending Policy Architecture to handle transactional services
4.6.1
Description
4.6.2
Alternative solutions
4.6.2.1
Alternative 1 - Use Rx to authorize transactional services
4.6.2.1.1
General
4.6.2.1.2
Architecture
4.6.2.1.3
Reference points
Word‑p. 38
4.6.2.1.4
PCC Information Flows
4.6.3
Comparison of alternatives
Word‑p. 40
4.6.4
Conclusion
$
Change history
Word‑p. 41