B.11 Summary
23.3353GPPRelease 17Stage 2Technical realization and information flowsTSUser Data Convergence (UDC)
Any network entity that performs application logic (in sessions which are limited in duration) and that stores user data (during the time where no session is running) is in principle applicable to the UDC concept. However some nodes may not fully benefit from the UDC concept, especially if
– permanent user data stored at the node – in a non UDC network – is not provisioned at that node
– parallel sessions for the same user at the same time cannot run independently
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2010-03 |
CP#47 |
CP-100051 |
Approved in CT#47 |
9.0.0 |
|||
|
2010-06 |
CP#48 |
CP-100282 |
0001 |
1 |
Removal of normative behaviour of the HLR-FE during MAP Update Location flow |
9.1.0 |
|
|
0002 |
1 |
Removal of security editor’s note |
|||||
|
0005 |
FE data view |
||||||
|
2010-09 |
CP#48 |
CP-100459 |
0004 |
3 |
UDC Reference Architecture |
9.2.0 |
|
|
2010-12 |
CP#50 |
CP-100680 |
0006 |
Provisioning FE correction |
9.3.0 |
||
|
0007 |
1 |
Notifications triggered by a FE to its cluster |
|||||
|
0008 |
1 |
Provisioning from self care systems |
|||||
|
2011-03 |
CP#51 |
CP-110074 |
0013 |
2 |
Notifications and transactions |
10.0.0 |
|
|
2012-03 |
CP#57 |
CP-120469 |
0014 |
1 |
Adding note on Data Model for User Data Convergence architecture |
11.0.0 |
|
|
2014-09 |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
12.0.0 |
|
|
2015-12 |
CT#70 |
– |
– |
– |
Update to Rel-13 version (MCC) |
13.0.0 |
|
|
2016-03 |
CT#71 |
CP-160031 |
0015 |
3 |
MCPTT Application FEs |
13.1.0 |
|
|
2017-03 |
CT#75 |
CP-170045 |
0018 |
1 |
MC services application FEs |
14.0.0 |
|
|
2018-06 |
CT#80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
|
2020-07 |
CT#88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-03 |
CT#95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |