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 32.850
Word version: 14.0.0
1…
2…
2
References
3
Definitions, symbols and abbreviations
4
Overview
5
Description of scenarios
6
Key Issues
7
Conclusions
$
Change History
2
References
3
Definitions, symbols and abbreviations
Word‑p. 8
3.1
Definitions
3.2
Symbols
3.3
Abbreviations
4
Overview
Word‑p. 9
4.1
General
4.2
Consideration of different Application Server (AS) types and roles
Word‑p. 10
4.3
Identifiers used for application differentiation
Word‑p. 11
4.3.1
IMS Communication Service Identifier (ICSI)
4.3.2
IMS Application Reference Identifier (IARI)
Word‑p. 12
4.4
Charging correlation
4.4.1
General
4.4.2
Charging data correlation
Word‑p. 13
4.4.3
SIP Identifier used for charging correlation
4.4.3.1
IMS Charging Identifier (ICID)
4.4.3.2
Related ICID
Word‑p. 14
4.4.3.3
Access network charging identifier
4.4.3.4
Inter Operator Identifier (IOI)
4.4.3.5
IMS visited network identifier
4.4.3.6
Loopback Indication
4.4.3.7
Session-ID
4.4.3.8
Outgoing Session-ID
4.4.4
SIP Identifier used for dialog correlation
Word‑p. 15
4.4.4.1
Original dialog identifier
4.5
Comparison of S-CSCF and AS CDR for correlation purposes
5
Description of scenarios
Word‑p. 20
5.1
Methodology
5.2
Scenario 1 MMTel
5.2.1
Description of scenario
5.2.2
Further considerations with the MMTEL when acting as B2BUA
Word‑p. 21
5.3
Scenario 2 TelCo enterprise service
Word‑p. 22
5.4
Scenario 3: Enhanced Multimedia Telephony (EMT)
Word‑p. 23
5.5
Scenario 4: Small Business Telephony (SBT)
Word‑p. 24
5.6
Scenario 5: Charging information from all IMS NEs including AS
Word‑p. 25
6
Key Issues
Word‑p. 26
6.1
Key Issue #1
6.1.1
General
6.1.2
Description
6.1.3
Assumptions
Word‑p. 27
6.1.4
Current status
6.1.5
Alternative options
6.1.5.1
Alternative 1 - SIP information which element writes a CR
6.1.5.2
Alternative 2 - Furnish Charging Information to CTF
6.1.5.3
Alternative 3 - Definition of a type of call
Word‑p. 28
6.1.5.4
Alternative 4 - Subscribe/Notify for CDR events
Word‑p. 29
6.1.6
Evaluation and recommendation
6.1.6.1
Evaluation
6.1.6.2
Recommendation
Word‑p. 31
6.2
Key Issue #2:
6.2.1
Description
6.2.2
Assumptions
6.2.3
Current status
6.2.4
Alternative options
Word‑p. 32
6.2.4.1
Alternative 1 - SIP Indication which Application is involved in Call
6.2.4.2
Alternative 2 - One CDR per AS
6.2.5
Evaluation
7
Conclusions
Word‑p. 33
$
Change History
Word‑p. 34