B.2.1 Rule A2: Exponent notation
24.0073GPPGeneral AspectsMobile radio interface signalling layer 3Release 17TS
An arithmetic expression used as exponent after a delimited string description is used to indicate repetitions.
A numerical expression between parentheses indicates a fixed number of repetitions.
<octet> ::= {0 | 1}(8) ;
is equivalent to
<octet> ::= {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} ;
This could also be written:
<octet> ::= bit(8) ;
When the exponent is negative or equal to 0, the exponentiated construction is equivalent to the null string.
An example of a common construction is the following:
<name : bit(5)>
Simple arithmetic, using numbers, terms "+", "-", "*" and "/", and parentheses are allowed in expressions.
Example:
<octet string(40)> ::= <octet>(8*(4+1)) ;
A star used alone between parentheses, or a double star, indicates a finite, possibly null, but indeterminate, number of repetitions. (The star used as an exponent can be understood also as meaning the union of all the sets obtained by replacing the star by zero or some positive integer).
<all bit strings> ::= {0 |1}(*) ;
<all bit strings> ::= {0 |1}** ;
This allows a shorter notation of recursive constructions such as:
<all bit strings> ::= {0|1} <all bit strings> | null;
A shorter notation is allowed when the expression has a single term, consisting of a star followed by the term:
<octet> ::= {0 | 1}*8 ;
<octet string(40)> ::= <octet>*(8*(4+1)) ;
<all bit strings> ::= bit**;
Application note:
The indefinite exponent is usually combined with some mean to indicate to the decoder the end of the repetition. Different techniques exist, such as indicating in a previous field the number of repetitions. Another technique is one-bit tagging, an example of which follows: {1 <item>}** 0.
Annex C (informative):
GPRS‑Services sequence diagram
Instead of providing a complete set of all scenarios, the intention of this clause is to provide some typical examples. It shall be noted, that within the figures only those parameters of the PDUs and the service primitives are shown, which are needed for a general understanding of the examples. Furthermore during the examples below (except C.17) no cell re‑selection takes place.
NOTE: The standalone PDP context modification procedure should use graceful disconnection of the LLC link.
Annex D (informative):
Change history
|
TSG SA# |
Spec |
Version |
CR |
Rev |
Rel |
New Version |
Subject |
Comment |
|---|---|---|---|---|---|---|---|---|
|
Jun 1999 |
GSM 04.07 |
7.1.0 |
Transferred to 3GPP CN |
|||||
|
CN#04 |
24.007 |
3.0.0 |
||||||
|
CN#5 |
24.007 |
3.0.0 |
002 |
1 |
R99 |
3.1.0 |
Addition of LL-STATUS_IND |
|
|
CN#6 |
24.007 |
3.0.1 |
004 |
1 |
R99 |
3.2.0 |
Uplink L3 Message Sequencing |
|
|
CN#6 |
24.007 |
3.0.1 |
005 |
R99 |
3.2.0 |
Mirror R99 LCS CR to 04.07 |
||
|
CN#6 |
24.007 |
3.0.1 |
003 |
5 |
R99 |
3.2.0 |
Using MM sublayer for PS-SMS message transfer |
|
|
CN#6 |
24.007 |
3.0.1 |
001 |
5 |
R99 |
3.2.0 |
Transaction Identifier Extension |
|
|
CN#7 |
24.007 |
3.2.0 |
006 |
1 |
R99 |
3.3.0 |
Updating Session Management (SM) for R99 |
|
|
CN#7 |
24.007 |
3.2.0 |
007 |
R99 |
3.3.0 |
Removal of Anonymous Access |
||
|
CN#7 |
24.007 |
3.2.0 |
008 |
R99 |
3.3.0 |
PMMSMS-REL-Req deletion in MS side |
||
|
CN#7 |
24.007 |
3.2.0 |
010 |
1 |
R99 |
3.3.0 |
Integrity checking of signalling messages for UMTS |
|
|
– |
24.007 |
3.3.0 |
– |
– |
R99 |
3.3.1 |
Editorial changes |
|
TSGN |
TSGN-number |
WG Number |
Spec |
CR |
Rev |
Rel |
Cat |
Old vers |
New ver |
Title |
WI |
Notes/Date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CN#8 |
NP-000270 |
N1-000620 |
24.007 |
006 |
2 |
R99 |
F |
3.3.1 |
3.4.0 |
Updating SM for R99 |
GSM/UMTS Interworking |
|
|
CN#8 |
NP-000270 |
N1-000619 |
24.007 |
012 |
R99 |
F |
3.3.1 |
3.4.0 |
Remove GRR primitive descriptions and make reference to other document |
GSM/UMTS Interworking |
||
|
CN#8 |
NP-000269 |
N1-000763 |
24.007 |
014 |
2 |
R99 |
F |
3.3.1 |
3.4.0 |
Change of the GMM Ready Timer behaviour |
GPRS |
|
|
CN#08 |
NP-000269 |
N1-000668 |
24.007 |
015 |
R99 |
C |
3.3.1 |
3.4.0 |
New PD for LLC for use by DTM (Dual Transfer Mode) mobiles |
GPRS |
||
|
CN#8 |
NP-000270 |
N1-000669 |
24.007 |
016 |
R99 |
C |
3.3.1 |
3.4.0 |
Services provided by the Radio Resource Management entity |
GSM/UMTS Interworking |
||
|
CN#9 |
NP-000443 |
N1-001032 |
24.007 |
013 |
3 |
R99 |
F |
3.4.0 |
3.5.0 |
SAPs and Service primitives for UMTS, PS mode. |
GSM/UMTS Interworking |
adapted to adjust the older used release of the spec |
|
CN#9 |
NP-000443 |
N1-000880 |
24.007 |
018 |
R99 |
F |
3.4.0 |
3.5.0 |
Protocol discriminator value for UE special conformance testing functions |
GSM/UMTS Interworking |
||
|
CN#9 |
NP-000443 |
N1-001015 |
24.007 |
019 |
1 |
R99 |
F |
3.4.0 |
3.5.0 |
Correction of send sequence number method applied protocols |
GSM/UMTS Interworking |
|
|
CN#9 |
NP-000443 |
N1-000930 |
24.007 |
020 |
R99 |
F |
3.4.0 |
3.5.0 |
Editorial corrections!! |
GSM/UMTS Interworking |
||
|
CN#9 |
NP-000441 |
N1-000969 |
24.007 |
021 |
R99 |
F |
3.4.0 |
3.5.0 |
Protocol Discriminator for DTM (simple class A) |
GPRS |
||
|
NP-10 |
NP-000673 |
N1-001188 |
24.007 |
024 |
R99 |
F |
3.5.0 |
3.6.0 |
Removal of Flow Id from RR-SAP |
TEI |
||
|
NP-10 |
NP-000670 |
N1-001367 |
24.007 |
025 |
1 |
R99 |
F |
3.5.0 |
3.6.0 |
RABMAS-SAP and RABMSM-SAP adaptation for Handling of unsynchronized PDP contexts |
GPRS |
|
|
NP-10 |
NP-000671 |
N1-001246 |
24.007 |
027 |
R99 |
F |
3.5.0 |
3.6.0 |
Updating CS/PS protocol architecture figure with RABM |
GSM/UMTS Interworking |
||
|
NP-10 |
NP-000671 |
N1-001256 |
24.007 |
028 |
R99 |
F |
3.5.0 |
3.6.0 |
Alignment of 24.007 to other specs |
GSM/UMTS Interworking |
||
|
NP-11 |
NP-010123 |
N1-010101 |
24.007 |
025 |
2 |
R99 |
F |
3.6.0 |
3.7.0 |
Addition of Stream Identifier and NAS Synchronization Indicator to the primitives |
GSM/UMTS interworking |
03-2001 |
|
NP-11 |
NP-010123 |
N1-010083 |
24.007 |
032 |
|
R99 |
F |
3.6.0 |
3.7.0 |
Change MMAS-SAP to RR-SAP in fig. 5.6 |
GSM/UMTS interworking |
03-2001 |
|
NP-11 |
NP-010207 |
N1-010486 |
24.007 |
034 |
|
R99 |
F |
3.6.0 |
3.7.0 |
Transfer of the N(SD) duplication avoidance protocol from GSM 04.18 |
GSM/UMTS interworking |
03-2001 |
|
NP-11 |
NP-010205 |
N1-010447 |
24.007 |
035 |
|
R99 |
F |
3.6.0 |
3.7.0 |
Deletion of cause ‘unsynchronousPDP’ in RABMAS-SAP |
TEI |
03-2001 |
|
NP-11 |
NP-010206 |
N1-010444 |
24.007 |
031 |
3 |
Rel-4 |
B |
3.7.0 |
4.0.0 |
Adaptation of SS protocol to PS domain |
TEI |
03-2001 |
|
NP-14 |
NP-010682 |
N1-011811 |
24.007 |
043 |
1 |
Rel-4 |
A |
4.0.0 |
4.1.0 |
Clarification of the send sequence number mechanism |
GSM/UMTS interworking |
12-2001 |
|
NP-16 |
NP-020218 |
N1-021341 |
24.007 |
047 |
2 |
Rel-4 |
A |
4.1.0 |
4.2.0 |
RR protocol message type octet |
GSM/UMTS interworking |
06-2002 |
|
NP-16 |
NP-020222 |
N1-020893 |
24.007 |
049 |
1 |
Rel-4 |
A |
4.1.0 |
4.2.0 |
Clarification of the extension mechanism for type 4 IEs |
TEI |
06-2002 |
|
NP-16 |
NP-020224 |
N1-021367 |
24.007 |
053 |
1 |
Rel-4 |
F |
4.1.0 |
4.2.0 |
Various clean-up of wrong references, eg towards 44.018 and 23.271 |
TEI4 |
06-2002 |
|
NP-16 |
24.007 |
Rel-5 |
4.2.0 |
5.0.0 |
Plenary decision to make this TS also for Rel-5. |
06-2002 |
||||||
|
NP-17 |
NP-020383 |
N1-021836 |
24.007 |
057 |
1 |
Rel-5 |
F |
5.0.0 |
5.1.0 |
Clarification of the CN release indicators |
TEI5 |
09-2002 |
|
NP-22 |
NP-030485 |
N1-031653 |
24.007 |
059 |
1 |
Rel-6 |
F |
5.1.0 |
6.0.0 |
Don’t use SAPI to differentiate between messages of the same message type. |
TEI6 |
12-2003 |
|
NP-24 |
NP-040185 |
N1-040967 |
24.007 |
063 |
1 |
Rel-6 |
A |
6.0.0 |
6.1.0 |
Corrections concerning the use of the LCS protocol |
LCS |
06-2004 |
|
NP-25 |
NP-040377 |
N1-041625 |
24.007 |
064 |
1 |
Rel-6 |
B |
6.1.0 |
6.2.0 |
Update of the Session Management services – MBMS |
MBMS |
09-2004 |
|
NP-25 |
NP-040375 |
N1-041645 |
24.007 |
067 |
4 |
Rel-6 |
B |
6.1.0 |
6.2.0 |
Sequence number handling during redirection in MOCN sharing scenario |
NTShar |
09-2004 |
|
NP-26 |
NP-040501 |
N1-04844 |
24.007 |
070 |
A |
6.2.0 |
6.3.0 |
Sequence numbering for SS via PS |
TEI4 |
12-2004 |
||
|
NP-27 |
NP-050068 |
N1-050045 |
24.007 |
072 |
Rel-6 |
A |
6.3.0 |
6.4.0 |
Addition of maximum data rate to RR_SYNC_IND and MMCC_SYNC_IND |
SCUDIF |
03-2005 |
|
|
CP-29 |
CP-050361 |
C1-050966 |
24.007 |
074 |
Rel-6 |
F |
6.4.0 |
6.5.0 |
Use of short header format on SDCCH / FACCH |
TEI6 |
09-2005 |
|
|
CP-29 |
CP-050366 |
C1-051030 |
24.007 |
075 |
1 |
Rel-7 |
F |
6.5.0 |
7.0.0 |
Handling of the L2 Pseudo Length |
TEI7 |
09-2005 |
|
CP-42 |
CP-080866 |
C1-085163 |
24.007 |
0078 |
2 |
Rel-8 |
B |
7.0.0 |
8.0.0 |
Support of EPS NAS protocols |
SAES |
12-2008 |
|
CP-43 |
CP-090125 |
C1-091296 |
24.007 |
0082 |
2 |
Rel-8 |
F |
8.0.0 |
8.1.0 |
UE side architecture figure without CSFB |
SAES |
03-2009 |
|
CP-43 |
CP-090153 |
C1-091320 |
24.007 |
0083 |
2 |
Rel-8 |
F |
8.0.0 |
8.1.0 |
Architecture figure for EPS UE + CSFB |
SAES-CSFB |
03-2009 |
|
CP-43 |
CP-090130 |
C1-091182 |
24.007 |
0085 |
1 |
Rel-8 |
F |
8.0.0 |
8.1.0 |
Message duplication in S1 mode |
SAES |
03-2009 |
|
CP-43 |
CP-090125 |
C1-091106 |
24.007 |
0086 |
1 |
Rel-8 |
F |
8.0.0 |
8.1.0 |
Add reference of LTE test control specification |
SAES |
03-2009 |
|
CP-43 |
CP-090126 |
C1-091350 |
24.007 |
0087 |
2 |
Rel-8 |
F |
8.0.0 |
8.1.0 |
Clarification of format of LV-E/TLV-E Length Indicator format |
SAES |
03-2009 |
|
CP-43 |
24.007 |
Rel-8 |
8.0.0 |
8.1.0 |
Editorial cleanup by MCC |
03-2009 |
||||||
|
CP-44 |
CP-090422 |
C1-092120 |
24.007 |
0090 |
1 |
Rel-8 |
F |
8.1.0 |
8.2.0 |
Handling of sequence numbers |
SAES-SRVCC |
06-2009 |
|
CP-46 |
Rel-9 |
8.2.0 |
9.0.0 |
Upgrade to Rel-9 by MCC |
12-2009 |
|||||||
|
CP-51 |
Rel-10 |
9.0.0 |
10.0.0 |
Upgrade to Rel-10 by MCC |
03-2011 |
|||||||
|
CP-56 |
CP-120309 |
C1-121630 |
24.007 |
0094 |
2 |
Rel-11 |
F |
10.0.0 |
11.0.0 |
Clarify maintenance concept for this specification |
TEI11 |
06-2012 |
|
CP-60 |
CP-130264 |
C1-131596 |
24.007 |
0095 |
1 |
Rel-12 |
F |
11.0.0 |
12.0.0 |
CM sublayer of EPS services |
TEI12 |
06-2012 |
|
CP-60 |
CP-130264 |
C1-131744 |
24.007 |
0096 |
2 |
Rel-12 |
11.0.0 |
12.0.0 |
Clarify on specification maintenance |
TEI12 |
06-2012 |
|
|
CP-70 |
24.007 |
Rel-13 |
12.0.0 |
13.0.0 |
Upgrade to Rel-13 by MCC |
12-2015 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CP-75 |
CP-170129 |
0099 |
2 |
B |
Addition of ePCO for GPRS |
14.0.0 |
|
2018-03 |
CP-79 |
CP-180075 |
0100 |
1 |
B |
Extended protocol discriminator |
15.0.0 |
|
2018-03 |
CP-79 |
CP-180075 |
0101 |
1 |
B |
Update of protocol discriminator values for test procedures for 5GS |
15.0.0 |
|
2018-03 |
CP-79 |
CP-180075 |
0103 |
2 |
B |
For 5GS – UE protocol architecture |
15.0.0 |
|
2018-03 |
CP-79 |
CP-180075 |
0104 |
2 |
B |
For 5GS – message and security headers and PDU session identities |
15.0.0 |
|
2018-03 |
CP-79 |
CP-180075 |
0107 |
B |
Format of standard IE for 5GS |
15.0.0 |
|
|
2018-03 |
CP-79 |
CP-180075 |
0108 |
1 |
B |
Scope update for 5GS |
15.0.0 |
|
2018-03 |
CP-79 |
CP-180075 |
0110 |
B |
Definition of 5GS NAS message type for 5GS |
15.0.0 |
|
|
2018-06 |
CP-80 |
CP-181057 |
0111 |
1 |
B |
Specification of security protected 5GS NAS message header |
15.1.0 |
|
2018-06 |
CP-80 |
CP-181069 |
0112 |
2 |
B |
EPS bearer identity in NAS message header |
15.1.0 |
|
2018-06 |
CP-80 |
CP-181057 |
0113 |
1 |
B |
Include TS 24.501 and TS 24.502 among the layer 3 related Technical Specifications |
15.1.0 |
|
2018-06 |
CP-80 |
CP-181058 |
0114 |
2 |
B |
PDU session identity |
15.1.0 |
|
2018-09 |
CP-81 |
CP-182128 |
0116 |
2 |
F |
Interaction when uplink user data packet is to be sent via a PDU session with suspended user-plane resources |
15.2.0 |
|
2018-09 |
CP-81 |
CP-182128 |
0117 |
1 |
F |
Correction on PTI definition |
15.2.0 |
|
2018-09 |
CP-81 |
CP-182128 |
0118 |
1 |
F |
Multiple access technologies in NG-RAN carrying 5GS NAS |
15.2.0 |
|
2018-12 |
CP-82 |
CP-183030 |
0121 |
2 |
F |
Value range of IEs for 5GMM and 5GSM protocols |
15.3.0 |
|
2018-12 |
CP-82 |
CP-183030 |
0122 |
F |
Correction to scope |
15.3.0 |
|
|
2019-03 |
CP-83 |
CP-190105 |
0123 |
F |
EPS bearers not released when moving to EMM-IDLE |
16.0.0 |
|
|
2019-06 |
CP-84 |
CP-191145 |
0124 |
F |
EPS bearers not released when moving to EMM-IDLE |
16.1.0 |
|
|
2020-03 |
CP-87e |
CP-200128 |
0128 |
3 |
D |
Correcting reference |
16.2.0 |
|
2020-06 |
CP-88e |
CP-201131 |
0129 |
1 |
F |
Type 3 IE is not recommended to be used as an optional IE |
16.3.0 |
|
2020-09 |
CP-89e |
CP-202170 |
0130 |
1 |
F |
IEI assignment rule between TSN AF and TSN translator |
16.4.0 |
|
2020-12 |
CP-90e |
CP-203188 |
0132 |
F |
Updates due to eV2XARC |
16.5.0 |
|
|
2020-12 |
CP-90e |
CP-203218 |
0133 |
F |
Include TS 24.519 among the layer 3 related Technical Specifications |
16.5.0 |
|
|
2020-12 |
CP-90e |
CP-203179 |
0134 |
1 |
F |
Updates due to ATSSS |
16.5.0 |
|
2020-12 |
CP-90e |
CP-203213 |
0138 |
F |
Updates due to ProSe signalling messages sent over the PC3 or PC5 interfaces |
16.5.0 |
|
|
2020-12 |
CP-90e |
CP-203214 |
0131 |
1 |
F |
Recommendation about the use of type 2 IEs |
17.0.0 |
|
2020-12 |
CP-90e |
CP-203168 |
0135 |
1 |
F |
PDU session IDs exclusive for the 5G core network |
17.0.0 |
|
2020-12 |
CP-90e |
CP-203168 |
0136 |
F |
IEI assignment from UE policy delivery service |
17.0.0 |
|
|
2020-12 |
CP-90e |
CP-203214 |
0139 |
F |
Coding of successive half-octet IEs |
17.0.0 |
|
|
2021-03 |
CP-91e |
CP-210116 |
0140 |
F |
UE policy delivery service missing |
17.1.0 |
|
|
2021-06 |
CP-92e |
CP-211150 |
0141 |
1 |
Corrections to L3 Messages description |
17.2.0 |
|
|
2022-03 |
CP-95e |
CP-220268 |
0142 |
– |
B |
Add new TS 24.554 |
17.3.0 |
|
2022-06 |
CP-96 |
CP-221111 |
0144 |
1 |
B |
Include TS 24.538 among the layer 3 related technical specifications |
17.4.0 |
|
2022-09 |
CP-97 |
CP-222158 |
0146 |
1 |
C |
Correction of the comprehension required criterion |
17.5.0 |