A.3 Contents of messages
04.103GPPMobile Radio Interface Layer 3 - Supplementary Services Specification - General AspectsTS
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 GSM 04.80 and GSM 09.02. 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 | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
Release 92 | Last common Phase 1/Phase 2 version | 3.2.3 | |||||
June 1991 | CR 04.10‑13 rev 2 (category D) / CR 04.10‑14 rev 1 (category D) | 4.0.0 | |||||
April 1992 | CR 04.10‑22 (category C) / CR 04.10‑24 rev 1 (category D) | 4.0.0 | 4.1.0 | ||||
Jan. 1993 | CR 04.10‑31 (category D) / CR 04.10‑32 rev 2 (category C) | 4.1.0 | 4.2.0 | ||||
April 1993 | CR 04.10‑28 rev 3 (category B) / CR 04.10‑29 rev 2 (category B) | 4.2.0 | 4.3.0 | ||||
June 1993 | CR 04.10‑43 rev 3 (category D) / CR 04.10‑45 (category B) | 4.3.0 | 4.4.0 | ||||
Oct. 1993 | CR 04.10‑47 rev 1 (category F) approved by SMG#08 | 4.4.0 | 4.5.0 | ||||
Jan. 1994 | CR 04.10‑48 rev 2 (category F) | 4.5.0 | 4.6.0 | ||||
April 1994 | CR 04.10‑51 (category F) CR 04.10‑52 rev 1 (category F)approved by SMG#10 | 4.6.0 | 4.7.0 | ||||
July 1994 | CR 04.10‑54 rev 1 (category F) approved by SMG#11 | 4.7.0 | 4.8.0 | ||||
Oct. 1994 | TS changed to final draft prETS 300 558 | 4.8.0 | 4.8.1 | ||||
Jan. 1995 | TS changed to ETS 300 558 First edition | 4.8.1 | 4.8.2 | ||||
Jan. 1995 | AR 04.10‑A001 rev 1 (category 2) approved by SMG#13 | 4.8.2 | Amendment 1 | ||||
Feb. 1996 | CR 04.10‑A004 rev 1 (category F) approved by SMG#17 | Amendment 1 | 4.10.0 | ||||
Aug. 1996 | TS changed to ETS 300 558 Second edition | 4.10.0 | 4.10.1 | ||||
Dec. 1996 | TS changed to draft prETS 300 941 (Release 96) | 4.10.1 | 5.0.0 | ||||
May 1997 | TS changed to ETS 300 941 first edition | 5.0.0 | 5.0.1 | ||||
March 1998 | CR 04.10-A005r3 (CCBS and TEI R97) | 5.0.1 | 6.0.0 | ||||
July 1998 | Specification published as TS 100 941 | 6.0.0 | 6.0.1 | ||||
Feb. 1999 | CR 04.10-A007r1 (category B) (UUS Release 98) approved SMG#28 | 6.0.1 | 7.0.0 | ||||
June 1999 | Publication of version 7.0.1 | 7.0.0 | 7.0.1 | ||||
Dec. 2001 | CN#14 | NP-010616 | A010 | Usage of SS Version Indicator | 7.0.1 | 7.1.0 | |