A.3 Contents of messages
24.0103GPPGeneral AspectsMobile radio interface layer 3Release 17Supplementary services specificationTS
The contents of messages is specified below the arrow. The diagrams do not show the SS version indicator, or other parts of the message contents unless they are directly related to the service shown. The names of relevant information elements are shown, and the associated contents is shown in brackets.
If the information element is the Facility IE then the contents information includes:
‑ the type of component that shall be used for the operation (e.g. invoke, return result, return error, reject);
‑ the name of the operation to be used (for the invoke and return result components only);
‑ the parameters that shall be included in the operation. For the function described by the diagram, only those parameters shown in the diagram are allowed. Unless stated otherwise all the parameters shown in the diagram shall be present when the operation is used for the function described by the diagram.
The detailed encoding of the operations and parameters shown in the diagrams is defined in 3GPP TS 24.080 [27] and 3GPP TS 29.002 [45]. Appropriate ASN.1 structures from these specifications shall be used to align with the diagrams.
The examples in figure A.2 illustrate the encoding. The first example shows a common information element operation where the operation name is shown. The second example shows a common information element operation where the operation name is not shown. Items in italics would be substituted with the appropriate identifiers.
MESSAGE NAME
————————————————————————————————————————————>
Facility (Component Type = OperationName (parameters))
MESSAGE NAME
————————————————————————————————————————————>
Facility (Component Type (parameters))
Figure A.2: Examples of the contents of messages
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
Apr 1999 |
Transferred to 3GPP CN1 |
||||||
|
CN#03 |
Approved at CN#03 |
3.0.0 |
|||||
|
CN#08 |
001 |
Alignment of SS protocol with current MM/GMM integrity protection rules |
3.1.0 |
||||
|
CN#11 |
Version increased from R99 to Rel-4 after CN#11 |
4.0.0 |
|||||
|
CN#11 |
002r1 |
Adaptation of SS to PS domain |
4.0.0 |
||||
|
CN#13 |
003 |
Clarification on the signalling connection for PS domain |
4.1.0 |
||||
|
CN#14 |
005 |
Usage of SS Version Indicator |
4.2.0 |
||||
|
CN#16 |
Version increased from Rel-4 to Rel-5 after CN#16 |
5.0.0 |
|||||
|
CN#26 |
Version increased from Rel-5 to Rel-6 after CN#26 |
6.0.0 |
|||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
2009-12 |
– |
Update to Rel-9 version (MCC) |
9.0.0 |
||||
|
2011-03 |
– |
Update to Rel-10 version (MCC) |
10.0.0 |
||||
|
2011-06 |
Correction of references to non-existent specifications |
10.1.0 |
|||||
|
2012-09 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||||
|
2014-09 |
– |
Update to Rel-12 version (MCC) |
12.0.0 |
||||
|
2015-12 |
– |
Update to Rel-13 version (MCC) |
13.0.0 |
||||
|
2017-03 |
– |
Update to Rel-14 version (MCC) |
14.0.0 |
||||
|
2018-06 |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
||||
|
2020-07 |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
||||
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |