12 Shared Repository Data identification
29.3643GPPIP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperabilityRelease 17TS
12.1 General
This clause describes an optional solution to avoid potential large amount of update, and possible notification, operations in Sh when data is shared among multiple subscribers. Only Repository Data may be shared among multiple subscribers.
12.2 Description
Shared Repository Data among multiple subscribers may be supported in the HSS. Each shared Repository Data is uniquely identified by a distinct IMS Public Service Identity and a Service Indication.
This PSI is only used for accessing the shared Repository Data via Sh interface. This PSI shall not exist from an IMS management point of view and thus it shall not be allowed to be unregistered or to be used as an IMS user in any way. The PSI Activation State shall be set to Inactive.
The PSI(s) used to identify a shared Repository Data are contained in a specific Repository Data (identified by a dedicated Service Indication value "SHARED-REPOSITORY-DATA-IDENTIFICATION") stored for each subscriber to whom this shared Repository Data applies.
One or multiple shared Repository Data may be stored in the HSS, while a subscriber may reference one or several of them.
When an AS wants to read a shared Repository Data for a subscriber, the AS should retrieve first the PSI(s) contained in the Repository Data identified by the dedicated Service Indication value "SHARED-REPOSITORY-DATA-IDENTIFICATION" and the Public Identity of this subscriber. Then, the AS uses received PSI(s) to retrieve the shared Repository Data, using corresponding specific Service Indication.
The AS should store the shared Repository Data locally and it should subscribe to notifications on changes. If shared Repository Data is modified, the HSS notifies the AS about it with a single Sh notification.
See figure 12.2-1 for an example of shared Repository Data usage.
Figure 12.2-1: Shared Data example
If the same Repository Data is defined for a subscriber both as individual Repository Data and shared Repository Data, the individual one shall take precedence.
The same Repository Data shall not be defined as different shared Repository Data for the same subscriber.
12.3 Service Indication
The shared Repository Data identification shall be contained in the Service Data of the Repository Data with the Service Indication having the value "SHARED-REPOSITORY-DATA-IDENTIFICATION".
12.4 Information elements
12.4.1 Shared Repository Data reference
A shared Repository Data identification is a distinct IMS Public Service Identity, as described in 3GPP TS 23.003 [24].
12.5 XML schemas
12.5.1 Shared Repository Data identification
The XML schema below describes the structure and content of the shared Repository Data identification.
<?xml version="1.0" encoding="utf-8" ?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="sharedRepositoryDataIdentification" type="tSharedRepositoryDataIdentification" />
<xs:simpleType name="tSharedRepositoryDataIdentification" final="restriction list">
<xs:restriction base="xs:anyURI" />
</xs:simpleType>
</xs:schema>
Annex A (informative):
Dataset example with variable length data
This example illustrates the use of offset and length elements to point variable data in a dataset.
Four variables are defined, each with the following values:
Var1 = 012345678
Var2 empty
Var3 = ABCD
Var4= 124345678
The coding of the dataset is as follows:
Figure Annex A-1: Dataset example
|
Byte order |
||||||
|
0 |
Dataset header |
|||||
|
Other fixed format data |
||||||
|
Var1 |
||||||
|
Offset=60 |
Len=9 |
|||||
|
Var2 |
||||||
|
Offset=69 |
Len=0 |
|||||
|
Other fixed format data |
||||||
|
Var3 |
||||||
|
Offset=69 |
Len=4 |
|||||
|
Var4 |
||||||
|
Offset =73 |
Len=8 |
|||||
|
Other fixed format data |
||||||
|
60 |
0 |
1 |
2 |
3 |
||
|
64 |
4 |
5 |
6 |
7 |
||
|
68 |
8 |
A |
B |
C |
Variable |
|
|
72 |
D |
1 |
2 |
3 |
length |
|
|
76 |
4 |
5 |
6 |
7 |
data |
|
|
80 |
8 |
|||||
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2008-12 |
CT#42 |
CP-080720 |
V1.0.0 approved in CT#42 |
8.0.0 |
|||
|
2009-03 |
CT#43 |
CP-090027 |
0001 |
1 |
Network provider options for CDIV with binary option |
8.1.0 |
|
|
0002 |
1 |
Complement on NDUB parameter in the binary option |
|||||
|
0003 |
1 |
IMS CAT description with binary option |
|||||
|
0004 |
1 |
AOC parameters with binary option |
|||||
|
0005 |
2 |
Editor’s notes and Service names corrections |
|||||
|
0006 |
AOC Service with XML option |
||||||
|
0007 |
Service Indication for XML format |
||||||
|
0008 |
Addition of schema locations for XML files |
||||||
|
0009 |
Cleanup of XML files for operator common data |
||||||
|
0010 |
1 |
NDUB parameter in XML option |
|||||
|
0011 |
1 |
CUG not supported in XML option |
|||||
|
0012 |
2 |
CAT parameters in XML option |
|||||
|
0013 |
1 |
Reverse charging note in XML |
|||||
|
0014 |
1 |
CC parameters in XML option |
|||||
|
2009-06 |
CT#44 |
CP-090304 |
0016 |
1 |
Document references in AOC subclause |
8.2.0 |
|
|
0017 |
1 |
Editorial Changes |
|||||
|
2009-06 |
Styles and format errors corrected in tables caused by implementation in v.8.2.0, e.g. bullets removed. |
8.2.1 |
|||||
|
2009-09 |
CT#45 |
CP-090551 |
0018 |
1 |
Flexible Alerting with binary option |
8.3.0 |
|
|
0019 |
CAT User configuration |
||||||
|
0020 |
1 |
XML schema for Flexible Alerting |
|||||
|
2009-12 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
9.0.0 |
|
|
2011-03 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
10.0.0 |
|
|
2011-09 |
CT#53 |
CP-110556 |
0023 |
– |
OIP/OIR data syntax |
10.1.0 |
|
|
2012-09 |
CT#57 |
CP-120482 |
0027 |
– |
IMS user group over Sh |
11.0.0 |
|
|
2012-12 |
CT#58 |
CP-120715 |
0028 |
1 |
XML corrections |
11.1.0 |
|
|
CP-120876 |
0029 |
2 |
Transparent Data coding of IMS ODB info |
||||
|
2013-03 |
CT#59 |
CP-130012 |
0041 |
– |
XML document Version |
11.2.0 |
|
|
2013-03 |
CT#59 |
CP-130034 |
0030 |
2 |
IM-SSF Service Data Definition based on XML |
12.0.0 |
|
|
0031 |
2 |
XML Schema for IM-SSF |
|||||
|
2013-06 |
CT#60 |
CP-130302 |
0042 |
– |
Correction on XML Schema for IMS CAMEL Data |
12.1.0 |
|
|
2014-06 |
CT#64 |
CP-140240 |
0043 |
1 |
Correction on XML Schema for IMS CAMEL Services |
12.2.0 |
|
|
2015-03 |
CT#67 |
CP-150016 |
0048 |
– |
Removal of CDIVN service |
12.3.0 |
|
|
2015-06 |
CT#68 |
CP-150273 |
0050 |
1 |
Shared Repository Data reference |
13.0.0 |
|
|
2015-12 |
CT#70 |
CP-150750 |
0051 |
– |
Communication Barring wording correction |
13.1.0 |
|
|
2017-03 |
CT#75 |
– |
– |
– |
Update to Rel-14 version (MCC) |
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-04 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |